- dovecot - dovecot.org

[Dovecot] Dovecot 2.0.16 question...
by Farokh Irani 30 Apr '14

30 Apr '14

I'm running Dovecot 2.0.16 on OS X Server 10.7.5 and I've got a problem with IMAP searches. There are a couple of accounts that are unable to search using an IMAP search, but I can't seem to find anything wrong. Any pointers on what I can do? Is there a search index file that I can delete to force a rebuild, or a script or app that will do that? I tried to use update-fts-index.pl, but to no avail. Thanks! Farokh ---------------------------------------------------------------------------- MCF Software...simply dependably engineered For all your computer and networking needs including hosting solutions for every need. Phone: 845-735-0210 Cell: 914-262-1594

1 0

[Dovecot] doveadm import : Error creating new mailbox
by Administrator BCS 29 Apr '14

29 Apr '14

Hello, I'm new to dovecot. I managed to set up a system running dovecot/mysql/postfix/postfixadmin with a virtual maildir setup on Ubuntu 12.04 I can add and remove users, send and receive mail, create folders, move mail between them etc so all ok. Now trying to manually import some mbox files from the old server into dovecot. Copied a mbox file to the new system, converted it to Maildir with mb2md resulting in a directory containing the new, cur en tmp. Looks ok, old email messages are all there. When importing this folder using doveadm import it fails with the message: Error: Couldn't create mailbox maildir:/home/vmail/bezoekerscentrumsonsbeek.nl/techniek/.INBOX: Invalid mailbox name What am I doing wrong? Martin output from doveadm -D import: > ┌─(adje@BCS:pts/0)──────────────────────────────────────────────────────────────────────────────────────────────────────(~)─┐ > └─(89:10:33:%)── sudo doveadm -D import -u > techniek(a)bezoekerscentrumsonsbeek.nl > maildir:/mnt/multimedia/mailoudeserver/testmap/techniek > maildir:/home/vmail/bezoekerscentrumsonsbeek.nl/techniek/ all > doveadm(root): Debug: Loading modules from directory: > /usr/lib/dovecot/modules/doveadm > doveadm(root): Debug: Skipping module doveadm_acl_plugin, because > dlopen() failed: > /usr/lib/dovecot/modules/doveadm/lib10_doveadm_acl_plugin.so: undefined > symbol: acl_user_module (this is usually intentional, so just ignore > this message) > doveadm(root): Debug: Skipping module doveadm_expire_plugin, because > dlopen() failed: > /usr/lib/dovecot/modules/doveadm/lib10_doveadm_expire_plugin.so: > undefined symbol: expire_set_deinit (this is usually intentional, so > just ignore this message) > doveadm(root): Debug: Skipping module doveadm_quota_plugin, because > dlopen() failed: > /usr/lib/dovecot/modules/doveadm/lib10_doveadm_quota_plugin.so: > undefined symbol: quota_user_module (this is usually intentional, so > just ignore this message) > doveadm(root): Debug: Skipping module doveadm_zlib_plugin, because > dlopen() failed: > /usr/lib/dovecot/modules/doveadm/lib10_doveadm_zlib_plugin.so: undefined > symbol: i_stream_create_deflate (this is usually intentional, so just > ignore this message) > doveadm(root): Debug: Effective uid=0, gid=0, home=/home/adje > doveadm(root): Debug: maildir++: > root=/mnt/multimedia/mailoudeserver/testmap/techniek, index=, control=, > inbox=/mnt/multimedia/mailoudeserver/testmap/techniek, alt= > doveadm(techniek(a)bezoekerscentrumsonsbeek.nl): Debug: Added userdb > setting: mail=maildir:/home/vmail/bezoekerscentrumsonsbeek.nl/techniek > doveadm(techniek(a)bezoekerscentrumsonsbeek.nl): Debug: Added userdb > setting: plugin/quota=dirsize:storage=0 > doveadm(techniek(a)bezoekerscentrumsonsbeek.nl): Debug: Effective uid=150, > gid=8, home=/home/vmail/bezoekerscentrumsonsbeek.nl/techniek > doveadm(techniek(a)bezoekerscentrumsonsbeek.nl): Debug: maildir++: > root=/home/vmail/bezoekerscentrumsonsbeek.nl/techniek, index=, control=, > inbox=/home/vmail/bezoekerscentrumsonsbeek.nl/techniek, alt= > doveadm(techniek(a)bezoekerscentrumsonsbeek.nl): Debug: Namespace : > /home/vmail/bezoekerscentrumsonsbeek.nl/techniek/.maildir:/home/vmail/bezoekerscentrumsonsbeek.nl/techniek/.INBOX doesn't exist yet, using default > permissions > doveadm(techniek(a)bezoekerscentrumsonsbeek.nl): Debug: Namespace : Using > permissions from /home/vmail/bezoekerscentrumsonsbeek.nl/techniek: > mode=0700 gid=-1 > doveadm(techniek(a)bezoekerscentrumsonsbeek.nl): Debug: Namespace : > /home/vmail/bezoekerscentrumsonsbeek.nl/techniek/.maildir:/home/vmail/bezoekerscentrumsonsbeek.nl/techniek/.INBOX doesn't exist yet, using default > permissions > doveadm(techniek(a)bezoekerscentrumsonsbeek.nl): Debug: Namespace : Using > permissions from /home/vmail/bezoekerscentrumsonsbeek.nl/techniek: > mode=0700 gid=-1 > doveadm(techniek(a)bezoekerscentrumsonsbeek.nl): Error: Couldn't create > mailbox maildir:/home/vmail/bezoekerscentrumsonsbeek.nl/techniek/.INBOX: > Invalid mailbox name Output of dovecot -n > # 2.0.19: /etc/dovecot/dovecot.conf > # OS: Linux 3.11.0-20-generic x86_64 Ubuntu 12.04.4 LTS ext4 > auth_mechanisms = plain login > first_valid_uid = 150 > last_valid_uid = 150 > mail_gid = mail > mail_location = maildir:/home/vmail/%d/%n > mail_uid = vmail > passdb { > args = /etc/dovecot/dovecot-sql.conf.ext > driver = sql > } > postmaster_address = adje(a)bezoekerscentrumsonsbeek.nl > protocols = " imap pop3" > service auth { > unix_listener /var/spool/postfix/private/auth { > group = postfix > mode = 0660 > user = postfix > } > unix_listener auth-userdb { > group = mail > mode = 0600 > user = vmail > } > } > ssl_cert = </etc/ssl/certs/dovecot.pem > ssl_key = </etc/ssl/private/dovecot.pem > userdb { > args = /etc/dovecot/dovecot-sql.conf.ext > driver = sql > } -- Systeembeheer Bezoekerscentrum Sonsbeek

3 6

[Dovecot] [repost] log sasl auth
by Roberto Tagliaferri - Tosnet srl 29 Apr '14

29 Apr '14

Excuse for the previous post. Hi, i've in use dovecot for pop3, imap and for sasl authenticator (for postfix). Can i log all sasl auth in a sql db (or in a flat file, or to a pipe)? -- Roberto Tagliaferri Tosnet srl

1 0

[Dovecot] log auth in a dn
by Roberto Tagliaferri - Tosnet srl 28 Apr '14

28 Apr '14

ÿØÿáExifII*ÿìDuckydÿáohttp://ns.adobe.com/xap/1.0/<?xpacket begin="ï»¿" id="W5M0MpCehiHzreSzNTczkc9d"?> <x:xmpmeta xmlns:x="adobe:ns:meta/" x:xmptk="Adobe XMP Core 5.3-c011 66.145661, 2012/02/06-14:56:27 "> <rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"> <rdf:Description rdf:about="" xmlns:xmpMM="http://ns.adobe.com/xap/1.0/mm/" xmlns:stRef="http://ns.adobe.com/xap/1.0/sType/ResourceRef#" xmlns:xmp="http://ns.adobe.com/xap/1.0/" xmpMM:OriginalDocumentID="xmp.did:F57A6890EE79E311A005A1F913A30D81" xmpMM:DocumentID="xmp.did:67FAA6F27A1311E3B506EF72D9F2709E" xmpMM:InstanceID="xmp.iid:67FAA6F17A1311E3B506EF72D9F2709E" xmp:CreatorTool="Adobe Photoshop CS6 (Windows)"> <xmpMM:DerivedFrom stRef:instanceID="xmp.iid:F57A6890EE79E311A005A1F913A30D81" stRef:documentID="xmp.did:F57A6890EE79E311A005A1F913A30D81"/> </rdf:Description> </rdf:RDF> </x:xmpmeta> <?xpacket end="r"?>ÿîAdobedÀÿÛÿÀdÿÄ !1#"A$5'w( !1AQa"q2BR#±²Â3s4¡Ñr¢dÿÚ?ŸŸB¹WÞýEØ&SqêõsÑðÌzL+ØÔÖ¹1s*7Iå\Þ£ÐGh»stIIêITwÌI-(nA!¹Âãð²a4û&$¶R|:°:ü+-Ìs\ÇbÃÀõñBd2:Öàýße!5Çþ¹ ¹[U=Ó|d'·³<=Uî7$é¥Å@*ÊñÚérTkÂÜ°µ#øFúv®?Û.IFµüÊ£øê«yÜ¿YbÜ)3°Ûþž^Ö¿aÉiy$ÓH$ÃIÏ¯©F°eç»šãßÏ·Yªú }ú(£¢®äN¹Õ ºÕ qŽRÙÙæiòqYŠ©<¶úÚfÐù`ËML)d?ÉOf¢(€NÂFN0Â ò1¥3æ/x!·{v÷UFo/!2O ?ú#)(o íñí_Ÿ-bý%VôëÍ¿ì%«¹ñ¢M,pÍdØDRFÉj×£m]Í<$=))Mf| fàEÜ<à_«3ÁèÇÞæDÝðó2Ý€0óF\ù0°ÇG{üÄÅ·ð·©nÞätµ?Q|Úè«ëO]Meèf×ú+SÇONâ¡|Íú/sÈP·üJM»:g€dïï.Ö7ugQuQsásoÖj'(#yªÄB ~Êð(uÅKI/Uë¶¬%ñÊªÍbÙŒÞ7eÒ!aÿ#`{%®ISÊs$; h@yp2Á9ÆJ ÛyZÖÆ÷éJ{ìOlùàcG»s6Ü5îKÓóS|/È÷â|_äñÝñŒ^~ÿg»ÅïÛÛßþŸÝAMÒ·Ÿ9Î4wrœ=¿ê®Âþñ$»©ñºúúÅ)ýßÒÝ5>v*-©[ïÇMÑ®uÓvjÉ²¶6ãBJ×ÕšéªäŠHH¶FðbT 8` ¡ñ8ê÷²y(qÓçu}®ÕúW67éÌŸBp}êBÁ t6°® ?nTbÍž©6Æ5®U¿Ùd5ÅhÎòl6ü¢2Q,$ÍõÜÍÁÑ¥Ø¡5åîJžÁ/VQÁ`$¿é_ü^94°$°»/bMl & ÅXsñ·%žžû"*¥RTŒNÖ6úäXÕmy{]9²Ü2tÇx=Ç k{Þý~e©ÉtHÒ d©H,d\dû¿œª×CŸ3s»fá/µQG?î h9ÚÝzhÆÂúpzSTr+ÅçŠJË`ÄZåHVÕÖì«ÔÆÈKìò²t¶ý« hŸÛ`·(NnàRme}¿ŠÛÂÐÙF¥à÷6èÜA¥ÙA1FëZy5+QŠÇ&dxx¬ñOÃ+©k;nnüoni~##å 'óÉ $2$Lª¬ ±XÂ»ØÊê®å{jnJuSÁ·]Š-Ø²9UâÆHYç`ylPó±·«ôé@MÏzGmUbÀ0®F)JI $±â$|n>9c6ä?aEŸ?9žÿ:ÓM7>J0H¹ÔdI a¥Ò±÷ékTÑ¡e[Oæ\oí|¥tªÿ¡ãå4uÈùý'mŸŠåYLÐûDÕb ySn× DTr~x¹t( ¬¥ã80åG Ëùoó/à~Ñð=WÃM-Lñ¹Êü^uÎDBñ¹7õ¢ÒÏþµ'd£ñYþWZFõnO× (^QX»m{ò É^Ø^`ÏÏàÆ¥3u×60¿M€Â-Fcmu\ÔYsy\Æ 66¿}A9Ëy8þ¶H°ÃcÖÃbaÚK7NóÜ*·Î8Ø 1ó2¹.â&%Èj,1ZÇÈºnb ÌöîÒïW6îØ.ÙZ®*é]²4}A_>Ö³ |ù!jb~ëŽÍÆÞ+²ëÂÝÿ${\¹ÞT'V2C!._o Kò`Àhm[n:\-õkRåæs<N(ä3$Å=f ÄV;ù€eÜc[±ä±ÚÊÖSÅmø7BÁåP¢ÔÔ×S 2²šv'`)$SšuÄðs&Aªé9óÇäÅ¥â@ŸjŒž¶¢TaÀ*2"»ýÆöÉÇJò¬²«Xsæak©°|×œôµ«Î@òsžøÐIŽRJÁQŸëH·fm /ž>}RGäQHÓôØÌº6Æèüäo°0LèpXgŸEc'}ý}:©æÂŽäØ\ô¬ÓîMÙžÅN>©/\àÿÏÉÆ»×VLUTvÏ9vdWå x§®Ö'8ÓEe¹`\ËqVµ·È8@ÏWðãbò3GçoD9à|ª×ŸOÝµ¬zÞ±ÙyüÓøyé§»öû×ioç<vîUL²_iC_/ÃÛãÄûº.?ëùß©Y_ÇO°ýÍÛõ_¹ÿrÿõØÿXù;÷œ|³ÕEñýkÙýœú\n·ÆÖ¿ÙZ¹×nøœößclÝß³~íŸïã^w&1#êÔÃ!Ìä²évžÝñŽqšæÿ"~¬äÍlÀ<Ò ÷W%EN0&dXÇ¿F3*äFÌl¡ÔÜ.(ÍW|9R0ZC®ISa©_gk7.¹/;ÑšGZÏµÙã`fPF6 -Ñ'û_O¥oBè°. ³F2Æi94(Âc À÷ëÎyrñH#é{\16ÔÃXþÊéÜŸ+ñÛ ºêP°VpÚÌ:@&új)jÕ{N+ëYN·ñÞï°QÉ4¡âµGcæØºXŒ×wYäÕw4Rh3Â£Ó"uyÙÕA¡ìHg&>#ezþ è-È±µ#p=|)2ªø,cÆ¶ Î«Û³;l®Jn$šÒ(K7ÓÇ^òªµŠìò+8€ÙðØv%àkÖ`Ç5Ý®W7ÌþÉX?ÊÈÚ ,íQJÅÈZE!i 'R¯üŒÙX92CW 3«Oe¯b@Sn€kã¹Þ>ÎjXV^fp6Âdp³naœ±ÚB€jd³-eìî®ßºåO'×ÞnÛŒÊÚ7wzËÉmCN®NÆØ¹<v©`IzDêhÞ¥ Ä]Îcï_1&Ã¶«1éšíXùI×KU+Çfó*Ï-vñ¢+#Ô\k0)(*·ÜEjÃGéËr¶ÜZ6£DNuŽÎäé?ºTN·³2Ëg¬,WØÊóeË^sÙû=;,c3,mqýÐäâÌtÿhZú>Šv^Dàï¡ídHÔÜ÷~cI§vœµ,o¶§È6B¿M©)ŠÞk|uª6ßÇ(Ï®ÏðÐ{[äSê"ÄåSÜñÑ?(n0CJ¡åš0FH:ç @å$ã8³ñÖãÅN£Æºäðli,$'!oÈŸ×±Rz:;T,ÀSKøÿ¶#|qvðõ®7ÜïJ^Ù;§R±56drêÌïXôYŸLž¹ §[»NöÀb°"tXØ"I<F&Ø{ÈýîHÊE5Õ_],À©:\Ž¥À=*ñMÄqÒd@%ÌÅ+$ù|ÌÑ<rš¹(YLÊmb¶Ý®êbÚeOjxE Â1ëÉeqãIÎÃégWëRžÀ ^þ¥úÊ]`·Ó€p!ÀñäÃ\H8d"3O@Ø+ï,{XòÄ[°¥7· IcV%ÆöxD+Ü\ÝÓsµ¯±cV¬NàåDª»Ë+jòvŒ3U°šèòh©:r$ÒI=Ï?²§íñãP3Fk62Ä^=ñç¥ZD Ì2³áµBÿX$jL§ÛXÑnâò4£áaè®FÉŒ¶[aŽ~ÎK§w%+r²ÆvFŠkYôŸØ3qè5ÃIQ¢FèùäNWàz€IP€ŒÁupE w *XÍu ¶7ÎLÙÓñ¹^Þ5RE1vÛäac¢6ÖÆàõ&=Žµ¢Ç"ÂæŒDë×ÕðÝwº)µ¶úcd¯Yõ§Zf?fY`ñ ê|µdÞ çV×ôÎdL-4ó$F·gRãzl "^;m*îXFHš>É=;[º®WªÚœ£¢:(£¢:(£¢:(£¢:(£¢:(£¢:(£¢ÿÙ

1 0

[Dovecot] Why does it appear that dovecot is deleting messages after migration?
by Bill Eccles 28 Apr '14

28 Apr '14

Hi, y'all, long-time Mac OS X Server user Bill here with a thorny question for the mailing list since nobody at discussions.apple.com can quite put their finger on the answer. While well-aquainted with other aspects of Server, Dovecot is a bit of a mystery still to me. So here it goes: Background I'm struggling to migrate from MacOS X 10.6 to 10.9. I tried twice using the "live server in target disk mode" method, but after things went horribly awry (meaning I was left with no working services on the new server), I gave up on that and have been working to slowly bring services over, one at a time. I've got both Dovecot and PostFix accepting connections from my test machine, and I am able to connect with IMAP to the new server. What I Do... First, I turn both mail servers off. Then I tar up the /var/spool/imap/dovecot/mail directory on the old server, move it to the new server, untar it in /Library/Server/Mail/Data/ (where it belongs), and change ownership to _dovecot:mail, all per many other suggestions found in the Apple forums. (All files appear to be in maildir format, that I can tell.) I then turn the mail service back on on the new server. What Dovecot Does... (or appears to do) If I quickly connect to the new server with my IMAP client (MacOS X Mail.app) and create a "fresh user" in Mail.app, message folders appear correctly. But it's only a matter of time before Dovecot, or something, runs "doveadm index -u (usernames) (mailboxes)" on all of the mailboxes. As it does, it deletes thousands of messages, leaving, for example, the same 17 in INBOX and 3695 in "Deleted Items Archive". And 0 in others, and other seemingly-random numbers of messages in still yet others. I can watch it marching through the mailboxes, one at a time, if I "ps -ax" enough times. What I've Done to Counteract This... Nothing I've done so far has been able to do anything about it. Re-untar the archive, and it just does it all again. Try using dsync, and it just deletes the messages from the un-tar'd archive. In other words, there are thousands of messages in the archive which don't seem to meet Dovecot's requirement for being in that particular folder, so it deletes them. The "cur" directory in a mailbox directory may start out with >21000 messages in it, but when it's done, it'll have deleted the same messages from "cur" every time, leaving me with a fraction of what I started out with. I even used the 65-migrate_mailboxes.pl script (supplied as part of OS X 10.9 Server), and the same thing happens. (The migrate script does a lot more than just what I've noted above, but most of what it does is responsible for settings and configuration migration. Very little of the script is responsible for moving the data, and that part of the script ends up being a bunch of "cp" followed by a "chown"--essentially what I'm doing.) The Questions What is going on? Failing a fix, am I trying to migrate the wrong way? Is there a better way? Random Thoughts and Observations I've changed hostnames. The old one was shr-xs.mydomain.net, and the new one is shr-mini.mydomain.net. Is it unhappy with that for some reason? In one of the directories where messages are deleted, there were a zillion files named like this: 1396718896.M324523P43630.shr-xs.mydomain.net,S=1209,W=1238:2,Sac There were also a bunch of files named like this: 1211416234.cyrus.457,S=893:2,Sac When it's all said and done, and Dovecot has done its thing, care to guess which ones are left? Only these: 1211416234.cyrus.457,S=893:2,Sac Just to see if I could influence which files get deleted, I deleted all of the dovecot* files in the mailbox directory. And Dovecot recreated them faithfully, but still deleted all but the ones which said "cyrus" in the filenames. I changed the hostname to match shr-xs.mydomain.net, and that doesn't seem to have affected things a bit, though I don't have enough data to support that I really succeeded in changing the hostname for all services (specifically for Dovecot). Is Dovecot really filtering out messages that just don't seem to "belong" in the folder? Thanks, y'all. I've puzzled on this one for about eight hours and it now hurts my brain. I hope somebody else has an answer sans brain hurts.

3 3

[Dovecot] dovecot temporary suspension all of pop3 login about 5 minutes
by Jason 28 Apr '14

28 Apr '14

Dear All， When the user login P0P3 more than 10 times in 1 minute that the dovecot temporary suspension all of pop3 login about 5 minutes. How to disable the setting for dovecot. Mail Log: Apr 24 16:11:14 mww dovecot: pop3-login: Login: user=<scan>, method=PLAIN, rip=192.168.16.84, lip=192.168.16.159, mpid=8767, session=<5USPZMX3/QDAqBBU> Apr 24 16:11:14 mww dovecot: pop3(scan): Disconnected: Logged out top=0/0, retr=0/0, del=0/0, size=0 Apr 24 16:11:15 mww dovecot: auth-worker: Error: no talloc stackframe at ../source3/param/loadparm.c:4864, leaking memory Apr 24 16:11:15 mww dovecot: pop3-login: Login: user=<scan>, method=PLAIN, rip=192.168.16.84, lip=192.168.16.159, mpid=8769, session=<GzyeZMX3/wDAqBBU> Apr 24 16:11:15 mww dovecot: pop3(scan): Disconnected: Logged out top=0/0, retr=0/0, del=0/0, size=0 Apr 24 16:11:16 mww dovecot: auth-worker: Error: no talloc stackframe at ../source3/param/loadparm.c:4864, leaking memory Apr 24 16:11:16 mww dovecot: pop3-login: Login: user=<scan>, method=PLAIN, rip=192.168.16.84, lip=192.168.16.159, mpid=8771, session=<bGSsZMX3AQDAqBBU> Apr 24 16:11:16 mww dovecot: pop3(scan): Disconnected: Logged out top=0/0, retr=0/0, del=0/0, size=0 Apr 24 16:11:17 mww dovecot: auth-worker: Error: no talloc stackframe at ../source3/param/loadparm.c:4864, leaking memory Apr 24 16:11:17 mww dovecot: pop3-login: Login: user=<scan>, method=PLAIN, rip=192.168.16.84, lip=192.168.16.159, mpid=8773, session=<ASq6ZMX3AwDAqBBU> Apr 24 16:11:17 mww dovecot: pop3(scan): Disconnected: Logged out top=0/0, retr=0/0, del=0/0, size=0 Apr 24 16:11:18 mww dovecot: auth-worker: Error: no talloc stackframe at ../source3/param/loadparm.c:4864, leaking memory Apr 24 16:11:18 mww dovecot: pop3-login: Login: user=<scan>, method=PLAIN, rip=192.168.16.84, lip=192.168.16.159, mpid=8775, session=<Ux3JZMX3BQDAqBBU> Apr 24 16:11:18 mww dovecot: pop3(scan): Disconnected: Logged out top=0/0, retr=0/0, del=0/0, size=0 Apr 24 16:11:23 mww dovecot: pop3-login: Disconnected (auth failed, 1 attempts in 4 secs): user=<scan>, method=PLAIN, rip=192.168.16.84, lip=192.168.16.159, session=<kP3WZMX3BwDAqBBU> Apr 24 16:12:04 mww dovecot: pop3-login: Disconnected (auth failed, 1 attempts in 4 secs): user=<jason>, method=PLAIN, rip=192.168.16.59, lip=192.168.16.159, session=<WX9NZ8X3pwDAqBA7> Dovecot v2.2.9 # 2.2.9: /etc/dovecot/dovecot.conf doveconf: Warning: NOTE: You can get a new clean config file with: doveconf -n > dovecot-new.conf doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:99: ssl_disable has been renamed to ssl # OS: Linux 3.13.0-24-generic x86_64 Ubuntu 14.04 LTS disable_plaintext_auth = no mail_location = mbox:~/mail:INBOX=/var/mail/%u namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { driver = pam } plugin { sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } protocols = " imap pop3" ssl = no ssl_cert = </etc/dovecot/dovecot.pem ssl_key = </etc/dovecot/private/dovecot.pem userdb { driver = passwd } protocol imap { mail_max_userip_connections = 100 } protocol pop3 { mail_max_userip_connections = 100 } Best regards, Jason

2 3

Re: [Dovecot] Fwd: Dovecot cannot connect to PostgreSQL server
by Chris Vaas 28 Apr '14

28 Apr '14

On Mon, Apr 28, 2014 at 9:30 AM, Steffen Kaiser < skdovecot(a)smail.inf.fh-brs.de> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Mon, 28 Apr 2014, Chris Vaas wrote: > > I just looked into my SELinux audit log and found the following denial. >> >> type=AVC msg=audit(1398609990.493:280): avc: denied { name_connect } for >> pid=5964 comm="auth" dest=5432 >> scontext=unconfined_u:system_r:dovecot_auth_t:s0 >> tcontext=system_u:object_r:postgresql_port_t:s0 tclass=tcp_socket >> >> There seems to be a good chance, that this is my problem, doesn't it? But >> how can I allow the connection? >> > > I don't run SELinux, checkout a SELinux HowTo, e.g. > http://wiki.centos.org/HowTos/SELinux, audit2allow looks promising. > > - -- Steffen Kaiser > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.11 (GNU/Linux) > > iQEVAwUBU14Dj3z1H7kL/d9rAQKtdwf/d4mIe45sOFRkOc+BGfhD/PSYOKK9Akk9 > xRofzDZszgj/I9w1T5AWrND3Xn3RfXmCA3MuvEG4L3JAIznuPJWAATkV1XMw56v5 > pe4Z6SRB9aH6QZFvmDBfO5pEVrsGoXYeDCY78rZhSERXXgutCDuWHhQUK6pnnXTY > m2lumWt6w1mHpvLZZ5gxd2MjZiDZqYJYhhDbMGxb6lcVN42WJgfD5Lm1J000F6Pq > pbwCR+2lz2W9tBTCChJqTwIMebUhxesUQxcmFrh9/0/tR7b5hKkEY2o9OtDxRGt6 > A6qE/9H82peC64AtV7Cn6rbEJ76HVSCWMP9lLOhmiflpP3cwF+d7VA== > =aI5S > -----END PGP SIGNATURE----- > Bam. Works! Thank you very much, everyone! Cheers Chris

1 0

Re: [Dovecot] Fwd: Dovecot cannot connect to PostgreSQL server
by Chris Vaas 28 Apr '14

28 Apr '14

On Mon, Apr 28, 2014 at 9:11 AM, Steffen Kaiser < skdovecot(a)smail.inf.fh-brs.de> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Mon, 28 Apr 2014, Chris Vaas wrote: > > On Mon, Apr 28, 2014 at 8:43 AM, Steffen Kaiser < >> skdovecot(a)smail.inf.fh-brs.de> wrote: >> >> -----BEGIN PGP SIGNED MESSAGE----- >>> Hash: SHA1 >>> >>> On Sun, 27 Apr 2014, Chris Vaas wrote: >>> >>> [fixed ugly top posting] >>> >>> On Sat, Apr 26, 2014 at 11:39 PM, Steffen < >>> skdovecot(a)smail.inf.fh-brs.de >>> >>>> wrote: >>>>> >>>> >>>> -----BEGIN PGP SIGNED MESSAGE----- >>>> >>>>> Hash: SHA1 >>>>> >>>>> Chris Vaas wrote: >>>>> >>>>> I am currently facing the following log output: >>>>>> >>>>>> Apr 26 16:40:28 h2290750 dovecot: auth: Error: pgsql(localhost): >>>>>> Connect failed to database mail: could not connect to server: >>>>>> Permission denied Apr 26 16:40:28 h2290750 dovecot: auth: Error: >>>>>> #011Is the server running on host "localhost" (::1) and accepting >>>>>> Apr 26 16:40:28 h2290750 dovecot: auth: Error: #011TCP/IP >>>>>> connections on port 5432? >>>>>> >>>>>> I have double checked the database. It is listening correctly and I >>>>>> can connect to it via >>>>>> >>>>>> psql -U mailreader mail >>>>>> >>>>>> I provided all necessary information to dovecot via this >>>>>> configuration snippet: >>>>>> >>>>>> driver = pgsql connect = host=localhost dbname=mail user=mailreader >>>>>> password=secret default_pass_scheme = SHA512 >>>>>> >>>>>> >>>>> does Postgres allow connections on "host ::1" for user mailreader ? >>>>> Actually I wonder, because I thought the Postgres lib defaults to >>>>> "local" (socket) by default on localhost -> does Postgres allow >>>>> connections on "local" for mailreader? Permissions are configured in >>>>> pg_hba.conf, but -> Does Postgres logs something? It should if PG >>>>> denies the connection. >>>>> >>>>> >>>> I set the host to 127.0.0.1 now. And my pg_hba.conf looks like that: >>> >>>> >>>> # TYPE DATABASE USER ADDRESS METHOD >>>> # Mail stuff >>>> host mail mailreader 127.0.0.1/32 md5 >>>> host mail mailreader ::1/128 md5 >>>> local all all md5 >>>> host all all 127.0.0.1/32 ident >>>> host all all ::1/128 ident >>>> >>>> >>> What about the "Does Postgres logs something?" >>> >>> >> The log under /var/logs/pgsql is completely empty. >> > > In addition to Aleksandar's question: Does Postgres runs at all? > > >>> Do you have SELinux or something like that running? >>> What about this question? >>> >> >> I do have a SELinux up and running, yeah. >> > > Did you've checked its logs, e.g. (pretty old): > http://linux.derkeiler.com/Mailing-Lists/Fedora/2006-03/msg05342.html > - -- Steffen Kaiser > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.11 (GNU/Linux) > > iQEVAwUBU13/FXz1H7kL/d9rAQLjbQf+IQV/jSAj+fvxCaIgxgzktUuJenONp5Za > LrxYEQ79YelD5ljH1Ms1cYyegp5+8ecHsp0Fc850ZBeEYsplfZjfvAoPP4lO+cdH > GOPt3+zniEdeEVMVFfOokyTGjSPWbRrlb5r/wWYj6pU35pkw1pK3M6hPxF2Y6grm > poLMdHvaktwIr9STtqu1JTOxRffLgW5qh1AcQwJ+BoNs+h0MKs7ddqgnfeV9bKZx > rmyOuAU36QnNcv+LJQJSiJMFw1pejS+OBvI23xYsj/04dAAiTzNHGe3doz/sF1PX > P2zroewTEEb+lkvjUkOmukLuTlLnCAVgdHyWZF37c5vML9HD7Xyqrg== > =e13N > -----END PGP SIGNATURE----- > It is running, yes. I can connect from my local machine to the server without a flaw. About SELinux: I just looked into my SELinux audit log and found the following denial. type=AVC msg=audit(1398609990.493:280): avc: denied { name_connect } for pid=5964 comm="auth" dest=5432 scontext=unconfined_u:system_r:dovecot_auth_t:s0 tcontext=system_u:object_r:postgresql_port_t:s0 tclass=tcp_socket There seems to be a good chance, that this is my problem, doesn't it? But how can I allow the connection? Cheers Chris

2 1

Re: [Dovecot] Fwd: Dovecot cannot connect to PostgreSQL server
by Chris Vaas 28 Apr '14

28 Apr '14

On Mon, Apr 28, 2014 at 8:43 AM, Steffen Kaiser < skdovecot(a)smail.inf.fh-brs.de> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Sun, 27 Apr 2014, Chris Vaas wrote: > > [fixed ugly top posting] > > On Sat, Apr 26, 2014 at 11:39 PM, Steffen <skdovecot(a)smail.inf.fh-brs.de >> >wrote: >> >> -----BEGIN PGP SIGNED MESSAGE----- >>> Hash: SHA1 >>> >>> Chris Vaas wrote: >>> >>>> I am currently facing the following log output: >>>> >>>> Apr 26 16:40:28 h2290750 dovecot: auth: Error: pgsql(localhost): >>>> Connect failed to database mail: could not connect to server: >>>> Permission denied Apr 26 16:40:28 h2290750 dovecot: auth: Error: >>>> #011Is the server running on host "localhost" (::1) and accepting >>>> Apr 26 16:40:28 h2290750 dovecot: auth: Error: #011TCP/IP >>>> connections on port 5432? >>>> >>>> I have double checked the database. It is listening correctly and I >>>> can connect to it via >>>> >>>> psql -U mailreader mail >>>> >>>> I provided all necessary information to dovecot via this >>>> configuration snippet: >>>> >>>> driver = pgsql connect = host=localhost dbname=mail user=mailreader >>>> password=secret default_pass_scheme = SHA512 >>>> >>> >>> does Postgres allow connections on "host ::1" for user mailreader ? >>> Actually I wonder, because I thought the Postgres lib defaults to >>> "local" (socket) by default on localhost -> does Postgres allow >>> connections on "local" for mailreader? Permissions are configured in >>> pg_hba.conf, but -> Does Postgres logs something? It should if PG >>> denies the connection. >>> >> > I set the host to 127.0.0.1 now. And my pg_hba.conf looks like that: >> >> # TYPE DATABASE USER ADDRESS METHOD >> # Mail stuff >> host mail mailreader 127.0.0.1/32 md5 >> host mail mailreader ::1/128 md5 >> local all all md5 >> host all all 127.0.0.1/32 ident >> host all all ::1/128 ident >> > > What about the "Does Postgres logs something?" > The log under /var/logs/pgsql is completely empty. > > Do you have SELinux or something like that running? >>> >> > What about this question? > I do have a SELinux up and running, yeah. > > > I remember that I had a server that had wrong permissions on: >>> >>> ls -al /var/run/postgresql >>> >>> drwxrwsr-x 2 postgres postgres 4096 Feb 10 07:32 ./ >>> srwxrwxrwx 1 postgres postgres 0 Apr 26 23:15 .s.PGSQL.5432= >>> >>> the .s.PGSQL. socket is the local socket usually used for localhost >>> connections and automatically found by libpg. >>> >> > The folder /var/run/postgresql is not existing on my machine. >> > > - -- Steffen Kaiser - Chris

2 2

[Dovecot] Fwd: Dovecot cannot connect to PostgreSQL server
by Chris Vaas 28 Apr '14

28 Apr '14

I set the host to 127.0.0.1 now. And my pg_hba.conf looks like that: # TYPE DATABASE USER ADDRESS METHOD # Mail stuff host mail mailreader 127.0.0.1/32 md5 host mail mailreader ::1/128 md5 local all all md5 host all all 127.0.0.1/32 ident host all all ::1/128 ident The folder /var/run/postgresql is not existing on my machine. The problem is still present. :( On Sat, Apr 26, 2014 at 11:39 PM, Steffen <skdovecot(a)smail.inf.fh-brs.de>wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Chris Vaas wrote: > > I am currently facing the following log output: > > > > Apr 26 16:40:28 h2290750 dovecot: auth: Error: pgsql(localhost): > > Connect failed to database mail: could not connect to server: > > Permission denied Apr 26 16:40:28 h2290750 dovecot: auth: Error: > > #011Is the server running on host "localhost" (::1) and accepting > > Apr 26 16:40:28 h2290750 dovecot: auth: Error: #011TCP/IP > > connections on port 5432? > > > > I have double checked the database. It is listening correctly and I > > can connect to it via > > > > psql -U mailreader mail > > > > I provided all necessary information to dovecot via this > > configuration snippet: > > > > driver = pgsql connect = host=localhost dbname=mail user=mailreader > > password=secret default_pass_scheme = SHA512 > > does Postgres allow connections on "host ::1" for user mailreader ? > Actually I wonder, because I thought the Postgres lib defaults to > "local" (socket) by default on localhost -> does Postgres allow > connections on "local" for mailreader? Permissions are configured in > pg_hba.conf, but -> Does Postgres logs something? It should if PG > denies the connection. > > Do you have SELinux or something like that running? > > I remember that I had a server that had wrong permissions on: > > ls -al /var/run/postgresql > > drwxrwsr-x 2 postgres postgres 4096 Feb 10 07:32 ./ > srwxrwxrwx 1 postgres postgres 0 Apr 26 23:15 .s.PGSQL.5432= > > the .s.PGSQL. socket is the local socket usually used for localhost > connections and automatically found by libpg. > > - -- > Steffen > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.9 (Darwin) > Comment: Using GnuPG with undefined - http://www.enigmail.net/ > > iQEVAwUBU1wnoXD1/YhP6VMHAQJh8gf/fyThDqYhNiMXk6YNtwgiAT8MLyCblXOR > 1/4scQAFQUTbHgOODBfoJkoTdtsmhBu0UmxNe9Y/1Y+j2pAcVU2GrJAGLEED1Is0 > OmPPptnrdGaqjsIaybIDpmuJM7vqmOYhPMvAOGVXdgXdKa5QQZU3hgo/fH1xdIrj > j45LEfLE8Cu9QedOolXz4adFLk2XuRylMJWhQWrsT3yutr38Nv6wqhRDl7Rxwo4p > 2y1b2GiBTZkVHXzUs0a2UKxOsYsgQVgCcN6wCyio0ogCTAKwHWeQ00rUpNmn9COw > xKf5nhFPR8RYlCKukk7Djb2aklIfvko6S9+QoCKZEufjNi/moA4pcg== > =1sd0 > -----END PGP SIGNATURE----- >

3 2