- dovecot - dovecot.org

Re: [Dovecot] LMTP error
by Joseph Tam 02 May '14

02 May '14

IT geek 31 <itgeek31(a)googlemail.com> writes: > I've recently switched to LMTP as I'm now using mdbox. However since > switching, mails sent to the root account do not get delivered due to the > following error: > > May 1 18:20:17 Server1 postfix/lmtp[13019]: CAEE91F851: to=<root(a)test.com>, > relay=mail.test.com[private/dovecot-lmtp], delay=1097, > delays=1096/0.45/0.43/0.46, dsn=4.3.0, status=deferred (host > mail.test.com[private/dovecot-lmtp] > said: 451 4.3.0 <root(a)test.com> Invalid user settings. Refer to server log > for more information. (in reply to RCPT TO command)) This setting: > first_valid_uid = 1010 will need to be changed to "0", or better yet, as others have suggested, alias root to some user with UID within 1010..1020. The dovecot logs that you ought to see will be something like May 1 16:12:11 viol dovecot: lda: Error: user root: Mail access for users with UID 0 not permitted (see first_valid_uid in config file, uid from userdb lookup). Joseph Tam <jtam.home(a)gmail.com>

3 2

[Dovecot] Imap user via proxy with starttls - how to rawlogs on proxy ?
by askforstatus 02 May '14

02 May '14

Hello, Is there any way to log user imap dialog with starttls when going via dovecot acting as imap proxy ? My intention is to log each and every user command similar to rawlogs feature. As per my current imap proxy config pre-login working like a charm but post-login is not possible due as i think the nature of proxy feature. Any idea ? Regards -- View this message in context: http://dovecot.2317879.n4.nabble.com/Imap-user-via-proxy-with-starttls-how-… Sent from the Dovecot mailing list archive at Nabble.com.

2 1

[Dovecot] Not backing up cache files
by Jesus Cea 02 May '14

02 May '14

I am using mdbox for dovecot storage. I wonder if I could skip "dovecot.index.cache" files and, in general, "*.cache" files when doing mail backup. Those files are big and change frequently. What I feel from reading documentation [1][2] is that they could be dropped in the backups, to be recreated on the fly if needed. But I would like expert confirmation. [1] http://wiki2.dovecot.org/IndexFiles [2] http://wiki2.dovecot.org/Design/Indexes/Cache Thanks!. -- Jesús Cea Avión _/_/ _/_/_/ _/_/_/ jcea(a)jcea.es - http://www.jcea.es/ _/_/ _/_/ _/_/ _/_/ _/_/ Twitter: @jcea _/_/ _/_/ _/_/_/_/_/ jabber / xmpp:jcea@jabber.org _/_/ _/_/ _/_/ _/_/ _/_/ "Things are not so easy" _/_/ _/_/ _/_/ _/_/ _/_/ _/_/ "My name is Dump, Core Dump" _/_/_/ _/_/_/ _/_/ _/_/ "El amor es poner tu felicidad en la felicidad de otro" - Leibniz

5 5

[Dovecot] BUG dovecot and nginx
by Tobias Oetiker 02 May '14

02 May '14

we have setup a two level proxy configuration for our zimbra server: [ dovecot 2.2.12 (imap proxy mode) ] V [ nginx (imap proxy mode) ] V [ zimbra imap server] and it does not work ... after tying a login, the connection just hangs and ends after 30 seconds with a timeout. - if I try again rightaway in the same dovecot connection, the login goes though without trouble. - looking at this with tshark I can see that on the second attempt, there is no capabilities query, dovecot just goes ahead and connects. if we drop nginx from the setup all is well also (login works directly as expected) - investigating the traffic differences between the setups with and without nginx, we find that for some reason dovecot does not react to the capabily answer from nginx. while it seems to happily accept the same answer when it is coming from zimbra directly. - the only difference I can see on the wire is that nginx is much quicker (2.5ms) in responding than the zimbra (25ms) server and that the position of the STARTTLS and SASL=PLAIN capabilities in the capability answer differs between the two. any ideas ? cheers tobi -- Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten, Switzerland www.oetiker.ch tobi(a)oetiker.ch +41 62 775 9902 *** We are hiring IT staff: www.oetiker.ch/jobs ***

2 1

[Dovecot] Rebuilding message guid in sdbox
by Renaud Allard 02 May '14

02 May '14

Hello, I am running dovecot 2.2.12 Current mail storage is sdbox and I am trying to compress all emails, which works fine, except for a few old mailboxes. If I run the following dsync command "dsync -u flea -o "mail_plugins=zlib" mirror maildir:~/ndbox" It fails with: dsync(flea): Error: Exporting mailbox INBOX failed: Backend doesn't support GUIDs, sync with header hashes instead Doing "doveadm dump flea/dbox/mailboxes/INBOX/dbox-Mails/dovecot.index" reveals that there are very old mails (about 5 years ago) without any guid like that one: RECORD: seq=1, uid=1560, flags=0x00 - ext 1 modseq : 16043 (ab3e000000000000) - ext 3 cache : 396 (8c010000) - cache offset=396 size=20, prev_offset = 0 - guid: So, my question is: is there a way to force dovecot to assign a guid to those messages? Best Regards

2 1

[Dovecot] Dovecot Director and MasterUsers
by Daniel Parthey 02 May '14

02 May '14

Hi, the Dovecot Director determines the backend host in some way by hashing the username: http://wiki2.dovecot.org/Director For normal logins username(a)example.org, the director always gets the same hash for the same username and ensures that the login is always proxied to the same backend. But what about MasterUsers in combination with Dovecot Director? http://wiki2.dovecot.org/Authentication/MasterUsers Which configuration directives should be used to make sure that logins username@example.org*masteruser1@example.org username@example.org*masteruser2@example.org username@example.org*masteruser3@example.org go to the same mailbox backend, in order to avoid NFS caching conflicts for mailbox username(a)example.org which should always reside on the same NFS client? Is the master user cut off from behind the master_user_separator? How is the director hash exactly calculated? Can the director hashing algorithm be configured in some way? Regards Daniel

2 1

[Dovecot] BUG: Authentication client sent unknown handshake command
by Jean-Yves Moulin 02 May '14

02 May '14

Hi everybody, I'm using dovecot-2.2.11 on NetBSD. After a kernel upgrade, while using the same dovecot binaries (they were working perfectly until today), I'm experiencing this error (more log at the end of my email): BUG: Authentication client sent unknown handshake command: REQUEST?227672066?18807?2?c717631d60216b2e9ec57a2fa69674b8?session_pid=16343?... I tried to build a newer version of dovecot (2.2.12) but same issue. I know this should come from my system and not dovecot, but how can I debug this kind of problem ? I already enabled various debug (auth_verbose, auth_debug, mail_debug) but I need more information. This issue have already been discussed on dovecot mailing list without solution :-) Thank you very much. Best, jym Log: Apr 16 16:29:16 dodo dovecot: imap-login: Debug: SSL: where=0x2002, ret=1: SSL negotiation finished successfully [::1] Apr 16 16:29:17 dodo dovecot: auth: Debug: client in: AUTH 2 PLAIN service=imap secured session=cE/PvSn3qgAAAAAAAAAAAAAAAAAAAAAB lip=::1 rip=::1 lport=993 rport=65450 resp=<hidden> Apr 16 16:29:17 dodo dovecot: auth: Debug: cache(mylogin@myhost.org,::1,<cE/PvSn3qgAAAAAAAAAAAAAAAAAAAAAB>): hit: <hidden> Apr 16 16:29:17 dodo dovecot: auth: Debug: client passdb out: OK 2 user=mylogin(a)myhost.org Apr 16 16:29:17 dodo dovecot: auth: Error: BUG: Authentication client sent unknown handshake command: REQUEST?227672066?18807?2?c717631d60216b2e9ec57a2fa69674b8?session_pid=16343?... Apr 16 16:29:17 dodo dovecot: imap: Error: Authentication server didn't send valid SPID as expected: MECH PLAIN plaintext Apr 16 16:29:17 dodo dovecot: imap: Error: Disconnected from auth server, aborting (client-pid=18807 client-id=2) Apr 16 16:29:17 dodo dovecot: imap-login: Internal login failure (pid=18807 id=2) (internal failure, 1 successful auths): user=<mylogin(a)myhost.org>, method=PLAIN, rip=::1, lip=::1, mpid=16343, TLS, session=<cE/PvSn3qgAAAAAAAAAAAAAAAAAAAAAB> Apr 16 16:29:17 dodo dovecot: imap-login: Debug: SSL alert: close notify [::1]

2 1

Re: [Dovecot] nfs flush/fsync config settings problem
by Wesley Huang 02 May '14

02 May '14

Hi Alessio, After days sorting the Heartbleed mess, I managed to set up Debian Squeeze amd64 for the test and I'm seeing the same error message: Fatal: nfs flush requires mail_fsync=always # doveconf -n | egrep 'fsync|nfs' mail_fsync = always mail_nfs_index = yes mail_nfs_storage = yes Cheers, Wesley On 14-04-03 09:24 AM, Alessio Cecchi wrote: > Hi, > > I'm using Maildir on Debian 6 64bit, try to "grep" for "fsync" on all > configuration files. > > Try also to install the same dovecot+configuration on Debian 6. > > Let me know! > Ciao > > Il 03/04/2014 15:12, Wesley Huang ha scritto: >> Hi Alessio, >> >> I have 2.2.12 installed in Debian Wheezy amd64 server. mail_fsync is >> specified and detected. Are you using mbox or maildir or dbox? We're >> using mbox and seeing the error. >> >> # dovecot --version >> 2.2.12 >> >> # dovecot -n | grep -E 'sync|nfs' >> mail_fsync = always >> mail_nfs_index = yes >> mail_nfs_storage = yes >> >> >> # egrep 'nfs|fsync' 10-mail.conf | egrep -v '#' >> mail_fsync=always >> mail_nfs_storage = yes >> mail_nfs_index = yes >> >> # uname -r >> 3.2.0-4-amd64 >> >> Cheers, >> >> Wesley >> >> On 14-04-03 04:22 AM, Alessio Cecchi wrote: >>> Il 08/01/2014 09:23, Troton_admin ha scritto: >>>> Hi, >>>> >>>> I need to place a maildir storage on a NFS filesystem, so I set up >>>> the config like this: >>>> >>>> mmap_disable = yes >>>> mail_nfs_storage = yes >>>> mail_nfs_index = yes >>>> mail_fsync = always >>>> lock_method = dotlock (also tried fcntl - local lockd is running, no >>>> success, now using dotlock, to be sure while debugging) >>>> >>>> The problem is that Dovecot (2.2.9/2.2.10 - the relevant code in >>>> mail-index.c is the same) logs a fatal error and quits the session >>>> (no daemon crash/coredump). >>> >>> Hi, >>> >>> I have a similar configuration but with dovecot 2.2.12 and NFS for me >>> works fine. Have you insert the "mail_fsync = always" in the right >>> place? Is there only one "mail_fsync" setting in your config? First >>> check this: >>> >>> root@mx:/etc/dovecot# grep mail_fsync /etc/dovecot/ -R >>> conf.d/10-mail.conf:mail_fsync = always >>> >>> root@mx:/etc/dovecot# dovecot -n | grep -E 'sync|nfs' >>> mail_fsync = always >>> mail_nfs_index = yes >>> mail_nfs_storage = yes >>> maildir_very_dirty_syncs = yes >>> >>> # 2.2.12: /etc/dovecot/dovecot.conf >>> # OS: Linux 2.6.32-5-amd64 x86_64 Debian 6.0.9 >>> >>> Let me know. >>> Ciao >> > >

3 3

[Dovecot] Assert Crash with HG 49e9d9743f6e
by Thomas Leuxner 02 May '14

02 May '14

New crash most likely related to Virtual plugin again: Apr 26 07:40:40 spectre dovecot: imap(tlx(a)leuxner.net): Panic: file mail-storage.c: line 1836 (mailbox_transaction_begin): assertion failed: (box->opened) Apr 26 07:40:40 spectre dovecot: imap(tlx(a)leuxner.net): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x6bc0f) [0x7fdfce48ac0f] -> /usr/lib/dovecot/libdovecot.so.0(+0x6bc6e) [0x7fdfce48ac6e] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7fdfce4442ce] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0x82299) [0x7fdfce777299] -> /usr/lib/dovecot/modules/lib20_virtual_plugin.so(+0x9f1b) [0x7fdfccc2df1b] -> /usr/lib/dovecot/modules/lib20_virtual_plugin.so(virtual_storage_sync_init+0x564) [0x7fdfccc2eb84] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_sync_init+0x33) [0x7fdfce776e53] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_sync+0x27) [0x7fdfce776f77] -> dovecot/imap [tlx(a)leuxner.net 95.223.79.50 EXAMINE](cmd_select_full+0x173) [0x412c13] -> dovecot/imap [tlx(a)leuxner.net 95.223.79.50 EXAMINE](command_exec+0x3c) [0x41839c] -> dovecot/imap [tlx(a)leuxner.net 95.223.79.50 EXAMINE]() [0x417400] -> dovecot/imap [tlx(a)leuxner.net 95.223.79.50 EXAMINE]() [0x4174ba] -> dovecot/imap [tlx(a)leuxner.net 95.223.79.50 EXAMINE](client_handle_input+0x115) [0x417775] -> dovecot/imap [tlx(a)leuxner.net 95.223.79.50 EXAMINE](client_input+0x72) [0x417b22] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x4e) [0x7fdfce49b9fe] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0xd7) [0x7fdfce49c9f7] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x9) [0x7fdfce49ba89] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7fdfce49bb08] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7fdfce449673] -> dovecot/imap [tlx(a)leuxner.net 95.223.79.50 EXAMINE](main+0x298) [0x40c128] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xfd) [0x7fdfce0b2ead] -> dovecot/imap [tlx(a)leuxner.net 95.223.79.50 EXAMINE]() [0x40c28d] Apr 26 07:40:40 spectre dovecot: imap(tlx(a)leuxner.net): Fatal: master: service(imap): child 31334 killed with signal 6 (core not dumped) Disabling virtual prevents Dovecot from crashing.

2 2

[Dovecot] Dovecot permission denied error in logs
by Andrew Stuart 02 May '14

02 May '14

dovecot --version 2.1.7 I am getting he following errors in the logs eve though there is no 'apply' user in /etc/dovecot/users I'm not sure wat to do next to diagnose. Can anyone advise please? It says 'refer to server log for more information' but I thought this was the server log? May 1 22:40:44 ip-xx-xxx-xx-xx postfix/local[18901]: 1B17763738: to=<apply@localhost>, orig_to=<apply(a)example.org>, relay=local, delay=147501, delays=147501/0.54/0/0.06, dsn=4.3.0, status=deferred (temporary failure) May 1 22:40:44 ip-xx-xxx-xx-xx dovecot: lda(apply): Error: user apply: Initialization failed: Namespace '': mkdir(/home/vmail//apply) failed: Permission denied (euid=1001(apply) egid=1001(apply) missing +w perm: /home/vmail/, dir owned by 5000:5000 mode=0755) May 1 22:40:44 ip-xx-xxx-xx-xx dovecot: lda(apply): Error: user apply: Initialization failed: Namespace '': mkdir(/home/vmail//apply) failed: Permission denied (euid=1001(apply) egid=1001(apply) missing +w perm: /home/vmail/, dir owned by 5000:5000 mode=0755) May 1 22:40:44 ip-xx-xxx-xx-xx dovecot: lda(apply): Fatal: Invalid user settings. Refer to server log for more information. May 1 22:40:44 ip-xx-xxx-xx-xx dovecot: lda(apply): Fatal: Invalid user settings. Refer to server log for more information. May 1 22:40:44 ip-xx-xxx-xx-xx postfix/local[18926]: 9E5376357A: to=<apply@localhost>, orig_to=<apply(a)example.org>, relay=local, delay=235638, delays=235637/0.6/0/0.06, dsn=4.3.0, status=deferred (temporary failure) May 1 22:40:44 ip-xx-xxx-xx-xx postfix/local[18908]: 252106364B: to=<apply@localhost>, orig_to=<apply(a)example.org>, relay=local, delay=218930, delays=218929/0.6/0/0.06, dsn=4.3.0, status=deferred (temporary failure) May 1 22:40:44 ip-xx-xxx-xx-xx dovecot: lda(apply): Error: user apply: Initialization failed: Namespace '': mkdir(/home/vmail//apply) failed: Permission denied (euid=1001(apply) egid=1001(apply) missing +w perm: /home/vmail/, dir owned by 5000:5000 mode=0755) May 1 22:40:44 ip-xx-xxx-xx-xx dovecot: lda(apply): Fatal: Invalid user settings. Refer to server log for more information. May 1 22:40:44 ip-xx-xxx-xx-xx postfix/local[18900]: 9A94063274: to=<apply@localhost>, orig_to=<apply(a)example.org>, relay=local, delay=306900, delays=306900/0.66/0/0.03, dsn=4.3.0, status=deferred (temporary failure) May 1 22:41:23 ip-xx-xxx-xx-xx dovecot: pop3-login: Login: user=<my.name(a)example.org >, method=PLAIN, rip=101.103.174.186, lip=10.172.21.51, mpid=18952, session=<mc9XXV74CwBlZ666> May 1 22:41:24 ip-xx-xxx-xx-xx dovecot: pop3(my.name(a)example.org): Disconnected: Logged out top=0/0, retr=0/0, del=0/424, size=57179196 [/var/log] dovecot -n # 2.1.7: /etc/dovecot/dovecot.conf # OS: Linux 3.11.0-19-generic x86_64 Ubuntu 13.10 ext4 auth_mechanisms = plain login disable_plaintext_auth = no mail_location = maildir:/home/vmail/%d/%n managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded- character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave 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 { args = scheme=CRYPT username_format=%u /etc/dovecot/passdb driver = passwd-file } plugin { sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } protocols = imap pop3 sieve service auth { unix_listener /var/spool/postfix/private/dovecot-auth { group = postfix mode = 0660 user = postfix } } ssl_cert = </etc/dovecot/mail.example.org.pem ssl_cipher_list = ALL:!LOW:!SSLv2:ALL:!aNULL:!ADH:!eNULL:!EXP:RC4+RSA: +HIGH:+MEDIUM ssl_key = </etc/dovecot/private/mail.example.org.key userdb { args = username_format=%u /etc/dovecot/users driver = passwd-file } protocol lda { deliver_log_format = msgid=%m: %$ mail_plugins = sieve postmaster_address = postmaster quota_full_tempfail = yes rejection_reason = Your message to <%t> was automatically rejected: %n%r } protocol imap { imap_client_workarounds = delay-newmail mail_max_userip_connections = 10 } protocol pop3 { mail_max_userip_connections = 10 pop3_client_workarounds = outlook-no-nuls oe-ns-eoh } [/etc/dovecot]

1 0

Re: [Dovecot] LMTP error
by Reindl Harald 01 May '14

01 May '14

Am 01.05.2014 19:43, schrieb IT geek 31: > On 1 May 2014 19:41, Reindl Harald: > > that you are working with unix-accounts and the root uid 0 > is prohibited for (good) saftey reasons > > Okay, that sounds good. How do I deliver mail to the root account then, and stop this error/warning/message? As > mails are now backing up in the queue and cannot be delivered... keep your responses on the list! * set a alias on the postfix side to another mail-address * that way dovecot never see the root-address as destination * use "postsuper -d queue_id" to kill the messages from the queue ______________________________ cat /etc/aliases | grep root # Person who should get root's mail root: h.reindl(a)thelounge.net ______________________________ don't forget calling "newaliases" after changes in that file if you have implemented aliases on postfix in a different way follow the documentation

2 1

[Dovecot] LMTP error
by IT geek 31 01 May '14

01 May '14

Hi, I've recently switched to LMTP as I'm now using mdbox. However since switching, mails sent to the root account do not get delivered due to the following error: May 1 18:20:17 Server1 postfix/lmtp[13019]: CAEE91F851: to=<root(a)test.com>, relay=mail.test.com[private/dovecot-lmtp], delay=1097, delays=1096/0.45/0.43/0.46, dsn=4.3.0, status=deferred (host mail.test.com[private/dovecot-lmtp] said: 451 4.3.0 <root(a)test.com> Invalid user settings. Refer to server log for more information. (in reply to RCPT TO command)) This obviously fills up my mail queue. All other mails to all other mailboxes deliver fine. I'm obviously missing something in my config... any ideas? I'm using Dovecot 2.2.12 on NetBSD 5.2.2. Many thanks, -Mark dovecot -n # 2.2.12: /usr/pkg/etc/dovecot/dovecot.conf # OS: NetBSD 5.2.2 cobalt auth_username_format = %Ln doveadm_password = secret doveadm_port = 12345 first_valid_uid = 1010 last_valid_uid = 1020 listen = 192.168.1.1 login_greeting = test.com mail_location = mdbox:~/mdbox mail_plugins = " notify replication" 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 = passwd } passdb { driver = passwd } plugin { mail_replica = tcp:Server2.test.com } protocols = imap lmtp service aggregator { fifo_listener replication-notify-fifo { mode = 0666 } unix_listener replication-notify { mode = 0600 } } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } user = root } service imap-login { inet_listener imap { port = 0 } } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { mode = 0777 } } ssl_cert = </etc/openssl/certs/mail.test.com.crt ssl_key = </etc/openssl/private/mail.test.com.key userdb { driver = passwd } userdb { driver = passwd } protocol lda { postmaster_address = postmaster(a)test.com }

3 7

[Dovecot] fts-lucene configuration
by Gregory Finch 01 May '14

01 May '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all, Is there a configuration option to set where fts-lucene stores its indexes? I know it defaults to lucene-indexes in the mail root directory. I'm looking to store it in the home directory. Thank you, Greg -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJTYmPZAAoJECD7Htp+IT9epBIQAKnR+cBtMZ8kkpvTefI/oVG6 ANu/gB/VGamrommOl0w+9/E0YwowdfqB3IqQuavR47KtPHE6X8gxyRf4p26p3dfC X13KCrdBvDQ0AArqi1RH4Blig2zFcLvC85QyBOvGKnYKg90wBKRODYdw9it8cU0P 1eJMkURCR5llIKUEnFQH1OBUr1rJ4c+tkke0fuxeikcoaS3DtW7LdPCQaJyYpUdS NmFehIG+n3jDQqx1jDJNBBQMlfSEz+svXFuHzAR/YCeQS8ETBQdQ7cC5ES5gBijy Z0f1bTRWhLOC9rcg3VzcbGm1ky+rAJeEVL1HGXluPOJjqLhjWvaDE+ola2cDHtNk IiVXtL4WdIAvSJ51kR8X3ubSWtHd+2mo93ryQqCE+AdhWh0lMNzxMB/r8LmVHMKY eMjFmu1QvC+W1Z20xUT5SZKFIIOnXzHZbzugkz2zKZEQbJw9AtdTrIwJ+CyxY+YN yREwPFJ2dGzglWtzk/lxAgRZUizAJEvmcLQ8n5ZPi4aX6SfZyYcD0t7nkAOVD3ff VsJdvYJeiPcoWLrQnemI4wAaClINw+7vLg4D+uiGLswyTtR4ccTg0wOUG6Bp8Jkv dMFRWLwJsK3dLYubLud9T2nlyMBG63hEyoDjgE8WxXXuIAYaYTTMUuGAf89fdwLN bgpfg40wgCfheu18qD9d =EDIQ -----END PGP SIGNATURE-----

1 0

[Dovecot] Problems with login_log_format (possible bug?)
by Trever L. Adams 01 May '14

01 May '14

login_log_format = %$: %s login_log_format_elements = user=<%u> method=%m rip=%r lip=%l mpid=%e %c session=<%{session}> These are the defaults, at least on a Fedora system. According to http://wiki2.dovecot.org/Variables, this should record for user@REALM when seeing the following Apr 30 18:08:40 TeaSet dovecot: auth: Debug: auth(user,...,<JhKid0v4bAAKAQG6>): username changed user -> user@REALM. If I wanted just user, user=<%u> should be changed to user=<%orig_user>. However, I only get user not user@REALME in imap-login log lines. I wouldn't mind this, but auth_username_format cannot be used in passed{} and I haven't been able to get pam_krb5 to uppercase the realm for it alone. (Everything else depends on it being lowercase.) I can make this work by just passing the user name part of username in the client, but then imap-login still doesn't have the required information for the same reason. Anyone have any suggestions? Thank you, Trever

1 0

[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

Re: [Dovecot] Dovecot cannot connect to PostgreSQL server
by Joseph Tam 28 Apr '14

28 Apr '14

Chris Vaas writes: >> 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 ... > 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 Shouldn't the last column here match your "default_pass_scheme" above? Maybe change "default_pass_scheme" to "md5-crypt" or "md5"? Joseph Tam <jtam.home(a)gmail.com>

2 1