- dovecot - dovecot.org

[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 02 May '14

02 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 02 May '14

02 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