- dovecot - dovecot.org

Dovecot/Sieve shortcuts?
by Adam Shostack 24 May '17

24 May '17

Hi, Is there a clean way to match on an email address the way procmail ^TO_ did? that was a macro which expanded to (^((Original-)?(Resent-)?(To|Cc|Bcc)|(X-Envelope |Apparently(-Resent)?)-To):(.*[^-a-zA-Z0-9_.])?) so you could write * ^TO_dovecot dovecot and grab messages to the list. In sieve, I find myseld writing ["To","cc"] and wonder if there's a better way. Adam

4 8

dovecot: auth-worker: Fatal: master: service(auth-worker): child XXXXX killed with signal 11
by dovecot＠jeffandjessi.com 24 May '17

24 May '17

Trying to track down a dovecot issue .... The error message is: dovecot: auth-worker: Fatal: master: service(auth-worker): child XXXXX killed with signal 11 (core not dumped - set service auth-worker { drop_priv_before_exec=yes }) The setup is dovecot 2.2.29.1 with passwd and mysql auth db's and a very basic config. both authentications work ... the symptom is that after a connection is made the auth worker loads and emails are downloaded and everything "is fine". However, about 30 second to a minute after the connection is done the process dies with the error message. Then the process starts all over with on the next checking of email ,but again everything "works" just seeing this error and the process dieing each time? enabled all extra verbose logging ,but nothing gives any clues.... Tried to enable core dumps ,but couldnt get core dumps to work ? The only thing is that a recently pkgsrc (netbsd) update create 2 packages, one for dovecot and one for mysql plugin , sense then now this error appears. ,but it appears the .so lib files are installed and linked correctly. Double checked all file permissions and user permissions as well as chroot , etc, etc, ,etc.... cant seem to narrow this one down .... any ideas on trouble shooting would be great .... even tried running a trace with gdb -p on the process ,but it just dies with a signal 11 ....

1 0

v2.2.30 release candidate released
by Timo Sirainen 24 May '17

24 May '17

https://dovecot.org/releases/2.2/rc/dovecot-2.2.30.rc1.tar.gz https://dovecot.org/releases/2.2/rc/dovecot-2.2.30.rc1.tar.gz.sig There are a couple of changes still coming, but now would be a good time to make sure anything unexpected hasn't broken. The final release should be out early next week. * auth: Use timing safe comparisons for everything related to passwords. It's unlikely that these could have been used for practical attacks, especially because Dovecot delays and flushes all failed authentications in 2 second intervals. Also it could have worked only when passwords were stored in plaintext in the passdb. * master process sends SIGQUIT to all running children at shutdown, which instructs them to close all the socket listeners immediately. This way restarting Dovecot should no longer fail due to some processes keeping the listeners open for a long time. + auth: Add passdb { mechanisms=none } to match separate passdb lookup + auth: Add passdb { username_filter } to use passdb only if user matches the filter. See https://wiki2.dovecot.org/PasswordDatabase + dsync: Add dsync_commit_msgs_interval setting. It attempts to commit the transaction after saving this many new messages. Because of the way dsync works, it may not always be possible if mails are copied or UIDs need to change. + imapc: Support imapc_features=search without ESEARCH extension. + imapc: Add imapc_features=fetch-bodystructure to pass through remote server's FETCH BODY and BODYSTRUCTURE. + imapc: Add quota=imapc backend to use GETQUOTA/GETQUOTAROOT on the remote server. + passdb imap: Add allow_invalid_cert and ssl_ca_file parameters. + If dovecot.index.cache corruption is detected, reset only the one corrupted mail instead of the whole file. + doveadm mailbox status: Add "firstsaved" field. + director_flush_socket: Add old host's up/down and vhost count as parameters - More fixes to automatically fix corruption in dovecot.list.index - dsync-server: Fix support for dsync_features=empty-header-workaround - imapc: Various bugfixes, including infinite loops on some errors - fts-lucene: Fix it to work again with mbox format - vpopmail: Fix compiling

1 0

Postfix and Dovecot SASL: log NTLM username
by Bradley Giesbrecht 24 May '17

24 May '17

dovecot 2.2.22 postfix 3.1.1 I’m seeing "SASL NTLM authentication failed: {long_hash}” in mail.log. Is there a way to log the SASL username? I think postfix is logging what Dovecot SASL is returning so I hope I am asking on the right list. Regards, Bradley Giesbrecht (pixilla)

2 5

dovecot: auth-worker: Fatal: master: service(auth-worker): child XXXXX killed with signal 11
by dovecot＠jeffandjessi.com 24 May '17

24 May '17

Trying to track down a dovecot issue .... The error message is: dovecot: auth-worker: Fatal: master: service(auth-worker): child XXXXX killed with signal 11 (core not dumped - set service auth-worker { drop_priv_before_exec=yes }) The setup is dovecot 2.2.29.1 with passwd and mysql auth db's and a very basic config. both authentications work ... the symptom is that after a connection is made the auth worker loads and emails are downloaded and everything "is fine". However, about 30 second to a minute after the connection is done the process dies with the error message. Then the process starts all over with on the next checking of email ,but again everything "works" just seeing this error and the process dieing each time? enabled all extra verbose logging ,but nothing gives any clues.... Tried to enable core dumps ,but couldnt get core dumps to work ? The only thing is that a recently pkgsrc (netbsd) update create 2 packages, one for dovecot and one for mysql plugin , sense then now this error appears. ,but it appears the .so lib files are installed and linked correctly. Double checked all file permissions and user permissions as well as chroot , etc, etc, ,etc.... cant seem to narrow this one down .... any ideas on trouble shooting would be great .... even tried running a trace with gdb -p on the process ,but it just dies with a signal 11 ....

2 1

[imaptest] Explaining errors
by aduprat 24 May '17

24 May '17

Hi, I'm an Apache James committer and we are curious to use imaptest in order to validate our IMAP protocol implementation. I'm using the nightlybuild : imaptest-20170506 I follow the examples given in the /T/ /est IMAP server compliancy/ examples https://imapwiki.org/ImapTest/Examples. And I wanted to analyse the errors reported, here are some: Error: user1(a)james.org[11]: seq too high (16 > 15, state=APPEND): * 16 FETCH (BODY[HEADER.FIELDS (In-Reply-To From) ] "From: marcelo(a)carpa.ciagri.usp.br") Error: user1(a)james.org[14]: seq too high (26 > 25, state=APPEND): * 26 FETCH (MODSEQ (6068) FLAGS (\Answered \Draft \Flagged)) Error: user1(a)james.org[14]: seq too high (20 > 16, state=APPEND): * 20 EXPUNGE Error: user10(a)james.org[18]: Keyword used without being in FLAGS: $Label1: * 1 FETCH (MODSEQ (8) FLAGS (\Answered \Deleted \Draft $Label1 $Label3)) Error: Checkpoint: Total RECENT count 6 larger than current message count 3 Warning: Disabling \Recent flag tracking Error: user1(a)james.org[5]: Owned flag changed: \Deleted: * 7 FETCH (FLAGS (\Answered \Deleted \Recent $Label2)) Error: user1(a)james.org[5]: STORE didn't return FETCH FLAGS for seq 18 (expunged=yes): 5.75 OK STORE completed. Error: user1(a)james.org[1]: SEARCH result missing seq 2 (uid 0): 1.13 OK SEARCH completed. Error: Keyword '$Label1' dropped, but it still had 1 references Do you have a link explaining what are those failures ? Is there a report by IMAP command giving us an idea about our compliancy ? Do you allow us to communicate about such tests, for example: - in news http://james.apache.org/#posts ? - in medium article ? We also would like to have James mentioned in the servers status page https://imapwiki.org/ImapTest/ServerStatus How may we help you for that ? Thanks in advance, -- Antoine Duprat Développeur LGS/OBM/R&D Committer/PMC Apache James ------------------ GROUPE LINAGORA 74-80 rue Roque de Fillol 92800 Puteaux +33 (0)8 10 25 12 51 +33 (0)6 45 63 27 17 aduprat(a)linagora.com ------------------ La présente transmission contient des informations confidentielles appartenant à Linagora, exclusivement destinées au(x) destinataire(s) identifié(s) ci-dessus. Si vous n'en faites pas partie, toute reproduction, distribution ou divulgation de tout ou partie des informations de cette transmission, ou toute action effectuée sur la base de celles-ci vous sont formellement interdites. Si vous avez reçu cette transmission par erreur, nous vous remercions de nous en avertir et de la détruire de votre système d'information. The present transmission contains privileged and confidential information belonging to Linagora, exclusively intended for the recipient(s) thereabove identified. If you are not one of these aforementioned recipients, any reproduction, distribution, disclosure of said information in whole or in part, as well as any action undertaken on the basis of said information are strictly prohbited. If you received the present transmission by mistake, please inform us and destroy it from your messenging and information systems.

2 2

Sender address when notifying original recipient
by Christoph Pleger 23 May '17

23 May '17

Hello, I am using sieve with notification of the original recipient in the case that an email has been identified to contain a virus. After upgrading dovecot from 2.2.21 to 2.2.29.1, I now detected that in these notifications, their sender address is now <postmaster@>, instead of <postmaster(a)mailserver.domain>, like it was before. Is it possible to revert to the old format? Regards Christoph

3 5

Dovecot pop3 feature
by Markus Eckerl 22 May '17

22 May '17

Hi all, we are using dovecot since several years without any problems or trouble. Now we are having trouble with a few of our customers - they are trying to fetch their emails every few seconds (3-5!). These customers are using Microsoft Exchange Server and also all of these customers are cared by the same IT Professional... Is it possible to send a pop3 "LOGIN-DELAY" if the customers last login is only a few seconds away? A simple firewall rule for rate limiting is not possible because most of them are business customers and they are connected using NAT. In RFC2449 <https://www.iana.org/assignments/pop3-extension-mechanism/pop3-extension-me…> I read that the pop3 capability "LOGIN-DELAY" exists. But it seems that dovecot does not offer this? Why? Kind regards Markus

2 1

Configuration is not working with Thunderbird
by Quark 22 May '17

22 May '17

Hi, I'm new to the list (and postfix / dovecot), so if I mistakenly omit something, then please forgive me. I cannot log into Thunderbird via IMAP with my configuration. However, I can check the mail of each user by logging into their user account & then using the "mail" command. Is there something that is wrong with my config to not allow me to log into Thunderbird (Version 52.1.1)? I'm using Postfix 3.1.0 if that helps. Any help would be greatly appreciated. Thanks! Here is the output of "|dovecot -n"|: # 2.2.22 (fe789d2): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.13 (7b14904) doveconf: Warning: NOTE: You can get a new clean config file with: doveconf -n > dovecot-new.conf doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:105: listen=..:port has been replaced by service { inet_listener { port } } doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:105: protocol { listen } has been replaced by service { inet_listener { address } } doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:106: ssl_listen=..:port has been replaced by service { inet_listener { port } } doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:106: protocol { ssl_listen } has been replaced by service { inet_listener { address } } # OS: Linux 4.4.0-77-generic x86_64 Ubuntu 16.04.2 LTS 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 imap-login { inet_listener imap { address = * port = 143 } inet_listener imaps { address = * port = 993 } } ssl_cert = </etc/letsencrypt/live/REDACTED/fullchain.pem ssl_key = </etc/letsencrypt/live/REDACTED/privkey.pem userdb { driver = passwd } protocol imap { imap_client_workarounds = tb-extra-mailbox-sep }

2 5

Backing up and restoring maildir folders
by Timothy D Legg 22 May '17

22 May '17

Hello, I am migrating to a different distribution of Linux that involves changing to an earlier version of dovecot (2.2.22 to 2.2.13). As part of this process, I will be copying several maildirs to the new machine. One of these has a number of files and directories that resemble this one example: cur/ dovecot.index dovecot.index.cache dovecot.index.log dovecot.mailbox.log dovecot-uidlist dovecot-uidvalidity dovecot-uidvalidity.59206030 .Drafts/ new/ .Sent/ subscriptions tmp/ .Trash/ Is it good enough to simply stop dovecot and tar this folder, and others like it, and copy them back to a similar location on the new installation? I haven't yet seen anything that resembles an official or standardized backup/recovery method for dovecot. With thanks and appreciation, Tim Legg

2 1