- dovecot - dovecot.org

Re: Compiling Dovecot on Solaris 10
by Joseph Tam 03 Feb '17

03 Feb '17

> I don't have problems building 2.2.27 on Solaris 10 > (using Sun Workshop compiler 5.11). ... and I don't have problems with Solaris10/gcc, but I don't have as many options as you do. Joseph Tam <jtam.home(a)gmail.com>

1 0

Crash while reading compressed mbox: Panic: file istream-zlib.c: line 416 (i_stream_zlib_seek): assertion failed: (ret == -1)
by Anton Yuzhaninov 03 Feb '17

03 Feb '17

Hello, I use mbox compressed by gzip as read-only folder (using zlib plugin). This setup worked for a while, but doesn't work with latest dovecot version (2.2.27). I have error in logs: Panic: file istream-zlib.c: line 416 (i_stream_zlib_seek): assertion failed: (ret == -1) I can see list of messages in MUA but can't ready body of any message. I've tried to delete indexes, but it doesn't help. Backtrace looks like: (gdb) bt #0 0x0000000011266a4a in thr_kill () from /lib/libc.so.7 #1 0x0000000011266a1b in raise () from /lib/libc.so.7 #2 0x0000000011266989 in abort () from /lib/libc.so.7 #3 0x0000000010ef3850 in default_fatal_finish (type=LOG_TYPE_PANIC, status=0) at failures.c:201 #4 0x0000000010ef5167 in i_internal_fatal_handler (ctx=0x7fffffffe010, format=0x1222cf93 "file %s: line %d (%s): assertion failed: (%s)", args=0x7fffffffdff0) at failures.c:670 #5 0x0000000010ef3e5f in i_panic (format=0x1222cf93 "file %s: line %d (%s): assertion failed: (%s)") at failures.c:275 #6 0x0000000012229238 in i_stream_zlib_seek (stream=0x118dd300, v_offset=56248, mark=false) at istream-zlib.c:416 #7 0x0000000010f05e48 in i_stream_skip (stream=0x118dd370, count=32489) at istream.c:278 #8 0x0000000010f057ba in i_stream_seek (stream=0x118dd370, v_offset=56248) at istream.c:300 #9 0x0000000010b17702 in istream_raw_mbox_get_body_size (stream=0x118ec870, expected_body_size=36695, body_size_r=0x7fffffffe2a0) at istream-raw-mbox.c:612 #10 0x0000000010b2b0aa in mbox_sync_read_next_mail (sync_ctx=0x7fffffffe418, mail_ctx=0x7fffffffe270) at mbox-sync.c:162 #11 0x0000000010b2964a in mbox_sync_loop (sync_ctx=0x7fffffffe418, mail_ctx=0x7fffffffe270, partial=false) at mbox-sync.c:1057 #12 0x0000000010b290cb in mbox_sync_do (sync_ctx=0x7fffffffe418, flags=MBOX_SYNC_UNDIRTY) at mbox-sync.c:1642 #13 0x0000000010b28999 in mbox_sync_int (mbox=0x118ee040, flags=MBOX_SYNC_UNDIRTY, lock_id=0x7fffffffe640) at mbox-sync.c:1969 #14 0x0000000010b280ea in mbox_sync (mbox=0x118ee040, flags=MBOX_SYNC_UNDIRTY) at mbox-sync.c:2022 #15 0x0000000010b28c9e in mbox_storage_sync_init (box=0x118ee040, flags=65) at mbox-sync.c:2071 #16 0x0000000010acc280 in mailbox_sync_init (box=0x118ee040, flags=65) at mail-storage.c:1740 #17 0x0000000010acb45d in mailbox_sync (box=0x118ee040, flags=65) at mail-storage.c:1788 #18 0x0000000000418cf5 in select_open (ctx=0x1184a1a8, mailbox=0x11816f50 "old/Example/INBOX.gz", readonly=false) at cmd-select.c:303 #19 0x0000000000418937 in cmd_select_full (cmd=0x1184a040, readonly=false) at cmd-select.c:426 #20 0x00000000004190f7 in cmd_select (cmd=0x1184a040) at cmd-select.c:435 #21 0x0000000000423b00 in command_exec (cmd=0x1184a040) at imap-commands.c:181 #22 0x00000000004220c0 in client_command_input (cmd=0x1184a040) at imap-client.c:986 -- Best Regards, Anton Yuzhaninov

1 0

Revision-proof archiving
by Paul Atreides 03 Feb '17

03 Feb '17

Hi, I am interested in the "Dovecot Email Archive" solution. Does anyone know if it is suitable revision-proof archiving? Is it available for smaller companies? I tried to contact people at dovecot.fi but I haven’t gotten any response yet. Thanks Regards,

2 1

dsync backup public namespace - how?
by Tobias Kirchhofer 03 Feb '17

03 Feb '17

Hello, We just celebrated the launch of our new mailserver setup (Dovecot and Postfix). Really nice! Now we want to change our quickfix backup with rsync to dsync. For mailder backup of users this was an easy task: dsync -v -f -u "${user}" backup "maildir:${destination}" (local file path destination) We use many public folder with ACL and now we are wondering how we can backup these folder in a similar manner: a) dsync -u doveadm(a)domain.com backup -n Namespacename "maildir:/var/vmail-backup/backup/public" or b) dsync -v -u doveadm(a)domain.com -N backup "maildir:${destination} But this is not working. a) does nothing, no error b) Error message: doveadm(doveadm(a)domain.com): Fatal: -N parameter requires syncing with remote host Any ideas? # dovecot --version 2.2.13 -- Tobias Kirchhofer tobias(a)kirchhofer.net

1 0

Dovecot auth-worker error after cram-md5 auth
by Poliman - Serwis 03 Feb '17

03 Feb '17

I set up cram-md5 using this tutorial https://wiki2.dovecot.org/HowTo/CRAM-MD5 in /etc/dovecot/dovecot.conf in passdb code block: listen = *,[::] protocols = imap pop3 #auth_mechanisms = plain login cram-md5 auth_mechanisms = cram-md5 plain login #dodana nizej linia ssl = required disable_plaintext_auth = yes log_timestamp = "%Y-%m-%d %H:%M:%S " mail_privileged_group = vmail postmaster_address = postmaster(a)vps342401.ovh.net ssl_cert = </etc/postfix/smtpd.cert ssl_key = </etc/postfix/smtpd.key ssl_protocols = !SSLv2 !SSLv3 !TLSv1 !TLSv1.1 ssl_cipher_list = ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384[image: :D]HE-RSA-AES128-GCM-SHA256[image: :D]HE-DSS-AES$ ssl_prefer_server_ciphers = yes ssl_dh_parameters_length = 2048 mail_max_userip_connections = 100 passdb { # args = /etc/dovecot/dovecot-sql.conf # driver = sql driver = passwd-file args = scheme=cram-md5 /etc/dovecot/cram-md5.pwd } userdb { driver = prefetch } userdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } Of course I created cram-md5.pwd file. All mails go out and come nicely. But after I want to do default settings by commented out these two lines: driver = passwd-file args = scheme=cram-md5 /etc/dovecot/cram-md5.pwd and uncomment # args = /etc/dovecot/dovecot-sql.conf # driver = sql I can't send emails - I use Thunderbird - get error "logging on server mail.example.com not work out". Error in logs: dovecot: auth-worker(22698): Error: Auth worker sees different passdbs/userdbs than auth server. dovecot: auth: Error: read(anvil-auth-penalty) failed: EOF Is it possible that hashed password from cram-md5.pwd file was written to database (if yes then where - I have ISPconfig)? I wasn't change any userdb {} block and this second userdb block has this same lines like default settings in passdb block. -- *Pozdrawiam / Best Regards* *Piotr Bracha* *tel. 534 555 877* *serwis(a)poliman.pl <serwis(a)poliman.pl>*

4 25

Dovecot dsync 'ssl_client_ca'
by Thierry 03 Feb '17

03 Feb '17

Hello, Still working with my dsync pb. I have done a clone (vmware) of my email server. Today I have two strictly identical emails servers (server1 (main) and server2 (bck) (except IP, hostname and mail_replica). The ssl config on my both server: ssl_protocols = !SSLv2 !SSLv3 ssl = required verbose_ssl = no ssl_key = </etc/ssl/private/private.key ssl_cert = </etc/ssl/certs/key.crt ssl_ca = </etc/ssl/certs/GandiStandardSSLCA2.pem This config is working for my email client and my email web interface ... Are they on the right order ? mail_replica = tcps:server1@domain.ltd and tcps:server2@domain.ltd There is trafic on my iptables rules on my both servers: 60 3600 ACCEPT tcp -- * * 0.0.0.0/0 0.0.0.0/0 tcp dpt:4711 My error message from server1 (main server): Feb 03 08:38:08 doveadm(user1(a)domain.ltd): Error: sync: Couldn't initialize SSL context: Can't verify remote server certs without trusted CAs (ssl_client_ca_* settings) Feb 03 08:42:35 doveadm(user2(a)domain.ltd): Error: sync: Couldn't initialize SSL context: Can't verify remote server certs without trusted CAs (ssl_client_ca_* settings) Feb 03 08:42:35 doveadm(user3(a)domain.ltd): Error: sync: Couldn't initialize SSL context: Can't verify remote server certs without trusted CAs (ssl_client_ca_* settings) Feb 03 08:42:35 doveadm(user4(a)domain.ltd): Error: sync: Couldn't initialize SSL context: Can't verify remote server certs without trusted CAs (ssl_client_ca_* settings) No logs from server2 Any ideas ? Thx for your support -- Cordialement, Thierry e-mail : lenaigst(a)maelenn.org PGP Key: 0xB7E3B9CD

3 4

Re: Dovecot performance and proxy loops with IPv6
by Daniel Betz 03 Feb '17

03 Feb '17

Ok, got it. change imap-login and pop-login to these like showed in dovocot wiki for high-performance login mode. service imap-login { chroot = login service_count = 0 client_limit = 600 process_limit = 100 process_min_avail = 16 } service pop3-login { chroot = login service_count = 0 client_limit = 600 process_limit = 100 process_min_avail = 16 }

1 0

postfix/smtpd[725]: fatal: no SASL authentication mechanisms
by Poliman - Serwis 03 Feb '17

03 Feb '17

I haven't doveadm logs in /var/log/. Are they default in another place or maybe should I turn on something? My config (default passdb block and auth_mechanisms, nothing more changed): root@vps342401:/etc/dovecot# doveconf -n # 2.2.9: /etc/dovecot/dovecot.conf # OS: Linux 3.13.0-100-generic x86_64 Ubuntu 14.04.5 LTS auth_mechanisms = plain login listen = *,[::] log_timestamp = "%Y-%m-%d %H:%M:%S " mail_max_userip_connections = 100 mail_plugins = " quota" mail_privileged_group = vmail passdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } plugin { quota = dict:user::file:/var/vmail/%d/%n/.quotausage sieve = /var/vmail/%d/%n/.sieve sieve_max_redirects = 25 } postmaster_address = postmaster(a)vps342401.ovh.net protocols = imap pop3 service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-userdb { group = vmail mode = 0600 user = vmail } user = root } service imap-login { client_limit = 1000 process_limit = 512 } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } ssl = required ssl_cert = </etc/postfix/smtpd.cert ssl_cipher_list = ECDHE-RSA-AES128-GCM-SHA256:EC DHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDH E-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS- AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE- ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128- SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE- RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128- SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA- AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:AES128- GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256: AES128-SHA:AES256-SHA:AES:CAMELLIA:DES-CBC3-SHA:!aNULL:! eNULL:!EXPORT:!DES:!RC4:!MD5:!PSK:!aECDH:!EDH-DSS-DES-CBC3- SHA:!EDH-RSA-DES-CBC3-SHA:!KRB5-DES-CBC3-SHA ssl_dh_parameters_length = 2048 ssl_key = </etc/postfix/smtpd.key ssl_prefer_server_ciphers = yes ssl_protocols = !SSLv2 !SSLv3 !TLSv1 !TLSv1.1 userdb { driver = prefetch } userdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } protocol imap { mail_plugins = quota imap_quota } protocol pop3 { mail_plugins = quota pop3_uidl_format = %08Xu%08Xv } protocol lda { mail_plugins = sieve quota postmaster_address = webmaster@localhost } protocol lmtp { mail_plugins = quota sieve postmaster_address = webmaster@localhost } And my logs: Error from mail.err: Feb 1 09:50:01 vps342401 postfix/smtpd[699]: fatal: no SASL authentication mechanisms Feb 1 09:51:02 vps342401 postfix/smtpd[724]: fatal: no SASL authentication mechanisms Feb 1 09:51:02 vps342401 postfix/smtpd[725]: fatal: no SASL authentication mechanisms Feb 1 09:52:21 vps342401 postfix/smtps/smtpd[773]: fatal: no SASL authentication mechanisms Error from syslog: Feb 1 09:52:21 vps342401 postfix/smtps/smtpd[773]: connect from host9323131.internet.3s.com[12.34.45.56] Feb 1 09:52:21 vps342401 postfix/smtps/smtpd[773]: fatal: no SASL authentication mechanisms Feb 1 09:52:22 vps342401 postfix/master[29133]: warning: process /usr/lib/postfix/smtpd pid 773 exit status 1 Feb 1 09:52:22 vps342401 postfix/master[29133]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling Feb 1 09:53:01 vps342401 CRON[777]: (root) CMD (/usr/local/ispconfig/server/server.sh 2>&1 | while read line; do echo `/bin/date` "$line" >> /var/log/ispconfig/cron.log; do ne) Feb 1 09:53:01 vps342401 CRON[778]: (root) CMD (/usr/local/ispconfig/server/cron.sh 2>&1 | while read line; do echo `/bin/date` "$line" >> /var/log/ispconfig/cron.log; done ) Is there any strange thing in these config lines? -- *Pozdrawiam / Best Regards* *Piotr Bracha* *tel. 534 555 877* *serwis(a)poliman.pl <serwis(a)poliman.pl>*

1 0

Dovecot, Postfix, and SASL AUTH EXTERNAL
by Matt Horan 03 Feb '17

03 Feb '17

Hey folks, I've been using the ever popular Dovecot and Postfix combo for years. A while back I also introduced mutual TLS for mail clients to Dovecot and Postfix. I achieved this by a custom checkpassword script and SASL AUTH EXTERNAL for IMAP. This all worked great with clients like Thunderbird, which can be configured to use mutual TLS and SASL EXTERNAL for IMAP, and mutual TLS with no additional authentication for SMTP. However, I found that other mail clients, in particular K-9 mail on Android, [1] are not compatible with this configuration. I've been patching K-9 mail to work around this issue for some time now. If I configure K-9 to behave like Thunderbird when sending messages via SMTP, all is well. However, there's been some activity on an issue [2] which suggests some changes may be upcoming which will be incompatible with my patch. Without my patch, K-9 tries to auth with Postfix via AUTH EXTERNAL after presenting its client certificate. Despite configuring Postfix to prefer certificates before SASL, Postfix forwards the authentication request to Dovecot, which rejects it without even trying my checkpassword script. With my patch, K-9 simply initiates an SMTP connection without any additional authentication when mutual TLS is used. This behavior is similar to Thunderbird. The K-9 maintainers do not seem interested in merging this behavior into mainline. I can't seem to get Postfix to ignore the SASL failures in the case of successful mutual TLS. I want to use SASL authentication as a fallback from untrusted clients, where I use a combination of password and one time code. Even if Dovecot did not reject the AUTH EXTERNAL request from Postfix, I'm not sure how it could determine whether a valid client certificate were presented to Postfix, unless some additional information were passed along in the SASL request. I'd love to hear any thoughts from the community on how to move forward here. Should I pressure the K-9 maintainers to behave more like other clients? Would it make sense to extend the SASL interface in some way such that Dovecot could handle an EXTERNAL request from Postfix? Or should Postfix simply ignore SASL EXTERNAL based on the configured authentication mechanism order? Thanks, Matt [1] https://github.com/k9mail/k-9/ [2] https://github.com/k9mail/k-9/issues/793 -- Matt Horan matt(a)matthoran.com http://matthoran.com/

1 0

Moving to new password scheme
by ＠lbutlr 02 Feb '17

02 Feb '17

dovecot is setup on a system with MD5-CRYPT password scheme for all users, and I would like to update this to something that is secure, probably SSHA256-CRYPT, but I want to do this seamlessly without the users having to jump through any hoops. The users are in mySQL (managed via postfixadmin) and the mailbox record simply stores the hash in the password field. Users access their accounts though IMAP MUAs or Roundcube. How would I setup my system so that if a user logs in and still has a $1$ password (MD5-CRYPT) their password will be encoded to the new SHCEME and then the SQL row updated with the $5$ password instead? Something where they are redirected after authentication to a page that forces them to renter their password (or choose a new one) is acceptable. And, while I am here, is it worthwhile to set the -r flag to a large number (like something over 100,000 which sets takes about 0.25 seconds to do on my machine)? -- Apple broke AppleScripting signatures in Mail.app, so no random signatures.

4 8