- dovecot - dovecot.org

Compilation fails: SSL_TXT_SSLV2 not defined
by Muffinman 07 Mar '16

07 Mar '16

Hello all, I'm trying to compile dovecot 2.2.21 on OS-X 10.11.3 and I'm running a bit of trouble with OpenSSL. I've cloned OpenSSL (OpenSSL 1.1.0-pre4-dev) from github and in openssl/ssl.h SSL_TXT_SSLV2 is not defined anymore. Compilation fails with: libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -I../../src/lib -I../../src/lib-test -DMODULE_DIR=\"/usr/local/lib/dovecot\" -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -Wno-duplicate-decl-specifier -Wstrict-aliasing=2 -MT iostream-openssl-common.lo -MD -MP -MF .deps/iostream-openssl-common.Tpo -c iostream-openssl-common.c -fno-common -DPIC -o .libs/iostream-openssl-common.o iostream-openssl-common.c:34:24: error: use of undeclared identifier 'SSL_TXT_SSLV2' if (strcasecmp(name, SSL_TXT_SSLV2) == 0) ^ 1 error generated. make[3]: *** [iostream-openssl-common.lo] Error 1 make[2]: *** [all-recursive] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2 In openssl/ssl.h the following is defined: # define SSL_TXT_SSLV3 "SSLv3" # define SSL_TXT_TLSV1 "TLSv1" # define SSL_TXT_TLSV1_1 "TLSv1.1" # define SSL_TXT_TLSV1_2 "TLSv1.2" # define SSL_TXT_ALL "ALL" Any suggestions on how to fix this? Kind regards, Maarten

2 3

questions regarding zlib plugin
by Götz Reinicke - IT Koordinator 07 Mar '16

07 Mar '16

Hi, faced with a current space problem on our dovecot 2.2.18 server, I thought about using the zlib plugin. My questions: - is it really as simple as adding the options to the conf files as described in the docs :) ? http://wiki2.dovecot.org/Plugins/Zlib - As this just compresses new messages; dose anybody has a sort of simple cron or whatever script or best practice how to compress existing maildir mails? The doc is a bit complicated to me at that point... Thanks a lot and regards . Götz

3 3

Ubuntu packages
by Peter Chiochetti 07 Mar '16

07 Mar '16

Since dovecot put up packages on their own repo, bigmichi stopped providing his'. I guess this is not Stephan; Would the kind person update ppa.launchpad.net/bigmichi1 ? Thank You -- peter

11 18

VS: Re: v2.2.22 release candidate released
by Aki Tuomi 06 Mar '16

06 Mar '16

In future release we will add master authentication too. Now you can use api key or doveadm password which are essentially same thing. ---Aki TuomiDovecot oy-------- Alkuperäinen viesti --------Lähettäjä: Peter Chiochetti <pch(a)myzel.net> Päivämäärä: 4.3.2016 20.20 (GMT+02:00) Saaja: dovecot(a)dovecot.org Aihe: Re: v2.2.22 release candidate released Am 2016-03-04 um 14:33 schrieb Timo Sirainen: > + Added doveadm HTTP API: See > http://wiki2.dovecot.org/Design/DoveadmProtocol/HTTP Hmm, so anybody who has the API key can send any doveadm commands? I guess something like /etc/sudoers for API keys would be good? Did I miss something? -- peter

3 2

Re: Dovecot stops responding when I update SSL certificate
by Joseph Tam 06 Mar '16

06 Mar '16

HotSlots Webmaster <webmaster(a)hotslots132.com> writes: > I have had Dovecot working fine with SSL for nearly two years now. It's > time to renew the SSL certificate, so I did (same CA). The new > certificate works fine in Apache and Postfix. But when I update Dovecot > to use the same certificate, and restart the server, Dovecot stops > responding to connects. > ... > Here is the end of the dovecot -n file that mentions SSL: > ... > ssl_dh_parameters_length = 2048 When you start dovecot, does CPU load of dovecot/ssl-params roof to 100%? It's possible it's generating ephemeral DH keys. In a previous post to this list, I note that the run time to generate these keys can vary wildly, and gets worse with longer keys. Sometimes you get lucky, and you'll generate then quickly, sometimes it takes a long while (minutes). http://dovecot.org/pipermail/dovecot/2015-November/102447.html Try running openssl dhparam -noout 2048 to see how it varies for you. If what I suspect is true, you can try using shorter keys. A followup post suggest a way you can precompute the key Joseph Tam <jtam.home(a)gmail.com>

3 2

VS: Re: Implementation of TLS OCSP Stapling
by Aki Tuomi 06 Mar '16

06 Mar '16

Luckily ocsp stapling is an SSL extension and clients not supporting it won't be asking for it either. ---Aki TuomiDovecot oy -------- Alkuperäinen viesti --------Lähettäjä: Andrew McGlashan <andrew.mcglashan(a)affinityvision.com.au> Päivämäärä: 6.3.2016 10.36 (GMT+02:00) Saaja: dovecot(a)dovecot.org Aihe: Re: Implementation of TLS OCSP Stapling On 3/03/2016 11:58 PM, aki.tuomi(a)dovecot.fi wrote: > We will take this feature under consideration and see if it can be implemented > in future release. Thank you for your suggestion! As much as I hate Outlook (Look Out!), there are loads of people using really old versions; 2003 is no longer supported, but loads of people use 2007. Thunderbird can be expected to be far more up to date. Implementing features to work with older clients will always be a problem. Just a simple example, almost unrelated here, but this is either wrong by TB or wrong by Outlook (versions 2007, 2010 and 2013 that I know of). When the IMAP server sends a message, OL will pop up a window that requires the user to acknowledge the message via a popup. TB just pops up the message in the normal 'new mail' notify if that is configured and it might be lost if notify isn't set to show. Either way, the implementation is different b/w the two client products. Is OL right or is TB right... IMAP doco says that the message should be made to be acknowledged by the client; OL's version can't easily be ignored or missed, but TB's can easily be missed. But TB's implementation is more user friendly if the server wants to keep sending messages from time to time. I considered using this for MOTD type stuff and maybe random inspirational or motivational messages; even to remind or inform users to do certain things [one example in the dovecot wiki is to advise that the vacation message is still active]. A TB notification is next to harmless, but an OL one needs to be acknowledged every time, which would be very painful. Anyway, the point is that if a feature is added for OCSP stabling support, you couldn't really expect older versions of Look Out to comply with it (even though M$ could patch it easily, they care less about older versions than getting people to subscribe to Office 365 these days). Cheers A.

1 0

Implementation of TLS OCSP Stapling
by dovecot＠flut.demon.nl 06 Mar '16

06 Mar '16

Hi all, About a year ago, Torsten already asked for OCSP stapling (http://dovecot.org/pipermail/dovecot/2015-April/100632.html) Unfortunately, there was no answer to his question. Now RFC 7633 ("TLS Feature Extension", https://tools.ietf.org/html/rfc7633, a.k.a. "Must Staple") has landed, revocation is getting serious! I personally would like to embed all my TLS certificates with the must-staple extension. The great project Let's Encrypt already supports it: https://github.com/letsencrypt/boulder/pull/1224 I'm aware most MTAs don't really care about the certificate, but big players as Google take TLS encryption very seriously: https://googleblog.blogspot.nl/2016/02/building-safer-web-for-everyone.html So I would like to know if Dovecot is planning to feature OCSP stapling. That way I know for sure my "must staple" certificates can be used by Dovecot. And in my opinion, every TLS offering daemon should be up to par to the capabilities of TLS.. Not lag behind :) What's your opinion on this matter? Thanks in advance for any anwser! Greets, Osiris

7 11

dovecot local indexes and multiple servers
by alex 05 Mar '16

05 Mar '16

Hi, I've been testing mdbox with local indexes on our nfs based directors + multiple imap/lda/pop3 server setup. The performance is noticeably better than maildir with indexes on nfs, so I'd like to make this work. About the possible direction to other servers the wiki says that it will create a new index 'on the fly'. That is true, but after the index is recreated, Thunderbird (imap) re-downloads all the messages and sees all those messages as unread again! This is probably quite logical as the message status is only kept in the indexes, but this is not very customer friendly. Is there a way to avoid this problem? I'd rather not manually sync those local indexes between our servers. In fact, I was planning on deleting (old) indexes when a user moved to another server or even if they haven't checked their mail for XX days. with up to 10Gb mailboxes the indexes themselves can get up to 20-40Mb for a mailbox. that amounts to quite a lot of storage for 200k+ users. Thanks, Alex.

2 2

VS: Dovecot stops responding when I update SSL certificate
by Aki Tuomi 05 Mar '16

05 Mar '16

Did you change dh parameter size as well? This causes dh generation which can take some time. ---Aki TuomiDovecot oy-------- Alkuperäinen viesti --------Lähettäjä: HotSlots Webmaster <webmaster(a)hotslots132.com> Päivämäärä: 5.3.2016 4.10 (GMT+02:00) Saaja: dovecot(a)dovecot.org Aihe: Dovecot stops responding when I update SSL certificate Dovecot 2.2.18 CentOS 6.7 (x86_64) Plesk 12.5.30 I have had Dovecot working fine with SSL for nearly two years now. It's time to renew the SSL certificate, so I did (same CA). The new certificate works fine in Apache and Postfix. But when I update Dovecot to use the same certificate, and restart the server, Dovecot stops responding to connects. I have triple-checked that the ssl_cert and ssl_key files are correct - all I did was change the names in the conf file. There's nothing in the log. I have tried various SSL tests but either they don't work (unspecific error) or they tell me nothing is wrong (and show the correct certificate.) I am running out of time to find a solution to this - what else can I look for? The one difference for the certificates is that I opted for one with a SHA256 root rather than SHA1 root. I have separately used a tool to verify that the certificate and private key match. Here is the end of the dovecot -n file that mentions SSL: ssl = required ssl_cert = </etc/pki/tls/certs/hotslots-cert.pem ssl_cipher_list = EECDH+AESGCM+AES128:EECDH+AESGCM+AES256:EDH+AESGCM+AES128:EDH+AESGCM+AES256:EECDH+SHA256+AES128:EECDH+SHA384+AES256:EDH+SHA256+AES128:EDH+SHA256+AES256:EECDH+SHA1+AES128:EECDH+SHA1+AES256:EDH+SHA1+AES128:EDH+SHA1+AES256:EECDH+HIGH:EDH+HIGH:AESGCM+AES128:AESGCM+AES256:SHA256+AES128:SHA256+AES256:SHA1+AES128:SHA1+AES256:HIGH:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!MD5:!PSK:!KRB5:!aECDH:!EDH+3DES ssl_dh_parameters_length = 2048 ssl_key = </etc/ssl/private/hotslots-private.pem ssl_protocols = TLSv1.1 TLSv1.2 !TLSv1 userdb { args = uid=popuser gid=popuser driver = static } protocol imap { mail_plugins = " quota imap_quota" } protocol pop3 { pop3_uidl_format = UID%u-%v } protocol lda { mail_plugins = " quota sieve" } (The !TLSv1 doesn't seem to be honored - I tried it with and without that. A problem for later.) Thanks for any help. Steve L

1 0

Dovecot stops responding when I update SSL certificate
by HotSlots Webmaster 05 Mar '16

05 Mar '16

Dovecot 2.2.18 CentOS 6.7 (x86_64) Plesk 12.5.30 I have had Dovecot working fine with SSL for nearly two years now. It's time to renew the SSL certificate, so I did (same CA). The new certificate works fine in Apache and Postfix. But when I update Dovecot to use the same certificate, and restart the server, Dovecot stops responding to connects. I have triple-checked that the ssl_cert and ssl_key files are correct - all I did was change the names in the conf file. There's nothing in the log. I have tried various SSL tests but either they don't work (unspecific error) or they tell me nothing is wrong (and show the correct certificate.) I am running out of time to find a solution to this - what else can I look for? The one difference for the certificates is that I opted for one with a SHA256 root rather than SHA1 root. I have separately used a tool to verify that the certificate and private key match. Here is the end of the dovecot -n file that mentions SSL: ssl = required ssl_cert = </etc/pki/tls/certs/hotslots-cert.pem ssl_cipher_list = EECDH+AESGCM+AES128:EECDH+AESGCM+AES256:EDH+AESGCM+AES128:EDH+AESGCM+AES256:EECDH+SHA256+AES128:EECDH+SHA384+AES256:EDH+SHA256+AES128:EDH+SHA256+AES256:EECDH+SHA1+AES128:EECDH+SHA1+AES256:EDH+SHA1+AES128:EDH+SHA1+AES256:EECDH+HIGH:EDH+HIGH:AESGCM+AES128:AESGCM+AES256:SHA256+AES128:SHA256+AES256:SHA1+AES128:SHA1+AES256:HIGH:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!MD5:!PSK:!KRB5:!aECDH:!EDH+3DES ssl_dh_parameters_length = 2048 ssl_key = </etc/ssl/private/hotslots-private.pem ssl_protocols = TLSv1.1 TLSv1.2 !TLSv1 userdb { args = uid=popuser gid=popuser driver = static } protocol imap { mail_plugins = " quota imap_quota" } protocol pop3 { pop3_uidl_format = UID%u-%v } protocol lda { mail_plugins = " quota sieve" } (The !TLSv1 doesn't seem to be honored - I tried it with and without that. A problem for later.) Thanks for any help. Steve L

1 0