April 2016 - dovecot - dovecot.org

Thunderbird version 45 no longer can login via SSL
by CJ Keist 22 Apr '16

22 Apr '16

All, Just ran into issue with the latest Thunderbird release today, version 45.0. This version will no longer login to our dovecot 1.2.17 version. I now this is old version but wanting to know if there is anyone finding a solution to this? Right now our work around is to reinstall Thunderbird version 38.7.2 Thanks... -- C. J. Keist Email: cj.keist(a)colostate.edu Systems Group Manager Solaris 10 OS (SAI) Engineering Network Services Phone: 970-491-0630 College of Engineering, CSU Fax: 970-491-5569 Ft. Collins, CO 80523-1301 All I want is a chance to prove 'Money can't buy happiness'

3 2

multiple recipient_delimiter
by Jörg Backschues 22 Apr '16

22 Apr '16

Hello, does the recipient_delimiter option accepts multiple delimiter by now? -- Regards Jörg Backschues

3 3

lda_original_recipient_header overrides RCPT TO?
by Gedalya 22 Apr '16

22 Apr '16

Hi all, The example config says: # Header where the original recipient address (SMTP's RCPT TO: address) is taken # from if not available elsewhere. With dovecot-lda -a parameter overrides this. # A commonly used header for this is X-Original-To. #lda_original_recipient_header = I'm using dovecot 2.2.19 The "if not available elsewhere" bit seems to hold true for LDA, but not for LMTP. That is to say, if the value I want used is passed with LDA using the -a option, and another one I want ignored is passed in the header specified in this option, it works correctly and I have the address detail in sieve. However when using LMTP and the desired value is passed as RCPT TO, and this option is defined, and such a header exists -- its value seems to take effect, and is matched by sieve as the envelope address.

1 0

Randomly SSL Errors since upgrade to 2.2.23-1 (Enterprise Edition)
by Urban Loesch 21 Apr '16

21 Apr '16

Hi, first of all, many thanks for a great piece of software. Today I updated one of our 2 IMAP/POP3 proxies from version 2.2.15.17-1 to 2.2.23.1-1 (both are enterprise editions). After the update I now see randomly the following errors in the log file on my first proxy: ... Apr 15 10:28:54 imap1 dovecot: pop3-login: Error: SSL: Stacked error: error:1408F119:SSL routines:SSL3_GET_RECORD:decryption failed or bad record mac Apr 15 10:34:24 imap1 dovecot: pop3-login: Error: SSL: Stacked error: error:1408F119:SSL routines:SSL3_GET_RECORD:decryption failed or bad record mac Apr 15 10:37:11 imap1 dovecot: imap-login: Error: SSL: Stacked error: error:140D00CF:SSL routines:SSL_write:protocol is shutdown Apr 15 10:39:04 imap1 dovecot: imap-login: Error: SSL: Stacked error: error:1408F119:SSL routines:SSL3_GET_RECORD:decryption failed or bad record mac Apr 15 10:43:02 imap1 dovecot: imap-login: Error: SSL: Stacked error: error:140D00CF:SSL routines:SSL_write:protocol is shutdown Apr 15 10:45:14 imap1 dovecot: pop3-login: Error: SSL: Stacked error: error:1408F119:SSL routines:SSL3_GET_RECORD:decryption failed or bad record mac Apr 15 10:50:31 imap1 dovecot: imap-login: Error: SSL: Stacked error: error:140D00CF:SSL routines:SSL_write:protocol is shutdown Apr 15 10:54:56 imap1 dovecot: imap-login: Error: SSL: Stacked error: error:1408F119:SSL routines:SSL3_GET_RECORD:decryption failed or bad record mac Apr 15 10:57:44 imap1 dovecot: imap-login: Error: SSL: Stacked error: error:140D00CF:SSL routines:SSL_write:protocol is shutdown Apr 15 10:59:49 imap1 dovecot: pop3-login: Error: SSL: Stacked error: error:140D00CF:SSL routines:SSL_write:protocol is shutdown Apr 15 11:00:59 imap1 dovecot: imap-login: Error: SSL: Stacked error: error:140D00CF:SSL routines:SSL_write:protocol is shutdown Apr 15 11:13:43 imap1 dovecot: pop3-login: Error: SSL: Stacked error: error:14094438:SSL routines:SSL3_READ_BYTES:tlsv1 alert internal error: SSL alert number 80 Apr 15 11:15:21 imap1 dovecot: imap-login: Error: SSL: Stacked error: error:140D00CF:SSL routines:SSL_write:protocol is shutdown Apr 15 11:18:33 imap1 dovecot: pop3-login: Error: SSL: Stacked error: error:140D00CF:SSL routines:SSL_write:protocol is shutdown Apr 15 11:20:12 imap1 dovecot: pop3-login: Error: SSL: Stacked error: error:140D00CF:SSL routines:SSL_write:protocol is shutdown Apr 15 11:20:40 imap1 dovecot: pop3-login: Error: SSL: Stacked error: error:1408F119:SSL routines:SSL3_GET_RECORD:decryption failed or bad record mac ... Some more details: OS: Debian wheezy (latest patchlevel) Dovecot: ii dovecot-ee-core 2:2.2.23.1-1 ii dovecot-ee-imapd 2:2.2.23.1-1 ii dovecot-ee-managesieved 2:2.2.23.1-1 ii dovecot-ee-mysql 2:2.2.23.1-1 ii dovecot-ee-pop3d 2:2.2.23.1-1 ii dovecot-ee-sieve 2:2.2.23.1-1 Libssl: ii libssl1.0.0:amd64 1.0.1e-2+deb7u20 One my second proxy there is running also Debian Wheezy with the latest patchlevel but dovecot version 2.2.15.17-1 (not yet updated): ii dovecot-ee-core 1:2.2.15.17-1 ii dovecot-ee-imapd 1:2.2.15.17-1 ii dovecot-ee-managesieved 0.4.6-4 ii dovecot-ee-mysql 1:2.2.15.17-1 ii dovecot-ee-pop3d 1:2.2.15.17-1 ii dovecot-ee-sieve 0.4.6-4 On this box I can't see this strange errors. Until now there was no user that complaints that he can't read his mails. Do you know what could cause this errors (for example: very old clients and so on)? Or are the logging of this errors new in dovecot 2.2.23? Many thanks Urban Loesch

2 2

problem with Sieve Duplicate Extension when used together with fileinto
by Marco Giunta 21 Apr '16

21 Apr '16

Hi at all, I'm trying to figure out a problem with Sieve Duplicate Extension when used together with fileinto. I use a Dovecot 2.2.23 and Pigeonhole v0.4.13 I have a user (user01) with 3 email addresses (mail01(a)example.com, mail02(a)example.com, user01(a)example.com) I want to discard duplicate, and I want to move email in different folder, so I'm using this sieve script: ---------------------------------------------- require ["fileinto", "duplicate", "imap4flags"]; if duplicate { discard; stop; } if address :is :all "to" "mail01(a)example.com" { fileinto "mail01"; } if address :is :all "to" "mail02(a)example.com" { fileinto "mail02"; } ------------------------------------- To make my test, I have a script that send always the same email; this is an example: ----------------------------------------- Delivered-To: user01(a)example.com Received: from smtp-server.example.com ([192.168.1.214]) by lmtp-server.example.com (Dovecot) with LMTP id YSaBBU53GFdhbwAAIDyJFw for <user01(a)example.com>; Thu, 21 Apr 2016 08:48:41 +0200 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: TEST EMAIL From: myself(a)example.com To: mail01(a)example.com, mail02(a)example.com, user01(a)example.com Date: Thu, 21 Apr 2016 08:48:41 +0200 Message-ID: <20160421064841.26889.86769(a)kratos.example.com> This is a test email Please ignore me. -------------------------------------------- The problem is that duplicate extension doesn't ALWAYS work ; I mean, one time it works (sieve discard 2 duplicate mails), one time it doesn't work at all (sieve doesn't discard any mail), another time it works only for one mail (sieve discards only 1 mail) Here my server log: Apr 21 08:49:07 smtp-server dovecot: lmtp(user01(a)example.com): 1dKXOMl3GFdibwAAIDyJFw: sieve: msgid=<20160421064906.26896.49900(a)myhost.example.com>: stored mail into mailbox 'mail01' Apr 21 08:49:07 smtp-server dovecot: lmtp(user01(a)example.com): 1dKXOMl3GFdibwAAIDyJFw: sieve: msgid=<20160421064906.26896.49900(a)myhost.example.com>: stored mail into mailbox 'mail02' Apr 21 08:49:07 smtp-server dovecot: lmtp(user01(a)example.com): oSM3And3GFdFaQAAIDyJFw: sieve: msgid=<20160421064906.26896.49900(a)myhost.example.com>: marked message to be discarded if not explicitly delivered (discard action) Apr 21 08:49:07 smtp-server dovecot: lmtp(user01(a)example.com): eY00CY93GFcucgAAIDyJFw: sieve: msgid=<20160421064906.26896.49900(a)myhost.example.com>: marked message to be discarded if not explicitly delivered (discard action) Apr 21 08:49:13 smtp-server dovecot: lmtp(user01(a)example.com): dSOyOtV3GFcmdAAAIDyJFw: sieve: msgid=<20160421064913.26904.88802(a)myhost.example.com>: stored mail into mailbox 'mail01' Apr 21 08:49:13 smtp-server dovecot: lmtp(user01(a)example.com): dSOyOtV3GFcmdAAAIDyJFw: sieve: msgid=<20160421064913.26904.88802(a)myhost.example.com>: stored mail into mailbox 'mail02' Apr 21 08:49:13 smtp-server dovecot: lmtp(user01(a)example.com): pSM3And3GFdFaQAAIDyJFw: sieve: msgid=<20160421064913.26904.88802(a)myhost.example.com>: marked message to be discarded if not explicitly delivered (discard action) Apr 21 08:49:13 smtp-server dovecot: lmtp(user01(a)example.com): vZWNOMl3GFcldAAAIDyJFw: sieve: msgid=<20160421064913.26904.88802(a)myhost.example.com>: marked message to be discarded if not explicitly delivered (discard action) Apr 21 08:49:18 smtp-server dovecot: lmtp(user01(a)example.com): eSOyOtV3GFcmdAAAIDyJFw: sieve: msgid=<20160421064918.26911.55371(a)myhost.example.com>: stored mail into mailbox 'mail01' Apr 21 08:49:18 smtp-server dovecot: lmtp(user01(a)example.com): qSM3And3GFdFaQAAIDyJFw: sieve: msgid=<20160421064918.26911.55371(a)myhost.example.com>: stored mail into mailbox 'mail01' Apr 21 08:49:18 smtp-server dovecot: lmtp(user01(a)example.com): qSM3And3GFdFaQAAIDyJFw: sieve: msgid=<20160421064918.26911.55371(a)myhost.example.com>: stored mail into mailbox 'mail02' Apr 21 08:49:18 smtp-server dovecot: lmtp(user01(a)example.com): aSaBBU53GFdhbwAAIDyJFw: sieve: msgid=<20160421064918.26911.55371(a)myhost.example.com>: stored mail into mailbox 'mail01' Apr 21 08:49:18 smtp-server dovecot: lmtp(user01(a)example.com): aSaBBU53GFdhbwAAIDyJFw: sieve: msgid=<20160421064918.26911.55371(a)myhost.example.com>: stored mail into mailbox 'mail02' Apr 21 08:49:18 smtp-server dovecot: lmtp(user01(a)example.com): eSOyOtV3GFcmdAAAIDyJFw: sieve: msgid=<20160421064918.26911.55371(a)myhost.example.com>: stored mail into mailbox 'mail02' Apr 21 08:49:22 smtp-server dovecot: lmtp(user01(a)example.com): rSM3And3GFdFaQAAIDyJFw: sieve: msgid=<20160421064922.26919.68793(a)myhost.example.com>: stored mail into mailbox 'mail01' Apr 21 08:49:22 smtp-server dovecot: lmtp(user01(a)example.com): rSM3And3GFdFaQAAIDyJFw: sieve: msgid=<20160421064922.26919.68793(a)myhost.example.com>: stored mail into mailbox 'mail02' Apr 21 08:49:22 smtp-server dovecot: lmtp(user01(a)example.com): YVCsNPJ3GFd1dgAAIDyJFw: sieve: msgid=<20160421064922.26919.68793(a)myhost.example.com>: marked message to be discarded if not explicitly delivered (discard action) Apr 21 08:49:23 smtp-server dovecot: lmtp(user01(a)example.com): bSaBBU53GFdhbwAAIDyJFw: sieve: msgid=<20160421064922.26919.68793(a)myhost.example.com>: marked message to be discarded if not explicitly delivered (discard action) Apr 21 08:49:27 smtp-server dovecot: lmtp(user01(a)example.com): fSOyOtV3GFcmdAAAIDyJFw: sieve: msgid=<20160421064927.26926.28383(a)myhost.example.com>: stored mail into mailbox 'mail01' Apr 21 08:49:27 smtp-server dovecot: lmtp(user01(a)example.com): sSM3And3GFdFaQAAIDyJFw: sieve: msgid=<20160421064927.26926.28383(a)myhost.example.com>: stored mail into mailbox 'mail01' Apr 21 08:49:27 smtp-server dovecot: lmtp(user01(a)example.com): sSM3And3GFdFaQAAIDyJFw: sieve: msgid=<20160421064927.26926.28383(a)myhost.example.com>: stored mail into mailbox 'mail02' Apr 21 08:49:27 smtp-server dovecot: lmtp(user01(a)example.com): fSOyOtV3GFcmdAAAIDyJFw: sieve: msgid=<20160421064927.26926.28383(a)myhost.example.com>: stored mail into mailbox 'mail02' Apr 21 08:49:27 smtp-server dovecot: lmtp(user01(a)example.com): ZVCsNPJ3GFd1dgAAIDyJFw: sieve: msgid=<20160421064927.26926.28383(a)myhost.example.com>: marked message to be discarded if not explicitly delivered (discard action) As you can see, the message ID of a single sent, is the same, so the duplicate extension should work. If I replace the 'fileinto' rule with, for example, a 'setflag' rule: ----------------------------------------------- require ["fileinto", "duplicate", "imap4flags"]; if duplicate { discard; stop; } if address :is :all "to" "mail01(a)example.com" { setflag "\\seen"; } if address :is :all "to" "mail02(a)example.com" { setflag "\\seen"; } ---------------------------------------------- it works like a charm: for every mail sent, the duplicate extension works. What is it wrong ? someone has any clue ? Cheers, Marco -- Marco Giunta - ITCS SysAdmin Via Bonomea, 265 34136 - Trieste, Italy Tel: +39-040-3787-503 Fax: +39-040-3787-244

1 0

Deliver same E-Mail in same Mailbox only once ?
by Christoph Adomeit 21 Apr '16

21 Apr '16

Hi there, I have a customer with domain a@tld and domain b@tld. b.tld is an alias for a.tld The Server is using virtual users based on mysql, dovecot for delivery and Maildir for Mail-Storage. If someone writes an e-mail to a.tld with a cc: to b.tld the customer receives the E-Mail twice. Is there a way to deliver the same Mail in the same Mailbox only once ? -- Christoph Adomeit GATWORKS GmbH Reststrauch 191 41199 Moenchengladbach Sitz: Moenchengladbach Amtsgericht Moenchengladbach, HRB 6303 Geschaeftsfuehrer: Christoph Adomeit, Hans Wilhelm Terstappen Christoph.Adomeit(a)gatworks.de Internetloesungen vom Feinsten Fon. +49 2166 9149-32 Fax. +49 2166 9149-10

5 5

Module is for different ABI version
by Oliver Riesen-Mallmann 21 Apr '16

21 Apr '16

Hi, I'm using the Dovecot Prebuilt Binary: deb http://xi.rename-it.nl/debian/ stable-auto/dovecot-2.2 main It seems, that the Prebuilt Binary provided at least once the 2.3 version, because doveconf -n shows: # 2.3.devel (5e7036c): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.devel (ef25ce6) # OS: Linux 3.2.0-4-amd64 x86_64 Debian 7.10 Now Prebuilt Binary provides the 2.2 version again, but I get some error messages on updates: Preparing to replace dovecot-imapd 2:2.2.23-1~auto+14 (using .../dovecot-imapd_2%3a2.2.23-1~auto+16_amd64.deb) ... doveconf: Error: Couldn't load plugin /usr/lib/dovecot/modules/settings/libmanagesieve_login_settings.so: Module is for different ABI version 2.2.ABIv20(2.2.devel) (we have 2.3.ABIv0(2.3.devel)) doveconf: Error: Couldn't load plugin /usr/lib/dovecot/modules/settings/libmanagesieve_settings.so: Module is for different ABI version 2.2.ABIv20(2.2.devel) (we have 2.3.ABIv0(2.3.devel)) and: Preparing to replace dovecot-core 2:2.2.23-1~auto+14 (using .../dovecot-core_2%3a2.2.23-1~auto+16_amd64.deb) ... doveconf: Error: Couldn't load plugin /usr/lib/dovecot/modules/settings/libmanagesieve_login_settings.so: Module is for different ABI version 2.2.ABIv20(2.2.devel) (we have 2.3.ABIv0(2.3.devel)) doveconf: Error: Couldn't load plugin /usr/lib/dovecot/modules/settings/libmanagesieve_settings.so: Module is for different ABI version 2.2.ABIv20(2.2.devel) (we have 2.3.ABIv0(2.3.devel)) After the update doveconf -n shows: # 2.2.devel (8828071): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.devel (ef25ce6) # OS: Linux 3.2.0-4-amd64 x86_64 Debian 7.10 How can I go back to ABI version 2.2? Regards Oliver

1 0

Foreman component
by Aki Tuomi 20 Apr '16

20 Apr '16

Hi! I am planning to add foreman component to dovecot core and I am hoping for some feedback: Foreman - generic per-user worker handling component It is responsible for managing worker pools per protocol, lifecycle management of workers and handing out instances to others, as in, unix socket connections. Each time a request is made to foreman for a worker, the worker is instantiated (if possible) and locked. Then connection is created to the socket of the worker, and the file descriptor is returned to requestor. When the requestor has completed the task, it's responsibility is to close the DATA channel and also ask foreman to unlock the worker. Components can register new workers using lib-foreman's API. Each worker is registered with struct foreman_worker { const char *protocol; const char *path; const char *version; unsigned int max_instances; unsigned int max_requests; /* how many requests one worker can handle */ unsigned int max_idletime_secs; /* how long worker can idle */ unsigned int max_processtime_secs; /* how long worker can process something */ unsigned int max_lifetime_secs; /* how long a worker can live this can be exceeded if the worker has work to do. */ }; /* minimum lifetime of worker: max_idletime_secs */ /* absolute maximum lifetime of worker: max_lifetime_secs + max_processtime_secs */ The unsigned ints are optional. If they are not defined, the workers are kept until foreman exceeds the total number of workers permitted across pools. Pools are per-worker-class pools, and are generated when a worker is registered. Version specifies the protocol version and is going to be "1000" now. Next version will always be 1001, 1002 etc. Any feedback or questions are welcome! Aki

3 2

Reappearing emails (resolved by 2.2.23)
by Ron Cleven 20 Apr '16

20 Apr '16

> ------------------------------ > > Message: 6 > Date: Wed, 16 Mar 2016 16:58:49 +1100 > From: Timo Sirainen<tss(a)iki.fi> > To: Dovecot Mailing List<dovecot(a)dovecot.org> > Subject: Re: Reappearing emails - IMAP trace > Message-ID:<4C26CC22-7C7D-4D91-A767-4E5B3D1F12BA(a)iki.fi> > Content-Type: text/plain; charset=us-ascii > > What mailbox format do you use? Are you able to reproduce this by running doveadm sync commands manually instead of letting replication do it? For example: > > - doveadm sync -s "" -d -u user@domain > state > - Run the UID STORE & UID MOVE > - doveadm sync -s "`cat state`" -d -u user@domain > > There have been some fixes, especially recentlyhttps://github.com/dovecot/core/commit/950a6e61d6c2dac961ce031bdd8b… sounds a bit similar although I don't really see how it would apply here. Would be a good idea to try anyway with v2.2.22.rc1 (which seems to be stable enough that I'll make v2.2.22 release soon). > > Anyway, I attempted a few times to reproduce it with your test but wasn't able to. We had been running 2 replicating servers (Maildir format) using version 2.2.10 under CentOS 7 in production for quite some time. In this forum, I reported a problem that I traced to a timing problem where unread emails being moved to Trash would magically reappear in the INBOX. I have since upgraded our production servers to 2.2.23. The new version resolved the problem. The version upgrade also resolved the occasional, but annoying, dsync maillog entries "Duplicate file entry at line ...". So, I am a very happy camper and appreciate the feedback.

2 1

GSSAPI authentication setup
by Braden McDaniel 20 Apr '16

20 Apr '16

I'm setting up dovecot on a new box; and once again I find myself banging my head against GSSAPI authentication. The particularly irritating thing is that I have this working on another box. I've done my best to ape the configuration of that box; but it's been some years since I set it up and somewhere along the line I have failed. My dovecot.conf has: auth_mechanism = plain gssapi passdb { driver = pam } userdb { driver = ldap args = /etc/dovecot/dovecot-ldap.conf.ext } where /etc/dovecot/dovecot-ldap.conf.ext is: hosts = ldap dn = cn=Manager,dc=endoframe,dc=net dnpass = XXXXXXXX ldap_version = 3 base = ou=people,dc=endoframe,dc=net deref = never scope = subtree user_attrs = homeDirectory=home,uidNumber=uid,gidNumber=gid user_filter = (&(objectClass=posixAccount)(uid=%u)) I've diff'd the contents of /etc/dovecot on the working vs. non-working servers, and I can see nothing of pertinence (just a few lines about loading the sieve plug-in). Now, logging in with the kerberos password via PAM *is* working. /etc/pam.d/dovecot: #%PAM-1.0 auth sufficient pam_krb5.so account sufficient pam_krb5.so But GSSAPI authentication is not: [ root@hinge ~]# telnet localhost 143 Trying ::1... Connected to localhost. Escape character is '^]'. * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE STARTTLS AUTH=PLAIN AUTH=GSSAPI] Dovecot ready. a authenticate GSSAPI a NO [UNAVAILABLE] Temporary authentication failure. [hinge.endoframe.net:2016-04-16 21:33:32] ^] telnet> close Connection closed. Oh... The kerberos server does have an IMAP service key for hinge; and that service key appears in hinge's /etc/krb5.keytab, as well. Any pointers on where I should be looking at this point would be very much appreciated. -- Braden McDaniel <braden(a)endoframe.com>

3 6