January 2012 - dovecot

[Dovecot] dbox vs. mdbox
by Douglas Mortensen 20 Apr '12

20 Apr '12

What are the pros and cons of both? Especially in regards to performance, stability, management & maintenance? I really appreciate feedback. We're on a time-crunch to migrate from a debian 5 box w/ dovecot 1.1 to a debian 6 box w/ dovecot 2.0.9 (built from source). Thanks, - Doug Mortensen Network Consultant Impala Networks Inc CCNA, MCSA, Security+, A+ Linux+, Network+, Server+ . www.impalanetworks.com P: (505) 327-7300 F: (505) 327-7545

6 12

[Dovecot] Folder Aliases - Revisited Yet Again
by Daniel L. Miller 11 Apr '12

11 Apr '12

I just did a search through my archives - seems this topic has been requested a few times since my posting two years ago. I asked about a specific implementation - which Mr. Sirainen never commented on. He was probably focused on something more important at the time - like a paying job. So I'll ask again... Calling Timo! If we can't get clients to agree on a "standard" set of folders (probably reasonably safe assumption) and if protocol implementations of variations of "*LIST*" are too far in the future...what about having alternative folder names presented based on login name - maybe by an extension? So where my usual login might be "user(a)domain.com", and that would continue to be supported as the default login, I could now have "user(a)domain.com+thunderbird", "user(a)domain.com+mobile", etc.? And each of those extensions would then have a system-wide map defining folder name relationships, like "Sent=Sent Items". Does this seem doable? -- Daniel

2 4

[Dovecot] IMAP to Maildir Migration preserving UIDs?
by Gedalya 30 Mar '12

30 Mar '12

Hello all, I'm facing the need to migrate from a proprietary IMAP server to Dovecot. The migration must be as smooth and transparent as possible. The mailbox format I would want to use is Maildir++. The storage format used by the current server is unknown, and I don't look forward to trying to reverse-engineer it. This leaves me with the option of reading the mailboxes using IMAP. There are tools like offlineimap or mbsync, and they do store the UID and UIDVALIDITY info. The last piece of the puzzle is a process to properly create the dovecot-uidlist and dovecot-uidvalidity files. So far I wasn't able to find anything on this. Are there any tips? Are there any tools available to do this job, or part of it? In either case I need this done, and I'll have to create whatever I can't find available. If there isn't anything out there that I'm yet to become aware of, then I'm looking at creating something like an offlineimap post-processing routine? Any help would be much appreciated. Gedalya

7 33

[Dovecot] zlib_save per namespace/mailbox?
by Lutz Preßler 29 Mar '12

29 Mar '12

Hi, the zlib_save question reminds me of a wish: I think it's not possible to set zlib_save parameter per namespace (or even mailbox). Per namespace would be something for the wish list to get rid of the cron job method to compress archival mailboxes. And maybe an option to add a "Z" flag to compressed maildir message files as recommended in the wiki regarding compress crob job. Lutz

3 2

[Dovecot] Antispam plugin not compatible with Dovecot 2.1
by interfaSys sàrl 20 Mar '12

20 Mar '12

Here is what I get when I try to compile the antispam plugin agaisnt Dovecot 2.1 ************** mailbox.c: In function 'antispam_save_begin': mailbox.c:138:12: error: 'struct mail_save_context' has no member named 'copying' mailbox.c: In function 'antispam_save_finish': mailbox.c:174:12: error: 'struct mail_save_context' has no member named 'copying' Failed to compile mailbox.c (plugin)! gmake[3]: *** [mailbox.plugin.o] Error 1 ************** The other objects compile fine. Cheers, Olivier

4 5

[Dovecot] per-user limit?
by Peter Hessler 29 Feb '12

29 Feb '12

I am seeing a problem where users are limited to 6 imap logins total. One of my users has a bunch of phones and computers, and wants them all on at the same time. I'm looking through my configuration, and I cannot see a limit on how many times a single user can connect. He is connecting from different IPs. Any ideas? My logs show the following error when they attempt to auth for a 7th time: dovecot: imap-login: Disconnected (no auth attempts): rip=111.yy.zz.xx, lip=81.209.183.113, TLS $ dovecot -n # 2.0.16: /etc/dovecot/dovecot.conf # OS: OpenBSD 5.1 amd64 ffs auth_mechanisms = plain login base_dir = /var/dovecot/ listen = *, [::] mail_location = maildir:/usr/home/%u/Maildir 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 mbox_write_locks = fcntl passdb { driver = bsdauth } service auth { unix_listener /var/run/dovecot/auth-master { mode = 0600 } unix_listener /var/spool/postfix/private/auth { group = wheel mode = 0660 user = _postfix } user = root } service imap-login { process_limit = 128 process_min_avail = 6 service_count = 1 user = _dovecot } service pop3-login { process_limit = 64 process_min_avail = 6 service_count = 1 user = _dovecot } ssl_cert = </etc/ssl/dovecotcert.pem ssl_key = </etc/ssl/private/dovecot.pem userdb { driver = passwd } protocol pop3 { pop3_uidl_format = %08Xu%08Xv } protocol lda { mail_plugins = sieve postmaster_address = postmaster(a)theapt.org } -- We are all in the gutter, but some of us are looking at the stars. -- Oscar Wilde

4 4

[Dovecot] MySQL server has gone away
by Mark Moseley 15 Feb '12

15 Feb '12

I'm running 2.0.17 and I'm still seeing a decent amount of "MySQL server has gone away" errors, despite having multiple hosts defined in my auth userdb 'connect'. This is Debian Lenny 32-bit and I'm seeing the same thing with 2.0.16 on Debian Squeeze 64-bit. E.g.: Jan 12 20:30:33 auth-worker: Error: mysql: Query failed, retrying: MySQL server has gone away Our mail mysql servers are busy enough that wait_timeout is set to a whopping 30 seconds. On my regular boxes, I see a good deal of these in the logs. I've been doing a lot of mucking with doveadm/dsync (working on maildir->mdbox migration finally, yay!) on test boxes (same dovecot package & version) and when I get this error, despite the log saying it's retrying, it doesn't seem to be. Instead I get: dsync(root): Error: user ...: Auth USER lookup failed dsync(root): Fatal: User lookup failed: Internal error occurred. Refer to server log for more information. Watching tcpdump at the same time, it looks like it's going through some of the mysql servers, but all of them have by now disconnected and are in CLOSE_WAIT. Here's an (edited) example after doing a dsync that completes without errors, with tcpdump running in the background: # sleep 30; netstat -ant | grep 3306; dsync -C^ -u mailbox(a)test.com backup mdbox:~/mdbox tcp 1 0 10.1.15.129:57436 10.1.52.48:3306 CLOSE_WAIT tcp 1 0 10.1.15.129:49917 10.1.52.49:3306 CLOSE_WAIT tcp 1 0 10.1.15.129:35904 10.1.52.47:3306 CLOSE_WAIT 20:49:59.725005 IP 10.1.15.129.35904 > 10.1.52.47.3306: F 1126:1126(0) ack 807 win 1004 <nop,nop,timestamp 312603858 766667259> 20:49:59.725459 IP 10.1.52.47.3306 > 10.1.15.129.35904: . ack 1127 win 123 <nop,nop,timestamp 766667998 312603858> 20:49:59.725568 IP 10.1.15.129.57436 > 10.1.52.48.3306: F 1126:1126(0) ack 807 win 1004 <nop,nop,timestamp 312603858 1842560856> 20:49:59.725779 IP 10.1.52.48.3306 > 10.1.15.129.57436: . ack 1127 win 123 <nop,nop,timestamp 1842561225 312603858> dsync(root): Error: user mailbox(a)test.com: Auth USER lookup failed dsync(root): Fatal: User lookup failed: Internal error occurred. Refer to server log for more information. 10.1.15.129 in this case is the dovecot server, and the 10.1.52.0/24 boxes are mysql servers. That's the same pattern I've seen almost every time. Just a FIN packet to two of the servers (ack'd by the mysql server) and then it fails. Is the retry mechanism supposed to transparently start a new connection, or is this how it works? In connecting remotely to these same servers (which aren't getting production traffic, so I'm the only person connecting to them), I get seemingly random disconnects via IMAP, always coinciding with a "MySQL server has gone away" error in the logs. This is non-production, so I'm happy to turn on whatever debugging would be useful. Here's doveconf -n from the box the tcpdump was on. This box is just configured for lmtp (but have seen the same thing on one configured for IMAP/POP as well), so it's pretty small, config-wise: # 2.0.17: /etc/dovecot/dovecot/dovecot.conf # OS: Linux 3.0.9-nx i686 Debian 5.0.9 auth_cache_negative_ttl = 0 auth_cache_ttl = 0 auth_debug = yes auth_failure_delay = 0 base_dir = /var/run/dovecot/ debug_log_path = /var/log/dovecot/debug.log default_client_limit = 3005 default_internal_user = doveauth default_process_limit = 1500 deliver_log_format = M=%m, F=%f, S="%s" => %$ disable_plaintext_auth = no first_valid_uid = 199 last_valid_uid = 201 lda_mailbox_autocreate = yes listen = * log_path = /var/log/dovecot/mail.log mail_debug = yes mail_fsync = always mail_location = maildir:~/Maildir:INDEX=/var/cache/dovecot/%2Mu/%2.2Mu/%u mail_nfs_index = yes mail_nfs_storage = yes mail_plugins = zlib quota mail_privileged_group = mail mail_uid = 200 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 mdbox_rotate_interval = 1 days mmap_disable = yes namespace { hidden = no inbox = yes list = yes location = prefix = INBOX. separator = . subscriptions = yes type = private } passdb { args = /opt/dovecot/etc/lmtp/sql.conf driver = sql } plugin { info_log_path = /var/log/dovecot/dovecot-deliver.log log_path = /var/log/dovecot/dovecot-deliver.log quota = maildir:User quota quota_rule = *:bytes=25M quota_rule2 = INBOX.Trash:bytes=+10%% quota_rule3 = *:messages=3000 sieve = ~/sieve/dovecot.sieve sieve_before = /etc/dovecot/scripts/spam.sieve sieve_dir = ~/sieve/ zlib_save = gz zlib_save_level = 3 } protocols = lmtp sieve service auth-worker { unix_listener auth-worker { mode = 0666 } user = doveauth } service auth { client_limit = 8000 unix_listener login/auth { mode = 0666 } user = doveauth } service lmtp { executable = lmtp -L process_min_avail = 10 unix_listener lmtp { mode = 0666 } } ssl = no userdb { driver = prefetch } userdb { args = /opt/dovecot/etc/lmtp/sql.conf driver = sql } verbose_proctitle = yes protocol lmtp { mail_plugins = zlib quota sieve } Thanks!

4 29

[Dovecot] Some Doveadm Tools lack proper exit codes
by Thomas Leuxner 13 Feb '12

13 Feb '12

Happy New Year Everyone, and *yes* it's that time of the year to archive old stuff again. Please implement proper error codes to support this (scripting) endeavor. => Good $ doveadm user foo userdb lookup: user foo doesn't exist $ echo $? 2 => Bad $ doveadm acl get -u tlx(a)leuxner.net FOO doveadm(tlx(a)leuxner.net): Error: Can't open mailbox FOO: Mailbox doesn't exist: FOO ID Global Rights $ echo $? 0 $ doveconf -n | head # 2.1.rc1 (056934abd2ef): /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-5-amd64 x86_64 Debian 6.0.3 Thanks Thomas

2 3

[Dovecot] Some Dovecot LDA version sends MDN rather than DSN for overquota.
by Mark Sapiro 12 Feb '12

12 Feb '12

It appears that there is some version of the Dovecot LDA that is sending an RFC 3798 MDN rather than an RFC 3464 DSN to report non-delivery to a user who is over quota. See <https://bugs.launchpad.net/mailman/+bug/693134> for a discussion of this and <https://bugs.launchpad.net/mailman/+bug/693134/+attachment/1773018/+files/A…> for the actual MDN message. The issue is that apparently a user was over quota and Dovecot returned an MDN with a disposition of deleted. This is intended to mean the the mail was delivered to the user but the user deleted it without reading it. If the message was actually not delivered, this should be reported to the MTA so it can return an appropriate SMTP status, or the LDA should send an RFC 3464 DSN with an action of failed. Note that I do not actually use the Dovecot LDA nor do I have any access to the system where the notice in the bug report was received, so I may have incomplete information and this may not be relevant to current versions of Dovecot, but I think it is wrong for Dovecot to report over quota non-delivery via an MDN. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 3

[Dovecot] Quota Calculation seems to be wrong when using dsync
by Thomas Leuxner 12 Feb '12

12 Feb '12

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Recently I encountered odd quota increases when using 'dsync' with the latest and greatest: 2.0.8 (89936539e3b8). Say you got something in place like this: plugin { quota = dict:user::file:%h/mdbox/dovecot-quota quota_rule = *:storage=1GB quota_rule2 = Trash:storage=+10%% } Kick off a manual backup: $ dsync -u user(a)domain.tld backup mdbox:/<path to backup>/mdbox This results in doubling the quota for the backed up user. It doesn't seem to matter whether 'mirror' or 'backup' mode is used, both increase the "source" quota. Doesn't sound right to me. You can only get to the "real" usage by running a recalc manually: $ doveadm quota recalc -u user(a)domain.tld Anyone else seen this? Regards Thomas P.S. Merry Christmas -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.16 (Darwin) iEYEARECAAYFAk0VtH8ACgkQ+meF/S97aXjUkwCfdZFpUPCOY9UiukT+G68jCHHr mmMAnRHz56BXMzpC84CIYvUn4KHpl8OA =M0AZ -----END PGP SIGNATURE-----

2 9