- dovecot - dovecot.org

Maildir P flag?
by Andrew McGlashan 23 Apr '16

23 Apr '16

Hi, I use Thunderbird with a mailredirect addon. It used to show me which emails were redirected. I believe it used the "P" Maildiir flag for this status. Now it seems that none of my email store has any file with a flag of P. Is this something that dovecot may have adjusted with my mail store? And if so, why? If not, any ideas where I might look for the next "culprit"? ;-) Thanks AndrewM

1 0

Progress messages
by Joel Roth 23 Apr '16

23 Apr '16

Hi Dovecot maintainers, I'm maintainer of Net::IMAP::Client, a perl IMAP client library.[1] I've had two bug reports related to Dovecot's in-progress messages.[2,3] While patches have been submitted to resolve both of these bugs, I would like to minimize the possibilty of future breakage. Hence the following questions: 1. Which parts of the RFC are relevant to the in-progress messages? 2. Do you have a list of all of Dovecot's in-progress messages? 3. If, in future, other in-progress messages may be added, can you provide a standard syntax that I may use to strip them from the reply stream. Finally, please CC replies to me, as I am not joined to the list. Thank you for your attention. Joel 1. https://metacpan.org/pod/Net::IMAP::Client 2. https://rt.cpan.org/Public/Bug/Display.html?id=84623 3. https://rt.cpan.org/Public/Bug/Display.html?id=113489 -- Joel Roth

2 1

UTF-8 encoded folders on filesystem
by Pavel Volkovitskiy 22 Apr '16

22 Apr '16

Hello! I wonder if that possible to have utf-8 encoded folders on filesystem with dovecot? May be this feature planned already? -- Pavel

3 5

Aborted login (auth failed)
by Christof Bodner 22 Apr '16

22 Apr '16

Hi, My SSL auth got invalid, so I updated my SSL configuration (Apache works) This ist the log: --- Apr 22 11:01:55 rosi dovecot: imap-login: Debug: SSL: elliptic curve secp384r1 will be used for ECDH and ECDHE key exchanges Apr 22 11:01:55 rosi dovecot: imap-login: Debug: SSL: elliptic curve secp384r1 will be used for ECDH and ECDHE key exchanges Apr 22 11:01:55 rosi dovecot: auth: Debug: auth client connected (pid=3466) Apr 22 11:01:55 rosi dovecot: auth: Debug: client in: AUTH#0111#011PLAIN#011service=imap#011secured#011session=a5AlFA8x3gAAAAAAAAAAAAAAAAAAAAAB#011lip=::1#011rip=::1#011lport=143#011rport=48350#011resp=<hidden> Apr 22 11:01:55 rosi dovecot: auth-worker(3460): Debug: pam(test,::1): lookup service=dovecot Apr 22 11:01:55 rosi dovecot: auth-worker(3460): Debug: pam(test,::1): #1/1 style=1 msg=Password: Apr 22 11:01:57 rosi dovecot: auth-worker(3460): pam(test,::1): pam_authenticate() failed: Authentication failure (password mismatch?) Apr 22 11:01:59 rosi dovecot: auth: Debug: client passdb out: FAIL#0111#011user=test Apr 22 11:01:59 rosi dovecot: imap-login: Aborted login (auth failed, 1 attempts in 4 secs): user=<test>, method=PLAIN, rip=::1, lip=::1, secured, session=<a5AlFA8x3gAAAAAAAAAAAAAAAAAAAAAB> --- A login via SSH is working, What could be the reason for the login fail? This is my config: --- # 2.2.9: /etc/dovecot/dovecot.conf # OS: Linux 3.13.0-85-generic x86_64 Ubuntu 14.04.4 LTS auth_debug = yes auth_verbose = yes mail_location = mbox:~/mail:INBOX=/var/mail/%u namespace { hidden = yes inbox = yes list = no location = mbox:~/mail:INBOX=/var/mail/%u prefix = "#mbox/" separator = / type = private } passdb { driver = pam } plugin { sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } protocols = " imap pop3" service auth { unix_listener /var/spool/postfix/private/auth { mode = 0666 } sl_ca = </etc/letsencrypt/live/HOST/chain.pem ssl_cert = </etc/letsencrypt/live/HOST/cert.pem ssl_key = </etc/letsencrypt/live/HOST/privkey.pem userdb { driver = passwd } verbose_ssl = yes protocol imap { mail_max_userip_connections = 400 } --- Thanks in advance for your help! KR, Christof -- --------------------------------------------------------------------- <http://www.oe8.oevsv.at>Landesverband Kärnten Christof Bodner, OE8BCK Bertha-von-Suttnerstraße 6/4 9500 Villach ---------------------------------------------------------------- email: mailto:oe8bck@oevsv.at Tel.: +43-650-7215383 --------------------------------------------------------------------- GnuPG public key: 0x7204CB8C Fingerprint 4065 0716 9A15 E26B 2286 9F04 FD3B 74E9 7204 CB8C ---------------------------------------------------------------------

2 2

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

sieve vacation: write to the .lda-dupes database without generating a vacation response.
by Bradley M. Kuhn 20 Apr '16

20 Apr '16

I'm using Dovecot's sieve extensions quite happily, they are very good! Thanks for all who worked on them. I have a question that maybe is appropriate for a sieve-specific discussion list, so if there is one I should post to instead, please let me know: I've poked through the sieve vacation RFC and all the documentation I can find and I cannot figure out how to do this. It's more-or-less not the intent of sieve's vacation, so perhaps it's more of a "you can't get there from here" situation, but maybe folks here have an idea: I am (ab)?using sieve vacation to send an automated response at all times to all senders who put me in the To line, every 90 days, which explains my lack of responsiveness and to explain who else might be better contact. (I have hundreds of emails sent to me to which I will never have time to respond, and probably should have been routed to someone else at my organization anyway.) However, I *don't* want my regular correspondents to receive this autoreply. I'd thus like to seed the database with known individuals I'm corresponding with to pretend they've already received the autoresponder. Since I bcc an archive address on all emails, my original thought was to detect people in the To and Cc line of outgoing emails and record them in the .lda-dupes database, as they received a vacation email. I can't figure out how to do this; there is no option on the sieve vacation directive that I can find to do something like this (i.e., I'm looking for a a "do the usual, but *don't* actually send the the email" option on the sieve vacation directive). I do have various other solutions that help in this regard, for example, I never send a vacation email to messages that match: header :contains "In-Reply-To" "@example.org" (where example.org is my domain). This helps, but obviously doesn't handle the situation where the correspondent doesn't reply to one of my emails, or had a stupid MUA. Furthermore, I'd like to implement as many methods as possible for my regular corespondents to limit their receipt of the autoresponder. Any ideas? Thanks in advance for any help or advice you can give! -- -- bkuhn ======================================================================== Become a Conservancy Supporter today: https://sfconservancy.org/supporter

4 4

[Dovecot] Patch: 2.0 support for URLAUTH, BURL, CATENATE
by Mike Abbott 18 Apr '16

18 Apr '16

Thank you Timo for beginning the port of URLAUTH, BURL, and CATENATE from 1.2 to 2.0. Attached please find two patches that finish the port to 2.0. One patch updates the dovecot-2.0-urlauth branch and is based on the tip of that branch. The other patch adds the full support to dovecot-2.0.beta5. The resulting URLAUTH/BURL/CATENATE code is the same. Please let me know if you have any questions about these patches. Thanks.

4 9

stats: Error: FIFO input error: CONNECT: Duplicate session ID
by Urban Loesch 18 Apr '16

18 Apr '16

Hi, yesterday I updatet to Dovecot EE version 2:2.2.23.1-1. Now sometimes I see this errors in my logs: ... Apr 18 09:02:19 dovecot1 dovecot: stats: Error: FIFO input error: CONNECT: Duplicate session ID NjcCDoSAFFd/KQAAFMUCeg for user user(a)domain1.com service lmtp Apr 18 09:04:05 dovecot1 dovecot: stats: Error: FIFO input error: CONNECT: Duplicate session ID rjV1HtCGFFcoogAAFMUCeg for user user(a)domain2.com service lmtp Apr 18 09:04:30 dovecot1 dovecot: stats: Error: FIFO input error: CONNECT: Duplicate session ID Sqi0IMWAFFeRNQAAFMUCeg for user user(a)domain3.com service lmtp ... The error only appears when a mail is sent to 2 ore more recipients concurrently. It's not ciritcal for me, all mails are getting delivered correctly. Thanks and regards Urban Loesch

2 1

AD LDAP auth shows unknown results
by victorpictor＠mailbox.hu 15 Apr '16

15 Apr '16

Hi List! Been struggling with AD LDAP auth, ldapsearch shows everything fine, but when I try to telnet, the log shows unknown attributes. Dovecot 2.0.19 dovecot -n: # 2.0.19: /etc/dovecot/dovecot.conf # OS: Linux 3.5.0-23-generic x86_64 Ubuntu 12.04.5 LTS ext4 auth_debug = yes auth_mechanisms = plain login auth_username_format = %n auth_verbose = yes disable_plaintext_auth = no listen = * mail_location = maildir:/var/mail/%u%d/Maildir namespace inbox { inbox = yes location = prefix = } passdb { args = /etc/dovecot/dovecot-ldap-passdb.conf driver = ldap } plugin { sieve = ~/.dovecot.sieve sieve_dir = ~/sieve sieve_global_dir = /var/lib/dovecot/sieve/ } protocols = " imap lmtp pop3" service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } user = vmail } ssl = no ssl_cert = </etc/ssl/certs/dovecot.pem ssl_key = </etc/ssl/private/dovecot.pem userdb { args = /etc/dovecot/dovecot-ldap-userdb.conf driver = ldap } protocol lmtp { mail_plugins = " sieve" postmaster_address = postmaster(a)domain.hu } Contents of passdb.conf: hosts = 1.2.3.4 auth_bind = yes auth_bind_userdn = DOMAIN\%u ldap_version = 3 base = dc=domain,dc=in scope = subtree deref = never pass_filter = (&(objectClass=person)(sAMAccountName=%u)(mail=*)) Contents of userdb.conf: hosts = 1.2.3.4 dn = DOMAIN\user dnpass = xxx ldap_version = 3 base = dc=domain,dc=in user_attrs = =uid=108,=gid=115,=home=/var/mail/%Lu,=mail=maildir:/var/mail/%Lu/Maildir/ user_filter = (&(objectClass=person)(sAMAccountName=%u)(mail=*)) # Attributes and filter to get a list of all users iterate_attrs = sAMAccountName=user iterate_filter = (objectClass=person) And the log after a test login: Apr 15 18:10:52 ubuntutest2 dovecot: auth: Debug: ldap(user,127.0.0.1): user search: base=dc=domain,dc=in scope=subtree filter=(&(objectClass=person)(sAMAccountName=user)(mail=*)) fields= Apr 15 18:10:52 ubuntutest2 dovecot: auth: Debug: ldap(user,127.0.0.1): result: objectClass(?unknown?)= cn(?unknown?)= instanceType(?unknown?)= whenCreated(?unknown?)= uSNCreated(?unknown?)= name(?unknown?)= objectGUID(?unknown?)= badPwdCount(?unknown?)= codePage(?unknown?)= countryCode(?unknown?)= badPasswordTime(?unknown?)= lastLogoff(?unknown?)= lastLogon(?unknown?)= primaryGroupID(?unknown?)= objectSid(?unknown?)= accountExpires(?unknown?)= logonCount(?unknown?)= sAMAccountName(?unknown?)= sAMAccountType(?unknown?)= userPrincipalName(?unknown?)= objectCategory(?unknown?)= givenName(?unknown?)= initials(?unknown?)= sn(?unknown?)= displayName(?unknown?)= description(?unknown?)= physicalDeliveryOfficeName(?unknown?)= userAccountControl(?unknown?)= msDS-SupportedEncryptionTypes(?unknown?)= pwdLastSet(?unknown?)= homeDrive(?unknown?)= homeDirectory(?unknown?)= memberOf(?unknown?)= mail(?unknown?)= whenChanged(?unknown?)= uSNChanged(?unknown?)= distinguishedName(?unknown?)= Any idea? Thanks for advance! Victorpictor

1 0

Tighten TLS - usage of specific ssl_ec-curve
by Martin 15 Apr '16

15 Apr '16

Hi folks, at first: thanks very much for the great piece of software! I have a proposal to tighten the TLS security: enable the usage of a specific ec-curve in the 10-ssl.conf, e.g. ssl_ec-curve = secp384r1 Reason: I use a 384 bit EC server key, but dovecot uses "only" a prime256v1 curve. Keygen was: f=dovecot; openssl ecparam -name secp384r1 -genkey -out $f.key openssl req -new -x509 -key $f.key -out ${f}.crt -days 2000 -sha512 Server check gives: prio ciphersuite protocols pfs curves 1 ECDHE-ECDSA-AES128-GCM-SHA256 TLSv1.2 ECDH,P-256,256bits prime256v1 2 ECDHE-ECDSA-AES128-SHA256 TLSv1.2 ECDH,P-256,256bits prime256v1 3 ECDHE-ECDSA-AES128-SHA TLSv1.2 ECDH,P-256,256bits prime256v1 4 ECDHE-ECDSA-AES256-GCM-SHA384 TLSv1.2 ECDH,P-256,256bits prime256v1 5 ECDHE-ECDSA-AES256-SHA384 TLSv1.2 ECDH,P-256,256bits prime256v1 6 ECDHE-ECDSA-AES256-SHA TLSv1.2 ECDH,P-256,256bits prime256v1 Certificate: UNTRUSTED, 384 bit, ecdsa-with-SHA512 signature $ sudo nano /etc/dovecot/conf.d/10-ssl.conf ssl = required ssl_protocols = !SSlv2 !SSLv3 TLSv1.2 ssl_cipher_list = EECDH+AES128+AESGCM:EECDH+AES256+AESGCM:EECDH+AES128+SHA256:EECDH+AES256+SHA384:EECDH+AES128+SHA:EECDH+AES256+SHA ssl_prefer_server_ciphers = yes ssl_key = </etc/dovecot/dovecot.key ssl_cert = </etc/dovecot/dovecot.crt OS is arch linux. Thanks very much, Martin

2 1

How to filter spam with same to: and from: adress
by Claude 14 Apr '16

14 Apr '16

Is it possible to create a filter somewhere to delete email that have same to: and from: adress. All these email are forged using my domain name with always different fictif user name. The only common point is that they have the same user name in the from: and to: adress Claude Gelinas agr. Phyto Ressources Inc.

2 1

A few new Pigeonhole features
by Stephan Bosch 14 Apr '16

14 Apr '16

Hi, A few new Pigeonhole features that enthusiasts can experiment with: - Recently, I implemented support for the "imapsieve" extension in Sieve and its IMAP counterpart (https://tools.ietf.org/html/rfc6785) This is now in the Pigeonhole master branch. This allows running Sieve scripts at IMAP activity, rather than at delivery. There are also facilities for the familiar sieve_before/sieve_after administrator scripts. The documentation is currently only in the sources and not on the wiki: https://raw.githubusercontent.com/dovecot/pigeonhole/master/doc/plugins/ima… - Yesterday, I implemented online trace debugging for Sieve scripts: i.e., directly during delivery rather than only using the sieve-test tool. This is also supported for the IMAPSIEVE feature discussed above. This is documented in the INSTALL file: https://github.com/dovecot/pigeonhole/blob/master/INSTALL#L522 In other news, I started a specification for a new Sieve feature that allows using the IMAP SPECIAL-USE attributes from Sieve scripts: https://tools.ietf.org/html/draft-bosch-sieve-special-use-00 There is no implementation yet. Any comments, suggestions or bug reports are welcome. Regards, Stephan.

2 4

Dovecot and Windows Live Mail 2012?
by David Mehler 14 Apr '16

14 Apr '16

Hello, I hope someone has this working, because I'm pulling my hair out at this one. I'm using well for this it's a win7 x64 machine running Windows Essentials 2012 and using the Windows Live mail component. I am trying to connect to my Dovecot server running 2.23 I believe. I keep getting the error "the imap command could not be sent to the server because of a non-network error" googling showed many with this, but no fix. In this account I'm trying to access port 143 which uses starttls. In Mail I've got the boxes for require a secure connection and authentication checked. I should note of course and with no surprise that Mail works oh just fine with the Hotmail account I've also got configured, it's only with the downloading of folders and sending of email to the dovecot server that mail has the issue. Please let me know if I can provide any additional information. Help appreciated. Thanks. Dave.

3 3

Best way to only replicate specific users
by Max 14 Apr '16

14 Apr '16

Hi, I was wondering about the best way to achieve this. Currently, the users I don't want replicated do not exist on the target system. The source tries to sync them but runs into an error. Technically, that works for me, but it doesn't seem like the right way to do it and clutters the log. Kind Regards, Max

1 0

antispam plugin, pipe backend, how to make it work?
by Johannes Rohr 13 Apr '16

13 Apr '16

Hi, my setup is a dovecot 2.0.19 IMAP server on Ubuntu Precise with the antispam plugin in version 2.0+20120225-2 and spamassassin at version 3.2.2 I have been trying and failed to get the pipe backend of the antispam plugin to work. Spamassin by itself works, a manual call of sa-learn works fine. Bayes data is stored in a mysql DB. I have the following configuration in /etc/dovecot/conf.d/90-plugin.conf plugin { #setting_name = value sieve=~/.dovecot.sieve sieve_dir=~/sieve antispam_pipe_program_spam_arg = --spam antispam_pipe_program_notspam_arg = --ham antispam_pipe_program = /usr/local/bin/sa-learn-pipe.sh antispam_pipe_program_args = --username=%u # % expansion done by dovecot antispam_trash = trash;Trash;Deleted Items;Deleted Messages antispam_spam = SPAM;Junk antispam_backend = pipe antispam_verbose_debug = 1 antispam_debug_target = syslog antispam_pipe_tmpdir = /tmp } I have tried the following wrapper script: #!/bin/bash # set -x LOGFILE=/tmp/sa-learn-pipe.log echo "$$-start ($*)" >> $LOGFILE #echo $* > /tmp/sendmail-parms.txt cat<&0 >> /tmp/sendmail-msg-$$.txt /usr/bin/sa-learn $* -D /tmp/sendmail-msg-$$.txt >> $LOGFILE 2>&1 && \ rm -f /tmp/sendmail-msg-$$.txt echo "$$-end" >> $LOGFILE exit 0 It somehow isn't working. I can call the wrapper script manually e.g. sudo -u vmail /usr/local/bin/sa-learn-pipe.sh --username=some(a)mail.user --ham \ < someham But it doesn't work from dovecot. It seems the script is called. but no new patterns show up in the bayes DB. Unfortunately, the plugin seems to be documented poorly. How does it call the programme it pipes to? Is it something like $programme --par1 --par2 < message ? Why can't / shouldn't I call sa-learn directly? All the instructions I found on the in internet contained a wrapper script, but none bothered to explain why you would actually need it. I would be very grateful, if someone could enlighten me on that... Cheers, Johannes

6 16

v2.2.23 released
by Timo Sirainen 13 Apr '16

13 Apr '16

http://dovecot.org/releases/2.2/dovecot-2.2.23.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.23.tar.gz.sig This is a bugfix-only release with various important fixes on top of v2.2.22. - Various fixes to doveadm. Especially running commands via doveadm-server was broken. - director: Fixed user weakness getting stuck in some situations - director: Fixed a situation where directors keep re-sending different states to each others and never becoming synced. - director: Fixed assert-crash related to a slow "user killed" reply - Fixed assert-crash related to istream-concat, which could have been triggered at least by a Sieve script.

6 6