- dovecot - dovecot.org

Virtual question
by LuKreme 03 Mar '18

03 Mar '18

“For each virtual directory you need to create a dovecot-virtual file. Its syntax is like:” OK, where does this file get created? Say I want the users to have a virtual mailbox that is messages received in the last month, does that file go into each user' s Maildir path? It sounds like I have to create a virtual folder for each user, then any folders inside that folders, and then the config files in each of the sub folders. user1/Maildir/virtual/month/dovecot-virtual user1/Maildir/virtual/week/dovecot-virtual user1/Maildir/virtual/flagged/dovecot-virtual user1/Maildir/virtual/Amazon/dovecot-virtual user2/Maildir/virtual/month/dovecot-virtual user2/Maildir/virtual/week/dovecot-virtual user2/Maildir/virtual/flagged/dovecot-virtual user2/Maildir/virtual/Amazon/dovecot-virtual Yes? If so, is there anyway to have a "global”virtual that applies to all users (but not that unifies the mail between users or anything like that). Also, will virtual mailboxes show up automatically for the user in the folder list or will they have to specifically subscribe to them? (Assuming they use a client that allows subscribing instead of auto showing all mailboxes like iOS). ˜kremels/ $ cat Maildir/virtual/month/dovecot-vitual # ~/Maildir/virtual/month/dovecot-virtual INBOX work/* all younger 2678400 That should create a mailbox "month” in a folder named "virtual” that shows all the messages from the last 31d, yes? And I should be able to access that mailbox in a MUA like Roundcube or <spit>Thunderbird? -- My main job is trying to come up with new and innovative and effective ways to reject even more mail. I'm up to about 97% now.

4 7

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

Using virtual folders with younger and index files
by Rob Hoelz 01 Mar '18

01 Mar '18

Hi list, I just encountered a problem while using dovecot's Virtual plugin with 2.3.0. I managed to solve the issue, but I wanted to bring it to the attention of others on the list to see if there exists a better solution, if I found a bug, or if it's just a matter of updating documentation. I have a virtual folder to get the most recent two weeks of mails; it looks something like this: > INBOX > all younger 1209600 I made this folder back in October. Lately, I started to notice that the virtual folder had a surprising amount of mail in it - I don't get 1,000 e-mails per week! After some doveadm commands, I realized that e-mails from October were still present in my virtual folder! Updating the dovecot-virtual would clear away e-mails older than two weeks (I needed to actually introduce a change, even if it was just whitespace - just touching the file didn't update things), and removing the dovecot index file also cleared things away. In then end, I ended up just telling dovecot to disable on-disk indexes for that folder. I created this folder based on the examples on https://wiki.dovecot.org/Plugins/Virtual - I'm wondering if I found a bug or if that page should be changed to recommend disabling on-disk indexes when using certain search query filters such as "younger". If the latter, I can always make the change - just let me know! -Rob

2 2

v2.3.0.1 released
by Timo Sirainen 28 Feb '18

28 Feb '18

https://dovecot.org/releases/2.3/dovecot-2.3.0.1.tar.gz https://dovecot.org/releases/2.3/dovecot-2.3.0.1.tar.gz.sig Small patch release to fix the worst bugs in v2.3.0. v2.3.1 is coming in about a month with a lot more changes. * 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 - imap-login with SSL/TLS connections may end up in infinite loop

1 0

Re: Quota status to postfix in distributed environment (Karol Augustin)
by SAAHIL IFTEKHAR 28 Feb '18

28 Feb '18

Hi Karol Thanks for taking time to go through the email and replying. I'll rewrite the issue again --> For example consider there two nodes. These each having their postfix and dovecot. I am trying to implement quota status to postfix to both the below cases:- case 1) mail sent within the node case 2) mail sent across the nodes In case 1 the postfix will query the dovecot of same node white in case 2 it will query the dovecot of other node. But suppose I am sending mail within the node and dovecot in other node is down. Mail will not go within the node. Even it will not defer also. This is evident from the logs(in last sections). I'll try to work suggestions you have given in mysetup though and post the relevant output. But if you have any other suggestion regarding what i have wrote just now. please let me know. Regards On 28-Feb-2018 5:19 am, <dovecot-request(a)dovecot.org> wrote: Send dovecot mailing list submissions to dovecot(a)dovecot.org To subscribe or unsubscribe via the World Wide Web, visit https://dovecot.org/mailman/listinfo/dovecot or, via email, send a message with subject or body 'help' to dovecot-request(a)dovecot.org You can reach the person managing the list at dovecot-owner(a)dovecot.org When replying, please edit your Subject line so it is more specific than "Re: Contents of dovecot digest..." Today's Topics: 1. Re: Quota status to postfix in distributed environment (@lbutlr) (SAAHIL IFTEKHAR) 2. Re: Quota status to postfix in distributed environment (Karol Augustin) 3. Re: Quota status to postfix in distributed environment (LuKreme) 4. Re: Quota status to postfix in distributed environment (Karol Augustin) ---------------------------------------------------------------------- Message: 1 Date: Tue, 27 Feb 2018 19:29:44 +0530 From: SAAHIL IFTEKHAR <response2saahil(a)gmail.com> To: dovecot(a)dovecot.org Subject: Re: Quota status to postfix in distributed environment (@lbutlr) Message-ID: <CAM5TiAQ2CT+u_BKEn0sKonirOQLD_Q0v=pVCcJBCiJfC08p7Mw(a)mail.gmail.com> Content-Type: text/plain; charset="utf-8" Hi Actually, the requirement is such that we have to work with this version only. I want to point out that the reason from the problem can be found out from logs(the end section). The "check_policy_service" in main.cf of postfix is the problem according to me. This configuration as a part of quota staus to postfix configuration. I hope many have went through this scenario or similar. So I am hoping to get some help for the same. Regards ------------------------------ Message: 2 Date: Tue, 27 Feb 2018 14:18:31 +0000 From: Karol Augustin <karol(a)augustin.pl> To: dovecot(a)dovecot.org Subject: Re: Quota status to postfix in distributed environment Message-ID: <b50c30e1b65c3875565ca2e49efeaafd(a)augustin.pl> Content-Type: text/plain; charset=US-ASCII On 2018-02-26 16:28, SAAHIL IFTEKHAR wrote: > Hi > > I have implemented Quota status to postfix in our setup. I have an imap server (dovecot) and mail server (postfix) in every node. I am able to send quota status to postfix and mails are rejected after 100% mail quota is crossed. This rejection is happening both in across the nodes and within the nodes. > > The problem is if I am sending mails to any node and if any other node's dovecot is down, mails are not going. For example, I am sending an email within the system but if some other node's dovecot is down then email within the system also will not go. > > My dovecot version is 2.2.10. My postfix version is 2.1.10. > > doveconf -n output is below:- > [snap] > > Here "service quota status" is the concerned section in conf file. > ____________________________________________________________ ____________________________________________ > > Postfix configuration is below:- > smtpd_relay_restrictions = > check_policy_service inet:201.123.80.9:54317 > check_policy_service inet:201.123.80.23:54317 > > virtual_transport=lmtp:unix:private/dovecot-lmtp > > Here, I am querying both two nodes. 201.123.80.9 is the other node. 201.123.80.23 is the node within which, email is sent. > ____________________________________________________________ _______________________________________________ > > logs while sending mail is below:- > [snap] > > I am understanding what the logs are trying to say. But I am not able to resolve the issue even after searching solution on internet and trying different hit and trials by myself. I want that if i am sending email to any node or within node, the configuration relating to "check _policy_service" for other node does not interfere and mail goes properly. At the same time I can also fetch quota status from other nodes. > > If I can get any help regarding this it will be really appreciable as I have tried a lot of options already. > Your problem is that if the dovecot is unreachable Postfix can't check the quota for the user. http://www.postfix.org/SMTPD_POLICY_README.html explains how to resolve this problem: smtpd_policy_service_default_action (default: 451 4.3.5 Server configuration problem): The default action when an SMTPD policy service request fails. Available with Postfix 3.0 and later. The default action when an SMTPD policy service request fails. Specify "DUNNO" to behave as if the failed SMTPD policy service request was not sent, and to continue processing other access restrictions, if any. You can configure it per policy also. The issue you might encounter with this setup is that if both of your dovecot nodes are unreachable Postfix will accept the e-mail and try to deliver it. When the nodes come online it will fail if the user is over quota and generate bounce to the envelope sender of the message, which might produce backscatter. I resolved this problem by keeping quota information in Mysql table and using custom policy server to check if user is allowed to receive more e-mail. Also this approach might not work with aliases and other redirections, the e-mail address checked by smtpd policy is the one before alias expansion. You should check if it suits your environment. Best, Karol -- Karol Augustin karol(a)augustin.pl http://karolaugustin.pl/ +353 85 775 5312

1 0

compile-error on pigeonhole
by Jakobus Schürz 28 Feb '18

28 Feb '18

Hi! I try to compile pigeonhole from git-sources and get this error: libtool: link: gcc -std=gnu99 -g -O2 -fstack-protector-strong -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -fno-builtin-strfti me -Wstrict-aliasing=2 -I../.. -pie -Wl,-z -Wl,relro -Wl,-z -Wl,now -o .libs/sievec sievec-sievec.o -Wl,--export-dynamic ../../src/lib-sieve/.libs/libdovecot-sieve.so ../../src/lib-sieve-tool/.libs/libsieve-tool.a /usr/local/lib/dovecot /libdovecot-storage.so /usr/local/lib/dovecot/libdovecot-lda.so -L/usr/local/lib/dovecot /usr/local/lib/dovecot/libdovecot.so -Wl,-rpath -Wl,/usr/local/lib/dovecot ../../src/lib-sieve/.libs/libdovecot-sieve.so: undefined reference to `array_idx_get_space' collect2: error: ld returned 1 exit status I'm not able to compile pigeonhole. Jakob

2 1

dovecot.index.pvt reset, view is now inconsistent
by Rupert Gallagher 28 Feb '18

28 Feb '18

Problem solved by going in manually. The log message appears for empty "public" folders. Say, you have a folder X with subfolder Y, where X does not contain any e-mail. The log message disappears if you drop an email into X, then remove it. Puf, gone! So, there seems to be a baby bug in how dovecot manages the index in this case.

3 2

BUG: Error: dovecot.index.pvt reset, view is now inconsistent when shared folder is new and empty
by Marco Giunta 28 Feb '18

28 Feb '18

Hi, I'm using Dovecot 2.2.33.2 on a RHEL 7, new installation. My log is full of : Error: INDEX_FOLDER/dovecot.index.pvt reset, view is now inconsistent or Error: INDEX_FOLDER/dovecot.index.pvt view is inconsistent when shared folder is never touched and empty. UserA share XXXXX folder with UserB, if XXXXX folder is new (never touched) and empty every time UserB looks in that folder, an error appears in log file. If UserA copy a mail in XXXXX folder, no more errors. If UserA (or UserB) delete all mails in XXXXX folder (the folder is empty again), no more errors. So the errors appear when UserB access a new (never touched) shared empty folder; if the folder is empty, but not new (p.e. UserA has already copied and deleted mails in that folder) error is logged only once. Attached my configuration. Thanks, Marco -- Marco Giunta - ITCS SysAdmin Via Bonomea, 265 34136 - Trieste, Italy Tel: +39-040-3787-503 Fax: +39-040-3787-244

1 0

Out of memory on lmtp vsz_limit
by Terence Lau 28 Feb '18

28 Feb '18

Hi, We've been getting these types or errors for quite a while now ... Fatal: master: service(lmtp): child 63477 returned error 83 (Out of memory (service lmtp { vsz_limit=4096 MB }, you may need to increase it) ... and these errors have been decreasing in occurrence as we increased the default_vsz_limit. Which is good but I would like to get some advice on how I could possibly eliminate the errors. We have an internal smtp server (postfix 3.1.0) that has the config "always_bcc=archive(a)company.com" over lmtp. This mailbox is on a separate dovecot server with the following config (please let me know if the full config is required): # 2.2.22 (fe789d2): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.13 (7b14904) # OS: Linux 4.4.0-109-generic x86_64 Ubuntu 16.04.1 LTS ext4 default_vsz_limit = 4 G mail_location = maildir:/home/vmail/%d/%n protocols = " imap lmtp pop3" service lmtp { inet_listener lmtp { port = 24 } } userdb { args = username_format=%u /etc/dovecot/users default_fields = uid=vmail gid=vmail home=/home/vmail/%d/%n driver = passwd-file } protocol lmtp { mail_plugins = } Since we discovered the errors, we've been increasing the default_vsz_limit to 1G, then 2G and now 4G (Server has 6GB of memory). These errors occur whenever a large number of emails get sent around the same time to our smtp server. This causes the dovecot server to start crunching CPU and Memory. Load average goes through the roof and takes some time to come back down as the smtp queue clears itself. This mailbox is obviously very large but we have a script that runs daily to delete any emails older than a month: find /home/vmail/company.com/archive/new/ -type f -mtime +30 -exec rm {} \; find /home/vmail/company.com/archive/cur/ -type f -mtime +30 -exec rm {} \; Still, the mailbox has on average of just under 300,000 emails. No one accesses this mailbox with an email client, not until we need to dig something up. And this has only happen once. So the emails pretty much never get read/process by a user. Now that we've increased the default_vsz_limit to 4G, the occurrence of these errors has reduced considerably. But they still happen occasionally. Short of increasing the memory further, are there any other options I have? Thanks. [https://www.royhill.com.au/email/Emalisignaturecurrent.jpg]

2 3

use IMAP and POP3 simultaneously (single inbox)
by Stanislaw Findeisen 28 Feb '18

28 Feb '18

Hi Is it safe to use IMAP and POP3 simultaneously to access the same inbox (using Maildir structure)? Thanks! Stanisław

2 1

Quota status to postfix in distributed environment
by SAAHIL IFTEKHAR 27 Feb '18

27 Feb '18

Hi I have implemented Quota status to postfix in our setup. I have an imap server (dovecot) and mail server (postfix) in every node. I am able to send quota status to postfix and mails are rejected after 100% mail quota is crossed. This rejection is happening both in across the nodes and within the nodes. The problem is if I am sending mails to any node and if any other node's dovecot is down, mails are not going. For example, I am sending an email within the system but if some other node's dovecot is down then email within the system also will not go. My dovecot version is 2.2.10. My postfix version is 2.1.10. *doveconf -n output is below:-* # 2.2.10: /etc/dovecot/dovecot.conf # OS: Linux 3.10.0-514.el7.x86_64 x86_64 Red Hat Enterprise Linux Server release 7.3 (Maipo) xfs auth_debug = yes base_dir = /var/run/dovecot/ first_valid_gid = 5000 first_valid_uid = 5000 hostname = CmdHQ login_greeting = ^^^^^^^^^^Dovecot ready^^^^^^^^^^ mail_debug = yes mail_gid = 6000 mail_location = Maildir:/var/mail/vmail/tcs.mil.in/%n mail_plugins = " quota" mail_uid = 6000 mbox_write_locks = fcntl passdb { args = /etc/dovecot/dovecot-ldap.conf driver = ldap } plugin { quota = maildir:User quota quota_rule = *:storage=8KB quota_rule2 = *:messages=12B quota_status_nouser = DUNNO quota_status_overquota = 552 5.2.2 Mailbox is over quota / mailbox is full quota_status_success = DUNNO quota_warning = storage=80%% quota-warning 80 %u } postmaster_address = postmaster(a)tcs.mil.in service auth { unix_listener auth-userdb { mode = 0600 user = postfix } } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } service quota-status { client_limit = 1 executable = quota-status -p postfix inet_listener { port = 54317 } } service quota-warning { executable = script /usr/local/bin/quota-warning.sh unix_listener quota-warning { group = postfix mode = 0666 user = postfix } user = postfix } ssl = required ssl_ca = </etc/dovecot/certs/cacert.pem ssl_cert = </etc/dovecot/certs/1CorpHQ_IMAP_Admin(a)tcs.mil.in.pem ssl_key = </etc/dovecot/certs/1CorpHQ_IMAP_Admin(a)tcs.mil.in.key userdb { args = /etc/dovecot/dovecot-ldap.conf driver = ldap } verbose_ssl = yes protocol lmtp { info_log_path = /var/log/dovecot-lmtp.log mail_plugins = " quota" } protocol lda { info_log_path = /var/log/dovecot-lda.log log_path = /var/log/dovecot-lda-errors.log mail_plugins = " quota" } protocol imap { mail_plugins = " quota" } Here "service quota status" is the concerned section in conf file. ________________________________________________________________________________________________________ *Postfix configuration is below:- * smtpd_relay_restrictions = check_policy_service inet:201.123.80.9:54317 check_policy_service inet:201.123.80.23:54317 virtual_transport=lmtp:unix:private/dovecot-lmtp Here, I am querying both two nodes. 201.123.80.9 is the other node. 201.123.80.23 is the node within which, email is sent. ___________________________________________________________________________________________________________ *logs while sending mail is below:-F*eb 22 12:43:24 1CorpHQ postfix/proxymap[7327]: In dict_changed_name Feb 22 12:43:24 1CorpHQ postfix/smtpd[7326]: initializing the server-side TLS engine Feb 22 12:43:24 1CorpHQ postfix/smtpd[7326]: In dict_changed_name Feb 22 12:43:24 1CorpHQ postfix/smtpd[7326]: match_list_match: 1CorpHQ: no match Feb 22 12:43:24 1CorpHQ postfix/smtpd[7326]: match_list_match: 201.123.80.23: no match Feb 22 12:43:24 1CorpHQ postfix/smtpd[7326]: match_list_match: 1CorpHQ: no match Feb 22 12:43:24 1CorpHQ postfix/smtpd[7326]: match_list_match: 201.123.80.23: no match Feb 22 12:43:24 1CorpHQ postfix/smtpd[7326]: text 220 1CorpHQserver.tcs.mil.in ESMTP Postfix Feb 22 12:43:24 1CorpHQ postfix/smtpd[7326]: text EHLO 1CorpHQ Feb 22 12:43:24 1CorpHQ postfix/smtpd[7326]: match_list_match: 1CorpHQ: no match Feb 22 12:43:24 1CorpHQ postfix/smtpd[7326]: match_list_match: 201.123.80.23: no match Feb 22 12:43:24 1CorpHQ postfix/smtpd[7326]: text 250-1CorpHQserver.tcs.mil.in Feb 22 12:43:24 1CorpHQ postfix/smtpd[7326]: text 250-PIPELINING Feb 22 12:43:24 1CorpHQ postfix/smtpd[7326]: text 250-SIZE 10240000 Feb 22 12:43:24 1CorpHQ postfix/smtpd[7326]: text 250-VRFY Feb 22 12:43:24 1CorpHQ postfix/smtpd[7326]: text 250-ETRN Feb 22 12:43:24 1CorpHQ postfix/smtpd[7326]: text 250-STARTTLS Feb 22 12:43:24 1CorpHQ postfix/smtpd[7326]: text 250-ENHANCEDSTATUSCODES Feb 22 12:43:24 1CorpHQ postfix/smtpd[7326]: text 250-8BITMIME Feb 22 12:43:24 1CorpHQ postfix/smtpd[7326]: text 250 DSN Feb 22 12:43:24 1CorpHQ postfix/smtpd[7326]: text STARTTLS Feb 22 12:43:24 1CorpHQ postfix/smtpd[7326]: text 220 2.0.0 Ready to start TLS Feb 22 12:43:24 1CorpHQ postfix/smtpd[7326]: setting up TLS connection from 1CorpHQ[201.123.80.23] Feb 22 12:43:24 1CorpHQ postfix/smtpd[7326]: 1CorpHQ[201.123.80.23]: TLS cipher list "aNULL:-aNULL:ALL:!EXPORT:!LOW:+RC4:@STRENGTH" Feb 22 12:43:24 1CorpHQ postfix/smtpd[7326]: SSL_accept:before/accept initialization Feb 22 12:43:24 1CorpHQ postfix/smtpd[7326]: SSL_accept:SSLv3 read client hello A Feb 22 12:43:24 1CorpHQ postfix/smtpd[7326]: SSL_accept:SSLv3 write server hello A Feb 22 12:43:24 1CorpHQ postfix/smtpd[7326]: SSL_accept:SSLv3 write certificate A Feb 22 12:43:24 1CorpHQ postfix/smtpd[7326]: SSL_accept:SSLv3 write key exchange A Feb 22 12:43:24 1CorpHQ postfix/smtpd[7326]: SSL_accept:SSLv3 write server done A Feb 22 12:43:24 1CorpHQ postfix/smtpd[7326]: SSL_accept:SSLv3 flush data Feb 22 12:43:24 1CorpHQ postfix/smtpd[7326]: SSL_accept:SSLv3 read client key exchange A Feb 22 12:43:24 1CorpHQ postfix/smtpd[7326]: SSL_accept:SSLv3 read finished A Feb 22 12:43:24 1CorpHQ postfix/smtpd[7326]: SSL_accept:SSLv3 write change cipher spec A Feb 22 12:43:24 1CorpHQ postfix/smtpd[7326]: SSL_accept:SSLv3 write finished A Feb 22 12:43:24 1CorpHQ postfix/smtpd[7326]: SSL_accept:SSLv3 flush data Feb 22 12:43:24 1CorpHQ postfix/smtpd[7326]: Anonymous TLS connection established from 1corphq[201.123.80.23]: TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits) Feb 22 12:43:24 1CorpHQ postfix/smtpd[7326]: text EHLO 1CorpHQ Feb 22 12:43:24 1CorpHQ postfix/smtpd[7326]: match_list_match: 1CorpHQ: no match Feb 22 12:43:24 1CorpHQ postfix/smtpd[7326]: match_list_match: 201.123.80.23: no match Feb 22 12:43:24 1CorpHQ postfix/smtpd[7326]: text 250-1CorpHQserver.tcs.mil.in Feb 22 12:43:24 1CorpHQ postfix/smtpd[7326]: text 250-PIPELINING Feb 22 12:43:24 1CorpHQ postfix/smtpd[7326]: text 250-SIZE 10240000 Feb 22 12:43:24 1CorpHQ postfix/smtpd[7326]: text 250-VRFY Feb 22 12:43:24 1CorpHQ postfix/smtpd[7326]: text 250-ETRN Feb 22 12:43:24 1CorpHQ postfix/smtpd[7326]: text 250-ENHANCEDSTATUSCODES Feb 22 12:43:24 1CorpHQ postfix/smtpd[7326]: text 250-8BITMIME Feb 22 12:43:24 1CorpHQ postfix/smtpd[7326]: text 250 DSN Feb 22 12:43:24 1CorpHQ postfix/smtpd[7326]: text MAIL FROM:< Cdr.1CorpHQ(a)tcs.mil.in> Feb 22 12:43:24 1CorpHQ postfix/trivial-rewrite[7330]: match_list_match: transport_maps: no match Feb 22 12:43:24 1CorpHQ postfix/trivial-rewrite[7330]: match_list_match: transport_maps: no match Feb 22 12:43:24 1CorpHQ postfix/trivial-rewrite[7330]: In dict_changed_name Feb 22 12:43:24 1CorpHQ postfix/trivial-rewrite[7330]: match_list_match: tcs.mil.in: no match Feb 22 12:43:24 1CorpHQ postfix/trivial-rewrite[7330]: match_list_match: tcs.mil.in: no match Feb 22 12:43:24 1CorpHQ postfix/trivial-rewrite[7330]: match_list_match: tcs.mil.in: no match Feb 22 12:43:24 1CorpHQ postfix/trivial-rewrite[7330]: match_list_match: tcs.mil.in: no match Feb 22 12:43:24 1CorpHQ postfix/smtpd[7326]: In valid verify sender addr Feb 22 12:43:24 1CorpHQ postfix/smtpd[7326]: text 250 2.1.0 Ok Feb 22 12:43:24 1CorpHQ postfix/smtpd[7326]: text RCPT TO:< CO.1CorpHQ(a)tcs.mil.in> Feb 22 12:43:24 1CorpHQ postfix/trivial-rewrite[7330]: match_list_match: tcs.mil.in: no match Feb 22 12:43:24 1CorpHQ postfix/trivial-rewrite[7330]: match_list_match: tcs.mil.in: no match Feb 22 12:43:24 1CorpHQ postfix/trivial-rewrite[7330]: match_list_match: tcs.mil.in: no match Feb 22 12:43:24 1CorpHQ postfix/trivial-rewrite[7330]: match_list_match: tcs.mil.in: no match Feb 22 12:43:24 1CorpHQ postfix/smtpd[7326]: In valid verify sender addr Feb 22 12:43:24 1CorpHQ postfix/smtpd[7326]: match_list_match: permit_mynetworks: no match Feb 22 12:43:24 1CorpHQ dovecot: quota-status: Debug: Loading modules from directory: /usr/lib64/dovecot Feb 22 12:43:24 1CorpHQ dovecot: quota-status: Debug: Module loaded: /usr/lib64/dovecot/lib10_quota_plugin.so Feb 22 12:43:24 1CorpHQ dovecot: auth: Debug: Loading modules from directory: /usr/lib64/dovecot/auth Feb 22 12:43:24 1CorpHQ dovecot: auth: Debug: Module loaded: /usr/lib64/dovecot/auth/libdriver_sqlite.so Feb 22 12:43:24 1CorpHQ dovecot: auth: Debug: Loading modules from directory: /usr/lib64/dovecot/auth Feb 22 12:43:24 1CorpHQ dovecot: auth: Debug: Module loaded: /usr/lib64/dovecot/auth/libauthdb_ldap.so Feb 22 12:43:24 1CorpHQ dovecot: auth: Debug: Read auth token secret from /var/run/dovecot//auth-token-secret.dat Feb 22 12:43:24 1CorpHQ dovecot: auth: Debug: master in: USER#0111# 011CO.1CorpHQ(a)tcs.mil.in#011service=quota-status Feb 22 12:43:24 1CorpHQ dovecot: auth: Debug: ldap(co.1corphq(a)tcs.mil.in): user search: base=dc=tcs,dc=mil,dc=in scope=subtree filter=(&(objectClass=person)(uid=co.1corphq)) fields=homeDirectory,uidNumber,gidNumber Feb 22 12:43:24 1CorpHQ dovecot: auth: Debug: ldap(co.1corphq(a)tcs.mil.in): no fields returned by the server Feb 22 12:43:24 1CorpHQ dovecot: auth: Debug: ldap(co.1corphq(a)tcs.mil.in): result: homeDirectory missing; uidNumber missing; gidNumber missing Feb 22 12:43:24 1CorpHQ dovecot: auth: Debug: userdb out: USER#0111# 011co.1corphq(a)tcs.mil.in Feb 22 12:43:24 1CorpHQ dovecot: quota-status: Debug: auth input: co.1corphq(a)tcs.mil.in Feb 22 12:43:24 1CorpHQ dovecot: quota-status: Debug: changed username to co.1corphq(a)tcs.mil.in Feb 22 12:43:24 1CorpHQ dovecot: quota-status: Debug: Added userdb setting: plugin/=yes Feb 22 12:43:24 1CorpHQ dovecot: quota-status(co.1corphq(a)tcs.mil.in): Debug: Effective uid=6000, gid=6000, home= Feb 22 12:43:24 1CorpHQ dovecot: quota-status(co.1corphq(a)tcs.mil.in): Debug: Quota root: name=User quota backend=maildir args= Feb 22 12:43:24 1CorpHQ dovecot: quota-status(co.1corphq(a)tcs.mil.in): Debug: Quota rule: root=User quota mailbox=* bytes=8192 messages=0 Feb 22 12:43:24 1CorpHQ dovecot: quota-status(co.1corphq(a)tcs.mil.in): Debug: Quota rule: root=User quota mailbox=* bytes=8192 messages=12 Feb 22 12:43:24 1CorpHQ dovecot: quota-status(co.1corphq(a)tcs.mil.in): Debug: Quota warning: bytes=6553 (80%) messages=0 reverse=no command=quota-warning 80 co.1corphq(a)tcs.mil.in Feb 22 12:43:24 1CorpHQ dovecot: quota-status(co.1corphq(a)tcs.mil.in): Debug: Quota grace: root=User quota bytes=819 (10%) Feb 22 12:43:24 1CorpHQ dovecot: quota-status(co.1corphq(a)tcs.mil.in): Debug: maildir++: root=/var/mail/vmail/tcs.mil.in/co.1corphq, index=, indexpvt=, control=, inbox=/var/mail/vmail/tcs.mil.in/co.1corphq, alt= Feb 22 12:43:24 1CorpHQ postfix/smtpd[7326]: warning: connect to 201.123.80.9:54317: Connection refused Feb 22 12:43:24 1CorpHQ postfix/smtpd[7326]: warning: problem talking to server 201.123.80.9:54317: Connection refused Feb 22 12:43:25 1CorpHQ postfix/smtpd[7326]: warning: connect to 201.123.80.9:54317: Connection refused Feb 22 12:43:25 1CorpHQ postfix/smtpd[7326]: warning: problem talking to server 201.123.80.9:54317: Connection refused Feb 22 12:43:25 1CorpHQ postfix/smtpd[7326]: NOQUEUE: reject: RCPT from 1CorpHQ[201.123.80.23]: 451 4.3.5 Server configuration problem; from=< Cdr.1CorpHQ(a)tcs.mil.in> to=<CO.1CorpHQ(a)tcs.mil.in> proto=ESMTP helo=<1CorpHQ> Feb 22 12:43:25 1CorpHQ postfix/smtpd[7326]: text 451 4.3.5 Server configuration problem Feb 22 12:43:25 1CorpHQ postfix/smtpd[7326]: text RSET Feb 22 12:43:25 1CorpHQ postfix/smtpd[7326]: text 250 2.0.0 Ok Feb 22 12:43:25 1CorpHQ postfix/smtpd[7326]: lost connection after RSET from 1CorpHQ[201.123.80.23] I am understanding what the logs are trying to say. But I am not able to resolve the issue even after searching solution on internet and trying different hit and trials by myself. I want that if i am sending email to any node or within node, the configuration relating to "check _policy_service" for other node does not interfere and mail goes properly. At the same time I can also fetch quota status from other nodes. If I can get any help regarding this it will be really appreciable as I have tried a lot of options already. Regards

4 4

Re: Quota status to postfix in distributed environment (@lbutlr)
by SAAHIL IFTEKHAR 27 Feb '18

27 Feb '18

Hi Actually, the requirement is such that we have to work with this version only. I want to point out that the reason from the problem can be found out from logs(the end section). The "check_policy_service" in main.cf of postfix is the problem according to me. This configuration as a part of quota staus to postfix configuration. I hope many have went through this scenario or similar. So I am hoping to get some help for the same. Regards On 27-Feb-2018 15:30, <dovecot-request(a)dovecot.org> wrote: Send dovecot mailing list submissions to dovecot(a)dovecot.org To subscribe or unsubscribe via the World Wide Web, visit https://dovecot.org/mailman/listinfo/dovecot or, via email, send a message with subject or body 'help' to dovecot-request(a)dovecot.org You can reach the person managing the list at dovecot-owner(a)dovecot.org When replying, please edit your Subject line so it is more specific than "Re: Contents of dovecot digest..." Today's Topics: 1. Re: Quota status to postfix in distributed environment (@lbutlr) ---------------------------------------------------------------------- Message: 1 Date: Mon, 26 Feb 2018 08:32:43 -0800 From: "@lbutlr" <kremels(a)kreme.com> To: dovecot(a)dovecot.org Subject: Re: Quota status to postfix in distributed environment Message-ID: <D525FAB8-D208-4B6E-AFBD-104EF48A6234(a)kreme.com> Content-Type: text/plain; charset=us-ascii On Feb 26, 2018, at 08:28, SAAHIL IFTEKHAR <response2saahil(a)gmail.com> wrote: > My dovecot version is 2.2.10. > My postfix version is 2.1.10. What happens if you use current-ish versions. -- This is my signature. There are many like it, but this one is mine. ------------------------------ Subject: Digest Footer _______________________________________________ dovecot mailing list dovecot(a)dovecot.org https://dovecot.org/mailman/listinfo/dovecot ------------------------------ End of dovecot Digest, Vol 178, Issue 64 ****************************************

1 0

Really slow IMAP performance
by Neil Jerram 26 Feb '18

26 Feb '18

Please could you help me to understand and fix why my dovecot IMAP performance is so bad? I've read through a lot of the performance-related material on the website, but I don't think that any of it could account for slowness at the level that I am seeing. The simplest scenario is moving a message from my Inbox to another IMAP folder. Using Gnus as the client, the whole UI freezes for about 2 minutes (which I assume is until the move is complete), and journalctl on the dovecot server says: Feb 24 10:24:24 arudy dovecot[1712]: imap(neil): Warning: Transaction log file /home/neil/dovecot-mail/.imap/INBOX/dovecot.index.log was locked for 98 seconds (Mailbox was synchronized) or the same message with (rotating while syncing). There must be something badly wrong in my setup, or perhaps in the spec of the server that dovecot is running on. What should I look at to start understanding this better? Many thanks - Neil

6 11

move more than one subvolder doesn't works
by Arno Schneider 26 Feb '18

26 Feb '18

Our setup: 2 replicated dovecot 2.2.33.2 servers thunderbird client When I select more than one mail subfolder in thunderbird and drag & drop them to another subfolder only one subfolger is moved. In the following I can't move another mail folder to the first target. Any ideas why this happens? best regards, arno

1 0

understanding dovecot director passdb configuration
by Kalyana sundaram 26 Feb '18

26 Feb '18

Hey All I am very new to dovecot ecosystem. Found the software really robust and secure. Kudos to the team!!! We are setting up dovecot imap servers sharing a single nfs mount point. So to avoid nfs cache issues, we are setting up dovecot director. We are using dovecot version 2.2.10. While going through the documentation of dovecot director I stumbled across the following lines in passdb configuration https://wiki2.dovecot.org/Director "Note that while this is the simplest director configuration, users will be assigned to a backend before they have been authenticated. A director configured this way can be attacked by sending it a large number of unknown users. To prevent this, the director should be configured to authenticate the user and might make use of a master password to log into the backend servers." I understand on static passdb config dovecot assigns a user to a machine in the list of backends by using md5(username)%number_of_mail_servers. But other than this calculation it does not incur any other resources. It does have tcp connection with the system which is trying to do bruteforce. If we move to authenticating users directly at the director server, the director servers imap-login director service should be anyways loaded on an attack. Is it anything to do that the imap-login will contact auth process asynchronously and keep itself free? I am pretty sure I am overlooking some point on the above statement. Can somebody throw some light on that? -- Kalyanasundaram http://blogs.eskratch.com/ https://github.com/kalyanceg/

2 1

imap-login director is not restarted after each auth request
by Kalyana sundaram 26 Feb '18

26 Feb '18

Hi imap-login by default in mail server is restarted after every login request keeping security in mind to avoid leak of critical data. But in a director config, the imap-login director process is not restarted on each auth request. Can somebody explain why this design decision is taken? -- Kalyanasundaram http://blogs.eskratch.com/ https://github.com/kalyanceg/

1 0