- dovecot - dovecot.org

Debian: Dovecot 2.3.0.1 won't start if dovecot-pop3d is missing
by Markus Schönhaber 03 Mar '18

03 Mar '18

Hello, given a Debian 9 system with Dovecot 2.2.34 installed from self-built packages made from the official tarball combined with Stephan Bosch's debian files (upgraded multiple times from packages made in a similar way). Today, I updated this system to 2.3.0.1 from the official repository at repo.dovecot.org. After the update, dovecot wouldn't start because of: > dovecot: master: Fatal: service(pop3) access(/usr/lib/dovecot/pop3) failed: No such file or directory Obviously, installing the dovecot-pop3d package, which provides the pop3 binary, made the error go away. Nevertheless, until v. 2.2.34 not installing the pop3 binary had never been a problem. Trying to solve this, I even commented the following sections in the config (which previously hadn't caused problems since the lines defining the ports etc. had already been commented): > 10-master.conf: > service pop3-login { > inet_listener pop3 { > #port = 110 > } > inet_listener pop3s { > #port = 995 > #ssl = yes > } > } > service pop3 { > # Max. number of POP3 processes (connections) > #process_limit = 1024 > } > 10-director.conf: > service pop3-login { > #executable = pop3-login director > } After those changes I had the configuration shown below, which produced the described error. Why would Dovecot insist that the pop3 binary has to exist on the system? BTW: Note the protocols = line in the doveconf -n output, whereas > # grep -R protocols /etc/dovecot/ > /etc/dovecot/dovecot.conf:# Most (but not all) settings can be overridden by different protocols and/or > /etc/dovecot/dovecot.conf:# Enable installed protocols > /etc/dovecot/dovecot.conf:!include_try /usr/share/dovecot/protocols.d/*.protocol > /etc/dovecot/conf.d/20-managesieve.conf:#protocols = $protocols sieve > /etc/dovecot/conf.d/10-ssl.conf:# SSL protocols to use > /etc/dovecot/conf.d/10-ssl.conf:#ssl_protocols = !SSLv2 > # ll /usr/share/dovecot/protocols.d/ > insgesamt 12 > -rw-r--r-- 1 root root 28 Mär 2 14:51 imapd.protocol > -rw-r--r-- 1 root root 28 Mär 2 14:51 lmtpd.protocol > -rw-r--r-- 1 root root 29 Mär 2 14:51 managesieved.protocol Regards mks doveconf -n # 2.3.0.1 (ffd8a29): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.0.1 (d33dca2) # OS: Linux 4.9.0-6-amd64 x86_64 Debian 9.3 ext4 auth_master_user_separator = * auth_mechanisms = plain login dict { quota = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext } imap_id_log = * mail_home = /var/spool/vmail/home/%d/%n mail_location = mdbox:/var/spool/vmail/mail/%d/%n mail_log_prefix = "%s[%p](%u)<%{session}>: " mail_plugins = " quota acl" managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date index ihave duplicate mime foreverypart extracttext namespace { list = children location = mdbox:/var/spool/vmail/mail/Public:INDEXPVT=/var/spool/vmail/home/Public prefix = Public/ separator = / subscriptions = no type = public } 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 = separator = / } passdb { args = /etc/dovecot/master-users driver = passwd-file master = yes pass = yes } passdb { args = /etc/dovecot/dovecot-proxy-sql.conf.ext driver = sql } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } passdb { args = /etc/dovecot/dovecot-system-sql.conf.ext driver = sql } plugin { acl = vfile mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename mail_log_fields = uid box msgid size quota = dict:User quota::proxy::quota recipient_delimiter = + sieve = file:~/sieve;active=~/.dovecot.sieve sieve_after = /var/spool/vmail/home/1-global/sieve } protocols = imap pop3 lmtp imap lmtp sieve service auth { inet_listener { port = 12345 } unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } } service dict { unix_listener dict { group = vmail mode = 0600 user = vmail } } service imap-login { inet_listener imap_2 { port = 10143 } } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } ssl_cert = </etc/ssl/certs/complete.crt ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it userdb { args = /etc/dovecot/master-users default_fields = master_user=%u driver = passwd-file } userdb { args = /etc/dovecot/dovecot-sql.conf.ext default_fields = master_user=%u driver = sql } userdb { args = /etc/dovecot/dovecot-system-sql.conf.ext driver = sql } verbose_proctitle = yes protocol lmtp { mail_plugins = " quota acl quota sieve" postmaster_address = postmaster@<domain> } protocol lda { mail_plugins = " quota acl sieve" } protocol imap { mail_max_userip_connections = 40 mail_plugins = " quota acl imap_quota acl" } remote 192.168.1.116 { protocol imap { disable_plaintext_auth = no } } remote 192.168.1.127 { protocol imap { disable_plaintext_auth = no } }

3 4

Re: Upgrade to 2.3.0.1 bre aks server
by post＠volker-wysk.de 03 Mar '18

03 Mar '18

Another remark: I have installed the new version from the PPA provided by dovecot.org: deb https://repo.dovecot.org/ce-2.3-latest/ubuntu/xenial xenial main Before (2.2.22) I had installed it from the ubuntu (canonical) package sources - and not the PPA provided by dovecot.org. Could it be, that the two don't play together? Bye Volker

1 0

Re: Upgrade to 2.3.0.1 bre aks server
by post＠volker-wysk.de 03 Mar '18

03 Mar '18

Here is my "dovecot -n": # 2.3.0.1 (ffd8a29): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.0.1 (d33dca2) # OS: Linux 4.4.0-116-generic x86_64 Ubuntu 16.04.4 LTS auth_debug = yes auth_username_format = %n auth_verbose = yes hostname = volker-wysk.de log_path = /var/log/dovecot.log mail_debug = yes mail_location = mdbox:~/lib/Dovecot-Mail managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date index ihave duplicate mime foreverypart extracttext imapsieve vnd.dovecot.imapsieve namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Entwürfe { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Papierkorb { special_use = \Trash } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } mailbox "Versendete Nachrichten" { special_use = \Sent } prefix = separator = . } passdb { driver = pam } plugin { imapsieve_mailbox1_before = file:/usr/lib/dovecot/sieve/report-spam.sieve imapsieve_mailbox1_causes = COPY imapsieve_mailbox1_name = Spam imapsieve_mailbox2_before = file:/usr/lib/dovecot/sieve/report-ham.sieve imapsieve_mailbox2_causes = COPY imapsieve_mailbox2_from = Spam imapsieve_mailbox2_name = * sieve = ~/.dovecot.sieve sieve_dir = ~/lib/Sieve sieve_global_extensions = +vnd.dovecot.pipe +vnd.dovecot.environment sieve_pipe_bin_dir = /usr/lib/dovecot/sieve sieve_plugins = sieve_imapsieve sieve_extprograms } postmaster_address = post(a)volker-wysk.de protocols = imap lmtp sieve ssl = required ssl_cert = </etc/ssl/certs/dovecot.pem ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it userdb { driver = passwd } protocol lmtp { mail_plugins = " sieve mail_log notify" } protocol lda { mail_plugins = " sieve" } protocol imap { mail_max_userip_connections = 50 mail_plugins = " imap_sieve" }

1 0

Upgrade to 2.3.0.1 breaks server
by post＠volker-wysk.de 03 Mar '18

03 Mar '18

Hi I've upgraded dovecot from 2.2.22 to 2.3.0.1, and now I can't log in any longer. My mail client says that the user name and password are rejected by dovecot. I get this messsage in the system logs: % journalctl -u dovecot.service (...) Mär 03 01:39:23 desktop systemd[1]: Stopped Dovecot IMAP/POP3 email server. Mär 03 01:39:23 desktop systemd[1]: Started Dovecot IMAP/POP3 email server. Mär 03 01:39:39 desktop auth[5736]: PAM audit_log_acct_message() failed: Operation not permitted I've followed the instructions in https://wiki2.dovecot.org/Upgrading/2.3 and https://repo.dovecot.org/ (for Ubuntu Xenial). Any ideas..? Bye V.W.

1 0

Autoexpunge of lazy_expunge namespace
by Angel L. Mateo 02 Mar '18

02 Mar '18

Hi, I'm using autoexpunge to clean my users' Trash and Spam mailboxes. But I'm also using lazy_expunge to keep a copy of deleted messages. Is there any to configure lazy_expunge namespace to be autoexpunged too? My lazy_expunge configuration is the "1 Namespace" described at https://wiki2.dovecot.org/Plugins/Lazyexpunge -- Angel L. Mateo Martínez Sección de Telemática Área de Tecnologías de la Información y las Comunicaciones Aplicadas (ATICA) http://www.um.es/atica Tfo: 868889150 Fax: 868888337

1 0

Re: Make fails with 2.3.0.1 & 2.2.34 on Mac OS X 10.7.5
by Aki Tuomi 02 Mar '18

02 Mar '18

> On 02 March 2018 at 08:42 James Brown <jlbrown(a)bordo.com.au> wrote: > > > > On 1 Mar 2018, at 9:52 pm, Aki Tuomi <aki.tuomi(a)dovecot.fi <mailto:aki.tuomi@dovecot.fi>> wrote: > > > > Can you also post your config.h? It should be at source root. > > > > Aki > > I tried but it was too big to post on the mailing list. I’m not sure if you got the direct email. > Yeah I got it. We have attempted to compile our code with OpenSSL 1.0, 1.0.2 and 1.1.0, but I'll try the specific releases too. Can you try this patch? diff --git a/src/lib-dcrypt/dcrypt-openssl.c b/src/lib-dcrypt/dcrypt-openssl.c index 26c9b91..187bb75 100644 --- a/src/lib-dcrypt/dcrypt-openssl.c +++ b/src/lib-dcrypt/dcrypt-openssl.c @@ -9,17 +9,17 @@ #include "array.h" #include "module-dir.h" #include "dovecot-openssl-common.h" -#include <openssl/evp.h> -#include <openssl/sha.h> -#include <openssl/err.h> -#include <openssl/rsa.h> -#include <openssl/ec.h> -#include <openssl/bio.h> -#include <openssl/pem.h> -#include <openssl/x509.h> -#include <openssl/engine.h> -#include <openssl/hmac.h> -#include <openssl/objects.h> +#include "openssl/evp.h" +#include "openssl/sha.h" +#include "openssl/err.h" +#include "openssl/rsa.h" +#include "openssl/ec.h" +#include "openssl/bio.h" +#include "openssl/pem.h" +#include "openssl/x509.h" +#include "openssl/engine.h" +#include "openssl/hmac.h" +#include "openssl/objects.h" #include "dcrypt.h" #include "dcrypt-private.h" And if it does not work, add after the includes #pragma message("OpenSSL version is " OPENSSL_VERSION_TEXT) #error See above And provide output? Aki

1 0

Make fails with 2.3.0.1 & 2.2.34 on Mac OS X 10.7.5
by James Brown 02 Mar '18

02 Mar '18

Have tried 2.3.0, 2.3.0.1 & 2.2.34. Compile is failing for me. ./configure --with-mysql --with-ssl=openssl: ... checking for SSL_read in -lssl... yes checking openssl/ssl.h usability... yes checking openssl/ssl.h presence... yes checking for openssl/ssl.h... yes checking openssl/err.h usability... yes checking openssl/err.h presence... yes checking for openssl/err.h... yes checking if OpenSSL version is 1.0.1 or newer... true checking if OpenSSL version is 1.0.2 or better... true checking whether SSL_clear_options exists... no ... No problems. But then ‘make’ ends with: dcrypt-openssl.c:117: error: field 'ctx' has incomplete type dcrypt-openssl.c: In function 'dcrypt_openssl_ctx_hmac_destroy': dcrypt-openssl.c:451: warning: implicit declaration of function 'HMAC_cleanup' dcrypt-openssl.c: In function 'dcrypt_openssl_generate_ec_key': dcrypt-openssl.c:555: error: dereferencing pointer to incomplete type dcrypt-openssl.c:556: error: dereferencing pointer to incomplete type dcrypt-openssl.c: In function 'dcrypt_openssl_ecdh_derive_secret_local': dcrypt-openssl.c:588: error: dereferencing pointer to incomplete type dcrypt-openssl.c: In function 'dcrypt_openssl_ecdh_derive_secret_peer': dcrypt-openssl.c:668: error: dereferencing pointer to incomplete type dcrypt-openssl.c:697: error: dereferencing pointer to incomplete type dcrypt-openssl.c:698: error: dereferencing pointer to incomplete type dcrypt-openssl.c: In function 'dcrypt_openssl_store_private_key_dovecot': dcrypt-openssl.c:1461: error: dereferencing pointer to incomplete type dcrypt-openssl.c:1482: error: dereferencing pointer to incomplete type dcrypt-openssl.c:1489: error: dereferencing pointer to incomplete type dcrypt-openssl.c: In function 'dcrypt_openssl_load_private_key': dcrypt-openssl.c:1615: error: dereferencing pointer to incomplete type dcrypt-openssl.c: In function 'dcrypt_openssl_store_public_key': dcrypt-openssl.c:1765: error: dereferencing pointer to incomplete type dcrypt-openssl.c: In function 'dcrypt_openssl_private_to_public_key': dcrypt-openssl.c:1801: error: dereferencing pointer to incomplete type dcrypt-openssl.c: In function 'dcrypt_openssl_name2oid': dcrypt-openssl.c:2062: error: dereferencing pointer to incomplete type dcrypt-openssl.c: In function 'dcrypt_openssl_public_key_id_old': dcrypt-openssl.c:2112: error: dereferencing pointer to incomplete type dcrypt-openssl.c: In function 'dcrypt_openssl_private_key_id_old': dcrypt-openssl.c:2135: error: dereferencing pointer to incomplete type dcrypt-openssl.c: In function 'dcrypt_openssl_public_key_id_evp': dcrypt-openssl.c:2153: error: dereferencing pointer to incomplete type make[3]: *** [libdcrypt_openssl_la-dcrypt-openssl.lo] Error 1 make[2]: *** [all-recursive] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2 Any suggestions? Thanks, James.

2 6

v2.2.34 released
by Timo Sirainen 01 Mar '18

01 Mar '18

https://dovecot.org/releases/2.2/dovecot-2.2.34.tar.gz https://dovecot.org/releases/2.2/dovecot-2.2.34.tar.gz.sig * CVE-2017-15130: TLS SNI config lookups may lead to excessive memory usage, causing imap-login/pop3-login VSZ limit to be reached and the process restarted. This happens only if Dovecot config has local_name { } or local { } configuration blocks and attacker uses randomly generated SNI servernames. * CVE-2017-14461: Parsing invalid email addresses may cause a crash or leak memory contents to attacker. For example, these memory contents might contain parts of an email from another user if the same imap process is reused for multiple users. First discovered by Aleksandar Nikolic of Cisco Talos. Independently also discovered by "flxflndy" via HackerOne. * CVE-2017-15132: Aborted SASL authentication leaks memory in login process. * Linux: Core dumping is no longer enabled by default via PR_SET_DUMPABLE, because this may allow attackers to bypass chroot/group restrictions. Found by cPanel Security Team. Nowadays core dumps can be safely enabled by using "sysctl -w fs.suid_dumpable=2". If the old behaviour is wanted, it can still be enabled by setting: import_environment=$import_environment PR_SET_DUMPABLE=1 * doveconf output now includes the hostname. + mail_attachment_detection_options setting controls when $HasAttachment and $HasNoAttachment keywords are set for mails. + imap: Support fetching body snippets using FETCH (SNIPPET) or (SNIPPET (LAZY=FUZZY)) + fs-compress: Automatically detect whether input is compressed or not. Prefix the compression algorithm with "maybe-" to enable the detection, for example: "compress:maybe-gz:6:..." + Added settings to change dovecot.index* files' optimization behavior. See https://wiki2.dovecot.org/IndexFiles#Settings + Auth cache can now utilize auth workers to do password hash verification by setting auth_cache_verify_password_with_worker=yes. + Added charset_alias plugin. See https://wiki2.dovecot.org/Plugins/CharsetAlias + imap_logout_format and pop3_logout_format settings now support all of the generic variables (e.g. %{rip}, %{session}, etc.) + Added auth_policy_check_before_auth, auth_policy_check_after_auth and auth_policy_report_after_auth settings. - v2.2.33: doveadm-server: Various fixes related to log handling. - v2.2.33: doveadm failed when trying to access UNIX socket that didn't require authentication. - v2.2.33: doveadm log reopen stopped working - v2.2.30+: IMAP stopped advertising SPECIAL-USE capability - v2.2.30+: IMAP stopped sending untagged OK/NO storage notifications - replication: dsync sends unnecessary replication notification for changes it does internally. NOTE: Folder creates, renames, deletes and subscribes still trigger unnecessary replication notifications, but these should be rather rare. - mail_always/never_cache_fields setting changes weren't applied for existing dovecot.index.cache files. - Fix compiling and other problems with OpenSSL v1.1 - auth policy: With master user logins, lookup using login username. - FTS reindexed all mails unnecessarily after loss of dovecot.index.cache file - mdbox rebuild repeatedly fails with "missing map extension" - SSL connections may have been hanging with imapc or doveadm client. - cassandra: Using protocol v3 (Cassandra v2.1) caused memory leaks and also timestamps weren't set to queries. - fs-crypt silently ignored public/private keys specified in configuration (mail_crypt_global_public/private_key) and just emitted plaintext output. - lock_method=dotlock caused crashes - imapc: Reconnection may cause crashes and other errors

7 9

Released Pigeonhole v0.4.22 for Dovecot v2.2.34.
by Stephan Bosch 01 Mar '18

01 Mar '18

Hello Dovecot users, Here is a new Pigeonhole release that goes with the new Dovecot v2.2.34 release. This release is not strictly necessary, as previous versions should be usable as well. This release only contains bugfixes. Changelog v0.4.22: - Fixed filesystem path handling problem: sieve plugin could have assert-crashed with specific path lengths with: "Panic: file realpath.c: line 86 (path_normalize): assertion failed: (npath_pos + 1 < npath + asize)". - Sieve extprograms plugin: Large output from "execute" command crashed delivery. Fixed buffering issue in code that handles output from the external program. - editheader extension: Extensively reworked the low-level implementation of adding and removing headers. This solves a few integer arithmetic problems reported by Clang runtime checks, but also improves code structure and reliability in general. - imapsieve: Fix assert crash occurring when selected messages are expunged concurrently by the time Sieve filter is to be applied. - imap4flags extension: Fix binary byte-code corruption occurring when the setflag, addflag, or removeflag command's flag-list is a variable. - enotify extension: mailto method: Fixed parsing of mailto URI with only a header part. - enotify extension: mailto method: Make sure "From:" header is set to a usable address and not "(null)". - Fixed writing address headers to outgoing messages. It sometimes erroneously applied another layer of MIME header encoding. The release is available as follows: https://pigeonhole.dovecot.org/releases/2.2/dovecot-2.2-pigeonhole-0.4.22.t… https://pigeonhole.dovecot.org/releases/2.2/dovecot-2.2-pigeonhole-0.4.22.t… Refer to http://pigeonhole.dovecot.org and the Dovecot v2.x wiki for more information. Have fun testing this release and don't hesitate to notify me when there are any problems. Regards, -- Stephan Bosch stephan(a)rename-it.nl

1 0

question about quota setting with postfix and dovecot
by Masaharu Kawada 01 Mar '18

01 Mar '18

Dear dovecot-list, I have questions regarding setting up quota with postfix(Maildir format)+ dovect. My main point of the question is to know how the user password is used in quota in this case. Please see the below configuration info and my questions are in the bottom. Here are what have been done: <Postfix side configuration> /etc/postfix/main.cf: ----- myhostname = mail.example.com mydomain = example.com myorigin = $mydomain inet_interfaces = all mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain home_mailbox = Maildir/ mailbox_command = /usr/libexec/dovecot/dovecot-lda -f "$SENDER" -a "$RECIPIENT" -d "$USER" <--Add ----- <Dovecot side configuration> 1. /etc/dovecot/conf.d/10-auth.conf: #!include auth-system.conf.ext #!include auth-sql.conf.ext #!include auth-ldap.conf.ext !include auth-passwdfile.conf.ext <---Only enabled #!include auth-checkpassword.conf.ext #!include auth-vpopmail.conf.ext #!include auth-static.conf.ext 2. /etc/dovecot/conf.d/10-master.conf service auth { snip/ unix_listener auth-userdb { mode = 0666 <---The permission for userdb 666 #user = #group = snip/ 3. /etc/dovecot/conf.d/10-mail.conf: mail_location = maildir:~/Maildir snip/ mail_plugins = $mail_plugins quota <---set the plugin snip/ 4. /etc/dovecot/conf.d/15-lda.conf: snip/ postmaster_address = root(a)example.com <---Add postmaster snip/ protocol lda { mail_plugins = $mail_plugins <--set the plugin } 5. /etc/dovecot/conf.d/20-imap.conf: protocol imap { mail_plugins = $mail_plugins imap_quota <--set the plugin snip/ 6. /etc/dovecot/conf.d/20-pop3.conf: snip/ protocol pop3 { mail_plugins = $mail_plugins quota <--set the plugin snip/ 7. /etc/dovecot/conf.d/90-quota.conf: plugin { <--set global quota quota = maildir:<User quota> quota_rule = *:storage=100M quota_rule2 = Trash:storage=+100M } 8. /etc/dovecot/conf.d/auth-passwdfile.conf.ext: snip/ passdb { driver = passwd-file args = scheme=CRYPT username_format=%u /etc/dovecot/users <--Path for passwdfile } userdb { driver = passwd-file args = username_format=%u /etc/dovecot/users } snip/ 9. /etc/dovecot/users: test004:{SSHA256}hFxB8tbyZrCCcwZKDaQEiUfojbRovOq8ECU0syPHQTCY0233:18222:18222::/home/test004::userdb_quota_rule=*:storage=1M test005:{SSHA256}hFxB8tbyZrCCcwZKDaQEiUfojbRovOq8ECU0syPHQTCY0233:18223:18223::/home/test005::userdb_quota_rule=*:storage=1M test006:{SSHA256}hFxB8tbyZrCCcwZKDaQEiUfojbRovOq8ECU0syPHQTCY0233:18224:18224::/home/test006::userdb_quota_rule=*:storage=1M Note:The hashed password is created running the blow command: # doveadm pw -s ssha256 10. /etc/dovecot/dovecot.conf: snip/ protocols = imap pop3 <--Available protocols snip/ 11. # service postfix restart # service dovcot restart Question: 1./etc/dovecot/users is supposed to be seen instead of /etc/passwd for authentification of imap and pops in receiving emails, isn't it? 2.If the answer for above question 1 is 'YES', then doesn't it require to get all password in /etc/passwd hashed for each user and place all of them into /etc/dovecot/users? 3.If the answer for above question 1 is 'NO', then what the hashed-password in /etc/dovcot/users such as {SSHA256}hFX... used for? Excuse me if those are silly questions, but I am not a dovecot person and would very much appreciate it if anyone would kindly give me a hand on this. Regards, Masaharu Kawada

1 0