July 2014 - dovecot - dovecot.org

Dovecot Replication: First Run
by Asai 19 Jul '14

19 Jul '14

Greetings, I'm working on building a redundant Dovecot server which will be replicated with my original. I would like to know if there's any potential problems I could run into in running this for the first time. For example, during an initial sync is it possible for the new server to sync improperly with the original and delete all of the emails on the original? Are there any gotchas that I should be aware of when doing a first run? -- --Asai

1 1

Difference btw. Dovecot Director and Dovecot Proxy
by Nathan Schultheiss 19 Jul '14

19 Jul '14

Hello, For a few days I try to understand what program (Dovecot Director or Dovecot Proxy) I should use for my email architecture. We are a hospital, and for security reasons, we must host ourselves our emails, and we must leave Google Apps... I wish to make a Dovecot backend for each department of the hospital. Each backend Dovecot has a local storage. Server 01: cardiology Server 02: emergency ... Server 05: administration Dovecot looks in the database which server to use to store email (lmtp) and transfer the mail for storage. I do not understand if I have to work with Dovecot Director or Proxy if I would that LMTP or IMAP request are forwarded to the right backend. Each have self storage and have not access to the other backend storage (no nfs, no network storage, ...). Users indicate imap.hospital.local, this point to Dovecot Director or Proxy and Dovecot check the login/password and forward the user to the right backend. In my database I put user@hospital = storage host 172.16.2.10 = folder /home/vmail/user/ (Maildir) I've read that the Director can refer the user to the same backend when there is a activ session (POP, IMAP, LMTP) But can we tell him to always refer the user to the same backend (IMAP and LMTP) ? I've found this picture schema who user have Dovecot Proxy => Dovecot Director => Dovecot Backend And I'm confused why they have proxy + director ?!? Can anyone tell me if I need to focus on Dovecot Director or Dovecot Proxy to create the architecture of this hospital ? My question is probably stupid for Dovecot sysadmin, but I'm lost in the WIKI :) Thanks in advance, Nathan

2 2

Postfix user@domain splitting
by Ricardo Branco 18 Jul '14

18 Jul '14

I have been trying looking though all the wiki documents to setup LMTP. It now seems to all be connected except that it keeps saying that the user is not recognised when postfix sends to LMTP, it sends the full recipent email address but seems that on the dovecot side it is unable to work with this. I have checked the userdb and made sure its using %n but alas it still does not work. Currently ive had to revert to using LDA as it works fine with that but i still dont know how as the postfix config variable $RECIPIENT is the full email address and does not seem to matter to LDA.

4 11

ulimit warning when restarting
by Will Yardley 18 Jul '14

18 Jul '14

When restarting Dovecot 2.2.10 (via atrpms) on RHEL 6, I get the error: Warning: fd limit (ulimit -n) is lower than required under max. load (1024 < 4096), because of default_client_limit # doveconf default_internal_user default_internal_user = dovecot Should dovecot print this warning based on $default_internal_user, or based on root? As root: # ulimit -n 1024 As user dovecot: $ ulimit -n 49152 $ whoami dovecot # grep dovecot /etc/security/limits.conf dovecot hard locks 49152 dovecot hard nofile 49152 dovecot hard maxlogins 8192 dovecot soft locks 49152 dovecot soft nofile 49152 dovecot soft maxlogins 8192

3 2

Panic: file mail-storage.c
by giovanni＠neweden.uk.to 18 Jul '14

18 Jul '14

Greetings, In my installation I have debian 7.6 dovecot 2.2.13 dovecot-antispamplugin VERSION=2.0 for this enviroment some users cannot get imap connections. Here below an excerpt the log file. Jul 09 23:54:07 imap(xx(a)xxx.co.uk): Panic: file mail-storage.c: line 2158(mailbox_copy): assertion failed: (!ctx->unfinished) ul 09 23:54:07 imap(xx(a)xxx.co.uk): Error: Raw backtrace: /usr/local/lib/dovecot/libdovecot.so.0(+0x6bb4f) [0x7fd796ccdb4f] -> /usr/local/lib/dovecot/libdovecot.so.0(+0x6bbae) [0x7fd796ccdbae] -> /usr/local/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7fd796c871ee] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(+0x82519) [0x7fd796fb9519] -> dovecot/imap() [0x40dba4] -> dovecot/imap(command_exec+0x3c) [0x41822c] -> dovecot/imap() [0x417290] -> dovecot/imap() [0x41734a] -> dovecot/imap(client_handle_input+0x115) [0x417605] -> dovecot/imap(client_input+0x72) [0x4179b2] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x4e) [0x7fd796cde81e] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0xd7) [0x7fd796cdf7f7] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x9) [0x7fd796cde8a9] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7fd796cde928] -> /usr/local/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7fd796c8c4d3] -> dovecot/imap(main+0x277) [0x40c067] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xfd) [0x7fd7968f5ead] -> dovecot/imap() [0x40c1c5] for others users imap connection is ok with antispam plugin working fine (antispam_backend = spool2dir) To enable the imap connections for the unlucky users (with the previous error) I had to remove the anti spam plugin. Does anybody is experiencing the same errors? cheers Giovanni

1 0

Dovecot/K9/Thunderbird IMAP interaction issues: replicated messages, constant reloading (TB) & missing new messages (K-9)
by David Gessel 18 Jul '14

18 Jul '14

Version Info: FreeBSD 9.2-RELEASE #0 r266046 AMD64, Dovecot 2.2.13, dovecot-pigeonhole-0.4.3, amavisd-new-2.8.0_2,1, clamav-0.98.4, postfix29-2.9.9_1,1, postfixadmin-2.3.6, spamassassin-3.4.0_12 (zpool data and output of dovecot -n at bottom of post) I suspect these are related problems and further that they are related to some trivial newb error I've made in my configuration, but searching descriptions of the symptoms has not yet guided me to a solution. I recently migrated from Courier to Dovecot on new hardware and imap synced a 16GB mailstore (du -hs) divided up into annual directories with about 15,000 messages each. I mention the size because it seems an errant Remove Duplicate Messages (Alternate) 0.3.9 acting on what seem to be false duplicates in Thunderbird reduced the inbox size from 7500-ish messages to 1300 (DOH!) and may have solved my K-9 problem described below. My old Courier server still has the vast majority of these messages and I will resync someday and then try to file them away more expediently than my previously somewhat lazy management style to keep the inbox small. * In thunderbird, I get constant downloading of messages. Every time I switch to the inbox from another folder, the messages start redownloading. This sometimes, but not always, seems to create duplicate messages, but I'm now fairly sure they are only created in the client and not on the server. Searching through various forums, it appears this has been a problem for Thunderbird for some time, but it wasn't for me on Courier. As posts about similar errors seem to have petered out over the last year without any clear guidance on how to fix it that I could find, I expect there's a simple fix I just haven't found yet, either in TB configuration or in Dovecot. Any hints? I tried Thunderfix to remove the .msf files and will be redownloading my mail over the thin pipe out to Iraq for the next 6 months (DOH!). One artifact is that when I restart thunderbird, my inbox is reported as having about 130 messages in it, then thunderbird starts redownloading headers and eventually gets back up to the 1297 currently listed both in the TB pane and by ls | wc -l in /cur. Is it possible there is a time out that needs to be extended? In TB, I've set (among other less apparently relevant options) mailnews.tcptimeout;1000 mail.db.idle_limit;30000000 * Also, with Thunderbird, I get duplication of messages in the client. I suspect this is related to the previous redownload error, but there is some indication in some posts that it is potentially related to a dirty flag. I've had this problem before with Thunderbird and Courier, but it went away after a TB update. It seems to have reappeared with Dovecot. The TB client hasn't been updated during the transition, so some interaction issue seems more likely than a pure TB bug. Likely TB's fault as this is a well known, but poorly diagnosed TB issue (deleting duplicates regularly seems to be the solution, but my inbox would double in size every few hours on the LAN. Now that I'm remote over a 2mbps link, it has slowed way down: bonus!). * "Expunged message reappeared, giving a new UID" errors appear a lot. This might well be related to the last error. This seems to happen with TB client connections, but I'm not sure what action triggers it. I am not replicating. I tried renaming 10-director.conf to 10-director.conf.disabled and got no complaints from Dovecot (as I'm not using replication, it shouldn't) but that indicates that this Expunged message reappeared error is probably of a different source than, for example, Simon Fraser's debug effort. * K9 was only showing a subset of my messages and generally not the new ones. They'd appear in the alert properly, but weren't visible in the client and sometimes they'd be visible and then disappear later. I imagined there could a correlation between TB checking mail and perhaps moving messages from /new to /cur and K9 losing track, but the potentially tragic "duplicate" removal may have reduced my inbox to a size that k9 can handle as K9 inbox display seems normal now as far as I can tell. When I resync (assuming I can), I sort of dread this problem reappearing. K9 worked as expected against Courier with the same inbox. These apparently difficult to diagnose problems are occasionally suggested as related to namespace configuration issues and thunderbird is reported to have issues with some separator options. I vaguely suspect this, but I'm pretty sure my namespace config is default and should be well tested. I haven't, for example, explicitly stated the default "/" but left it commented out. I increased the connection limit count per user*IP to 20 as TB seems to be parallel downloading a lot of folders. This has neither improved nor degraded performance in any way I can see and is probably irrelevant. Any hints greatly appreciated. Filesystem/Zpool data: NAME PROPERTY VALUE SOURCE zroot size 400G - zroot capacity 28% - zroot altroot - default zroot health ONLINE - zroot guid 1061309925223582150 default zroot version - default zroot bootfs zroot local zroot delegation on default zroot autoreplace off default zroot cachefile - default zroot failmode wait default zroot listsnapshots off default zroot autoexpand off default zroot dedupditto 0 default zroot dedupratio 1.10x - zroot free 286G - zroot allocated 114G - zroot readonly off - zroot comment - default zroot expandsize 0 - zroot freeing 0 default zroot feature@async_destroy enabled local zroot feature@empty_bpobj active local zroot feature@lz4_compress active local server # dovecot -n # 2.2.13: /usr/local/etc/dovecot/dovecot.conf # OS: FreeBSD 9.2-RELEASE amd64 auth_default_realm = mydomain.com auth_mechanisms = plain login auth_realms = mydomain.com mydomain2.org disable_plaintext_auth = no first_valid_gid = 5000 first_valid_uid = 5000 hostname = mydomain.com imap_client_workarounds = tb-extra-mailbox-sep tb-lsub-flags imap_idle_notify_interval = 29 mins last_valid_gid = 5000 last_valid_uid = 5000 lda_mailbox_autocreate = yes listen = * mail_gid = 5000 mail_location = maildir:~/:CONTROL=/var/no-quota/%u mail_plugins = quota mail_log notify mail_temp_dir = /var/tmp mail_uid = 5000 maildir_broken_filename_sizes = yes 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 duplicate spamtest spamtestplus editheader mbox_lazy_writes = no 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 = /usr/local/etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { expire = Trash mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename mail_log_fields = uid box msgid size quota = maildir:User quota quota_exceeded_message = Storage quota for this account has been exceeded, please try again later. quota_rule = *:storage=50G quota_rule2 = Trash:storage=+30%% quota_rule3 = Sent:storage=+30%% quota_warning = storage=90%% quota-warning 90 %u quota_warning2 = storage=75%% quota-warning 75 %u sieve = ~/.dovecot.sieve sieve_before = /usr/local/etc/dovecot/sieve/ sieve_dir = ~/sieve sieve_extensions = +spamtest +spamtestplus +relational +comparator-i;ascii-numeric +editheader } postmaster_address = gessel(a)mydomain.com protocols = imap lmtp sieve sieve sendmail_path = /usr/local/sbin/sendmail service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } unix_listener auth-userdb { group = vmail mode = 0600 user = vmail } } service managesieve-login { inet_listener sieve { port = 4190 } service_count = 1 vsz_limit = 128 M } service quota-warning { executable = script /usr/local/bin/quota-warning.sh unix_listener quota-warning { user = vmail } user = vmail } ssl = required ssl_cert = </usr/local/etc/ca/server-cert.pem ssl_cipher_list = ECDHE-RSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-SHA384:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-SHA256:ECDHE-RSA-RC4-SHA:ECDHE-RSA-AES256-SHA:!SSLv2 ssl_key = </usr/local/etc/ca/server-unencrypted-key.pem ssl_prefer_server_ciphers = yes userdb { driver = prefetch } userdb { args = /usr/local/etc/dovecot/dovecot-sql.conf.ext driver = sql } protocol lda { mail_plugins = quota mail_log notify sieve } protocol imap { mail_max_userip_connections = 20 mail_plugins = quota mail_log notify imap_quota imap_zlib } protocol lmtp { mail_plugins = quota mail_log notify sieve }

3 5

Sieve: adding Date: header when missing
by Daniele Nicolodi 17 Jul '14

17 Jul '14

Hello, there is a way with a sieve rule to add a Date: header when it is missing? Adding one with the time of reception of the message or using the date from the the first Received: header would be good options. Unfortunately I'm receiving some useful automated messages that lack a Date header and this screws up the sorting in my imap clients. I have a script to fix those acting on the Maildir storage, but I would prefer to have the thing solved more radically. Thanks. Cheers, Daniele

6 12

dspam dovecot-lda
by Eric Broch 17 Jul '14

17 Jul '14

Hello list, Is there a way to call a spam filter in dovecot-lda like maildrop uses the xfilter command within the .mailfilter file to do the same? Eric

2 1

possible bug around ACL
by Maciej 'Agaran' Pijanka 17 Jul '14

17 Jul '14

Hello I want to set readonly over IMAP for users mailboxes at Archive namespace, (and have single user who can move mails there on automated way) This don't work but found that if I add file to /srv/mail.archives/<user>/dovecot-acl containing only owner lr then login to imap (with telnet) and do 1 GETACL Archive I get following result from gdb attached to worker process serving particular connection. Program received signal SIGSEGV, Segmentation fault. acl_mailbox_right_lookup (box=0x7fd75e4e1dc0, right_idx=right_idx@entry=10) at acl-mailbox.c:40 40 if (abox->skip_acl_checks) (gdb) p abox $1 = (struct acl_mailbox *) 0x0 (gdb) # uname -a Linux omelette 3.2.0-4-amd64 #1 SMP Debian 3.2.57-3 x86_64 GNU/Linux ii dovecot-core 1:2.2.13-2 amd64 local build from sources in testing just disabled lucene ps. I am idling on #dovecot too, if any info is needed with faster round trip time than emails. best regards -- agaran at pld dash linux dot org I do not fear computers. I fear the lack of them. [Isaac Asimov]

1 0

If local Dovecot stops working, check lo
by Steve Litt 17 Jul '14

17 Jul '14

Hi all, You probably know this already, but just in case... Let's say you have your email client getting mail from a Dovecot server on the same computer (which is a really good way of doing things, by the way). Then one day your email client starts saying "connection refused" after a suitably long timeout. So then, to find out where things are getting stuck, you do the following command: openssl s_client -connect 127.0.0.1:993 -quiet And you don't even get an OK back. This means it's not your username or password, because you never even got that far. Before spending a lot of time doing diagnostic tests and narrowing it to the root cause, try this as root: ifdown lo ifup lo A malfunctioning lo will cause Dovecot not to connect to clients. My experience with Debian Wheezy is that lo "goes down" a lot, so this is one of the first things I do when odd stuff happens. HTH, SteveT Steve Litt * http://www.troubleshooters.com/ Troubleshooting Training * Human Performance

6 8