February 2017 - dovecot

dovecot/auth CPU spikes
by nicolas＠andrillon.net 05 Feb '17

05 Feb '17

Hi All, I have recently moved by webmail server from a VPS to a hosted dedicated server running Ubuntu 16.04. Everything is fine except that login is particularly and consistently long (around 4-5 seconds). I have noticed that the process dovecot/auth seems to eat all of the resources of one of the cores available on the host during login. The authentication backend is a postgres database which is running absolutely fine. I have been scavenging on the dovecot mailing list for some time but I have not been able to find a solution to my problem so decided to send this bottle to the sea. Here is my config: $ sudo dovecot -n # 2.2.22 (fe789d2): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.13 (7b14904) # OS: Linux 3.14.32-xxxx-grs-ipv6-64 x86_64 Ubuntu 16.04.1 LTS ext4 auth_cache_size = 10 M auth_mechanisms = plain login default_internal_user = vmail first_valid_uid = 0 mail_location = maildir:/home/data/vmail/%d/%n mail_plugins = " fts fts_solr" mail_privileged_group = vmail maildir_stat_dirs = yes 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 inbox { inbox = yes location = mailbox Archive { auto = subscribe special_use = Archive } mailbox Drafts { auto = subscribe special_use = Drafts } mailbox Junk { auto = subscribe special_use = Junk } mailbox Sent { auto = subscribe special_use = Sent } mailbox "Sent Messages" { special_use = Sent } mailbox Trash { auto = subscribe special_use = Trash } prefix = } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { antispam_backend = pipe antispam_mail_notspam = learn_ham antispam_mail_sendmail = /usr/bin/rspamc antispam_mail_sendmail_args = -h;localhost:11334;-P;q1 antispam_mail_spam = learn_spam antispam_spam = Junk antispam_trash = Trash fts = solr fts_solr = break-imap-search url=http://localhost:8080/solr/ sieve = file:~/sieve;active=~/.dovecot.sieve sieve_before = /var/lib/dovecot/sieve.d/ } postmaster_address = postmaster(a)domain.net protocols = imap lmtp sieve pop3 service auth-worker { unix_listener auth-worker { user = vmail } user = vmail } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } unix_listener auth-userdb { group = vmail mode = 0660 user = vmail } user = vmail } service imap-login { inet_listener imap { port = 0 } service_count = 1 } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0666 user = postfix } user = vmail } service pop3-login { inet_listener pop3 { port = 0 } } ssl = required ssl_cert =

1 2

Re: Panic error from dovecot 2.2.27 using libressl 2.4.5 (cross-posting at GitHub)
by Aki Tuomi 05 Feb '17

05 Feb '17

Sorry for finnish. I think it might also work with libtool flag -static in Makefile.am LDADD flags.---Aki TuomiDovecot oy -------- Original message --------From: Aki Tuomi <aki.tuomi(a)dovecot.fi> Date: 05/02/2017 20:21 (GMT+02:00) To: Dovecot Mailing List <dovecot(a)dovecot.org> Subject: Re: Panic error from dovecot 2.2.27 using libressl 2.4.5 (cross-posting at GitHub) jos ldflags laittaa -static vivun niin se preferoi .a filedn linkkausta. ---Aki TuomiDovecot oy -------- Original message --------From: Timo Sirainen <tss(a)iki.fi> Date: 05/02/2017 20:19 (GMT+02:00) To: Dovecot Mailing List <dovecot(a)dovecot.org> Subject: Re: Panic error from dovecot 2.2.27 using libressl 2.4.5 (cross-posting at GitHub) On 5 Feb 2017, at 19.58, Timo Sirainen <tss(a)iki.fi> wrote: > > On 5 Feb 2017, at 19.49, Timo Sirainen <tss(a)iki.fi> wrote: >> >> On 4 Feb 2017, at 20.03, Ruga <ruga(a)protonmail.com> wrote: >>> >>> https://github.com/libressl-portable/portable/issues/278 >> >> I've no idea why that would happen. The only idea I had got rejected by someone. > > Oh, that's with OSX. I think that's the reason. Nothing to do with libressl. I'll see if I can reproduce it, as soon as I can figure out how to get a newer OpenSSL installed to my OSX.. Attached patch seems to work.

1 0

Re: Panic error from dovecot 2.2.27 using libressl 2.4.5 (cross-posting at GitHub)
by Aki Tuomi 05 Feb '17

05 Feb '17

jos ldflags laittaa -static vivun niin se preferoi .a filedn linkkausta. ---Aki TuomiDovecot oy -------- Original message --------From: Timo Sirainen <tss(a)iki.fi> Date: 05/02/2017 20:19 (GMT+02:00) To: Dovecot Mailing List <dovecot(a)dovecot.org> Subject: Re: Panic error from dovecot 2.2.27 using libressl 2.4.5 (cross-posting at GitHub) On 5 Feb 2017, at 19.58, Timo Sirainen <tss(a)iki.fi> wrote: > > On 5 Feb 2017, at 19.49, Timo Sirainen <tss(a)iki.fi> wrote: >> >> On 4 Feb 2017, at 20.03, Ruga <ruga(a)protonmail.com> wrote: >>> >>> https://github.com/libressl-portable/portable/issues/278 >> >> I've no idea why that would happen. The only idea I had got rejected by someone. > > Oh, that's with OSX. I think that's the reason. Nothing to do with libressl. I'll see if I can reproduce it, as soon as I can figure out how to get a newer OpenSSL installed to my OSX.. Attached patch seems to work.

1 0

Panic error from dovecot 2.2.27 using libressl 2.4.5 (cross-posting at GitHub)
by Ruga 05 Feb '17

05 Feb '17

https://github.com/libressl-portable/portable/issues/278

2 3

Dovecot v2.2.22 (fe789d2) starting up for imap, pop3 (core dumps disabled)
by baskar anand 05 Feb '17

05 Feb '17

Always I have the following lines in my mail.log (at startup and service restart) dovecot: master: Warning: Killed with signal 15 (by pid=3156 uid=0 code=kill) dovecot: log: Warning: Killed with signal 15 (by pid=1 uid=0 code=kill) dovecot: master: Dovecot v2.2.22 (fe789d2) starting up for imap, pop3 (core dumps disabled) dovecot -n output is below: # 2.2.22 (fe789d2): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.13 (7b14904) # OS: Linux 4.4.0-31-generic x86_64 Ubuntu 16.04.1 LTS auth_mechanisms = plain login mail_location = mbox:~/mail:INBOX=/var/mail/%u mail_privileged_group = mail 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 { driver = pam } protocols = " imap pop3" service auth-worker { user = root } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } } ssl_cert =

2 1

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