August 2014 - dovecot

poolmon improvements
by Timo Sirainen 11 Aug '14

11 Aug '14

I've been planning to improve poolmon failure checking for a long time already, but I still haven't managed to get to it. Maybe somebody else has more time, so here's a feature request for anyone to implement: poolmon currently gives up immediately if the first check to any service fails. It really should be trying multiple times over multiple seconds before giving up. I think ideally it would be: - Individual check timeout could still be the default 5 seconds - Add full check time setting, which could be e.g. 15 seconds. If all checks fail during this time then disable the host. - If request fails because connection gets rejected, retry quickly, e.g. after 0,1 seconds - If check fails because of protocol errors, wait for a long time, e.g. 1 second So this would avoid backend being removed in situations where it really shouldn't be removed: - Dovecot restarts - Dovecot reloads - load spikes and other random issues that cause temporary problems Especially the load spike is an annoying issue which my plan doesn't even fully solve. The solution to fix a heavily overloaded cluster isn't really to start removing all of its backends that are busy working..

1 0

Frequent error: unknown namespace Trash
by Michael Ludwig 11 Aug '14

11 Aug '14

Hello to all of you! ;-) My first post on this list. I frequently get this error in dovecot.log every time a user logs in and out: ============================= imap(mailaddress): Error: quota: Unknown namespace: Trash ============================= When I change my conf.d/90-quota.conf from "Trash" to ".Trash" (as this is the imap/maildir folder name, the error stays the same, but with the ".Trash" in dovecot.log This is what my 90-quoato.conf looks like: ============================= plugin { quota_rule = *:storage=2G quota_rule2 = Trash:storage=+100M quota_grace = 10%% } ============================= Where can I start my search, what is going wrong? Just for letting you know: This mailserver is a fresh and clean setup. I am using postfix/dovecotvimbadmin/mysql/spamassassin/clamsmtp. Cheers, Michael

1 0

postfix-dovecot Auth USER lookup failed
by Timothy Murphy 10 Aug '14

10 Aug '14

I'm running postfix + dovecot on my CentOS-7 home server. When I send myself a message I get this error message in /var/log/maillog: Aug 9 12:59:57 alfred postfix/lmtp[31336]: B0D02220748: to=<tim(a)localhost.gayleard.eu>, orig_to=<tim@localhost>, relay=alfred.gayleard.eu[private/dovecot-lmtp], delay=475, delays=474/0.03/0.02/0.09, dsn=4.3.0, status=deferred (host alfred.gayleard.eu[private/dovecot-lmtp] said: 451 4.3.0 <tim(a)localhost.gayleard.eu> Internal error occurred. Refer to server log for more information. (in reply to RCPT TO command)) and in /var/log/dovecot I read Aug 09 13:13:03 auth-worker(31472): Error: passwd(tim(a)localhost.gayleard.eu): getpwnam() failed: Address family not supported by protocol Aug 09 13:13:03 lmtp(31470): Error: user tim(a)localhost.gayleard.eu: Auth USER lookup failed It seems that USER is set to tim(a)localhost.gayleard.eu rather than tim . I am including the line mailbox_transport = lmtp:unix:private/dovecot-lmtp in /etc/postfix/main.cf . If I omit this line so that postfix sends email directly to ~/Maildir I have no problem - except that spam is not being filtered. I give the output of postconf -n below. Any advice or enlightenment gratefully received. Output of postconf -n ---------------------- [tim@alfred ~]$ cat /tmp/postconf alias_database = hash:/etc/aliases alias_maps = hash:/etc/aliases 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 home_mailbox = Maildir/ html_directory = no inet_interfaces = all inet_protocols = all mail_owner = postfix mailbox_transport = lmtp:unix:private/dovecot-lmtp mailq_path = /usr/bin/mailq.postfix manpage_directory = /usr/share/man mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain mydomain = gayleard.eu myhostname = alfred.gayleard.eu mynetworks = 192.168.0.0/24, 127.0.0.0/8 myorigin = $mydomain newaliases_path = /usr/bin/newaliases.postfix queue_directory = /var/spool/postfix readme_directory = /usr/share/doc/postfix-2.6.6/README_FILES relay_domains = relayhost = out.alice.it sample_directory = /usr/share/doc/postfix-2.6.6/samples sendmail_path = /usr/sbin/sendmail.postfix setgid_group = postdrop smtp_sasl_auth_enable = yes smtp_sasl_password_maps = hash:/etc/postfix/password smtp_sasl_security_options = smtpd_milters = unix:/var/run/spamass-milter/postfix/sock unknown_local_recipient_reject_code = 550 ---------------------- -- Timothy Murphy e-mail: gayleard /at/ eircom.net School of Mathematics, Trinity College, Dublin 2, Ireland

2 2

Dovecot v2.2 FTS is not indexing "text/html" emails...
by Akash 09 Aug '14

09 Aug '14

Hi, I am not sure its intended or a fault in the newest Dovecot versions. I have been using Dovecot v1.2.15 on Debian squeeze and FTS is working as expected. When I search a quoted string "very good", I get 107 results including plain and HTML emails which have this phrase. In order to compare the benefits of lucene over squat, I recently started testing dovecot v2.2.13 on Debian Sid with the same maildir content. But now the same search "very good" yielded just 8 results. I thought it could be some problem with lucene so I tried switching to squat and got 107 results again. After this I deleted the old squat search index files created by v1.2.15 and re-indexed the mail-box by using doveadm index command. Now the same squat search is giving 8 results just as lucene. So I have realized that its not a problem with just lucene but FTS in newer dovecot isn't indexing those emails which have Content-type as text/html. Thus if a mail is like this: Content-Type: text/html <b>He is very good.</b> It isn't shown in search by the squat indexes created using dovecot v2.2.13. I have done further testing on some sample emails which confirmed this behavior. Why is this so? -Regards, Akash

1 0

Converting maildir files from quoted-printable to 8bit
by Andrzej A. Filip 09 Aug '14

09 Aug '14

How to easily convert maildir files from (single part) quoted-printable to 8bit encoding? [I would like to ease access to sent/posted archives.]

1 0

Throttling pop3-login connections
by Alex 09 Aug '14

09 Aug '14

Hi, I have a fedora20 system with dovecot-2.2.13 running various services, including pop3. I'm noticing some users are frequently hamming pop3, and wondered if this was normal, or something I should be investigating? Aug 8 14:05:20 email dovecot: pop3-login: Login: user=<user1>, method=PLAIN, rip=97.77.115.121, lip=192.168.1.1, mpid=30509, session=<DnRtDCIAUQBhTXN5> Aug 8 14:05:21 email dovecot: pop3(user1): Disconnected: Logged out top=0/0, retr=0/0, del=0/15, size=5693601 So it is immediately followed by a logout, but when there are 50 of them successively in a five minute period, I wondered if it is creating unnecessary overhead on the system? I suppose this most likely is how they have their email client configured, but wondered if some throttling would be necessary? Any advice would be most appreciated. Thanks, Alex

4 5

Re: postfix-dovecot via lmtp
by Reindl Harald 08 Aug '14

08 Aug '14

STOP to post HTML and convert even plaintext messages Am 04.08.2014 um 12:50 schrieb Timothy Murphy: > On Monday, August 04, 2014 12:14:44 PM Reindl Harald wrote: > > > >> > I read in /var/log/maillog > >> > > >> > Aug 4 11:29:13 alfred postfix/lmtp[14871]: 9C04C220A99: > >> > to=<tim(a)localhost.gayleard.eu>, orig_to=<tim@localhost>, > >> > relay=alfred.gayleard.eu[private/dovecot-lmtp], delay=971, > >> > delays=971/0.03/0.02/0.1, dsn=4.3.0, status=deferred > >> > (host alfred.gayleard.eu[private/dovecot-lmtp] said: 451 4.3.0 > >> > <tim(a)localhost.gayleard.eu> Internal error occurred. > >> > Refer to server log for more information. (in reply to RCPT TO > >> > command)) > > > >> "Refer to server log for more information" comes from dovecot lmtpd > >> so look there and post the output of "doveconf -n" > > > > Thanks very much for your response. > > > > The only information in /var/log/dovecot > > (where I send dovecot debug and info logs) is > > Aug 04 11:29:13 lmtp(14872): > > Debug: none: root=, index=, indexpvt=, control=, inbox=, alt= > > Aug 04 11:29:13 lmtp(14872): > > Info: Connect from local > > Aug 04 11:29:13 lmtp(14872): > > Debug: auth input: > > Aug 04 11:29:13 lmtp(14872): > > Info: Disconnect from local: Successful quit > > > > The output of "doveconf -n" is > > ------------------------- > > # 2.2.10: /etc/dovecot/dovecot.conf > > # OS: Linux 3.10.0-123.4.4.el7.x86_64 x86_64 CentOS Linux release 7.0.1406 (Core) > > debug_log_path = /var/log/dovecot > > info_log_path = /var/log/dovecot > > listen = * > > log_path = /var/log/dovecot > > login_trusted_networks = 192.168.2.0/24 > > mail_debug = yes > > mail_gid = 1000 > > mail_location = maildir:~/Maildir > > mail_uid = 1000 > > 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 > ihave > > mbox_write_locks = fcntl > > 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 > > } > > plugin { > > sieve = ~/.sieve/dovecot.sieve > > sieve_dir = ~/.sieve > > } > > protocols = imap pop3 lmtp sieve > > service imap-login { > > inet_listener imap { > > port = 143 > > } > > inet_listener imaps { > > port = 993 > > ssl = yes > > } > > } > > service lmtp { > > unix_listener /var/spool/postfix/private/dovecot-lmtp { > > group = postfix > > mode = 0777 > > user = postfix > > } > > } > > service managesieve-login { > > inet_listener sieve { > > port = 4190 > > } > > } > > ssl = required > > ssl_cert = </etc/pki/dovecot/certs/dovecot.pem > > ssl_key = </etc/pki/dovecot/private/dovecot.pem > > userdb { > > driver = passwd > > } > > protocol lmtp { > > mail_plugins = " sieve" > > } > > protocol lda { > > mail_plugins = " sieve" > > } > > protocol sieve { > > managesieve_notify_capability = fileinto reject envelope environment mailbox date > > } > > ------------------------- > > > > > > -- > > Timothy Murphy > > e-mail: gayleard /at/ eircom.net > > School of Mathematics, Trinity College, Dublin 2, Ireland

4 3

postfix-dovecot via lmtp
by Timothy Murphy 08 Aug '14

08 Aug '14

I've been trying for some days to get postfix + dovecot + pigeonhole/sieve working on a CentOS-7 home server. I think I may have detected the problem; I read in /var/log/maillog Aug 4 11:29:13 alfred postfix/lmtp[14871]: 9C04C220A99: to=<tim(a)localhost.gayleard.eu>, orig_to=<tim@localhost>, relay=alfred.gayleard.eu[private/dovecot-lmtp], delay=971, delays=971/0.03/0.02/0.1, dsn=4.3.0, status=deferred (host alfred.gayleard.eu[private/dovecot-lmtp] said: 451 4.3.0 <tim(a)localhost.gayleard.eu> Internal error occurred. Refer to server log for more information. (in reply to RCPT TO command)) (I've split one long line here.) 1) I see that the permissions on /var/spool/postfix/private/ are [tim@alfred ~]$ ls -ls /var/spool/postfix/ 4 drwx------. 2 postfix root 4096 Aug 4 11:30 private The socket dovecot-lmtp setup by postfix is in this directory; does dovecot need permission to access this? 2) I see that this mail (a test email from me) was deferred. What exactly does this mean? Where is the mail stored? I couldn't find it anywhere. (It has already been brought to the server by fetchmail.) 3) Am I right in thinking that there are 2 alternatives to dovecot/sieve a) amavisd-new with postfix + spamassassin b) postfix + procmail ? 4) I remember seeing a posting (probably not in this mailing list) describing how one can trace the progress of email through the server. Unfortunately I didn't note the URL, and now cannot find it. Does anyone have a pointer to such a document? As will probably be obvious, I am not at all clear how postfix and dovecot fit together if one introduces lmtp. I take it that without lmtp (or similar) postfix just delivers email to ~/Maildir/cur (in my case), and dovecot is not involved at all until a client (KMail in my case) looks at email? -- Timothy Murphy e-mail: gayleard /at/ eircom.net School of Mathematics, Trinity College, Dublin 2, Ireland

2 2

Dovecot, Thunderbird and messages in wrong folder
by Gerhard Wiesinger 08 Aug '14

08 Aug '14

Hello, Sometimes it happens that messages (e.g. one or two) appear in wrong folders in Thunderbird (latest version, also past versions, different computers, also Earlybird). When I repair the folder (folder/Settings/Repair Folder) in Thunderbird, the folder is correct then. It happens on my new server with Fedora 20, Dovecot 2.2.13 and Maildir but it also happened on my old server with Fedora 1, Dovecot 2.2.13 and mbox. Has anyone the same issue? Any guess whether it might be a thunderbird or dovecot issue? Anyone has the same issues with thunderbird and a different IMAP server (e.g. cyrus)? Thank you. Ciao, Gerhard Config (only relevant parts here): # 2.2.13: /etc/dovecot/dovecot.conf # OS: Linux 3.15.8-200.fc20.x86_64 x86_64 Fedora release 20 (Heisenbug) auth_mechanisms = plain login lda_mailbox_autocreate = yes listen = * mail_gid = vmail mail_home = /home/vmail/%n mail_location = maildir:~/Maildir mail_max_userip_connections = 20 mail_plugins = " stats mailbox_alias zlib" mail_uid = vmail protocols = imap lmtp sieve service imap-login { inet_listener imap { port = 0 } process_min_avail = 2 service_count = 0 } service imap { client_limit = 20 executable = imap postlogin process_limit = 20 } service lmtp { inet_listener lmtp { port = 24 } process_min_avail = 2 } service managesieve-login { process_min_avail = 1 } service postlogin { executable = script-login -d rawlog } service stats { fifo_listener stats-mail { mode = 0600 user = vmail } } ssl_cert = </etc/pki/dovecot/imap.crt ssl_key = </etc/pki/dovecot/imap.key submission_host = 127.0.0.1 userdb { args = username_format=%n /etc/dovecot/users driver = passwd-file } protocol imap { imap_client_workarounds = tb-extra-mailbox-sep mail_plugins = " stats mailbox_alias zlib imap_stats imap_zlib" } protocol lmtp { mail_plugins = " stats mailbox_alias zlib sieve" }

2 1

Dovecot and remote SASL Client via TLS
by Gerhard Wiesinger 08 Aug '14

08 Aug '14

Hello, Is it possible to configure Dovecot as SASL client for central authentication (also remotely via TCP/TLS)? Following use case: IMAP server (host 1) <=> Windows Domain Controller and /etc/shadow authenticator via pam (host2) Should work as: IMAP server (host 1) <=> SASL Client via TLS <=> Network <=> SASL Server via TLS <=> Local SASL via pam <=> Windows Domain Controller and /etc/shadow authenticator via pam (host2) Thank you. Ciao, Gerhard -- http://www.wiesinger.com/

1 2