- dovecot - dovecot.org

how to doveadm search from "<>" (null sender)?
by Daniel Funke 12 Jun '15

12 Jun '15

Hi, I tried to search for mailer daemon messages but can't find a syntax for the null sender. all these does not work: doveadm -u xxx from "<>" doveadm -u xxx from <> doveadm -u xxx from "" any ideas? Thank you Daniel

2 1

Replication: "cross-updates" of mail meta-data
by Andre Nathan 11 Jun '15

11 Jun '15

Hello I have a two-server dovecot setup using replication. Each server runs two dovecot instances, one for director and another for the backend. Initially I set up a single server, got it all working, then rsync'd the data and index partitions to the new one and started the clusters (I used rsync as a way to speed-up dovecot's initial replication). Both servers listen on a virtual IP addresses load-balanced by IPVS as well as their own IP addresses. When I started dovecot in the second server, users started reporting that some of their messages were missing. I noticed that while the mail data seemed to be up to date in server1, it wasn't in server2; however, the indexes were being updated in server2 but not in server1. For example, "doveadm quota get -u some-user" would report the wrong value in server1 and the right value in server2, while a "du" would show that only server1 actually had the most up-to-date data. At the moment I had to take down server2, because as soon as dovecot is running in it, users start reporting missing messages again. To solve that problem, a "doveadm force-resync" in server1 isn't enough. I either rsync the index files from server2 or remove the indexes in server1 before the force-resync, which then works. Has anyone ever saw anything similar to this? Any help would be much appreciated. I'm running Ubuntu 14.04 with dovecot 2.2.15 with the configurations below: === Backend instance === # dovecot -n # 2.2.15: /etc/dovecot/dovecot.conf # OS: Linux 3.16.0-37-generic x86_64 Ubuntu 14.04.2 LTS auth_master_user_separator = * auth_mechanisms = plain login auth_username_chars = abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@= auth_worker_max_count = 10 disable_plaintext_auth = no doveadm_password = secret doveadm_port = 12345 listen = server1.mydomain.com mail_fsync = never mail_gid = dovemail mail_plugins = " notify replication quota" mail_uid = dovemail managesieve_sieve_capability = fileinto reject envelope vacation subaddress comparator-i;ascii-numeric relational regex copy include vacation-seconds imapflags notify namespace { inbox = yes location = mailbox SPAM { auto = subscribe } prefix = separator = / type = private } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } passdb { args = /etc/dovecot/dovecot-sql-master.conf.ext driver = sql master = yes pass = yes } plugin { mail_replica = tcp:192.168.0.2:12345 # server2's replication IP quota = dict:User quota::file:/var/lib/imap/user/%2.256RHn/%n/dovecot-quota quota_rule = *:storage=1GB sieve = /var/lib/imap/sieve/%2.256RHn/%n/dovecot.sieve sieve_dir = /var/lib/imap/sieve/%2.256RHn/%n sieve_extensions = comparator-i;ascii-numeric copy envelope fileinto imapflags include notify regex reject relational subaddress vacation-seconds sieve_max_redirects = 20 sieve_max_script_size = 512KB sieve_quota_max_scripts = 2 sieve_vacation_min_period = 1 sieve_vacation_send_from_recipient = yes } protocols = imap pop3 lmtp sieve replication_dsync_parameters = -f -d -N -l 30 -U service aggregator { fifo_listener replication-notify-fifo { group = dovemail mode = 0666 user = dovemail } unix_listener replication-notify { group = dovemail mode = 0666 user = dovemail } } service auth-worker { user = $default_internal_user } service auth { client_limit = 10240 process_limit = 1 process_min_avail = 1 } service doveadm { inet_listener { address = 192.168.0.1 port = 12345 } vsz_limit = 1 G } service imap { process_limit = 8192 process_min_avail = 10 } service lmtp { inet_listener { address = lmtpcluster.internal.mydomain.com, server1.internal.mydomain.com port = 1124 } process_limit = 512 process_min_avail = 10 } service managesieve-login { inet_listener sieve { address = lmtpcluster.internal.mydomain.com, server1.internal.mydomain.com port = 4190 } } service managesieve { process_limit = 20 process_min_avail = 10 } service pop3 { process_limit = 512 process_min_avail = 10 } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { group = dovemail mode = 0666 user = dovemail } } ssl_cert = </etc/ssl/certs/mydomain.crt ssl_key = </etc/ssl/private/mydomain.key userdb { driver = prefetch } userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } verbose_proctitle = yes protocol imap { imap_client_workarounds = tb-extra-mailbox-sep delay-newmail imap_idle_notify_interval = 2 mins imap_max_line_length = 64 k mail_max_userip_connections = 50 mail_plugins = " notify replication quota imap_quota" } protocol lmtp { info_log_path = /var/log/mail/dovecot-lmtp.log mail_fsync = optimized mail_plugins = " notify replication sieve quota" } protocol sieve { mail_plugins = " notify replication sieve" managesieve_implementation_string = ManageSieve managesieve_logout_format = bytes=%i/%o managesieve_max_line_length = 65536 managesieve_sieve_capability = comparator-i;ascii-numeric copy envelope fileinto imapflags include notify regex reject relational subaddress vacation-seconds ssl = no } protocol pop3 { mail_plugins = " notify replication quota" pop3_client_workarounds = outlook-no-nuls oe-ns-eoh } === Director instance === # dovecot -n -c /etc/dovecot_director/dovecot_director.conf # 2.2.15: /etc/dovecot_director/dovecot_director.conf # OS: Linux 3.16.0-37-generic x86_64 Ubuntu 14.04.2 LTS auth_master_user_separator = * auth_mechanisms = plain login auth_username_chars = abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@= auth_worker_max_count = 10 base_dir = /var/run/dovecot_director director_mail_servers = server1.internal.mydomain.com server2.internal.mydomain.com director_servers = A.B.C.1 A.B.C.2 # server1 and server2 external IP addresses disable_plaintext_auth = no instance_name = dovecot_director listen = lmtpcluster.mydomain.com, server1.mydomain.com lmtp_proxy = yes login_greeting = IMAP/POP3 server mail_fsync = never mail_gid = dovemail mail_plugins = " quota" mail_uid = dovemail managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave passdb { args = /etc/dovecot_director/dovecot_director-sql.conf.ext driver = sql } passdb { args = /etc/dovecot_director/dovecot_director-sql-master.conf.ext driver = sql master = yes pass = yes } protocols = imap pop3 lmtp service auth-worker { user = $default_internal_user } service auth { client_limit = 10240 process_limit = 1 process_min_avail = 1 } service director { fifo_listener login/proxy-notify { mode = 0666 } inet_listener { address = A.B.C.1 port = 7777 } unix_listener director-userdb { mode = 0600 } unix_listener login/director { mode = 0666 } } service imap-login { executable = imap-login director idle_kill = 10 secs inet_listener imap { port = 143 } process_limit = 400 process_min_avail = 10 service_count = 0 vsz_limit = 512 M } service lmtp { inet_listener lmtp { address = lmtpcluster.internal.mydomain.com, server1.internal.mydomain.com port = 24 } process_limit = 512 } service pop3-login { executable = pop3-login director idle_kill = 10 secs inet_listener pop3 { port = 110 } process_limit = 256 } ssl_cert = </etc/ssl/certs/mydomain.crt ssl_key = </etc/ssl/private/mydomain.key userdb { driver = prefetch } userdb { args = /etc/dovecot_director/dovecot_director-sql.conf.ext driver = sql } verbose_proctitle = yes protocol lmtp { auth_socket_path = director-userdb info_log_path = /var/log/mail/dovecot-director-lmtp.log passdb { args = proxy=y nopassword=y port=1124 driver = static name = } } Thanks in advance, Andre

1 0

Error starting 1.0.15 with SSL_DISABLE=No
by Steve Matzura 11 Jun '15

11 Jun '15

When starting Dovecot 1.0.15 after building it from source using the standard procedure, I receive the following message when starting, even though SLL_DISABLE=No: Error: SSL support not compiled in but ssl_disable=no Fatal: Invalid configuration in /usr/local/etc/dovecot.conf How is SSL support configured and built in? I know it has something to do with the --SSL_CFLAGS flag.

2 2

suggestion: avoid help keeping XP alive
by A. Schulze 10 Jun '15

10 Jun '15

Hello, if possible encourage people to update then helping them keeping horribly outdated XP + OE still alive... Thanks Andreas

1 0

Order of keys
by Steve Matzura 10 Jun '15

10 Jun '15

I hope I'm asking this on the right list, in the right place. I go through this every three years and for whatever reason keep forgetting to record how this works! In the Dovecot config, there are two places to define SSL certificates--ssl_cert_file and ssl_key_file. My question is this: Which two of the three files--the certifying authority, the signed certificate for the specific system, and the private certificate file--are combined to create the file that goes with ssl_cert_file? Since there are six possible permutations to answer this question (because order of files matters), which two go with ssl_crt_file and in what order? I have a private certificate file, the certifying authority's .CRT file, and the certifying authority's signed .PEM file which contains the system's certified certificate. Thanks in advance.

2 1

can't enable sieve on ubuntu trusty
by Mihai Badici 10 Jun '15

10 Jun '15

I try to create a sieve rule on a Ubuntu server ( managed by i-mscp) For this rule i need the editheader extension. I edited /etc/dovecot/conf.d/90-sieve.conf and added the following: plugin { #sieve_extensions = +notify +imapflags sieve_extensions = +editheader .... Restarted dovecot and didn't work Looks like the content of 90-sieve.conf is ignored. dovecot -n show no rule activated: dovecot -n # 2.2.9: /etc/dovecot/dovecot.conf # OS: Linux 3.13.0-53-generic x86_64 Ubuntu 14.04.2 LTS auth_mechanisms = plain login cram-md5 digest-md5 disable_plaintext_auth = no mail_location = maildir:~/ mail_plugins = quota managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave namespace inbox { inbox = yes location = prefix = INBOX. separator = . type = private } passdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } plugin { autocreate = Trash autocreate2 = Spam autocreate3 = Deffered autocreate4 = Whatever autosubscribe = Trash autosubscribe2 = Spam autosubscribe3 = Deffered quota = maildir:User quota quota_rule = *:storage=1GB quota_warning = storage=95%% quota-warning 95 %u quota_warning2 = storage=80%% quota-warning 80 %u } protocols = " imap lmtp sieve pop3" service auth { unix_listener auth-master { mode = 0600 user = vmail } } service quota-warning { executable = script /var/www/imscp/engine/quota/imscp-dovecot-quota.sh group = imscp unix_listener quota-warning { mode = 0600 user = vmail } } ssl_cert = </etc/imscp/imscp_services.pem ssl_key = </etc/imscp/imscp_services.pem ssl_protocols = !SSLv2 !SSLv3 userdb { driver = prefetch } userdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } protocol imap { mail_plugins = quota imap_quota } protocol pop3 { pop3_uidl_format = %u-%v } protocol lda { auth_socket_path = /var/run/dovecot/auth-master mail_plugins = quota postmaster_address = postmaster(a)ispcp.sf-hosting.net } Mihai Badici[1] -------- [1] http://mihai.badici.ro

1 0

Dovecot mbox & other programs
by Pali Rohár 09 Jun '15

09 Jun '15

Hello, I want to use dovecot as imap server with mbox storage format (described at [1]) but I also want to access (and modify!) those mbox files which are stored on server (and used by dovecot). What is correct way to read those mboxes? From wiki page [1] I read that I should ignore first message in mbox (which contains X-IMAPbase header) and mbox file is in mboxcl2 format. And what is correct way to modify that mbox file (which is used by dovecot imap)? I would like to configure mutt on server to directly access those mbox mailboxes without need to use imap protocol (over localhost). It is possible without any data/message damage? [1] - http://wiki2.dovecot.org/MailboxFormat/mbox -- Pali Rohár pali.rohar(a)gmail.com

6 15

special_use \Archive not working with some foldernames
by Hajo Locke 09 Jun '15

09 Jun '15

Hello list, i use dovecot 2.2.18 compiled on my own and want to report an odd behaviour when using a folder for special_use \Archive. In my case it is not working when using some special foldernames (mbox). I compared to version 2.2.15 which i found pre-packaged on launchpad.net, same behaviour. All other special_use Folder work like expected. My situation: We authenticate users using mysql-db. also we allow users to store individuell special_use settings in db. this is a way which was recommended by this mailinglist some years ago. we use a password_query like this: password_query = SELECT `inbox` as `user`, `password`, `home` as userdb_home, `uid` AS userdb_uid, `gid` AS userdb_gid, `userdb_import` AS userdb_userdb_import FROM `mail_users` WHERE `login` = '%u' AND `active`='Y' typical column in db looks like this: | username | cryptedpass | path | inboxname | uid | gid | Y | namespace/inbox/mailbox=Sent namespace/inbox/mailbox/Sent/name=Gesendet namespace/inbox/mailbox/Sent/auto=subscribe namespace/inbox/mailbox/Sent/special_use=\Sent namespace/inbox/mailbox=Drafts namespace/inbox/mailbox/Drafts/name=EntwÃ¼rfe namespace/inbox/mailbox/Drafts/auto=subscribe namespace/inbox/mailbox/Drafts/special_use=\Drafts namespace/inbox/mailbox=Trash namespace/inbox/mailbox/Trash/name=Papierkorb namespace/inbox/mailbox/Trash/auto=subscribe namespace/inbox/mailbox/Trash/special_use=\Trash namespace/inbox/mailbox=Junk namespace/inbox/mailbox/Junk/name=Spam namespace/inbox/mailbox/Junk/auto=subscribe namespace/inbox/mailbox/Junk/special_use=\Junk namespace/inbox/mailbox=Archives namespace/inbox/mailbox/Archives/name=Archiv namespace/inbox/mailbox/Archives/auto=subscribe namespace/inbox/mailbox/Archives/special_use=\Archive | Now i noticed that in this case the folder Archiv was not binded to special_use \Archive: * LIST (\NoInferiors \UnMarked \Junk) "/" Spam * LIST (\NoInferiors \UnMarked \Drafts) "/" Entw&APw-rfe * LIST (\NoInferiors \UnMarked \Sent) "/" Gesendet * LIST (\NoInferiors \UnMarked \Trash) "/" Papierkorb * LIST (\NoInferiors \UnMarked) "/" Archiv * LIST (\HasNoChildren) "/" INBOX If i change the name of folder which is binded to special_use \Archive its working again, no other changes: * LIST (\NoInferiors \UnMarked \Archive) "/" Archiviu or a shorter one: * LIST (\HasNoChildren \Archive) "/" Arc It works in most cases, it is not working if i have chosen name "Archiv". It seems also that autocreating of folder is not working if name is "Archiv". I activated the debug settings but was not helpful. Looks the same in all cases: Debug: Added userdb setting: namespace/inbox/mailbox=Archives Debug: Added userdb setting: namespace/inbox/mailbox/Archives/auto=subscribe Debug: Added userdb setting: namespace/inbox/mailbox/Archives/name=Arc Debug: Added userdb setting: namespace/inbox/mailbox/Archives/special_use=\Archive or: Debug: Added userdb setting: namespace/inbox/mailbox=Archives Debug: Added userdb setting: namespace/inbox/mailbox/Archives/auto=subscribe Debug: Added userdb setting: namespace/inbox/mailbox/Archives/name=Archiviu Debug: Added userdb setting: namespace/inbox/mailbox/Archives/special_use=\Archive or the not working one: Debug: Added userdb setting: namespace/inbox/mailbox=Archives Debug: Added userdb setting: namespace/inbox/mailbox/Archives/auto=subscribe Debug: Added userdb setting: namespace/inbox/mailbox/Archives/name=Archiv Debug: Added userdb setting: namespace/inbox/mailbox/Archives/special_use=\Archive I have no idea what is going wrong here. I have no further hints in my logs. What to do now? Any ideas? Thanks, Hajo

1 0

Re: Dovecot mbox & other programs
by Joseph Tam 08 Jun '15

08 Jun '15

Pali Roh?r <pali.rohar(a)gmail.com> writes: > Still I want read/write access to storage and want to use mbox as > storage (also for easier backup and copy)... Backup performance may be another big win for Maildir, especially for incremental backups. Be that as it may ... > And my question was how to properly read and write from/to mbox files > which are used by dovecot. Dovecot mailbox indices are self-healing: indices should be rengenerated automatically when the mailbox is out of sync with regards to the indices. There may be a few complaints in the mail logs about it (e.g. UIDVALIDITY changes), but they are mostly harmless. Joseph Tam <jtam.home(a)gmail.com>

1 0

LMTPs between proxy and backend
by Patrick Westenberg 05 Jun '15

05 Jun '15

Hi @all, I have a 3 server setup (MX ==LMTP==> Proxy ==LMTP==> Backend). After upgrading to 2.2.18 I was able to use LMTPs from MX to the proxy but not from the proxy to the backend: Received: from mf01.example.net ([172.17.1.5]) by mb01.example.net (Dovecot) with LMTP id T+LnDWrvcVWDSwAAJnBBGg for <patrick(a)example.net>; Fri, 05 Jun 2015 20:50:58 +0200 Received: from mx01.example.net ([172.17.1.5]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits) zlib compression) by mf01.example.net (Dovecot) with LMTP id 8uuXJ13vcVW2fgAATr09kg Can anyone help or is Dovecot not able to use LMTPs as client? Regards Patrick Proxy: # 2.2.18: /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 0.4.8 (0c4ae064f307+) # OS: Linux 3.16.0-0.bpo.4-amd64 x86_64 Debian 7.8 auth_mechanisms = plain login director_mail_servers = 172.17.1.1 172.17.1.2 director_servers = 172.17.1.3 172.17.1.4 director_user_expire = 5 mins lmtp_proxy = yes log_path = /var/log/dovecot.log 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 protocols = imap pop3 lmtp sieve service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } unix_listener auth-userdb { user = dovecot } } service director { fifo_listener login/proxy-notify { mode = 0666 } inet_listener { address = 172.17.1.3 port = 9090 } unix_listener director-userdb { mode = 0600 } unix_listener login/director { mode = 0666 } } service imap-login { executable = imap-login director process_min_avail = 1 service_count = 0 } service lmtp { inet_listener lmtp { address = 172.17.1.3 port = 24 } process_min_avail = 20 } service managesieve-login { executable = managesieve-login director inet_listener sieve { port = 4190 } } service pop3-login { executable = pop3-login director } ssl_cert = </etc/ssl/certs/wildcard.pem ssl_cipher_list = <snip> ssl_dh_parameters_length = 2048 ssl_key = </etc/ssl/private/wildcard.key ssl_prefer_server_ciphers = yes ssl_protocols = !SSLv3 !SSLv2 verbose_proctitle = yes protocol !smtp { passdb { args = proxy=y nopassword=y starttls=any-cert driver = static name = } } protocol smtp { passdb { args = /usr/local/etc/dovecot/dovecot-sql.conf.ext driver = sql name = } userdb { args = /usr/local/etc/dovecot/dovecot-sql.conf.ext driver = sql name = } } protocol lmtp { auth_socket_path = director-userdb } Backend: # 2.2.18: /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 0.4.8 (0c4ae064f307+) # OS: Linux 3.14-0.bpo.1-amd64 x86_64 Debian 7.8 auth_mechanisms = plain login listen = 172.17.1.2 lmtp_save_to_detail_mailbox = yes log_path = /var/log/dovecot.log login_trusted_networks = 172.17.1.3 172.17.1.4 mail_home = /srv/mail/%Ld/%Ln mail_location = maildir:~/Maildir mail_plugins = quota notify replication 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 namespace inbox { inbox = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Spamverdacht { auto = subscribe special_use = \Junk } mailbox Trash { auto = subscribe special_use = \Trash } prefix = INBOX/ separator = / type = private } passdb { args = /usr/local/etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { mail_replica = tcps:mb01.wk-serv.net quota = dict:User quota::file:%h/Maildir/dovecot-quota quota_rule2 = INBOX/Trash:ignore quota_status_nouser = DUNNO quota_status_success = DUNNO quota_warning = storage=90%% quota-warning 90 %u quota_warning2 = storage=75%% quota-warning 75 %u sieve = ~/.dovecot.sieve sieve_after = /usr/local/etc/dovecot/sieve/sieve_after.sieve sieve_default = /usr/local/etc/dovecot/sieve/default.sieve sieve_dir = ~/sieve } postmaster_address = postmaster(a)wk-serv.de protocols = imap pop3 lmtp sieve service aggregator { fifo_listener replication-notify-fifo { user = vmail } unix_listener replication-notify { user = vmail } } service auth { unix_listener auth-userdb { group = vmail mode = 0666 user = vmail } } service config { unix_listener config { mode = 0600 user = vmail } } service doveadm { inet_listener { port = 12345 ssl = yes } } service imap-login { process_min_avail = 2 service_count = 0 } service lmtp { inet_listener lmtp { address = 172.17.1.2 port = 24 } process_min_avail = 20 } service managesieve-login { inet_listener sieve { port = 4190 } } service quota-status { client_limit = 1 executable = quota-status -p postfix inet_listener { port = 12340 } } service quota-warning { executable = script /usr/local/etc/dovecot/quota_warning.sh unix_listener quota-warning { user = vmail } user = root } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { mode = 0600 user = vmail } } ssl = required ssl_cert = </etc/ssl/certs/wildcard.crt ssl_client_ca_file = /etc/ssl/certs/startssl-bundle.pem ssl_key = </etc/ssl/private/wildcard.key ssl_protocols = !SSLv3 !SSLv2 userdb { driver = prefetch } userdb { args = /usr/local/etc/dovecot/dovecot-sql.conf.ext driver = sql } verbose_proctitle = yes protocol lmtp { mail_plugins = quota notify replication sieve } protocol imap { mail_max_userip_connections = 30 mail_plugins = quota notify replication imap_quota }

1 0

Does Dovecot allow different clients to subscribe different subsets of IMAP folders?
by Steve 04 Jun '15

04 Jun '15

I have a working Dovecot IMAP server (v. 2.2.9) where I have a single user but a lot of folders (over 800 in total, hierarchically arranged, about 50 of which are in active use.) I have multiple clients (including k9Mail on Android and Thunderbird on Linux and Windows). These clients all present a consistent subscription to a single subset of the available folders . What I'd like to be able to do is (somehow) allow different devices (different email clients) to subscribe to a different subset of folders. For example, I may want K9mail on my phone to be subscribed only to my "main Inbox" - but for Thunderbird on Windows to also be subscribed to active mailing-list folders. Does Dovecot support such a mode of operation? If so, how do I configure it? If not, what options are there to achieve the desired end result - i.e. different devices/IMAP clients subscribed to different subsets of the universe of folders available to a single user. Mandatory details: Version : 2.2.9 Configuration: See http://paste.ubuntu.com/11564807/

3 4

Testing SHA512-CRYPT password hashes with doveadm pw -t fails
by Felix Zielcke 04 Jun '15

04 Jun '15

Hi, I use Debian jessie with Dovecot 2.2.13-11. While writing a script for Horde to change the passwords in my passwd file I noticed doveadm pw -t fails for SHA512-CRYPT: # doveadm pw -s SHA1 -p test {SHA1}qUqP5cyxm6YcTAhz05Hph5gvu9M= # doveadm pw -t {SHA1}qUqP5cyxm6YcTAhz05Hph5gvu9M= -p test {SHA1}qUqP5cyxm6YcTAhz05Hph5gvu9M= (verified) # doveadm pw -s SHA512-CRYPT -p test {SHA512-CRYPT}$6$8FfoioQWQDR/Vuzu$ynKiO/E6Xf4dMvfx2LsP9KQotqy5cEOEppnEh5Hqe1UpCYAgOwSIJlNb0O65fxdYcRZH3gNFQ7ZOM/2kD/R811 doveadm pw -t {SHA512-CRYPT}$6$8FfoioQWQDR/Vuzu$ynKiO/E6Xf4dMvfx2LsP9KQotqy5cEOEppnEh5Hqe1UpCYAgOwSIJlNb0O65fxdYcRZH3gNFQ7ZOM/2kD/R811 -p test doveadm(root): Fatal: reverse password verification check failed: Password mismatch If this can't work for SHA512-CRYPT then at least the error message should be more helpful. Or am I understanding the -t option wrongly? Then this sohuld be maybe somewhere clarified. I just use now doveadm auth test which works fine. Regards, Felix Zielcke

2 2

Misleading SSL/TLS Log Messages
by Yahooguntu 03 Jun '15

03 Jun '15

Hi all, I think I've found a small bug in how Dovecot logs SSL/TLS info. Basically, if I connect to the server using TLS, the logs have a lot of entries saying I used SSLv3 (which is not allowed). Here's my system info: OSX Yosemite (x86_64, HFS+) Dovecot 2.2.15 (via Homebrew) OpenSSL 0.9.8zd The configuration (see below) disallows SSLv3, and if I try and connect with OpenSSL to test that ("openssl s_client -connect localhost:993 -ssl3") it fails as expected. If I do the same command, but with "-tls1" instead of "-ssl3", I can connect and run IMAP commands. The problem is, if I open up the Dovecot logs and look at the SSL log messages, they all say I used SSLv3. As an example, this is a truncated log from when I connected to the server and immediately did a LOGOUT: 14:50:59 : master: Warning: Killed with signal 15 (by pid=1 uid=0 code=unknown 0) 14:51:03 : master: Dovecot v2.2.15 starting up for imap, lmtp (core dumps disabled) 14:51:13 : imap-login: Debug: SSL: elliptic curve secp384r1 will be used for ECDH and ECDHE key exchanges 14:51:13 --- last message repeated 1 time --- 14:51:13 : imap-login: Debug: SSL: where=0x10, ret=1: before/accept initialization [127.0.0.1] 14:51:13 : imap-login: Debug: SSL: where=0x2001, ret=1: before/accept initialization [127.0.0.1] 14:51:13 : imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3 read client hello A [127.0.0.1] 14:51:13 : imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3 write server hello A [127.0.0.1] 14:51:13 : imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3 write certificate A [127.0.0.1] 14:51:13 : imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3 write key exchange A [127.0.0.1] 14:51:13 : imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3 write server done A [127.0.0.1] 14:51:13 : imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3 flush data [127.0.0.1] 14:51:13 : imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3 read client certificate A [127.0.0.1] 14:51:13 : imap-login: Debug: SSL: where=0x2002, ret=-1: SSLv3 read client key exchange A [127.0.0.1] 14:51:13 --- last message repeated 1 time --- 14:51:13 : imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3 read client key exchange A [127.0.0.1] 14:51:13 : imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3 read finished A [127.0.0.1] 14:51:13 : imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3 write session ticket A [127.0.0.1] 14:51:13 : imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3 write change cipher spec A [127.0.0.1] 14:51:13 : imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3 write finished A [127.0.0.1] 14:51:13 : imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3 flush data [127.0.0.1] 14:51:13 : imap-login: Debug: SSL: where=0x20, ret=1: SSL negotiation finished successfully [127.0.0.1] 14:51:13 : imap-login: Debug: SSL: where=0x2002, ret=1: SSL negotiation finished successfully [127.0.0.1] 14:51:19 : imap-login: Aborted login (no auth attempts in 6 secs): user=<>, rip=127.0.0.1, lip=127.0.0.1, TLS, session=<QdX1YaIXTQB/AAAB> 14:51:19 : imap-login: Debug: SSL alert: close notify [127.0.0.1] The second to last line, which indicates I never tried to log in, correctly states that I used TLS. All the lines for SSL debugging, though, state I used SSL or SSLv3. This is a test setup, so it accepts any mail from @example.com addresses over LMTP and allows any user to connect with the password "staticpassword". Here's the output of "dovecot -n": # 2.2.15: /usr/local/etc/dovecot/dovecot.conf # OS: Darwin 14.3.0 x86_64 hfs default_client_limit = 50 default_internal_user = _dovecot default_login_user = _dovenull default_process_limit = 10 listen = 127.0.0.1 mail_gid = admin mail_location = mbox:/usr/local/etc/dovecot/mailboxes/%n mail_uid = [my username] namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { args = password=staticpassword driver = static } postmaster_address = postmaster at example.com protocols = imap lmtp service lmtp { inet_listener lmtp { address = 127.0.0.1 ::1 port = 24 } } ssl = required ssl_cert = </usr/local/etc/dovecot/ssl/cert.pem ssl_key = </usr/local/etc/dovecot/ssl/key.pem ssl_protocols = !SSLv2 !SSLv3 verbose_ssl = yes

2 1

indexer-worker crashes handling mails with big attachments (dovecot 2.2.16/2.2.18 + FTS Apache Solr + Tika)
by Robinson Bomze 03 Jun '15

03 Jun '15

Hi, yesterday i tried to setup Dovecot with Solr (3.6.2) + Tika (1.8) for FTS. i used a fresh Debian 8.0 system in the beginning with Dovecot 2.2.13 from the Debian repository. After i got some issues with Tika/Dovecot and i read on the mailinglist that these problems where fixed in 2.2.14+, so i tried 2.2.18. With 2.2.18 i get panics with big (ok... huge) attachments. Most mailboxes (and their attachments) get index fine, but on some i got panics from the indexer-worker. i was able to isolate the problem. It seems that when Tika (which works flawless) sends a big reply to Dovecot and Dovecot sends this data to Solr, communication crashes between Dovecot and Solr. Eg. indexing an email with a 200k char wordfile results in a panic of the indexer-worker: Jun 02 23:50:57 indexer-worker(username): Warning: I/O leak: 0x7ff65f39f540 (line 120, fd 20) Jun 02 23:50:57 indexer-worker(username): Warning: Timeout leak: 0x7ff65f39f2e0 (line 325) Jun 02 23:50:57 indexer: Error: Indexer worker disconnected, discarding 1 requests for username Jun 02 23:50:57 imap(username): Error: indexer failed to index mailbox INBOX.username Jun 02 23:50:57 indexer-worker(username): Fatal: master: service(indexer-worker): child 11429 killed with signal 11 (core dumped) I got similar issues results with 2.2.16: Jun 02 23:21:12 indexer-worker(username): Warning: I/O leak: 0x7ffff7811cc0 (line 127, fd 20) Jun 02 23:21:12 indexer-worker(username): Panic: file ioloop.c: line 39 (io_add_file): assertion failed: (callback != NULL) Jun 02 23:21:12 indexer-worker(username): Error: Raw backtrace: /usr/local/lib/dovecot/libdovecot.so.0(+0x77130) [0x7ffff7842130] -> /usr/local/lib/dovecot/libdovecot.so.0(+0x7 Jun 02 23:21:12 indexer: Error: Indexer worker disconnected, discarding 1 requests for username Jun 02 23:21:12 imap(username): Error: indexer failed to index mailbox INBOX.username Jun 02 23:21:12 indexer-worker(username): Fatal: master: service(indexer-worker): child 7909 killed with signal 6 (core dumps disabled) The problem was already posted: http://dovecot.org/pipermail/dovecot/2015-May/100901.html I could trigger the same panic running the indexer via 'doveadm index -u username MAILBOX'. Here is a backtrace (bt) of the 2.2.18-crash (on line #8 you see a fragement of the text sent to solr): #0 array_count_i (array=0x8) at array.h:155 #1 array_get_modifiable_i (count_r=<synthetic pointer>, array=0x8) at array.h:228 #2 priorityq_remove_idx (pq=0x0, idx=0) at priorityq.c:121 #3 0x00007ff65f3ef5eb in priorityq_remove (pq=<optimized out>, item=item@entry=0xa26920) at priorityq.c:138 #4 0x00007ff65f3e1e70 in timeout_remove (_timeout=<optimized out>) at ioloop.c:288 #5 0x00007ff65f3e2781 in io_loop_move_timeout (_timeout=_timeout@entry=0xa27f98) at ioloop.c:861 #6 0x00007ff65f39ff37 in http_client_connection_switch_ioloop (conn=conn@entry=0xa27ea0) at http-client-connection.c:1357 #7 0x00007ff65f3a3d68 in http_client_switch_ioloop (client=client@entry=0xa0bf20) at http-client.c:211 #8 0x00007ff65f39c005 in http_client_request_continue_payload (_req=_req@entry=0xa0ee88, data=0xa42fa0 "k for evidence of fluid spill.\nIf the device is mounted on a stand, examine the condition of the mount.\nIf the device moves on casters, check the condition of the casters. Check operation of brakes, i"..., size=55453) at http-client-request.c:566 #9 0x00007ff65f39c22a in http_client_request_send_payload (_req=_req@entry=0xa0ee88, data=<optimized out>, size=<optimized out>) at http-client-request.c:625 #10 0x00007ff65e972429 in solr_connection_post_more (post=0xa0ee80, data=<optimized out>, size=size@entry=55453) at solr-connection.c:504 #11 0x00007ff65e96ea09 in fts_backed_solr_build_commit (ctx=0xa1a880) at fts-backend-solr.c:341 #12 0x00007ff65e96eaad in fts_backend_solr_update_set_mailbox (_ctx=0xa1a880, box=0x0) at fts-backend-solr.c:407 #13 0x00007ff65eb7cfac in fts_backend_set_cur_mailbox (ctx=ctx@entry=0xa1a880) at fts-api.c:129 #14 0x00007ff65eb7cfe3 in fts_backend_update_deinit (_ctx=<optimized out>) at fts-api.c:143 #15 0x00007ff65eb8303c in fts_transaction_end (t=t@entry=0xa11ed0) at fts-storage.c:550 #16 0x00007ff65eb83e91 in fts_transaction_commit (t=0xa11ed0, changes_r=0x7ffdcdca5e30) at fts-storage.c:615 #17 0x00007ff65f688a82 in mailbox_transaction_commit_get_changes (_t=_t@entry=0x7ffdcdca5ee0, changes_r=changes_r@entry=0x7ffdcdca5e30) at mail-storage.c:1837 #18 0x00007ff65f688b2e in mailbox_transaction_commit (t=t@entry=0x7ffdcdca5ee0) at mail-storage.c:1818 "bt full" looks like this: #0 array_count_i (array=0x8) at array.h:155 No locals. #1 array_get_modifiable_i (count_r=<synthetic pointer>, array=0x8) at array.h:228 No locals. #2 priorityq_remove_idx (pq=0x0, idx=0) at priorityq.c:121 count = <optimized out> #3 0x00007ff65f3ef5eb in priorityq_remove (pq=<optimized out>, item=item@entry=0xa26920) at priorityq.c:138 No locals. #4 0x00007ff65f3e1e70 in timeout_remove (_timeout=<optimized out>) at ioloop.c:288 timeout = 0xa26920 #5 0x00007ff65f3e2781 in io_loop_move_timeout (_timeout=_timeout@entry=0xa27f98) at ioloop.c:861 new_to = 0xa1adf0 old_to = <optimized out> #6 0x00007ff65f39ff37 in http_client_connection_switch_ioloop (conn=conn@entry=0xa27ea0) at http-client-connection.c:1357 No locals. #7 0x00007ff65f3a3d68 in http_client_switch_ioloop (client=client@entry=0xa0bf20) at http-client.c:211 conn = 0xa27ea0 _conn = 0xa27ea0 host = <optimized out> peer = <optimized out> #8 0x00007ff65f39c005 in http_client_request_continue_payload (_req=_req@entry=0xa0ee88, data=0xa42fa0 "k for evidence of fluid spill.\nIf the device is mounted on a stand, examine the condition of the mount.\nIf the device moves on casters, check the condition of the casters. Check operation of brakes, i"..., size=55453) at http-client-request.c:566 prev_ioloop = 0x9f4730 req = 0xa36970 conn = 0xa27ea0 client = 0xa0bf20 ret = <optimized out> __FUNCTION__ = "http_client_request_continue_payload" #9 0x00007ff65f39c22a in http_client_request_send_payload (_req=_req@entry=0xa0ee88, data=<optimized out>, size=<optimized out>) at http-client-request.c:625 __FUNCTION__ = "http_client_request_send_payload" #10 0x00007ff65e972429 in solr_connection_post_more (post=0xa0ee80, data=<optimized out>, size=size@entry=55453) at solr-connection.c:504 conn = 0xa0be50 __FUNCTION__ = "solr_connection_post_more" Hope anyone fixes the code... i need this feature :) Thanks a lot in advance!

2 1

multi sync (>2 servers) + selective sync + trigger
by b-dovecot.org＠grmbl.net 03 Jun '15

03 Jun '15

Hi all, I've been researching ways to replicate mail across multiple mailstores and have a few questions. Synching 2 mailstores (M1 & M2) via dsync works fine. I want to add a 3rd and 4th (M3 & M4) server to also be synced. Multi-sync (>2 servers): 1) How do I tell M1 and/or M2 to also sync to M3 and/or M4? Selective sync: 2) How do I sync specific domains to specific servers and not to others? Trigger: 3) Does a normal sync check only check the mailbox being changed or does it get triggered on mailbox changes to check ALL indexes and sync all changed mailboxes accordingly? 4) Can I use an email to trigger a sync for any other mailboxes which might be out of sync? TIA B

3 3

Outlook Express with XP...
by SH Development 03 Jun '15

03 Jun '15

Dovecot 2.0.9 I am able to connect successfully with Thunderbird, Win 8, Apple Mail, iPhone, iPad. Outlook Express on Win XP receives just fine, but will not send. I get a "Client host rejected: Access denied” message. I believe this is simply Postfix telling me the connection isn’t properly authenticated, as setting up the exact same credentials on another client (non OE) works. It is only with OE on XP that I am unable to send/authenticate. I have literally tried every combination of settings in OE and nothing works. What else might I need to enable to get this working? Using SSL, ports 993, 587 PLAINTEXT. dovecot -n as follows: # 2.0.9: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-504.16.2.el6.x86_64 x86_64 CentOS release 6.6 (Final) ext4 log_timestamp = "%Y-%m-%d %H:%M:%S " mail_location = maildir:/home/vmail/%d/%n/Maildir mail_max_userip_connections = 50 namespace { inbox = yes location = prefix = INBOX. separator = . type = private } passdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } protocols = imap pop3 service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-master { mode = 0600 user = vmail } user = root } ssl_ca = </etc/pki/dovecot/certs/intermediate.pem ssl_cert = </etc/pki/dovecot/certs/dovecot.pem ssl_key = </etc/pki/dovecot/private/dovecot.pem userdb { args = uid=5000 gid=5000 home=/home/vmail/%d/%n allow_all_users=yes driver = static } protocol lda { auth_socket_path = /var/run/dovecot/auth-master log_path = /home/vmail/dovecot-deliver.log postmaster_address = postmaster(a)starionhost.net } protocol pop3 { pop3_uidl_format = %08Xu%08Xv }

7 11

Re: Outlook Express with XP...
by Joseph Tam 02 Jun '15

02 Jun '15

SH Development writes: > I have literally tried every combination of settings in OE and nothing > works. What else might I need to enable to get this working? > > Using SSL, ports 993, 587 PLAINTEXT. As others have noted, your MTA handles the connection. I believe Windows XP needs to be updated to the latest service patch to handle SSLv3 disabled sites. Try checking to make sure your Postfix SSL security settings and your WinXP SSL capabilities are compatible. Joseph Tam <jtam.home(a)gmail.com>

1 0

Pop3 service stops responding
by Mike Eriksson 02 Jun '15

02 Jun '15

Hi! I have problem with the pop3 service stops responding at random intervals on my server. We started to notice this problem as we're running icinga to check the imap & pop3 service. When icinga reports that the service is down. We try to telnet to the server on port 110 but it refuses the connection. I've checked the netstat during this time and it's listens on port 110. My first thought we were hitting the max connections and similar. Changed login_max_connections from 128 to 256. Didnt solve the problem. Started the debug on the dovecot server but could not see anything in the logs. Also the error log or the syslog dosnt report anything that I can see. Best thing would of course be to start and upgrade the software and os(Debian 5) but I'm not comfortable upgrading it at the moment as my knowledge about dovecot / postfix isn't great. Do you have any idéas how to move forward? dovecot -n # 1.0.15: /etc/dovecot/dovecot.conf base_dir: /var/run/dovecot/ log_path: /var/log/dovecot-error.log info_log_path: /var/log/dovecot-info.log log_timestamp: %Y-%m-%d %H:%M:%S protocols: pop3 imap imaps pop3s ssl_cipher_list: ALL:!LOW disable_plaintext_auth: no login_dir: /var/run/dovecot//login login_executable(default): /usr/lib/dovecot/imap-login login_executable(imap): /usr/lib/dovecot/imap-login login_executable(pop3): /usr/lib/dovecot/pop3-login login_max_processes_count: 256 first_valid_uid: 1090 last_valid_uid: 1090 first_valid_gid: 1090 last_valid_gid: 1090 mail_privileged_group: mail mail_location: maildir:~/Maildir mail_executable(default): /usr/lib/dovecot/imap mail_executable(imap): /usr/lib/dovecot/imap mail_executable(pop3): /usr/lib/dovecot/pop3 mail_plugins(default): quota imap_quota mail_plugins(imap): quota imap_quota mail_plugins(pop3): quota mail_plugin_dir(default): /usr/lib/dovecot/modules/imap mail_plugin_dir(imap): /usr/lib/dovecot/modules/imap mail_plugin_dir(pop3): /usr/lib/dovecot/modules/pop3 pop3_uidl_format(default): pop3_uidl_format(imap): pop3_uidl_format(pop3): %08Xu%08Xv auth default: username_chars: abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@% username_translation: %@ username_format: %Lu passdb: driver: sql args: /etc/dovecot/dovecot-sql.conf userdb: driver: passwd userdb: driver: sql args: /etc/dovecot/dovecot-sql.conf socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix master: path: /var/run/dovecot/auth-master mode: 384 user: vmail group: vmail plugin: quota: maildir sieve_global_path: /etc/dovecot/sieve_scripts/spam-sort.sieve login_max_processes_count: 256 login_max_connections: 256 max_mail_processes: 1024 Best Regards Mike

2 1

Failed running extprograms execute via socket - fatal recv(MSG_PEEK) failed disconnected
by E.B. 01 Jun '15

01 Jun '15

I switched from running my extprograms execute script directly to running with dovecot socket. Log shows only this dovecot: lmtp(test(a)example.com): Debug: wdi0Tb5VPlGfPnEAM/SpMA: sieve: action execute: running program: test dovecot: lmtp(test(a)example.com): Debug: Namespace : Using permissions from /vmail/example.com/test: mode=0770 gid=default dovecot: script: Fatal: recv(MSG_PEEK) failed: disconnected For testing I opened up the script and socket with permissions 777 but the error seems to indicate less about permissions more about some kind of protocol problem i guessing. Sieve script calls using this: execute "test"; Plugin config: plugin { sieve_plugins = sieve_extprograms sieve_global_extensions = +vnd.dovecot.execute sieve_execute_socket_dir = sieve-execute sieve_before = /usr/local/etc/dovecot/sieve } service test { executable = script /usr/local/etc/dovecot/sieve_globals/test.sh unix_listener sieve-execute/test { mode = 0660 group = vmail } } FYI I have quota-warning sockets configured identical to this and they work good. Dovecot 2.2.16 Pigeonhole 0.4.7 Help appreciate a lot.

2 14

Sieve extprograms ?not exexuting?
by E.B. 01 Jun '15

01 Jun '15

Hello, I was testing the extprograms plugin. I think I had it working in the past, but many things have changed since then, so no use trying to figure out where it broke - starting over again... Debug-enabled log give me: Apr 27 04:11:36 mail dovecot: lmtp(test(a)example.com): Debug: qOGyA0DePHVaOyHEM/SpMA: sieve: action execute: running program: test.sh Apr 27 04:11:36 mail dovecot: lmtp(test(a)example.com): Debug: waiting for program `/usr/local/etc/dovecot/sieve_globals/test.sh' to finish after 0 seconds So I guess it thinks it is running my script? But simple test script does nothing. Here it is: #!/bin/sh read INPUT INPUT="Hello world: $INPUT" echo "$INPUT" >> /tmp/hello echo "---------------------------" >> /tmp/hello Permissions on this script file for now are rwxrwxrwx But nothing goes to /tmp/hello at all. Script works when I run it manually. I also tried without the "read" but I think that's required isn't it? Anyway, what else can I do to debug this? Dovecot 2.2.16 Pigeonhole 0.4.7

4 7

OT: Central sieve management
by list＠airstreamcomm.net 29 May '15

29 May '15

A bit off topic, but I was wondering if anyone here has a solution for centrally managing sieve for multiple users from a custom web application? We would like to implement pigeonhole sieve on our dovecot cluster, however we need to be able to access user’s sieve configurations from a central location for troubleshooting and support purposes.

3 3

Enabling Master User for migration
by Charles Marcus 29 May '15

29 May '15

Hi all, Ok, just need a quick-n-dirty way to enable a master user for a migration... Reading the docs, I'm not sure what the bare minimum is I need to do this... At: http://wiki2.dovecot.org/Authentication/MasterUsers The Example config shows: auth_master_user_separator = * passdb { driver = passwd-file args = /etc/dovecot/passwd.masterusers master = yes pass = yes } passdb { driver = shadow } userdb { driver = passwd } But, if I'm using a non-real user (just need a master user that can log in as all other users for the migration), do I need all three of these? Or just the first two? Or, just the first one? I think I need the first two and not the last one, but am unsure. This is on a production system so don't want to break things, and I'm unfamiliar with using multiple passdb's... Thanks, Charles

2 6

Shared inbox?
by Chris Ross 29 May '15

29 May '15

I'm running dovecot 2.2.16 on my FreeBSD mail server. I've read information on the wiki about setting up shared mailboxes, but I want to do something that isn't really coved by the instructions I was reading there. My son (now 7 years old) has an account on the system, but doesn't use it directly. But, for things he's interested in like Minecraft, and/or the local zoo, we have given out his email address in a small number of places. What I would like to set up, both for now while he's not actually ever reading his email himself, and perhaps even for the future when we teach and/or allow for that, is for my wife and I to be able to "view" his inbox from our accounts. The instructions for setting up shared folders all are written so that they're secondary folders to all accounts. Is there a way to either (a) configure sharing someone elses Inbox by other accounts, or (b) setting up a separately configured shared folder to _act_ as the inbox for a single account? Thanks. Any suggestions to achieve the above described end goal would be appreciated. - Chris

3 6

Creating IMAP folders/subfolders with Thunderbird
by Alex Regan 29 May '15

29 May '15

Hi, I have dovecot-2.2.15 on fedora21 with Thunderbird and having some difficulty creating subfolders and deleting folders. Creating subfolders results in a folder at the root with a caret instead of a slash called folder^subfolder with an entry in .subscriptions with that name, instead of a new folder under the directory. I'm also unable to delete any folders. The command from within Thunderbird is just completely ignored. Any idea what's happening here? Thanks, Alex

2 2

X-UID in mail header is removed?
by mkawada＠redhat.com 28 May '15

28 May '15

Dear Dovecot Mailing List, I have 2 questions regarding dovecot and would very much appreciate if you would kindly give me helps. <Question 1> Is 'X-UID' no longer shown in mail header via pop3? I have checked with the following 3 version of dovecot packages in order to make sure if a message sent by dovecot have 'X-UID' in its mail header, and the result is that only "dovecot-0.99.11-10.EL4" shows 'X-UID' and the other ones do not(Please see the result written in the second half of this mail). <Question 2> Is 'X-UID' used for checking if a message has already been sent to a user so that he never gets any duplicated mails that are already in his mbox? The reason why I am asking this here is that I am working on a problem that a user sometimes gets a duplicated mail from dovecot if the user keeps mails on the server as its settings. I actually thought this kind of thing would happen if the 'UIDL' gets corrupted or changed for some reasons. However, it is said that this issue never happened in using "dovecot-0.99.11-10.EL4" which shows 'X-UID' in mail header and in using "dovecot-2.0.9-8.el6_6.4" which does not show 'X-UID', the issue happens sometimes. Thus, I would like information indicating what is exactly used to avoid getting any duplicated messages while downloading a message via pop3 from dovecot. Here is the test result I checked: (dovecot-0.99.11-10.EL4) ]# telnet localhost 110 Trying 127.0.0.1... Connected to localhost.localdomain (127.0.0.1). Escape character is '^]'. +OK dovecot ready. user test +OK pass password +OK Logged in. list +OK 1 messages: 1 786 . RETR 1 +OK 786 octets Return-Path: <root(a)localhost.localdomain> Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by localhost.localdomain (8.13.1/8.13.1) with ESMTP id t4S4dBcu006057 for <test(a)localhost.localdomain>; Thu, 28 May 2015 13:39:11 +0900 Received: (from root@localhost) by localhost.localdomain (8.13.1/8.13.1/Submit) id t4S4dB6u006056 for test; Thu, 28 May 2015 13:39:11 +0900 Date: Thu, 28 May 2015 13:39:11 +0900 From: root <root(a)localhost.localdomain> Message-Id: <201505280439.t4S4dB6u006056(a)localhost.localdomain> To: test(a)localhost.localdomain Subject: test mail X-IMAPbase: 1432787986 1 Status: O X-UID: 1 <--X-UID shown here Content-Length: 5 X-Keywords: test . UIDL +OK 1 1432787986.1 (dovecot-1.0.7-9.el5_11.4) ]# telnet localhost 110 Trying 127.0.0.1... Connected to localhost.localdomain (127.0.0.1). Escape character is '^]'. +OK Dovecot ready. user test +OK pass password +OK Logged in. list +OK 1 messages: 1 606 . RETR 1 +OK 606 octets Return-Path: <root(a)localhost.localdomain> Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by localhost.localdomain (8.13.8/8.13.8) with ESMTP id t4S27gBo007199 for <test(a)localhost.localdomain>; Thu, 28 May 2015 11:07:42 +0900 Received: (from root@localhost) by localhost.localdomain (8.13.8/8.13.8/Submit) id t4S27fXd007197 for test; Thu, 28 May 2015 11:07:41 +0900 Date: Thu, 28 May 2015 11:07:41 +0900 From: root <root(a)localhost.localdomain> Message-Id: <201505280207.t4S27fXd007197(a)localhost.localdomain> To: test(a)localhost.localdomain Subject: testmail test . UIDL +OK 1 0000000155667888 . (dovecot-2.0.9-8.el6_6.4) ]# telnet localhost 110 Trying ::1... telnet: connect to address ::1: Connection refused Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. +OK Dovecot ready. user test +OK pass password +OK Logged in. list +OK 1 messages: 1 605 . RETR 1 +OK 605 octets Return-Path: <root(a)localhost.localdomain> X-Original-To: test Delivered-To: test(a)localhost.localdomain Received: by localhost.localdomain (Postfix, from userid 0) id 3629F4336A; Wed, 27 May 2015 11:34:39 +0900 (JST) Date: Wed, 27 May 2015 11:34:39 +0900 To: test(a)localhost.localdomain Subject: test mail User-Agent: Heirloom mailx 12.4 7/29/08 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20150527023439.3629F4336A(a)localhost.localdomain> From: root(a)localhost.localdomain (root) test . UIDL +OK 1 0000000155652c77 Thanks, Masaharu Kawada

1 0

Re: FREAK/Logjam, and SSL protocols to use
by Jacques Distler 27 May '15

27 May '15

> For a given computational effort, you get the most bang-for-the-buck by > choosing large parameters (and checking very carefully that they are > "safe") rather than smaller parameters (and/or checking them less > carefully) which you then regenerate. This discussion (on the OpenSSH mailing list) http://marc.info/?t=143221614200001 may be helpful to those thinking about this.

1 0

Re: FREAK/Logjam, and SSL protocols to use
by Jacques Distler 27 May '15

27 May '15

>But when you write NOT to regenerate, are you saying that using larger primes makes regenerating unnecessary, or are you telling us that it's somehow harmful? For a given computational effort, you get the most bang-for-the-buck by choosing large parameters (and checking very carefully that they are "safe") rather than smaller parameters (and/or checking them less carefully) which you then regenerate. Every time you regenerate, there's a small (but finite) probability that the new parameters are actually unsafe. You'd do better using those CPU cycles to improve the proof that your original set of parameters was safe (admittedly, no one actually does this), rather than generating a new set. Remember, the DH parameters (p,g) are NOT secret; they are transmitted in the clear everytime. As long as you're using Ephemeral Diffie-Hellman (choosing new exponents, a and b, for each session) with large safe DH parameters, it's hard to think of a threat model where you improve the security AT ALL by regenerating the DH parameters.

1 0

Re: FREAK/Logjam, and SSL protocols to use
by Jacques Distler 27 May '15

27 May '15

>It is not at this point emphasized anywhere, including on weakdh.org, that it is actually of high importance to regenerate your DH parameters frequently. That's not really correct. If you're using a prime of length at least 2048 bits, then the corresponding discrete-log problem is well-beyond the pre-computation ability of the NSA (or anyone else). It is computationally intensive to generate such large primes, p (and corresponding base parameter, g). You need to ensure that p is actually prime (the costly step [1]) and that g is primitive. Which is why most implementations have used shorter (<= 1024 bit) primes. Using shorter primes, and regenerating DH parameters at regular intervals, is only a linear-time improvement. By contrast, generating longer DH parameters (without bothering to regenerate) is an EXPONENTIAL improvement in security. So the best setting is to set ssl_dh_parameters_length as large as feasible ([2] recommends 2048 bits), and NOT to regenerate. [1] http://en.wikipedia.org/wiki/Miller%E2%80%93Rabin_primality_test [2] https://weakdh.org/sysadmin.html

2 1

FREAK/Logjam, and SSL protocols to use
by Ron Leach 27 May '15

27 May '15

List, good afternoon, I was reading up on a TLS Diffie Hellman protocol weakness described here https://weakdh.org/sysadmin.html which is similar to the earlier FREAK attack, and can result in downgrade of cipher suites. Part of the solution workaround that the researchers describe for Dovecot here https://weakdh.org/sysadmin.html includes altering DH parameters length to 2048, and re-specifying the allowable cipher suites - they give their suggestion. But the researchers make no comment on the allowable protocols that, in Dovecot, are controlled in 10-ssl.conf in the stanza headed # SSL protocols to use #ssl_protocols = !SSLv2 I couldn't find any advice on up-to-date SSL/TLS protocol settings in the Dovecot wiki, either (I looked in http://wiki2.dovecot.org/SSL/DovecotConfiguration ). At the moment our installation is using only the default settings for allowed protocols; I'm not sure what those defaults might be, but our 10-ssl.conf may only be disallowing SSLv2, if the 'example' entry is the default. We're running 2.2.15, and are due to upgrade to 2.2.18 shortly; quite possibly the defaults differ in a more recent release. What SSL protocols do folk on the list recommend should be allowed in Dovecot these days? (Actually, I mean which protocols really 'must' be disallowed?) regards, Ron

5 10

/etc/ssl/certs/dovecot.pem erased by OpenSuse's update mechanism
by Wolfgang Gross 27 May '15

27 May '15

Hi, this is not a genuine Dovecot bug, more a nuisance. It applies to OpenSuse 13.2 but maybe also to other Linux's. The standard installation of Dovecot (especially 10-ssl.conf) places the certificate dovecot.pem in /etc/ssl/certs. Sometimes during updates does OpenSuse renew all certificates in /etc/ssl/certs and erases dovecot.pem. This blocks further access to the mailbox. I found a similar report here: https://bbs.archlinux.de/viewtopic.php?id=27288 Workaround: Move dovecot.pem to another directory and change 10-ssl.conf accordingly. Regards Wolfgang Gross -- Dr. W. Gross Sektion Chirurgische Forschung Klinik für Allgemein-, Viszeral- und Transplantationschirurgie Universitätsklinikum Heidelberg Im Neuenheimer Feld 365, D-69120 Heidelberg, Germany Tel. ++49 (0)6221/566392, Fax: ++49 (0)6221/566402 WGross(a)uni-hd.de

3 3

Can email be shared between POP3 and shell account access?
by Steve Matzura 26 May '15

26 May '15

I needed to receive a message to admin(a)mydomain.com. I waited and waited for it, but it never showed up in the admin mailbox on the mydomain.com machine. So I looked for the admin account in /etc/dovecot.passwd, and there it was, plain-text password and all! I set up a retrieval system for the admin POP3 account and got all the messages I was waiting for, not to mention about 20 that I wasn't, which were obviously old and discardable. This got me to thinking, is it possible to have an account accessible not just via POP3 from the ouside, but through mail/mailx on the inside, and if so, how is that set up?

3 3

sieve: extract first chars of body in sieve script
by Ingo Thierack 26 May '15

26 May '15

Hello, is it possible to extract the first x chars of the body of an message to forward it, or the complete body inside an sieve script. I want to forward specific mails via telegram-messenger. No Problem to extract the "from" and the "subject". if header :matches "Subject" "*" { set "subject" "${1}"; } if header :matches "from" "*" { set "from" "${1}"; } pipe :copy :try "notify.sh" [ "(${from})# ${subject}" ]; But is it also possible for the body? If I can only pass the complete body, I can cut out the first x chars inside the notify-script. Can't find any hint for that. Regards Ingo

2 1

Segfault on "doveadm sync -u <an-specific-user> tcp:<other-node-ip>:port"
by Listas＠Adminlinux 25 May '15

25 May '15

Hi! When I run "doveadm sync -u <an-specific-user> tcp:192.168.0.2:12345", I get this error: http://pastebin.com/NxyyNGJk Only to one specific user... I've tried to repair with "doveadm force-resync", unsuccessfully. Is this known? Ubuntu14.04 + Dovecot-2.2.15. My doveconf -n: http://pastebin.com/25sURwJL Thanks! -- Thiago Henrique

1 0

Typo in systemd commit HG 8dc79a437858
by Thomas Leuxner 25 May '15

25 May '15

The apostrophes need to be removed from the LimitCORE example, otherwise the parameter will not be recognized: $ cat /etc/systemd/system/dovecot.service.d/service.conf [Service] #Environment='OPTIONS=-p' #LimitCORE=8192 LimitCORE=infinity

3 4

timeout for POP3 query.
by Christian Eichert 25 May '15

25 May '15

Is there a way to timeout POP3 query if they come to often? More precise I want to know if there is a setting in dovecot that makes it ignore pop3 requests from a certain user if they come more often then a certain amount of time. I am looking for a setting in dovecot, not a firewall solution. I would like dovecot to answer something like "requests come to often, please come back later." regards christian

2 1

Couldn't set transaction log view (seq 9..13)
by micah anderson 25 May '15

25 May '15

Hello, I'm using 2.2.13 on Debian stable, and I perform regular dsync backups. Typically if there is an error, dsync can recover from it the next time it is run, but I've been encountering a new error that doesn't seem to self-heal: # /usr/bin/dsync -u gae backup ssh -i /root/.ssh/id_rsa backmaildir(a)internal.example /usr/bin/dsync -u micah dsync-remote(micah): Error: /srv/maildirbackups/m/micah/daily.1/mailboxes/INBOX/dbox-Mails/dovecot.index: Couldn't set transaction log view (seq 9..13) dsync-remote(micah): Error: Failed to read transaction log for mailbox INBOX Re-running the dsync never fixes the issue. I'm happy to provide any additional information if so required to help track down this problem! micah

3 2

Controlling IP addresses for services
by Alex 24 May '15

24 May '15

Hi, I'm using dovecot-2.2.15 on fedora21 and would like to configure pop3s and imaps to only listen on localhost and internal addresses. It seems the listen= parameter only supports ports, not IP addresses. Is it possible to control which IPs the services listen on? I'm also interested in knowing the differences between pop3-login and just the pop3 service? Same with imap-login and imap? I've searched the wiki and still a bit confused. Thanks, Alex

5 5

Problem with sieve not triggering randomly?
by Chris Adams 23 May '15

23 May '15

I'm running CentOS 7.1 with Dovecot 2.2.10 (CentOS packaged version). I have Postfix feeding messages to Dovecot for local delivery via LMTP, and I have Amavisd for spam filtering. For messages above a certain threshold, Amavisd adds the "X-Spam-Flag: YES" header, and I file that into the Spam folder using a default (system-wide) sieve script (there aren't any per-user sieve scripts set up): require "fileinto"; if header :contains "X-Spam-Flag" "YES" { fileinto "Spam"; } I can see it work on my test messages and from lmtp log entries. However, it doesn't seem to always work. I had a user complain about a spam increase, and I looked in their mailbox. I see a message with the "X-Spam-Flag: YES" header, but it is in the INBOX (and the corresponding lmtp log entry shows that's where it went). Why would the sieve script work on some messages and not others? I don't see any errors in the log. I see a bunch of messages from the same source to different users, and they were all filed into INBOX, not Spam. Looking at the message in question, it is a pretty bogus message. There are multiple From: and Subject: headers. Would that cause sieve to "punt" on the message (but not log anything about it)? -- Chris Adams <cma(a)cmadams.net>

3 11

Dovecot-Director, (Manage)-Sieve und Remote-IP
by Benjamin Hück 23 May '15

23 May '15

Hello, I`ve got a question about Dovecot-Director and (Manage)-Sieve: is there any possibility to pass-through the original IP-address to the backend server? In this case I try to pass-through the IP-address of a webmail server. I`ve looked for a solution in different forums and tried it with the parameter "login_trusted_networks", however no success. The above solution is working with IMAP/POP3/LMTP, but not with Sieve. For any solutions or any hint I would be grateful. Best regards Benjamin Hück -- ________________________________ ________________________________ KEVAG Telekom GmbH Cusanusstr. 7 D-56073 Koblenz Fon: +49 261 20162-0 Fax: +49 261 20162-25100 http://www.kevag-telekom.de/ Geschäftsführer: Bernd Gowitzke, Gerd Thewalt Sitz der Gesellschaft: Koblenz, Amtsgericht Koblenz, HRB Nr. 5343 USt.IdNr. DE 18 77 67 843 St-Nr. 22/650/0182/7

2 2

Re: charset_to_utf8 assertion of remaining src_size
by Cassidy Larson 23 May '15

23 May '15

We're using FreeBSD 10.1 Thanks On Thu, May 21, 2015 at 4:56 PM, Xin Li <delphij(a)delphij.net> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA512 > > On 05/21/15 15:47, Cassidy Larson wrote: > > I've been seeing this same error as well now: > > > > Fatal: master: service(indexer-worker): child 20979 killed with > > signal 6 (core not dumped - set service indexer-worker { > > drop_priv_before_exec=yes }) Panic: file charset-iconv.c: line 132 > > (charset_to_utf8): assertion failed: (*src_size - pos <= > > CHARSET_MAX_PENDING_BUF_SIZE) > > Quick question -- Are you using FreeBSD (10.0+)? > > Cheers, > - -- > Xin LI <delphij(a)delphij.net> https://www.delphij.net/ > FreeBSD - The Power to Serve! Live free or die > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.1.4 (FreeBSD) > > iQIcBAEBCgAGBQJVXmKfAAoJEJW2GBstM+nspmoP/0CKS0g8ka/4uPF+jaq7+DD6 > 1PxCufdz/p528rclbXvEK3XE++sULihNVtO24TgXMOIJZB6jCfbfo+O17N9ZS7g9 > Vaz0r0URU28joAeDX/NR1yzYpHdo277RhXiPlKuyep+fEgi6Szm/mNaR+aCtYrge > 8Qm2U2eaHFQk/2qpyvC4ZlFzXSVIR+AIMSh87YqJSWSVd3PjNDLxZLDeUaQyygG5 > 1lW3lsy0yDOTISI58rXavOi7qa4qKo0ySDOMLct3GrdXzL5S8N/Pc3RnRTP5p9dY > 22cGoH3XloijWAef93qHSuPFuC9Yiko4g/FZAtfuQg6mCETvhPDfhXBgRf3IFYAr > vuMOyBX+3TrQQI+zz3aolou10WH+E+PPbJFFZcNq4sRGQYtSXBA4RmDDKU4NgwoB > gIzS43GjPidJTxdzEC+eedmS6Rt5wvyFaDK1h5+x/mgnfEie6E9Hfk8IBqRHZMUW > HixCmBnC3p1GN+R8rbPxjuycP06bB7YXLJ28o06gM2agrGv5vu83j+WqO2g6wJIP > hRKnyCVVPUeAnkLpS+7nXZwW5R/j8M5y7V8rbiYCX4q+zWCJZl/ac1G12zwva5k1 > MwyjciDP951soMM2RYsQQSE5RxRKMC03kqGt+qnBx3jBR7afzhOmcO9gcKQJEY5R > qjwnZ0voZtV7u2Ptcv1Q > =hWt9 > -----END PGP SIGNATURE----- >

3 2

RE: v2.2.18 released
by dovecot＠outputservices.com 22 May '15

22 May '15

On 05/22/15 12:24, James wrote: > On 22/05/2015 16:27, dovecot(a)outputservices.com wrote: >> I am just starting out and trying to get dovecot and postfix working in Solaris 10 environment. >> >> Went from 2.2.15 to 2.2.17, then to 2.2.18 >> >> Both version 2.2.17 & 2.2.18 gave this same error. 2.2.15 does not. >> >> ----------------------------------- >> May 15 09:27:37 master: Info: Dovecot v2.2.18 starting up for imap >> May 15 09:27:37 ssl-params: Info: Generating SSL parameters >> May 15 09:27:37 ssl-params: Fatal: Couldn't load required plugin /tmp/tocevod/lib/dovecot/libssl_iostream_openssl.so: dlopen() failed: ld.so.1: ssl-params: fatal: relocation error: file /tmp/tocevod/lib/dovecot/libssl_iostream_openssl.so: symbol SSL_clear_options: referenced symbol not found > > > I suspect you have compiled with one SSL library and are running with another. > > Hints: > > 1. Check RPATH in libs: > $ dump -Lv /tmp/tocevod/lib/dovecot/libssl_iostream_openssl.so > > 2. unset LD_LIBRARY_PATH > > 3. Check which ssl libs are being used: > $ ldd /tmp/tocevod/lib/dovecot/libssl_iostream_openssl.so Yep, that is it. It found some old ssl libraries. I will go back and look at the compile command better. > > 4. and symbol check: > $ ldd -r /tmp/tocevod/lib/dovecot/libssl_iostream_openssl.so > > > > I assume your use of /tmp is temporary. Set prefix to, eg, /opt/tocevod. > > > > James. Thanks

1 0

RE: v2.2.18 released
by dovecot＠outputservices.com 22 May '15

22 May '15

I am just starting out and trying to get dovecot and postfix working in Solaris 10 environment. Went from 2.2.15 to 2.2.17, then to 2.2.18 Both version 2.2.17 & 2.2.18 gave this same error. 2.2.15 does not. ----------------------------------- May 15 09:27:37 master: Info: Dovecot v2.2.18 starting up for imap May 15 09:27:37 ssl-params: Info: Generating SSL parameters May 15 09:27:37 ssl-params: Fatal: Couldn't load required plugin /tmp/tocevod/lib/dovecot/libssl_iostream_openssl.so: dlopen() failed: ld.so.1: ssl-params: fatal: relocation error: file /tmp/tocevod/lib/dovecot/libssl_iostream_openssl.so: symbol SSL_clear_options: referenced symbol not found May 15 09:27:37 ssl-params: Error: child process failed with status 22784 May 15 09:27:46 master: Warning: Killed with signal 15 (by pid=1848 uid=0 code=kill) ------------------------------------------------ doveconf -n # 2.2.18: /tmp/tocevod/etc/dovecot/dovecot.conf # OS: SunOS 5.10 i86pc log_path = /tmp/tocevod/log/log login_trusted_networks = 137.106.0.0/16 mail_location = mbox:~/posta:INBOX=/var/mail/%u namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { args = /dovecot/etc/dovecot/conf.d/ldap.settings driver = ldap } protocols = imap service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 } } ssl_cert = </dovecot/certs/dovecot.pem ssl_key = </dovecot/certs/dovecot.key ssl_prefer_server_ciphers = yes ssl_protocols = !SSLv2 !SSLv3 userdb { args = /dovecot/etc/dovecot/conf.d/ldap.settings driver = ldap }

2 1

Couldn't create lock .dovecot-sync.lock
by listas＠adminlinux.com.br 22 May '15

22 May '15

Hi, In a cluster with two servers and replication via dovecot-dsync, this error is logged: server1 dovecot: dsync-server(<user>): Error: Couldn't create lock /var/lib/imap/user/6a/<user>/.dovecot-sync.lock: No such file or directory This is because "/var/lib/imap/user/6a/<user>/" doesn't exist in server1. In another cluster node, the directory exists and everything seems to work fine. In my view, this indicates that the first sync is failing. In the first user access Dovecot creates home_dir for him. But the sync is not happening at this time to create the home_dir on the other node. My confs with doveconf -n: http://www.adminlinux.com.br/newcluster_doveconf.txt Thanks in advance! -- Thiago Henrique

2 2

Problems To Get Dovecot Running On FreeBSD: auth process crashes
by Christian Felsing 22 May '15

22 May '15

Hello, I ran into problems to get Dovecot running on FreeBSD. Steps for reproduction. Start Docot with dovecot -F (same result if started by rc script) telnet 192.168.116.38 110 Trying 192.168.116.38... Connected to freebsd. Escape character is '^]'. -ERR Disconnected: Auth process broken Connection closed by foreign host. logfile shows following: May 22 11:41:24 freebsd dovecot: master: Dovecot v2.2.18 starting up for imap, pop3, lmtp, sieve May 22 11:41:27 freebsd dovecot: auth: Error: auth: environment corrupt; missing value for DOVECOT_ May 22 11:41:27 freebsd dovecot: auth: Fatal: unsetenv(RESTRICT_SETUID) failed: Bad address May 22 11:41:27 freebsd dovecot: master: Error: service(auth): command startup failed, throttling for 2 secs May 22 11:41:27 freebsd dovecot: pop3-login: Disconnected: Auth process broken (disconnected before auth was ready, waited 1 secs): user=<>, rip=192.168.116.1, lip=192.168.116.38, session=<cBLNdqgWWADAqHQB> May 22 11:41:32 freebsd dovecot: master: Warning: Killed with signal 2 (by pid=0 uid=0 code=kernel) Error message is quite meaningless regarding reason for crash. I am running same config on a Linux (Debian 8) host w/o problems. Is it a problem specific to FreeBSD? Christian ---cut here--- [root@freebsd /usr/local/etc/dovecot]# doveconf -n # 2.2.18: /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 0.4.8 (0c4ae064f307+) # OS: FreeBSD 10.1-RELEASE-p10 amd64 auth_debug = yes auth_debug_passwords = yes auth_master_user_separator = * auth_mechanisms = plain login auth_ssl_username_from_cert = yes auth_username_chars = "abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@#" auth_username_translation = "@#" auth_verbose = yes base_dir = /var/run/dovecot/ disable_plaintext_auth = no first_valid_uid = 124 hostname = mail.taunusstein.net last_valid_uid = 124 lda_mailbox_autocreate = yes listen = 192.168.116.38 log_timestamp = %Y-%m-%d %H:%M:%S login_greeting = mail.taunusstein.net imap4/pop3 ready. mail_gid = 124 mail_location = maildir:~/Maildir mail_privileged_group = vmail mail_uid = 124 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 imapflags notify namespace { list = children location = maildir:%%h/Maildir:INDEX=~/Maildir/shared/%%u prefix = shared/%%u/ separator = / subscriptions = no type = shared } namespace inbox { inbox = yes list = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = separator = / type = private } passdb { args = /usr/local/etc/dovecot/passwd.masterusers driver = passwd-file master = yes } passdb { driver = pam } plugin { acl = vfile:/etc/dovecot/global-acls:cache_secs=300 acl_shared_dict = file:/var/lib/dovecot/shared-mailboxes autocreate = Trash autocreate2 = Drafts autosubscribe = Trash autosubscribe2 = Drafts fts = solr fts_solr = break-imap-search url=http://solr.lan:8983/solr/ quota = maildir:User quota quota_rule = *:storage=500M quota_rule2 = Trash:storage=+100M quota_warning = storage=95%% quota-warning 95 %u quota_warning2 = storage=80%% quota-warning 80 %u recipient_delimiter = + sieve = ~/.dovecot.sieve sieve_dir = ~/sieve sieve_extensions = +notify +imapflags } postmaster_address = postmaster(a)taunusstein.net protocols = imap pop3 lmtp sieve sendmail_path = /usr/lib/sendmail service anvil { client_limit = 4000 } service auth-worker { group = vmail } service auth { client_limit = 8000 unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-master { group = vmail mode = 0660 user = vmail } unix_listener auth-userdb { group = postfix mode = 0666 user = postfix } user = root } service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } process_limit = 1024 } service imap-postlogin { executable = script-login /opt/dovecot-cf/bin/lastlogin.py } service imap { executable = imap imap-postlogin } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0660 user = postfix } } service managesieve-login { inet_listener sieve { port = 4190 } inet_listener sieve_deprecated { port = 2000 } } service pop3-login { inet_listener pop3 { port = 110 } inet_listener pop3s { port = 995 ssl = yes } process_limit = 1024 } service pop3-postlogin { executable = script-login /opt/dovecot-cf/bin/lastlogin.py } service pop3 { executable = pop3 pop3-postlogin } service quota-warning { user = vmail } ssl_cert = </usr/local/etc/dovecot/ssl/taunusstein.net.pem ssl_cipher_list = kEECDH:kEDH:AESGCM:ALL:+3DES:!RC4:!LOW:!EXP:!MD5:!aNULL:!eNULL ssl_dh_parameters_length = 4096 ssl_key = </usr/local/etc/dovecot/ssl/taunusstein.net.key ssl_parameters_regenerate = 1 hours ssl_prefer_server_ciphers = yes ssl_protocols = !SSLv2 !SSLv3 TLSv1 TLSv1.1 TLSv1.2 ssl_require_crl = no userdb { args = /usr/local/etc/dovecot/dovecot-samba4.conf driver = ldap } protocol lda { auth_socket_path = /var/run/dovecot/auth-master mail_plugins = " sieve acl" } protocol imap { imap_client_workarounds = tb-extra-mailbox-sep mail_max_userip_connections = 20 mail_plugins = quota imap_quota acl imap_acl fts fts_solr } protocol lmtp { mail_plugins = quota sieve } protocol sieve { managesieve_logout_format = bytes ( in=%i : out=%o ) } protocol pop3 { mail_plugins = quota pop3_uidl_format = %08Xu%08Xv } ---cut here---

2 1

race condition? -> Error: dict quota: Quota update failed, it's now desynced
by Steffen Kaiser 22 May '15

22 May '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I get this error now and then, but only for users, that share or use shared mailboxes. See this snippet: 2015-05-22 02:27:09 IMAP(<uid1>) [28776]: Info: Disconnected: Logged out in=21450 out=76933 2015-05-22 02:27:09 IMAP(<uid1>) [28774]: Info: Disconnected: Logged out in=3769 out=16379 2015-05-22 02:27:09 IMAP(<uid1>) [28770]: Info: Disconnected: Logged out in=641 out=394985 2015-05-22 02:27:09 IMAP(<uid1>) [28614]: Info: Disconnected: Logged out in=510 out=2178 2015-05-22 02:27:09 IMAP(<uid1>) [28768]: Info: expunge: box=users.<OTHER-UID>.INBOX, uid=8711, msgid=<008801d093ef$f46c00d0$dd440270$(a)example.com>, size=17433, vsize=17849, from=[cut] 2015-05-22 02:27:09 IMAP(<OTHER-UID>) [28830]: Info: Disconnected: Logged out in=555 out=2763 2015-05-22 02:27:09 IMAP(<uid1>) [28768]: Info: Disconnected: Logged out in=628 out=2851717 2015-05-22 02:27:09 IMAP(<uid1>) [28768]: Error: dict quota: Quota update failed, it's now desynced 2015-05-22 02:27:09 IMAP(<OTHER-UID>) [28827]: Info: Disconnected: Logged out in=267 out=1256 2015-05-22 02:27:09 IMAP(<OTHER-UID>) [28824]: Info: Disconnected: Logged out in=175 out=1073 2015-05-22 02:27:09 IMAP(<OTHER-UID>) [28831]: Info: Connection closed in=550 out=3197 2015-05-22 02:27:09 IMAP(<OTHER-UID>) [28663]: Info: expunge: box=INBOX, uid=8711, msgid=<008801d093ef$f46c00d0$dd440270$(a)example.com>, size=17433, vsize=17849, from=[cut] 2015-05-22 02:27:09 IMAP(<OTHER-UID>) [28663]: Info: Disconnected: Logged out in=800 out=25925 OTHER-UID shares the INBOX to uid1. Now, the _same_ message is about to delete once via the "sharing" uid and once from the consumer at the same time. My quota backend is Postgres, via quota = pgsql:/usr/local/dovecot-2.2.15/etc/dovecot/dovecot-dict-sql.conf.ext on Dovecot v2.2 hg 18272:466596200825 . I tried to replicate the error, by setting up two accounts, A shares INBOX to B, setup A and B in the same Thunderbird, configured that both A and B expunge the INBOX on termination of MUA, but I cannot reproduce that the same message is deleted twice in parallel. I also tried current hg's tip 8737:8906101589f9, but I cannot reproduce the error, no matter what I try. Also, I think, that in this very case the quota is OK still, because it had been updated for the sharing user OTHER-UID. - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEVAwUBVV7xKHz1H7kL/d9rAQIlWAf+M0KHX2IjJufhamNlnlWJRhbGO+qmwnlh A6644yzn8vEtx3zHvOfvULAEZyWPsHlmMnu2YNKa3JrUYXte2zl1M7AzLR0Wsl9k xcBGxsbeRhqkDOrDoNRXMAZaTzWdqHDvXDGBujsh7+whjDh+Uv9uD0/LYxuRo+lb r54QF9qgSv4NLB4DlWhPMcwWjBWmTRu5kJGpU05jwlCgroZxkvB59FXaccMQXe5r ay9YWhBLz1qVVRg7ZsnY6ogwmlM/MyreI0o8A6iPfgDmrOcHjYbQ7jLGb7771vHJ SUjyC5NsU/A9HWr3jI2gmi2kSMIvPKOxHtUKpschLqBprbUkj0tNyg== =0bWX -----END PGP SIGNATURE-----

1 0

sieve permission problem with dovecot.svbin
by Cliff Hayes 22 May '15

22 May '15

Hello list, I am starting to see these in maillog: dovecot: lmtp(31949, dwright): Error: kXK3KnTpXFXNfAAAU+Cu/Q: sieve: binary open: failed to open: open(/var/spool/mail/dwright/.dovecot.svbin) failed: Permission denied (euid=520(dwright) egid=12(mail) missing +r perm: /var/spool/mail/dwright/.dovecot.svbin, euid is not dir owner) But the directory /var/spool/mail/dwright is owned by dwright:mail with permission set to 700. How do I fix? Here is my config: # 2.0.9: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-431.29.2.el6.x86_64 x86_64 Scientific Linux release 6.5 (Carbon) auth_failure_delay = 5 secs auth_username_format = %Ln auth_verbose_passwords = plain mail_access_groups = mail mail_location = maildir:~/Maildir mail_plugins = " quota" 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 mbox_write_locks = fcntl passdb { driver = pam } plugin { quota = maildir:User quota quota_rule = *:storage=1G quota_rule2 = Trash:storage=+100M sieve = ~/.dovecot.sieve sieve_after = /dovecotSieveAfter/ sieve_dir = ~/sieve } protocols = imap lmtp sieve service managesieve-login { inet_listener sieve { port = 4190 } } ssl_ca = </etc/pki/dovecot/certs/intermediate20150202.crt ssl_cert = </etc/pki/dovecot/certs/avalon20150202.crt ssl_key = </etc/pki/dovecot/private/avalon20150129.key ssl_verify_client_cert = yes userdb { args = /etc/dovecot/passwd driver = passwd-file } protocol lmtp { log_path = /var/log/dovecot-lmtp.log mail_plugins = " quota sieve" } protocol lda { log_path = /var/log/dovecot-lda.log mail_plugins = " quota sieve" } protocol imap { mail_plugins = " quota imap_quota" }

2 1

dovecot 2.2.18 and ssl_parameters_regenerate
by django＠nausch.org 22 May '15

22 May '15

HI Timo, On http://wiki2.dovecot.org/SSL/DovecotConfiguration I read in chapter SSL security settings: When Dovecot starts up for the first time, it generates new 512bit and 1024bit Diffie Hellman parameters and saves them into <prefix>/var/lib/dovecot/ssl-parameters.dat. After the initial creation they're by default regenerated every week. With newer computers the generation shouldn't take more than a few seconds, but with older computers it can take as long as half an hour. The extra security gained by the regeneration is quite small, so with slower computers, for Dovecot versions prior to v2.2, you might want to disable it If I discover the default-value of ssl_parameters_regenerate I receive: # doveconf -d ssl_parameters_regenerate ssl_parameters_regenerate = 0 In your doku you wrote, that dovecot will regenerate every week. :/ ? I set it to "1 hours" and watch if /var/lib/dovecot/ssl-parameters.dat is build every hour, but nothing happens. ssl-parameters.dat is only rebuild, if I change ssl_dh_parameters_length What's the problem? What I've made false? ttyl Django -- http://dokuwiki.nausch.org http://wetterstation-pliening.info http://ebersberger-liedersammlung.de

1 0

charset_to_utf8 assertion of remaining src_size
by Xin Li 22 May '15

22 May '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hi, I have seen the following assertion fails on my own mail server (indexer-worker): Panic: file charset-iconv.c: line 132 (charset_to_utf8): assertion failed: (*src_size - pos <= CHARSET_MAX_PENDING_BUF_SIZE) However, when charset_to_utf8_try returns FALSE (e.g. iconv() got EINVAL or EILSEQ), the for loop in charset_to_utf8 may end earlier, and there may be additional pending characters, and the assertion doesn't seem always hold in the error case, perhaps we should assert that pos is non-zero in the error case? Cheers, - -- Xin LI <delphij(a)delphij.net> https://www.delphij.net/ FreeBSD - The Power to Serve! Live free or die -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.1.2 (FreeBSD) iQIcBAEBCgAGBQJVVjO/AAoJEJW2GBstM+nsbKUP/29fYdZArCiUSStK0hCtRvC3 o4L35zq4iP4WUry7VqNtdMg2Uiythei9l0JokNOJAy2ZDktJ3ns9CArXHi/pJE7/ V8374Iu9ygb4tzDvcNY/353SFkN+Sw4pJzSGJTelVT8nHxahQMtN7E0u26l54zNx p1H8rgt2nVA8eRvKL9MrhudN3eSI2+Jq4HX+dR4/Tu4qLkSU1nqi8sopQxNXzW4C 4XG4haSbTtXLu0H1MGa8y5pmwrFmZEluNOBm2SOww+UqeteD/MwE/pgA7g+cQx8l /t3FWzSe4C9HROV1VGW5V5HDM7cDvNJZ+nxQGI6L6qInkCBqQx/muIb9nIe7dhro tiHIuX4h8X2zaga+iD+B9fkf4QpDUc11WYE+0DUArb2cNTTAgeTXQ68+g0Q+UC8s OxUVDA4KwOSzkpEifDgvVCdgPG7U87SGe9NlMGjSZvAIEPsww16A3f2IaM4fhFa2 lVuTh1wq8phdWXLbCbZ0F36hAyxVbbwC5Xyj4Ygy3QL4RiBC7CJJ8I4f1lRLnoFz 1Wg0/M7psXBLVN7vx2MKtK5Rj1OvMOKmL4VpkhKcnp2z/Y9I5Qq2CP4C5uOv3DLJ JjoCsnVDpWJKQo6EPleb9OxVJF+NmjHd63zimXbuUyDJ7AJCsx/0m9mJZ5QYf+jU U3OqESCU5e5q++QLd2Kl =ksoA -----END PGP SIGNATURE-----

3 4

"doveadm backup" doesn't work anymore after upgrading to 2.2.18
by Jesus Cea 21 May '15

21 May '15

Until today I could do this to backup my primary IMAP4 server: """ doveadm backup ssh csi doveadm dsync-server """ It doesn't work anymore after upgrading to Dovecot 2.2.18: """ jcea@ubuntu:~$ doveadm backup ssh csi doveadm dsync-server Enter passphrase for key '/home/jcea/.ssh/id_rsa': dsync-remote(root): Error: Mailbox INBOX: Failed to get attribute vendor/vendor.dovecot/pvt/server/sieve/default: Mailbox attributes not enabled dsync-local(jcea): Error: Remote command returned error 65: ssh csi doveadm dsync-server dsync-server """ The first error is regular business: I don't have SIEVE in the backup, since it is a backup. I have seen this error forever, no consequences. Now in 2.2.18 I get the second error and the backup is aborted. It doesn't work anymore. I don't find any reference to error 65 anywhere. -- Jesús Cea Avión _/_/ _/_/_/ _/_/_/ jcea(a)jcea.es - http://www.jcea.es/ _/_/ _/_/ _/_/ _/_/ _/_/ Twitter: @jcea _/_/ _/_/ _/_/_/_/_/ jabber / xmpp:jcea@jabber.org _/_/ _/_/ _/_/ _/_/ _/_/ "Things are not so easy" _/_/ _/_/ _/_/ _/_/ _/_/ _/_/ "My name is Dump, Core Dump" _/_/_/ _/_/_/ _/_/ _/_/ "El amor es poner tu felicidad en la felicidad de otro" - Leibniz

2 2

Log mail access
by Philipp Brüll 20 May '15

20 May '15

Hello, is it somehow possible to log the access to a mail? The log entry should be written, if a user fetches a mail via imap or pop3. It would be convenient for debugging. I've checked the Logging-Wiki and the docs for the mail_log plugin, but they seem to log any event but "mail access". Best regards, Philipp

1 0

what's the different between the processes dovecot-auth and dovecot -w
by 刘莹莹 20 May '15

20 May '15

hi： what's the different between the processes dovecot-auth and dovecot -w ? What's the function on each of them ? thanks

1 0

Re: Can't achieve alias working with SQL
by Samuel 19 May '15

19 May '15

Le 19/05/2015 14:54, Jorge Bastos a écrit : > Hi Samuel, > >> On a fresh install of Jessie, I achieve to make dovecot/postfix working >> with SQL, but I still can't send email to alias for wich one I get : >> "Unknown user" >> >> After debug enable in dovecot, I see that the user_query SQL , just >> query for the "users" table and not the "forward" table so the final >> alias user is not known. >> >> But when I check postfix for alias, it seems ok : >> >> root@cluster-dovecot:/etc/dovecot# postmap -q contact2(a)XXXXXXXX.com >> mysql:alias_maps contact(a)XXXXXXXXXX.com >> >> So what do I missed for alias working with dovecot ? >> > I had similar question on how to make it working, and it ended up being: > > virtual_alias_maps = mysql:/etc/postfix/mysql-virtual-alias-maps.cf I have found : In fact, it was not dovecot but postfix policy fault because of check_policy_service making alias down. I'm digging on it now. Thanks. Samuel.

1 0

Re: Controlling shared folder rename?
by andy＠thecsillags.com 19 May '15

19 May '15

Eventually I figured out a solution that looks like it should work; postlogin scripting described here http://wiki2.dovecot.org/PostLoginScripting . Specifically, the sample at the bottom that adds a shared folder, obviously will need some work to make it work the way I want, but it should work. May 19 2015 3:18 PM, andy(a)thecsillags.com (mailto:andy@thecsillags.com) wrote: Dovecot version 2.2.16 I'm using shared folders and what I'd like to do is either have the folder that gets shared be able to be renamed by the user, or failing that, to be able to have an administrator define how the shared folder shows up to the account it's shared to. For example, right now, the INBOX owned by testuser(a)mydomain.com (mailto:testuser@mydomain.com) is shared to otheruser@mydomain as shows up as shared/testuser(a)mydomain.com (mailto:testuser@mydomain.com) because of the prefix directive in the shared namespace in 10-mail.conf. It would be nice if, either via a dict (like the way the acls work), or via normal IMAP folder commands, that I control how it shows up to otheruser@mydomain. So if I could do something like: prefix = proxy::sharedname or similar. Currently trying to rename from IMAP fails -- given the way my understanding of how things works is, I'm not surprised, but hey, it was worth a shot right? First, does the question make sense? Two, is there a way to do this? Thanks, :Drew

1 0

Re: Can't achieve alias working with SQL
by Samuel 19 May '15

19 May '15

Le 19/05/2015 14:54, Jorge Bastos a écrit : > Hi Samuel, > >> On a fresh install of Jessie, I achieve to make dovecot/postfix working >> with SQL, but I still can't send email to alias for wich one I get : >> "Unknown user" >> >> After debug enable in dovecot, I see that the user_query SQL , just >> query for the "users" table and not the "forward" table so the final >> alias user is not known. >> >> But when I check postfix for alias, it seems ok : >> >> root@cluster-dovecot:/etc/dovecot# postmap -q contact2(a)XXXXXXXX.com >> mysql:alias_maps contact(a)XXXXXXXXXX.com >> >> So what do I missed for alias working with dovecot ? >> > I had similar question on how to make it working, and it ended up being: > > virtual_alias_maps = mysql:/etc/postfix/mysql-virtual-alias-maps.cf In fact, this part is yet in my main.conf and is working (see my postmap query above). And I don't understand why dovecot doesn't use it. So I revert back my dirty user_query and I'm still searching why I can't send email to alias .... Thanks. Samuel.

1 0

Understanding the "doveadm replicator status" output
by Listas＠Adminlinux 19 May '15

19 May '15

Where can I get more detailed information about the output of the 'doveadm replicator status' ? man doveadm-replicator isn't enough. For example, Total number of known users = 29409, but the server has only 17667 users. This is confusing. Look: # doveadm user '*' |wc -l 17667 # doveadm replicator status Queued 'sync' requests 0 Queued 'high' requests 0 Queued 'low' requests 0 Queued 'failed' requests 0 Queued 'full resync' requests 12962 Waiting 'failed' requests 16447 Total number of known users 29409 What it means to "Queued full resync requests" ? thanks! Thiago Henrique

1 0

Re: Can't achieve alias working with SQL
by Samuel 19 May '15

19 May '15

Hi, Le 19/05/2015 14:54, Jorge Bastos a écrit : > Hi Samuel, > >> On a fresh install of Jessie, I achieve to make dovecot/postfix working >> with SQL, but I still can't send email to alias for wich one I get : >> "Unknown user" >> >> After debug enable in dovecot, I see that the user_query SQL , just >> query for the "users" table and not the "forward" table so the final >> alias user is not known. >> >> But when I check postfix for alias, it seems ok : >> >> root@cluster-dovecot:/etc/dovecot# postmap -q contact2(a)XXXXXXXX.com >> mysql:alias_maps contact(a)XXXXXXXXXX.com >> >> So what do I missed for alias working with dovecot ? >> > I had similar question on how to make it working, and it ended up being: > > virtual_alias_maps = mysql:/etc/postfix/mysql-virtual-alias-maps.cf Finally I achieved making alias to work by changing the user_query: #FROM users WHERE username = '%n' AND domain = '%d' TO : FROM users WHERE username = '%n' AND domain = '%d' or email=(select destination from forwards where source='%u'); But I don't know if that's the right way. Wanting for any suggestion .... Samuel.

1 1

Can't achieve alias working with SQL
by Samuel 19 May '15

19 May '15

Hello, On a fresh install of Jessie, I achieve to make dovecot/postfix working with SQL, but I still can't send email to alias for wich one I get : "Unknown user" After debug enable in dovecot, I see that the user_query SQL , just query for the "users" table and not the "forward" table so the final alias user is not known. But when I check postfix for alias, it seems ok : root@cluster-dovecot:/etc/dovecot# postmap -q contact2(a)XXXXXXXX.com mysql:alias_maps contact(a)XXXXXXXXXX.com So what do I missed for alias working with dovecot ? Do I need a special conf in master.conf for sending alias AND final recipient or do I have to change the dovecot user_query for taking in acount the "forward" table in the SQL query ? .... or other thing I could miss ... Thanks a lot ... Samuel. DOVECOT : root@cluster-dovecot:/etc/dovecot# dovecot --version 2.2.13 root@cluster-dovecot:/etc/dovecot# dovecot -n # 2.2.13: /etc/dovecot/dovecot.conf # OS: Linux 3.16.0-4-amd64 x86_64 Debian 8.0 auth_debug_passwords = yes auth_mechanisms = plain login dict { quota = mysql:/etc/dovecot/dovecot-dict-sql-user.conf quota_domain = mysql:/etc/dovecot/dovecot-dict-sql-domain.conf } lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes mail_debug = yes mail_location = mbox:~/mail:INBOX=/var/mail/%u mail_plugins = quota fts fts_solr acl zlib mail_log notify managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } plugin { quota = dict:user::proxy::quota quota2 = dict:domain:%d:proxy::quota_domain quota_grace = 1M quota_warning = storage=100%% quota-warning 100 %u quota_warning2 = storage=95%% quota-warning 95 %u quota_warning3 = storage=80%% quota-warning 80 %u quota_warning4 = -storage=100%% quota-warning below %u sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } protocols = imap pop3 sieve lmtp service auth { unix_listener /var/spool/postfix/private/auth { group = mail mode = 0660 user = postfix } unix_listener auth-master { mode = 0660 user = vmail } unix_listener auth-userdb { mode = 0660 user = vmail } } service dict { unix_listener dict { mode = 0666 user = dovecot } } service imap-login { inet_listener imap { address = * port = 143 } inet_listener imaps { address = * port = 993 } process_limit = 256 } service managesieve-login { inet_listener sieve { port = 4190 } } service managesieve { process_limit = 1024 } service quota-status { executable = quota-status -p postfix inet_listener { port = 12340 } } service quota-warning { executable = script /usr/local/bin/quota-warning.sh unix_listener quota-warning { mode = 0666 user = vmail } user = vmail } ssl_cert = </etc/dovecot/dovecot.pem ssl_key = </etc/dovecot/private/dovecot.pem userdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } protocol lmtp { mail_plugins = " sieve" } protocol lda { mail_plugins = " quota sieve" } protocol imap { mail_plugins = " quota imap_quota" } POSTFIX : alias_database = hash:/etc/aliases alias_maps = hash:/etc/aliases alias_maps_dbname = $mysql_dbname alias_maps_hosts = $mysql_host alias_maps_password = $mysql_passwd alias_maps_select_field = destination alias_maps_table = forwards alias_maps_user = $mysql_user alias_maps_where_field = source append_dot_mydomain = no biff = no bounce_queue_lifetime = 1d broken_sasl_auth_clients = yes config_directory = /etc/postfix dovecot_destination_concurrency_limit = 1 dovecot_destination_recipient_limit = 1 gid_maps_dbname = $mysql_dbname gid_maps_hosts = $mysql_host gid_maps_password = $mysql_passwd gid_maps_select_field = gid gid_maps_table = users gid_maps_user = $mysql_user gid_maps_where_field = concat(username,'@',domain) inet_interfaces = all mailbox_command = procmail -a "$EXTENSION" mailbox_domains_dbname = $mysql_dbname mailbox_domains_hosts = $mysql_host mailbox_domains_password = $mysql_passwd mailbox_domains_select_field = domain mailbox_domains_table = domains mailbox_domains_user = $mysql_user mailbox_domains_where_field = domain mailbox_maps_dbname = $mysql_dbname mailbox_maps_hosts = $mysql_host mailbox_maps_password = $mysql_passwd mailbox_maps_select_field = home mailbox_maps_table = users mailbox_maps_user = $mysql_user mailbox_maps_where_field = concat(username,'@',domain) mailbox_size_limit = 0 maximal_queue_lifetime = 1d mydestination = cluster-dovecot.ingescom.com, localhost.ingescom.com, , localhost myhostname = cluster-dovecot.ingescom.com mynetworks = 127.0.0.0/8 [::ffff:127.0.0.0]/104 [::1]/128 myorigin = /etc/mailname mysql_dbname = mail mysql_host = 10.40.30.1 mysql_passwd = mail_admin mysql_user = mail_admin readme_directory = no recipient_delimiter = + relayhost = smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache smtpd_banner = $myhostname ESMTP $mail_name (Debian/GNU) smtpd_delay_reject = yes smtpd_recipient_restrictions = check_policy_service inet:127.0.0.1:12340 smtpd_relay_restrictions = permit_mynetworks permit_sasl_authenticated defer_unauth_destination reject smtpd_sasl_auth_enable = yes smtpd_sasl_local_domain = $mydomain smtpd_sasl_security_options = noanonymous smtpd_tls_cert_file = /etc/ssl/certs/ssl-cert-snakeoil.pem smtpd_tls_key_file = /etc/ssl/private/ssl-cert-snakeoil.key smtpd_tls_session_cache_database = btree:${data_directory}/smtpd_scache smtpd_use_tls = yes uid_maps_dbname = $mysql_dbname uid_maps_hosts = $mysql_host uid_maps_password = $mysql_passwd uid_maps_select_field = uid uid_maps_table = users uid_maps_user = $mysql_user uid_maps_where_field = concat(username,'@',domain) virtual_alias_maps = mysql:alias_maps virtual_gid_maps = mysql:gid_maps virtual_mailbox_base = / virtual_mailbox_domains = mysql:mailbox_domains virtual_mailbox_limit = 1024000000 virtual_mailbox_maps = mysql:mailbox_maps virtual_minimum_uid = 2000 virtual_transport = dovecot virtual_uid_maps = mysql:uid_maps master.conf : (I tried several conf) dovecot unix - n n - - pipe flags=DRhu user=vmail:vmail argv=/usr/bin/sudo /usr/lib/dovecot/deliver -d ${recipient} -a ${original_recipient} #flags=DRhu user=vmail: argv=/usr/bin/sudo /usr/lib/dovecot/deliver -f ${sender} -d ${user}@${nexthop} -a ${recipient} #flags=DRhu user=vmail: argv=/usr/bin/sudo /usr/lib/dovecot/deliver -f ${sender} -d ${user}@${nexthop} -a ${original_recipient} #flags=DRhu user=vmail:vmail argv=/usr/bin/sudo /usr/lib/dovecot/deliver -f ${sender} -d ${recipient} -a ${original_recipient}

1 0

doveadm index panic
by Nick Rosier 19 May '15

19 May '15

Hi, running dovecot 2.2.18. when I try to re-index my INBOX I get following error: # doveadm index -u user(a)domain.com INBOX doveadm(user(a)domain.com): Warning: I/O leak: 0x80101ada0 (line 120, fd 15) doveadm(user(a)domain.com): Warning: Timeout leak: 0x801019fe0 (line 325) doveadm(user(a)domain.com): Panic: file ioloop.c: line 39 (io_add_file): assertion failed: (callback != NULL) zsh: abort doveadm index -u user(a)domain.com INBOX Any ideas? Rgds, N.

1 1

Re: fs_api_module_register
by Eric Broch 19 May '15

19 May '15

Marcus, Thanks for the spec file. I'm fairly new to creating RPM's and I just found out that the issue is taking place during the 'make check' portion of the spec file. I'm not sure what 'make check' does after having googled it, although, I think it checks for run-time errors. Any hints? Eric On 5/16/2015 12:52 PM, Marcus Rueckert wrote: > On 2015-05-16 11:52:55 -0600, Eric Broch wrote: >> I'm building on CentOS 5 (x86) and CentOS 6 (x86_64). The rpmbuild >> failed on both with the same error. Is there any other information you >> would need from me? I'm not sure if I'm missing some dependency, or not. >> May I trouble you for the dovecot.spec file you used to build your RPM? > https://build.opensuse.org/package/show/server:mail/dovecot22 > > sles 11 should be close to centos 6. > > darix >

1 1

Imap process timeout to quota proxy on logout after async commit
by Fernando Coelho 19 May '15

19 May '15

Hi there, I am having some trouble implementing a quota proxy server for a memcached based dict (I am using the version 2.2.15). I created a multi-threaded daemon that is using non-blocking sockets to receive the data and reply to dovecot. Right now everything but the atomic increase message is working great. Here is an example of such a message: B1 A1 priv/quota/storage 86583 A1 priv/quota/messages 1 D1 The program process it and I replies:OA1 Everything keeps working as expects until the user sends the imap a logout command. The only problem is that for some reason dovecot tries to read data from server without sending anything, and after 30 seconds it exits with an timeout error. The following message is logged: May 18 22:46:00 imap[11654]: user 29908633#perm!terra (29908633#perm!terra) from 127.0.0.1: Error: read(/tmp/quotatest) failed: Timeout after 30 seconds May 18 22:46:00 imap[11654]: user 29908633#perm!terra (29908633#perm!terra) from 127.0.0.1: Info: Disconnected: Logged out in=40 out=827 May 18 22:46:00 imap[11654]: user 29908633#perm!terra (29908633#perm!terra) from 127.0.0.1: Error: dict quota: Quota update failed, it's now desynced The really strange part is that it only fails if and atomic increase was sent and only when the user logs out. I use the same pattern ("OA<transaction id>\n") to reply for other commits (such as when there is an unset followed by a set) and there is no issue. Is there anything that I am missing? Thanks in advance.

1 0

sssd and dovecot
by Günther J. Niederwimmer 18 May '15

18 May '15

Hello, I like to install dovecot on a centos 7.1 with freeIPA all information for dovecot is from sssd. but I found no way to configure this correct. Have any a link, or can help me please. Thanks for a answer. -- mit freundlichen Grüssen / best regards, Günther J. Niederwimmer

2 1

Should I use "dsync_remote_cmd" with dsync via tcp?
by Listas＠Adminlinux 18 May '15

18 May '15

Hi, By the Documentation the directive "dsync_remote_cmd" seems to me required only to dsync via ssh. Is this right? I have set dsync via tcp. Should I have set "dsync_remote_cmd" ? Thanks! Thiago Henrique

1 0

Failure at run doveadm deduplicate
by Listas＠Adminlinux 18 May '15

18 May '15

Hi, In my server, accounts are receiving many doubled emails in its mailbox. In some accounts the "doveadm deduplicate" is doing nothing, even if there are duplicate messages. But in some cases, this error has left me particularly concerned: # doveadm deduplicate -u <user> -m ALL doveadm(<user>): Panic: file mail-transaction-log.c: line 271 (mail_transaction_log_rotate): assertion failed: (file->locked) doveadm(<user>): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x67f30) [0x7f77b9f85f30] -> /usr/lib/dovecot/libdovecot.so.0(default_fatal_handler+0x2a) [0x7f77b9f85f9a] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f77b9f39515] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xc296f) [0x7f77ba2b996f] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_index_write+0x1be) [0x7f77ba2b8c3e] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_index_sync_commit+0x262) [0x7f77ba2b1012] -> /usr/lib/dovecot/libdovecot-storage.so.0(mdbox_map_atomic_finish+0x26) [0x7f77ba225a36] -> /usr/lib/dovecot/libdovecot-storage.so.0(mdbox_sync+0x61) [0x7f77ba229d91] -> /usr/lib/dovecot/libdovecot-storage.so.0(mdbox_storage_sync_init+0x66) [0x7f77ba229e26] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_sync_init+0x2b) [0x7f77ba26954b] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_sync+0x27) [0x7f77ba269657] -> doveadm(+0x1b5f4) [0x7f77bab995f4] -> doveadm(+0x1970b) [0x7f77bab9770b] -> doveadm(doveadm_mail_try_run+0x26c) [0x7f77bab9845c] -> doveadm(main+0x414) [0x7f77bab946a4] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7f77b9b7aec5] -> doveadm(+0x168f7) [0x7f77bab948f7] I'm using dovecot-2.2.15. Is this known? What other kind of information could be useful to help find this issue? Full log on the link: http://pastebin.com/CMfjxydy My confs with doveconf -n : http://www.adminlinux.com.br/newcluster_doveconf.txt Thanks Thiago Henrique

1 0

fts_lucene error
by Hanns Mattes 18 May '15

18 May '15

Hi, after upgrading to 2.2.18 I get the following error: lmtp(root(a)bruecko.de): Error: Couldn't load required plugin /usr/lib64/dovecot/modules/lib21_fts_lucene_plugin.so: dlopen() failed: /usr/lib64/dovecot/modules/lib21_fts_lucene_plugin.so: undefined symbol: _ZN6lucene8analysis8snowball16SnowballAnalyzerC1EPFiPKvmP6bufferEPKc Running Opensuse 13.2 I'm using the RPMs from the server-Mail Repo. So I'm not sure, if the error is related to this builds, my system or something else. Any hints? Regards Hanns

3 4

RE: v2.2.18 released
by dovecot＠outputservices.com 18 May '15

18 May '15

I am just starting out and trying to get dovecot and postfix working in Solaris 10 environment. Went from 2.2.15 to 2.2.17, then to 2.2.18 Both version 2.2.17 & 2.2.18 gave this same error. 2.2.15 does not. ----------------------------------- May 15 09:27:37 master: Info: Dovecot v2.2.18 starting up for imap May 15 09:27:37 ssl-params: Info: Generating SSL parameters May 15 09:27:37 ssl-params: Fatal: Couldn't load required plugin /tmp/tocevod/lib/dovecot/libssl_iostream_openssl.so: dlopen() failed: ld.so.1: ssl-params: fatal: relocation error: file /tmp/tocevod/lib/dovecot/libssl_iostream_openssl.so: symbol SSL_clear_options: referenced symbol not found May 15 09:27:37 ssl-params: Error: child process failed with status 22784 May 15 09:27:46 master: Warning: Killed with signal 15 (by pid=1848 uid=0 code=kill) ------------------------------------------------ doveconf -n # 2.2.18: /tmp/tocevod/etc/dovecot/dovecot.conf # OS: SunOS 5.10 i86pc log_path = /tmp/tocevod/log/log login_trusted_networks = 137.106.0.0/16 mail_location = mbox:~/posta:INBOX=/var/mail/%u namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { args = /dovecot/etc/dovecot/conf.d/ldap.settings driver = ldap } protocols = imap service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 } } ssl_cert = </dovecot/certs/dovecot.pem ssl_key = </dovecot/certs/dovecot.key ssl_prefer_server_ciphers = yes ssl_protocols = !SSLv2 !SSLv3 userdb { args = /dovecot/etc/dovecot/conf.d/ldap.settings driver = ldap }

1 0

Googling: dovecot: auth-worker(default): pam_start() failed: Critical error - immediate abort
by david＠davidwbrown.name 18 May '15

18 May '15

Howdy, Googling: dovecot: auth-worker(default): pam_start() failed: Critical error - immediate abort dobbeltganger dovecot: auth-worker(default): pam(user,1.2.3.4): lookup service=dovecot dobbeltganger out of memory [4543] returns just 3 references. Examining memory server side reveals use of virtual memory but not 100% OS: Ubuntu 14.04 client 10.04 server-side. Email client: Thunderbird (Thunderbird prompts for the password which has worked for years). dovecot -n # 1.2.9: /etc/dovecot/dovecot.conf # OS: Linux 2.6.34.1-rscloud x86_64 Ubuntu 10.04.4 LTS log_timestamp: %Y-%m-%d %H:%M:%S ssl: required verbose_ssl: yes login_dir: /var/run/dovecot/login login_executable: /usr/lib/dovecot/imap-logina login_processes_count: 5 login_max_processes_count: 256 mail_max_userip_connections: 40 mail_privileged_group: mail mail_location: maildir:~/Maildir mail_debug: yes mbox_write_locks: fcntl dotlock auth default: realms: davidwbrown.name, karlbrown.name default_realm: dobbeltganger.com username_format: %n verbose: yes debug: yes debug_passwords: yes passdb: driver: pam userdb: driver: passwd socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix

1 0

How do I fix this: master: Warning: fd limit (ulimit -n) is lower than required
by Robert Chalmers 16 May '15

16 May '15

I get this when I reload dovecot after any changes. How can I fix it? I can’t find any reference to it anywhere. master: Warning: fd limit (ulimit -n) is lower than required under max. load (256 < 1000), because of default_client_limit thanks Robert

3 5

fs_api_module_register
by Eric Broch 16 May '15

16 May '15

Hello list, I'm trying to build a binary rpm from dovecot sources 2.2.18 and pigeonhole.0.4.8. During the make portion I'm getting the following error: make[3]: Leaving directory `/root/rpmbuild/BUILD/dovecot-2.2.18/src/lib-storage' for bin in test-mail-search-args-imap test-mail-search-args-simplify test-mailbox-get; do \ if ! /bin/sh ../../run-test.sh ../.. ./$bin; then exit 1; fi; \ done /root/rpmbuild/BUILD/dovecot-2.2.18/src/lib-storage/.libs/lt-test-mail-search-args-imap: symbol lookup error: /root/rpmbuild/BUILD/dovecot-2.2.18/src/lib-storage/.libs/lt-test-mail-search-args-imap: undefined symbol: fs_api_module_register I created a binary rpm from dovecot sources 2.2.16 and pigeonhole sources 0.4.7 and all went well. Can anyone give me any hints as to the problem? Eric

2 2

Core dump at imap process
by Dominik Breu 16 May '15

16 May '15

hello list, testing the 2.18 release i got following core dump. Maybe Timo you can get a look at it. greetings dominik Core Dump: root@hbs-buko:/var/vmail/hbs-buko.info/dominik.breu# gdb /usr/lib/dovecot/imap core GNU gdb (Debian 7.7.1+dfsg-5) 7.7.1 Copyright (C) 2014 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from /usr/lib/dovecot/imap...Reading symbols from /usr/lib/debug//usr/lib/dovecot/imap...done. done. [New LWP 4069] Core was generated by `dovecot/imap'. Program terminated with signal SIGSEGV, Segmentation fault. #0 imap_msgpart_contains_body (msgpart=0x0) at imap-msgpart.c:311 311 imap-msgpart.c: Datei oder Verzeichnis nicht gefunden. (gdb) bt full #0 imap_msgpart_contains_body (msgpart=0x0) at imap-msgpart.c:311 No locals. #1 0x00007f4eba177054 in fetch_state_update_stats (msgpart=<optimized out>, ctx=0x7f4ebacfa910, ctx=0x7f4ebacfa910) at imap-fetch-body.c:169 No locals. #2 0x00007f4eba17747b in fetch_rfc822_header (ctx=0x7f4ebacfa910, mail=0x7f4ebad08a10, context=<optimized out>) at imap-fetch-body.c:529 msgpart = 0x0 str = <optimized out> #3 0x00007f4eba1754cc in imap_fetch_more_int (ctx=ctx@entry=0x7f4ebacfa910, cancel=false) at imap-fetch.c:506 h = <optimized out> _data_stack_cur_id = 4 state = 0x7f4ebacfa960 client = 0x7f4ebacf9bb0 count = <optimized out> ret = <optimized out> __FUNCTION__ = "imap_fetch_more_int" #4 0x00007f4eba1765ca in imap_fetch_more (ctx=0x7f4ebacfa910, cmd=cmd@entry=0x7f4ebacfa7b0) at imap-fetch.c:558 ret = <optimized out> __FUNCTION__ = "imap_fetch_more" #5 0x00007f4eba169864 in cmd_fetch (cmd=0x7f4ebacfa7b0) at cmd-fetch.c:286 client = <optimized out> ctx = 0x7f4ebacfa910 args = 0x7f4ebace2b08 next_arg = <optimized out> list_arg = 0x7f4ebad03b50 search_args = 0x0 qresync_args = {qresync_sample_seqset = 0x7f4ebacd71f8, qresync_sample_uidset = 0x1} messageset = 0x7f4ebace2c70 "353" send_vanished = <optimized out> ret = <optimized out> #6 0x00007f4eba173cbc in command_exec (cmd=cmd@entry=0x7f4ebacfa7b0) at imap-commands.c:167 hook = 0x7f4ebace00f0 diff = <optimized out> finished = <optimized out> #7 0x00007f4eba172b32 in client_command_input (cmd=0x7f4ebacfa7b0) at imap-client.c:828 client = 0x7f4ebacf9bb0 command = <optimized out> __FUNCTION__ = "client_command_input" #8 0x00007f4eba172f2d in client_handle_next_command (remove_io_r=<synthetic pointer>, client=0x7f4ebacf9bb0) at imap-client.c:926 No locals. #9 client_handle_input (client=0x7f4ebacf9bb0) at imap-client.c:938 _data_stack_cur_id = 3 remove_io = false handled_commands = false client = 0x7f4ebacf9bb0 #10 0x00007f4eba1732f5 in client_input (client=0x7f4ebacf9bb0) at imap-client.c:980 cmd = 0xea880 output = 0x7f4ebacfa5d0 bytes = 2 __FUNCTION__ = "client_input" #11 0x00007f4eb99a2b6c in io_loop_call_io (io=0x7f4ebacfa6c0) at ioloop.c:501 ioloop = 0x7f4ebacdf740 t_id = 2 __FUNCTION__ = "io_loop_call_io" ---Type <return> to continue, or q <return> to quit--- #12 0x00007f4eb99a3ba5 in io_loop_handler_run_internal (ioloop=ioloop@entry=0x7f4ebacdf740) at ioloop-epoll.c:220 ctx = 0x7f4ebace0460 io = <optimized out> tv = {tv_sec = 1799, tv_usec = 999300} events_count = <optimized out> msecs = <optimized out> ret = 1 i = 0 j = <optimized out> call = <optimized out> __FUNCTION__ = "io_loop_handler_run_internal" #13 0x00007f4eb99a2bd9 in io_loop_handler_run (ioloop=ioloop@entry=0x7f4ebacdf740) at ioloop.c:548 No locals. #14 0x00007f4eb99a2c58 in io_loop_run (ioloop=0x7f4ebacdf740) at ioloop.c:525 __FUNCTION__ = "io_loop_run" #15 0x00007f4eb9941243 in master_service_run (service=0x7f4ebacdf5d0, callback=<optimized out>) at master-service.c:581 No locals. #16 0x00007f4eba16696c in main (argc=1, argv=0x7f4ebacdf390) at main.c:431 set_roots = {0x7f4eba38b940 <imap_setting_parser_info>, 0x0} login_set = {auth_socket_path = 0x7f4ebacd7048 "\001", postlogin_socket_path = 0x0, postlogin_timeout_secs = 60, callback = 0x7f4eba17ccc0 <login_client_connected>, failure_callback = 0x7f4eba17c930 <login_client_failed>, request_auth_token = 1} service_flags = <optimized out> storage_service_flags = <optimized out> username = 0x0 c = <optimized out>

2 2

Dovecot Replication - Architecture Endianness?
by Reuben Farrelly 16 May '15

16 May '15

Hi all, I've had an interesting use case come up which - to cut the story short - one way to solve the problem I am looking at may be to replicate a small number of mailboxes to a third remote server. I've currently had replication running between my main dovecot machine and another remote VM for some time and working well (so I'm not new to replication and I've got a good working config), but I've a need to add a third to the mix for a select number of mailboxes. The arch on both of those is Gentoo x86_64 and with latest 2.1.16 -hg. I have attempted this so far by rsync'ing the initial Maildirs and then once the bulk of the data has been transferred rely on dovecot's replication to keep things in sync. I figure that this should in theory mean that the subsequent updates in both directions are incremental and the bulk of the data gets moved while the device is here on my desk using rsync. I've attempted to do this using a Raspberry Pi as a remote device, but when I set it up the dovecot replication process seems to need to start the replication over from scratch even after the rsync is done. I know this is happening as the disk utilisation on the Pi skyrockets once the replication starts and I end up with thousands of double ups of all the mails ... which defeats the entire point of the process. If I do an identical configuration but on a third Gentoo x86_64 VM locally it all works as expected. No double ups of mails and the "catchup" between the two devices is practically instant. Same filesystem even. The only difference appears to be the system architecture. So main my question is this. Is there a known architecture/endian limitation on replication? I guess cross-arch replication is not something many people try but is it supposed to work anyway? Has anyone else got replication working across different arch's? Also is there a way to restrict replication users aside from a crude hack around system first and last UIDs? Thanks, Reuben

3 10

Re: imap_logout_format improvements
by Joseph Tam 16 May '15

16 May '15

Timo Sirainen wrote: > So all in all, you can now add to imap_logout_format: >... > Any thoughts on what else would be useful? Maybe quota stats like number of quota errors, or quota usage? Bytes used by Email marked \Deleted? Joseph Tam <jtam.home(a)gmail.com>

2 1

Re: [Dovecot] IMAP and POP3 operations log per user
by Miloš Dukić 16 May '15

16 May '15

On 05/14/15 23:49, Jorge Bastos wrote: > Hi, > > > > I'd like to have a log per user, and protocol (imap+pop3), where this log > would tell me/save the message sender+subject+operation (deleted, marked to > expunge/other/was read/other). > > Is there something similar to this that already exists? > > > > If not is there something like this on the TODO/whishlist? > > > > Thanks in advanced, > > Jorge Bastos > . > Jorge, Per user loggin is not available. You can enable Dovecot events in 10-logging.conf. Just uncomment mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename in plugin section. Depending on your setup, it will be logged to /var/log/maillog, or whatever you defined in your syslog configuration.

1 0

Released Pigeonhole v0.4.8 for Dovecot v2.2.18
by Stephan Bosch 15 May '15

15 May '15

Hello Dovecot users, Here is the final 0.4.8 release. No significant changes were committed since the last release candidate. Changelog v0.4.8: * LDA Sieve plugin: Dovecot changed the deliver_log_format setting to include %{delivery_time}. This prompted changes in Pigeonhole that make this release dependent on Dovecot v2.2.17. + Implemented magic to make sieve_default script visible from ManageSieve under a configurable name. This way, users can see the default rules, edit them and store a private adjusted version. This could also be achieved by copying the default script into the user's script storage, but updates to the global sieve_default script would be ignored that way. + ManageSieve: Implemented support for reporting command statistics at disconnect. Statistics include the number of bytes and scripts uploaded/downloaded/checked and the number of scripts deleted/renamed. - Fixed problem in address test: erroneously decoded mime-encoded words in address headers. - extprograms plugin: Fixed failure occurring when connecting to script service without the need to read back the output from the external program. - Fixed bug in script storage path normalization occurring with relative symbolic links below root. - Fixed and updated various parts of the documentation - ManageSieve: Used "managesieve" rather than "sieve" as login service name, which means that all managesieve-specific settings where ignored. - Managesieve: Storage quota was not always enforced properly for scripts uploaded as quoted string. Nobody uses that, but it is allowed in the specification and we support it, so it should work properly. The release is available as follows: http://pigeonhole.dovecot.org/releases/2.2/dovecot-2.2-pigeonhole-0.4.8.tar… http://pigeonhole.dovecot.org/releases/2.2/dovecot-2.2-pigeonhole-0.4.8.tar… Refer to http://pigeonhole.dovecot.org and the Dovecot v2.x wiki for more information. Have fun testing this new release and don't hesitate to notify me when there are any problems. Regards, -- Stephan Bosch stephan(a)rename-it.nl

1 0

Many Duplicated messages after migrate from 2.0.19 to 2.2.15
by Listas＠Adminlinux 15 May '15

15 May '15

Hi, In my company, we have several failover clusters (~50k accounts per cluster) with Ubuntu12.04 and Dovecot-2.0.19 (without dsync, replication at block level with DRBD). We are migrating to active/active clusters with Ubuntu14.04 and Dovecot-2.2.15 with replication via dovecot-dsync. Each new cluster consists of two machines and each machine runs two instances of Dovecot (one for backend and the other for proxy Dovecot-director). We did the migration of message files, indexes and sieve scripts using rsync to one of the backends. After we turn on the second backend and let the dsync work in replication for him. Now, many accounts are with duplicated messages and some new emails delivered are also being duplicated. Doveadm deduplicate doesn't work for me. I ran: doveadm deduplicate -u <user> -m ALL Does do the migration of files with rsync was a mistake ? We are using mdbox on both clusters. My confs with doveconf -n for both clusters: http://www.adminlinux.com.br/newcluster_doveconf.txt http://www.adminlinux.com.br/oldcluster_doveconf.txt Thanks and regards, Thiago Henrique

1 0

v2.2.18 released
by Timo Sirainen 15 May '15

15 May '15

http://dovecot.org/releases/2.2/dovecot-2.2.18.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.18.tar.gz.sig Oops, director was somewhat broken in 2.2.17. I thought I tested the last changes in it well enough, but looks like not. To avoid all existing Dovecot director installations from breaking I decided to make 2.2.18 release quickly afterwards.. BTW. We're planning on making some changes soon to how version control is used in Dovecot development, which should help avoid these kind of problems. The main problem now is that everything gets directly committed to the master branch (although we have a separate more stable dovecot-ee repo also). The new plan is to do something like this: http://nvie.com/posts/a-successful-git-branching-model/ Besides some minor compiling issues and other small changes, the important ones are: - director: Login UNIX sockets were normally detected as doveadm or director ring sockets, causing it to break in existing installations. - sdbox: When copying a mail in alt storage, place the destination to alt storage as well.

3 2

Best practice for getting sieve scripts replicated?
by Michael Grimm 15 May '15

15 May '15

Hi — I do have replication between two servers running, and mail is replicated without any issues. I do have sieve running at both servers without any issues. But replication of sieve scripts doesn't work as "expected": Whenever I do modify my default script und upload it via "doveadm sieve put -u abc -a default < default" it becomes uploaded to the home directory of user abc as expected, but it will not be replicated to the partner server. Whenever I do deactivate the default script by "doveadm sieve deactivate -u abc", followed by a deletion "doveadm sieve delete -u abc default" plus subsequent upload of the script "doveadm sieve put -u abc -a default < default", replication takes place instantly. Questions: Is a modification of a sieve script supposed to be triggered the latter way? Or am I doing it the wrong way? Thanks and regards, Michael

2 5

Alternate Storage altmove not working bug
by Daniel van Ham Colchete 15 May '15

15 May '15

Hello everyone! I would like to report a bug here. We are using dovecot's sdbox with alternate storage here. From time to time my SSD partition gets full and I always find users with lots of e-mails stuck there, and altmove just won't move them. It moves most of the e-mails correctly, but a few was getting stuck everyday. So, I think I have found the problem! When a user moves the message from one mailbox to another, the move will keep all the flags! Including MAIL_INDEX_MAIL_FLAG_BACKEND 0x40. So, altmove think this message was already moved and doesn't do anything. I did a doveadm dump on the destination mailbox's index and what I see is a lot of this: RECORD: seq=104, uid=104, flags=0x48 (Seen) - ext 0 keywords : (0000) - ext 1 modseq : 12 (0c00000000000000) - ext 3 cache : 14004 (b4360000) - cache offset=14004 size=76, prev_offset = 0 - mime.parts: (48000000b404000000000000cc04000000000000e542000000000000fd4300000000000018010000) (pos=0 hdr.p=1204 hdr.v=1228 body.p=17125 body.v=17405 flags=48) - size.physical: 18329 (9947000000000000) - date.received: 1418235366 (e68d8854) Although the 0x40 flag is set, the file still lives on the main/ssd storage area. My config: http://pastebin.com/8Wk4bfRK Dovecot version: 2.2.5-0~auto+22 Host is Xeon E3 64bit, running Debian 7. Filesystem is plain local ext4 on both storage areas I know my version is outdated but I didn't find anything related to this there. Just one last question: how can I remove that flag from the message? I have taken a look at doveadm-flags(1) but it doesn't seem to allow anything on that flag. Thank you very much! Best, Daniel Colchete

2 2

Return code 139 when enabling auth debugging
by Stefan Midjich 15 May '15

15 May '15

Hi I'm running dovecot 2.2.10 installed from base repos on CentOS 7. I'm trying to use sqlite as an auth backend but it's not working so I enabled some auth debugging settings in conf.d/10-logging.conf and then dovecot refused to start. sudo dovecot -F produced 139. Here is doveconf -n: http://dpaste.com/2BNB2F7 Unfortunately when I have these settings enabled doveconf does not work and only produces the first comment line. So here is the output of sudo grep -v '^#' /etc/dovecot/conf.d/10-logging.conf | grep -v '^$': http://dpaste.com/0G0VVK8 And when these settings are uncommented dovecot -F produces return code 139 and no output. So I'm having a hard time troubleshooting my authentication when I can't even troubleshoot my debug options not working. ;) -- Hälsningar / Greetings http://Stefan.Midjich.name

1 0

Re: [Dovecot] IMAP and POP3 operations log per user
by Steffen Kaiser 15 May '15

15 May '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thu, 14 May 2015, Jorge Bastos wrote: > I'd like to have a log per user, and protocol (imap+pop3), where this log > would tell me/save the message sender+subject+operation (deleted, marked to > expunge/other/was read/other). > Is there something similar to this that already exists? Check out the mail_log plugin. You'll have to break the logfiles by users via script. - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEVAwUBVVWSGHz1H7kL/d9rAQLIzAf/ZtNOLa1n12LnxwhMaS1B+6LEHDOCZWtw ldTarGE0uovu/OH84PEq4MkE5Y1Oww+VWmA+b2csBx1C0bZmcQeF2g7O65fESYsI Qu/xSuJLhOyUm4sppE62Zqyxba+rG2tyj9XpKMrHI6nU3ZTCOhVu/RJ2TB2WkhkB 21pgYEpkBYvRZK2PPqRwl+Lwc3oGQvWoYHcyniXL0v2P5tNNQj1gTuGVm53dPliM cFm9p4EjAOKEZyFgQokBljDpp03OMpEu16GT8XjCg8Fxg2BkF2XHBx/Wvv8DxQCC vyLA1SFMLNNRoizwF+xVlUJu4AW8fWBLhCgvOAFw4mFXkbMoi+lUwQ== =vRwJ -----END PGP SIGNATURE-----

1 0

Trying to get mail working
by Steve Matzura 15 May '15

15 May '15

I have charge of a very mixed system--current OS (Fedora 20--OK 21's out but I just haven't upgraded yet), current (or nearly so) Mailman (2.1.18-1), Postfix 2.10 with a configuration file sfrom something a lot older which I've run through the upgrade-configuration procedure, and old Dovecot (1.0.15). Is there anything I can do to test each of these components individually, then add a second component and test the three pairs, then all three together? I am nobody's definitioin of an expert in any of these three components, so am having a lot of trouble making them work together, so I thought maybe there might be some test procedure that might straighten me out. Thanks in advance.

2 1

[Dovecot] IMAP and POP3 operations log per user
by Jorge Bastos 14 May '15

14 May '15

Hi, I'd like to have a log per user, and protocol (imap+pop3), where this log would tell me/save the message sender+subject+operation (deleted, marked to expunge/other/was read/other). Is there something similar to this that already exists? If not is there something like this on the TODO/whishlist? Thanks in advanced, Jorge Bastos

1 0

v2.2.17 Segfault
by Adam Lackorzynski 14 May '15

14 May '15

Hi, I'm using libexec/dovecot/imap via a ssh tunnel. 2.2.17 segfaults while accessing a NULL pointer. The following change fixes it for me: --- dovecot-2.2.17/src/lib-imap/imap-keepalive.c 2015-05-03 11:12:11.000000000 +0200 +++ dovecot-2.2.17/src/lib-imap/imap-keepalive.c 2015-05-14 20:06:29.490617405 +0200 @@ -11,6 +11,8 @@ { unsigned int addr; + if (!ip) + return FALSE; if (ip->family == 0) return FALSE; if (ip->family == AF_INET) { Thanks, Adam -- Adam adam(a)os.inf.tu-dresden.de Lackorzynski http://os.inf.tu-dresden.de/~adam/

2 1

Pigeonhole v0.4.8.rc3 compilation error (bad mail-deliver.h)
by Jacques Distler 14 May '15

14 May '15

Got a /usr/local/include/dovecot/mail-deliver.h:30:17: error: field has incomplete type 'struct timeval' struct timeval delivery_time_started; ^ error. This is because mail-deliver.h in dovecot-2.2.17 is missing an #include <sys/time.h> Adding that line to mail-deliver.h fixes the problem. Oddly, I had no problem compiling dovecot itself.

2 1

v2.2.17 released
by Timo Sirainen 14 May '15

14 May '15

http://dovecot.org/releases/2.2/dovecot-2.2.17.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.17.tar.gz.sig A few director improvements since RC2, some fixes and a new plugin: http://wiki2.dovecot.org/Plugins/QuotaClone * Dovecot no longer checks or warns if a mountpoint is removed. This was causing more trouble than it was worth. Make sure that all the mountpoints that Dovecot accesses aren't writable by mail processes when they're unmounted. * dict server wasn't properly escaping/unescaping data. Fixing this broke backwards compatibility with data that contains line feeds. This hopefully affects only very few installations. If you're using dict to save multiline data (Sieve scripts to SQL), you may be affected. * imap: SPECIAL-USE capability is no longer advertised if there are no special_use flags specified for any mailboxes. + lmtp: Added lmtp_hdr_delivery_address setting to specify whether to include email address in Delivered-To: and Received: headers. + Added initial version of full text search library, which includes language-specific text normalization and filtering. This is still in development, but it's already possible to use for testing with fts-lucene and fts-solr. + lda, lmtp: deliver_log_format can now include %{delivery_time}, which expands to how many milliseconds it took to deliver the mail. With LMTP %{session_time} also expands to how many milliseconds the LMTP session took, not including the delivery time. + lmtp proxy: Mail delivery logging includes timing information. + imap: Most IMAP commands now include in the tagged reply how many milliseconds it took to run the command (not counting the time spent on waiting for the IMAP client to read/write data). + director: Implemented director_proxy_maybe passdb extra field to be able to run director and backend in the same Dovecot instance. (LMTP doesn't support mixed proxy/non-proxy destinations currently.) + doveadm: Added -F <file> parameter to read a list of users from the given file and run the command for all the users. This is similar to -A parameter reading the list of users from userdb lookup. + Implemented initial Cassandra CQL support as lib-sql backend. It's only usable as dict backend currently. + Added quota-clone plugin to copy current quota usage to a dict. - auth: If auth_master_user_separator was set, auth process could be crashed by trying to log in with empty master username. - imap-login, pop3-login: Fixed crash on handshake failures with new OpenSSL versions (v1.0.2) when SSLv3 was disabled. - auth: If one passdb fails allow_nets check, it shouldn't have failed all the other passdb checks later on. - imap: Server METADATA couldn't be accessed - imapc: Fixed \Muted label handling in gmail-migration. - imapc: Various bugfixes and improvements. - Trash plugin fixes by Alexei Gradinari - mbox: Fixed crash/corruption in some situations

2 1

Released Pigeonhole v0.4.8.rc3 for Dovecot v2.2.17
by Stephan Bosch 13 May '15

13 May '15

Hello Dovecot users, RC2 had one more important bug caused by the new sieve_default_name feature. To prevent causing more of such rather stupid bugs in the future, I created an external shell-based test suite to test dovecot-lda delivery, the doveadm sieve tools and ManageSieve. These kind of tests aren't possible with the current Sieve-based test suite that is included in the Pigeonhole tarball. Now I can test most basic top-level Pigeonhole functionality in one go. Additionally, I created one new feature for ManageSieve. It allows logging various statistics at client disconnect, much like POP3 currently supports. This is e.g. useful for debugging. In the process, I fixed a few ManageSieve bugs as well. If RC3 doesn't cause any more issues, I will release 0.4.8 this Friday. Changelog v0.4.8 (updated): * LDA Sieve plugin: Dovecot changed the deliver_log_format setting to include %{delivery_time}. This prompted changes in Pigeonhole that make this release dependent on Dovecot v2.2.17. + Implemented magic to make sieve_default script visible from ManageSieve under a configurable name. This way, users can see the default rules, edit them and store a private adjusted version. This could also be achieved by copying the default script into the user's script storage, but updates to the global sieve_default script would be ignored that way. + ManageSieve: Implemented support for reporting command statistics at disconnect. Statistics include the number of bytes and scripts uploaded/downloaded/checked and the number of scripts deleted/renamed. - Fixed problem in address test: erroneously decoded mime-encoded words in address headers. - extprograms plugin: Fixed failure occurring when connecting to script service without the need to read back the output from the external program. - Fixed bug in script storage path normalization occurring with relative symbolic links below root. - Fixed and updated various parts of the documentation - ManageSieve: Used "managesieve" rather than "sieve" as login service name, which means that all managesieve-specific settings where ignored. - Managesieve: Storage quota was not always enforced properly for scripts uploaded as quoted string. Nobody uses that, but it is allowed in the specification and we support it, so it should work properly. The release is available as follows: http://pigeonhole.dovecot.org/releases/2.2/dovecot-2.2-pigeonhole-0.4.8.rc3… http://pigeonhole.dovecot.org/releases/2.2/dovecot-2.2-pigeonhole-0.4.8.rc3… Refer to http://pigeonhole.dovecot.org and the Dovecot v2.x wiki for more information. Have fun testing this new release and don't hesitate to notify me when there are any problems. Regards, -- Stephan Bosch stephan(a)rename-it.nl

1 0

v2.2.17 release candidate 2 released
by Timo Sirainen 13 May '15

13 May '15

http://dovecot.org/releases/2.2/rc/dovecot-2.2.17.rc2.tar.gz http://dovecot.org/releases/2.2/rc/dovecot-2.2.17.rc2.tar.gz.sig Changes since rc1: - Compiling fix for fs-compress in Solaris and maybe others. - Implemented Cassandra CQL support as lib-sql backend. This is mainly usable as dict-sql backend. - lib-fts fixes and improvements - Some other small random changes If no new issues are found, v2.2.17 final should be out in a day or two. (Actually looks like I have a few more bugs that probably will be fixed for it.) Changes since v2.2.16: * Dovecot no longer checks or warns if a mountpoint is removed. This was causing more trouble than it was worth. Make sure that all the mountpoints that Dovecot accesses aren't writable by mail processes when they're unmounted. * dict server wasn't properly escaping/unescaping data. Fixing this broke backwards compatibility with data that contains line feeds. This hopefully affects only very few installations. If you're using dict to save multiline data (Sieve scripts to SQL), you may be affected. * imap: SPECIAL-USE capability is no longer advertised if there are no special_use flags specified for any mailboxes. + lmtp: Added lmtp_hdr_delivery_address setting to specify whether to include email address in Delivered-To: and Received: headers. + Added initial version of full text search library, which includes language-specific text normalization and filtering. This is still in development, but it's already possible to use for testing with fts-lucene and fts-solr. + lda, lmtp: deliver_log_format can now include %{delivery_time}, which expands to how many milliseconds it took to deliver the mail. With LMTP %{session_time} also expands to how many milliseconds the LMTP session took, not including the delivery time. + lmtp proxy: Mail delivery logging includes timing information. + imap: Most IMAP commands now include in the tagged reply how many milliseconds it took to run the command (not counting the time spent on waiting for the IMAP client to read/write data). + director: Implemented director_proxy_maybe passdb extra field to be able to run director and backend in the same Dovecot instance. (LMTP doesn't support mixed proxy/non-proxy destinations currently.) + doveadm: Added -F <file> parameter to read a list of users from the given file and run the command for all the users. This is similar to -A parameter reading the list of users from userdb lookup. + Implemented initial Cassandra CQL support as lib-sql backend. It's only usable as dict backend currently. - auth: If auth_master_user_separator was set, auth process could be crashed by trying to log in with empty master username. - imap-login, pop3-login: Fixed crash on handshake failures with new OpenSSL versions (v1.0.2) when SSLv3 was disabled. - auth: If one passdb fails allow_nets check, it shouldn't have failed all the other passdb checks later on. - imap: Server METADATA couldn't be accessed - imapc: Fixed \Muted label handling in gmail-migration. - imapc: Various bugfixes and improvements. - Trash plugin fixes by Alexei Gradinari - mbox: Fixed crash/corruption in some situations when the first mail was expunged.

2 3

dovecot-lda panics when postmaster_address is given on command line
by Onno Molenkamp 13 May '15

13 May '15

Hi, When passing a postmaster_address to dovecot-lda on the command line with -o, it panics: $ ./dovecot-lda -o postmaster_address=anything lda(onno,)Panic: file lda-settings.c: line 80 (lda_settings_check): assertion failed: (set->postmaster_address[0] == SETTING_STRVAR_UNEXPANDED[0]) It looks like postmaster_address has already been expanded at that point when it's given on the command line. (set->postmaster_address[0] is "1") I'm running v2.2.15, but with v2.2.17.rc1 the same thing happens. Regards, Onno

2 1

Released Pigeonhole v0.4.8.rc1 for Dovecot v2.2.17.rc1
by Stephan Bosch 12 May '15

12 May '15

Hello Dovecot users, Here's the Pigeonhole RC that goes with the Dovecot RC. It includes a few small fixes and one new feature. Changelog v0.4.8.rc1: * LDA Sieve plugin: Dovecot changed the deliver_log_format setting to include %{delivery_time}. This prompted changes in Pigeonhole that make this release dependent on Dovecot v2.2.17. + Implemented magic to make sieve_default script visible from ManageSieve under a configurable name. This way, users can see the default rules, edit them and store a private adjusted version. This could also be achieved by copying the default script into the user's script storage, but that way updates to the global sieve_default script would be ignored. - Fixed problem in address test: erroneously decoded mime-encoded words in address headers. - extprograms plugin: Fixed failure occurring when connecting to script service without the need to read back the output from the external program. - Fixed bug in script storage path normalization occurring with relative symbolic links below root. - Fixed and updated various parts of the documentation. The release is available as follows: http://pigeonhole.dovecot.org/releases/2.2/dovecot-2.2-pigeonhole-0.4.8.rc1… http://pigeonhole.dovecot.org/releases/2.2/dovecot-2.2-pigeonhole-0.4.8.rc1… Refer to http://pigeonhole.dovecot.org and the Dovecot v2.x wiki for more information. Have fun testing this new release and don't hesitate to notify me when there are any problems. Regards, -- Stephan Bosch stephan(a)rename-it.nl

3 7

Re: Dovecot is not reading connections from iOS devices correctly. Any ideas?
by Joseph Tam 11 May '15

11 May '15

Robert Chalmers writes: > dovecot-info.log > May 11 09:27:45 imap-login: Info: Aborted login (no auth attempts in 0 > secs): user=<>, rip=192.168.0.1, lip=192.168.0.15, > session=<pXcBJ8oVbgDAqAAB> > > When I try to connect using either the iOS Mail app, or Outlook mail > app, nothing happens at al with ssl, and if I use plain login the iOS > device tells me I have either the username or password wrong - which I > haven't. Some mail readers have auto-discover features that are rather stupid. If possible, manually configure the SSL style (TLS/STARTTLS) and port rather than letting it guess. To diagnose whether it is some dovecot config error, you can manually connect with both flavours of SSL openssl s_client -connect 192.168.0.15:993 ... or ... openssl s_client -starttls imap -connect 192.168.0.15:143 then if it gets past the SSL handshake, a login <user> <password> to test the authentication part. This will at least tell you whether it's a client side or server side issue. (However, since it is working with other client, it's probably a client side issue.) Joseph Tam <jtam.home(a)gmail.com>

1 0

v2.2.17 release candidate released
by Timo Sirainen 11 May '15

11 May '15

http://dovecot.org/releases/2.2/rc/dovecot-2.2.17.rc1.tar.gz http://dovecot.org/releases/2.2/rc/dovecot-2.2.17.rc1.tar.gz.sig Quite a lot of changes, so here's a release candidate first. If no problems are reported I'll make v2.2.17 release early next week. Please test especially non-Linux systems as there are some larger configure/Makefile changes done since v2.2.16. * Dovecot no longer checks or warns if a mountpoint is removed. This was causing more trouble than it was worth. Make sure that all the mountpoints that Dovecot accesses aren't writable by mail processes when they're unmounted. * dict server wasn't properly escaping/unescaping data. Fixing this broke backwards compatibility with data that contains line feeds. This hopefully affects only very few installations. If you're using dict to save multiline data (Sieve scripts to SQL), you may be affected. * imap: SPECIAL-USE capability is no longer advertised if there are no special_use flags specified for any mailboxes. + lmtp: Added lmtp_hdr_delivery_address setting to specify whether to include email address in Delivered-To: and Received: headers. + Added initial version of full text search library, which includes language-specific text normalization and filtering. This is still in development, but it's already possible to use for testing with fts-lucene and fts-solr. + lda, lmtp: deliver_log_format can now include %{delivery_time}, which expands to how many milliseconds it took to deliver the mail. With LMTP %{session_time} also expands to how many milliseconds the LMTP session took, not including the delivery time. + lmtp proxy: Mail delivery logging includes timing information. + imap: Most IMAP commands now include in the tagged reply how many milliseconds it took to run the command (not counting the time spent on waiting for the IMAP client to read/write data). + director: Implemented director_proxy_maybe passdb extra field to be able to run director and backend in the same Dovecot instance. (LMTP doesn't support mixed proxy/non-proxy destinations currently.) + doveadm: Added -F <file> parameter to read a list of users from the given file and run the command for all the users. This is similar to -A parameter reading the list of users from userdb lookup. - auth: If auth_master_user_separator was set, auth process could be crashed by trying to log in with empty master username. - imap-login, pop3-login: Fixed crash on handshake failures with new OpenSSL versions (v1.0.2) when SSLv3 was disabled. - auth: If one passdb fails allow_nets check, it shouldn't have failed all the other passdb checks later on. - imap: Server METADATA couldn't be accessed - imapc: Fixed \Muted label handling in gmail-migration. - imapc: Various bugfixes and improvements. - Trash plugin fixes by Alexei Gradinari - mbox: Fixed crash/corruption in some situations when the first mail was expunged.

10 17

Released Pigeonhole v0.4.8.rc2 for Dovecot v2.2.17.rc1
by Stephan Bosch 11 May '15

11 May '15

Hello Dovecot users, Ok, RC1 contained one rather stupid bug that caused a segfault at delivery. It was caused by a new feature, so the list of changes is not updated. Changelog v0.4.8: * LDA Sieve plugin: Dovecot changed the deliver_log_format setting to include %{delivery_time}. This prompted changes in Pigeonhole that make this release dependent on Dovecot v2.2.17. + Implemented magic to make sieve_default script visible from ManageSieve under a configurable name. This way, users can see the default rules, edit them and store a private adjusted version. This could also be achieved by copying the default script into the user's script storage, but that way updates to the global sieve_default script would be ignored. - Fixed problem in address test: erroneously decoded mime-encoded words in address headers. - extprograms plugin: Fixed failure occurring when connecting to script service without the need to read back the output from the external program. - Fixed bug in script storage path normalization occurring with relative symbolic links below root. - Fixed and updated various parts of the documentation. The release is available as follows: http://pigeonhole.dovecot.org/releases/2.2/dovecot-2.2-pigeonhole-0.4.8.rc2… http://pigeonhole.dovecot.org/releases/2.2/dovecot-2.2-pigeonhole-0.4.8.rc2… Refer to http://pigeonhole.dovecot.org and the Dovecot v2.x wiki for more information. Have fun testing this new release and don't hesitate to notify me when there are any problems. Regards, -- Stephan Bosch stephan(a)rename-it.nl

1 0

Bug#776094: dovecot-imapd: corrupts mailbox after trying to retrieve it (fwd)
by Santiago Vila 11 May '15

11 May '15

Hello. I wrote about this three weeks ago but got no answer. I'm going to officially "forward" the Debian bug this time, with all the details. The test case is just 840 bytes long. Please give it a try. ---------- Forwarded message ---------- From: Santiago Vila <sanvila(a)unex.es> To: submit(a)bugs.debian.org Date: Fri, 23 Jan 2015 22:32:28 +0100 (CET) Subject: dovecot-imapd: corrupts mailbox after trying to retrieve it Package: dovecot-imapd Version: 1:2.2.13-11 Severity: serious The following mbox folder, when put in $HOME/mail, becomes corrupted after trying to retrieve it with fetchmail. The problem may be reproduced by using the same machine as server and client: * Put "inbox-b" in $HOME/mail * Put this in $HOME/.fetchmailrc server localhost proto imap port 143: user "someuser" pass "thepassword" * Retrieve email using this command line: fetchmail -a localhost --folder inbox-b -m "true" Note: By looking at the "true" above it is clear that whatever fetchmail does with the message is not important at all. You will see something like this: 12 messages for someuser at localhost (folder inbox-b). reading message someuser@localhost:1 of 12 (171 header octets) (3 body octets) flushed reading message someuser@localhost:2 of 12 (245 header octets) (3 body octets) flushed reading message someuser@localhost:3 of 12 (245 header octets) (3 body octets) flushed reading message someuser@localhost:4 of 12 (245 header octets) (3 body octets) flushed reading message someuser@localhost:5 of 12 (245 header octets) (3 body octets) flushed reading message someuser@localhost:6 of 12 (171 header octets) (3 body octets) flushed reading message someuser@localhost:7 of 12 (171 header octets) (3 body octets) flushed reading message someuser@localhost:8 of 12 (245 header octets) (3 body octets) flushed reading message someuser@localhost:9 of 12 (245 header octets) (3 body octets) flushed reading message someuser@localhost:10 of 12 (245 header octets) (3 body octets) flushed reading message someuser@localhost:11 of 12 (245 header octets) (3 body octets) flushed reading message someuser@localhost:12 of 12 (273 header octets)fetchmail: incorrect header line found - see manpage for bad-header option not flushed And in fact "inbox-b" in the server is now like this: [...] >From root(a)example.com Tue Jan 13 10:18:20 2015 rstuvwxyzabcdefghijklmnopqrstuvwxyz(a)example.com To: a(a)example.com Subject: a MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Message-Id: <20150113091737.B5ADA5F8B1(a)example.com> Date: Tue, 13 Jan 2015 10:17:25 +0100 (CET) X-UID: 16035 Status: O a Note how the From: line has been truncated from its original state. I have been suffering from this problem for months. At first I believed it was some misbehaving procmail/formail recipe I had on the server, but that's not the case as this example shows. Thanks.

6 23

Dovecot is not reading connections from iOS devices correctly. Any ideas?
by Robert Chalmers 11 May '15

11 May '15

From the dovecot logs. dovecot-info.log May 11 09:27:45 imap-login: Info: Aborted login (no auth attempts in 0 secs): user=<>, rip=192.168.0.1, lip=192.168.0.15, session=<pXcBJ8oVbgDAqAAB> dovecot-debug.log May 11 09:27:45 auth: Debug: auth client connected (pid=17388) When I try to connect using either the iOS Mail app, or Outlook mail app, nothing happens at al with ssl, and if I use plain login the iOS device tells me I have either the username or password wrong - which I haven't. Connection from Mac with MailMate works fine. iOS doesn't. so I'm stumped. I can't see why this is refusing the connection.

1 0

What is this message in appfirewall.log telling me ? on OSX
by Robert Chalmers 11 May '15

11 May '15

I'm on OS X What is this telling me? socketfilterfw[22097] <Info>: dovecot: Deny TCP CONNECT (in:7 out:0) Thanks Robert

2 3

Cant use doveadm to set ACL . [request for help]
by Kevin Laurie 11 May '15

11 May '15

Hi, i keep getting error for using doveadm acl get commands. Below is the output for grep 'socket_path' :- grep 'socket_path' /etc/dovecot/dovecot.conf auth_socket_path = /var/run/dovecot/auth-master auth_socket_path = /var/run/dovecot/auth-master [root@mail root]# doveadm acl get -u bob(a)mydomain.net -S /var/run/dovecot/auth-master -m Inbox doveadm(bob(a)mydomain.net): Error: doveadm server sent invalid handshake: VERSION 1 1 doveadm(bob(a)mydomain.net): Error: /var/run/dovecot/auth-master: Internal failure for bob(a)mydomain.net ID Global Rights

2 1

New York: Matilda, seit Jahren mit dem immer gleichen Outfit - DIE WELT
by Michael Grimm 10 May '15

10 May '15

Cool, und vor allem gut! > http://www.welt.de/vermischtes/article140736122/Matilda-seit-Jahren-mit-dem… <http://www.welt.de/vermischtes/article140736122/Matilda-seit-Jahren-mit-dem…>

1 1

Xi broken
by Stephan Bosch 10 May '15

10 May '15

Hi, Xi is broken at the moment. This XenServer version won't boot jessie kernel. Can't fix this myself, so this may take some time. Regards, Stephan.

4 5

FYI: dovecot (008632bdfd2c) compilation woes, and minor glitch regarding update-version.sh
by Michael Grimm 10 May '15

10 May '15

Hi — 1) I'm trying to compile a recent hg dovecot version (008632bdfd2c) at a FBSD10-STABLE system without success: libtool: compile: cc -DHAVE_CONFIG_H -I. -I../.. -I../../src/lib -I../../src/lib-test -I/usr/local/include -DUDHRDIR=\"../../src/lib-fts\" -DDATADIR=\"/usr/local/share/dovecot\" -DTEST_STOPWORDS_DIR=\"../../src/lib-fts\" -I/usr/local/include -std=gnu99 -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -Wno-duplicate-decl-specifier -Wstrict-aliasing=2 -I/usr/local/include -MT fts-tokenizer-generic.lo -MD -MP -MF .deps/fts-tokenizer-generic.Tpo -c fts-tokenizer-generic.c -fPIC -DPIC -o .libs/fts-tokenizer-generic.o fts-tokenizer-generic.c:111:18: error: use of undeclared identifier 'White_Space' if (uint32_find(White_Space, N_ELEMENTS(White_Space), c, &idx)) ^ fts-tokenizer-generic.c:113:18: error: use of undeclared identifier 'Dash' if (uint32_find(Dash, N_ELEMENTS(Dash), c, &idx)) ^ […] fts-tokenizer-generic.c:212:18: error: use of undeclared identifier 'MidLetter' if (uint32_find(MidLetter, N_ELEMENTS(MidLetter), c, &idx)) ^ fts-tokenizer-generic.c:214:18: error: use of undeclared identifier 'MidNum' if (uint32_find(MidNum, N_ELEMENTS(MidNum), c, &idx)) ^ fatal error: too many errors emitted, stopping now [-ferror-limit=] 20 errors generated. Makefile:591: recipe for target 'fts-tokenizer-generic.lo' failed gmake[4]: *** [fts-tokenizer-generic.lo] Error 1 gmake[4]: Leaving directory '/usr/local/etc/dovecot/SOURCE/dovecot-2.2/src/lib-fts' 2) I don't have a python binary installed, only a python2 link to the python27 binary (FBSD, and python27 from ports). Thus, update-version.sh will fail to evaluate hg's changeset. As a quick fix I needed to create a link: python -> python2 Regards, Michael

4 7

Full text search indexes not used for header/body OR queries?
by Robert L Mathews 09 May '15

09 May '15

I've noticed that when using Lucene full text search, most queries use the indexes and/or header cache and are fast: . SEARCH BODY test . OK Search completed (0.001 secs). . SEARCH SUBJECT test . OK Search completed (0.053 secs). . SEARCH BODY test SUBJECT test . OK Search completed (0.002 secs). . SEARCH OR SUBJECT test FROM test . OK Search completed (0.093 secs). But an OR query that mixes headers and body does not use the available FTS indexes for the BODY part and is slow: . SEARCH OR BODY test SUBJECT test * OK Searched 62% of the mailbox, ETA 0:05 * OK Searched 70% of the mailbox, ETA 0:04 . OK Search completed (15.147 secs). Is this the expected behavior? Since the FTS code can handle an AND of header and body searches, I'm surprised it doesn't do the same for an OR. I noticed this while tracking down poor performance in Thunderbird, which issues searches like this: UID SEARCH RETURN (ALL) (OR FROM "Evelyn" (OR SUBJECT "Evelyn" (OR TO "Evelyn" (OR CC "Evelyn" BODY "Evelyn")))) NOT DELETED These are slow even with FTS enabled because of this behavior. I'm using Dovecot 2.1.7 from Debian wheezy. (I know this is outdated; however, I've examined the 2.1.x and 2.2.x changelogs and found no mention of it.) -- Robert L Mathews, Tiger Technologies, http://www.tigertech.net/

1 1

PublicFolders using Maildir and INDEXPVT in Dovecot v2.2.13
by Panayiotis Fafakos 08 May '15

08 May '15

Dear all, we have succesfully configured Dovecot v2.2.13 in debian wheezy 7.8 (using backports) using Maildir structure, to use private index files for the \Seen flag on a per user basis. All users access their emails and Public Folders using IMAP protocol. The problem is that when a user moves an email from publicFolderA to publicFolderB under the same namespace the other users see this message as unread, although they have actually read it when it was in publicFolderA. Please note that this is an old message which has been moved , it was not copied, so the actual UID should be the same... Is there a way to keep the \Seen flag for the messages that are moved from folder to folder? Is there a way to keep the \Seen flag in a database, so that we can ignore the folder structure and only check the message UIDs? We could use MySQL, PgSQL or even SQLite... Below follows the Public-Folder namespace declaration: ------------------------------------------ namespace { inbox = no location = maildir:/var/vmail/Public-Folders:LAYOUT=fs:INDEXPVT=~/Maildir/public/%u prefix = Public-Folders/ separator = / subscriptions = no type = public } ------------------------------------------ With the above system configuration we have the complete folder structure under ~/Maildir/public/%u, and many log files, one for each folder a user has accessed. Could we only have one index file for each user for all the public folder structure under the same namespace? Kind regards to all, Panayiotis Fafakos

2 3