- dovecot - dovecot.org

FTS solr info
by Brad Koehn 11 Dec '16

11 Dec '16

Are there updated instructions on setting up FTS with solr? I’m in the midst of upgrading my site and the links don’t appear to work or be applicable to current versions of solr. I grabbed 6.3.0 from apache and the instructions are no longer working, e.g., there’s no `solr/conf/schema.xml` file to replace; the `start.jar` has moved, etc. Just wondering if there’s somewhere else I should look, or if I should just hack it together on my own. Thanks! Brad Koehn

2 1

2.2.27 panic file mail-index-map.c: line 549 (mail_index_map_lookup_seq_range): assertion failed: (first_uid > 0)
by Toni Mattila 10 Dec '16

10 Dec '16

Hi, Dec 5 20:24:31 dovecot: imap(xx(a)yy.zz,7ckWZu1CuZFVTILa): Fatal: master: service(imap): child 7292 killed with signal 6 (core dumped) Dec 5 20:24:32 dovecot: imap(xx(a)yy.zz,LnAlZu1COBVVTILa): Panic: file mail-index-map.c: line 549 (mail_index_map_lookup_seq_range): assertion failed: (first_uid > 0) Dec 5 20:24:32 dovecot: imap(xx(a)yy.zz,LnAlZu1COBVVTILa): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0 [0x32416f] -> /usr/lib/dovecot/libdovecot.so.0 [0x3241ed] -> /usr/lib/dovecot/libdovecot.so.0 [0x323e0b] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_index_map_lookup_seq_range+0xf1) [0x234c61] -> /usr/lib/dovecot/libdovecot-storage.so.0 [0x249c2c] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_index_lookup_seq_range+0x2c) [0x24963c] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_get_seq_range+0x3f) [0x1aa39f] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_search_arg_init+0x26f) [0x1997af] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_search_args_init+0x6f) [0x19996f] -> dovecot/imap(imap_search_args_build+0x91) [0x8066c91] -> dovecot/imap(cmd_search+0xb9) [0x8058219] -> dovecot/imap(command_exec+0x83) [0x805f2b3] -> dovecot/imap [0x805d28f] -> dovecot/imap [0x805d30a] -> dovecot/imap(client_handle_input+0x45) [0x805d515] -> dovecot/imap(client_input+0x71) [0x805da (gdb) bt #0 0x00635402 in __kernel_vsyscall () #1 0x00949d70 in raise () from /lib/i686/nosegneg/libc.so.6 #2 0x0094b751 in abort () from /lib/i686/nosegneg/libc.so.6 #3 0x00224164 in default_fatal_finish (type=<value optimized out>, status=0) at failures.c:201 #4 0x002241ed in i_internal_fatal_handler (ctx=0xbf8627d0, format=0x5b7fac "file %s: line %d (%s): assertion failed: (%s)", args=0xbf8627f4 "ƿ\\") at failures.c:670 #5 0x00223e0b in i_panic (format=0x5b7fac "file %s: line %d (%s): assertion failed: (%s)") at failures.c:275 #6 0x00594c61 in mail_index_map_lookup_seq_range (map=0x89afc50, first_uid=0, last_uid=4294967295, first_seq_r=0xbf8628e4, last_seq_r=0xbf8628e0) at mail-index-map.c:550 #7 0x005a9c2c in view_lookup_seq_range (view=0x89af670, first_uid=0, last_uid=4294967295, first_seq_r=0xbf8628e4, last_seq_r=0xbf8628e0) at mail-index-view.c:252 #8 0x005a963c in mail_index_lookup_seq_range (view=0x89af670, first_uid=0, last_uid=4294967295, first_seq_r=0xbf8628e4, last_seq_r=0xbf8628e0) at mail-index-view.c:513 #9 0x0050a39f in mailbox_get_seq_range (box=0x8995418, uid1=0, uid2=4294967295, seq1_r=0xbf8628e4, seq2_r=0xbf8628e0) at mailbox-get.c:11 #10 0x004f97af in mailbox_uidset_change (args=0x89b4d40, arg=0x89b4e10, change_uidsets=true, search_saved_uidset=0x8991e7c) at mail-search.c:45 #11 mail_search_arg_init (args=0x89b4d40, arg=0x89b4e10, change_uidsets=true, search_saved_uidset=0x8991e7c) at mail-search.c:72 #12 0x004f996f in mail_search_args_init (args=0x89b4d40, box=0x8995418, change_uidsets=true, search_saved_uidset=0x8991e7c) at mail-search.c:142 #13 0x08066c91 in imap_search_args_build (cmd=0x8992800, args=0x8995030, charset=0x8070f89 "UTF-8", search_args_r=0xbf862998) at imap-search-args.c:71 #14 0x08058219 in cmd_search (cmd=0x8992800) at cmd-search.c:42 #15 0x0805f2b3 in command_exec (cmd=0x8992800) at imap-commands.c:181 #16 0x0805d28f in client_command_input (cmd=0x8992800) at imap-client.c:986 #17 0x0805d30a in client_command_input (cmd=0x8992800) at imap-client.c:1046 #18 0x0805d515 in client_handle_next_command (client=0x8991db8) at imap-client.c:1088 #19 client_handle_input (client=0x8991db8) at imap-client.c:1100 #20 0x0805dae1 in client_input (client=0x8991db8) at imap-client.c:1147 #21 0x0023aa88 in io_loop_call_io (io=0x8992778) at ioloop.c:599 #22 0x0023c62f in io_loop_handler_run_internal (ioloop=0x8979498) at ioloop-epoll.c:222 #23 0x0023ac0f in io_loop_handler_run (ioloop=0x8979498) at ioloop.c:648 #24 0x0023aef8 in io_loop_run (ioloop=0x8979498) at ioloop.c:623 #25 0x001bb49d in master_service_run (service=0x89793c8, callback=0x806af90 <client_connected>) at master-service.c:641 #26 0x0806b927 in main (argc=Cannot access memory at address 0x0 ) at main.c:460 (gdb) Panicing stopped when all index files where deleted. Cheers, Toni Mattila

2 9

doveadm-server uses 100% cpu and never finishes, dsync backup also never finishes
by Patrick van Zweden 09 Dec '16

09 Dec '16

Hi Guys, I have a quite interesting problem. I have two servers that replicate to each-other. Suddenly one of the accounts is starting to eat a very large amount of disk space on, what basically is the replica for this account. doveadm-server seems to hang and keeps on filling the disk. I came across this message in the logs: Dec 8 07:36:40 <server> dovecot: dsync-server(<account>): Fatal: pool_system_malloc(6291528): Out of memory Dec 8 07:36:40 <server> dovecot: dsync-server(<account>): Fatal: master: service(doveadm): child 883 returned error 83 (Out of memory (service doveadm { vsz_limit=256 MB }, you may need to increase it) - set DEBUG_OUTOFMEM=1 environment to get core dump) I’ve increased the vsz_limit to 5G so it has stopped complaining. Only… the process never seems to finish. I’ve tried to export the mailbox using dsync: dsync -Dv backup -u 'xxxxx' sdbox:/tmp/patrick_export/ However this process never finishes either. It looks like it stays in one of the mailboxes and keeps on trying to copy messages. Format of the mailbox is sdbox Version of dovecot on all servers: 2.2.9 Any pointers for solving this problem? Kind regards, Patrick -- Patrick van Zweden

1 1

doveadm
by Eric Broch 09 Dec '16

09 Dec '16

Hello list, I'm interested in setting up dovecot replication but when I run the command doveadm user '*', which is necessary as indicated here: http://wiki2.dovecot.org/Replication, I get the following output: Error: User listing returned failure Fatal: user listing failed It also indicates the following on the wiki2: "Make sure that user listing is configured for your userdb, this is required by replication to find the list of users that are periodically replicated" I use a vpopmail backup so the question is how do I "Make sure that user listing is configured for...userdb"? This is my userdb settings for vpopmail: userdb { args = cache_key=%u quota_template=quota_rule=*:backend=%q driver = vpopmail } Thank-you Eric

1 1

Correct user for replication
by John Fawcett 08 Dec '16

08 Dec '16

Hi I've set up replication with the settings below. With these settings, aggregator runs as user dovecot and replicator as user root. Are those the recommended settings or should I change them, in particular for replicator which is running as a privileged user? service aggregator { fifo_listener replication-notify-fifo { mode = 0666 user = vmail } unix_listener replication-notify { mode = 0666 user = vmail } } service replicator { unix_listener replicator-doveadm { mode = 0660 group = mail } } service doveadm { inet_listener { port = 999 ssl = yes } } ssl_client_ca_file = /etc/pki/tls/cert.pem doveadm_password = secret plugin { mail_replica = tcps:hostname.domainname.tld:999 } thanks John

1 0

Migrate from dovecot 1.1 to 2.2 Maildir to 2.2 mdbox
by Daniel Betz 08 Dec '16

08 Dec '16

Hello list, im am trying to migrate customer mails via dsync from an old dovecot 1.1 setup to an new installed dovecot 2.2.25 setup with mdbox. Upgrading the old dovecot 1.1 to 2.2 with Maildir isnt an problem and the replication to the new setup works well too. The only problem now is, that the POP3 UIDL are completely wrong on the target setup. Im using for Maildir pop3_uidl_format = %f With mdbox i cant use it anymore. But what do i need for mdbox ? Or is there an way to migrate the POP3 uidl list to the mdbox ? I could live with it, when i were able to mark the mails older 14 days as read. Is there an way to do this on many mailboxes ? I have read in Release News from 2.2.26 that there are some fixes with POP3 UIDL .. what is it in detail and could it help me ? Hop you can point me to the right direction. Regards, Daniel Freundliche Grüße, Daniel Betz System Design Engineer / Senior Systemadministration ___________________________________ domainfactory GmbH Oskar-Messter-Str. 33 85737 Ismaning Germany Telefon: +49 (0)89 / 55266-364 Telefax: +49 (0)89 / 55266-222 E-Mail: dbetz(a)df.eu<mailto:dbetz@df.eu> Internet: www.df.eu<http://www.df.eu/> Registergericht: Amtsgericht München HRB-Nummer 150294, Geschäftsführer: Tobias Mohr, Stephan Wolfram

2 1

Dovecot: Mails flagged as read get flagged as unread
by plataleas 07 Dec '16

07 Dec '16

Hi all We experience some unexpected behavior with dovecot. It happens that emails marked as read get marked as unread (MUA is Thunderbird on port 143). Unfortunately this happens randomly, reproducing this issue is difficult. We could not find any pattern, it happens rarely. We are running dovecot version 2.2.24 on Debian Jessie (backports repository). /root@dovecot01:~# dovecot --version// //2.2.24 (a82c823)/ Our Setup: /ha-proxy01 -> dovecot-proxy01 (proxy=yes) -> dovecot01 (proxy=no) * IP is used for multiple services (ports). We use the haproxy to send traffic on different ports to different servers. / Below the configuration (IMAPC is active for migration purposes). Do you have any recommendations where we could focus for troubleshooting? I found some posts about mbox_lazy_writes causing similar issues. However we use mdbox in our setup. If we enable rawlog for what log patterns should we search? Your Inputs are highly appreciated! Thanks and Regards plataleas *----- haproxy configuration ------ *frontend frontend_mail.company.org-143 bind 10.100.189.34:143 mode tcp default_backend backend_mail.company.org-143 backend backend_mail.company.org-143 mode tcp balance source server dovecot-proxy01.company.org dovecot-proxy01.company.org:10143 check send-proxy-v2 server dovecot-proxy02.company.org dovecot-proxy02.company.org:10143 check send-proxy-v2 backup *----- config Dovecot Proxy -----* /root@dovecot-proxy01:~# dovecot -n # 2.2.24 (a82c823): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.13 (7b14904) # OS: Linux 3.16.0-4-amd64 x86_64 Debian 8.5 auth_username_chars = abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@* default_client_limit = 5000 default_process_limit = 500 disable_plaintext_auth = no haproxy_trusted_networks = 10.10.189.28,10.10.189.29 imap_capability = IMAP4rev1 UIDPLUS CHILDREN NAMESPACE THREAD=ORDEREDSUBJECT THREAD=REFERENCES SORT QUOTA IDLE ACL ACL2=UNION STARTTLS listen = 10.10.189.25 mail_location = mdbox:%h/mdbox mail_max_userip_connections = 0 mail_plugins = zlib mdbox_rotate_size = 10 M 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 = INBOX. separator = . } passdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } plugin { gzip_save_level = 6 pop3_migration_mailbox = POP3-MIGRATION-NS/INBOX sieve = file:~/sieve;active=~/.dovecot.sieve zlib_save = gz } protocols = imap pop3 lmtp service imap-login { inet_listener imap_haproxy { address = 10.10.189.25 haproxy = yes port = 10143 } inet_listener imaps_haproxy { address = 10.10.189.25 haproxy = yes port = 10993 ssl = yes } } service lmtp { inet_listener lmtp { address = 10.10.189.25 port = 24 } } service pop3-login { inet_listener pop3_haproxy { address = 10.10.189.25 haproxy = yes port = 10110 } inet_listener pop3s_haproxy { address = 10.10.189.25 haproxy = yes port = 10995 ssl = yes } } ssl_ca = </etc/pki/tls/certs/wildcard_company.org-bundle.pem ssl_cert = </etc/pki/tls/certs/wildcard_company.org-cert.pem ssl_key = </etc/pki/tls/private/wildcard_company.org.key userdb { args = /etc/dovecot/dovecot-ldap.conf.ext default_fields = home=/home/virtual/%u driver = ldap } verbose_proctitle = yes protocol imap { mail_plugins = zlib imap_zlib } / /root@dovecot-proxy01:~# grep -v '^ *$#.*$\?$' /etc/dovecot/dovecot-ldap.conf.ext// //uris = ldaps://ldap.comany.org// //dn = 'cn=ldap-reader,ou=customers,dc=company,dc=org'// //dnpass = upser_password// //sasl_bind = no// //tls = no// //auth_bind = yes// //base = ou=customers,dc=company,dc=org// //user_attrs = =home=/data/vmails/%Ld/%Ln,=uid=10000,=gid=10000,mailquota=quota_rule=*:storage=%$G// //user_filter = (&(uid=%u)(pfAccountStatus=active))// //pass_attrs = uid=user,userPassword=password,pfmailHost=host,=proxy_maybe=yes// //pass_filter = (&(uid=%u)(pfAccountStatus=active))// / *-------------config Dovecot LDA---------* * * /root@dovecot01:~# dovecot -n / # 2.2.24 (a82c823): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.13 (7b14904) # OS: Linux 3.16.0-4-amd64 x86_64 Debian 8.5 auth_username_chars = abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@* default_client_limit = 5000 default_process_limit = 500 disable_plaintext_auth = no haproxy_trusted_networks = 10.10.189.28,10.10.189.29 imapc_features = rfc822.size imapc_host = mail-direct.company.org imapc_list_prefix = INBOX imapc_user = %u listen = 10.10.189.42 mail_location = mdbox:%h/mdbox mail_max_userip_connections = 0 mail_plugins = zlib mail_prefetch_count = 20 mdbox_rotate_size = 10 M namespace { hidden = yes list = no location = pop3c: prefix = POP3-MIGRATION-NS/ } 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 = INBOX. separator = . } passdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } plugin { gzip_save_level = 6 pop3_migration_ignore_missing_uidls = yes pop3_migration_mailbox = POP3-MIGRATION-NS/INBOX sieve = file:~/sieve;active=~/.dovecot.sieve zlib_save = gz } pop3c_host = mail-direct.company.org pop3c_password = # hidden, use -P to show it protocols = imap pop3 lmtp service imap-login { inet_listener imap_haproxy { address = 10.10.189.42 haproxy = yes port = 10143 } inet_listener imaps_haproxy { address = 10.10.189.42 haproxy = yes port = 10993 ssl = yes } } service lmtp { inet_listener lmtp { address = 10.10.189.42 port = 24 } } service pop3-login { inet_listener pop3_haproxy { address = 10.10.189.42 haproxy = yes port = 10110 } inet_listener pop3s_haproxy { address = 10.10.189.42 haproxy = yes port = 10995 ssl = yes } } ssl_ca = </etc/ssl/certs/certs/wildcard_company.org-bundle.pem ssl_cert = </etc/ssl/certs/wildcard.company.org.crt ssl_key = </etc/ssl/private/wildcard.company.org.key userdb { args = /etc/dovecot/dovecot-ldap.conf.ext default_fields = home=/home/virtual/%u driver = ldap } verbose_proctitle = yes protocol imap { mail_plugins = zlib imap_zlib } protocol doveadm { mail_plugins = zlib pop3_migration }

4 5

Dovecot migration via dsync : mail_location problem (INBOX) ?
by Cédric ML 07 Dec '16

07 Dec '16

Hello, I'm trying to migrate mail accounts from an old dovecot 1.0.15 to a new dovecot 2.2.26. I've set up a master-user on old dovecot, and I run dsync on new server, like this : # doveadm -D -o mail_fsync=never sync -R -u user(a)domain.tld imapc: my user(a)domain.tld looks like this (on the new server): # doveadm user user(a)domain.tld field value uid 2000 gid 2000 home /home/vmail/domain.tld/user mail maildir:/home/vmail/domain.tld/user/mail quota_rule *:bytes=0 User mail folder on the old server looks like this : # ls -la /home/virtual/user(a)domain.tld/ total 64 drwx------ 11 vmail vmail 4096 2016-12-06 16:26 ./ drwxrwx--- 234 vmail vmail 12288 2016-12-05 12:57 ../ drwx------ 2 vmail vmail 89 2016-12-06 15:29 cur/ -rw------- 1 vmail vmail 352 2016-12-06 16:26 dovecot.index -rw------- 1 vmail vmail 19456 2016-12-06 16:26 dovecot.index.cache -rw------- 1 vmail vmail 2220 2016-12-06 16:26 dovecot.index.log -rw------- 1 vmail vmail 10 2016-12-06 15:14 dovecot-keywords -rw------- 1 vmail vmail 170 2016-12-06 16:21 dovecot-uidlist drwx------ 5 vmail vmail 148 2016-12-05 16:52 .Drafts/ drwx------ 5 vmail vmail 148 2016-12-05 16:52 .FauxIndesirable/ drwx------ 5 vmail vmail 148 2016-12-05 16:52 .Indesirable/ -rw-r----- 1 vmail vmail 293 2016-12-06 15:29 maildirsize drwx------ 2 vmail vmail 85 2016-12-06 15:29 new/ drwx------ 5 vmail vmail 148 2016-12-05 16:52 .Sent/ drwx------ 5 vmail vmail 148 2016-12-05 16:52 .Spam/ drwx------ 2 vmail vmail 6 2016-12-07 10:46 tmp/ drwx------ 5 vmail vmail 4096 2016-12-06 15:36 .Trash/ When I run the sync, with "doveadm -D -o mail_fsync=never sync -R -u user(a)domain.tld imapc:" on the new server, the new server synchronises the mail from the new server, and the file system on the new server looks like this : root@dovecot-pa3:/home/vmail/domain.tld# ls -la /home/vmail/domain.tld/user/mail/ total 84 drwx------ 15 mailbox mailbox 4096 Dec 7 11:02 . drwx------ 3 mailbox mailbox 4096 Dec 7 11:02 .. drwx------ 2 mailbox mailbox 4096 Dec 7 11:02 cur -rw------- 1 mailbox mailbox 556 Dec 7 11:02 dovecot.index.log -rw------- 1 mailbox mailbox 96 Dec 7 11:02 dovecot.mailbox.log -rw------- 1 mailbox mailbox 51 Dec 7 11:02 dovecot-uidlist -rw------- 1 mailbox mailbox 8 Dec 7 11:02 dovecot-uidvalidity -r--r--r-- 1 mailbox mailbox 0 Dec 7 11:02 dovecot-uidvalidity.5847de3b drwx------ 5 mailbox mailbox 4096 Dec 7 11:02 .Drafts drwx------ 5 mailbox mailbox 4096 Dec 7 11:02 .INBOX.Drafts drwx------ 5 mailbox mailbox 4096 Dec 7 11:02 .INBOX.FauxIndesirable drwx------ 5 mailbox mailbox 4096 Dec 7 11:02 .INBOX.Indesirable drwx------ 5 mailbox mailbox 4096 Dec 7 11:02 .INBOX.Sent drwx------ 5 mailbox mailbox 4096 Dec 7 11:02 .INBOX.Spam drwx------ 5 mailbox mailbox 4096 Dec 7 11:02 .INBOX.Trash drwx------ 5 mailbox mailbox 4096 Dec 7 11:02 .Junk -rw------- 1 mailbox mailbox 17 Dec 7 11:02 maildirsize drwx------ 2 mailbox mailbox 4096 Dec 7 11:02 new drwx------ 5 mailbox mailbox 4096 Dec 7 11:02 .Sent -rw------- 1 mailbox mailbox 23 Dec 7 11:02 subscriptions drwx------ 2 mailbox mailbox 4096 Dec 7 11:02 tmp drwx------ 5 mailbox mailbox 4096 Dec 7 11:02 .Trash But dovecot is condigured to have ".Trash", ".Junk" etc... folders, not ".INBOX.Trash" I've try multiple things : - use namespaces for compatibility and add "-n <namespace>" in sync command, without success - modify the mail_location for the user, tried to add LAYOUT=fs, INBOX=<folder>, ... without success. Can anybody help me with that please ? Here's the #doveconf -n output : ------------------------------------------------------- # 2.2.devel (f7f4b65): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.devel (53a3582) # OS: Linux 3.16.0-4-amd64 x86_64 Debian 8.6 auth_mechanisms = plain login doveadm_password = # hidden, use -P to show it doveadm_port = 12345 imapc_features = rfc822.size fetch-headers imapc_host = oldserver.domain.tld imapc_master_user = masteruser imapc_password = # hidden, use -P to show it imapc_user = %u mail_plugins = " quota notify replication" mail_prefetch_count = 20 managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date index ihave duplicate mime foreverypart extracttext mbox_write_locks = fcntl dotlock namespace compat { hidden = no list = no location = maildir:~/mail/ prefix = INBOX separator = / } namespace inbox { hidden = no inbox = yes list = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk { auto = subscribe special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox Trash { auto = subscribe special_use = \Trash } prefix = separator = / } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { mail_replica = tcp:192.168.159.9:12345 quota = maildir:User quota quota_grace = 10%% quota_rule = Trash:storage=+100M quota_status_nouser = DUNNO quota_status_overquota = 552 5.2.2 Boite de messagerie pleine. quota_status_success = DUNNO quota_warning = storage=95%% quota-warning 95 %u quota_warning2 = storage=85%% quota-warning 85 %u sieve = file:~/sieve;active=~/.dovecot.sieve sieve_before = /var/lib/dovecot/sieve/ sieve_before2 = /home/vmail/%d/%n/sieve/Vacation.sieve sieve_default = /var/lib/dovecot/sieve/dovecot.sieve sieve_default_name = default sieve_global = /var/lib/dovecot/sieve/ } protocols = " imap sieve pop3 sieve" service aggregator { fifo_listener replication-notify-fifo { mode = 0666 user = mailbox } unix_listener replication-notify { mode = 0666 user = mailbox } } service auth { inet_listener { port = 12346 } unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-userdb { group = mailbox user = mailbox } } service config { unix_listener config { user = mailbox } } service doveadm { inet_listener { port = 12345 } user = mailbox } service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 } } service managesieve-login { inet_listener sieve { port = 4190 } process_min_avail = 1 service_count = 1 vsz_limit = 64 M } service quota-warning { executable = script /usr/local/bin/quota-warning.sh unix_listener quota-warning { user = mailbox } user = mailbox } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { group = mailbox mode = 0660 } } ssl = required ssl_cert = </etc/ssl/certs/crt-and-intermediate.pem ssl_key = # hidden, use -P to show it userdb { driver = prefetch } userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } protocol lmtp { postmaster_address = postmaster(a)domain.tld } protocol lda { mail_plugins = " quota notify replication sieve" postmaster_address = postmaster(a)domain.tld } protocol imap { mail_plugins = " quota notify replication imap_quota" } ------------------------------------------------------- Best regards, Cédric

2 2

Re: v2.2.27 released --- libressl
by Ruga 07 Dec '16

07 Dec '16

>openssl version Libressl 2.4.4 Patch for dovecot: perl -i -ple 's/^(#if OPENSSL_VERSION_NUMBER < 0x10100000L\s*)$/$1 || defined (LIBRESSL_VERSION_NUMBER)/' ./src/lib-dcrypt/dcrypt-openssl.c; perl -i -ple 's/^(#if OPENSSL_VERSION_NUMBER < 0x10100000L\s*)$/$1 || defined (LIBRESSL_VERSION_NUMBER)/' ./src/lib-ssl-iostream/dovecot-openssl-common.c; perl -i -ple 's/^(#if OPENSSL_VERSION_NUMBER >= 0x10100000L\s*)$/$1 && !defined (LIBRESSL_VERSION_NUMBER)/' ./src/lib-dcrypt/dcrypt-openssl.c; perl -i -ple 's/^(#if OPENSSL_VERSION_NUMBER >= 0x10100000L\s*)$/$1 && !defined (LIBRESSL_VERSION_NUMBER)/' ./src/lib-ssl-iostream/dovecot-openssl-common.c; Both configuration and compilation are OK. The test fails as follows: [...] test_load_v1_public_key .............................................. : ok Panic: file randgen.c: line 21 (random_fill): assertion failed: (init_refcount > 0) Error: Raw backtrace: 2 libdcrypt_openssl.so 0x0000000103413d24 default_fatal_finish + 36 -> 3 libdcrypt_openssl.so 0x0000000103413afd default_fatal_handler + 61 -> 4 libdcrypt_openssl.so 0x0000000103414069 i_panic + 169 -> 5 libdcrypt_openssl.so 0x000000010344110c random_fill + 220 -> 6 libdcrypt_openssl.so 0x000000010340a63d dcrypt_openssl_store_private_key + 1037 -> 7 test-crypto 0x0000000103387f54 test_load_v2_key + 580 -> 8 test-crypto 0x000000010338990e test_run + 142 -> 9 test-crypto 0x0000000103386921 main + 81 -> 10 libdyld.dylib 0x00007fff9da95255 start + 1 /bin/sh: line 1: 56954 Abort trap: 6 ./$bin make[2]: *** [check-test] Error 1 make[1]: *** [check-recursive] Error 1 make: *** [check-recursive] Error 1 -------- Original Message -------- Subject: v2.2.27 released Local Time: 3 December 2016 6:48 PM UTC Time: 3 December 2016 17:48 From: tss(a)iki.fi To: dovecot-news(a)dovecot.org, Dovecot Mailing List <dovecot(a)dovecot.org> https://dovecot.org/releases/2.2/dovecot-2.2.27.tar.gz https://dovecot.org/releases/2.2/dovecot-2.2.27.tar.gz.sig Note that the download URLs are now https with a certificate from Let's Encrypt. * dovecot.list.index.log rotation sizes/times were changed so that the .log file stays smaller and .log.2 is deleted sooner. + Added mail_crypt plugin that allows encryption of stored emails. See http://wiki2.dovecot.org/Plugins/MailCrypt + stats: Global stats can be sent to Carbon server by setting stats_carbon_server=ip:port + imap/pop3 proxy: If passdb returns proxy_not_trusted, don't send ID/XCLIENT + Added generic hash modifier for %variables: %{<hash algorithm>;rounds=<n>,truncate=<bits>,salt=s>:field} Hash algorithm is any of the supported ones, e.g. md5, sha1, sha256. Also "pkcs5" is supported using SHA256. For example: %{sha256:user} or %{md5;truncate=32:user}. + Added support for SHA3-256 and SHA3-512 hashes. + config: Support DNS wildcards in local_name, e.g. local_name *.example.com { .. } matches anything.example.com, but not multiple.anything.example.com. + config: Support multiple names in local_name, e.g. local_name "1.example.com 2.example.com" { .. } - Fixed crash in auth process when auth-policy was configured and authentication was aborted/failed without a username set. - director: If two users had different tags but the same hash, the users may have been redirected to the wrong tag's hosts. - Index files may have been thought incorrectly lost, causing "Missing middle file seq=.." to be logged and index rebuild. This happened more easily with IMAP hibernation enabled. - Various fixes to restoring state correctly in un-hibernation. - dovecot.index files were commonly 4 bytes per email too large. This is because 3 bytes per email were being wasted that could have been used for IMAP keywords. - Various fixes to handle dovecot.list.index corruption better. - lib-fts: Fixed assert-crash in address tokenizer with specific input. - Fixed assert-crash in HTML to text parsing with specific input (e.g. for FTS indexing or snippet generation) - doveadm sync -1: Fixed handling mailbox GUID conflicts. - sdbox, mdbox: Perform full index rebuild if corruption is detected inside lib-index, which runs index fsck. - quota: Don't skip quota checks when moving mails between different quota roots. - search: Multiple sequence sets or UID sets in search parameters weren't handled correctly. They were incorrectly merged together.

2 2

Segmentation fault in imap_bodystructure_is_plain_7bit
by Mihai Craiu 06 Dec '16

06 Dec '16

Hi, I have a lot of errors like this in my log: Fatal: master: service(imap): child 26049 killed with signal 11 (core dumped) Dovecot 2.2.18 build from sources ./configure --prefix=/opt/dovecot2 --with-mysql --with-sqlite --with-solr --with-ssl --disable-rpath --disable-static. Debian Wheezy 3.2.63-2 x86_64. Filesystem is ZFS. All the core files are similar: $ gdb /opt/dovecot2/libexec/dovecot/imap core GNU gdb (GDB) 7.4.1-debian Copyright (C) 2012 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". For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>... Reading symbols from /opt/dovecot2/libexec/dovecot/imap...done. [New LWP 11635] warning: Can't read pathname for load map: Input/output error. [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `/opt/dovecot2/libexec/dovecot/imap imap-postlogin'. Program terminated with signal 11, Segmentation fault. #0 imap_bodystructure_is_plain_7bit (part=part@entry=0x234cd50) at imap-bodystructure.c:458 458 if (data->content_subtype != NULL && (gdb) bt #0 imap_bodystructure_is_plain_7bit (part=part@entry=0x234cd50) at imap-bodystructure.c:458 #1 0x00007f920a0fbfaf in index_mail_body_parsed_cache_flags (mail=0x234be60) at index-mail.c:587 #2 index_mail_parse_body_finish (mail=mail@entry=0x234be60, field=field@entry=MAIL_CACHE_IMAP_BODYSTRUCTURE, success=success@entry=true) at index-mail.c:1007 #3 0x00007f920a0fc369 in index_mail_parse_body (mail=mail@entry=0x234be60, field=field@entry=MAIL_CACHE_IMAP_BODYSTRUCTURE) at index-mail.c:1081 #4 0x00007f920a0fc498 in index_mail_parse_bodystructure (mail=mail@entry=0x234be60, field=field@entry=MAIL_CACHE_IMAP_BODYSTRUCTURE) at index-mail.c:1222 #5 0x00007f920a0fcf1c in index_mail_get_special (_mail=_mail@entry=0x234be60, field=field@entry=MAIL_FETCH_IMAP_BODYSTRUCTURE, value_r=value_r@entry=0x7ffc1518fde8) at index-mail.c:1379 #6 0x00007f920a0b29cd in dbox_mail_get_special (_mail=_mail@entry=0x234be60, field=field@entry=MAIL_FETCH_IMAP_BODYSTRUCTURE, value_r=value_r@entry=0x7ffc1518fde8) at dbox-mail.c:229 #7 0x00007f920a0a83f0 in mdbox_mail_get_special (_mail=0x234be60, field=MAIL_FETCH_IMAP_BODYSTRUCTURE, value_r=0x7ffc1518fde8) at mdbox-mail.c:213 #8 0x00007f920a08f96d in mail_get_special (mail=<optimized out>, field=field@entry=MAIL_FETCH_IMAP_BODYSTRUCTURE, value_r=value_r@entry=0x7ffc1518fde8) at mail.c:317 #9 0x0000000000419a6a in fetch_bodystructure (ctx=0x232bbd8, mail=<optimized out>, context=<optimized out>) at imap-fetch.c:690 #10 0x0000000000419f9f in imap_fetch_more_int (ctx=ctx@entry=0x232bbd8, cancel=false) at imap-fetch.c:506 #11 0x000000000041af07 in imap_fetch_more (ctx=0x232bbd8, cmd=cmd@entry=0x232ba00) at imap-fetch.c:558 #12 0x000000000040f0c9 in cmd_fetch (cmd=0x232ba00) at cmd-fetch.c:286 #13 0x0000000000418aec in command_exec (cmd=cmd@entry=0x232ba00) at imap-commands.c:167 #14 0x0000000000417ad0 in client_command_input (cmd=cmd@entry=0x232ba00) at imap-client.c:814 #15 0x0000000000417b64 in client_command_input (cmd=0x232ba00) at imap-client.c:874 #16 0x0000000000417e45 in client_handle_next_command (remove_io_r=<synthetic pointer>, client=0x232ade0) at imap-client.c:912 #17 client_handle_input (client=client@entry=0x232ade0) at imap-client.c:924 #18 0x0000000000418212 in client_input (client=0x232ade0) at imap-client.c:966 #19 0x00007f9209df134b in io_loop_call_io (io=0x232b8f0) at ioloop.c:501 #20 0x00007f9209df1e5b in io_loop_handler_run_internal (ioloop=ioloop@entry=0x22ec790) at ioloop-epoll.c:220 #21 0x00007f9209df13d9 in io_loop_handler_run (ioloop=ioloop@entry=0x22ec790) at ioloop.c:548 #22 0x00007f9209df1458 in io_loop_run (ioloop=0x22ec790) at ioloop.c:525 #23 0x00007f9209d92993 in master_service_run (service=0x22ec620, callback=callback@entry=0x421140 <client_connected>) at master-service.c:581 #24 0x000000000040c60b in main (argc=2, argv=0x22ec390) at main.c:431 (gdb) q Thanks.

1 0

Panic: file dsync-mailbox-tree-sync.c: line 576 (node_mailbox_trees_cmp): assertion failed: (ret != 0)
by Gilles Chauvin 06 Dec '16

06 Dec '16

Hi, Here is a crash that's happening using the latest Dovecot version (v2.2.27 on CentOS7 x86_64): We are using replication. Judging by the second server's logs, I believe this has something to do with the fact that we're using the lazy_expunge plugin. Every night after midnight, we purge the lazy_expunge namespace by running a command similar to following one on the main server (server01 in the logs below): # doveadm expunge -A MAILBOX 'EXPUNGED/*' SAVEDBEFORE "$(date +'%F')" The lazy_expunge namespace is configured as follows: namespace expunged { disabled = no hidden = yes ignore_on_failure = no inbox = no list = no location = sdbox:/srv/mail/expunged/%1n/%n:SUBSCRIPTIONS=subscriptions-expunged order = 0 prefix = EXPUNGED/ separator = / subscriptions = no type = private } plugin { lazy_expunge = EXPUNGED/ } First server's logs: 2016-12-06T13:09:31.212620+01:00 server01 dovecot: dsync-server(user01): Panic: file dsync-mailbox-tree-sync.c: line 576 (node_mailbox_trees_cmp): assertion failed: (ret != 0) 2016-12-06T13:09:31.213473+01:00 server01 dovecot: dsync-server(user01): Error: Raw backtrace: /usr/local/lib/dovecot/libdovecot.so.0(+0x92d70) [0x7f57cc18ad70] -> /usr/local/lib/dovecot/libdovecot.so.0(+0x92e4e) [0x7f57cc18ae4e] -> /usr/local/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f57cc1264e0] -> dovecot/doveadm-server [10.0.0.2 user01 recv_mailbox_tree_deletes]() [0x447584] -> dovecot/doveadm-server [10.0.0.2 user01 recv_mailbox_tree_deletes]() [0x447a57] -> dovecot/doveadm-server [10.0.0.2 user01 recv_mailbox_tree_deletes]() [0x447849] -> dovecot/doveadm-server [10.0.0.2 user01 recv_mailbox_tree_deletes]() [0x447849] -> dovecot/doveadm-server [10.0.0.2 user01 recv_mailbox_tree_deletes](dsync_mailbox_trees_sync_init+0x1f9) [0x447cc9] -> dovecot/doveadm-server [10.0.0.2 user01 recv_mailbox_tree_deletes](dsync_brain_recv_mailbox_tree_deletes+0x207) [0x43a477] -> dovecot/doveadm-server [10.0.0.2 user01 recv_mailbox_tree_deletes](dsync_brain_run+0x5fe) [0x436e4e] -> dovecot/doveadm-server [10.0.0.2 user01 recv_mailbox_tree_deletes]() [0x437280] -> dovecot/doveadm-server [10.0.0.2 user01 recv_mailbox_tree_deletes]() [0x44c5af] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x52) [0x7f57cc19e4d2] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0xe7) [0x7f57cc19fa07] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x3c) [0x7f57cc19e56c] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7f57cc19e728] -> dovecot/doveadm-server [10.0.0.2 user01 recv_mailbox_tree_deletes]() [0x41faae] -> dovecot/doveadm-server [10.0.0.2 user01 recv_mailbox_tree_deletes]() [0x421316] -> dovecot/doveadm-server [10.0.0.2 user01 recv_mailbox_tree_deletes]() [0x433b64] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x52) [0x7f57cc19e4d2] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0xe7) [0x7f57cc19fa07] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x3c) [0x7f57cc19e56c] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7f57cc19e728] -> /usr/local/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f57cc12c513] -> dovecot/doveadm-server [10.0.0.2 user01 recv_mailbox_tree_deletes](main+0x197) [0x413b57] -> /lib64/libc.so.6(__libc_start_main+0xf5) [0x7f57cbd57b15] -> dovecot/doveadm-server [10.0.0.2 user01 recv_mailbox_tree_deletes]() [0x413bf5] 2016-12-06T13:09:31.214076+01:00 server01 dovecot: dsync-server(user01): Fatal: master: service(doveadm): child 6837 killed with signal 6 (core dumps disabled) 2016-12-06T13:11:42.880516+01:00 server01 dovecot: dsync-local(user01): Error: read(server02.localdomain) failed: EOF (last sent=mailbox_delete, last recv=mailbox_tree_node) Second server's logs: 2016-12-06T12:09:36.220591+01:00 server02 dovecot: doveadm(user01): Error: Duplicate mailbox GUID eab35824e49b4658840001001776124f for mailboxes EXPUNGED/Trash/C2i - Coordination-temp-ac1fea3af7e1f2c29ce1c62442a06272/Demissions C2i and EXPUNGED/Trash/C2i - Coordination/Demissions C2i - giving a new GUID c4ffaf08709c465813ae0000a26dfa6e to EXPUNGED/Trash/C2i - Coordination-temp-ac1fea3af7e1f2c29ce1c62442a06272/Demissions C2i 2016-12-06T12:09:36.220859+01:00 server02 dovecot: doveadm(user01): Error: Duplicate mailbox GUID 2ab10a2bee9b4658840001001776124f for mailboxes EXPUNGED/Trash/C2i - Coordination-temp-ac1fea3af7e1f2c29ce1c62442a06272/2014-2015 and EXPUNGED/Trash/C2i - Coordination/2014-2015 - giving a new GUID c6ffaf08709c465813ae0000a26dfa6e to EXPUNGED/Trash/C2i - Coordination-temp-ac1fea3af7e1f2c29ce1c62442a06272/2014-2015 2016-12-06T12:09:36.221091+01:00 server02 dovecot: doveadm(user01): Error: Duplicate mailbox GUID eeb35824e49b4658840001001776124f for mailboxes EXPUNGED/Trash/C2i - Coordination-temp-ac1fea3af7e1f2c29ce1c62442a06272/2012-2013 and EXPUNGED/Trash/C2i - Coordination/2012-2013 - giving a new GUID c8ffaf08709c465813ae0000a26dfa6e to EXPUNGED/Trash/C2i - Coordination-temp-ac1fea3af7e1f2c29ce1c62442a06272/2012-2013 2016-12-06T12:09:36.284224+01:00 server02 dovecot: dsync-local(user01): Error: Mailbox EXPUNGED/Trash/C2i - Coordination/2008-2009/Formation FC sync: mailbox_rename failed: Can't rename mailboxes to/from expunge namespace. 2016-12-06T12:09:45.469706+01:00 server02 dovecot: dsync-server(user01): Error: Duplicate mailbox GUID eab35824e49b4658840001001776124f for mailboxes EXPUNGED/Trash/C2i - Coordination-temp-ac1fea3af7e1f2c29ce1c62442a06272/Demissions C2i and EXPUNGED/Trash/C2i - Coordination/Demissions C2i - giving a new GUID 671ae30f799c465882b00000a26dfa6e to EXPUNGED/Trash/C2i - Coordination-temp-ac1fea3af7e1f2c29ce1c62442a06272/Demissions C2i 2016-12-06T12:09:45.470389+01:00 server02 dovecot: dsync-server(user01): Error: Duplicate mailbox GUID 2ab10a2bee9b4658840001001776124f for mailboxes EXPUNGED/Trash/C2i - Coordination-temp-ac1fea3af7e1f2c29ce1c62442a06272/2014-2015 and EXPUNGED/Trash/C2i - Coordination/2014-2015 - giving a new GUID 691ae30f799c465882b00000a26dfa6e to EXPUNGED/Trash/C2i - Coordination-temp-ac1fea3af7e1f2c29ce1c62442a06272/2014-2015 2016-12-06T12:09:45.471214+01:00 server02 dovecot: dsync-server(user01): Error: Duplicate mailbox GUID eeb35824e49b4658840001001776124f for mailboxes EXPUNGED/Trash/C2i - Coordination-temp-ac1fea3af7e1f2c29ce1c62442a06272/2012-2013 and EXPUNGED/Trash/C2i - Coordination/2012-2013 - giving a new GUID 6b1ae30f799c465882b00000a26dfa6e to EXPUNGED/Trash/C2i - Coordination-temp-ac1fea3af7e1f2c29ce1c62442a06272/2012-2013 2016-12-06T12:09:45.485663+01:00 server02 dovecot: dsync-server(user01): Error: Mailbox EXPUNGED/Trash/C2i - Coordination/2008-2009/Formation FC sync: mailbox_rename failed: Can't rename mailboxes to/from expunge namespace. [... Previous line repeated numerous times ...] 2016-12-06T12:14:32.583382+01:00 server02 dovecot: dsync-server(user01): Error: Mailbox EXPUNGED/Trash/C2i - Coordination/2008-2009/Formation FC sync: mailbox_rename failed: Can't rename mailboxes to/from expunge namespace. 2016-12-06T12:14:36.778278+01:00 server02 dovecot: dsync-local(user01): Error: Mailbox EXPUNGED/Trash/C2i - Coordination/2008-2009/Formation FC sync: mailbox_rename failed: Can't rename mailboxes to/from expunge namespace. [... / ...] 2016-12-06T12:19:30.677497+01:00 sauto dovecot: dsync-server(user01): Panic: file dsync-mailbox-tree-sync.c: line 576 (node_mailbox_trees_cmp): assertion failed: (ret != 0) 2016-12-06T12:19:30.678991+01:00 sauto dovecot: dsync-server(user01): Error: Raw backtrace: /usr/local/lib/dovecot/libdovecot.so.0(+0x92d70) [0x7f40f3cd1d70] -> /usr/local/lib/dovecot/libdovecot.so.0(+0x92e4e) [0x7f40f3cd1e4e] -> /usr/local/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f40f3c6d4e0] -> dovecot/doveadm-server [10.0.0.1 user01 recv_mailbox_tree_deletes]() [0x447584] -> dovecot/doveadm-server [10.0.0.1 user01 recv_mailbox_tree_deletes]() [0x447a57] -> dovecot/doveadm-server [10.0.0.1 user01 recv_mailbox_tree_deletes]() [0x447849] -> dovecot/doveadm-server [10.0.0.1 user01 recv_mailbox_tree_deletes]() [0x447849] -> dovecot/doveadm-server [10.0.0.1 user01 recv_mailbox_tree_deletes](dsync_mailbox_trees_sync_init+0x1f9) [0x447cc9] -> dovecot/doveadm-server [10.0.0.1 user01 recv_mailbox_tree_deletes](dsync_brain_recv_mailbox_tree_deletes+0x207) [0x43a477] -> dovecot/doveadm-server [10.0.0.1 user01 recv_mailbox_tree_deletes](dsync_brain_run+0x5fe) [0x436e4e] -> dovecot/doveadm-server [10.0.0.1 user01 recv_mailbox_tree_deletes]() [0x437280] -> dovecot/doveadm-server [10.0.0.1 user01 recv_mailbox_tree_deletes]() [0x44c5af] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x52) [0x7f40f3ce54d2] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0xe7) [0x7f40f3ce6a07] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x3c) [0x7f40f3ce556c] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7f40f3ce5728] -> dovecot/doveadm-server [10.0.0.1 user01 recv_mailbox_tree_deletes]() [0x41faae] -> dovecot/doveadm-server [10.0.0.1 user01 recv_mailbox_tree_deletes]() [0x421316] -> dovecot/doveadm-server [10.0.0.1 user01 recv_mailbox_tree_deletes]() [0x433b64] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x52) [0x7f40f3ce54d2] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0xe7) [0x7f40f3ce6a07] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x3c) [0x7f40f3ce556c] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7f40f3ce5728] -> /usr/local/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f40f3c73513] -> dovecot/doveadm-server [10.0.0.1 user01 recv_mailbox_tree_deletes](main+0x197) [0x413b57] -> /lib64/libc.so.6(__libc_start_main+0xf5) [0x7f40f389eb15] -> dovecot/doveadm-server [10.0.0.1 user01 recv_mailbox_tree_deletes]() [0x413bf5] 2016-12-06T12:19:30.689038+01:00 sauto dovecot: dsync-server(user01): Fatal: master: service(doveadm): child 96318 killed with signal 6 (core dumps disabled) 2016-12-06T12:19:30.749074+01:00 sauto dovecot: dsync-local(user01): Error: read(server01.localdomain) failed: EOF (last sent=mailbox_delete, last recv=mailbox_tree_node) Thanks, Kind regards, Gilles.

1 0

LMTP delivery honours .forward by default?
by MRob 06 Dec '16

06 Dec '16

I was under the impression that Dovecot does not look at .forward by default, since of course, Sieve is where that kind of logic should go. However, I'm seeing a .forward file being honoured by the LMTP delivery agent. Is this to be expected?

2 5

COPY vs APPEND for imapsieve?
by MRob 06 Dec '16

06 Dec '16

The examples on the imapsieve documentation page use COPY but not APPEND to watch messages coming into a folder. Are there not circumstances that a client would APPEND a message to a folder instead of COPY? Is APPEND only used by most clients for adding a sent message to the sent folder? I'm not familiar enough with IMAP clients to know if by leaving off APPEND I am safe or I am at risk to miss some actions I shouldn't.

2 2

imapsieve environment variables missing?
by MRob 06 Dec '16

06 Dec '16

RFC6785 says imap.user and imap.email environment variables should be made available but I can't access them no matter what I try. Are they not implemented because vnd.dovecot.environment already provides the username? (which does work for me) If imap.user and imap.email are there, can you provide an example how to access them so I can see what I did wrong?

2 13

Re: v2.2.27 released
by Joseph Tam 05 Dec '16

05 Dec '16

Timo announced: > https://dovecot.org/releases/2.2/dovecot-2.2.27.tar.gz > https://dovecot.org/releases/2.2/dovecot-2.2.27.tar.gz.sig > > Note that the download URLs are now https with a certificate from Let's Encrypt. wget complained about ERROR: certificate common name `wiki.dovecot.org' doesn't match requested host name `dovecot.org'. and indeed, the certificate CN and download URL is mismatched. The nice thing about Let's Encrypt is that it's easy to (re)generate the certitcate with SANs to get rid of this mismatch. Browser didn't complain though. Joseph Tam <jtam.home(a)gmail.com>

2 2

v2.2.27 released
by Timo Sirainen 05 Dec '16

05 Dec '16

https://dovecot.org/releases/2.2/dovecot-2.2.27.tar.gz https://dovecot.org/releases/2.2/dovecot-2.2.27.tar.gz.sig Note that the download URLs are now https with a certificate from Let's Encrypt. * dovecot.list.index.log rotation sizes/times were changed so that the .log file stays smaller and .log.2 is deleted sooner. + Added mail_crypt plugin that allows encryption of stored emails. See http://wiki2.dovecot.org/Plugins/MailCrypt + stats: Global stats can be sent to Carbon server by setting stats_carbon_server=ip:port + imap/pop3 proxy: If passdb returns proxy_not_trusted, don't send ID/XCLIENT + Added generic hash modifier for %variables: %{<hash algorithm>;rounds=<n>,truncate=<bits>,salt=s>:field} Hash algorithm is any of the supported ones, e.g. md5, sha1, sha256. Also "pkcs5" is supported using SHA256. For example: %{sha256:user} or %{md5;truncate=32:user}. + Added support for SHA3-256 and SHA3-512 hashes. + config: Support DNS wildcards in local_name, e.g. local_name *.example.com { .. } matches anything.example.com, but not multiple.anything.example.com. + config: Support multiple names in local_name, e.g. local_name "1.example.com 2.example.com" { .. } - Fixed crash in auth process when auth-policy was configured and authentication was aborted/failed without a username set. - director: If two users had different tags but the same hash, the users may have been redirected to the wrong tag's hosts. - Index files may have been thought incorrectly lost, causing "Missing middle file seq=.." to be logged and index rebuild. This happened more easily with IMAP hibernation enabled. - Various fixes to restoring state correctly in un-hibernation. - dovecot.index files were commonly 4 bytes per email too large. This is because 3 bytes per email were being wasted that could have been used for IMAP keywords. - Various fixes to handle dovecot.list.index corruption better. - lib-fts: Fixed assert-crash in address tokenizer with specific input. - Fixed assert-crash in HTML to text parsing with specific input (e.g. for FTS indexing or snippet generation) - doveadm sync -1: Fixed handling mailbox GUID conflicts. - sdbox, mdbox: Perform full index rebuild if corruption is detected inside lib-index, which runs index fsck. - quota: Don't skip quota checks when moving mails between different quota roots. - search: Multiple sequence sets or UID sets in search parameters weren't handled correctly. They were incorrectly merged together.

7 11

doveadm edit headers?
by MRob 05 Dec '16

05 Dec '16

Hello, is there a way to edit a message header using doveadm? I see how I can fetch the things I need, but even if I can't edit in place; if I extract the full message, edit it, there doesn't seem to be a way to append it back again?

3 5

Virtual mailboxes, please help
by Peter Hodur 05 Dec '16

05 Dec '16

Hi, I'm trying to setup virtual mailboxes. My setup: - migrated from Courier, so: separator = . prefix = INBOX. inbox = yes In doc i have read, thant i need to create separate namespace. namespace { prefix = virtual/ separator = / location = virtual:~/Maildir/virtual So i need to change / with . (Dot) in prefix and separator? Do i need to append LAYOUT=maildir++ to location? Where must location point? To the same directory where mail_location? Or do i need to create separate hierarchy for virtual mailboxes? Thanks for any answer ;) Peter ml.

3 3

Mail marked read upon download
by Curtis Vaughan 05 Dec '16

05 Dec '16

Just set up a new server with postfix and dovecot. I don't know why, but as soon as mail is accessed it is marked read. I'll see emails momentarily marked unread, but then switch to read later although I haven't opened them. This has never been an issue before. Any ideas why? Thanks. Curtis

2 1

CVE-2016-8562 in dovecot
by Aki Tuomi 05 Dec '16

05 Dec '16

We are sorry to report that we have a bug in dovecot, which merits a CVE. See details below. If you haven't configured any auth_policy_* settings you are ok. This is fixed with https://git.dovecot.net/dovecot/core/commit/c3d3faa4f72a676e183f34be960cff1… and https://git.dovecot.net/dovecot/core/commit/99abb1302ae693ccdfe0d57351fd42c… Important vulnerability in Dovecot (CVE-2016-8562) CVSS score: 7.4 (CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:N/A:H) Affected version(s): 2.2.25.1 up to 2.2.26.1 Fixed in: 2.2.27.1rc1 Short summary: Dovecot auth component can be crashed by remote user when auth-policy component is activated. If auth-policy component has been activated in Dovecot, then remote user can use SASL authentication to crash auth component. Workaround is to disable auth-policy component until fix is in place. This can be done by commenting out all auth_policy_* settings. Aki Tuomi Dovecot oy

6 12

SAML | Input buffer full (no auth attempts in 0 secs)
by mj 04 Dec '16

04 Dec '16

Hi, In my journey to enable SAML auth for our webmail (sogo.nu) I have created a password-less dovecot imap listener on 127.0.0.1/32, so that once a user is SAML authenticated for the SOGo webmail, SOGo can connect to dovecot on 127.0.0.1:143 with something like "01 LOGIN username randompassword". Watching this (tcpflow) as it happens,i can see the following auth attempt coming from sogo: > 1 login "username" "eF7VVm1vmzAQ/iuI77wY8kJQEy1t2inSukpJVU37UhlzJN7AjmyzZPv1Owfgkdjfkgkfldlkfjg9jQNMvaNZMm7RvifC/Pc/ecfaFpkcdTrUEZLoW1K3Kh4+rn2C6ViCXVXMeCFqBjw+Ll9PZDHLh+TFsPu3ERmozttTGb2PO22627DV2pVl7g+8T7dPthydZQUIcLbahgYFsPoDQmHNsYzbbms7E9nz32B8kIEuY7oxFETi8bpE6U9MAZjiiLUiABzdB1rnUJ8zqSQX+fDBwSOH54T6I49GPiu2Q4+GxPLmps9Wk1qUrTWBtP3QIUN24pShfS0qOlWXsKaF5or7ZceId++yDLMvkCzDQhPyId85l1I1VBsYLf8URcUjPHUyerj8al0BtgPOOQ2pM1lBsuvjbp9jGbBE26KykyXjlWnbkFs5bpy11hRZwAVaBa8CcCzaih1kdp7sSdmmYG1C8U9mM/2lNoLbDaDYeK55ZALVcyPOJwefde1qwFjuYrIYWzkdpgp8QC9EYKDfdybD/eDC9JQAbX08tr0huSYBDOZv3+VUD6/evQJ4HtTRo2TtR9ZGqYQopSXvGjK0yXgETDiZnoAL0InHTAm+jTMkXwDBCFUZxVeY4s9VzhWL3CSgGGpkh8A6+N22I6mWc/hk8Au8xmLZaGGiiwL9YUx1e8LgZrCbrS21yksBvbgzDssWGUOQFLe04vooDwoscmtAwGpIBBEHYzlCdAcswsGsFcPjrKsddsIBs8uK6YDGrzuEWOdBAx8ZTgi7aCdsTW4cMtLQY7FBSGuioOTZYlcRQPzy16X5FuvOYxaSbgTsOK2daNwKNL8+z4edokyJkthqoMdaW05DzQvwcLtGJvvGzy+w+" Note, the actual 'password' is even longer. This connection attempt is causing dovecot to throw the following error: > Dec 02 22:34:33 imap-login: Info: Disconnected: Input buffer full (no > auth attempts in 0 secs): user=<>, rip=x.y.z.32, lip=x.y.z.68, > session=<d+o3tLNCaOvAV48g> and > BYE Input buffer full, aborting So this doesn't work. :-( The question: is there a way to make this work? (make the input buffer larger, for example..?) Or any other ideas to make this work? Thanks in advance, MJ

2 2

move IMAP folder
by James 04 Dec '16

04 Dec '16

I am trying to move an IMAP folder from Thunderbird and nothing happens. What /var/log file should I look in?

1 0

RE: First steps in Dovecot; IMAP not working
by Richard 04 Dec '16

04 Dec '16

> Date: Tuesday, October 18, 2016 13:12:39 +0200 > From: Moi <anic297(a)mac.com> > > Thank you. It worked and I now have several log files to check. > > In the meantime, I've tried once again to send a message to > "mailtest" from an outside address; this time, I got an error reply: > > This report relates to a message you sent with the following header > fields: > > Message-id: <00e201d2290f$67da8c70$378fa550$(a)mac.com> > Date: Tue, 18 Oct 2016 09:15:21 +0200 > From: Moi > To: 'Mail Test' <mailtest(a)barbu.sytes.net> > Subject: Test > > Your message cannot be delivered to the following recipients: > > Recipient address: mailtest(a)barbu.sytes.net > Reason: Illegal host/domain name found > <end of reply> > > Yet another area with a problem; at least this is now a valid > reason for it to not work. > Is this a misconfiguration of my DNS server? Assuming that "barbu.sytes.net" is the intended hostname (not something made up to obscure the real name), there is an MX-record for that that points to "mail.barbu.sytes.net", but there is no A-record for the "mail." hostname. There is an A-record for "mail.sytes.net", in case that is what you were intending, in which case you'd need to fix the MX on "barbu.sytes.net".

2 1

Show pigeonhole version?
by MRob 04 Dec '16

04 Dec '16

How can I query the current pigeonhole version from a running instance to verify it is what I expect? Possible to get `dovecot --version` to show things like that?

2 1

No stats under FreeBSD 10.3
by Ruud Boon 04 Dec '16

04 Dec '16

HI, I’m currently testing the stats module of Dovecot (2.2.26.0 (23d1de6)) Looks like there no statistics under FreeBSD. Server isn’t busy yet but got at least a few connection open. Added mail_plugins = $mail_plugins stats plugin { stats_refresh = 30 secs stats_track_cmds = yes } doveadm stats dump global reset_timestamp last_update num_logins num_cmds num_connected_sessions auth_successes auth_master_successes auth_failures auth_db_tempfails auth_cache_hits auth_cache_misses user_cpu sys_cpu clock_time min_faults maj_faults vol_cs invol_cs disk_input disk_output read_count read_bytes write_count write_bytes mail_lookup_path mail_lookup_attr mail_read_count mail_read_bytes mail_cache_hits 1478031539 0.000000 0 0 0 0 0 0 0 0 0 0.0 0.0 0.0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Cheers, Ruud

4 5

CentOS 7
by Eric Broch 04 Dec '16

04 Dec '16

Hello List, I'm building a dovecot-2.2.27 RPM for CentOS 7 and running into some issues The dovecot.spec (http://pkgs.fedoraproject.org/cgit/rpms/dovecot.git/tree/dovecot.spec) file runs 'autoreconf -I . -fiv' for aarch64 support just before the %configure option but is failing This worked fine on <= 2.2.26.0 when there was an m4/*.m4 directory (with *.m4 in it) in the sources. Is there something I should be aware of? Was the m4 directory removed for a reason? As a workaround I created the m4 directory and everything worked out, but is this the best solution? Eric

2 2

Too many references: cannot splice
by Sebastian Köhler 02 Dec '16

02 Dec '16

Hello, multiple times per day one of our Dovecot servers has the problem that it suddenly refuses to accept new connections and then floods the logs with these messages: Dec 2 12:43:06 alfa3201 dovecot: pop3-login: Error: fd_send(pop3, 18) failed: Too many references: cannot splice Dec 2 12:43:07 alfa3201 dovecot: pop3-login: Error: fd_send(pop3, 18) failed: Too many references: cannot splice Dec 2 12:43:07 alfa3201 dovecot: imap-login: Error: fd_send(imap, 16) failed: Too many references: cannot splice Dec 2 12:43:07 alfa3201 dovecot: imap-login: Error: fd_send(imap, 16) failed: Too many references: cannot splice We have to either do a restart of the server or a doveadm kick on all users to make it reachable again. On my search for a solution I found a similar report from March[1] however without a fix. [1] http://dovecot.org/pipermail/dovecot/2016-March/103514.html dovecot -n # 2.2.24 (a82c823): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.13 (7b14904) # OS: Linux 4.4.17-040417-generic x86_64 Debian 8.6 auth_mechanisms = plain login debug_log_path = /var/log/dovecot-debug.log default_client_limit = 8003 default_process_limit = 2000 default_vsz_limit = 512 M disable_plaintext_auth = no listen = * login_greeting = [CENSORED] - ready. mail_location = maildir:~/Maildir:CONTROL=/opt/dovecot/control/%n-control:INDEX=/opt/dovecot/index/%n mail_plugins = " stats quota" namespace inbox { inbox = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Spam { auto = subscribe special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { auto = subscribe special_use = \Trash } prefix = INBOX. separator = . } passdb { args = dovecot-%s driver = pam } plugin { quota = fs:%n(soft quota) sieve = ~/.dovecot.sieve sieve_dir = ~/sieve stats_command_min_time = 1 mins stats_domain_min_time = 12 hours stats_ip_min_time = 12 hours stats_memory_limit = 16 M stats_refresh = 30 secs stats_session_min_time = 15 mins stats_track_cmds = no stats_user_min_time = 24 hours } protocols = " imap pop3" service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } } service imap-login { inet_listener imaps { ssl = yes } } service imap-postlogin { executable = script-login /etc/dovecot/post-login/expire.sh } service imap { executable = imap imap-postlogin } service pop3-login { inet_listener pop3 { port = 110 } inet_listener pop3s { port = 995 ssl = yes } } service pop3-postlogin { executable = script-login /etc/dovecot/post-login/expire.sh } service pop3 { executable = pop3 pop3-postlogin } service quota-status { executable = quota-status -p postfix unix_listener /var/spool/postfix/private/quota { group = postfix mode = 0660 user = postfix } } service stats { fifo_listener stats-mail { mode = 0666 user = dovecot } } ssl_ca = </etc/ssl.crt/ca-admin.crt ssl_cert = </etc/ssl.crt/admin.crt ssl_key = </etc/ssl.key/admin.key ssl_protocols = !SSLv2 !SSLv3 userdb { driver = passwd } protocol imap { imap_capability = +XLIST +NAMESPACE METADATA QUOTA imap_idle_notify_interval = 1 mins mail_max_userip_connections = 500 mail_plugins = " stats quota imap_quota imap_stats" } protocol pop3 { mail_max_userip_connections = 500 mail_plugins = " stats quota" pop3_client_workarounds = outlook-no-nuls oe-ns-eoh }

2 2

Defining INDEX target to other location than maildir seems to have no effect.
by Julian Sternberg 02 Dec '16

02 Dec '16

Dovecot Version 2.2.13 Linux Distribution: Debian Jessie CPU Architecture: x64 Filesystem: GlusterFS/NFS, XFS for Base System/Index Files. Two Dovecot/Postfix nodes accessing same GlusterFS/NFS Maildir. Regardless what i choose in mail_location (:INDEX=MEMORY or :INDEX=/var/indexes/%d/%n) all Mailbox index files will still get created within the users mail_location maildir: ~/Maildir My mail_location Maildir directory is shared on GlusterFS mount so i need to get index files away from this share due locking mechanism and faster caching. The weird is, if i set INDEX to /var/indexes, the index files getting created sometimes but then not updated frequently and exist parallel on Maildir which are mostly newer than on /var/indexes. If you delete the dovecot.index* files from Maildir, they will get recreated immediatly on Imap access but not on the alternative set INDEX location, they are getting recreated within Maildir again. Here is doveconf -n Output: # 2.2.13: /etc/dovecot/dovecot.conf # OS: Linux 3.16.0-4-amd64 x86_64 Debian 8.6 auth_mechanisms = plain login cram-md5 disable_plaintext_auth = no first_valid_uid = 2000 hostname = censored.hostname.com last_valid_uid = 2000 lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes listen = * lock_method = dotlock mail_fsync = always mail_gid = 2000 mail_home = /storage/vmail/%d/%n mail_location = maildir:~/Maildir:LAYOUT=fs:INDEX=MEMORY mail_nfs_storage = yes mail_privileged_group = vmail mail_temp_dir = /var/tmp mail_uid = 2000 maildir_very_dirty_syncs = yes 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 mmap_disable = yes namespace inbox { inbox = yes location = mailbox Archive { auto = no special_use = \Archive } mailbox Archives { auto = no special_use = \Archive } mailbox "Deleted Items" { auto = no special_use = \Trash } mailbox "Deleted Messages" { auto = no special_use = \Trash } mailbox Drafts { auto = no special_use = \Drafts } mailbox Sent { auto = subscribe special_use = \Sent } mailbox "Sent Items" { auto = no special_use = \Sent } mailbox "Sent Messages" { auto = no special_use = \Sent } mailbox Spam { auto = create special_use = \Junk } mailbox Trash { auto = subscribe special_use = \Trash } mailbox virtual/All { auto = no special_use = \All } prefix = separator = / type = private } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { quota = maildir:User quota quota_rule = *:storage=1G quota_rule2 = Trash:storage=+100M quota_rule3 = Sent:storage=+100M quota_warning = storage=95%% quota-warning 95 %u quota_warning2 = storage=80%% quota-warning 80 %u sieve = /storage/vmail/%d/%n/sieve/dovecot.sieve sieve_before = /storage/vmail/sieve/dovecot.sieve sieve_dir = /storage/vmail/%d/%n/sieve sieve_global = /storage/vmail/sieve } postmaster_address = postmaster(a)censored.hostname.com protocols = " imap lmtp sieve pop3" quota_full_tempfail = yes service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-userdb { group = vmail mode = 0666 user = vmail } } service imap-login { inet_listener imaps { port = 993 ssl = yes } service_count = 0 } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0666 user = postfix } } service managesieve-login { inet_listener sieve { port = 4190 } service_count = 1 } service pop3-login { inet_listener pop3 { port = 110 } inet_listener pop3s { port = 995 ssl = yes } } service quota-warning { executable = script /usr/local/bin/quota-warning.sh unix_listener quota-warning { user = vmail } user = vmail } ssl = required ssl_ca = </etc/ssl/censored.hostname.com/ssl-bundle-mail.crt ssl_cert = </etc/ssl/censored.hostname.com/censored_hostname.com.crt ssl_cipher_list = ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:AES:CAMELLIA:DES-CBC3-SHA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!MD5:!PSK:!aECDH:!EDH-DSS-DES-CBC3-SHA:!EDH-RSA-DES-CBC3-SHA:!KRB5-DES-CBC3-SHA ssl_key = </etc/ssl/censored.hostname.com/censored.hostname.com.key ssl_protocols = !SSLv2 !SSLv3 ssl_require_crl = no userdb { args = uid=2000 gid=2000 home=/storage/vmail/%d/%n allow_all_users=yes driver = static } protocol lmtp { mail_plugins = " quota sieve" } protocol lda { mail_plugins = " sieve quota" } protocol imap { imap_client_workarounds = tb-extra-mailbox-sep mail_plugins = " quota imap_quota" } protocol sieve { mail_max_userip_connections = 10 } protocol pop3 { mail_plugins = " quota" pop3_client_workarounds = outlook-no-nuls oe-ns-eoh pop3_uidl_format = %08Xu%08Xv }

3 3

maildir-size-fix.pl - The file command can wrongly detect gzipped mails as being Minix filesystems
by Rarylson Freitas 02 Dec '16

02 Dec '16

Hi, Some days ago, I have used the maildir-size-fix.pl script (cited in this mail thread: http://www.dovecot.org/list/dovecot/2013-January/087942.html, in available here: http://dovecot.org/tools/maildir-size-fix.pl) This is a very good script and helped me a lot! However, some compressed mails where misdetected as non-compressed mail. So I discovered that some versions of the file command (some old versions) can wrongly detect gzipped files as being Minix filesystems. Actually, the error was occurring in about 1 gzipped mail for each 60000 or 100000 mails. I reported this file command bug here: https://bugs.launchpad.net/ubuntu/+source/file/+bug/1646233. But I think it's worth to make a small improvement in maildir-size-fix.pl, making it more error prone. What do you, guys, think about this? This is the patch I'm proposing: ``` --- maildir-size-fix.pl.orig 2016-12-01 14:41:30.044689101 -0200 +++ maildir-size-fix.pl 2016-12-01 14:49:42.971197715 -0200 @@ -37,7 +37,10 @@ return $stat[7]; } - my $type=`file "$path"`; + # Detecting all possible types (keep going) since some versions of the file + # command can wrong detect gzip files as Minix filesystems. + # See: https://bugs.launchpad.net/ubuntu/+source/file/+bug/1646233 + my $type=`file -k "$path"`; my $program = ""; if ($type =~ /gzip/) { $program = "gunzip"; ``` -- *Rarylson Freitas*

2 1

Implementing secondary quota w/ "Archive" namespace
by Fred Turner 01 Dec '16

01 Dec '16

Hello folks— My first post, so please be gentle… :-) I have a client email server using SSDs for primary user mailboxes, but since the number of users keeps growing and they all seem to be very reluctant to delete anything, I’ve implemented an “Archive” namespace that stores its mailboxes on a larger HD RAID. The idea is that, as the users approach their quota, they move messages to the Archive mailboxes to alleviate space in their primary Inbox namespace. This secondary storage part is working well, but I’m having trouble w/ getting the quotas to work right. Here are the basics of the setup: Mac Pro Server 2012 Mac OS X Server 10.6.8 Dovecot 1.1.20apple0.5 Here is how I’ve configured my namespaces (during testing): namespace private { separator = / prefix = inbox = yes } namespace private { separator = / prefix = testArchive/ location = maildir:/Shared Items/MailArchive/%u subscriptions = yes } My quota research has led me to try this: quota = maildir:User quota:ns= quota2 = maildir:ns=testArchive/ quota2_rule = *:storage=20G The first line is already in the default config, with the exception of the added “:ns=“ at the end. The 2nd line in the examples I saw had a middle component w/ the quota name, but when I tried that, like so: quota2 = maildir:Archive quota:ns=testArchive/ my server fails and shows this in the logs: > Fatal: IMAP(*): Quota root test backend maildir: Unknown parameter: ns=testArchive/ Any idea why it doesn’t like that? Also, do I need to add a quota_rule for the primary quota? It does not have one normally in the Mac OS X Server config… Thus far in my testing, I’ve been able to get the 2 quotas to show up in Roundcube and Mac Mail.app. It’s a little messy…the first shows up as “User quota”, the 2nd as “ns=testArchive/“, presumably because I cannot leave the description field in there. Unfortunately, both quotas show the same amount of space in use. If I drop the primary quota to a mere 4MB for testing, and if I have 5.2MB of messages in a testArchive folder, the space used for “User quota” shows as 5.2MB (>100%), as does the “ns=testArchive/“ quota (which is 20GB). In actuality, the Inbox namespace is really only using a few KB— the 5.2MB is in the testArchive namespace. This means that I cannot move messages between either set of namespaces, and new messages are not delivered. So, the quota trouble here is negating the whole point of having the Archive namespace... Is there a way to get Dovecot to “see” the 2 quotas as unique/discrete? It seems like I’m close to accomplishing what I want, but just can’t quite get it to cooperate. And that “Unknown parameter” error is bewildering. Any ideas? Thx, Fred P.S. I can add my Dovecot config to the thread upon request…didn’t want to make this initial message even longer.

4 16

AW: User unknown in local recipient table
by Kalle Erlacher 01 Dec '16

01 Dec '16

Hallo Liste, hallo Ralf, danke schon mal. Ja die Whitespaces sind beim Rauslöschen entstanden. Ich verstand das so, dass das nun durch die address_verify_map erledigt würde. Muss ich dann entsprechend einfach auf die verweisen? Ich versuchte gerade die address_verify_map = btree:$data_directory/verify_cache auf local_recipient_maps = btree:$data_directory/verify_cache verweisen zu lassen. Leider ohne Erfolg. Bisher ist verify_cache nämlich leider noch unbefüllt. Entsprechend bekomme ich folgende Fehler: Dec 1 16:16:29 test-mail postfix/smtpd[5550]: warning: btree:/var/lib/postfix/verify_cache is unavailable. open database /var/lib/postfix/verify_cache.db: No such file or directory Dec 1 16:16:29 test-mail postfix/smtpd[5550]: warning: btree:/var/lib/postfix/verify_cache lookup error for "juergen @domain.org" Dec 1 16:16:29 test-mail postfix/smtpd[5550]: NOQUEUE: reject: RCPT from localhost[127.0.0.1]: 451 4.3.0 <juergen.pittorf(a)doag.org>: Temporary lookup failure; from=<kalle(a)domain.org> to=<juergen(a)domain.org> proto=ESMTP helo=<test-mail.domain.org> Auch ein plumpes touch auf /var/lib/postfix/verify_cache.db bringt danach den selben Fehler. Liebe Grüße Kalle -----Ursprüngliche Nachricht----- Von: Dovecot [mailto:dovecot-bounces@listen.jpberlin.de] Im Auftrag von Ralf Hildebrandt Gesendet: Donnerstag, 1. Dezember 2016 15:38 An: dovecot(a)listen.jpberlin.de Betreff: Re: User unknown in local recipient table * Kalle Erlacher <kalle.erlacher(a)doag.org>: > Dec 1 14:38:44 test-mail postfix/smtpd[3366]: NOQUEUE: reject: RCPT > from > localhost[127.0.0.1]: 550 5.1.1 <juergen(a)domain.org>: Recipient > address > rejected: User unknown in local recipient table; > from=<kalle(a)domain.org> to=<juergen @domain.org> proto=ESMTP > helo=<test-mail.domain.org> ... local recipient table = domain ist in mydestination > mydestination = test-mail.domain.org mail. domain.org domain.org > localhost Ich hoffe das Leerzeichen zwischen "mail." und "domain.org" ist nicht wirklich da Explizit ist da nix gesetzt, laut "postconf -n", ergo defaults für local_recipient_maps: local_recipient_maps = proxy:unix:passwd.byname $alias_maps Aber die Domain domain.org soll doch sicher im dovecot landen, oder? -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebrandt(a)charite.de | http://www.charite.de

3 3

Re: dovecot Digest, Vol 163, Issue 34
by J. Nick Koston 01 Dec '16

01 Dec '16

Aki, Multiple local_names would be ideal to accommodate certificates that have multiple names. The way I’m reading the code it looks like its having to pay for the memory for every name on the certificate because a unique CTX is being created for each name even if they are all on a single certificate. This would be a big memory win for anyone using a certificate with multiple names on it. Thanks -Nick cPanel Inc >> > > Dear Aki et al., > > How straightforward would it be to implement the following or similar syntax: > > local_name foo.tld www.foo.tld mail.foo.tld bar.tld { > ... > } > > ?? > > Thank you! > > -FG > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > dovecot mailing list > dovecot(a)dovecot.org > http://dovecot.org/cgi-bin/mailman/listinfo/dovecot > > ------------------------------ > > End of dovecot Digest, Vol 163, Issue 34 > ****************************************

2 3

use IMAPSIEVE to update database with last_read date
by KT Walrus 30 Nov '16

30 Nov '16

Just noticed the Dovecot support IMAPSIEVE extension… Could I use this extension to update an external database with the date that the user last read the message? My app sends certain “notification” messages to the user’s dovecot mail address. The user reads the messages in their dovecot mailboxes only using IMAP. I want to update my app’s database to record this read time for all “notification” messages sent by the app. Seems to me I could write a short sieve script to send a “notify” message to an app specific address that my app “watches” and updates the appropriate database record with the last_read time. Is this workable for production deploy? Or, is there a better way for a sender to be notified when the recipient actually reads the message? The sender will be my app and the recipient is a dovecot mailbox accessed by IMAP. Kevin

2 3

Sieve script won't compile. Compiler output isn't helpful.
by Steven Mainor 30 Nov '16

30 Nov '16

Hello! I hope you will forgive my ignorance but I have a problem I have been trying to solve for a week and I'm not sure where else to turn. I'm trying to write a sieve script to sort all of my mail. I was writing this script to replace the one I am currently using but I can't seem to get it to compile. I don't know a lot about sieve or really scripting of any kind and I just can't figure out what I'm doing wrong. The compiler just puts out a bunch of output that doesn't make sense. like "unexpected character" when I know the character works there because I am already running a script with some of the same lines. I'm attaching the script with some names and addresses changed and the sieve output to this email. I would greatly appreciate any help anyone could offer.

5 8

Quota Clone not tracking unlimited quota
by Prakash Autade 30 Nov '16

30 Nov '16

We are configuring 'Count quota' with 'Quota Clone Plugin' Everything is working perfectly when we set limit in quota_rule(quota_rule = *:bytes=500M). In case of unlimited quota(quota_rule = *:bytes=0) - Count quota is updating values * - Quota Clone plugin is not updating values in redis.* We have configured dovecot as mail_plugins = $mail_plugins quota quota_clone mail_log notify mailbox_list_index = yes plugin { quota = count:User quota quota_vsizes = yes quota_rule = *:bytes=0 quota_clone_dict = redis:host=127.0.0.1:port=6379 } -- Sincerely, Prakash P. Autade.

1 0

Dovecot seems to open extra namespaces
by Thorsten Hater 30 Nov '16

30 Nov '16

Dear all, I am slightly confused by the following log entries ...: imap(...): Debug: Namespace inbox: type=private, prefix=INBOX., sep=., inbox=yes, hidden=no, list=yes, subscriptions=yes location=maildir:~/Maildir ...: imap(...): Debug: maildir++: root=~/Maildir, index=, indexpvt=, control=, inbox=~/Maildir, alt= ...: imap(...): Debug: Namespace : type=private, prefix=, sep=, inbox=no, hidden=yes, list=no, subscriptions=no location=fail::LAYOUT=none ...: imap(...): Debug: none: root=, index=, indexpvt=, control=, inbox=, alt= It seems that Dovecot opens two different namespaces, despite only one being configured in 10-mail.conf/15-mailboxes.conf. Is this normal and intended? Further, what is the purpose of the line starting with 'none'? Best regards, Thorsten Dovecot version: 2.2.26.0 on Debian Jessie

3 4

shared/public mailbox application
by Michael Fox 30 Nov '16

30 Nov '16

I'm new to Dovecot and I need help configuring a shared or public mailbox - I'm not sure which is appropriate. I've read the wiki and Peer's book and neither appears to cover what I'd like to do. So I could use some specific help on how to configure a solution for the following: I'd like to create two real mailboxes, let's call them AAA and BBB. Let's call the domain "mydomain". Anyone user can send mail to them, just like any other address: aaa@mydomain or bbb@mydomain. I'd like all IMAP users in mydomain to be able to read the messages in those mailboxes. I'd like all POP users in mydomain to also see those messages. (But I don't think I need help with the virtual part). I'd like only a few designated IMAP users to be able to delete the messages in those mailboxes, including dummy users AAA and BBB themselves. Ideally, I'd like them to appear in the client under a separate namespace from shared mailboxes. Example: INBOX +--- the normal stuff. Shared +--- user1 +--- user2 Special +--- AAA +--- BBB My confusion: 1) I don't know if this requires a shared namespace or a public namespace. It "feels" like it's "public", since all users would have access. But Peer's book and the wiki describe manually creating folders for public namespaces and controlling the contents with manual file manipulation, which leads me to believe that they can't be used for regular mail (although the book and the wiki never say one way or the other). I don't want to manually control files. I want to send mail to the mailbox and delete (see above) it with a client. 2) There are several examples in Peer's book and the wiki, but none seem to match what I want. (This is the problem with documentation that is predominantly example-based). I guess I need more explanation of the mechanical differences between shared and public and why one would pick one over the other. Can someone help? Please be as specific as you can. Thanks much, Michael

3 8

v2.2.27 release candidate released
by Timo Sirainen 30 Nov '16

30 Nov '16

http://dovecot.org/releases/2.2/rc/dovecot-2.2.27.rc1.tar.gz http://dovecot.org/releases/2.2/rc/dovecot-2.2.27.rc1.tar.gz.sig Most interestingly there's a new mail_crypt plugin. It would be nice if crypto gurus could check through it for any issues. Director's tagging fix was also quite a large change, but the new code is already used in production and appears to be working fine. * dovecot.list.index.log rotation sizes/times were changed so that the .log file stays smaller and .log.2 is deleted sooner. + Added mail_crypt plugin that allows encryption of stored emails. See http://wiki2.dovecot.org/Plugins/MailCrypt + stats: Global stats can be sent to Carbon server by setting stats_carbon_server=ip:port + imap/pop3 proxy: If passdb returns proxy_not_trusted, don't send ID/XCLIENT + Added generic hash modifier for %variables: %{<hash algorithm>;rounds=<n>,truncate=<bits>,salt=s>:field} Hash algorithm is any of the supported ones, e.g. md5, sha1, sha256. Also "pkcs5" is supported using SHA256. For example: %{sha256:user} or %{md5;truncate=32:user}. + Added support for SHA3-256 and SHA3-512 hashes. + config: Support DNS wildcards in local_name, e.g. local_name *.example.com { .. } matches anything.example.com, but not multiple.anything.example.com. - Fixed crash in auth process when auth-policy was configured and authentication was aborted/failed without a username set. - director: If two users had different tags but the same hash, the users may have been redirected to the wrong tag's hosts. - Index files may have been thought incorrectly lost, causing "Missing middle file seq=.." to be logged and index rebuild. This happened more easily with IMAP hibernation enabled. - Various fixes to restoring state correctly in un-hibernation. - dovecot.index files were commonly 4 bytes per email too large. This is because 3 bytes per email were being wasted that could have been used for IMAP keywords. - Various fixes to handle dovecot.list.index corruption better. - lib-fts: Fixed assert-crash in address tokenizer with specific input. - Fixed assert-crash in HTML to text parsing with specific input (e.g. for FTS indexing or snippet generation) - doveadm sync -1: Fixed handling mailbox GUID conflicts. - sdbox, mdbox: Perform full index rebuild if corruption is detected inside lib-index, which runs index fsck.

1 0

auth client limit versus service count of mail processes
by Christian Balzer 29 Nov '16

29 Nov '16

Hello, We've got a pretty substantial dovecot installation (versions 2.1.7 and 2.2.13 on the backends, but tested with 2.2.24 as well) and this is the relevant config snippet from 10-master.conf: --- default_process_limit = 1024 default_client_limit = 16384 [...] service imap { # Most of the memory goes to mmap()ing files. You may need to increase this # limit if you have huge mailboxes. #vsz_limit = $default_vsz_limit vsz_limit = 512M # Max. number of IMAP processes (connections) #process_limit = 1024 process_limit = 524288 } service pop3 { # Max. number of POP3 processes (connections) process_limit = 2048 # Reduce spawns from hell service_count = 100 } --- The above works fine, no warnings. Since 2 of our mailbox servers get a high number (2million/day) of IMAP logins and resulting mail process spawns, I pondered doing the service count bit for IMAP as well. But adding a "service_count = 100" line (any value larger than 1 really) to the imap section we get the dreaded: --- Nov 28 17:05:40 mbx09 dovecot: config: Warning: service auth { client_limit=16384} is lower than required under max. load (528384) --- And that's quite true, once reaching that limit auth will pile up and fail eventually. Clearly the pop3 part with a max of 2048 processes (we see about 300 at peak times) neatly fits into the client limit of 16384. Now setting the client limit in the auth section to the required value of course will do no real good in this scenario, as the fd limit becomes the next bottleneck and I'm not going to raise that to 500k, thank you very much. ^o^ So basically my questions here are: 1. Where's the difference in Dovecot's logic between a mail service that has a service count of 1 versus one with >1? 2. Any way to get the process recycling for IMAP going w/o setting the fd limit to a ridiculous amount? Thanks, Christian -- Christian Balzer Network/Systems Engineer chibi(a)gol.com Global OnLine Japan/Rakuten Communications http://www.gol.com/

2 2

what user to use for SIS deduplication?
by Jesus Cea 28 Nov '16

28 Nov '16

Running Dovecot 2.2.25. I have the following line in my root crontab: "/usr/local/bin/doveadm sis deduplicate /home/dovecot/buzones/attachments /home/dovecot/buzones/attachments/queue" This line is execute each hour and the plan is to deduplicate attachments stored in the SIS system. This works well most of the time, but from time to time cron complains with this error: """ Error: mkdir(/home/dovecot/buzones/attachments/bb/f8/hashes) failed: No such file or directory """ In those situations I just create the directory by hand and set the right permissions. Interestingly, most of the time everything works fine, dovecot creates the needed directories and everything is fine. But I get that error every few days and I must create the directory by hand. Am I running the deduplication process correctly?. It is launched as "root" and I would expect it to "setgid()" to the right user/group (dovemail). Should I run it in the dovemail cron?. I have a faint memory of getting the very same error in that case, a missing hash directory, but I am not sure I am recalling correctly. Any advice?. Thanks. -- 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

1 0

Problem with multiple ldap passdb
by Martin Wheldon 28 Nov '16

28 Nov '16

Hi mailing list, I'm currently running dovecot 2.2.13 from Debian Jessie, all is running fine. However I am attempting to merge 2 LDAP authentication sources. I would like to attempt to authenticate against the first authentication source, if that fails either by password fail or user not found, then attempt the next LDAP server. I've added the a passdb and userdb entry for the new ldap server. As you can see from the log below the user isn't found in the first LDAP query, but is in the second one. However the authentication fails: Nov 22 13:59:38 he01-imap-01 dovecot: auth: Debug: client in: AUTH#0111#011PLAIN#011service=imap#011secured#011session=WTLjLuRB9QBRlIlQ#011lip=51.254.222.112#011rip=81.148.137.80#011lport=143#011rport=56821#011resp=AG1hcnRpbi53aGVsZG9uQGdyXWVuaGlsbHMtaXQuY28udWsAQ3JhY2spbk4wdw== (previous base64 data may contain sensitive data) Nov 22 13:59:38 he01-imap-01 dovecot: auth: Debug: ldap(martin.wheldon at greenhills-it.co.uk,81.148.137.80,<WTLjLuRB9QBRlIlQ>): bind search: base=dc=greenhills-it,dc=co,dc=uk filter=(&(&(ukFirmGhITAccSrvcs=Email)(ukFirmGhITAccLocked=Email-FALSE))(|(uidNumber=martin.wheldon at greenhills-it.co.uk)(mail=martin.wheldon at greenhills-it.co.uk))) Nov 22 13:59:38 he01-imap-01 dovecot: auth: Error: ldap(martin.wheldon at greenhills-it.co.uk,81.148.137.80,<WTLjLuRB9QBRlIlQ>): ldap_search(base=dc=greenhills-it,dc=co,dc=uk filter=(&(&(ukFirmGhITAccSrvcs=Email)(ukFirmGhITAccLocked=Email-FALSE))(|(uidNumber=martin.wheldon at greenhills-it.co.uk)(mail=martin.wheldon at greenhills-it.co.uk)))) failed: No such object Nov 22 13:59:38 he01-imap-01 dovecot: auth: Debug: ldap(martin.wheldon at greenhills-it.co.uk,81.148.137.80,<WTLjLuRB9QBRlIlQ>): bind search: base=dc=greenhills-it,dc=co,dc=uk filter=(|(uid=martin.wheldon at greenhills-it.co.uk)(mail=martin.wheldon at greenhills-it.co.uk)) Nov 22 13:59:38 he01-imap-01 dovecot: auth: Debug: ldap(martin.wheldon at greenhills-it.co.uk,81.148.137.80,<WTLjLuRB9QBRlIlQ>): result: uid=00000001; uid unused Nov 22 13:59:38 he01-imap-01 dovecot: auth: Debug: ldap(martin.wheldon at greenhills-it.co.uk,81.148.137.80,<WTLjLuRB9QBRlIlQ>): username changed martin.wheldon at greenhills-it.co.uk -> 00000001 Nov 22 13:59:38 he01-imap-01 dovecot: auth: Debug: ldap(00000001,81.148.137.80,<WTLjLuRB9QBRlIlQ>): result: uid=00000001 Nov 22 13:59:40 he01-imap-01 dovecot: auth: Debug: client passdb out: FAIL#0111#011user=00000001#011temp#011original_user=martin.wheldon at greenhills-it.co.uk I know that the password was entered correctly because if I disable the new ldap config and login I get authenticated properly. Nov 22 14:00:38 he01-imap-01 dovecot: auth: Debug: auth client connected (pid=2626) Nov 22 14:00:39 he01-imap-01 dovecot: auth: Debug: client in: AUTH#0111#011PLAIN#011service=imap#011secured#011session=ipKBMuRBBQBRlIlQ#011lip=51.254.222.112#011rip=81.148.137.80#011lport=143#011rport=38149#011resp=AG1hcnRpbi53aGVsZG9uQGdyXWVuaGlsbHMtaXQuY28udWsAQ3JhY2spbk4wdw== (previous base64 data may contain sensitive data) Nov 22 14:00:39 he01-imap-01 dovecot: auth: Debug: ldap(martin.wheldon at greenhills-it.co.uk,81.148.137.80,<ipKBMuRBBQBRlIlQ>): bind search: base=dc=greenhills-it,dc=co,dc=uk filter=(|(uid=martin.wheldon at greenhills-it.co.uk)(mail=martin.wheldon at greenhills-it.co.uk)) Nov 22 14:00:39 he01-imap-01 dovecot: auth: Debug: ldap(martin.wheldon at greenhills-it.co.uk,81.148.137.80,<ipKBMuRBBQBRlIlQ>): result: uid=00000001; uid unused Nov 22 14:00:39 he01-imap-01 dovecot: auth: Debug: ldap(martin.wheldon at greenhills-it.co.uk,81.148.137.80,<ipKBMuRBBQBRlIlQ>): username changed martin.wheldon at greenhills-it.co.uk -> 00000001 Nov 22 14:00:39 he01-imap-01 dovecot: auth: Debug: ldap(00000001,81.148.137.80,<ipKBMuRBBQBRlIlQ>): result: uid=00000001 Nov 22 14:00:39 he01-imap-01 dovecot: auth: Debug: client passdb out: OK#0111#011user=00000001#011original_user=martin.wheldon at greenhills-it.co.uk I've done loads of googling and I believe that this is possible so I must either have misread the documentation or am triggering a bug. Neither of which I seem to be able to confirm. Any help would be much appreciated. My broken configuration is below: # 2.2.13: /etc/dovecot/dovecot.conf # OS: Linux 3.16.0-4-amd64 x86_64 Debian 8.6 auth_debug = yes auth_debug_passwords = yes auth_mechanisms = plain login default_vsz_limit = 512 M lmtp_rcpt_check_quota = yes lmtp_save_to_detail_mailbox = yes 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 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-ldap-new.conf.ext driver = ldap } passdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap skip = authenticated } plugin { antispam_backend = pipe antispam_pipe_program = /usr/sbin/sendmail antispam_pipe_program_args = -f;%{auth_user};-r;%{auth_user} antispam_pipe_program_notspam_arg = retrain-as-ham(a)greenhills-it.co.uk antispam_pipe_program_spam_arg = retrain-as-spam(a)greenhills-it.co.uk antispam_spam = Spam antispam_trash = Trash quota = maildir:User quota quota_rule = *:storage=1G quota_rule2 = Trash:ignore quota_rule3 = Spam:ignore sieve = ~/.dovecot.sieve sieve_before = /var/lib/dovecot/sieve/move-spam.sieve sieve_dir = ~/sieve } protocols = " imap lmtp sieve pop3" service imap-login { process_min_avail = 20 service_count = 1 } service imap { process_min_avail = 20 } service lmtp { inet_listener lmtp { address = he01-imap-01.greenhills-it.co.uk 127.0.0.1 port = 2003 } } service pop3 { process_min_avail = 20 } ssl = required ssl_cert = </etc/ssl/certs/combined_2015_greenhills-it.co.uk.cert ssl_cipher_list = ALL:HIGH:!MEDIUM:!LOW:!SSLv2:!EXPORT:!PSK:!DES:!3DES:!MD5:!DES+MD5:!RC4:!SEED+SHA:!aECDH:!EDH-DSS-DES-CBC3-SHA:!EDH-RSA-DES-CBC3-SHA:!KRB5-DES-CBC3-SHA:!eNULL:!aNULL:@STRENGTH ssl_dh_parameters_length = 2048 ssl_key = </etc/ssl/private/stripped.2015.greenhills-it.co.uk.pem ssl_prefer_server_ciphers = yes ssl_protocols = !SSLv2 !SSLv3 userdb { args = /etc/dovecot/dovecot-ldap-new.conf.ext driver = ldap } userdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } protocol lmtp { mail_plugins = " quota sieve" } protocol imap { mail_plugins = " quota imap_quota" } # Working LDAP configuration # /etc/dovecot/dovecot-ldap.conf.ext uris = ldap://he01-auth-01.greenhills-it.co.uk dn = uid=dovecot,ou=people,ou=SRV_Accounts,dc=greenhills-it,dc=co,dc=uk dnpass = VerySecret sasl_bind = no auth_bind = yes ldap_version = 3 base = dc=greenhills-it,dc=co,dc=uk scope = subtree user_attrs = homeDirectory=home,uidNumber=uid,gidNumber=gid,gosaMailQuota=quota_rule=*:storage=%$M user_filter = (|(uid=%u)(mail=%u)(gosaMailAlternateAddress=%u)) pass_attrs = uid=user,userPassword=password pass_filter = (|(uid=%u)(mail=%u)) default_pass_scheme = CRYPT # Non working LDAP configuration # /etc/dovecot/dovecot-ldap-new.conf.ext uris = ldap://dir.greenhills-it.co.uk dn = "cn=dovecot,ou=search accounts,ou=services,dc=greenhills-it,dc=co,dc=uk" dnpass = VerySecret sasl_bind = no tls = yes tls_ca_cert_file = /etc/ssl/certs/GreenhillsCACert.pem tls_require_cert = demand debug_level = -1 auth_bind = yes ldap_version = 3 base = ou=customers,dc=greenhills-it,dc=co,dc=uk scope = subtree user_attrs = homeDirectory=home,uidNumber=uid,gidNumber=gid,ukFirmGhITAccMailQuota=quota_rule=*:storage=%$M user_filter = (&(&(ukFirmGhITAccSrvcs=Email)(ukFirmGhITAccLocked=Email-FALSE))(|(uidNumber=%u)(mail=%u)(ukFirmGhITAccMailAlias=%u))) pass_attrs = uidNumber=user pass_filter = (&(&(ukFirmGhITAccSrvcs=Email)(ukFirmGhITAccLocked=Email-FALSE))(|(uidNumber=%u)(mail=%u))) default_pass_scheme = SSHA Best Regards -- Martin Wheldon Greenhills IT Ltd. Telephone: 01904 238 454 Website: www.greenhills-it.co.uk Greenhills IT Ltd. is a limited company registered in England and Wales. Company Registration No: 06387214 Registered Offices: 2 Greenhills, Claxton, YORK, North Yorkshire, YO60 7SA

1 1

Rebuild UIDs for mdbox
by Darac Marjal 28 Nov '16

28 Nov '16

Hello all, I think I'm hitting an issue with overly large UIDs in one of my mailboxes. I initially thought it was a problem with claws-mail hitting an infinite loop. Claws-mail /seems/ to work fine, until it gets to this one mailbox, wherein the following is logged: [20:23:04] IMAP> 86 SELECT LocalCron [20:23:04] IMAP< * OK [CLOSED] Previous mailbox closed. [20:23:04] IMAP< * FLAGS (\Answered \Flagged \Deleted \Seen \Draft Junk NonJunk) [20:23:04] IMAP< * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft Junk NonJunk \*)] Flags permitted. [20:23:04] IMAP< * 399 EXISTS [20:23:04] IMAP< * 0 RECENT [20:23:04] IMAP< * OK [UNSEEN 399] First unseen. [20:23:04] IMAP< * OK [UIDVALIDITY 1163720154] UIDs valid [20:23:04] IMAP< * OK [UIDNEXT 3069273506] Predicted next UID [20:23:04] IMAP< * OK [HIGHESTMODSEQ 120748] Highest [20:23:04] IMAP< 86 OK [READ-WRITE] Select completed (0.000 + 0.000 secs). imap-thread.c:1344:imap select run - end 0 imap-thread.c:388:generic_cb imap-thread.c:372:found imap 0x22c8f60 imap-thread.c:1431:imap select - end imap.c:3961:select: exists 399 recent 0 expunge 0 uid_validity 1163720154 can_create_flags 1 imap-thread.c:2018:imap fetch_uid - begin imap-thread.c:372:found imap 0x22c8f60 imap-thread.c:372:found imap 0x22c8f60 [20:23:04] IMAP- [fetching UIDs...] [20:23:04] IMAP> 87 UID FETCH 1:* (UID) [20:23:04] IMAP< [FETCH data - 1024 bytes] [20:23:04] IMAP< [FETCH data - 1024 bytes] [20:23:04] IMAP< [20:23:04] IMAP< [FETCH data - 1024 bytes] [20:23:04] IMAP< [FETCH data - 1024 bytes] [20:23:04] IMAP< FETCH (UID 3069273244) [20:23:04] IMAP< [FETCH data - 1024 bytes] [20:23:04] IMAP< [FETCH data - 1024 bytes] [20:23:04] IMAP< TCH (UID 3069273313) [20:23:04] IMAP< [FETCH data - 1024 bytes] [20:23:04] IMAP< [FETCH data - 1024 bytes] [20:23:04] IMAP< TCH (UID 3069273382) [20:23:04] IMAP< [FETCH data - 1024 bytes] [20:23:04] IMAP< [FETCH data - 1024 bytes] [20:23:04] IMAP< TCH (UID 3069273451) [20:23:04] IMAP< [FETCH data - 1024 bytes] [20:23:04] IMAP< [FETCH data - 551 bytes] imap-thread.c:2008:imap fetch_uid run - end 0 imap-thread.c:388:generic_cb imap-thread.c:372:found imap 0x22c8f60 imap-thread.c:2029:imap fetch_uid - end imap.c:542:unlocking session 0x22e4c00 imap.c:4663:get_num_list: got 399 msgs imap.c:4673:removing old messages from /home/darac/.claws-mail/imapcache/mail.darac.org.uk/darac(a)darac.org.uk/LocalCron imap.c:4677:get_num_list - ok - 399 folder.c:2265:Removed message 2147483647 from cache. That last line (Removed message 2147483647 from cache) is repeated ad infinitum. Now, I happened to spot that that number is 2^31 - 1 so started looking to see if claws-mail was handling UIDs incorrectly. That lead me to http://wiki.dovecot.org/Clients/NegativeUIDs. Firstly, that page states that UIDs should be 32-bit integers. If so, why do there appear to be UIDs greater than 3 billion in the mailbox? Secondly, that page gives instructions on how to fix the problem with mbox and maildir backends. However, my mail is stored in mdboxes. Is there a way to re-generate UIDs for mdbox mailboxes? Thanks in advance!

2 2

CPU for Dovecot
by Miloslav Hůla 28 Nov '16

28 Nov '16

Hi, we are planning to change hardware for our standalone Dovecot instance handling ~5800 IMAP users with 1TB mailboxes on local RAID. Is there some recommendation about CPU? We can choose from: - Intel Xeon E5-2620v4 - 2,1GHz@8,0GT 20MB cache, 8core, HT, 85W, LGA2011 - Intel Xeon E5-2623v4 - 2,6GHz@8,0GT 10MB cache, 4core, HT, 85W, LGA2011 The difference is about more cores vs. hi frequency. Thank you, Miloslav

4 4

Dovecot proxy
by Gandalf Corvotempesta 26 Nov '16

26 Nov '16

Hi to all I have some *production* pop3/inappropriate server that i would like to move under a proxy Some questions: 1. Keeping the same original hostname on the proxy (in example mail.mydomain.tld) and changing the hostname on the imap server, makes some troubles like MUA redownloading all the messages? Is dovecot (running on the imap server) happy seeing the hostname change? What about maildirs, where the hostname is wrote on the mail file? 2. Dovecot proxy will proxy the whole pop3/imap traffic or only the login auth? I don't want to expose the mailservers to internet, all imap session must be proxied through the proxy. this because I'll use local IPs on each mail server. 3. Performance for the proxy server? The same as the mailserver or higher due to the missing email computation? In example, the proxy doesn't have to access disks or emails data but has only to transmit what the mailserver osd saying 4. Like question 3, any real users for the proxy? I would like to know some info about hardware and userbase (in example: dual quad xeon 5600, 32Gb ram, 10.000 concurrent sessions) In my case I'm planning for about 100 active sessions. Can i use a small EC2 instance?

1 1

Re: (build) crash in dcrypt when "-Bsymbolic-functions" is used on linking
by Aki Tuomi 25 Nov '16

25 Nov '16

On 26.10.2016 13:48, Christian Ehrhardt wrote: > Hi, > I was wondering about a crash when building dovecot 2.2.25 on latest > Ubuntu. > I wondered as I've had the same source building on Debian just fine. > > Some debugging led me to this weird behavior: > Using this gdb command file called autoreportissue in my case: > break dcrypt_initialize > commands > p dcrypt_vfs > p &dcrypt_vfs > watch dcrypt_vfs > c > end > break dcrypt_set_vfs > commands > p dcrypt_vfs > p &dcrypt_vfs > c > end > r > > Running test-crypto on Debian and Ubuntu reported those two behaviours: > gdb -d /root/dovecot-2.2.25/src/ -x autoreportissue ./test-crypto > > Good: > Breakpoint 1, dcrypt_initialize (backend=0x555555587c02 "openssl", > set=0x0, error_r=0x0) at dcrypt.c:15 > 15 if (dcrypt_vfs != NULL) { > $1 = (struct dcrypt_vfs *) 0x0 > $2 = (struct dcrypt_vfs **) 0x555555796370 <dcrypt_vfs> > Hardware watchpoint 3: dcrypt_vfs > Breakpoint 2, dcrypt_set_vfs (vfs=0x7ffff7835020 <dcrypt_openssl_vfs>) > at dcrypt.c:56 > 56 dcrypt_vfs = vfs; > $3 = (struct dcrypt_vfs *) 0x0 > $4 = (struct dcrypt_vfs **) 0x555555796370 <dcrypt_vfs> > Hardware watchpoint 3: dcrypt_vfs > Old value = (struct dcrypt_vfs *) 0x0 > New value = (struct dcrypt_vfs *) 0x7ffff7835020 <dcrypt_openssl_vfs> > dcrypt_set_vfs (vfs=0x7ffff7835020 <dcrypt_openssl_vfs>) at dcrypt.c:57 > 57 } > > Bad: > Breakpoint 1, dcrypt_initialize (backend=0x555555589f02 "openssl", > set=0x0, error_r=0x0) at dcrypt.c:11 > 11 { > $1 = (struct dcrypt_vfs *) 0x0 > $2 = (struct dcrypt_vfs **) 0x555555798370 <dcrypt_vfs> > Hardware watchpoint 3: dcrypt_vfs > Breakpoint 2, dcrypt_set_vfs (vfs=0x7ffff780a020 <dcrypt_openssl_vfs>) > at dcrypt.c:56 > 56 dcrypt_vfs = vfs; > $3 = (struct dcrypt_vfs *) 0x0 > $4 = (struct dcrypt_vfs **) 0x7ffff780a890 <dcrypt_vfs> > Panic: file dcrypt.c: line 34 (dcrypt_initialize): assertion failed: > (dcrypt_vfs != NULL) > Error: Raw backtrace: > /root/dovecot-2.2.25/src/lib-dcrypt/test-crypto(+0x15f7c) > [0x555555569f7c] -> > /root/dovecot-2.2.25/src/lib-dcrypt/test-crypto(default_error_handler+0) > [0x55555556a030] -> > /root/dovecot-2.2.25/src/lib-dcrypt/test-crypto(i_fatal+0) > [0x55555556a2ff] -> > /root/dovecot-2.2.25/src/lib-dcrypt/test-crypto(dcrypt_initialize+0x140) > [0x55555555f030] -> > /root/dovecot-2.2.25/src/lib-dcrypt/test-crypto(main+0x23) > [0x55555556706d] -> > /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1) > [0x7ffff782d3f1] -> > /root/dovecot-2.2.25/src/lib-dcrypt/test-crypto(_start+0x2a) > [0x55555555edea] > Program received signal SIGABRT, Aborted. > > One can see that in the bad case the pointer of dcrypt_vfs is pointing > to something of the scope of the .libs/libdcrypt_openssl.so file and > not the dcrypt_initialize of test-crypto. > > That made me wonder even more - where would this issue of variable > scope come from. After more debugging I found that the linker flag > "-Bsymbolic-functions" is the reason. This is default on recent > Ubuntu, but not on Debian (?yet?). > > Eventually what happens is that the dcrypt_vfs becomes part of the > .libs/libdcrypt_openssl.so. So the call from there to dcrypt_set_vfs > ends up setting not the expected variable. > I was unable to come up with a reasonable fix since I'm not enough > into your sublib structure. > > For now I assume I'm gonna build the package stripping this flag in > Ubuntu. > But long term I think dovecot should fix it to work with that compiler > flag. > Therefore the report to make you aware. > > > P.S. thanks to the dovecot community for having unit tests that find > this at build time! > > -- > Christian Ehrhardt > Software Engineer, Ubuntu Server > Canonical Ltd Hi! Thank you for reporting this, we'll look into it. Aki Tuomi Dovecot oy

1 1

Could the index of dovecot be stored in database?
by eSX 25 Nov '16

25 Nov '16

Hi dovecot, I have a question about the index of dovecot. I had read the wiki, and saw that I can custom a Input streams to do read/seek/sync...by implementing a istream-*.c file. Thus maybe dovecot can read mail from a http server or any others. But I found that the index of maildir can't extend very well. There is no extern API for developer? For example, I want to put the index to database(maybe, MySQL) or any else, But I found I have no way to implement it, Unless a heavy modification? -- eSX

1 0

Patch for dovecot-antispam-plugin to support IMAP Flags indicating Junk status
by Jonas Wielicki 25 Nov '16

25 Nov '16

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Dear list, I made a patch which extends dovecot-antispam-plugin with support to take the addition and removal of a specific set of flags as trigger for learning. This allows for very tight integration with Thunderbird and KMail, which both set flags for Junk messages (Thunderbird sets "Junk", KMail sets "JUNK"). With this patch and according configuration, dovecot-antispam-plugin can trigger on the addition (learn as spam) and removal (learn as ham) of these flags. Combined with a sieve script which sets these flags for incoming mail which has been classified as spam, this allows for a tight and intuitive feedback loop between users and the server-side spam classification system. I tested that patch with dovecot 2.2 from Debian stretch and so far it works pretty well. I realise that dovecot-antispam-plugin has not been updated since 2013. It also has not been migrated to Github yet. If it is to be migrated there, I would be happy to submit a pull request there for discussion and merging. Otherwise, someone would have to indicate how to go forward with applying this patch to the official version, if that is desired. The patch is based on current tip and feedback is appreciated. I took some inspiration from dovecot-core/src/plugins/notify/notify-storage.c -- this requires the use of struct mail_private to be able to override the vfunc for mail_update_keywords, which I actually do not like. However, when I tried to make this patch base on the use of the notify plugin (via notify_register), I ran into the issue that the transaction is partially freed before the transaction_commit event from notify is emitted, which is unfortunate and breaks at least the mailtrain backend (which I use). This is in theory fixable, but I wanted to keep the patch as small as possible, as I have no idea whether this will eventually end up upstream or whether I’ll have to maintain that for myself. If upstream is not interested in this patch, please let me know! In that case, I would consider making an own plugin, which fewer backends (possibly only a mailtrain-like one) out of this, but frankly, I would consider that a waste of resources. In the hope that this is useful for others and hoping for feedback, Jonas Wielicki -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEG/EPV+Xzd5wEoQQIwGIDJZdiWIoFAlg4Fd0ACgkQwGIDJZdi WIpM3Q//TWVHDFx5LK14y0jOnxzE7kGthc6hakILnWqYgl7B/wlljD1HLrec//hg 9LEancjURnv3sPU/kEEpl6RRDX5kDMbXXKXMq7/1R7bNdmeMz5NEebAo7ktlCii7 ikk7MPL0F8UViY7IoW7y5NxfqMUldYseejn0GwKiVkEyqlyGLRbP7ijyzMWjpIWp eqOg/b5bNX6ARMC1O/hKhvHw4AhvSO2j73da60Xchu39gvDa2kC+MTU/kX4wb6po kPOEgFxGhpxG0+UMzUEBPLYwY3Q9x+R/PzlpUF6xEjYxgE7leVRVfCHiZLsMUGH1 itozwSzoAyDYV+Rbzk8OEBL6EGBJQHqYmNybULZsJkxhUenNeC4GRf7NcJ0jAisG rSfwr/+kD9+ErKNgtNJzfceLYGNWti44whV6kXxRxqGlIfJsJB7ZMdrj8+wSdn0p slXUoyHMUkRkN92tIPqZF5cb+5Ke+O+5hHE07Wohxw3eNoBSqtQWo81aigjaCraC ivcZX3HswTapyKtpgWMzjoWqp982crr+wtAI+AlEUKoCEqF54EnxM1kB1qoe0HcH nMgMdIkXI4VzPaUNUK206ffEtlnKNIqF3SkOkBX263L0ZJgXyCFRRj6W3z78VDdP He62tN/FPPBtmeVrmCj2ZDE+6gqtMQN52FsN4mpaq4BrCYlYB7g= =3+CU -----END PGP SIGNATURE-----

1 0

Updated my Dovecot certificate for the first time
by Steve Litt 25 Nov '16

25 Nov '16

Hi all, I've used Dovecot since February 2012, but because I kept reinstalling Linux with every major version, I never had a Dovecot self-signed certificate go bad on me before. Til now. I started using rolling release Void Linux about a year ago, and my Dovecot self-signed certificate just expired. The solution I used is contained in these documents: http://wiki2.dovecot.org/SSL/CertificateCreation http://wiki2.dovecot.org/SSL/CertificateClientImporting file:///etc/ssl/dovecot-openssl.cnf http://www.faqforge.com/linux/renew-the-dovecot-ssl-certificate-on-ubuntu-l… I basically moved my old /etc/ssl/certs/dovecot.pem and /etc/ssl/private/dovecot.pem, then edited /etc/ssl/dovecot-openssl.cnf specifically to give myself the common name of 192.168.100.2. I had earlier used my hostname, but that produced a conflict, so I just used the ip address. Then I ran dovecot-mkcert.sh to create the new self-signed cert, and finally, configured Claws-Mail to use /etc/ssl/certs/dovecot.pem as its cert. Obviously, if my Claws-Mail were on a different machine than my Dovecot, I would have had Claws-Mail point to a local copy. Alpine still gives me a bad cert warning, saying I should either fix it or disable checking. I haven't yet found a way to get Alpine to discriminate between a valid self-signed cert and a bad one. Anyway, all's good. SteveT Steve Litt November 2016 featured book: Quit Joblessness: Start Your Own Business http://www.troubleshooters.com/startbiz

7 9

Re: Updated my Dovecot certificate for the first time
by Joseph Tam 24 Nov '16

24 Nov '16

On Thu, 24 Nov 2016, Steve Litt wrote >> add the public part of the cert into your system's trusted CA store. > > Silly question, but how would you do that? You didn't say which OS you're running on (alpine runs on Windows as well), but I'll assume *nix. A previous poster showed you how to do it with a real certificate, and the steps are the same. However, the way I found out without too much fuss was to process trace my alpine process and see where it tied to load a cert $ strace -o trace.out alpine ... quit after connection $ grep -F cert traceout /1: open64("/etc/openssl/cert.pem", O_RDONLY) Err#2 ENOENT /1: stat("/etc/openssl/certs/cbf06781.0", 0xFFBF8E54) Err#2 ENOENT ... Your output will be different of course. The first load is the default pre-loaded root CAs (Thawte, etc.) supplied by OpenSSL, and the second, etc. are chained certificate lookups. You would replace the missing cert with your own self-signed public pem file. e.g. cp mypub.pem /etc/openssl/certs/cbf06781.0 For Windows, I don't know where it fetches it from. Joseph Tam <jtam.home(a)gmail.com>

1 0

Re: Updated my Dovecot certificate for the first time
by Joseph Tam 24 Nov '16

24 Nov '16

> Alpine still gives me a bad cert warning, saying I should either fix it > or disable checking. I haven't yet found a way to get Alpine to > discriminate between a valid self-signed cert and a bad one. Well, it can't discriminate since any certificate (except those in your trusted store) that asserts its own validity is suspect. You can either get alpine to not complain e.g. inbox-path={192.168.100.2:143/user=whatever/tls/novalidate-cert} or add the public part of the cert into your system's trusted CA store. Joseph Tam <jtam.home(a)gmail.com>

2 1

antispam plugin not working correctly
by Felix Zielcke 23 Nov '16

23 Nov '16

Hi, I've configured the antispam plugin like in the wiki to use the sa- learn-pipe.sh shell script. But it's not creating the log file in /tmp. Even if I add a "touch /tmp/x" in sa-learn-pipe.sh it's not created. So how I can check if it works correctly? dovecot version 2.2.26.0 /var/log/debug although contains: Nov 23 18:36:49 daedalus imap [fzielcke(a)z-51.de 80.187.96.201 UID MOVE]: antispam: mail copy: src spam: 1, dst spam: 0, src unsure: 0 Nov 23 18:36:49 daedalus imap [fzielcke(a)z-51.de 80.187.96.201 UID MOVE]: antispam: running mailtrain backend program /usr/bin/sa-learn-pipe.sh Nov 23 18:36:49 daedalus imap [fzielcke(a)z-51.de 80.187.96.201 UID MOVE]: antispam: running mailtrain backend program /usr/bin/sa-learn-pipe.sh Nov 23 18:36:49 daedalus imap [fzielcke(a)z-51.de 80.187.96.201 UID MOVE]: antispam: running mailtrain backend program parameter 1 --ham # doveconf -n |grep antispam antispam_backend = pipe antispam_debug_target = syslog antispam_pipe_program = /usr/bin/sa-learn-pipe.sh antispam_pipe_program_notspam_arg = --ham antispam_pipe_program_spam_arg = --spam antispam_pipe_tmpdir = /tmp antispam_spam_pattern_ignorecase = SPAM antispam_trash_pattern_ignorecase = trash;Deleted * antispam_verbose_debug = 1 mail_plugins = acl zlib quota imap_zlib imap_acl imap_quota antispam

1 0

Active sieve script symbolic link doesn't update when changed.
by Steven Mainor 23 Nov '16

23 Nov '16

While setting up sieve on my email server I mistakenly setup a symlink (~/sieve/myfilter.svbin > ~/.dovecot.sieve) but I think that that should have been (~/sieve/myfilter.sieve > ~/.dovecot.sieve). I have fixed the mistake but dovecot/sieve still throws an error saying that the symlink still links to the wrong file. I have made sure the symlink is fixed (it links to ~/sieve/myfilter.sieve) and I tried restarting dovecot and the server but nothing works. I still get the error and my sieve filters aren't processed. Any help would be greatly appreciated. ~# grep sieve /var/log/syslog | nano temp.save Nov 23 01:32:09 1 dovecot: lda(steve(a)degga.net): Warning: sieve: file storage: Active Sieve script symlink /var/mail/vmail/degga.net/steve/.dovecot.sieve is broken: Invalid scriptname (points to myfilter.svbin). vmail@1:/var/mail/vmail/degga.net/steve/mail$ ls -l -a #redacted irrelevant stuff lrwxrwxrwx 1 vmail vmail 14 Nov 23 02:43 .dovecot.sieve -> myfilter.sieve vmail@1:/var/mail/vmail$ dovecot -n # 2.2.22 (fe789d2): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.13 (7b14904) # OS: Linux 4.4.0-47-generic x86_64 Ubuntu 16.04.1 LTS ext4 auth_mechanisms = plain login auth_verbose = yes mail_home =/var/mail/vmail/%d/%n mail_location = maildir:/var/mail/vmail/%d/%n/mail:LAYOUT=fs managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date index ihave duplicate mime foreverypart extracttext namespace inbox { inbox = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk { auto = subscribe special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { auto = subscribe special_use = \Trash } prefix = } passdb { args = username_format=%u scheme=ssha512 /etc/dovecot/passwd.db driver = passwd-file } plugin { sieve = ~/.dovecot.sieve sieve_after = /var/mail/vmail/sieve-after sieve_before = /var/mail/vmail/sieve-before sieve_dir = ~/sieve } protocols = imap sieve service auth { unix_listener /var/spool/postfix/private/dovecot-auth { group = postfix mode = 0660 user = postfix } } # SSL information redacted here. userdb { args = uid=vmail gid=vmail home=/var/mail/vmail/%d/%n driver = static } protocol lda { deliver_log_format = msgid=%m: %$ mail_plugins = sieve postmaster_address =postmaster(a)degga.net quota_full_tempfail = yes rejection_reason = Your message to <%t> was automatically rejected:%n% r } protocol imap { imap_client_workarounds = delay-newmail tb-extra-mailbox-sep mail_max_userip_connections = 10 }

2 2

Exim still accepting emails to nonexistent users
by Marti Markov 23 Nov '16

23 Nov '16

After adding the configuration bit: deny message = invalid recipient domains = +local_domains !verify = recipient/callout=no_cache from: http://wiki2.dovecot.org/LMTP/Exim <http://wiki2.dovecot.org/LMTP/Exim> running update-exim4.conf and service exim4 restart the server is still accepting emails to recipients that do not exist in dovecot. Any ideas?

3 6

Single user to have lrw to all mailboxes
by Marti Markov 23 Nov '16

23 Nov '16

I have implemented a global acl: * owner lrwstipkae INBOX.Spam owner lrwstipeka .Trash owner lrwsti INBOX.Trash owner lrw * user=master-user(a)mydomain.com lrs * owner lrwstipkae But the master-user then loses all other permissions on his own mailbox, he is left only with: lrs Any pointers on how to fix this?

1 0

Good email client to use with Dovecot?
by Steve Litt 22 Nov '16

22 Nov '16

Hi all, When I use an email client, its purpose is as a window into my Dovecot IMAP, and as a mechanism to reply to and send emails. I don't do filtering or calendaring on my email client (filtering via procmail direct to Dovecot). What email clients are all of you using to look at your IMAP email? Thanks, SteveT Steve Litt November 2016 featured book: Quit Joblessness: Start Your Own Business http://www.troubleshooters.com/startbiz

20 40

LDAP auth problems "unknown user"
by Nikolai Lusan 22 Nov '16

22 Nov '16

Hi, I am setting up a dovecot instance to host a bunch of virtual domains, with ldap backing for auth. I am using a single hostname for test purposes, with a couple of entries in the diectory. If I use auth binds I get a result, but this does not suit the end purpose of the server. If I use ldapsearch with the same base, search filter, and credentials as the ldap auth config I get the correct attributes returned, and I have bit of perl that verifies the password hash matches the password provided. I am running out of ideas here, I had thought of putting in a custom bit of perl and using the checkpassword method, but this is sub optimal. If anyone can help with this I'd be grateful. # dovecot --version 2.2.26.0 (23d1de6) # dovecot -n # 2.2.26.0 (23d1de6): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.16 (fed8554) # OS: Linux 4.8.0-1-amd64 x86_64 Debian stretch/sid ext3 auth_cache_size = 2 M auth_debug = yes auth_debug_passwords = yes auth_default_realm = maliuta.org auth_master_user_separator = * auth_mechanisms = plain login auth_realms = maliuta.org auth_verbose = yes auth_verbose_passwords = yes first_valid_uid = 117 last_valid_uid = 117 lda_mailbox_autocreate = yes login_log_format_elements = user=<%u> method=%m rip=%r lip=%l mpid=%e %c mail_gid = vmail mail_location = maildir:/var/spool/vmail/%d/%n/Maildir mail_uid = vmail managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded- character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date index ihave duplicate mime foreverypart extracttext namespace 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 = } passdb { args = /etc/dovecot/ldap/maliuta.org-ldap.conf.ext driver = ldap } plugin { sieve = file:~/sieve;active=~/.dovecot.sieve } protocols = " imap lmtp sieve" service auth-worker { user = $default_internal_user } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-userdb { group = vmail mode = 0660 user = vmail } user = $default_internal_user } service dict { unix_listener dict { group = vmail mode = 0660 user = vmail } } service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 0 } } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0660 user = postfix } } ssl_cert = # grep -v '^ *$#.*$\?$' /etc/dovecot/ldap/maliuta.org-ldap.conf.ext uris = ldap://localhost dn = cn=admin,dc=maliuta,dc=org dnpass = <secret> tls = yes tls_ca_cert_dir = /etc/ssl/certs auth_bind = no ldap_version = 3 base = ou=mail,dc=mailuta,dc=org scope = subtree default_pass_scheme = SSHA deref = never user_attrs = postfixDeliveryAddress=user user_filter = (&(postfixDeliveryEnabled=TRUE)(objectClass=postfixMailPerson)) pass_attrs = postfixDeliveryAddress=user,userPassword=password pass_filter = (&(postfixDeliveryEnabled=TRUE)(objectClass=postfixMailPerson)(postfixD eliveryAddress=%u)) iterate_attrs = uid=user iterate_filter = (objectClass=postfixMailPerson) # ldapsearch -H ldap://localhost:389 -x -D 'cn=admin,dc=maliuta,dc=org' -W -b "ou=mail,dc=maliuta,dc=org" -s sub -LLL -ZZ '(&(postfixDeliveryEnabled=TRUE)(objectClass=postfixMailPerson)(postfixDeliveryAddress=nikolai(a)test.maliuta.org))' uid userPassword Enter LDAP Password: dn: mail=nikolai(a)test.maliuta.org,ou=mail,dc=maliuta,dc=org uid: nikolai userPassword:: e1NTSEF9QVBZMTlaeGw1cWd0a25XeGxURXdqM2g5Yk5YL3BxOGY= ## From /var/log/mail.log Nov 20 07:24:20 kiliya dovecot: auth: Debug: auth client connected (pid=27086) Nov 20 07:24:20 kiliya dovecot: auth: Debug: client in: AUTH#0111#011PLAIN#011service=imap#011secured#011session=1kW2C65BFI2WZbl8#011lip=<local_ip>#011rip=<remote_ip>#011lport=143#011rport=36116#011local_name=<hostname>#011resp=AG5pa29sYWlAdGVzdC5tYWxpdXRhLm9yZwBmb29iYXIzMzQ0 (previous base64 data may contain sensitive data) Nov 20 07:24:20 kiliya dovecot: auth: Debug: ldap(nikolai(a)test.maliuta.org,<remote_ip>,<1kW2C65BFI2WZbl8>): cache miss Nov 20 07:24:20 kiliya dovecot: auth: Debug: ldap(nikolai(a)test.maliuta.org,<remote_ip,<1kW2C65BFI2WZbl8>): pass search: base=ou=mail,dc=mailuta,dc=org scope=subtree filter=(&(postfixDeliveryEnabled=TRUE)(objectClass=postfixMailPerson)(postfixDeliveryAddress=nikolai(a)test.maliuta.org)) fields=postfixDeliveryAddress,userPassword Nov 20 07:24:20 kiliya dovecot: auth: ldap(nikolai(a)test.maliuta.org,<remote_ip>,<1kW2C65BFI2WZbl8>): unknown user (given password: <correct_password>) Nov 20 07:24:22 kiliya dovecot: auth: Debug: client passdb out: FAIL#0111#011user=nikolai(a)test.maliuta.org -- Nikolai Lusan <nikolai(a)lusan.id.au>

2 2

Maildir migration from Dovecot to Dovecot
by Marco Hofmann (XenAdmin) 22 Nov '16

22 Nov '16

Hello everbody, I'm a proud user of Dovecot 2.2.9 on Ubuntu 14.04 LTS. I currently migrate all my Linux services to a new Debian 8 Jessie Server. On this server I installed and configured Dovecot 2.2.24. Now I search a way to migrate the two IMAP users I have on this server preserving all timestamps, folders and flags. Yes, only two ;-) I read the following two articles: http://wiki2.dovecot.org/Tools/Doveadm/Sync http://wiki2.dovecot.org/Migration/Dsync But I must say, that either these articles are not so good, or I act quite dumb. I understand that I have to use "doveadm backup" against my old server to make a one sync with all properties of each mail. What I miss are proper examples and that there are so many options, I could set. But what confuses me most is the the configuration file in (http://wiki2.dovecot.org/Migration/Dsync) which I don't know how to reference? Am I using the wrong guides, are the article someway misleading or is there anything else I'm overlooking? Thank you so much! -- Marco Hofmann https://www.meinekleinefarm.net/ Twitter: @ZomboBrain

2 1

nologin + reason -> logging reason
by Arkadiusz Miśkiewicz 22 Nov '16

22 Nov '16

Hi. I'm using nologin with own reason [1]. That works fine. For example pop3 client gets nice message like "-ERR [AUTH] Account is locked. Please contact support." Unfortunately maillog lacks information details about why user was not allowed to log in. pop3-login: Disconnected (auth failed, 1 attempts in 2 secs): user=<testuser>, method=LOGIN, rip=1.1.1.1, lip=2.2.2.2, session=<yIsRftBBmsrB7y2h> Is it possible to log "reason" there, too? (whether it is default/internal dovecot reason or my custom one). reason is the only thing in maillog that allows to distinguish why user was not allowed to log in. 1. http://wiki2.dovecot.org/PasswordDatabase/ExtraFields -- Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org )

3 5

Clients creating folders in root when using shared namespace
by Jon Cutting 21 Nov '16

21 Nov '16

We have set up dovecot to use a shared namespace, and it works well. However, when a client attempts to create a folder in the namespace, although dovecot responds with permission denied, it still goes on to create a folder, but in the root of our virtual mailbox folder (more confusingly, even issuing a LIST command for a non-existent subfolder creates the folder in the root). I've checked through the documentation for a misconfiguration but so far to no avail. Our steps to reproduce are as follows: * Create shared namespace (in our case we've used prefix Users/%%u/) * Share folder from one user to another so that the shared folder displays in LIST * Create a folder as a subfolder of the shared folder (i.e. . CREATE Users/testfolder) Expected behaviour: permission is denied and no folder is created Actual behaviour: permission is denied, but folder is created at the root of our vmail store (in the above example a folder /mnt/storage/vmail/testfolder would be created) Thanks, Jon Output from doveconf -n # 2.2.13: /etc/dovecot/dovecot.conf # OS: Linux 3.16.0-4-amd64 x86_64 Debian 8.6 ext4 mail_location = maildir:/mnt/storage/vmail/%d/%n/Maildir mail_plugins = " quota zlib acl" managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave namespace Users { list = children location = maildir:/mnt/storage/vmail/%%d/%%n/Maildir:INDEX=/mnt/storage/vmail/%d/%n/sharedindex/%%d/%%n/ prefix = Users/%%u/ separator = / subscriptions = no type = shared } namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = separator = / type = private } passdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } plugin { acl = vfile acl_shared_dict = file:/mnt/storage/vmail/%d/shared-mailboxes.db quota = maildir:User quota quota_rule = *:storage=50GB sieve = /mnt/storage/vmail/%d/%n/.dovecot.sieve sieve_before = /mnt/storage/vmail/dovecot.sieve sieve_dir = /mnt/storage/vmail/%d/%n/sieve zlib_save = gz zlib_save_level = 6 } protocols = imap lmtp sieve service imap-login { inet_listener imaps { port = 993 ssl = yes } } service lmtp { inet_listener lmtp { address = 0.0.0.0 port = 2003 } user = vmail } service managesieve-login { inet_listener sieve { port = 4190 } service_count = 1 vsz_limit = 64 M } ssl = required ssl_ca = </etc/dovecot/dovecotca.pem ssl_cert = </etc/dovecot/dovecot.pem ssl_key = </etc/dovecot/private/dovecot.pem userdb { args = uid=5000 gid=5000 home=/mnt/storage/vmail/%d/%n allow_all_users=yes driver = static } protocol imap { imap_client_workarounds = tb-extra-mailbox-sep mail_plugins = " quota zlib acl imap_quota" } protocol lmtp { mail_plugins = " quota zlib acl sieve" }

1 0

[PATCH] Manually cleanup OpenSSL from dovecot_openssl_common_global_unref()
by Apollon Oikonomopoulos 21 Nov '16

21 Nov '16

OpenSSL 1.1 features a cleanup function that is automatically run on shutdown using atexit(3). This function frees all OpenSSL-allocated resources. In dovecot, OpenSSL is loaded indirectly using dlopen(3) against the relevant dovecot crypto module and is finally unloaded using dlclose(3). Until OpenSSL 1.0.1c this worked fine, however OpenSSL 1.0.1c makes sure[1] that the library stays loaded after the initial dlclose() so that the atexit(3) handlers can run on shutdown. This, together with the fact that dovecot uses custom allocation functions for OpenSSL and has already partially free()'d some of OpenSSL's resources in module_free(), leads to a segfault at process shutdown[2]. We fix this by explicitly calling OPENSSL_cleanup() during module unload. This is safe to do, as long as we will never want to subsequently re-initialize OpenSSL. [1] https://github.com/openssl/openssl/commit/4af9f7fe79ff82b90c16969b7e5871435… [2] https://buildd.debian.org/status/fetch.php?pkg=dovecot&arch=amd64&ver=1:2.2… Signed-off-by: Apollon Oikonomopoulos <apoikos(a)debian.org> --- src/lib-ssl-iostream/dovecot-openssl-common.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/src/lib-ssl-iostream/dovecot-openssl-common.c b/src/lib-ssl-iostream/dovecot-openssl-common.c index 51ea3ad..2bf6307 100644 --- a/src/lib-ssl-iostream/dovecot-openssl-common.c +++ b/src/lib-ssl-iostream/dovecot-openssl-common.c @@ -101,6 +101,9 @@ bool dovecot_openssl_common_global_unref(void) ERR_remove_thread_state(NULL); #endif ERR_free_strings(); +#if OPENSSL_VERSION_NUMBER >= 0x10100000L + OPENSSL_cleanup(); +#endif return FALSE; } -- 2.10.1

4 4

Index-cache sizes
by Tom Sommer 21 Nov '16

21 Nov '16

I had a customer with an INBOX cache of 400MB+ (5.5GB maildir) which gave me "Error: mmap_anon(474165248) failed: Cannot allocate memory" errors, then I deleted the cache files and ran 'doveadm index -u xxx(a)example.com "*"', now the INBOX cache is 7MB What is up with that? Is the cache now missing something or does it make sense to wipe cache files and reindex cache every-so-often? -- Tom

1 0

Feedback on first, i.e. novice-level, experiences with dovecot
by Michael Felt 21 Nov '16

21 Nov '16

a) google: "dovecot imap configuration" brought an article from 2005 as the first item: while I like debian and a bit of history you may want to ask yourself how to improve your site as the primary hit from google. FYI: years ago I had great results in the top of google searches - and then I made a major error - I moved my site to a new url and google forgot me. b) using your http://wiki.dovecot.org/QuickConfiguration as a guide: I built dovecot using --prefix=/opt (I abhor /usr/local these days - that is so 1984ish). The applications got installed in /opt/bin root@x066:/data/prj/aixtools/dovecot/core# ls -ltr /opt total 36 drwxr-xr-x 3 root root 4096 Nov 20 14:33 lib drwxr-xr-x 3 root root 4096 Nov 20 14:33 include drwxr-xr-x 6 root root 4096 Nov 20 14:33 share drwxr-xr-x 3 root root 4096 Nov 20 14:33 libexec drwxr-xr-x 2 root root 4096 Nov 20 14:33 sbin drwxr-xr-x 2 root root 4096 Nov 20 14:33 bin Are the directories 'make install' touched or made. root@x066:/data/prj/aixtools/dovecot/core# /opt/bin/doveconf -n # 2.3.devel (92c8109): /opt/etc/dovecot/dovecot.conf doveconf: Fatal: open(/opt/etc/dovecot/dovecot.conf) failed: No such file or directory where are example configs? root@x066:/data/prj/aixtools/dovecot/core# find /opt -name example-config root@x066:/data/prj/aixtools/dovecot/core# Not in /opt How about a default config? root@x066:/data/prj/aixtools/dovecot/core# find / -name dovecot /etc/init.d/dovecot /etc/pam.d/dovecot /etc/default/dovecot /etc/dovecot /var/lib/dovecot ^C Seems to be /etc/dovecot root@x066:/data/prj/aixtools/dovecot/core# ls -l /etc/dovecot total 40 drwxr-xr-x 2 root root 4096 Apr 30 2015 conf.d -rw-r--r-- 1 root root 4180 Jun 8 2014 dovecot.conf -rw-r----- 1 root dovecot 410 Jun 8 2014 dovecot-db.conf.ext -rw-r----- 1 root dovecot 782 Jun 8 2014 dovecot-dict-sql.conf.ext -rw-r--r-- 1 root dovecot 1363 Apr 30 2015 dovecot.pem -rw-r----- 1 root dovecot 5348 Jun 8 2014 dovecot-sql.conf.ext drwx------ 2 root root 4096 Apr 30 2015 private -rw-r--r-- 1 root root 121 Jun 8 2014 README and finally - read README to find the examples: root@x066:/data/prj/aixtools/dovecot/core# cat /etc/dovecot/README Configuration files go to this directory. See example configuration files in /usr/share/doc/dovecot-core/example-config/ Conclusion: --prefix=/opt is not applied everywhere. * More first impressions as I come to them - if you want them - as I hope this helps make dovecot better! Michael

2 4

doveadm service: verify client cert
by Matwey V. Kornilov 20 Nov '16

20 Nov '16

Hello, I want to open a socket for connecting doveadm using tcps. I do the following: service doveadm { inet_listener { port = 5001 ssl = yes } } At the same time, I would like to verify client certificates for connections goes to port 5001. I am trying to do the following, but it doesn't work: protocol doveadm { ssl_require_crl = yes ssl_verify_client_cert = yes } How could I achieve required behavior?

1 0

Compound Literal - xlc and gcc differences can be patched
by Michael Felt 19 Nov '16

19 Nov '16

Since I so miserably misspelled packaging - a new thread specific to the issue at hand. I found a "workaround". In short, xlc does not accept arrays of nested array - the bottom line (best message) is: 1506-995 (S) An aggregate containing a flexible array member cannot be used as a member of a structure or as an array element. At the core - all the other messages come because this (I shall call it nesting). For the test-http-auth.c file I have a patch (attached). make ran for while with no issue, then it started running into several files with this same style of specification - doveadm-dict.c being the first one. I ran "make -i" and I notice several files with this - for xlc - "unaccepted" syntax. Please look at the patch - what it basically is - and let me know whether you would consider accepting patches in this form (e.g., verify gcc (I assume) will accept it as well). If your answer is yes, I shall proceed with the additional files (learn how your MACROS work!) and send them to you. Again, initially I would just send one, e.g., doveadm-dict.c - to be sure your regular compiler also builds this alternate specification. Thank you for your consideration! Michael

2 5

Re: Good email client to use with Dovecot?
by Joseph Tam 19 Nov '16

19 Nov '16

Steve Litt asks > * And most important, where can I find the best, most unambiguous > Alpine documentation, that doesn't assume I know anything about > Alpine? The ~/.pinerc config file is well documented. There is a bewildering number of options, and you can tweak it just about anyway you like. Choice of mail readers tend to a religious issue. Users of a particular reader will only change when you pry their cold dead fingers off of it. Alpine is not a bad choice (I've been using it and it's predeccesor for decades), and I go through mail faster than most people I know as I can type faster than they can click buttons, scroll, and drag windows around. However, it sort of sucks when you read formatted mail HTML with lots of graphics). Joseph Tam <jtam.home(a)gmail.com>

1 0

Generalized looping possible in pigeonhole sieve?
by Jeff Kletsky 18 Nov '16

18 Nov '16

I'm struggling to achieve the kind of filtering with sieve that I was able to do with procmail. TL;DR I'd like a way to loop through a set of (address, destination) pairs in sieve so that I can maintain the (address, destination) pairs in one place and not have to explicitly write scores of nearly identical [...] if address :matches ["From", "Sender", "To", "Cc"] "address53" { fileinto "destination53" } if address :matches ["From", "Sender", "To", "Cc"] "address54" { fileinto "destination54" } [...] Longer: I've been using a table-based dispatch approach with procmail for years and it was working reasonably well. The approach uses list of pairs of address and destination boxes and doing a lookup based on the message to be delivered. With procmail, I collected the list of addresses and passed them to external scripts to do the lookup. If I just had a dozen boxes that I deal with, that would be straightforward to implement and maintain in sieve. As the list is an order of magnitude greater than that, maintaining the list of pairs in an external file and programmatically looping through it is a lot easier. I've looked at vnd.dovecot.execute and it certainly can return a destination box name given the input information. Unfortunately, the construct of (for example) address :matches "To" "*"' only returns the first address, not the list of addresses. I can't see a good way to get all the addressees from sieve to pass to the external program. If I have to pass the message (or at least the interesting headers) to the external program and then parse the address list myself, then I'm nearly all the way to just using a full-on external program to parse the whole message. While I'm not adverse to writing the whole thing in Python (or the like) and just using sieve as a thin shell, I'd like to make sure I'm not missing something in sieve. One way to achieve this would be to be able to loop through the pairs and using variable substitution for each iteration. I haven't seen anything in Dovecot Pigeonhole sieve that allows this. If you have any ideas on how to harness sieve for this, I'd appreciate it! Jeff

3 2

BUG: nopassword doesn't work with CRAM-MD5
by Arkadiusz Miśkiewicz 18 Nov '16

18 Nov '16

Hello. dovecot 2.2.26.0 When testing nopassword extra field (http://wiki2.dovecot.org/PasswordDatabase/ExtraFields) with CRAM-MD5 dovecot doesn't allow any password (while it should) and returns " Authentication failed" while in logs: Nov 17 08:22:34 auth-worker(1551): Info: sql(pepe,127.0.0.1,<Y8amDXpBptV/AAAB>): Requested CRAM-MD5 scheme, but we have a NULL password NULL is there because our sql query returns empty password just like wiki says "nopassword: you want to allow all passwords, use an empty password and this field. " If password is returned in sql query then it fails, too: Nov 17 09:00:49 auth-worker(2206): Error: sql(pepe,127.0.0.1,<eO5vlnpBtNd/AAAB>): nopassword set but password is non- empty So looks to be a bug. -- Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org )

3 6

Any way to simplify repeated use of same string-list?
by Jeff Kletsky 18 Nov '16

18 Nov '16

I often use the same set of header names when doing an 'address' comparison. I would prefer to be able to specify that once, then re-use it in several places. As an example set "address_mailman_fields" "\"To\", \"Cc\", \"From\", \"Errors-To\""; if address :domain :matches ["${address_mailman_fields}"] "example.com" { [...] } if address :domain :matches ["${address_mailman_fields}"] "dovecot.org" { [...] } or the like would be quite helpful. From what I can tell, even though the variable interpolation *looks* like a string-list, it isn't parsed as such. For example, from sieve-test output: sieve-test(jeff): Debug: Mailbox <filename> Opened mail UID=1 because: header "To", "Cc", "From", "Errors-To" (Cache file is unusable) testing: line 27: info: DEBUG: address ["${address_mailman_fields}"] didn't match. sieve-test(jeff): Debug: Mailbox <filename> Opened mail UID=1 because: header ["To", "Cc", "From", "Errors-To"] (Cache file is unusable) testing: line 34: info: DEBUG: address "[${address_mailman_fields}]" didn't match. Is there any trick available to specify a string-list once, then re-use it throughout the script? Thanks, Jeff

1 0

dovecot pre-install issue
by soumitri＠iitk.ac.in 17 Nov '16

17 Nov '16

Hello all, I am going for a dovecot director based setup (2 director+ 2 imap), more imap servers will be added later depending on demand/load. Presently I have 12000+ dovecot users with Maildir quota varying from 1 GB to 20GB. (peak hour IOPS 50000+) I am having 2 options in choosing dovecot version. 1) Old stable release. I.e RHEL, with prebuilt binary. This will be having less trouble in managing. Why RHEL still using version 2.2.10. 2) Latest release with best features and lesser known bugs. I.e CentOS7 with with latest compiled version. I have to be more involved if a bug is found. I will prefer a less admin work after the setup, with all/most features working. If you have a recent similar setup/dovecot gurus, Pl. suggest. With thanks & regards, -- Soumitri Mishra http://home.iitk.ac.in/~soumitri/

3 5

New Gmail Android App and Dovecot
by David Flanigan 16 Nov '16

16 Nov '16

Dovecot Users, I have a sudden new problem that has cropped up just recently and I am stumped. My implementation has been working for over a year with no issues. Version Data: Dovecot: v2.2.10 (using self signed certificates) openSSL: v1.01e Gmail Android App: v6.10.23 November 3, 2016 The issue: I use the iphone Gmail App to access my e-mail from phone and tablet. It is simple and supports multiple accounts very nicely. This has worked for better than 18 months without issue. This week I upgraded my Android app to the latest version of Gmail and I stopped getting incoming e-mail. I can still pick up via outlook and other tools I use, but just not the android version of Gmail. When I attempt to pick up mail i see the below error in my log file. _Nov 16 14:18:56 ns1 dovecot: imap-login: Disconnected (no auth attempts in 0 secs): user=<>, rip=10.10.10.198, lip=10.1.1.10, TLS: SSL_read() failed: error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version number, session=<73vF8W9BdgCmrL7G>_ Disconnect and no new e-mail. There is no error in the Gmail app that I can find. The Gmail app works fine with my other accounts (Gmail, work, etc) so I am wondering if it is a configuration issue on my side or Gmail App stopped supporting something I was using. My SSl config is RPM standard other than SSL=yes and my self signed certificates. Any thoughts would be appreciated. -- Kind Regards, David

3 2

Crashing when run against OpenSSL 1.1.0c
by Michael Marley 15 Nov '16

15 Nov '16

Hi, I am running Dovecot 2.2.26.0 compiled against OpenSSL 1.1 and, since upgrading to OpenSSL 1.1.0c, the "lmtp" process has been crashing with SIGSEGV whenever it receives SIGINT. This always happens a minute or so after the lmtp process handles a message. It can also be manually reproduced by sending SIGINT to one of the running lmtp processes. I am compiling and running on an Ubuntu 17.04 x86_64 system using GCC 6.2. Here is the output of me reproducing it with gdb: (gdb) signal SIGINT Continuing with signal SIGINT. Program received signal SIGSEGV, Segmentation fault. 0x00007f6748cc2fb0 in ?? () (gdb) bt #0 0x00007f6748cc2fb0 in ?? () #1 0x00007f674872ac60 in ossl_init_thread_stop (locals=<optimized out>) at crypto/init.c:336 #2 0x00007f674872aee4 in OPENSSL_cleanup () at crypto/init.c:391 #3 0x00007f67491052e0 in __run_exit_handlers (status=0, listp=0x7f674948c5d8 <__exit_funcs>, run_list_atexit=run_list_atexit@entry=true, run_dtors=run_dtors@entry=true) at exit.c:83 #4 0x00007f674910533a in __GI_exit (status=<optimized out>) at exit.c:105 #5 0x00007f67490eb3f8 in __libc_start_main (main=0x555b35fbfbc0 <main>, argc=1, argv=0x7ffd4ede3588, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffd4ede3578) at ../csu/libc-start.c:325 #6 0x0000555b35fbfe3a in _start () Here is the output of "doveconf -n": # 2.2.26.0 (23d1de6): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.devel (623ae77) # OS: Linux 4.8.7-040807-generic x86_64 Ubuntu Zesty Zapus (development branch) auth_mechanisms = plain login auth_username_format = %Ln mail_location = mdbox:~/mdbox mailbox_list_index = yes managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date index ihave duplicate mime foreverypart extracttext namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { driver = pam } plugin { sieve = file:~/sieve;active=~/.dovecot.sieve } postmaster_address = michael(a)michaelmarley.com protocols = imap sieve lmtp service auth { client_limit = 1624 unix_listener /var/spool/postfix/private/dovecot-auth { group = postfix mode = 0660 user = postfix } } service imap-login { inet_listener imaps { port = 0 } } service lmtp { process_min_avail = 5 unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } ssl = required ssl_ca = </etc/ssl/private/COMODORSADomainValidationSecureServerCA.crt ssl_cert = </etc/ssl/private/michaelmarley.com.crt ssl_cipher_list = HIGH !RC4 !aNULL !eNULL !3DES @STRENGTH ssl_dh_parameters_length = 4096 ssl_key = # hidden, use -P to show it ssl_protocols = !SSLv3 userdb { driver = passwd } protocol lmtp { mail_plugins = " sieve" } protocol lda { mail_plugins = " sieve" } local_name matthewtmarley.com { ssl_ca = </etc/ssl/private/COMODORSADomainValidationSecureServerCA.crt ssl_cert = </etc/ssl/private/matthewtmarley.com.crt ssl_key = # hidden, use -P to show it } I tried recompiling Dovecot to see if that might do any good, but I got the same result. Also, I noticed that the "test-crypto" test in src/lib-dcrypt also crashes on exit (despite the fact that all the tests succeeded) with a very similar stacktrace: (gdb) run Starting program: /home/michael/Source/dovecot/core/src/lib-dcrypt/test-crypto [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". test_cipher_test_vectors ............................................. : ok test_cipher_aead_test_vectors ........................................ : ok test_hmac_test_vectors ............................................... : ok test_load_v1_keys .................................................... : ok test_load_v1_key ..................................................... : ok test_load_v1_public_key .............................................. : ok test_load_v2_key ..................................................... : ok test_load_v2_public_key .............................................. : ok test_get_info_v2_key ................................................. : ok test_gen_and_get_info_rsa_pem ........................................ : ok test_get_info_rsa_private_key ........................................ : ok test_get_info_invalid_keys ........................................... : ok test_get_info_key_encrypted .......................................... : ok test_get_info_pw_encrypted ........................................... : ok test_password_change ................................................. : ok test_load_invalid_keys ............................................... : ok 0 / 16 tests failed Program received signal SIGSEGV, Segmentation fault. 0x00007ffff75a5480 in ?? () (gdb) bt #0 0x00007ffff75a5480 in ?? () #1 0x00007ffff6ff7c60 in ossl_init_thread_stop (locals=<optimized out>) at crypto/init.c:336 #2 0x00007ffff6ff7ee4 in OPENSSL_cleanup () at crypto/init.c:391 #3 0x00007ffff78472e0 in ?? () from /lib/x86_64-linux-gnu/libc.so.6 #4 0x00007ffff784733a in exit () from /lib/x86_64-linux-gnu/libc.so.6 #5 0x00007ffff782d3f8 in __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6 #6 0x000055555555f68a in _start () If there is anything I have missed or if there is any other way I can help, please let me know. Thanks, Michael Marley

3 3

lazy-load SNI?
by Felipe Gasper 15 Nov '16

15 Nov '16

Hello, We’re rolling out large SNI deployments for our mail servers. Each domain gets an entry like this in the config: local_name mail.foo.com { ssl_cert = </ssl/domain_tls/*.foo.com/combined ssl_key = </ssl/domain_tls/*.foo.com/combined } There are a couple problems we’re finding with this approach: 1) Dovecot wants to load everything at once, which has some machines taking up many GiB of memory just for Dovecot. Is there any way to defer loading of an SSL cert until a client actually requests it? 2) Any time we add or remove a domain, Dovecot’s SNI config matrix needs to be rebuilt. Is there a way to handle SNI requests dynamically via some sort of configuration plugin, so we wouldn’t need to rebuild the config on domain add/remove? I looked through the docs but couldn’t see a way to do this. Thank you in advance! -Felipe Gasper Mississauga, ON

4 12

[PATCH] ssl: fix reference to SSLv2 and disable SSLv3
by Apollon Oikonomopoulos 15 Nov '16

15 Nov '16

This is driven by the fact that OpenSSL 1.1 does not know about SSLv2 at all and dovecot's defaults simply make OpenSSL error out with "Unknown protocol 'SSLv2'"[1]. So we change the defaults to refer to SSLv2 iff OpenSSL seems to know something about it. While at it, it's also a good idea to disable SSLv3 by default as well. [1] https://bugs.debian.org/844347 Signed-off-by: Apollon Oikonomopoulos <apoikos(a)debian.org> --- doc/example-config/conf.d/10-ssl.conf | 2 +- src/lib-master/master-service-ssl-settings.c | 6 +++++- 2 files changed, 6 insertions(+), 2 deletions(-) diff --git a/doc/example-config/conf.d/10-ssl.conf b/doc/example-config/conf.d/10-ssl.conf index 31b750c..2cd445b 100644 --- a/doc/example-config/conf.d/10-ssl.conf +++ b/doc/example-config/conf.d/10-ssl.conf @@ -46,7 +46,7 @@ ssl_key = </etc/ssl/private/dovecot.pem #ssl_dh_parameters_length = 1024 # SSL protocols to use -#ssl_protocols = !SSLv2 +#ssl_protocols = !SSLv3 # SSL ciphers to use #ssl_cipher_list = ALL:!LOW:!SSLv2:!EXP:!aNULL diff --git a/src/lib-master/master-service-ssl-settings.c b/src/lib-master/master-service-ssl-settings.c index 4a05045..6b43f6c 100644 --- a/src/lib-master/master-service-ssl-settings.c +++ b/src/lib-master/master-service-ssl-settings.c @@ -44,7 +44,11 @@ static const struct master_service_ssl_settings master_service_ssl_default_setti .ssl_key = "", .ssl_key_password = "", .ssl_cipher_list = "ALL:!LOW:!SSLv2:!EXP:!aNULL", - .ssl_protocols = "!SSLv2", +#ifdef SSL_TXT_SSLV2 + .ssl_protocols = "!SSLv2 !SSLv3", +#else + .ssl_protocols = "!SSLv3", +#endif .ssl_cert_username_field = "commonName", .ssl_crypto_device = "", .ssl_verify_client_cert = FALSE, -- 2.10.1

2 1

save failed to open mailbox quarantine
by Eggert Ehmke FTV Spandau 15 Nov '16

15 Nov '16

I have dovecot 2.2.13 set up with spamassassin and amavis. This works fine so far, Spam emails are forwarded to "username+Quarantine(a)mydomain.de". The recipient_delimiter=+ is set, the Quarantine folder exists. However, Dovecot tries to deliver it to a folder quarantine, that does not exist. In the dovecot-deliver.log there are these lines: Nov 14 14:16:13 lda(username(a)mydomain.de): Info: msgid=<2707212.2aHC3KDWrN@wookie>: save failed to open mailbox quarantine: Mailbox doesn't exist: quarantine Nov 14 14:16:13 lda(username(a)mydomain.de): Info: msgid=<2707212.2aHC3KDWrN@xxxxxx>: saved mail to INBOX Indeed the message is found in the inbox. What can be done so the folder name is not converted to lower case?

2 5

How does one mark all messages as read (imap4flag "seen") with sieve?
by Ben Johnson 15 Nov '16

15 Nov '16

Hello! I had hoped that marking all messages that arrive to a specific mailbox as read/seen would be as simple as applying the following sieve script to all incoming mail for that mailbox user: ######################## require ["imap4flags"]; addflag "\\Seen"; ######################## With this script in-place, mail does not appear to be marked as read/seen. It arrives as it normally would, and my email client sees it as new mail. Is something more required? Or is it a bug/limitation in my email client? I've found many examples of "addflag "\\Seen";" on the web, but all of them are wrapped in conditional logic of some variety. This is a spam-training mailbox and I simply want everything marked as seen/read upon arrival so I'm not bothered/notified every time. Thanks for any pointers here! -Ben

3 12

dovecot / tcp-wrappers / FBSD 10.3
by Jim Pazarena 14 Nov '16

14 Nov '16

Can anyone share the proper config to get wrappers working in dovecot on FreeBSD? The dovecot examples do not seem to work, and I thought perhaps FBSD needs slightly different configs. I've compiled with: -DHAVE_LIBWRAP which I presume is the first step. The example for dovecot.conf in uncommenting: login_access_sockets = tcpwrap merely causes a log error of "imap-login: Error: connect(tcpwrap) failed: No such file or directory" Suggestions/Direction much appreciated.

3 2

Self-Signed Certificate issue
by Darryl Baker 13 Nov '16

13 Nov '16

My apologies if this is a repeat but my search of the archive did not turn it up in the recent past. If this has been covered just point me at the previous thread, please. I am running a small email site which I am moving from uw-imapd and Solaris to Ubuntu and Dovecot imaps and pop3s. I am trying to use a self-signed certificate for this site. I am using Thunderbird as the test client. I've tried both the pre-built snakeoil certificate and building a special one for dovecot. In /var/log/mail.err I keep getting what I am interpreting as a missing CA cert. The message is: dovecot: imap-login: Error: SSL: Stacked error: error:14094418:SSL routines:ssl3_read_bytes:tlsv1 alert unknown ca: SSL alert number 48 The certificate was created by: openssl req -new -x509 -days 365 -nodes -out /etc/ssl/certs/dovecot.pem -keyout /etc/ssl/private/dovecot.pem The Dovecot version is 2.2.22 (fe789d2) The Ubuntu version is 16.04 LTS current patches. *Darryl Baker*

3 3

help needed configuration of quota warning mails
by Götz Reinicke 13 Nov '16

13 Nov '16

Hi, we run dovecot 2.2.24 and from what I see, quota management with warning message is configured currently with "noenforcing". Our individual quota limit is stored in the users ldap DN which is fetched as I see from the logs and by "doveadm quota get -u" I tried to trigger the warning mail by going over the limit on my account step by step and can see that values are counted with the command above and in thunderbird by showing the orange and than red warning symbol at the bottom for me. But the warning mail script is not triggert. How may I debug this? /usr/local/bin/quota-warning.sh is owned currently by vmail and executable by vmail. Thanks for feedback and suggestion . /Götz

1 0

Dovecot lmtp
by Peter Fraser 13 Nov '16

13 Nov '16

Hi All I am migrating from dovecot-1.x where I had LDA running to dovecot2-2.2.26.0_1 where I am trying to set up LMTP. I have enabled a TCP/IP socket .Setting below. service lmtp { inet_listener lmtp { address = 127.0.0.1 port = 24 } } and put this additional entry in postfix virtual_transport = lmtp:127.0.0.1:24 in 10-mail.conf my mail location is below mail_location=maildir:~/Maildir:INBOX=~/Maildir/:INDEX=~/Maildir/tmp/index My problem is that when I enable lmtp, dovecot creates a new maildir at /home/vmail/user(a)domain.com and delivers the email there in a Maildir instead of using the default one at /home/vmail/username I researched it but I just can't seem to figure out why this is. I would really appreciate any help on this. Thanks in advance.

2 1

Redirect the emails from domain2 to domain1
by Quaquaraquà 11 Nov '16

11 Nov '16

Dear Dovecot and Exim users, I have a VPS using these two applications. I am transitioning from a domain_old to a domain_new. I'd like to redirect all the emails from domain_old to the local mailboxes of users @ domain_new. In exim I've assumed that it is enough to add domain_old to the list of local domains: domainlist local_domains = @ : domain_new : domain_old ... begin routers ... local_users: debug_print = "R: local_user for $local_part@$domain" driver = accept domains = +local_domains transport = dovecot_lmtp cannot_route_message = Unknown user However in Dovecot I'm checking both the username and the domain to perform the authentication: auth_username_format = %Lu passdb { driver = sql ; } password_query = SELECT username, domain, password FROM users WHERE username = '%n' AND domain = '%d' To have this system to work, I wish some special rule that rewrites the domain from domain_old to domain_new. But I'm not sure whether this needs to be done in exim or dovecot and how to add it? - Quaquaraqua'

3 2

How to Analyze Missing UIDs (and Files) in Maildirs?
by Jochen Bern 11 Nov '16

11 Nov '16

Hello everyone, I would like pointers on how to analyze the following situation, please: I'm running one test and one production dovecot IMAPS server for one of our platforms. The clients are essentially appliances we distribute, auth by client cert, virtual users only, mailboxes in maildir format: > auth_ssl_require_client_cert = yes > auth_ssl_username_from_cert = yes > auth_mechanisms = plain > ssl = required > ssl_cert = </etc/pki/dovecot/certs/... > ssl_key = </etc/pki/dovecot/private/... > ssl_ca = </etc/pki/dovecot/certs/... > ssl_verify_client_cert = yes > mail_location = maildir:~ > userdb { > driver = static > args = uid=... gid=... home=/home/.../%Ld_realm/%Ln > } > passdb { > driver = static > args = password=... > } The client certs have CNs unique to the appliance and no client besides that appliance is supposed to access the mailbox. Appliances take note of the UIDs they've seen (and not yet deleted) and expect to be able to re-access e-mails by the UIDs they know. (Needless to say, I keep my hands away from the cache files so as not to cause the UIDs to be reassigned.) The dovecot version used is updated along with the CentOS 6 source RPMs - which contain a 2.0.9 plus whatever patches CentOS backported - and receives two additional patches from me, one from current dovecot sources to improve closure of inactive SSL connections and one from me that turns the IMAP CREATE command into a NOP; the appliance code doesn't expect mailboxes to have folders besides INBOX. ------- QA is looking into an upcoming new feature that requires appliances to reread old e-mails, and got errors that UIDs the test appliances expected to still be on the (test) server weren't. I verified, the UIDs are indeed absent from the dovecot-uidlist files. The mails in question arrived *sometime* over the course of the last 12 months and must've vanished *sometime* since then ... ugh. No trace of what may have happened to them in any logs, of course. On the test server, I re-enabled logging of DELETE, UNDELETE and EXPUNGE commands, in case the appliances delete mails themselves and forget to update their own cache. Are there other IMAP commands that could remove mails, and thus should be added to the list? Would it be possible to have dovecot configured so that there's a log entry whenever a client tries to retrieve a UID that dovecot doesn't have in the maildir anymore? ------- While looking into the above issue, I noticed that a large number of mailboxes (test as well as production) have UIDs that *are* listed in dovecot-uidlist, yet, no corresponding file is present anymore. Example: > # grep -c : *_realm/$EXAMPLE_USER/dovecot-uidlist > 58 > # grep : *_realm/$EXAMPLE_USER/dovecot-uidlist | sed -e '2,57d' -e 's/ .*//' > 1 > 152 > # for PAIR in `grep : *_realm/$EXAMPLE_USER/dovecot-uidlist | sed -e 's/ .*:/:/'` ; do > > IMAP_UID=`echo $PAIR | sed -e 's/:.*//'`; BASE=`echo $PAIR | sed -e 's/.*://'` > > CNT=`find *_realm/$EXAMPLE_USER -type f -name "$BASE"'*' -ls | wc -l` > > if [ $CNT -ne 1 ]; then echo "Found $CNT files for UID $IMAP_UID"; fi; done > Found 0 files for UID 135 > Found 0 files for UID 136 > Found 0 files for UID 139 > Found 0 files for UID 142 > Found 0 files for UID 143 > Found 0 files for UID 144 > Found 0 files for UID 145 > Found 0 files for UID 150 > Found 0 files for UID 151 Is that normal behaviour? If not, how would I try to find out what happens there? Kind regards, -- Jochen Bern Systemingenieur Fon: +49 6151 9067-231 Fax: +49 6151 9067-290 E-Mail: jochen.bern(a)binect.de www.binect.de www.facebook.de/binect Binect GmbH Robert-Koch-Straße 9, 64331 Weiterstadt, DE Geschäftsführung: Christian Ladner, Dr. Frank Wermeyer, Nils Manegold Unternehmenssitz: Weiterstadt Register: Amtsgericht Darmstadt, HRB 94685 Umsatzsteuer-ID: DE 221 302 264 MAX 21-Unternehmensgruppe

1 0

Enterprise Edition: Any known access issues with the repo? Have existing accounts been expired?
by deoren 11 Nov '16

11 Nov '16

Hi, I'm getting errors when attempting to run apt-get update on an Ubuntu 14.04 box where I've had an existing EE installation for some time: > W: Failed to fetch https://apt.dovecot.fi/stable-2.2/ubuntu/trusty/dists/trusty/main/binary-am… HttpError401 > > W: Failed to fetch https://apt.dovecot.fi/stable-2.2/ubuntu/trusty/dists/trusty/main/binary-i3… HttpError401 > > E: Some index files failed to download. They have been ignored, or old ones used instead. I'm running 2.2.25.5 now and when I looked at the announcement forum[1] I see a posting[2] for 2.2.26.1, but nothing about repo changes. For what it is worth, I use the EE credentials on only a single node so I am hopefully not triggering any abuse thresholds. I tried accessing the URL used in the /etc/apt/sources.list.d/FILENAME.list file via a web browser and it isn't accepting the provided username/password. Have existing credentials been expired? If so, what is the next step to restore access? Thanks. References: [1] https://forum.open-xchange.com/forumdisplay.php?35-Dovecot-Announcements [2] http://software.open-xchange.com/products/dovecot/doc/Release_Notes_for_Dov…

2 1

Maildir filename has wrong S value - possible culprit
by Libor Pavlík 11 Nov '16

11 Nov '16

Hi, I'm new to dovecot but as I see in mailinglist archive this issue is old and I didn't find this in archive. One of cuplrits (I believe not the only possible) is spamassassin. It's added headers make exactly the difference between S value and filesize. Probably it's in the way emails are processed in "manufactory" of Qmail+Vpopmail+Spamassassin but now I'm not able to say how can it be repaired. As mentioned above I'm using solution with Qmail+Vpopmail+Spamassassin+Dovecot, my Dovecot version is 2.2.26.0. Libor Pavlík

1 0

post-delivery virus scan
by Brad Koehn 11 Nov '16

11 Nov '16

I have discovered that many times the virus definitions I use for scanning messages (ClamAV, with the unofficial signatures http://sanesecurity.com/usage/linux-scripts/) are updated some time after my server has received an infected email. It seems the virus creators are trying to race the virus definition creators to see who can deliver first; more than half of the infected messages are found after they’ve been delivered. Great. To help detect and remove the infected messages after they’ve been delivered to users’ mailboxes, I created a small script that iterates the INBOX and Junk mailbox directories, scans recent messages for viruses, and deletes them if found. The source of my script (run via cron) is here: https://gitlab.koehn.com/snippets/9 Unfortunately Dovecot doesn’t like it if messages are deleted (dbox) out from under it. I tried a doveadm force-resync on the folder containing the messages, but it seems Dovecot is still unhappy. At least on the new version (2.2.26.0) it doesn’t crash; 2.2.25 would panic and coredump when it discovered messages had been deleted. I’m wondering if there’s a better way to scan recent messages and eradicate them so the Dovecot isn’t upset when it happens. Maybe using doveadm search? Looking for suggestions. --- Brad

6 9

Re: How does one mark all messages as read (imap4flag "seen") with sieve?
by Ben Johnson 11 Nov '16

11 Nov '16

On 11/10/2016 2:02 AM, Aki Tuomi wrote: > Hi! > > Can you provide bt full from gbd? > > Install debug symbols and acquire core file > > Run gdb /path/to/bin /path/to/core > > Issue bt ful > > Send it to list. > > > Aki Tuomi > > Dovecot oy > > > > On November 10, 2016 at 2:42 AM Larry Rosenman <larryrtx(a)gmail.com> > wrote: > > looks to me from the coredump (although you pointed to the wrong binary) > that > deliver was PANIC()'ing with > > io_add(0x%x) called twice fd=%d, callback=%p -> %p > > I'm not sure what that message means, but maybe one of the dovecot folks > does. > > Are all the packages built together? > > Are you averse to compiling stuff yourself? Thanks so much for the assistance here, Larry and Aki. Aki, you had asked me to send this core-dump to the list when I asked about it back in September; I did post the "bt full" output at that time, but there were no further replies: http://www.dovecot.org/list/dovecot/2016-September/105428.html And for convenience, here is the "bt full" output I posted back then: http://pastebin.com/4xdGNXa6 So, this is where I'm confused: Larry, you mentioned "although you pointed to the wrong binary", which is a concern I had asked about back in September: http://www.dovecot.org/list/dovecot/2016-September/105424.html I still don't understand how this is pointing to the wrong binary: # gdb /usr/lib/dovecot/dovecot-lda /var/vmail/tmp/core-deliver-6-5000-5000-29125-1473732949 Is /usr/lib/dovecot/dovecot-lda not the binary that segfaulted here? Sure, the gdb output says, "Core was generated by `/usr/lib/dovecot/deliver ...", but on the system in question, that is a symlink pointing to /usr/lib/dovecot/dovecot-lda: # ls -lah /usr/lib/dovecot/deliver lrwxrwxrwx 1 root root 11 Sep 21 10:29 /usr/lib/dovecot/deliver -> dovecot-lda What am I missing here? The mismatch message does say something specific about this: warning: the debug information found in "/lib64/ld-2.23.so" does not match "/lib64/ld-linux-x86-64.so.2" (CRC mismatch). Is this the result of pointing to the wrong executable when calling "gdb"? If so, where is the correct executable to pass as the fist argument? Again, for convenience, the pipe script I'm using: http://pastebin.com/zXzBDcvG And the debug output from said pipe script: http://pastebin.com/rz2f4S4G My full "doveconf -n": http://pastebin.com/hCgpA009 Thanks! -Ben

1 0

service doveadm : ssl problems
by nerbrume＠free.fr 10 Nov '16

10 Nov '16

Hello, I'm using dovecot 2.2.13 on Debian stable. My users are authenticated through PAM, and stored in an LDAP backend I'm trying to set-up replication with ssl, following (mainly) this : http://wiki2.dovecot.org/Replication 1) I only diverted from the instructed setup by not setting "doveadm_port = 12345", as it would give me errors of the like: > Fatal: /var/run/dovecot/auth-userdb: Configured passdbs don't support crentials lookups (to see if user is proxied, because doveadm_port is set) but rather specifying the port in the mail_replica setting : "mail_replica = tcps:my.domain.com:1465" (following a mail from here : http://www.dovecot.org/list/dovecot/2016-September/105356.html) So far, this seems to be working for me. 2) However, I'm having ssl problems. I have a let's encrypt certificate, and have concatened the CA cert and my server cert in a fullchain.pem. Excerpt from my ssl config : > ssl = yes > ssl_cert = </etc/letsencrypt/live/my.domain.com/fullchain.pem > ssl_key = </etc/letsencrypt/live/my.domain.comi/privkey.pem doveadm return me these errors (sudo -u dovecot doveadm -v sync -u user tcps:my.domain.com:12345) : > doveadm(casoli): Info: Received invalid SSL certificate: unable to get local issuer certificate: /CN=my.domain.com > doveadm(casoli): Error: doveadm server disconnected before handshake: Received invalid SSL certificate: unable to get local issuer certificate: /CN=my.domain.com > doveadm(casoli): Fatal: Disconnected from remote: Received invalid SSL certificate: unable to get local issuer certificate: /CN=my.domain.com Which I can reproduce with openssl (openssl s_client -showcerts -CApath /etc/ssl/certs -connect my.domain.com:12345) : > (...) > Verify return code: 21 (unable to verify the first certificate) Indeed, in this case, dovecot only returns the local part of the certificate (my.domain.com) and not the full chain (with the intermediate CA). While testing regular IMAPS with openssl is ok (openssl s_client -showcerts -CApath /etc/ssl/certs -connect my.domain.com:993) > (...) > Verify return code: 0 (ok) And I can see the full chain. So, it's seems to me that doveadm is somehow wrongly serving my certificate, truncating it, but I can't see why, and if this is a misconfiguratin on my part. I can post more config files or message outputs if needed, I kept them redacted here for the sake of brevity. Regards, N

2 2

Dovecot 2 LDAP "unknown user"
by Peter Fraser 10 Nov '16

10 Nov '16

Hi All I am using Dovecot dovecot2-2.2.25_6 on FreeBSD 11. I am trying to set up LDAP authentication to Active Director as I had it in version 1 of Dovecot. My settings are at bottom. When I run doveadm auth test username, I get back root@BSD-11:/usr/local/etc/dovecot # doveadm auth test username Password: passdb: user auth succeeded extra fields: user=username root@BSD-11:/usr/local/etc/dovecot # But when I run telnet 127.0.0.1 110 and try to log in it says unknown user. Error below in maillog. BSD-11 dovecot: pop3: Error: Authenticated user not found from userdb, auth lookup id=2262958081 (client-pid=2273 client-id=1) Nov 1 15:15:41 BSD-11 dovecot: pop3-login: Internal login failure (pid=2273 id=1) (internal failure, 1 successful auths): user= root@BSD-11:/usr/local/etc/dovecot # doveconf -n # 2.2.25 (7be1766): /usr/local/etc/dovecot/dovecot.conf # OS: FreeBSD 11.0-RELEASE-p1 i386 auth_debug = yes auth_verbose = yes listen = * login_greeting = Mail Server ready. mail_location = maildir:~/Maildir namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { args = /usr/local/etc/dovecot/dovecot-ldap.conf.ext driver = ldap } ssl_cert = </usr/local/etc/certs/certs/dovecot.pem ssl_key = </usr/local/etc/certs/private/dovecot.pem userdb { args = /usr/local/etc/dovecot/dovecot-ldap.conf.ext driver = ldap } protocol lda { mail_plugins = } #Contents of dovecot-ldap.conf.ext hosts = 192.168.153.143 dn = user(a)domain.com dnpass = password auth_bind = yes auth_bind_userdn = domain\%u ldap_version = 3 base = dc=domain,dc=com pass_filter = (&(objectclass=person)(uid=%u)) user_attrs = homeDirectory=/home/vmail/%u,uid=1002,gid=1002 Amy help would be appreciated.

3 9

question concerning junk folder
by Rajesh M 10 Nov '16

10 Nov '16

hi using centos 6.5, qmailtoaster, dovecot, spamassassin. i found that junk folder is specified under /etc/dovecot/conf.d/15-mailboxes.conf the issue is that this folder is getting created automatically and genuine emails from both within the server and also from external domains are being routed to the Junk folder. all these emails are not scanned by spamassasin. i wish to disable to creation of Junk folder and also routing of emails to the Junk folder. help required please. ##################### # NOTE: Assumes "namespace inbox" has been defined in 10-mail.conf. namespace inbox { # These mailboxes are widely used and could perhaps be created automatically: mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Trash { special_use = \Trash } ##################### rajesh

2 1

search body with wildcards
by W. de Hoog 10 Nov '16

10 Nov '16

Hi, A question. We are using fts_solr. When searching for content in BODY I noticed that dovecot only supports full words. "BODY calibration" returns results but "BODY calibra" does not. Nor "BODY calibra*". Solr does support searching with wildcards so why is it that dovecot does not? regards, -- Willem-Jan de Hoog

1 2

tons of dovecot/config processes
by Arkadiusz Miśkiewicz 10 Nov '16

10 Nov '16

Hi. I've noticed that dovecot (using 2.2.26.0 here) starts dovecot/config processes that stay for long time. Example: [root@ixion-pld ~]# service dovecot restart Stopping Dovecot service.......................................................................................................................................[ DONE ] Starting Dovecot service.......................................................................................................................................[ DONE ] [root@ixion-pld ~]# ps aux|grep dovecot root 25333 0.0 0.0 13736 2480 ? Ss 09:40 0:00 /usr/sbin/dovecot dovecot 25336 0.0 0.0 9480 924 ? S 09:40 0:00 dovecot/anvil [0 connections] root 25337 0.0 0.0 9612 2416 ? S 09:40 0:00 dovecot/log root 25339 0.0 0.0 12496 3256 ? S 09:40 0:00 dovecot/config root 25341 0.0 0.0 132168 888 pts/1 S+ 09:40 0:00 grep dovecot [root@ixion-pld ~]# doveadm reload [root@ixion-pld ~]# ps aux|grep dovecot root 25333 0.0 0.0 13872 2720 ? Ss 09:40 0:00 /usr/sbin/dovecot dovecot 25336 0.0 0.0 9480 924 ? S 09:40 0:00 dovecot/anvil [0 connections] root 25344 0.0 0.0 9612 2428 ? S 09:40 0:00 dovecot/log root 25346 0.0 0.0 12496 3192 ? S 09:40 0:00 dovecot/config root 25348 0.0 0.0 132168 876 pts/1 S+ 09:40 0:00 grep dovecot so far good - only one dovecot/config. Lets connect to pop3 and keep connection [root@ixion-pld ~]# telnet localhost pop3 Trying 127.0.0.1.110... Connected to localhost. Escape character is '^]'. +OK Mail server ready. on the other console [root@ixion-pld ~]# ps aux|grep dovecot root 25333 0.0 0.0 13872 2720 ? Ss 09:40 0:00 /usr/sbin/dovecot dovecot 25336 0.0 0.0 9480 924 ? S 09:40 0:00 dovecot/anvil [2 connections] root 25344 0.0 0.0 9612 2428 ? S 09:40 0:00 dovecot/log root 25346 0.0 0.0 12496 3192 ? S 09:40 0:00 dovecot/config dovenull 25364 0.0 0.0 20908 4080 ? S 09:41 0:00 dovecot/pop3-login [127.0.0.1] dovecot 25365 0.0 0.0 100236 7776 ? S 09:41 0:00 dovecot/auth [0 wait, 0 passdb, 0 userdb] root 25368 0.0 0.0 132168 856 pts/1 S+ 09:41 0:00 grep dovecot so there is a client connected and one dovecot/config. Lets reload: [root@ixion-pld ~]# doveadm reload [root@ixion-pld ~]# ps aux|grep dovecot root 25333 0.0 0.0 13872 2752 ? Ss 09:40 0:00 /usr/sbin/dovecot dovecot 25336 0.0 0.0 9480 924 ? S 09:40 0:00 dovecot/anvil [2 connections] root 25344 0.0 0.0 9612 2428 ? S 09:40 0:00 dovecot/log root 25346 0.0 0.0 12920 3700 ? S 09:40 0:00 dovecot/config dovenull 25364 0.0 0.0 20908 4080 ? S 09:41 0:00 dovecot/pop3-login [127.0.0.1] dovecot 25365 0.0 0.0 100236 7776 ? S 09:41 0:00 dovecot/auth [0 wait, 0 passdb, 0 userdb] root 25371 0.0 0.0 9612 2196 ? S 09:41 0:00 dovecot/log root 25373 0.0 0.0 12496 3196 ? S 09:41 0:00 dovecot/config root 25375 0.0 0.0 132168 856 pts/1 S+ 09:41 0:00 grep dovecot now we have two dovecot/config processes. Second dovecot/config stays there until client disconnects (what for?). When clients disconnects we are back to single dovecot/config: [root@ixion-pld ~]# ps aux|grep dovecot root 25333 0.0 0.0 13872 2752 ? Ss 09:40 0:00 /usr/sbin/dovecot dovecot 25336 0.0 0.0 9480 924 ? S 09:40 0:00 dovecot/anvil [0 connections] root 25371 0.0 0.0 9612 2196 ? S 09:41 0:00 dovecot/log root 25373 0.0 0.0 12496 3196 ? S 09:41 0:00 dovecot/config root 25418 0.0 0.0 132168 852 pts/1 S+ 09:43 0:00 grep dovecot Now on production server where are tons of clients this looks more insane: # ps aux|grep dovecot/config | wc -l 56 Note that I'm running with shutdown_clients = no here (+ high performance auth/login variant). So looks like something is not right here. Obviously with shutdown_clients=yes this doesn't occur since clients are disconnected. doveadm reload can happen every 2 minutes (because dovecot requires reload when SSL certificates change; new domain gets added, new cert gets automatically created -> reload, certificate is renewed (every 2 months) -> reload etc) -- Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org )

1 0

Dovecot processes turning zombie
by Adrian POPA 10 Nov '16

10 Nov '16

Hi I am running Ubuntu 14.04 (plan to go to 16.04) with Postfix and Dovecot 2.2.9 from Ubuntu repository. Dovecot configuration has not changed dramatically since the days of Ubuntu 12.04 (can't remember Dovecot version). In the last months, connection to Dovecot IMAP service become more and more dificult. First Ubuntu Thunderbird refused to connect, than Android phones. The last one connecting regularly was an old XP laptop(!). Now it's facing problems too. Again, I did not make any configuration changes lately so only system upgrades (libraries) may have caused this. The first thing to notice was that some Dovecot processes are going zombie (defunct). At startup "ssl-params", then sometimes "auth", "imap-login" and rarely "config". Turning on debug logging in Dovecot show that offending process "is ignoring idle SIGINT". And "auth client limit (1000) reached". This behavior also impacts on Postfix delivery through Dovecot LDA with "status=deferred (temporary failure)" (I turned off mail sending with -e in lda invocation). Another thing is SLL connection. Attempts to test with openssl s_client show that Dovecot is not responding after ClientHelo when it should normally send server certificate. The very same certificate is used with Postfix and it works (I can send mails through Postfix) but IMAP connections to Dovecot do not. There is no protocol mismatch because I have try a local SSL connection (same computer). Initial messages are TLS1.2 but nothing in response. So my question is: did you faced such problems and found a cause (and maybe a fix)? Upgrading to Ubuntu 16.04 with whatever Dovecot version it provides may resolve the issues? Thanks

1 0

<-FIN <-RST ->FIN,ACK <-RST on SSL connection shutdown
by Heiko Schlittermann 10 Nov '16

10 Nov '16

Hello, a typical connection close, tcpdump'ed on the server side, looks as follows: 21:44:01.168131 IP xxx.xxx.3.101.143 > xxx.xxx.3.96.35518: Flags [FP.], seq 3982457856:3982457959, ack 1570044906, win 243, options [nop,nop,TS val 138698279 ecr 159494908], length 103 21:44:01.172405 IP xxx.xxx.3.101.143 > xxx.xxx.3.96.35518: Flags [R], seq 3982457960, win 0, length 0 21:44:01.172442 IP xxx.xxx.3.96.35518 > xxx.xxx.3.101.143: Flags [F.], seq 32, ack 104, win 342, options [nop,nop,TS val 159494909 ecr 138698279], length 0 21:44:01.172471 IP xxx.xxx.3.101.143 > xxx.xxx.3.96.35518: Flags [R], seq 3982457960, win 0, length 0 The server closes (FIN) the connection, and already 4.274 ms later the server sends a RST to the client. The clients response to FIN arrives some μs later. (On the client side the order of the packages is different (FIN from Server, FIN,ACK from client, RST from Server, RST from Server) This behaviour seems to be odd (the client side firewall complains about the unexpected packages). I can reproduce it using openssl -connect … -starttls imap .. on the client side. It happens on IMAP+STARTTLS as well as on IMAPS. It does not happen on plaintext IMAP. There I see the expected shudown handshake FIN - FIN,ACK - ACK. Dovecot version is 2.2.24 (a82c823) Best regards from Dresden/Germany Viele Grüße aus Dresden Heiko Schlittermann -- SCHLITTERMANN.de ---------------------------- internet & unix support - Heiko Schlittermann, Dipl.-Ing. (TU) - {fon,fax}: +49.351.802998{1,3} - gnupg encrypted messages are welcome --------------- key ID: F69376CE - ! key id 7CBF764A and 972EAC9F are revoked since 2015-01 ------------ -

1 0

Backing up dovecot mailboxes
by Jerry 09 Nov '16

09 Nov '16

Does anyone have a working solution as to how I can use "doveadm backup" to back up a virtual users mailbox to a removable USB device. I keep receiving numerous errors and no files are backed up although the directories are created. -- Jerry

3 2

Indexing failed: 500 Internal Server Error
by W. de Hoog 09 Nov '16

09 Nov '16

Hi, While running doveadm index on a mailbox this gets printed: doveadm(neil): Error: fts_solr: Indexing failed: 500 Internal Server Error doveadm(neil): Panic: file http-client-request.c: line 792 (http_client_request_send_payload): assertion failed: (ret == 0) doveadm(neil): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x88662) [0x7f0a52750662] -> /usr/lib/dovecot/libdovecot.so.0(+0x886d9) [0x7f0a527506d9] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f0a526e9f81] -> /usr/lib/dovecot/libdovecot.so.0(http_client_request_send_payload+0xc8) [0x7f0a52703cf8] -> /usr/lib/dovecot/modules/lib21_fts_solr_plugin.so(solr_connection_post_more+0x49) [0x7f0a518654a9] -> /usr/lib/dovecot/modules/lib21_fts_solr_plugin.so(+0x3187) [0x7f0a51861187] -> /usr/lib/dovecot/modules/lib20_fts_plugin.so(+0x8667) [0x7f0a51ec8667] -> /usr/lib/dovecot/modules/lib20_fts_plugin.so(fts_build_mail+0x4f1) [0x7f0a51ec8fb1] -> /usr/lib/dovecot/modules/lib20_fts_plugin.so(+0xefce) [0x7f0a51ecefce] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_precache+0x29) [0x7f0a52a045f9] -> /usr/bin/doveadm(+0x2e997) [0x565355d01997] -> /usr/bin/doveadm(+0x28dec) [0x565355cfbdec] -> /usr/bin/doveadm(+0x299ca) [0x565355cfc9ca] -> /usr/bin/doveadm(doveadm_cmd_ver2_to_mail_cmd_wrapper+0x209) [0x565355cfd7d9] -> /usr/bin/doveadm(doveadm_cmd_run_ver2+0x555) [0x565355d0c715] -> /usr/bin/doveadm(doveadm_cmd_try_run_ver2+0x37) [0x565355d0c767] -> /usr/bin/doveadm(main+0x1da) [0x565355cecc7a] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0) [0x7f0a5231f830] -> /usr/bin/doveadm(_start+0x29) [0x565355ced059] $ dovecot -n # 2.2.26.0 (23d1de6): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.devel (623ae77) # OS: Linux 4.4.0-45-generic x86_64 Ubuntu 16.04.1 LTS disable_plaintext_auth = no log_path = /var/log/dovecot.log mail_plugins = fts fts_solr mail_privileged_group = mail namespace { hidden = yes inbox = yes list = no location = mbox:~/mail:INBOX=/var/mail/%u prefix = "#mbox/" separator = / } namespace { list = yes location = sdbox:/home/imapshared-sdbox prefix = shared/ separator = / subscriptions = no type = public } namespace inbox { location = sdbox:~/sdboxmail mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = separator = / } passdb { driver = pam } plugin { fts = solr fts_autoindex = yes fts_solr = break-imap-search url=http://localhost:8080/solr/ fts_squat = partial=4 full=10 sieve = file:~/sieve;active=~/.dovecot.sieve } protocols = " imap" ssl_cert = </etc/ssl/certs/dovecot.pem ssl_key = # hidden, use -P to show it userdb { driver = passwd } protocol imap { imap_client_workarounds = tb-extra-mailbox-sep tb-lsub-flags } -- Willem-Jan de Hoog

3 6

Too many references: cannot splice
by Luis Ugalde 09 Nov '16

09 Nov '16

Hi, A while ago I sent an email regarding these "*ETOOMANYREFS* Too many references: cannot splice." that we've seen since Debian updated the Jessie kernel to 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt20-1+deb8u3 (2016-01-17) x86_64 while older kernels, like 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt11-1+deb8u6 (2015-11-09) x86_64 showed no errors at all. I was wondering if no one else is getting these errors, or if you know any workarounds that might probe useful, apart from downgrading the kernel. I would say that the infrastructure we're running is quite standard, with directors balancing users to NFS backed dovecot servers. Best regards, Luis Ugalde.

2 3

Repeat e-mail syndrome shows up in 2.2.26+
by The Doctor 09 Nov '16

09 Nov '16

Getting complaints from people about pop/imap issues. some people are getting repaeted e-mail. Other are not able to delete their e-mails from an IMAP lcient. Current configuration /usr/dovecot2/sbin/dovecot -n # 2.2.26.0 (23d1de6): /usr/dovecot2/etc/dovecot/dovecot.conf # OS: FreeBSD 11.0-RELEASE-p2 amd64 base_dir = /var/run/dovecot/ disable_plaintext_auth = no first_valid_uid = 100 info_log_path = /var/log/dovecot-info.log listen = [::] log_path = /var/log/dovecot.log login_log_format_elements = user=<%u> method=%m rip=%r lip=%l %c mail_debug = yes mail_location = mbox:~/mail:INBOX=/var/mail/%u mail_log_prefix = %Us(%u): mdbox_rotate_size = 2 k passdb { args = /etc/master.passwd driver = passwd-file } plugin { home = /usr/dovecot2 } service auth { executable = /usr/dovecot2/libexec/dovecot/auth user = root } service imap-login { chroot = login client_limit = 256 executable = /usr/dovecot2/libexec/dovecot/imap-login inet_listener imap { address = 204.209.81.1, 127.0.0.1 port = 143 } inet_listener imaps { address = 204.209.81.1, 127.0.0.1 port = 993 ssl = yes } process_limit = 128 process_min_avail = 3 service_count = 1 user = dovecot } service imap { executable = /usr/dovecot2/libexec/dovecot/imap process_limit = 512 } service lmtp { executable = lmtp -L inet_listener lmtp { address = 204.209.81.1 127.0.0.1 ::1 port = 24 } process_min_avail = 5 } service pop3-login { chroot = login client_limit = 256 executable = /usr/dovecot2/libexec/dovecot/pop3-login inet_listener pop3 { address = 204.209.81.1 port = 110 } inet_listener pop3s { address = 204.209.81.1 port = 995 ssl = yes } process_limit = 128 process_min_avail = 3 service_count = 1 user = dovecot } service pop3 { executable = /usr/dovecot2/libexec/dovecot/pop3 process_limit = 512 } ssl_cert = </usr/dovecot2/etc/dovecot/ssl/pop3.nk.ca.2016.chain.crt ssl_cipher_list = ALL:!LOW:!SSLv2:!EXP:aNULL ssl_key = # hidden, use -P to show it userdb { driver = passwd } userdb { args = /etc/passwd driver = passwd-file } verbose_ssl = yes protocol imap { imap_client_workarounds = delay-newmail tb-extra-mailbox-sep imap_idle_notify_interval = 2 mins imap_logout_format = bytes=%i/%o imap_max_line_length = 64 k mail_max_userip_connections = 10 mail_plugin_dir = /usr/dovecot2/lib/dovecot/imap ssl_cert = </usr/dovecot2/etc/dovecot/ssl/pop3.nk.ca.2016.chain.crt ssl_cipher_list = ALL:!LOW:!SSLv2:!EXP:aNULL ssl_key = # hidden, use -P to show it verbose_ssl = yes } protocol pop3 { mail_max_userip_connections = 3 mail_plugins = pop3_client_workarounds = outlook-no-nuls oe-ns-eoh pop3_enable_last = yes pop3_lock_session = yes pop3_logout_format = top=%t/%p, retr=%r/%b, del=%d/%m, size=%s pop3_no_flag_updates = yes pop3_reuse_xuidl = yes pop3_save_uidl = no pop3_uidl_format = %08Xu%08Xv ssl_cert = </usr/dovecot2/etc/dovecot/ssl/pop3.nk.ca.2016.chain.crt ssl_cipher_list = ALL:!LOW:!SSLv2:!EXP:aNULL ssl_key = # hidden, use -P to show it verbose_ssl = yes } protocol lmtp { auth_username_format = %Lu info_log_path = /var/log/dovecot-lmtp.log } Sorry about the indents. Anything causing these issues? -- Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca God,Queen and country!Never Satan President Republic!Beware AntiChrist rising! http://www.fullyfollow.me/rootnl2k Look at Psalms 14 and 53 on Atheism Time for the USA to hold a referendum on its republic and vote to dissolve!!

6 13

that's just so amazing and wonderful
by mrgrim 08 Nov '16

08 Nov '16

Hi friend! Look at that amazing stuff, it is absolutely wonderful. Please take a look <http://bargain.jontrauner.com/e4tfx/5> Speak to you later, mrgrim

1 0

imapsieve pigeonhole plugin?
by Larry Rosenman 08 Nov '16

08 Nov '16

How do you enable the imapsieve plugin? I added sieve_plugins = imapsieve and it whines: hebighonker.lerctr.org /usr/local/etc/dovecot/conf.d # service dovecot restart managesieve: Fatal: Plugin 'imapsieve' not found from directory /usr/local/lib/dovecot/sieve doveconf: Error: managesieve-login: dump-capability process returned 89 Stopping dovecot. Waiting for PIDS: 97491. managesieve: Fatal: Plugin 'imapsieve' not found from directory /usr/local/lib/dovecot/sieve doveconf: Error: managesieve-login: dump-capability process returned 89 Starting dovecot. managesieve: Fatal: Plugin 'imapsieve' not found from directory /usr/local/lib/dovecot/sieve doveconf: Error: managesieve-login: dump-capability process returned 89 this plugin seems to be poorly documented. :( -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 (c) E-Mail: larryrtx(a)gmail.com US Mail: 17716 Limpia Crk, Round Rock, TX 78664-7281

2 11

wiki: Plugins/Virtual: SQL error?
by Larry Rosenman 08 Nov '16

08 Nov '16

Is one of these supposed to be imap? Note that none of the namespaces have inbox=yes. This is because for IMAP users you want the inbox namespace to have inbox=yes, but for POP3 users you want the virtual namespace to have inbox=yes. This requires setting the inbox=yes in userdb extra fields <http://wiki2.dovecot.org/UserDatabase/ExtraFields>. For example with MySQL you can can do this like: user_query = SELECT ..., \ CASE '%s' WHEN 'pop3' THEN NULL ELSE 'yes' END AS 'namespace/inbox/inbox', \ CASE '%s' WHEN 'pop3' THEN 'yes' ELSE NULL END AS 'namespace/virtual/inbox' \ WHERE ... -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 (c) E-Mail: larryrtx(a)gmail.com US Mail: 17716 Limpia Crk, Round Rock, TX 78664-7281

1 0

A lot of duplicate GUIDS.
by kjonca＠o2.pl 08 Nov '16

08 Nov '16

Recently I have in logs a LOT of messages like this: [....] Nov 06 19:39:36 IMAP(kjonca): Error: mdbox /home/kjonca/Mail/1/storage: Duplicate GUID 13511 in m.1530:845670 (size=2622) and m.1371:1831730 (size=916) Nov 06 19:39:36 IMAP(kjonca): Error: mdbox /home/kjonca/Mail/1/storage: Duplicate GUID 13512 in m.1530:847414 (size=2274) and m.1371:1832476 (size=1069) Nov 06 19:39:36 IMAP(kjonca): Error: mdbox /home/kjonca/Mail/1/storage: Duplicate GUID 13513 in m.1530:848971 (size=2339) and m.1371:1833330 (size=1202) Nov 06 19:39:36 IMAP(kjonca): Error: mdbox /home/kjonca/Mail/1/storage: Duplicate GUID 13514 in m.1530:850496 (size=2723) and m.1371:1834276 (size=1036) Nov 06 19:39:36 IMAP(kjonca): Error: mdbox /home/kjonca/Mail/1/storage: Duplicate GUID 13515 in m.1530:852219 (size=2187) and m.1371:1835108 (size=1638) Nov 06 19:39:36 IMAP(kjonca): Error: mdbox /home/kjonca/Mail/1/storage: Duplicate GUID 13516 in m.1530:853684 (size=2614) and m.1371:1836275 (size=942) Nov 06 19:39:36 IMAP(kjonca): Error: mdbox /home/kjonca/Mail/1/storage: Duplicate GUID 13517 in m.1530:855355 (size=1990) and m.1371:1837035 (size=1241) Nov 06 19:39:36 IMAP(kjonca): Error: mdbox /home/kjonca/Mail/1/storage: Duplicate GUID 13518 in m.1530:856738 (size=2724) and m.1371:1837913 (size=1772) Nov 06 19:39:36 IMAP(kjonca): Error: mdbox /home/kjonca/Mail/1/storage: Duplicate GUID 13519 in m.1530:858491 (size=2810) and m.1371:1839151 (size=1090) Nov 06 19:39:36 IMAP(kjonca): Error: mdbox /home/kjonca/Mail/1/storage: Duplicate GUID 13520 in m.1530:860313 (size=3775) and m.1371:1839988 (size=1206) Nov 06 19:39:36 IMAP(kjonca): Error: mdbox /home/kjonca/Mail/1/storage: Duplicate GUID 13521 in m.1530:862569 (size=2253) and m.1371:1840884 (size=1491) Nov 06 19:39:36 IMAP(kjonca): Error: mdbox /home/kjonca/Mail/1/storage: Duplicate GUID 13522 in m.1530:864044 (size=6491) and m.1371:1841937 (size=1335) Nov 06 19:39:36 IMAP(kjonca): Error: mdbox /home/kjonca/Mail/1/storage: Duplicate GUID 13523 in m.1530:867783 (size=1824) and m.1371:1842892 (size=1342) Nov 06 19:39:36 IMAP(kjonca): Error: mdbox /home/kjonca/Mail/1/storage: Duplicate GUID 13524 in m.1530:869032 (size=2387) and m.1371:1843849 (size=1941) Nov 06 19:39:36 IMAP(kjonca): Error: mdbox /home/kjonca/Mail/1/storage: Duplicate GUID 13526 in m.1530:872105 (size=2607) and m.1371:1845147 (size=1496) Nov 06 19:39:36 IMAP(kjonca): Error: mdbox /home/kjonca/Mail/1/storage: Duplicate GUID 13528 in m.1530:875255 (size=1967) and m.1371:1846195 (size=1214) [...] # 2.2.devel (42f5200): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.devel (623ae77) # OS: Linux 4.4.0-1-amd64 x86_64 Debian stretch/sid Only "suspected operation" was this sequence: 1. $doveadm mailbox rename RSS RSS-old 2. $doveadm mailbox create RSS 3. --------- copy mails from RSS-old to RSS, and expunge from RSS-old - this operation fails and in dovecot logs were a lot of messages about duplicated guids ---------- 4. $doveadm mailbox delete RSS-old Initially in RSS mailbox were a lot of deleted and expunged mails, but I did not "doveadm purge" I looks like "doveadm force-resync" helps, but I'm not sure if I lost some mails? KJ -- http://stopstopnop.pl/stop_stopnop.pl_o_nas.html Due to circumstances beyond your control, you are master of your fate and captain of your soul.

1 0