June 2018 - dovecot - dovecot.org

Re: 2.3.1 Replication is throwing scary errors
by Reuben Farrelly 08 Jun '18

08 Jun '18

Hi Andy, Funny you say that - I've been testing this very problem for some time today to narrow down the commits where I think the problem started occurring. So far I have been able to roll forward to commit from git: 74ef8506dcb946acc42722683e49fdcb964eed19 >> "doveadm: Unref header search context after use" . So far I have been running on that code for a few hours and I'm not yet seeing the problem, which indicates the issue is probably subsequent to this. I'm of the view that the problem started occurring somewhere between that commit above on 6 March and the final 2.3.1 release on 27 March. There are a lot of changes between those two dates, and testing to narrow down to one specific commit is extremely time consuming. It would be really helpful if even one of the Dovecot developers could comment on this and give us some direction (or candidate commits to investigate) or just let us know if the root cause has been found. This bug is a showstopper and has stopped me tracking master-2.3 for over 3 months now, as I can't test later builds or even upgrade to the 2.3.1 release while replication is so broken. Reuben > Message: 1 > Date: Sun, 6 May 2018 13:21:57 +1000 > From: Andy Weal <andy(a)bizemail.com.au> > To: dovecot(a)dovecot.org > Subject: 2.3.1 Replication is throwing scary errors > Message-ID: <f4274128-350b-9a74-a344-8e6caeffa112(a)bizemail.com.au> > Content-Type: text/plain; charset="utf-8"; Format="flowed" > > Hi all, > > New to the mailing lists but have joined up because of above */2.3.1 > Replication is throwing scary errors > > > /*Brief system configuration > ??? MX1 - Main > ??? ??? Freebsd 11.1-Release-p9 > ??? ??? Hosted on a Vultr VM in Sydney AU > ??? ??? MTA = Postfix 3.4-20180401 > ??? ??? Dovecot = 2.3.1 > ??? ??? File system = ufs > ??? MX2 - Backup > ??? ??? Freebsd 11.1-Release-p9 > ??? ???? Running on bare metal - no VM or jails > ??? ??? MTA = Postfix 3.4-20180401 > ??? ??? Dovecot = 2.3.1 > ??? ??? File system = ufs ( on SSD) > > */ > /*Brief sequence of events > > 1. ??? apx 10 days back upgraded both mx1 and mx2 to dovecot 2.3.1_2 > from 2.3.0 ? (service dovecot stop, portmaster upgrade, service > dovecot start) > 2. ??? both systems ran ok with no errors for 10 days. > 3. ??? Last night I shutdown mx2 and restarted it a few hours later > 4. ??? within minutes i was getting the following types of errors on mx2 > > ???????? May 06 12:56:29 doveadm: Error: Couldn't lock > /var/mail/vhosts/example.net/user1/.dovecot-sync.lock: > fcntl(/var/mail/vhosts/example.net/user1/.dovecot-sync.lock, write-lock, > F_SETLKW) locking failed: Timed out after 30 seconds (WRITE lock held by > pid 1960) > > ? Before i venture down the rabbit hole of fault finding and excess > coffee consumption I was wondering if any of you had any updates on the > problems discussed below. > > > Cheers for now, > Andy > > > > Hi, > > [Formatting is a bit rough, replying from a trimmed digest email] > >> /Message: 1 />/Date: Fri, 6 Apr 2018 15:04:35 +0200 />/From: Michael Grimm <trashcan at ellael.org > <https://dovecot.org/mailman/listinfo/dovecot>> />/To: Dovecot Mailing List <dovecot at dovecot.org > <https://dovecot.org/mailman/listinfo/dovecot>> />/Subject: Re: 2.3.1 Replication is throwing scary errors />/Message-ID: <E7E7A927-68F8-443F-BA59-E66CED8FE878 at ellael.org > <https://dovecot.org/mailman/listinfo/dovecot>> />/Content-Type: text/plain; charset=utf-8 />//>/Reuben Farrelly wrote: />>/From: Michael Grimm <trashcan at ellael.org > <https://dovecot.org/mailman/listinfo/dovecot>> />//>>>/[This is Dovecot 2.3.1 at FreeBSD STABLE-11.1 running in two jails at > distinct servers.] />>>/I did upgrade from 2.2.35 to 2.3.1 today, and I do become pounded by > error messages at server1 (and vice versa at server2) as follows: />>>/| Apr 2 17:12:18 <mail.err> server1.lan dovecot: doveadm: Error: > dsync(server2.lan): I/O has stalled, \ />>>/no activity for 600 seconds (last sent=mail_change, last > recv=mail_change (EOL)) />>>/| Apr 2 17:12:18 <mail.err> server1.lan dovecot: doveadm: Error: Timeout > during state=sync_mails \ />>>/(send=changes recv=mail_requests) />>>/[?] />>>/| Apr 2 18:59:03 <mail.err> server1.lan dovecot: doveadm: Error: > dsync(server2.lan): I/O has stalled, \ />>>/no activity for 600 seconds (last sent=mail, last recv=mail (EOL)) />>>/| Apr 2 18:59:03 <mail.err> server1.lan dovecot: doveadm: Error: Timeout > during state=sync_mails \ />>>/(send=mails recv=recv_last_common) />>>/I cannot see in my personal account any missing replications, *but* I > haven't tested this thoroughly enough. I do have customers being > serviced at these productive servers, *thus* I'm back to 2.2.35 until I > do understand or have learned what is going on. />//>/In my reply to this statement of mine I mentioned that I have seen those > timeouts quite some times during the past year. Thus, I upgraded to > 2.3.1 again, and boom: after some hours I ended up in hanging processes > [1] like (see Remko's mail in addition) ... />//>/doveadm-server: [IP4/6 <USER1> SOME/MAILBOX import:0/0] (doveadm-server) />//>/? at server2 paired with a file like ? />//>/-rw------- 1 vmail dovecot uarch 0 Apr 3 16:52 > /home/to/USER1/.dovecot-sync.lock />//>/Corresponding logfile entries at server2 are like ? />//>/Apr 3 17:10:49 <mail.err> server2.lan dovecot: doveadm: Error: Couldn't > lock /home/to/USER1/.dovecot-sync.lock: \ />/fcntl(/home/to/USER1/.dovecot-sync.lock, write-lock, F_SETLKW) locking > failed: Timed out after 30 seconds \ />/(WRITE lock held by pid 51110) />//>/[1] Even stopping dovecot will not end those processes. One has to > manually kill those before restarting dovecot. />//>/After one day of testing 2.3.1 with a couple of those episodes of > locking/timeout, and now missing mails depending with server your MUA > will connect to, I went back to 2.2.35. After two days at that version I > never had such an episode again. />//>>/It's not just you. This issue hit me recently, and it was impacting />>/replication noticeably. I am following git master-2.3 . />/[...] />>/There is also a second issue of a long standing race with replication />>/occurring somewhere whereby if a mail comes in, is written to disk, is />>/replicated and then deleted in short succession, it will reappear />>/again to the MUA. I suspect the mail is being replicated back from />>/the remote. A few people have reported it over the years but it's not />>/reliable or consistent, so it has never been fixed. />>/And lastly there has been an ongoing but seemingly minor issue />>/relating to locking timing out after 30s particularly on the remote />>/host that is being replicated to. I rarely see the problem on my />>/local disk where almost all of the mail comes in, it's almost always />>/occurring on the replicate/remote system. />//>/It might be time to describe our setups in order to possibly find co > mmon > grounds that might trigger this issue you describe and Rimko and myself > ran into as well. />//>/Servers: Cloud Instances (both identical), around 25ms latency apart. />/Intel Core Processor (Haswell, no TSX) (3092.91-MHz K8-class CPU) />/Both servers are connected via IPsec/racoon tunnels />/OS: FreeBSD 11.1-STABLE (both servers) />/Filesystem: ZFS />/MTA: postfix 3.4-20180401 (postfix delivers via dovecot's LMTP) />/IMAP: dovecot running in FreeBSD jails (issues with 2.3.1, fine with > 2.2.35) />/Replication: unsecured tcp / master-master />/MUA: mainly iOS or macOS mail.app, rarely roundcube / > For me: > > Servers: Main: VM on a VMWare ESXi local system (light > load), local SSD disks (no NFS) > Redundant: Linode VM in Singapore, around 250ms away > Also no NFS. Linode use SSDs for IO. > There is native IPv6 connectivity between both VMs. > As I am using TCPs I don't have a VPN between them - > just raw IPv6 end to end. > OS: Gentoo Linux x86_64 kept well up to date > Filesystem: EXT4 for both > MTA: Postfix 3.4-x (same as you) > IMAP: Dovecot running natively on the machine (no jail/chroot) > Replication: Secured TCP / master-master (but only one master is > actively used for SMTP and MUA access) > MUA: Thunderbird, Maildroid, MS Mail, Gmail client, > Roundcube, LG Mail client on handset etc > >> /I believe it is worthwhile to mention here that I run a poor man's > fail-over approach (round-robin DNS) as follows: />//>/DNS: mail.server.tld resolves to one IP4 and one IP6 address of each > server, thus 4 IP addresses in total / > For me I have a simple pair of servers that replicate mail to each > other. Clients connect to the main server only, which is where mail > comes in. The second one that experiences the problem with locking is > only a redundant server which is a secondary MX, that only gets > occasional SMTP deliveries from time to time. So the amount of > replication back from the "secondary" is very minimal; the vast bulk of > the replication is the primary replicating changes out. > > Reuben >

8 20

sieve, pigeonhole; reject message
by dovecot-user 08 Jun '18

08 Jun '18

Hello everybody. I use the version of dovecot 2.3.0.1 and postfix 3.3.0 on my test computer. Postfix pass incoming messages to Dovecot via the LMTP protocol. I want to understand how to fine tune the "reject" action in sieve-scripts. The task: in my installation I use the translation of a set of aliases into the (hidden) target email address inside postfix (postfix directives: canonical_classes = envelope_recipient; canonical_maps = hash://etc/postfix/canonical), so in dovecot the mails fall into one mailbox; However, the original headers (for example, the alias of the recipient) can be extracted with sieve scripts (the "Received" header). In my case, when I use the "reject" action in the sieve script, dovecot generates a message to the sender with the text: "Your message to <hidden(a)domain.tld> was automatically rejected ..", but this behavior opens the address to the sender of what is hidden behind the alias. Is it possible to redefine the text of the reject message using the extracting values from the "Received" header so that the email address hidden behind the alias does not appear there? Or some other way to customize the reject-message? Thank you.

1 0

dovecot-pigeonhole Missing sieve_imapsieve Plugin?
by Will Foster 07 Jun '18

07 Jun '18

Hi Folks, I am having a problem configuring imapsieve via dovecot-pidgeonhole on CentOS7. After following the docs here: https://wiki2.dovecot.org/Pigeonhole/Sieve/Plugins/IMAPSieve I get: dovecot[22026]: managesieve: Fatal: Plugin 'sieve_imapsieve' not found from directory /usr/lib64/dovecot/sieve dovecot[22026]: doveconf: Error: managesieve-login: dump-capability process returned 89 There doesn't seem to be that plugin present or provided by dovecot-pigeonhole # ls -lah /usr/lib64/dovecot/sieve/ total 56K drwxr-xr-x. 2 root root 46 Jun 5 12:16 . drwxr-xr-x. 7 root root 4.0K Jun 5 12:16 .. -rwxr-xr-x. 1 root root 52K Aug 3 2017 lib90_sieve_extprograms_plugin.so Am I doing something wrong? This is provided via the CentOS EPEL package Here's my system details: * dovecot-pigeonhole-2.2.10-8.el7.x86_64 * CentOS 7.5 on XFS * Rainloop Webmail / Mutt / IMAP access Here's my dovecot -n ------------ # 2.2.10: /etc/dovecot/dovecot.conf managesieve(root): Fatal: Plugin 'sieve_imapsieve' not found from directory /usr/lib64/dovecot/sieve doveconf: Error: managesieve-login: dump-capability process returned 89 # OS: Linux 3.10.0-862.2.3.el7.x86_64 x86_64 CentOS Linux release 7.5.1804 (Core) first_valid_uid = 1000 info_log_path = /var/log/dovecot-info.log log_path = /var/log/dovecot.log mail_location = mbox:~/Mail:INBOX=/home/%u/Mail/INBOX_MAIL mail_privileged_group = mail mbox_write_locks = fcntl 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 = %s driver = pam } passdb { driver = pam } plugin { imapsieve_url = sieve://localhost:4190 sieve = file:~/sieve;active=~/.dovecot.sieve sieve_after = /etc/dovecot/sieve-after sieve_dir = ~/sieve sieve_plugins = sieve_imapsieve sieve_extprograms sieve_user_log = ~/.dovecot.sieve.log } protocols = imap sieve sieve service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } } service managesieve-login { inet_listener sieve { port = 4190 } process_min_avail = 0 service_count = 1 vsz_limit = 64 M } ssl = required ssl_cert = </etc/pki/tls/certs/example.net.crt ssl_key = </etc/pki/tls/private/example.net.key userdb { driver = passwd } userdb { driver = passwd } protocol lmtp { mail_plugins = " sieve" } protocol lda { mail_plugins = " sieve" } protocol imap { mail_plugins = " imap_sieve" } ------------- Thanks for any guidance here. -- @sadsfae // gpg: A31F27E0 // irc: sadsfae come have a squat at https://hobo.house

2 2

Re: 2.3.1 Replication is throwing scary errors
by Michael Grimm 07 Jun '18

07 Jun '18

Am 2018-06-07 08:48, schrieb Remko Lodder: > On Thu, Jun 07, 2018 at 08:04:49AM +0200, Michael Grimm wrote: >> Conclusion: After 12 hours of running a patched FBSD port I do get >> those >> error messages but replictaion seems to work now. But, I still have >> the >> feeling that there might something else going wrong. > > I agree with that. Are you using the new pkg that ler@ prepared ? That > includes > the patch and is a 'native' package.. Yes, I am running this new port from ler@. And: Thanks for his very fast modification! Regards, Michael

1 0

Shared mailboxes, index files and 'per-user-seen' flags
by Thomas Robers 07 Jun '18

07 Jun '18

Hello, i have a dovecot server version 2.3.1 under CentOS 6.9 and we're using shared mailboxes with index files shared. With this configuration I can see a lot of error messages like: Jun 6 13:20:31 mail dovecot: Error: imap(userA(a)tutech.de)<4513> <onjjWPdtDuLAqG3R>: /export/home/imap/userA(a)tutech.de/shared /userB(a)tutech.de/folder/dovecot.index.pvt view is inconsistent In 10-mail.conf the location setting is: location = maildir:%%h/Maildir:INDEXPVT=%h/shared/%%u I thought setting the index files to "not shared" might help to get rid of the errors, so I changed the setting to: location = maildir:%%h/Maildir:INDEX=%h/shared/%%u:INDEXPVT=%h /shared/%%u like it's mentioned in the Dovecot wiki. But that doesn't work as I expected, because the 'per-user-seen' flags do not work correctly anymore, i think. If UserA, who has UserB as shared mailbox, changes the seen flags of UserBs INBOX, UserBs seen flags are also changed. The other way, if UserB changes seen flags in his INBOX they are not changed in the shared view of UserA. Is this the supposed way to work or do i have an error in the configuration? Any help is appreciated. Thanks, Thomas. Here's my currently used configuration: # 2.3.1 (c5a5c0c82): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.devel (61b47828) # OS: Linux 2.6.32-696.23.1.el6.x86_64 x86_64 CentOS release 6.9 (Final) ext4 # Hostname: mail.tutech.de auth_master_user_separator = * auth_mechanisms = plain login auth_verbose = yes disable_plaintext_auth = no doveadm_password = # hidden, use -P to show it doveadm_port = 12345 imap_max_line_length = 2 M mail_debug = yes mail_location = maildir:/export/home/imap/%Lu/Maildir mail_plugins = acl zlib mail_log notify mail_prefetch_count = 1 mailbox_idle_check_interval = 10 secs 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 index ihave duplicate mime foreverypart extracttext namespace { hidden = no ignore_on_failure = no inbox = no list = children location = maildir:%%h/Maildir:INDEXPVT=%h/shared/%%u prefix = shared/%%u/ separator = / subscriptions = yes type = shared } namespace inbox { hidden = no inbox = yes list = 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 = INBOX/ separator = / type = private } passdb { args = /etc/dovecot/master-users driver = passwd-file master = yes } passdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } plugin { acl = vfile:/etc/dovecot/global-acls:cache_secs=300 acl_shared_dict = file:/export/home/shared-db/shared-mailboxes mail_log_events = append delete undelete expunge copy mailbox_delete mailbox_rename flag_change mail_log_fields = uid box msgid size from flags mail_replica = tcp:mail2.tutech.de sieve = ~/.dovecot.sieve sieve_dir = ~/sieve sieve_global = /var/lib/dovecot/sieve/global/ sieve_user_log = ~/.dovecot.sieve.log zlib_save = gz zlib_save_level = 6 } protocols = imap pop3 lmtp sieve sieve service aggregator { fifo_listener replication-notify-fifo { mode = 0666 user = vmail } unix_listener replication-notify { mode = 0666 user = vmail } } service auth { unix_listener /var/spool/postfix/private/auth { mode = 0666 } unix_listener auth-userdb { group = vmail mode = 0660 user = vmail } } service config { unix_listener config { user = vmail } } service doveadm { inet_listener { port = 12345 } user = vmail } service imap-login { inet_listener imaps { port = 993 ssl = yes } process_limit = 500 process_min_avail = 20 } service imap { executable = imap } service lmtp { inet_listener lmtp { address = 127.0.0.1 port = 24 } } service managesieve-login { inet_listener sieve { port = 4190 } inet_listener sieve_deprecated { port = 2000 } } service pop3-login { inet_listener pop3s { port = 995 ssl = yes } } service pop3 { executable = pop3 } service replicator { unix_listener replicator-doveadm { mode = 0666 } } ssl = required ssl_cert = </etc/pki/dovecot/certs/mail.tutech.de.crt_chain ssl_cipher_list = ALL:!LOW:!SSLv2:!EXP:!aNULL:!EXPORT ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it syslog_facility = local6 userdb { args = /etc/dovecot/dovecot-ldap-userdb.conf.ext driver = ldap } protocol lmtp { mail_plugins = acl zlib mail_log notify sieve } protocol imap { mail_max_userip_connections = 100 mail_plugins = acl zlib mail_log notify imap_zlib imap_acl rawlog_dir = /tmp/rawlog/%u }

2 1

Header DATE field not returned when placed after MIME section
by Xavier Guerin 06 Jun '18

06 Jun '18

Hello, I am using Dovecot 2.2.34p0 on OpenBSD 6.3 stable. I am writting an application using the vmime (http://www.vmime.org) library (x-ref issue: https://github.com/kisli/vmime/issues/199). I noticed through testing over my own e-mail server that in some situations the DATE field is not returned upon ENVELOPE or HEADER.FIELDS request. The e-mails at fault happen to have the DATE field at the very end of the header, after the MIME section. Example 1: Delivered-To: Received: Return-Path: Delivered-To: DKIM-Signature: From: To: Message-ID: Subject: MIME-Version: 1.0 Content-Type: text/html;charset=UTF-8 Content-Transfer-Encoding: 7bit Date: Fri, 01 Jun 2018 17:44:44 -0400 Example 2: Return-Path: Delivered-To: Received: Delivered-To: DKIM-Signature: From: Reply-To: To: Subject: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_338_1573405959.1527768044781" X-Mailer: EMail_2.0 Date: Fri, 01 Jun 2018 17:36:01 -0400 Thanks in advance for the insight,

3 2

offtopic: Solr compatible IMAP client
by Andy Smith 04 Jun '18

04 Jun '18

Hi, not sure if I'm allowed to go this off topic on here, sorry if not! I've just installed Solr FTS for Dovecot and its great, as is Dovecot! ;) It works perfectly for fast searches using Roundcube, but can anyone suggest any Windows and/or Linux mail clients that work well with IMAP searches rather than doing their own searches on local copies of mails? I've had a look at Thunderbird and you can use IMAP search, buy you have to manually select it from an advanced search dialogue and it seems you cannot make this the default behaviour. I also tried OperaMail but it doesn't appear to work at all (only header is searchable without downloading local copies). I'm pretty sure Outlook will only use its own search engine on its local copy of data. thanks a lot, Andy. PS this guide was really helpful for setting up Solr FTS with a recent release of Solr (I'm using 6.5), might be worth including a link somewhere on the Dovecot wiki?: http://mor-pah.net/2016/08/15/dovecot-2-2-with-solr-6-or-5

4 7

Re: SSL error after upgrading to 2.31
by Aki Tuomi 01 Jun '18

01 Jun '18

You forgot to cc the list. ssl_ca is used only for validating client certificates. ---Aki TuomiDovecot oy -------- Original message --------From: Marc Perkel <marc(a)perkel.com> Date: 21/05/2018 18:25 (GMT+02:00) To: Aki Tuomi <aki.tuomi(a)dovecot.fi> Subject: Re: SSL error after upgrading to 2.31 On 05/21/2018 07:54 AM, Aki Tuomi wrote: Does ssl_cert file contain intermediates? No - but the ssl_ca does. --- Aki Tuomi Dovecot oy -------- Original message -------- From: Marc Perkel <marc(a)perkel.com> Date: 21/05/2018 16:32 (GMT+02:00) To: dovecot(a)dovecot.org Subject: SSL error after upgrading to 2.31 After upgrading to 2.31 I'm getting this error. Not sure what I'm doing wrong. No (No signatures could be verified because the chain contains only one certificate and it is not self signed.) ssl = yes ssl_cert = </etc/exim/certs/ctyme.com.crt ssl_key = </etc/exim/certs/ctyme.com.key ssl_ca = </etc/exim/certs/ca.crt local mail.ctyme.com { protocol imap { ssl_cert = </etc/exim/certs/ctyme.com.crt ssl_key = </etc/exim/certs/ctyme.com.key ssl_ca = </etc/exim/certs/ca.crt } protocol pop3 { ssl_cert = </etc/exim/certs/ctyme.com.crt ssl_key = </etc/exim/certs/ctyme.com.key ssl_ca = </etc/exim/certs/ca.crt } } local mail.junkemailfilter.com { protocol imap { ssl_cert = </etc/exim/certs/junkemailfilter.com.crt ssl_key = </etc/exim/certs/junkemailfilter.com.key ssl_ca = </etc/exim/certs/ca.crt } protocol pop3 { ssl_cert = </etc/exim/certs/junkemailfilter.com.crt ssl_key = </etc/exim/certs/junkemailfilter.com.key ssl_ca = </etc/exim/certs/ca.crt } }

3 9