- dovecot - dovecot.org

Allow selection of safe curves in dovecot
by Ruga 26 Aug '16

26 Aug '16

http://safecurves.cr.yp.to

2 1

Change dovecot hostname
by Scott W. Sander 25 Aug '16

25 Aug '16

I have noticed that the name of my private server running dovecot appears in email headers rather than the public-friendly name of my server. Is there a method to specify an alternate server name for the dovecot server to use for itself in the dovecot configuration files? I performed a few Google searches and was not able to find the answer to my question. ------- user@server1:~$ dovecot --version 2.2.9 user@server1:~$ dovecot -n # 2.2.9: /etc/dovecot/dovecot.conf # OS: Linux 3.16.0-77-generic x86_64 Ubuntu 14.04.4 LTS ext4 auth_mechanisms = plain login info_log_path = /var/log/dovecot.log log_path = /var/log/dovecot.log mail_location = maildir:/var/mail/vhosts/%d/%n 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 { args = scheme=PLAIN username_format=%u /etc/dovecot/dovecot-users driver = passwd-file } protocols = " imap lmtp pop3" service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } } service imap-login { inet_listener imaps { port = 993 ssl = yes } } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } service pop3-login { inet_listener pop3s { port = 995 ssl = yes } } ssl = required ssl_cert = </etc/ssl/certs/server1_combined.pem ssl_key = </etc/ssl/private/server1_key.pem userdb { args = uid=vmail gid=vmail home=/var/mail/vhosts/%d/%n driver = static }

3 5

Possible IMAP IDLE bug in Dovecot 2.2.18 and 2.2.25
by cleber-listas＠inetweb.com.br 24 Aug '16

24 Aug '16

Hello Guys, I guess that I found a bug in Dovecot 2.2.18 and 2.2.25 versions. The problem it's when I try to connect in a Dovecot used a proxy to another e-mail server (in our case it's a Smartermail Server) the DoveCot send a lot of IDLE commands to the destination server. With that, the LOG files grow and grow and grow :( I make a test with 1 connection only and if you see the log file in the same second the dovecot send 25, 40 IDLE commands. But, when I disconnect the client (outlook 2013) the dovecot continue to send the IDLE command for some seconds. If I try to connect directly to Smartermail with Outlook this don't occurrs. Bellow the LOG FILE: 16:08:08 [192.168.202.11][21425199] connected at 22/08/2016 16:08:08 16:08:08 [192.168.202.11][21425199] command: C CAPABILITY 16:08:09 [192.168.202.11][21425199] command: L LOGIN "cleber(a)testdomain.com.br" XXXX 16:08:09 [192.168.202.11][21425199] cleber(a)testdomain.com.br logged in 16:08:09 [192.168.202.11][21425199] command: 36mc IDLE 16:08:09 [192.168.202.11][21425199] command: 2x04 ID ("name" "Microsoft Outlook" "version" "15.0.4849.1000") 16:08:09 [192.168.202.11][21425199] response: 2x04 BAD Command does not exist or is not implemented 16:08:09 [192.168.202.11][21425199] command: g4zp LSUB "" "*" 16:08:09 [192.168.202.11][21425199] command: pv81 IDLE 16:08:09 [192.168.202.11][21425199] command: 2it1 SELECT "INBOX" 16:08:09 [192.168.202.11][21425199] response: * 912 EXISTS 16:08:09 [192.168.202.11][21425199] response: * 0 RECENT 16:08:09 [192.168.202.11][21425199] response: * OK [UNSEEN 904] Message 904 is first unseen 16:08:09 [192.168.202.11][21425199] response: * OK [UIDVALIDITY 1] UIDs valid 16:08:09 [192.168.202.11][21425199] response: * OK [UIDNEXT 26830] Predicted next UID 16:08:09 [192.168.202.11][21425199] response: * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) 16:08:09 [192.168.202.11][21425199] response: * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft)] 16:08:09 [192.168.202.11][21425199] response: 2it1 OK [READ-WRITE] SELECT completed 16:08:09 [192.168.202.11][21425199] command: a6tj IDLE 16:08:09 [192.168.202.11][21425199] command: bn09 FETCH 912 (UID) 16:08:09 [192.168.202.11][21425199] command: 78b6 IDLE 16:08:09 [192.168.202.11][21425199] command: q13w UID FETCH 1:26829 (UID FLAGS) 16:08:09 [192.168.202.11][21425199] command: p02s IDLE 16:08:09 [192.168.202.11][21425199] command: 9de9 IDLE 16:08:09 [192.168.202.11][21425199] command: xjyf IDLE 16:08:09 [192.168.202.11][21425199] command: holb IDLE 16:08:09 [192.168.202.11][21425199] command: sfbq IDLE 16:08:09 [192.168.202.11][21425199] command: tuvb IDLE 16:08:09 [192.168.202.11][21425199] command: hv13 IDLE 16:08:09 [192.168.202.11][21425199] command: ctgw IDLE 16:08:09 [192.168.202.11][21425199] command: s00g IDLE 16:08:09 [192.168.202.11][21425199] command: 9zx1 IDLE 16:08:09 [192.168.202.11][21425199] command: dtu2 IDLE 16:08:09 [192.168.202.11][21425199] command: 1brp IDLE 16:08:09 [192.168.202.11][21425199] command: vhds IDLE 16:08:09 [192.168.202.11][21425199] command: cp9s IDLE 16:08:09 [192.168.202.11][21425199] command: hx1b IDLE 16:08:09 [192.168.202.11][21425199] command: 6thy IDLE 16:08:09 [192.168.202.11][21425199] command: 4ert IDLE 16:08:09 [192.168.202.11][21425199] command: cy32 IDLE 16:08:09 [192.168.202.11][21425199] command: z7ku IDLE 16:08:09 [192.168.202.11][21425199] command: xeqd IDLE 16:08:09 [192.168.202.11][21425199] command: gqis IDLE 16:08:09 [192.168.202.11][21425199] command: bdz2 IDLE 16:08:09 [192.168.202.11][21425199] command: zzyq IDLE 16:08:09 [192.168.202.11][21425199] command: 41do IDLE 16:08:09 [192.168.202.11][21425199] command: 7k73 IDLE 16:08:10 [192.168.202.11][21425199] command: 5989 IDLE 16:08:10 [192.168.202.11][21425199] command: lyt4 IDLE 16:08:10 [192.168.202.11][21425199] command: 8ji4 IDLE 16:08:10 [192.168.202.11][21425199] command: pt5b IDLE 16:08:10 [192.168.202.11][21425199] command: ha2s IDLE 16:08:10 [192.168.202.11][21425199] command: ay0x IDLE 16:08:10 [192.168.202.11][21425199] command: t66x IDLE 16:08:10 [192.168.202.11][21425199] command: pf4j IDLE 16:08:10 [192.168.202.11][21425199] command: 2q5x IDLE 16:08:10 [192.168.202.11][21425199] command: wdup IDLE 16:08:10 [192.168.202.11][21425199] command: ii7b IDLE 16:08:10 [192.168.202.11][21425199] command: 2g4k IDLE 16:08:10 [192.168.202.11][21425199] command: lxxg IDLE 16:08:10 [192.168.202.11][21425199] command: vilu IDLE 16:08:10 [192.168.202.11][21425199] command: ms05 IDLE 16:08:10 [192.168.202.11][21425199] command: 8ugb IDLE 16:08:10 [192.168.202.11][21425199] command: 1vfo IDLE 16:08:10 [192.168.202.11][21425199] command: s78s IDLE 16:08:10 [192.168.202.11][21425199] command: 7h2k IDLE 16:08:10 [192.168.202.11][21425199] command: 0het IDLE 16:08:10 [192.168.202.11][21425199] command: rgj7 IDLE 16:08:10 [192.168.202.11][21425199] command: myx3 IDLE 16:08:10 [192.168.202.11][21425199] command: oi5h IDLE 16:08:10 [192.168.202.11][21425199] command: p4mr IDLE 16:08:10 [192.168.202.11][21425199] command: z0dn IDLE 16:08:10 [192.168.202.11][21425199] command: ivj4 IDLE 16:08:10 [192.168.202.11][21425199] command: vxt4 IDLE 16:08:10 [192.168.202.11][21425199] command: mj9c IDLE 16:08:10 [192.168.202.11][21425199] command: 0cf3 IDLE 16:08:10 [192.168.202.11][21425199] command: u215 IDLE 16:08:10 [192.168.202.11][21425199] command: czw6 IDLE 16:08:10 [192.168.202.11][21425199] command: t3nw IDLE 16:08:10 [192.168.202.11][21425199] command: ixmt IDLE 16:08:10 [192.168.202.11][21425199] command: o3qi IDLE 16:08:10 [192.168.202.11][21425199] command: ca1l IDLE 16:08:10 [192.168.202.11][21425199] command: 3r67 IDLE 16:08:10 [192.168.202.11][21425199] command: 8rmq IDLE 16:08:10 [192.168.202.11][21425199] command: yi76 IDLE 16:08:10 [192.168.202.11][21425199] command: 7doe IDLE 16:08:10 [192.168.202.11][21425199] command: 1xzf IDLE 16:08:10 [192.168.202.11][21425199] command: y78i IDLE 16:08:10 [192.168.202.11][21425199] command: 7g2f IDLE 16:08:10 [192.168.202.11][21425199] command: vmvn IDLE 16:08:10 [192.168.202.11][21425199] command: m9z5 IDLE 16:08:10 [192.168.202.11][21425199] command: cq7q IDLE 16:08:11 [192.168.202.11][21425199] command: 3c54 IDLE 16:08:11 [192.168.202.11][21425199] command: otih IDLE 16:08:11 [192.168.202.11][21425199] command: uuhy IDLE 16:08:11 [192.168.202.11][21425199] command: 7dya IDLE 16:08:11 [192.168.202.11][21425199] command: i2rb IDLE 16:08:11 [192.168.202.11][21425199] command: 13kl IDLE 16:08:11 [192.168.202.11][21425199] command: mbxe IDLE 16:08:11 [192.168.202.11][21425199] command: 0oz5 IDLE 16:08:11 [192.168.202.11][21425199] command: ymn7 IDLE 16:08:11 [192.168.202.11][21425199] command: vavf IDLE 16:08:11 [192.168.202.11][21425199] command: 3vdh IDLE 16:08:11 [192.168.202.11][21425199] command: rnci IDLE 16:08:11 [192.168.202.11][21425199] command: n3gu IDLE 16:08:11 [192.168.202.11][21425199] command: gu0f IDLE 16:08:11 [192.168.202.11][21425199] command: gewp IDLE 16:08:11 [192.168.202.11][21425199] command: vu84 IDLE 16:08:11 [192.168.202.11][21425199] command: d1rz IDLE 16:08:11 [192.168.202.11][21425199] command: 7nz9 IDLE 16:08:11 [192.168.202.11][21425199] command: trs9 IDLE 16:08:11 [192.168.202.11][21425199] command: yqlo IDLE 16:08:11 [192.168.202.11][21425199] command: 2jtj IDLE 16:08:11 [192.168.202.11][21425199] command: 085e IDLE 16:08:11 [192.168.202.11][21425199] command: 2jyw IDLE 16:08:11 [192.168.202.11][21425199] command: ycwo IDLE 16:08:11 [192.168.202.11][21425199] command: iemo IDLE 16:08:11 [192.168.202.11][21425199] command: eien IDLE 16:08:11 [192.168.202.11][21425199] command: lxi2 IDLE 16:08:11 [192.168.202.11][21425199] command: uhug IDLE 16:08:11 [192.168.202.11][21425199] command: jabp IDLE 16:08:11 [192.168.202.11][21425199] command: v1hf IDLE 16:08:11 [192.168.202.11][21425199] command: s0pp IDLE 16:08:11 [192.168.202.11][21425199] command: i4qi IDLE 16:08:11 [192.168.202.11][21425199] command: bc7b IDLE 16:08:11 [192.168.202.11][21425199] command: 6kxh IDLE 16:08:11 [192.168.202.11][21425199] command: bd0a IDLE 16:08:11 [192.168.202.11][21425199] command: i578 IDLE 16:08:11 [192.168.202.11][21425199] command: 4fb8 IDLE 16:08:11 [192.168.202.11][21425199] command: y259 IDLE 16:08:11 [192.168.202.11][21425199] command: tftj IDLE 16:08:11 [192.168.202.11][21425199] command: vm65 IDLE 16:08:11 [192.168.202.11][21425199] command: 2seb IDLE 16:08:11 [192.168.202.11][21425199] command: 2tu4 IDLE 16:08:11 [192.168.202.11][21425199] command: 7fq3 IDLE 16:08:11 [192.168.202.11][21425199] command: nydu IDLE 16:08:11 [192.168.202.11][21425199] command: 5na0 IDLE 16:08:12 [192.168.202.11][21425199] command: yqr4 IDLE 16:08:12 [192.168.202.11][21425199] command: lmd5 IDLE 16:08:12 [192.168.202.11][21425199] command: d4ir IDLE 16:08:12 [192.168.202.11][21425199] command: prma IDLE 16:08:12 [192.168.202.11][21425199] command: g53z IDLE 16:08:12 [192.168.202.11][21425199] command: 8isn IDLE 16:08:12 [192.168.202.11][21425199] command: x5l9 IDLE 16:08:12 [192.168.202.11][21425199] command: mb99 IDLE 16:08:12 [192.168.202.11][21425199] command: 3az0 IDLE 16:08:12 [192.168.202.11][21425199] command: nfpf IDLE 16:08:12 [192.168.202.11][21425199] command: 4roj IDLE 16:08:12 [192.168.202.11][21425199] command: fzcr IDLE 16:08:12 [192.168.202.11][21425199] command: nzgu IDLE 16:08:12 [192.168.202.11][21425199] command: ta6y IDLE 16:08:12 [192.168.202.11][21425199] command: 3ig2 IDLE 16:08:12 [192.168.202.11][21425199] command: 7kgp IDLE 16:08:12 [192.168.202.11][21425199] command: lri1 IDLE 16:08:12 [192.168.202.11][21425199] command: 2isc IDLE 16:08:12 [192.168.202.11][21425199] command: l5mz IDLE 16:08:12 [192.168.202.11][21425199] command: 37j4 IDLE 16:08:12 [192.168.202.11][21425199] command: k4cq IDLE 16:08:12 [192.168.202.11][21425199] command: ye7w IDLE 16:08:12 [192.168.202.11][21425199] command: 0uck IDLE 16:08:12 [192.168.202.11][21425199] command: 0oyd IDLE 16:08:12 [192.168.202.11][21425199] command: 2cbj IDLE 16:08:12 [192.168.202.11][21425199] command: 1pj6 IDLE 16:08:12 [192.168.202.11][21425199] command: nkji IDLE 16:08:12 [192.168.202.11][21425199] command: 1c2o IDLE 16:08:12 [192.168.202.11][21425199] command: b0k8 IDLE 16:08:12 [192.168.202.11][21425199] command: qaeh IDLE 16:08:12 [192.168.202.11][21425199] command: diex IDLE 16:08:12 [192.168.202.11][21425199] command: f6nh IDLE 16:08:12 [192.168.202.11][21425199] command: 6lkk IDLE 16:08:12 [192.168.202.11][21425199] command: 3jep IDLE 16:08:12 [192.168.202.11][21425199] command: vsev IDLE 16:08:12 [192.168.202.11][21425199] command: r79z IDLE 16:08:12 [192.168.202.11][21425199] command: 0bhv IDLE 16:08:12 [192.168.202.11][21425199] command: ow86 IDLE 16:08:12 [192.168.202.11][21425199] command: qnwo IDLE 16:08:12 [192.168.202.11][21425199] command: egss IDLE 16:08:12 [192.168.202.11][21425199] command: t36m IDLE 16:08:12 [192.168.202.11][21425199] command: cj9l IDLE 16:08:12 [192.168.202.11][21425199] command: abfg IDLE 16:08:12 [192.168.202.11][21425199] command: unln IDLE 16:08:12 [192.168.202.11][21425199] command: x217 IDLE 16:08:12 [192.168.202.11][21425199] command: l9br IDLE 16:08:12 [192.168.202.11][21425199] command: 5moj IDLE 16:08:12 [192.168.202.11][21425199] command: e6al IDLE 16:08:12 [192.168.202.11][21425199] command: r7n7 IDLE 16:08:13 [192.168.202.11][21425199] command: tn7m IDLE 16:08:13 [192.168.202.11][21425199] command: 6ljm IDLE 16:08:13 [192.168.202.11][21425199] command: g6ub IDLE 16:08:13 [192.168.202.11][21425199] command: xers IDLE 16:08:13 [192.168.202.11][21425199] command: 2vjl IDLE 16:08:13 [192.168.202.11][21425199] command: wn21 IDLE 16:08:13 [192.168.202.11][21425199] command: lvpe IDLE 16:08:13 [192.168.202.11][21425199] command: nx7v IDLE 16:08:13 [192.168.202.11][21425199] command: an9d IDLE 16:08:13 [192.168.202.11][21425199] command: bno6 IDLE 16:08:13 [192.168.202.11][21425199] command: y1ui IDLE 16:08:13 [192.168.202.11][21425199] command: i3pw IDLE 16:08:13 [192.168.202.11][21425199] command: ixg4 IDLE 16:08:13 [192.168.202.11][21425199] command: phsg IDLE 16:08:13 [192.168.202.11][21425199] command: g8nn IDLE 16:08:13 [192.168.202.11][21425199] command: 3rn6 IDLE 16:08:13 [192.168.202.11][21425199] command: 85iv IDLE 16:08:13 [192.168.202.11][21425199] command: o8cu IDLE 16:08:13 [192.168.202.11][21425199] command: x3uh IDLE 16:08:13 [192.168.202.11][21425199] command: jlsf IDLE 16:08:13 [192.168.202.11][21425199] command: 4brr IDLE 16:08:13 [192.168.202.11][21425199] command: tsyx IDLE 16:08:13 [192.168.202.11][21425199] command: p71l IDLE 16:08:13 [192.168.202.11][21425199] command: lk79 IDLE 16:08:13 [192.168.202.11][21425199] command: f97g IDLE 16:08:13 [192.168.202.11][21425199] command: 8svd IDLE 16:08:13 [192.168.202.11][21425199] command: 08d3 IDLE 16:08:13 [192.168.202.11][21425199] command: i1ba IDLE 16:08:13 [192.168.202.11][21425199] command: dari IDLE 16:08:13 [192.168.202.11][21425199] command: l9uj IDLE 16:08:13 [192.168.202.11][21425199] command: 4ei0 IDLE 16:08:13 [192.168.202.11][21425199] command: nrgl IDLE 16:08:13 [192.168.202.11][21425199] command: oel6 IDLE 16:08:13 [192.168.202.11][21425199] command: 5xvd IDLE 16:08:13 [192.168.202.11][21425199] command: 2lx9 IDLE 16:08:13 [192.168.202.11][21425199] command: swiv IDLE 16:08:13 [192.168.202.11][21425199] command: p7jj IDLE 16:08:13 [192.168.202.11][21425199] command: tgpw IDLE 16:08:13 [192.168.202.11][21425199] command: trsd IDLE 16:08:13 [192.168.202.11][21425199] command: pccw IDLE 16:08:14 [192.168.202.11][21425199] command: rdhw IDLE 16:08:14 [192.168.202.11][21425199] command: 2rig IDLE 16:08:14 [192.168.202.11][21425199] command: vit6 IDLE 16:08:14 [192.168.202.11][21425199] command: yv2g IDLE 16:08:14 [192.168.202.11][21425199] command: oxe1 IDLE 16:08:14 [192.168.202.11][21425199] command: q5ty IDLE 16:08:14 [192.168.202.11][21425199] command: 0jmr IDLE 16:08:14 [192.168.202.11][21425199] command: 95qq IDLE 16:08:14 [192.168.202.11][21425199] command: h5vd IDLE 16:08:14 [192.168.202.11][21425199] command: n24j IDLE 16:08:14 [192.168.202.11][21425199] command: dapo IDLE 16:08:14 [192.168.202.11][21425199] command: 6fm1 IDLE 16:08:14 [192.168.202.11][21425199] command: 5901 IDLE 16:08:14 [192.168.202.11][21425199] command: i6mt IDLE 16:08:14 [192.168.202.11][21425199] command: 5ch4 IDLE 16:08:14 [192.168.202.11][21425199] command: y8ke IDLE 16:08:14 [192.168.202.11][21425199] command: gef5 IDLE 16:08:14 [192.168.202.11][21425199] command: va4d IDLE 16:08:14 [192.168.202.11][21425199] command: k7me IDLE 16:08:14 [192.168.202.11][21425199] command: btre IDLE 16:08:14 [192.168.202.11][21425199] command: ajdc IDLE 16:08:14 [192.168.202.11][21425199] command: avxy IDLE 16:08:14 [192.168.202.11][21425199] command: 60n3 IDLE 16:08:14 [192.168.202.11][21425199] command: m4ym IDLE 16:08:14 [192.168.202.11][21425199] command: f764 IDLE 16:08:14 [192.168.202.11][21425199] command: 00ag IDLE 16:08:14 [192.168.202.11][21425199] command: mv6y IDLE 16:08:14 [192.168.202.11][21425199] command: nf39 IDLE 16:08:14 [192.168.202.11][21425199] command: o0pk IDLE 16:08:14 [192.168.202.11][21425199] command: tw5i IDLE 16:08:14 [192.168.202.11][21425199] command: vdkq IDLE 16:08:14 [192.168.202.11][21425199] command: i3af IDLE 16:08:14 [192.168.202.11][21425199] command: qsmq IDLE 16:08:14 [192.168.202.11][21425199] command: l7gs IDLE 16:08:14 [192.168.202.11][21425199] command: wlyv IDLE 16:08:14 [192.168.202.11][21425199] command: hrl6 IDLE 16:08:14 [192.168.202.11][21425199] command: 6o3m IDLE 16:08:14 [192.168.202.11][21425199] command: d62f IDLE 16:08:14 [192.168.202.11][21425199] command: ztx1 IDLE 16:08:14 [192.168.202.11][21425199] command: ejoq IDLE 16:08:14 [192.168.202.11][21425199] command: jo8n IDLE 16:08:15 [192.168.202.11][21425199] command: 898c IDLE 16:08:15 [192.168.202.11][21425199] command: uo5n IDLE 16:08:15 [192.168.202.11][21425199] command: ljkw IDLE 16:08:15 [192.168.202.11][21425199] command: fqwe IDLE 16:08:15 [192.168.202.11][21425199] command: z2r4 IDLE 16:08:15 [192.168.202.11][21425199] command: v1k3 IDLE 16:08:15 [192.168.202.11][21425199] command: 9ruc IDLE 16:08:15 [192.168.202.11][21425199] command: humj IDLE 16:08:15 [192.168.202.11][21425199] command: wmy6 IDLE 16:08:15 [192.168.202.11][21425199] command: 2r60 IDLE 16:08:15 [192.168.202.11][21425199] command: a66w IDLE 16:08:15 [192.168.202.11][21425199] command: 3sn5 IDLE 16:08:15 [192.168.202.11][21425199] command: o4j4 IDLE 16:08:15 [192.168.202.11][21425199] command: 4j68 IDLE 16:08:15 [192.168.202.11][21425199] command: 7e0z IDLE 16:08:15 [192.168.202.11][21425199] command: ts0o IDLE 16:08:15 [192.168.202.11][21425199] command: k62v IDLE 16:08:15 [192.168.202.11][21425199] command: 9u3v IDLE 16:08:15 [192.168.202.11][21425199] command: 1vo5 IDLE 16:08:15 [192.168.202.11][21425199] command: un6t IDLE 16:08:15 [192.168.202.11][21425199] command: v74a IDLE 16:08:15 [192.168.202.11][21425199] command: zqk5 IDLE 16:08:15 [192.168.202.11][21425199] command: 7v00 IDLE 16:08:15 [192.168.202.11][21425199] command: d6yk IDLE 16:08:15 [192.168.202.11][21425199] command: mtc3 IDLE 16:08:15 [192.168.202.11][21425199] command: fu9l IDLE 16:08:15 [192.168.202.11][21425199] command: bbzw IDLE 16:08:15 [192.168.202.11][21425199] command: zwms IDLE 16:08:15 [192.168.202.11][21425199] command: vw1a IDLE 16:08:15 [192.168.202.11][21425199] command: buw0 IDLE 16:08:15 [192.168.202.11][21425199] command: ogzd IDLE 16:08:15 [192.168.202.11][21425199] command: 4481 IDLE 16:08:15 [192.168.202.11][21425199] command: pvdz IDLE 16:08:15 [192.168.202.11][21425199] command: 112d IDLE 16:08:15 [192.168.202.11][21425199] command: ah3f IDLE 16:08:15 [192.168.202.11][21425199] command: pmj9 IDLE 16:08:15 [192.168.202.11][21425199] command: ljzk IDLE 16:08:15 [192.168.202.11][21425199] command: dbuv IDLE 16:08:15 [192.168.202.11][21425199] command: gb84 IDLE 16:08:15 [192.168.202.11][21425199] command: sb7b IDLE 16:08:15 [192.168.202.11][21425199] command: iml4 IDLE 16:08:15 [192.168.202.11][21425199] command: wek0 IDLE 16:08:15 [192.168.202.11][21425199] command: ovhh IDLE 16:08:15 [192.168.202.11][21425199] command: 39bq IDLE 16:08:15 [192.168.202.11][21425199] command: tu31 IDLE 16:08:15 [192.168.202.11][21425199] command: wok3 IDLE 16:08:15 [192.168.202.11][21425199] command: p2ez IDLE 16:08:15 [192.168.202.11][21425199] command: argr IDLE 16:08:15 [192.168.202.11][21425199] command: q9dq IDLE 16:08:15 [192.168.202.11][21425199] command: ea8l IDLE 16:08:15 [192.168.202.11][21425199] command: nfnd IDLE 16:08:15 [192.168.202.11][21425199] command: sc4z IDLE 16:08:15 [192.168.202.11][21425199] command: 5bpf IDLE 16:08:15 [192.168.202.11][21425199] command: j8k8 IDLE 16:08:15 [192.168.202.11][21425199] command: brs0 IDLE 16:08:15 [192.168.202.11][21425199] command: rjvj IDLE 16:08:16 [192.168.202.11][21425199] command: nmj0 IDLE 16:08:16 [192.168.202.11][21425199] command: x7uv IDLE 16:08:16 [192.168.202.11][21425199] command: s0cq IDLE 16:08:16 [192.168.202.11][21425199] command: xi5v IDLE 16:08:16 [192.168.202.11][21425199] command: j3vg IDLE 16:08:16 [192.168.202.11][21425199] command: xxtr IDLE 16:08:16 [192.168.202.11][21425199] command: czhg IDLE 16:08:16 [192.168.202.11][21425199] command: qhu0 IDLE 16:08:16 [192.168.202.11][21425199] command: 4kue IDLE 16:08:16 [192.168.202.11][21425199] command: yydo IDLE 16:08:16 [192.168.202.11][21425199] command: jt93 IDLE 16:08:16 [192.168.202.11][21425199] command: sibh IDLE 16:08:16 [192.168.202.11][21425199] command: u7n7 IDLE 16:08:16 [192.168.202.11][21425199] command: 58wp IDLE 16:08:16 [192.168.202.11][21425199] command: 4s1d IDLE 16:08:16 [192.168.202.11][21425199] command: 87a4 IDLE 16:08:16 [192.168.202.11][21425199] command: lol8 IDLE 16:08:16 [192.168.202.11][21425199] command: 5h58 IDLE 16:08:16 [192.168.202.11][21425199] command: v7dy IDLE 16:08:16 [192.168.202.11][21425199] command: nsh7 IDLE 16:08:16 [192.168.202.11][21425199] command: dzp1 IDLE 16:08:16 [192.168.202.11][21425199] command: xj4s IDLE 16:08:16 [192.168.202.11][21425199] command: 0ws3 IDLE 16:08:16 [192.168.202.11][21425199] command: t6n2 IDLE 16:08:16 [192.168.202.11][21425199] command: o3ol IDLE 16:08:16 [192.168.202.11][21425199] command: t4rw IDLE 16:08:16 [192.168.202.11][21425199] command: mgvo IDLE 16:08:16 [192.168.202.11][21425199] command: 5rse IDLE 16:08:16 [192.168.202.11][21425199] command: 7fdj IDLE 16:08:16 [192.168.202.11][21425199] command: 7s6h IDLE 16:08:16 [192.168.202.11][21425199] command: mlfb IDLE 16:08:16 [192.168.202.11][21425199] command: 06hh IDLE 16:08:16 [192.168.202.11][21425199] command: 32ni IDLE 16:08:16 [192.168.202.11][21425199] command: cslk IDLE 16:08:16 [192.168.202.11][21425199] command: aml4 IDLE 16:08:16 [192.168.202.11][21425199] command: rle9 IDLE 16:08:16 [192.168.202.11][21425199] command: dg6a IDLE 16:08:16 [192.168.202.11][21425199] command: 20hl IDLE 16:08:16 [192.168.202.11][21425199] command: f3pc IDLE 16:08:16 [192.168.202.11][21425199] command: 8f6a IDLE 16:08:17 [192.168.202.11][21425199] command: reav IDLE 16:08:17 [192.168.202.11][21425199] command: 3qpc IDLE 16:08:17 [192.168.202.11][21425199] command: 5utk IDLE 16:08:17 [192.168.202.11][21425199] command: ldjq IDLE 16:08:17 [192.168.202.11][21425199] command: sbhb IDLE 16:08:17 [192.168.202.11][21425199] command: ire7 IDLE 16:08:17 [192.168.202.11][21425199] command: o2n7 IDLE 16:08:17 [192.168.202.11][21425199] command: t9n7 IDLE 16:08:17 [192.168.202.11][21425199] command: cags IDLE 16:08:17 [192.168.202.11][21425199] command: tx43 IDLE 16:08:17 [192.168.202.11][21425199] command: 87o5 IDLE 16:08:17 [192.168.202.11][21425199] command: zjfx IDLE 16:08:17 [192.168.202.11][21425199] command: 7url IDLE 16:08:17 [192.168.202.11][21425199] command: 58ky IDLE 16:08:17 [192.168.202.11][21425199] command: zgr9 IDLE 16:08:17 [192.168.202.11][21425199] command: 6nif IDLE 16:08:17 [192.168.202.11][21425199] command: 07jo IDLE 16:08:17 [192.168.202.11][21425199] command: 3scq IDLE 16:08:17 [192.168.202.11][21425199] command: 1j7j IDLE 16:08:17 [192.168.202.11][21425199] command: l0b2 IDLE 16:08:17 [192.168.202.11][21425199] command: p7qy IDLE 16:08:17 [192.168.202.11][21425199] command: qms1 IDLE 16:08:17 [192.168.202.11][21425199] command: sln8 IDLE 16:08:17 [192.168.202.11][21425199] command: x07c IDLE 16:08:17 [192.168.202.11][21425199] command: jand IDLE 16:08:17 [192.168.202.11][21425199] command: iicp IDLE 16:08:17 [192.168.202.11][21425199] command: 264r IDLE 16:08:17 [192.168.202.11][21425199] command: nqoj IDLE 16:08:17 [192.168.202.11][21425199] command: p516 IDLE 16:08:17 [192.168.202.11][21425199] command: 00dj IDLE 16:08:17 [192.168.202.11][21425199] command: 0oo8 IDLE 16:08:17 [192.168.202.11][21425199] command: 7yc3 IDLE 16:08:17 [192.168.202.11][21425199] command: ex3e IDLE 16:08:17 [192.168.202.11][21425199] command: dyw0 IDLE 16:08:17 [192.168.202.11][21425199] command: qy06 IDLE 16:08:17 [192.168.202.11][21425199] command: 6opb IDLE 16:08:17 [192.168.202.11][21425199] command: oxnm IDLE 16:08:17 [192.168.202.11][21425199] command: wiqm IDLE 16:08:17 [192.168.202.11][21425199] command: 74jg IDLE 16:08:17 [192.168.202.11][21425199] command: r750 IDLE My dovecot -n config: # 2.2.25 (7be1766): /usr/local/etc/dovecot/dovecot.conf # OS: Linux 2.6.32-642.1.1.el6.x86_64 x86_64 CentOS release 6.8 (Final) auth_cache_negative_ttl = 0 auth_cache_ttl = 0 auth_mechanisms = plain login auth_verbose = yes auth_verbose_passwords = plain base_dir = /var/run/dovecot/ debug_log_path = /var/log/dovecot/debug.log disable_plaintext_auth = no info_log_path = /var/log/dovecot/info.log log_path = /var/log/dovecot/dovecot.log passdb { args = /usr/local/etc/dovecot/conf.d/10-mysql.conf driver = sql } protocols = pop3 imap service imap-login { service_count = 0 vsz_limit = 512 M } service pop3-login { process_min_avail = 1 service_count = 0 } ssl_ca = </usr/local/etc/dovecot/RapidSSL_CA_G3.pem ssl_cert = </usr/local/etc/dovecot/mailserverpro.pem ssl_key = </usr/local/etc/dovecot/mailserverpro.pem userdb { driver = prefetch } My MYSQL connection config: password_query = SELECT NULL AS password, NULL as user, NULL AS destuser, host, 'Y' AS nologin, 'Y' as nodelay, 'Y' AS nopassword, 'Y' AS proxy, 'Y' as proxy_nopipelining, 120 AS proxy_timeout FROM dovecot_domains WHERE domain = '%d' Anybody can help? Best Regards, Cleber

5 9

virtual users, mailer daemon send mails to non existant recipient and dovecot store it
by Sam 24 Aug '16

24 Aug '16

Hello, Sometime when we receive a spam or virus that is detected as it, mailer daemon send a reply to the sender to inform that the message is a spam or content viruses. The problem is that the sender of the spam as something like voicemail(a)ourdomain.fr ( the user voicemail doesn't exist in our database ) And sometimes dovecot create the directory and store the reply 's mail... Aug 23 16:07:31 mail3 postfix/cleanup[15687]: C7EEB406FFFD: message-id=<20160823140731.C7EEB406FFFD(a)mail3.ourdomain.fr> Aug 23 16:07:31 mail3 postfix/qmgr[12987]: C7EEB406FFFD: from=<>, size=14280, nrcpt=1 (queue active) Aug 23 16:07:31 mail3 postfix/bounce[15800]: 824D7406FFFC: sender non-delivery notification: C7EEB406FFFD Aug 23 16:07:31 mail3 postfix/qmgr[12987]: 824D7406FFFC: removed Aug 23 16:07:31 mail3 dovecot: auth: Debug: master in: USER#0111#011voicemail#011service=lda Aug 23 16:07:31 mail3 dovecot: auth: Debug: userdb out: USER#0111#011voicemail#011uid=1001#011gid=1001#011home=/home/vmail/voicemail Aug 23 16:07:31 mail3 dovecot: lda(voicemail): msgid=<20160823140731.C7EEB406FFFD(a)mail3.ourdomain.fr>: saved mail to INBOX Aug 23 16:07:31 mail3 postfix/pipe[15791]: C7EEB406FFFD: to=<voicemail(a)ourdomain.fr>, relay=dovecot, delay=0.02, delays=0/0/0/0.01, dsn=2.0.0, status=sent (delivered via dovecot service) Aug 23 16:07:31 mail3 postfix/qmgr[12987]: C7EEB406FFFD: removed here is the stored mail : Return-Path: <MAILER-DAEMON> Delivered-To: voicemail(a)ourdomain.fr Received: by mail3.ourdomain.fr (Postfix) id C7EEB406FFFD; Tue, 23 Aug 2016 16:07:31 +0200 (CEST) Date: Tue, 23 Aug 2016 16:07:31 +0200 (CEST) From: MAILER-DAEMON(a)ourdomain.fr (Mail Delivery System) Subject: Undelivered Mail Returned to Sender To: voicemail(a)ourdomain.fr Auto-Submitted: auto-replied MIME-Version: 1.0 Content-Type: multipart/report; report-type=delivery-status; boundary="824D7406FFFC.1471961251/mail3.ourdomain.fr" Message-Id: <20160823140731.C7EEB406FFFD(a)mail3.ourdomain.fr> This is a MIME-encapsulated message. --824D7406FFFC.1471961251/mail3.ourdomain.fr Content-Description: Notification Content-Type: text/plain; charset=us-ascii This is the mail system at host mail3.ourdomain.fr. I'm sorry to have to inform you that your message could not be delivered to one or more recipients. It's attached below. For further assistance, please send mail to postmaster. If you do so, please include this problem report. You can delete your own text from the attached returned message. The mail system <existing.user(a)ourdomain.com> (expanded from <existing.user(a)ourdomain.fr>): host mails.collaboration-sfr.com[86.64.240.34] said: 552 5.2.0 <ae7X1t00115ZlG601e7Xvw> reject for policy reason : spam detected in your mail (in reply to end of DATA command) --824D7406FFFC.1471961251/mail3.ourdomain.fr Content-Description: Delivery report Content-Type: message/delivery-status Reporting-MTA: dns; mail3.ourdomain.fr X-Postfix-Queue-ID: 824D7406FFFC X-Postfix-Sender: rfc822; voicemail(a)ourdomain.fr Arrival-Date: Tue, 23 Aug 2016 16:07:29 +0200 (CEST) Final-Recipient: rfc822; existing.user(a)ourdomain.com Original-Recipient: rfc822;existing.user(a)ourdomain.fr Action: failed Status: 5.2.0 Remote-MTA: dns; mails.collaboration-sfr.com Diagnostic-Code: smtp; 552 5.2.0 <ae7X1t00115ZlG601e7Xvw> reject for policy reason : spam detected in your mail --824D7406FFFC.1471961251/mail3.ourdomain.fr Content-Description: Undelivered Message Content-Type: message/rfc822 Return-Path: <voicemail(a)ourdomain.fr> Received: from 177.222.108.254.dynamic.on.com.br (unknown [177.222.108.254]) by mail3.ourdomain.fr (Postfix) with ESMTP id 824D7406FFFC for <existing.user(a)ourdomain.fr>; Tue, 23 Aug 2016 16:07:29 +0200 (CEST) From:voicemail@ourdomain.fr To:existing.user@ourdomain.fr Subject: [Vigor2820 Series] New voice mail message from 01425939048 on 2016/08/23 11:07:28 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="5A1b791c537d41f1" --5A1b791c537d41f1 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Dear existing.user : There is a message for you from 01425939048, on 2016/08/23 11:07:28 . You might want to check it when you get a chance.Thanks! --5A1b791c537d41f1 Content-Type: audio/x-wav; name="Message_from_01425939048.wav.zip" Content-Transfer-Encoding: BASE64 Content-Description: Voicemail sound attachment. Content-Disposition: attachment; filename="Message_from_01425939048.wav.zip" UEsDBBQAAAAIAGZiF0n9ycl98x4AAE54AAAQAAAAODU5MjE2MjE1MDA4LndzZuxbW2/jWHJ+ dgP9H9hCMJbaHrWuljW2e2FJlCz1iLJk3T39QJG0SIkXNS/WpcdAZgYJctmXBNgE+7jAArkB uTzkKUD+jLFJ9l+kDnl4Ubd4KM/0dIBgG6ZskfVV1amqU6fqHPb5L1aK/IvXz5+dL1huzk4F 9OdMm1ASf3HYuCq9YZqHr891SzUlBT17/ozC/855weB0aWFKmvo6cPvV9n3nyfkrl8W585CS WXVqgTyQcmPfATEvbsuVy+7lLULdmLqkTpMLXTM1c70QkhPBMDVZ40SVFQW9X+85P6ZpavCP ... I don't understand why I don't have the same behavior that when I send a mail to a non existant address ( <tottttt(a)ourdomain.fr>: Recipient address rejected: User unknown in virtual mailbox table ) How can I fix it? Thanks a lot! Samuel

5 11

juste pour vous
by bunkertor 24 Aug '16

24 Aug '16

Salut, Regardez ce qu'ils ont pour vous, je suppose que cela vaut la peine de lire, plus d'infos ici <http://ntispokequi.truthisthenewporn.com/xofbi> bunkertor

1 0

Re: dovecot Digest, Vol 160, Issue 25
by Ron Cleven 23 Aug '16

23 Aug '16

>> >On August 23, 2016 at 6:57 PM Sam<sr42354(a)gmail.com> wrote: >> > >> > >> >Hello, >> > >> >Sometime when we receive a spam or virus that is detected as it, mailer >> >daemon send a reply to the sender to inform that the message is a spam >> >or content viruses. >> > >> >The problem is that the sender of the spam as something like >> >voicemail(a)ourdomain.fr ( the user voicemail doesn't exist in our database ) >> > >> >And sometimes dovecot create the directory and store the reply 's mail... >> > >> > If I understand your question correctly, you are sometimes sending an after-the-fact bounce message based upon the return-path in at least some situations where you detect a spam or virus (as opposed to responding with an error code response during the SMTP session)? If my understanding is correct, you should never ever ever ever ever ever ever send those sort of NDR's. Please google "backscatter".

1 0

antispam plugin pipe script seems not to be called when it "should be"
by Ben Johnson 23 Aug '16

23 Aug '16

Hello, (Full "doveconf -n" output is at the end of this message.) I'm attempting to recreate a "recipe" I had used successfully for quite some time (in Ubuntu 12.04 LTS), which allowed me to train SpamAssassin's Bayes database when someone dragged an email message from one sub-folder of the account to another. I later tried to re-implement it (in Ubuntu 14.04 LTS), and core-dumps resulted. I posted to this list about it several times, but nobody was ever able to help me solve the problem. I just tried the same (in Ubuntu 16.04 LTS), hoping that the source had evolved since then, and while I don't see a core-dump, the pipe script doesn't seem to be called. I've booby-trapped the pipe script with quite a bit of debugging output, which should be written to a file, but I don't see any indication that the pipe script is ever executed. When logged-in as an IMAP user, and I drag a message from the user's Inbox into the "Spam" folder, I do see the following activity in the syslog: Aug 18 22:12:15 example.com imap: antispam: mailbox_is_unsure(Junk): 0 Aug 18 22:12:15 example.com imap: antispam: mailbox_is_trash(INBOX): 0 Aug 18 22:12:15 example.com imap: antispam: mailbox_is_trash(Junk): 0 Aug 18 22:12:15 example.com imap: antispam: mail copy: from trash: 0, to trash: 0 Aug 18 22:12:15 example.com imap: antispam: mailbox_is_spam(INBOX): 0 Aug 18 22:12:15 example.com imap: antispam: mailbox_is_spam(Junk): 1 Aug 18 22:12:15 example.com imap: antispam: mailbox_is_unsure(INBOX): 0 Aug 18 22:12:15 example.com imap: antispam: mail copy: src spam: 0, dst spam: 1, src unsure: 0 Aug 18 22:12:15 example.com imap: antispam: running mailtrain backend program /bin/bash Aug 18 22:12:15 example.com imap: antispam: running mailtrain backend program /bin/bash Aug 18 22:12:15 example.com imap: antispam: running mailtrain backend program parameter 1 /usr/local/bin/sa-learn-pipe.sh Aug 18 22:12:15 example.com imap: antispam: running mailtrain backend program parameter 2 --spam But the piped message is never delivered to the target mailbox. The mail log at /var/log/mail.log does not register any activity when I move messages (and maybe that's expected). Here are the contents of the /usr/local/bin/sa-learn-pipe.sh script: http://pastebin.com/7vm74jmk The permissions and mode on the script seem appropriate: $ stat /usr/local/bin/sa-learn-pipe.sh File: '/usr/local/bin/sa-learn-pipe.sh' Size: 1765 Blocks: 8 IO Block: 4096 regular file Device: fd01h/64769d Inode: 669345 Links: 1 Access: (0755/-rwxr-xr-x) Uid: ( 5000/ vmail) Gid: ( 5000/ vmail) Access: 2016-08-18 19:09:47.307392919 -0400 Modify: 2016-08-18 19:09:31.231391749 -0400 Change: 2016-08-18 19:09:31.231391749 -0400 Birth: - What might I be doing incorrectly here? Please let me know if I can provide any other information. Thank you in advance, -Ben Full "doveconf -n" output: $ doveconf -n # 2.2.22 (fe789d2): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.13 (7b14904) # OS: Linux 4.4.0-34-generic x86_64 Ubuntu 16.04.1 LTS auth_mechanisms = plain login disable_plaintext_auth = no 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 { antispam_backend = pipe antispam_debug_target = syslog antispam_pipe_program = /bin/bash antispam_pipe_program_args = /usr/local/bin/sa-learn-pipe.sh antispam_pipe_program_notspam_arg = --ham antispam_pipe_program_spam_arg = --spam antispam_pipe_tmpdir = /tmp antispam_spam_pattern_ignorecase = SPAM;JUNK antispam_trash_pattern_ignorecase = trash;Deleted * antispam_verbose_debug = 1 quota = dict:user::file:/var/vmail/%d/%n/.quotausage quota_rule2 = Trash:storage=+100M quota_rule3 = Junk:ignore quota_rule4 = INBOX:storage=+100M quota_warning = storage=100%% quota-reached 100 %u %d quota_warning2 = storage=95%% quota-warning 95 %u %d quota_warning3 = storage=80%% quota-warning 80 %u %d quota_warning4 = -storage=100%% quota-below below %u %d sieve = /var/vmail/%d/%n/.sieve sieve_max_redirects = 25 } postmaster_address = postmaster(a)example.com 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 } } service quota-below { executable = script /usr/local/bin/quota-below.sh unix_listener quota-below { group = vmail mode = 0666 user = vmail } user = vmail } service quota-reached { executable = script /usr/local/bin/quota-reached.sh unix_listener quota-reached { group = vmail mode = 0666 user = vmail } user = vmail } service quota-warning { executable = script /usr/local/bin/quota-warning.sh unix_listener quota-warning { group = vmail mode = 0666 user = vmail } user = vmail } ssl_cert = </etc/postfix/smtpd.cert ssl_key = </etc/postfix/smtpd.key ssl_protocols = !SSLv2 !SSLv3 userdb { driver = prefetch } userdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } protocol imap { mail_plugins = quota imap_quota antispam } protocol pop3 { mail_plugins = quota pop3_uidl_format = %08Xu%08Xv } protocol lda { mail_plugins = sieve quota } protocol lmtp { mail_plugins = quota sieve postmaster_address = webmaster@localhost }

5 8

Director/Doveadm: Trying to iterate users, but userdbs don't support it
by Tom Sommer 23 Aug '16

23 Aug '16

Hi I'm doing: doveadm force-resync -S director1:1234 -A "*" The director gives this error: Jul 06 16:17:29 auth: Error: Trying to iterate users, but userdbs don't support it Jul 06 16:17:29 doveadm: Error: User listing returned failure Jul 06 16:17:29 doveadm: Error: Failed to iterate through some users The director has "iterate_query" set -- Tom

2 2

Re: Catch-all with LMTP and Postfix
by Aki Tuomi 23 Aug '16

23 Aug '16

On 22.08.2016 21:53, Michael Starks wrote: > On 08/22/2016 01:29 AM, Aki Tuomi wrote: >> It seems your postfix is misbehaving. Did you forget to run postmap? >> >> Aki Tuomi >> Dovecot oy > > Thanks for the response, Aki. I dug a little deeper and found this: > > lrwxrwxrwx. 1 root root 20 Jul 24 01:37 virtual_alias_maps -> > /etc/postfix/virtual > > I had been postmapping virtual_alias_maps, but not virtual. I guess > postmap doesn't follow links. When I postmapped virtual and did a > 'postfix reload' it started to work. Seems you accidentically replied to me only. Postfix uses the filename you provide as name for the db file, so running it against symlinks does follow the symlink, but it uses the symlink name as what it uses to create the .db file. You can test this by creating file and doing symlink for it and running postmap against the symlink. You'll see that it will create symlink-name.db file instead of file.db. Aki Tuomi Dovecot oy

2 1

Re: Change dovecot hostname
by Joseph Tam 23 Aug '16

23 Aug '16

"Scott W. Sander" writes: > Received: from mail.domain.test > by appserver4.domain.com (Dovecot) with LMTP id z7RGLzH4uldlPAAAxdv4Dw > for <user(a)domain.test>; Mon, 22 Aug 2016 09:03:45 -0400 > ------- > > I want the part that says "by appserver4.domain.com (Dovecot)" to say "by > mail.domain.test (Dovecot)". I don't want it to say the FQDN of the actual > host server that is running Dovecot. > > The server currently referenced as "mail.domain.test" in the headers is > postfix running on the same machine. Oh yeah, right, LMTP. I don't run LMTP myself, but I suspect the hostname is mapped from the IP of the LMTP listening interface (using /etc/hosts or DNS). Maybe you can change the IP of your listening interface to match mail.domain.test and firewall it off if that IP is public facing. >From reading the code, I can't quite grok how LMTP derives the host label, but as a last resort, you can patch at src/lmtp/commands.c in client_get_added_headers(). Joseph Tam <jtam.home(a)gmail.com>

1 0

specifying elliptic curve
by İhsan Doğan 23 Aug '16

23 Aug '16

Hi, I've noticed that Dovecot is using per default the elliptic curve sect571r1. Because not all clients might support sect571r1, I would like to set the elliptic curve manually. Is that possible? -Ihsan -- ihsan(a)dogan.ch http://blog.dogan.ch/

3 2

a question about certificates from letsencrypt
by Andreas Meyer 22 Aug '16

22 Aug '16

Hello! Certificates from letsencrypt are renewed every three months. Does that mean a MUA has to accept the renewed certificates manually everytime it is renewed? Sorry if this is OT! Greetings Andreas

6 6

Crash on opening mailbox
by Ladislav Laska 22 Aug '16

22 Aug '16

Hi! I'm currently experiencing a crash of dovecot 2.2.25 on Gentoo, upon opening mailbox. The crash only triggers on opening inbox, other mailboxes seem to work fine. It happens every time, and can be reproduced on request. I also briefly tried 2.2.19, and it behaves the same. The bug seems to be triggered by some mail, as I encountered it previously and fixed by removing some spam. I guess it might be malformed header of some kind. I can open the mailbox locally using mutt, but fail to do so remotely (using mutt or K-9 mail on android). Unforunately, I haven't been able to isolate the specific mail, as when I create a new mailbox, dovecot refuses to open it: [CANNOT] Mailbox isn't a valid mbox file (0.000 + 0.000 secs). I'm not really sure what's going on and will investigate further once I find some time to do so. I also experienced a similar problem on opening a specific mail, but it's much harder to reproduce and I currently don't have an example. The crash looks very similar, and only happens on first attempt to open a specific mail, it always works later on. I'm attaching a stack trace and dovecot -n. I'm also willing to send the binary and core dump, but not publicly, as I'm not eager to share whatever's inside with the whole world. Other than what I mentioned, I'm running pretty standard setup, with postfix on Gentoo x86_64, ext4 fs, quota and disk space is plentiful. The delivery agent is dovecot itself, in postfix/main.cf I have: mailbox_command = /usr/libexec/dovecot/deliver I'm using sieve script to file my mail, but the problem manifested even before when I was still using procmail to deliver my mail (I migrated because I had doubts about procmail and dovecot lock cooperation) I'll keep my mailbox corrupted for a few more days, and access the mail only locally, hoping to test a potential fix. Let me know if you need any more info/experimentation. Also, if you know a good way to find the mail that causes the trouble out of the core, let me know, I'd be glad to forward it for testing. Thanks and I hope we can find (and fix) the problem! -- S pozdravem Ladislav Láska <laska(a)kam.mff.cuni.cz> Katedra Aplikované Matematiky, MFF UK tel.: +420 739 464 167

2 8

Re: Change dovecot hostname
by Joseph Tam 22 Aug '16

22 Aug '16

"Scott W. Sander" writes: > I have noticed that the name of my private server running dovecot appears > in email headers rather than the public-friendly name of my server. Which headers are you taking about? If you're talking about Received: headers, that's usually inserted by your MTA, not dovecot. Joseph Tam <jtam.home(a)gmail.com>

3 2

LMTP doing passdb queries ?
by Peter Mogensen 22 Aug '16

22 Aug '16

Hi, I can see dovecot is doing a passdb query when handling the LMTP RCPT command. That's kinda unexpected for me. I would have thought it only did a userdb lookup. I have disabled lmtp_proxy to be sure it didn't do a passdb lookup to check the proxy field. Is this expected? Doesn't the LDA only do userdb lookups? /Peter

1 2

Catch-all with LMTP and Postfix
by Michael Starks 22 Aug '16

22 Aug '16

Hidy-ho, I'm having a difficult time getting catch-all working when using Dovecot LMTP. I would like *(a)example.com (everything) to go to virtual(a)example.com, where virtual is a valid virtual user. It seems that things are getting as far as LMTP, but then the mail gets bounced. To wit: Aug 21 08:02:50 hostname postfix/lmtp[4914]: 8DF8E9AFE6: to=<test(a)example.com>, relay=mail.example.com[private/dovecot-lmtp], delay=0.07, delays=0.04/0.01/0.01/0.01, dsn=5.1.1, status=bounced (host mail.example.com[private/dovecot-lmtp] said: 550 5.1.1 <test(a)example.com> User doesn't exist: test(a)example.com (in reply to RCPT TO command)) In the previous log example, test(a)example.com should have been forwarded (aliased) to the virtual mail user. Some config details: [root@hostname postfix]# cat /etc/postfix/virtual ######################################### #### Postmap this file after editing #### ######################################### # Person who should get root's mail. Don't receive mail as root! #root you # Basic system aliases -- these MUST be present MAILER-DAEMON postmaster postmaster root # General redirections for pseudo accounts bin root daemon root named root nobody root uucp root www root ftp-bugs root postfix root # Put your local aliases here. @example.com virtual(a)example.com # Well-known aliases manager root dumper root operator root abuse postmaster # trap decode to catch security attacks decode root [root@hostname postfix]# cat /etc/postfix/virtual_mailbox_domains ################################################ #### Do NOT postmap this file after editing #### ################################################ example.com [root@hostname postfix]# cat /etc/postfix/virtual_mailbox_maps ######################################### #### Postmap this file after editing #### ######################################### # From: http://wiki.dovecot.org/LDA/Postfix # Info: if you use the Dovecot LDA or LMTP it doesn't matter what you use behind the recipient address. Use "OK", the full name of the user or else. # I am using the Dovecot LMTP @example.com OK [root@hostname postfix]# dovecot --version 2.2.10 [root@hostname postfix]# dovecot -n # 2.2.10: /etc/dovecot/dovecot.conf # OS: Linux 3.10.0-327.22.2.el7.x86_64 x86_64 CentOS Linux release 7.2.1511 (Core) auth_verbose = yes login_greeting = What's crackalackin? mail_debug = yes mail_home = /var/mail/%d/%n mail_location = maildir:~/mail maildir_very_dirty_syncs = yes mbox_write_locks = fcntl namespace inbox { hidden = no 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 = separator = / type = private } passdb { args = scheme=SSHA512 /etc/dovecot/passdb driver = passwd-file } protocols = imap lmtp 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 } } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } ssl_cert = </etc/pki/tls/certs/hostname.com.crt ssl_cipher_list = EDH+CAMELLIA:EDH+aRSA:EECDH+aRSA+AESGCM:EECDH+aRSA+SHA256:EECDH:+CAMELLIA128:+AES128:+SSLv3:!aNULL:!eNULL:!LOW:!3DES:!MD5:!EXP:!PSK:!DSS:!RC4:!SEED:!IDEA:!ECDSA:kEDH:CAMELLIA128-SHA:AES128-SHA ssl_dh_parameters_length = 2048 ssl_key = </etc/pki/tls/certs/example.com.key ssl_prefer_server_ciphers = yes ssl_protocols = !SSLv3 !SSLv2 userdb { args = /etc/dovecot/userdb driver = passwd-file } [root@hostname postfix]# postconf -d mail_version mail_version = 2.10.1 [root@talyn postfix]# postconf -n alias_database = hash:/etc/aliases alias_maps = hash:/etc/aliases body_checks = pcre:/etc/postfix/body_checks.pcre broken_sasl_auth_clients = no command_directory = /usr/sbin config_directory = /etc/postfix daemon_directory = /usr/libexec/postfix data_directory = /var/lib/postfix debug_peer_level = 2 debugger_command = PATH=/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin ddd $daemon_directory/$process_name $process_id & sleep 5 disable_vrfy_command = yes header_checks = pcre:/etc/postfix/header_checks.pcre html_directory = no inet_protocols = all mail_owner = postfix mail_spool_directory = /var/spool/mail mailq_path = /usr/bin/mailq.postfix manpage_directory = /usr/share/man message_size_limit = 20480000 mydestination = $myhostname, localhost.$mydomain, localhost myhostname = mail.example.com mynetworks_style = host newaliases_path = /usr/bin/newaliases.postfix notify_classes = resource, software, bounce queue_directory = /var/spool/postfix readme_directory = /usr/share/doc/postfix-2.10.1/README_FILES relay_domains = $mydestination sample_directory = /usr/share/doc/postfix-2.10.1/samples sendmail_path = /usr/sbin/sendmail.postfix setgid_group = postdrop smtp_header_checks = pcre:/etc/postfix/smtp_header_checks.pcre smtp_tls_note_starttls_offer = yes smtp_use_tls = yes smtpd_banner = $myhostname Microsoft ESMTP MAIL Service, Version: 6.0.3790.1830 ready. smtpd_data_restrictions = reject_unauth_pipelining, reject_multi_recipient_bounce permit smtpd_helo_required = yes smtpd_recipient_restrictions = permit_sasl_authenticated, permit_mynetworks, permit_sasl_authenticated, reject_invalid_hostname, reject_invalid_helo_hostname, reject_non_fqdn_helo_hostname, reject_non_fqdn_hostname, reject_non_fqdn_sender, reject_non_fqdn_recipient, reject_unknown_sender_domain, reject_unknown_recipient_domain, reject_unauth_destination, check_recipient_access hash:/etc/postfix/recipient_access.hash, check_recipient_access pcre:/etc/postfix/recipient_access.pcre, check_sender_access hash:/etc/postfix/sender_access.hash, check_sender_access pcre:/etc/postfix/sender_access.pcre, reject_rbl_client b.barracudacentral.org, reject_rbl_client zen.spamhaus.org, reject_rbl_client bl.spamcop.net permit smtpd_sasl_auth_enable = yes smtpd_sasl_local_domain = smtpd_sasl_path = private/auth smtpd_sasl_security_options = noanonymous smtpd_sasl_type = dovecot smtpd_tls_auth_only = yes smtpd_tls_cert_file = /etc/pki/tls/certs/example.com.crt smtpd_tls_key_file = /etc/pki/tls/certs/example.com.key smtpd_tls_loglevel = 1 smtpd_tls_received_header = yes smtpd_tls_security_level = may smtpd_tls_session_cache_timeout = 3600s tls_random_source = dev:/dev/urandom unknown_local_recipient_reject_code = 550 virtual_alias_maps = hash:/etc/postfix/virtual virtual_mailbox_domains = /etc/postfix/virtual_mailbox_domains virtual_mailbox_maps = hash:/etc/postfix/virtual_mailbox_maps virtual_transport = lmtp:unix:private/dovecot-lmtp Thank you in advance for your assistance.

2 1

Field Return-Path contains twice the domain
by Quaquaraquà 22 Aug '16

22 Aug '16

Dear exim & dovecot users, posting on both mailing lists as I am not sure who has the ultimate responsability for this field. I am trying to set up a mail server for multiple domains in my VPS. So I managed to set up the authentication through a dovecot authenticator, which relies to a sqlite database. I would like that, from the database perspective, a query has, as input parameters, both the username and the domain to check the password. For this purpose, I am requesting that the SMTP account is in the full form username(a)domain.com. When forwarded to the dovecot authenticator, I can extract the user with %n and %d. This works, but it has a utter drawback: emails are sent repeating twice the domain in the Return-Path field, e.g. : Return-Path: <"user(a)domain.net"@domain.net> Subject: Re: Hello To: nuquaquaraqua(a)gmail.com From: user <user(a)domain.net> How do I properly fix the field Return-Path now? dovecot --version: 2.2.25 (7be1766) Exim version 4.87 #1 built 28-Jul-2016 18:38:04 Kind regards, Quaquaraqua

1 0

Port 143 is no SSL; no client auth; plain password auth. But port 993 is SSL; client cert auth.
by UK Universal Support Limited 21 Aug '16

21 Aug '16

I am experiencing the error "Error: BUG: Authentication client sent unknown handshake command:" My goal is Port 143: no SSL; no client auth; plain password auth. Port 993: SSL; client cert auth. I found the archive http://www.dovecot.org/list/dovecot/2016-February/103067.html and followed it, but does not work, I see the following log in /var/log/maillog Aug 21 15:36:42 vps0 dovecot: master: Dovecot v2.2.25 (7be1766) starting up for imap (core dumps disabled) Aug 21 15:37:51 vps0 dovecot: auth: Error: BUG: Authentication client sent unknown handshake command: REQUEST?1997012993?3734?1?e067999d43eebcecf0c9d44a1c108d75?session_pid=3741?r... Aug 21 15:37:51 vps0 dovecot: imap: Error: Authentication server didn't send valid SPID as expected: MECH#011PLAIN#011plaintext Aug 21 15:37:51 vps0 dovecot: imap: Error: Disconnected from auth server, aborting (client-pid=3734 client-id=1) Aug 21 15:37:51 vps0 dovecot: imap-login: Internal login failure (pid=3734 id=1) (internal failure, 1 successful auths): user=<contact>, method=PLAIN, rip=212.104.147.161, lip=46.30.14.36, mpid=3741, TLS, session=<UkXhtpY6W8XUaJOh> Aug 21 15:37:51 vps0 dovecot: imap-login: Disconnected (no auth attempts in 0 secs): user=<>, rip=212.104.147.161, lip=46.30.14.36, TLS handshaking: SSL_accept() failed: error:140D9115:SSL routines:SSL_GET_PREV_SESSION:session id context uninitialized, session=<nkrktpY6XMXUaJOh> Can anyone advice any solution? Dovecot version: 2.2.25 (7be1766) Operating system:CentOS 7, 64bit, selinux is off. CPU architecture: Intel x86 64bit. Filesystem: xfs # /usr/local/bin/doveconf -n # 2.2.25 (7be1766): /usr/local/etc/dovecot/dovecot.conf # OS: Linux 3.10.0-327.28.2.el7.x86_64 x86_64 CentOS Linux release 7.2.1511 (Core) auth_mechanisms = plain login auth_ssl_username_from_cert = yes disable_plaintext_auth = no mail_location = maildir:~/Maildir 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 service auth-ssl { executable = auth -o auth_ssl_require_client_cert=yes unix_listener auth-master-ssl { mode = 0666 } unix_listener login/login-ssl { mode = 0666 } } service imap-login-ssl { chroot = login executable = imap-login -l imap-ssl login-ssl inet_listener imaps { port = 993 ssl = yes } user = $default_login_user } service imap-login { inet_listener imaps { port = 0 } } service imap-ssl { executable = imap -a auth-master-ssl unix_listener login/imap-ssl { user = $default_login_user } } ssl_ca = </etc/SslCert/dovecot/2016080505CAcert.WithCrl.pem ssl_cert = </etc/SslCert/dovecot/2016080506cert.pem ssl_key = </etc/SslCert/dovecot/2016080506PrivateKey.NoPassPhrase.pem userdb { driver = passwd } protocol imap { auth_ssl_require_client_cert = no ssl_require_crl = no ssl_verify_client_cert = no } protocol imaps { auth_ssl_require_client_cert = yes ssl_require_crl = yes ssl_verify_client_cert = yes } #

1 0

Re: Crash on opening mailbox
by Aki Tuomi 21 Aug '16

21 Aug '16

So it seems. Sorry must've missed them. ---Aki TuomiDovecot oy -------- Original message --------From: Ladislav Laska <laska(a)kam.mff.cuni.cz> Date: 21/08/2016 13:59 (GMT+02:00) To: Aki Tuomi <aki.tuomi(a)dovecot.fi> Cc: dovecot(a)dovecot.org Subject: Re: Crash on opening mailbox Hi! dovecot -n and backtrace are both attached in my original email, due to their size. Did the attachments not arrive? The relevant log does not contain much more than the trace, but here it is: Aug 21 12:58:28 ibex dovecot: imap-login: Login: user=<krakonos>, method=PLAIN, rip=77.48.73.189, lip=78.108.107.19, mpid=17785, TLS, session=<Q5igz5I66sxNMEm9> Aug 21 12:58:28 ibex dovecot: imap(krakonos): Debug: Effective uid=1000, gid=100, home=/home/krakonos Aug 21 12:58:28 ibex dovecot: imap(krakonos): Debug: Namespace inbox: type=private, prefix=, sep=, inbox=yes, hidden=no, list=yes, subscriptions=yes location=mbox:~/.mbox Aug 21 12:58:28 ibex dovecot: imap(krakonos): Debug: mbox: INBOX defaulted to /home/krakonos/.mbox/inbox Aug 21 12:58:28 ibex dovecot: imap(krakonos): Debug: fs: root=/home/krakonos/.mbox, index=, indexpvt=, control=, inbox=/home/krakonos/.mbox/inbox, alt= Aug 21 12:58:29 ibex dovecot: imap(krakonos): Panic: file ../../../src/lib/array.h: line 219 (array_idx_i): assertion failed: (idx * array->element_size < array->buffer->used) Aug 21 12:58:29 ibex dovecot: imap(krakonos): Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(+0x8d91e) [0x7fa68fb6a91e] -> /usr/lib64/dovecot/libdovecot.so.0(+0x8da0a) [0x7fa68fb6aa0a] -> /usr/lib64/dovecot/libdovecot.so.0(i_fatal+0) [0x7fa68fb08fce] -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0x79e56) [0x7fa68fe6ae56] -> /usr/lib64/dovecot/libdovecot-storage.so.0(index_mail_get_first_header+0xd6) [0x7fa68fe6b2a6] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_get_first_header+0x3d) [0x7fa68fe1e93d] -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0x8de70) [0x7fa68fe7ee70] -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0x8e062) [0x7fa68fe7f062] -> /usr/lib64/dovecot/libdovecot.so.0(i_stream_read+0x53) [0x7fa68fb74e03] -> /usr/lib64/dovecot/libdovecot.so.0(i_stream_read_data+0x3d) [0x7fa68fb7583d] -> /usr/lib64/dovecot/libdovecot.so.0(message_parse_header_next+0x72) [0x7fa68fb56042] -> /usr/lib64/dovecot/libdovecot.so.0(+0x736c1) [0x7fa68fb506c1] -> /usr/lib64/dovecot/libdovecot.so.0(i_stream_read+0x53) [0x7fa68fb74e03] -> /usr/lib64/dovecot/libdovecot.so.0(i_stream_read_data+0x3d) [0x7fa68fb7583d] -> /usr/lib64/dovecot/libdovecot.so.0(message_parse_header_next+0x72) [0x7fa68fb56042] -> /usr/lib64/dovecot/libdovecot.so.0(+0x736c1) [0x7fa68fb506c1] -> /usr/lib64/dovecot/libdovecot.so.0(i_stream_read+0x53) [0x7fa68fb74e03] -> /usr/lib64/dovecot/libdovecot.so.0(i_stream_read_data+0x3d) [0x7fa68fb7583d] -> /usr/lib64/dovecot/libdovecot.so.0(message_get_header_size+0x74) [0x7fa68fb59d64] -> /usr/lib64/dovecot/libdovecot-storage.so.0(imap_msgpart_open+0x317) [0x7fa68fea7ff7] -> dovecot/imap() [0x41d4ae] -> dovecot/imap() [0x41b9fc] -> dovecot/imap(imap_fetch_more+0x3a) [0x41ca0a] -> dovecot/imap(cmd_fetch+0x32c) [0x40f57c] -> dovecot/imap(command_exec+0x9c) [0x41a29c] -> dovecot/imap() [0x418772] -> dovecot/imap() [0x418800] -> dovecot/imap(client_handle_input+0x175) [0x418b95] Aug 21 12:58:29 ibex dovecot: imap(krakonos): Fatal: master: service(imap): child 17785 killed with signal 6 (core dumped) On Sat, Aug 20, 2016 at 01:25:01AM +0300, Aki Tuomi wrote: > > > On August 19, 2016 at 10:00 PM Ladislav Laska <laska(a)kam.mff.cuni.cz> wrote: > > > > > > Hi! > > > > I'm currently experiencing a crash of dovecot 2.2.25 on Gentoo, upon opening > > mailbox. The crash only triggers on opening inbox, other mailboxes seem to > > work fine. It happens every time, and can be reproduced on request. I also > > briefly tried 2.2.19, and it behaves the same. > > > > The bug seems to be triggered by some mail, as I encountered it previously > > and fixed by removing some spam. I guess it might be malformed header of > > some kind. I can open the mailbox locally using mutt, but fail to do so > > remotely (using mutt or K-9 mail on android). Unforunately, I haven't been > > able to isolate the specific mail, as when I create a new mailbox, dovecot > > refuses to open it: > > > > [CANNOT] Mailbox isn't a valid mbox file (0.000 + 0.000 secs). > > > > I'm not really sure what's going on and will investigate further once I find > > some time to do so. > > > > I also experienced a similar problem on opening a specific mail, but it's > > much harder to reproduce and I currently don't have an example. The crash > > looks very similar, and only happens on first attempt to open a specific > > mail, it always works later on. > > > > I'm attaching a stack trace and dovecot -n. I'm also willing to send the > > binary and core dump, but not publicly, as I'm not eager to share whatever's > > inside with the whole world. > > > > Other than what I mentioned, I'm running pretty standard setup, with postfix > > on Gentoo x86_64, ext4 fs, quota and disk space is plentiful. The delivery > > agent is dovecot itself, in postfix/main.cf I have: > > > > mailbox_command = /usr/libexec/dovecot/deliver > > > > I'm using sieve script to file my mail, but the problem manifested even > > before when I was still using procmail to deliver my mail (I migrated > > because I had doubts about procmail and dovecot lock cooperation) > > > > I'll keep my mailbox corrupted for a few more days, and access the mail only > > locally, hoping to test a potential fix. Let me know if you need any more > > info/experimentation. Also, if you know a good way to find the mail that > > causes the trouble out of the core, let me know, I'd be glad to forward it > > for testing. > > > > Thanks and I hope we can find (and fix) the problem! > > > > -- S pozdravem Ladislav Láska > > <laska(a)kam.mff.cuni.cz> > > Katedra Aplikované Matematiky, MFF UK tel.: +420 739 464 167 > > Hi! > > Please provide > > doveconf -n > > relevant log files (or at least anything you care to share) > > gdb /path/to/binary /path/to/core > bt full > > --- > Aki Tuomi > Dovecot Oy -- S pozdravem Ladislav Láska <laska(a)kam.mff.cuni.cz> Katedra Aplikované Matematiky, MFF UK tel.: +420 739 464 167

1 0

Dovecot & Thunderbird on shared mbox
by Ruga 19 Aug '16

19 Aug '16

Occasional error from TB when selecting a dovecot's shared mbox: "Unable to open the summary file for [shared]" "Perhaps there was an error on disk, or the full path is too long." The server's disk is clear, and the longest full path is [a-zA-Z\/\.]{46}. The error occurs occasionally.

2 2

POP3 strange logging behavior after upgrade from 2.2.13 to 2.2.25
by Iavor Stoev 19 Aug '16

19 Aug '16

Hello, I've tested the patch and can confirm that the issue is resolved. Thank you for your assistance! Iavor Stoev Project Manager // Head of System & Network Administration Department ICDSoft Ltd - http://icdsoft.com On 18.8.2016 г. 18:14 ч., dovecot-request(a)dovecot.org wrote: > Hi! > > This has been now fixed in > https://github.com/dovecot/core/commit/7424d35ff1b7d17c0caf7b426c0ef3c2b822… > > Aki Tuomi > Dovecot Oy

1 0

What might cause messages delivered with dovecot-lda to be "invisible" to IMAP clients?
by Ben Johnson 19 Aug '16

19 Aug '16

Hello! I'm attempting to use dovecot-lda, and for whatever reason, messages that I send with it are not visible in my IMAP client. $ dovecot --version 2.2.22 (fe789d2) (Full "doveconf -n" output is at the bottom of this message!) Here's the the sequence of commands that I'm using: # su vmail $ echo 'This is a test message.' > /tmp/test.txt $ stat /tmp/test.txt File: '/tmp/test.txt' Size: 24 Blocks: 8 IO Block: 4096 regular file Device: fd01h/64769d Inode: 783925 Links: 2 Access: (0664/-rw-rw-r--) Uid: ( 5000/ vmail) Gid: ( 5000/ vmail) Access: 2016-08-18 20:49:38.419011552 -0400 Modify: 2016-08-18 20:49:07.178995015 -0400 Change: 2016-08-18 20:49:38.191011425 -0400 Birth: - $ /usr/lib/dovecot/dovecot-lda -d "test(a)example.com" -p "/tmp/test.txt" When I do this, the destination mailbox acts like there's a new message (I'm using Thunderbird, and the mailbox is highlighted in blue and bolded, which is the "new mail" behavior in this client). But when I "check my inbox", i.e., click on the Inbox, I don't see the new message. With regard to the filesystem, the message is present and contains the intended contents. Here's the "stat" output: $ stat /var/vmail/example.com/ben/Maildir/cur/1471567777.M685753P32257.example.com,S=24:2, File: '/var/vmail/example.com/ben/Maildir/cur/1471567777.M685753P32257.example.com,S=24:2,' Size: 24 Blocks: 8 IO Block: 4096 regular file Device: fd01h/64769d Inode: 783925 Links: 2 Access: (0664/-rw-rw-r--) Uid: ( 5000/ vmail) Gid: ( 5000/ vmail) Access: 2016-08-18 20:51:05.647059340 -0400 Modify: 2016-08-18 20:50:58.543055378 -0400 Change: 2016-08-18 20:50:58.543055378 -0400 Birth: - Might anyone know why I'm not "seeing" this message in my IMAP client? Interestingly, I tried another IMAP client (Blue Mail for Android), and I can actually see the messages there, but they appear in the Inbox as: (No subject) <Empty Message> When I click on the messages, Blue Mail simply displays "No text", without the quotes. Surely, I'm overlooking something simple... Thank you for any help here! -Ben Full "doveconf -n" output: $ doveconf -n # 2.2.22 (fe789d2): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.13 (7b14904) # OS: Linux 4.4.0-34-generic x86_64 Ubuntu 16.04.1 LTS auth_mechanisms = plain login disable_plaintext_auth = no 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 { antispam_backend = pipe antispam_debug_target = syslog antispam_pipe_program = /bin/bash antispam_pipe_program_args = /usr/local/bin/sa-learn-pipe.sh antispam_pipe_program_notspam_arg = --ham antispam_pipe_program_spam_arg = --spam antispam_pipe_tmpdir = /tmp antispam_spam_pattern_ignorecase = SPAM;JUNK antispam_trash_pattern_ignorecase = trash;Deleted * antispam_verbose_debug = 1 quota = dict:user::file:/var/vmail/%d/%n/.quotausage quota_rule2 = Trash:storage=+100M quota_rule3 = Junk:ignore quota_rule4 = INBOX:storage=+100M quota_warning = storage=100%% quota-reached 100 %u %d quota_warning2 = storage=95%% quota-warning 95 %u %d quota_warning3 = storage=80%% quota-warning 80 %u %d quota_warning4 = -storage=100%% quota-below below %u %d sieve = /var/vmail/%d/%n/.sieve sieve_max_redirects = 25 } postmaster_address = postmaster(a)example.com 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 } } service quota-below { executable = script /usr/local/bin/quota-below.sh unix_listener quota-below { group = vmail mode = 0666 user = vmail } user = vmail } service quota-reached { executable = script /usr/local/bin/quota-reached.sh unix_listener quota-reached { group = vmail mode = 0666 user = vmail } user = vmail } service quota-warning { executable = script /usr/local/bin/quota-warning.sh unix_listener quota-warning { group = vmail mode = 0666 user = vmail } user = vmail } ssl_cert = </etc/postfix/smtpd.cert ssl_key = </etc/postfix/smtpd.key ssl_protocols = !SSLv2 !SSLv3 userdb { driver = prefetch } userdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } protocol imap { mail_plugins = quota imap_quota antispam } protocol pop3 { mail_plugins = quota pop3_uidl_format = %08Xu%08Xv } protocol lda { mail_plugins = sieve quota } protocol lmtp { mail_plugins = quota sieve postmaster_address = webmaster@localhost }

1 1

Quota issue: enforced, but reporting issue
by dovecot＠avv.solutions 18 Aug '16

18 Aug '16

Hello everyone, I face the following challenge: - dovecot 2.2.13 - userdb: passwd-file - quota enabled: -- default 1GB -- changed for some users thru users file: user@domain:passwd::::::userdb_quota_rule=*:storage=15M - when sending a message to this user while near quota, warnings are correctly triggered => *OK* - when sending a message to this user while over quota, message is refused => *OK* - when checking quota from mail client (eg Thunderbird 45.2), reported quota is.. 1GB => *NOK* - some config: mail_plugins = quota notify acl plugin { acl_shared_dict = file:/sd/MAIL_IMAP_POP/%d/shared-mailboxes quota = maildir:User quota:ns= quota_exceeded_message = Storage quota for this account has been exceeded, please try again later. quota_rule = *:storage=1G quota_rule2 = Trash:storage=+10%% quota_rule3 = Spam:storage=+20%% quota_status_nouser = DUNNO quota_status_overquota = 552 5.2.2 Mailbox is full quota_status_success = DUNNO quota_warning = storage=90%% quota-warning 90 %u %d quota_warning2 = storage=75%% quota-warning 75 %u %d } protocol imap { mail_plugins = quota notify acl imap_quota imap_acl service replication-notify-fifo { name = aggregator } service anvil-auth-penalty { name = anvil } service auth-worker { name = auth-worker } service auth-client { name = auth } service config { name = config } service dict { name = dict } service login/proxy-notify { name = director } service dns-client { name = dns_client } service doveadm-server { name = doveadm } service imap { name = imap-login } service imap-urlauth { name = imap-urlauth-login } service imap-urlauth-worker { name = imap-urlauth-worker } service token-login/imap-urlauth { name = imap-urlauth } service login/imap { name = imap } service indexer-worker { name = indexer-worker } service indexer { name = indexer } service ipc { name = ipc } service lmtp { name = lmtp } service log-errors { name = log } service pop3 { name = pop3-login } service login/pop3 { name = pop3 } service replicator-doveadm { name = replicator } service login/ssl-params { name = ssl-params } service stats-mail { name = stats } } - 90-quota: passdb { driver = passwd-file args = scheme=CRYPT username_format=%u /etc/dovecot/users } userdb { driver = passwd-file args = username_format=%u /etc/dovecot/users # Default fields that can be overridden by passwd-file #default_fields = quota_rule=*:storage=1G # Override fields from passwd-file #override_fields = home=/home/virtual/%u } Any idea? Already spent hours on this. Thank you in advance for the help. Cheers A.

1 0

Reporting on CephFS being ready to use with Dovecot
by Daniel van Ham Colchete 18 Aug '16

18 Aug '16

I would like to report that from version 10.2.3 on (next release), Ceph FS is working really well with Dovecot systems. For those that don't know, Ceph is a "distributed object store and file system designed to provide excellent performance, reliability and scalability.". We have used it here since 2013 very successfully, but never with our Dovecot setup. For more information go on http://ceph.com/. Since Ceph Jewel (the current version), Ceph FS is considered production ready by their team. With Ceph FS you have a cache-coherent POSIX-compliant [1] clustered file system, without most of the NFS shortcomings. Ceph have very nice features like online upgrades, online maintenance, constant deep scrubbing of replicated data, cache tiering (HD -> SSD -> etc), erasure coding (clustered RAID6 for really old email - I'm not using), etc. Ceph is very complex to operate but very flexible and robust. This year we moved our Dovecot servers to a Ceph based system, found one bug there (http://tracker.ceph.com/issues/15920) when Dovecot's LMTP was delivery an email, and the fix is about to be released on version 10.2.3. I have been using a fix-build here for a couple of months without issue. So, now I'm glad to share with you guys that it works really well! My setup involves two clusters, each with about 30k-40k users. Each cluster will have two HD storages (with 6TB HDs), two SSD storages (with Intel 480GB SSDs) and two frontends. In a few months will add a third server of each type. Clusters work better with 3's. Here we used mdbox as it is better performant on Ceph for maintenance tasks, since each file is an object on Ceph and maintenance costs increase with the number of objects. We created two base directories: - /srv/dovecot/mail/%d/%n - stored on HDs with the most recent files cached on SSDs, thanks to Ceph Cache Tiering. Also, the directory structure itself is stored on SSDs, so dir listings are very fast (Ceph FS Metadata). - /srv/dovecot/index/%d/%n - stored only on SSDs, thanks for Ceph FS file layout. On our setup about 17% of the IOPs are going to HDs, the rest will go to SSDs, even though SSDs are less than 5% of the space. This is a matter of tuning the cache tiering parameters, but we didn't look at that yet. That setup is working like a charm, performance is about 53% better than when we were using NFS on the same hardware. Our previous DRBD+Heartbeat setup didn't allow for online maintenance and had a few problems. Now we can do 100% online maintenance on storage without users noticing, and on frontends with just a reconnect but without any downtime. Ceph is hard to learn at first but those with bigger setups and stronger SLAs will want to take a look at that. I really recommend that the Dovecot community take at look at that setup. Good luck! Best, Daniel Colchete [1] http://docs.ceph.com/docs/hammer/dev/differences-from-posix/

3 2

POP3 strange logging behavior after upgrade from 2.2.13 to 2.2.25
by Iavor Stoev 18 Aug '16

18 Aug '16

Hello, After the upgrade from Dovecot version 2.2.13 to 2.2.25, we experience the following strange behavior with POP3 logging. When a connection is closed with reason "Connection closed" & "Disconnected for inactivity", the number of deleted mails is missing. Like del=/1166 & del=/4138 from the example bellow. With Dovecot 2.2.13: Feb 14 03:35:20 serverXYZ dovecot: pop3(user(a)domain.com): Connection closed top=0/0, retr=0/0, del=0/946, size=39500197 Feb 15 16:49:18 serverXYZ dovecot: pop3(user(a)domain.com): Disconnected for inactivity top=0/0, retr=0/0, del=0/739, size=52319632 With Dovecot 2.2.25: Jul 31 02:56:03 serverXYZ dovecot: pop3(user(a)domain.com): Connection closed top=1/1380, retr=0/0, del=/4138, size=284167741 Jul 31 02:34:47 serverXYZ dovecot: pop3(user(a)domain.com): Disconnected for inactivity top=0/0, retr=0/0, del=/1166, size=111425436 For sessions completed normally, everything works fine with both Dovecot versions: Jul 31 06:55:48 serverXYZ dovecot: pop3(user(a)domain.com): Disconnected: Logged out top=0/0, retr=0/0, del=0/0, size=0 Jul 31 02:36:59 serverXYZ dovecot: pop3(user(a)domain.com): Disconnected: Logged out top=0/0, retr=1/18821, del=1/1, size=18803 Please advise if this behavior is normal and if yes how should we read entries like "del=/4138"? Thank you Iavor Stoev Project Manager // Head of System & Network Administration Department ICDSoft Ltd - http://icdsoft.com

2 1