- dovecot - dovecot.org

Can sieve feed mails to a pipe like procmail can?
by Peter Kielbasiewicz 13 Apr '17

13 Apr '17

Currently I use procmail to filter mails according to specific tokens and trigger certain actions. For that I feed mails which match certain criteria to a pipe which then post processes the mail right when it arrives. >From what I found I could use a workaround with sieve by storing mails somewhere and then work on those at certain intervals. But this is an awkward solution which causes delays and extra work for locking and post processing. I read that sieve be the more modern system but without the post-processing feature it is no replacement for procmail to me. Peter

2 1

dovecot & iOS
by Dirk Laurenz 12 Apr '17

12 Apr '17

Hello List, i have a working dovecot imap service running with multiple clients running fine, even iOS. What's anying is, that only on iOS ( ) i see a huge bunch of .CONTROL directories - marked grey. It seems to be a copy of the existing folder structure. I don't see this on thunderbird, outlook or even roundcube. Is there any chance to configure dovecot to hide those folders to iOS? Here's some extended Information.... Attached: Screenshot from iOS, where you can see, what i mean dovecot Version: 2.1.7 root@mail01:~# dovecot -n # 2.1.7: /etc/dovecot/dovecot.conf # OS: Linux 4.9.14+ armv6l Debian 7.11 lda_mailbox_autocreate = yes listen = * mail_location = maildir:~/Maildir:INBOX=~/Maildir/Inbox:LAYOUT=fs:CONTROL=~/Maildir/.CONTROL:INDEX=~/Maildir/.INDEX namespace { inbox = yes location = mailbox { special_use = \Drafts name = Drafts } mailbox { special_use = \Junk name = Junk } mailbox { special_use = \Sent name = Sent } mailbox { special_use = \Sent name = Sent Messages } mailbox { special_use = \Trash name = Trash } prefix = name = inbox } passdb { driver = pam } plugin { antispam_debug_target = syslog antispam_signature = X-DSPAM-Signature antispam_spam = SPAM antispam_verbose_debug = 1 } postmaster_address = postmaster@domain protocols = " imap" service replication-notify-fifo { name = aggregator } service anvil-auth-penalty { name = anvil } service auth-worker { name = auth-worker } service auth-client { name = auth } service config { name = config } service dict { name = dict } service login/proxy-notify { name = director } service dns-client { name = dns_client } service doveadm-server { name = doveadm } service imap { name = imap-login } service login/imap { name = imap } service indexer-worker { name = indexer-worker } service indexer { name = indexer } service ipc { name = ipc } service lmtp { name = lmtp } service log-errors { name = log } service pop3 { name = pop3-login } service login/pop3 { name = pop3 } service replicator { name = replicator } service login/ssl-params { name = ssl-params } service stats-mail { name = stats } ssl_cert = </etc/dovecot/fullchain.pem ssl_key = </etc/dovecot/private/privkey.pem userdb { driver = passwd } protocol lmtp { service replication-notify-fifo { name = aggregator } service anvil-auth-penalty { name = anvil } service auth-worker { name = auth-worker } service auth-client { name = auth } service config { name = config } service dict { name = dict } service login/proxy-notify { name = director } service dns-client { name = dns_client } service doveadm-server { name = doveadm } service imap { name = imap-login } service login/imap { name = imap } service indexer-worker { name = indexer-worker } service indexer { name = indexer } service ipc { name = ipc } service lmtp { name = lmtp } service log-errors { name = log } service pop3 { name = pop3-login } service login/pop3 { name = pop3 } service replicator { name = replicator } service login/ssl-params { name = ssl-params } service stats-mail { name = stats } } protocol lda { info_log_path = /var/log/dovecot-lda.log log_path = /var/log/dovecot-lda.log service replication-notify-fifo { name = aggregator } service anvil-auth-penalty { name = anvil } service auth-worker { name = auth-worker } service auth-client { name = auth } service config { name = config } service dict { name = dict } service login/proxy-notify { name = director } service dns-client { name = dns_client } service doveadm-server { name = doveadm } service imap { name = imap-login } service login/imap { name = imap } service indexer-worker { name = indexer-worker } service indexer { name = indexer } service ipc { name = ipc } service lmtp { name = lmtp } service log-errors { name = log } service pop3 { name = pop3-login } service login/pop3 { name = pop3 } service replicator { name = replicator } service login/ssl-params { name = ssl-params } service stats-mail { name = stats } } protocol imap { mail_plugins = antispam service replication-notify-fifo { name = aggregator } service anvil-auth-penalty { name = anvil } service auth-worker { name = auth-worker } service auth-client { name = auth } service config { name = config } service dict { name = dict } service login/proxy-notify { name = director } service dns-client { name = dns_client } service doveadm-server { name = doveadm } service imap { name = imap-login } service login/imap { name = imap } service indexer-worker { name = indexer-worker } service indexer { name = indexer } service ipc { name = ipc } service lmtp { name = lmtp } service log-errors { name = log } service pop3 { name = pop3-login } service login/pop3 { name = pop3 } service replicator { name = replicator } service login/ssl-params { name = ssl-params } service stats-mail { name = stats } }

3 6

Released Pigeonhole v0.4.18 for Dovecot v2.2.29.
by Stephan Bosch 12 Apr '17

12 Apr '17

Hello Dovecot users, Here's the definitive 0.4.18 release. There were no changes since the release candidate. Changelog v0.4.18: + imapsieve plugin: Implemented the copy_source_after rule action. When this is enabled for a mailbox rule, the specified Sieve script is executed for the message in the source mailbox during a "COPY" event. This happens only after the Sieve script that is executed for the corresponding message in the destination mailbox finishes running successfully. + imapsieve plugin: Added non-standard Sieve environment items for the source and destination mailbox. - multiscript: The execution of the discard script had an implicit "keep", rather than an implicit "discard". The release is available as follows: https://pigeonhole.dovecot.org/releases/2.2/dovecot-2.2-pigeonhole-0.4.18.t… https://pigeonhole.dovecot.org/releases/2.2/dovecot-2.2-pigeonhole-0.4.18.t… Refer to http://pigeonhole.dovecot.org and the Dovecot v2.x wiki for more information. Have fun testing this release and don't hesitate to notify me when there are any problems. Regards, -- Stephan Bosch stephan(a)rename-it.nl

1 0

Vpopmail Error
by Bobber 12 Apr '17

12 Apr '17

I'm trying to compile the latest Dovecot (v2.2.29) and when I run make I get this error: > auth-userdb-vpopmail.o: In function `userdb_vpopmail_get_quota': > /usr/local/src/dovecot-2.2.29/src/auth/userdb-vpopmail.c:64: undefined > reference to `var_expand_table_build' > collect2: error: ld returned 1 exit status > Makefile:932: recipe for target 'auth' failed > make[3]: *** [auth] Error 1 > make[3]: Leaving directory '/usr/local/src/dovecot-2.2.29/src/auth' > Makefile:496: recipe for target 'all-recursive' failed > make[2]: *** [all-recursive] Error 1 > make[2]: Leaving directory '/usr/local/src/dovecot-2.2.29/src' > Makefile:619: recipe for target 'all-recursive' failed > make[1]: *** [all-recursive] Error 1 > make[1]: Leaving directory '/usr/local/src/dovecot-2.2.29' > Makefile:463: recipe for target 'all' failed > make: *** [all] Error 2 I'm using Debian Jessie and it's up to date. Just to make sure it wasn't something in Jessie I went back into v2.2.28 (which I've been using since it was released) and did a clean build successfully. I've never had any problems compiling dovecot up until now. Any ideas on how to fix this? -- *Bob Wooldridge* Blog: http://kc0dxf.net/blog/

4 8

v2.2.29.rc1 released
by Timo Sirainen 11 Apr '17

11 Apr '17

http://dovecot.org/releases/2.2/rc/dovecot-2.2.29.rc1.tar.gz http://dovecot.org/releases/2.2/rc/dovecot-2.2.29.rc1.tar.gz.sig Planning to release v2.2.29 on Monday. Please find and report any bugs before that. * When Dovecot encounters an internal error, it logs the real error and usually logs another line saying what function failed. Previously the second log line's error message was a rather uninformative "Internal error occurred. Refer to server log for more information." Now the real error message is duplicated in this second log line. * lmtp: If a delivery has multiple recipients, run autoexpunging only for the last recipient. This avoids a problem where a long autoexpunge run causes LMTP client to timeout between the DATA replies, resulting in duplicate mail deliveries. * config: Don't stop the process due to idling. Otherwise the configuration is reloaded when the process restarts. * mail_log plugin: Differentiate autoexpunges from regular expunges * imapc: Use LOGOUT to cleanly disconnect from server. * lib-http: Internal status codes (>9000) are no longer visible in logs * director: Log vhost count changes and HOST-UP/DOWN + quota: Add plugin { quota_max_mail_size } setting to limit the maximum individual mail size that can be saved. + imapc: Add imapc_features=delay-login. If set, connecting to the remote IMAP server isn't done until it's necessary. + imapc: Add imapc_connection_retry_count and imapc_connection_retry_interval settings. + imap, pop3, indexer-worker: Add (deinit) to process title before autoexpunging runs. + Added %{encrypt} and %{decrypt} variables + imap/pop3 proxy: Log proxy state in errors as human-readable string. + imap/pop3-login: All forward_* extra fields returned by passdb are sent to the next hop when proxying using ID/XCLIENT commands. On the receiving side these fields are imported and sent to auth process where they're accessible via %{passdb:forward_*}. This is done only if the sending IP address matches login_trusted_networks. + imap-login: If imap_id_retain=yes, send the IMAP ID string to auth process. %{client_id} expands to it in auth process. The ID string is also sent to the next hop when proxying. - fts-tika: Fixed crash when parsing attachment without Content-Disposition header. Broken by 2.2.28. - trash plugin was broken in 2.2.28 - auth: When passdb/userdb lookups were done via auth-workers, too much data was added to auth cache. This could have resulted in wrong replies when using multiple passdbs/userdbs. - auth: passdb { skip & mechanisms } were ignored for the first passdb - oauth2: Various fixes, including fixes to crashes - dsync: Large Sieve scripts (or other large metadata) weren't always synced. - Index rebuild (e.g. doveadm force-resync) set all mails as \Recent - imap-hibernate: %{userdb:*} wasn't expanded in mail_log_prefix - doveadm: Exit codes weren't preserved when proxying commands via doveadm-server. Almost all errors used exit code 75 (tempfail). - ACLs weren't applied to not-yet-existing autocreated mailboxes. - Fixed a potential crash when parsing a broken message header. - cassandra: Fallback consistency settings weren't working correctly. - doveadm director status <user>: "Initial config" was always empty - imapc: Various reconnection fixes.

3 10

How to use quota with dovecot
by Mik J 11 Apr '17

11 Apr '17

Hello, I would like to use quotas with dovecot and things are not clear to me. I read this page https://wiki2.dovecot.org/Quota 1) I did this # ls /usr/local/lib/dovecot/lib10_quota_plugin.so /usr/local/lib/dovecot/lib10_quota_plugin.so # grep mail_plugins /etc/dovecot/conf.d/10-mail.conf mail_plugins = notify replication quota Then the page tells about 20-imap.conf but an explanation is written # Space separated list of plugins to load (default is global mail_plugins). So what is that default global mail_plugins ? Is it the one coming from 10-mail.conf ? 2) I tried both use this mail_plugins = $mail_plugins quota in 20-imap.conf or comment it. And restarted dovecot each time Then commented out in 90-quota.conf quota_rule = *:storage=1G quota_rule2 = Trash:storage=+100M quota_grace = 10%% } But I have this message # doveadm quota recalc -u user(a)mydomain.org doveadm(user(a)mydomain.org): Error: Quota not enabled Does anyone knows why ?

4 5

v2.2.29 released
by Timo Sirainen 11 Apr '17

11 Apr '17

https://dovecot.org/releases/2.2/dovecot-2.2.29.tar.gz https://dovecot.org/releases/2.2/dovecot-2.2.29.tar.gz.sig * passdb/userdb dict: Don't double-expand %variables in keys. If dict was used as the authentication passdb, using specially crafted %variables in the username could be used to cause DoS (CVE-2017-2669) * When Dovecot encounters an internal error, it logs the real error and usually logs another line saying what function failed. Previously the second log line's error message was a rather uninformative "Internal error occurred. Refer to server log for more information." Now the real error message is duplicated in this second log line. * lmtp: If a delivery has multiple recipients, run autoexpunging only for the last recipient. This avoids a problem where a long autoexpunge run causes LMTP client to timeout between the DATA replies, resulting in duplicate mail deliveries. * config: Don't stop the process due to idling. Otherwise the configuration is reloaded when the process restarts. * mail_log plugin: Differentiate autoexpunges from regular expunges * imapc: Use LOGOUT to cleanly disconnect from server. * lib-http: Internal status codes (>9000) are no longer visible in logs * director: Log vhost count changes and HOST-UP/DOWN + quota: Add plugin { quota_max_mail_size } setting to limit the maximum individual mail size that can be saved. + imapc: Add imapc_features=delay-login. If set, connecting to the remote IMAP server isn't done until it's necessary. + imapc: Add imapc_connection_retry_count and imapc_connection_retry_interval settings. + imap, pop3, indexer-worker: Add (deinit) to process title before autoexpunging runs. + Added %{encrypt} and %{decrypt} variables + imap/pop3 proxy: Log proxy state in errors as human-readable string. + imap/pop3-login: All forward_* extra fields returned by passdb are sent to the next hop when proxying using ID/XCLIENT commands. On the receiving side these fields are imported and sent to auth process where they're accessible via %{passdb:forward_*}. This is done only if the sending IP address matches login_trusted_networks. + imap-login: If imap_id_retain=yes, send the IMAP ID string to auth process. %{client_id} expands to it in auth process. The ID string is also sent to the next hop when proxying. + passdb imap: Use ssl_client_ca_* settings for CA validation. - fts-tika: Fixed crash when parsing attachment without Content-Disposition header. Broken by 2.2.28. - trash plugin was broken in 2.2.28 - auth: When passdb/userdb lookups were done via auth-workers, too much data was added to auth cache. This could have resulted in wrong replies when using multiple passdbs/userdbs. - auth: passdb { skip & mechanisms } were ignored for the first passdb - oauth2: Various fixes, including fixes to crashes - dsync: Large Sieve scripts (or other large metadata) weren't always synced. - Index rebuild (e.g. doveadm force-resync) set all mails as \Recent - imap-hibernate: %{userdb:*} wasn't expanded in mail_log_prefix - doveadm: Exit codes weren't preserved when proxying commands via doveadm-server. Almost all errors used exit code 75 (tempfail). - ACLs weren't applied to not-yet-existing autocreated mailboxes. - Fixed a potential crash when parsing a broken message header. - cassandra: Fallback consistency settings weren't working correctly. - doveadm director status <user>: "Initial config" was always empty - imapc: Various reconnection fixes.

4 6

How to migration my mails from another server ?
by Mik J 10 Apr '17

10 Apr '17

Hello, I would like to host my mails and I would like to retrieve my existing mailbox content from my ISP My ISP ====== I don't have root access on the server The server seem to use Dovecot according to the banner. My machine ========== I have root access on the server I use Dovecot 2.2.21 I use Maildir I read this page multiple times but it's not clear to me https://wiki2.dovecot.org/Migration/Dsync "Set up configuration for the IMAP server you wish to migrate from" Is it my ISP's server or my server ? In which configuration file should I do this ? The same for this option dsync_features = empty-header-workaroundwhere is it supposed to be configured ? My most important case is quite "simple": the mailboxes (there are 2 or 3) I want to migrate don't exist on my machine, so there is no such problems as merge existing mails. Will this migration use imap and retrieve the content of the mails ? Will it use port 143 or 993 ? I'll use the backup option I have another case which there are mails on both servers. So I would like to keep existing mails on my machine. I'll use the sync -1 option ? Thank you

3 3

Re: abrt reported "imap killed by SIGBUS"
by Hongying Liu 10 Apr '17

10 Apr '17

Sorry for late response. This issue occurs ran randomly. So I don't know how to run valgrind command. 2017-04-10 17:14 GMT+08:00 Hongying Liu <hongyliu(a)redhat.com>: > Sorry for late response. > > This issue occurs ran randomly. So I don't know how to run valgrind > command. > > I upload the coredump. > > The version of dovecot is dovecot-2.2.10-7.el7.x86_64. > > 2017-04-07 14:07 GMT+08:00 Aki Tuomi <aki.tuomi(a)dovecot.fi>: > >> Please keep responses on list. >> >> Can you please run valgrind on this, as it appears to be some sort of >> memory corruption issue. >> >> Aki >> >> > On April 7, 2017 at 5:37 AM Hongying Liu <hongyliu(a)redhat.com> wrote: >> > >> > >> > Thanks for your response. >> > >> > (gdb) p cache >> > $1 = (struct mail_cache *) 0x7fc4a811a320 >> > (gdb) p cache->hdr >> > $2 = (const struct mail_cache_header *) 0x7fc4a6ddb000 >> > (gdb) p cache->hdr->file_seq >> > Cannot access memory at address 0x7fc4a6ddb008 <---- >> > (gdb) p reset_id >> > $3 = 1488892251 >> > >> > >> > 2017-04-06 19:34 GMT+08:00 Aki Tuomi <aki.tuomi(a)dovecot.fi>: >> > >> > > Hi! >> > > >> > > Responses in middle. >> > > >> > > Aki >> > > >> > > On 06.04.2017 06:05, Hongying Liu wrote: >> > > > Hi sbr-services, >> > > > >> > > > Could you give me some idea? >> > > > >> > > > ### abrt reported the error as below. >> > > > [root@cupop4 log]# abrt-cli list --since 1488267244 id >> > > > ad716dbfd3a68bbe0f055e32ebfe562f4f75df43 >> > > > reason: imap killed by SIGBUS >> > > > time: Sun Mar 19 2017 10:58:27 AM JST >> > > > cmdline: dovecot/imap >> > > > package: dovecot-2.2.10-7.el7 >> > > > uid: 80180 (acaa2325) >> > > > count: 2 >> > > > Directory: /var/spool/abrt/ccpp-2017-03-19-10:58:27-4904 >> > > > 'abrt-cli report を実行する/var/spool/abrt/ccpp-2017 >> -03-19-10:58:27-4904' >> > > > >> > > > >> > > > ### /var/log/messages >> > > > Mar 19 10:58:27 cupop4 abrt-hook-ccpp: Process 4904 (imap) of user >> 80180 >> > > > killed by SIGBUS - dumping core >> > > > >> > > > And, there are lots of ldap error in /var/log/messages. Dovecot >> uses the >> > > > ldap as userdb and passwddb. >> > > > Is the ldap error related to imap crash? >> > > > >> > > > Mar 19 10:58:21 cupop4 nslcd[1534]: [a378de] >> <group/member="postfix"> >> > > > ldap_result() failed: Invalid DN syntax: Invalid DN >> > > >> > > This looks like an invalid DN syntax. >> > > >> > > > >> > > > ### /var/log/dovecot >> > > > >> > > > Mar 19 10:58:27 cupop4 dovecot: imap(acaa2325): Fatal: master: >> > > > service(imap): child 4904 killed with signal 7 (core dumped) >> > > > >> > > Can you do p cache, p cache->hdr, p cache->hdr->file_seq and p >> reset_id >> > > >> > > > ### gdb >> > > > >> > > > Core was generated by `dovecot/imap'. >> > > > Program terminated with signal 7, Bus error. >> > > > #0 0x00007fc4a69f293e in mail_cache_lookup_offset >> (cache=0x7fc4a811a320, >> > > > view=<optimized out>, seq=<optimized out>, offset_r=offset_r@entry >> > > > =0x7ffe23a98900) >> > > > at mail-cache-lookup.c:95 >> > > > 95 while (cache->hdr->file_seq != reset_id) { >> > > > (gdb) bt >> > > > #0 0x00007fc4a69f293e in mail_cache_lookup_offset >> (cache=0x7fc4a811a320, >> > > > view=<optimized out>, seq=<optimized out>, offset_r=offset_r@entry >> > > > =0x7ffe23a98900) >> > > > at mail-cache-lookup.c:95 >> > > > #1 0x00007fc4a69f2afa in mail_cache_lookup_iter_init >> > > > (view=view@entry=0x7fc4a81332b0, >> > > > seq=<optimized out>, ctx_r=ctx_r@entry=0x7ffe23a988e0) >> > > > at mail-cache-lookup.c:154 >> > > > #2 0x00007fc4a69f2f8f in mail_cache_seq (seq=<optimized out>, >> > > > view=0x7fc4a81332b0) at mail-cache-lookup.c:322 >> > > > #3 mail_cache_field_exists (view=view@entry=0x7fc4a81332b0, >> > > seq=seq@entry=760, >> > > > field=field@entry=4) at mail-cache-lookup.c:352 >> > > > #4 0x00007fc4a69f3151 in mail_cache_lookup_field >> (view=0x7fc4a81332b0, >> > > > dest_buf=dest_buf@entry=0x7ffe23a98a00, seq=760, >> > > field_idx=field_idx@entry >> > > > =4) >> > > > at mail-cache-lookup.c:413 >> > > > #5 0x00007fc4a69d9439 in index_mail_cache_lookup_field >> > > > (mail=mail@entry=0x7fc4a8128cd0, >> > > > buf=buf@entry=0x7ffe23a98a00, field_idx=field_idx@entry=4) >> > > > at index-mail.c:68 >> > > > #6 0x00007fc4a69d94a7 in index_mail_get_fixed_field >> > > (mail=0x7fc4a8128cd0, >> > > > field=<optimized out>, data=<optimized out>, data_size=8) at >> > > > index-mail.c:130 >> > > > #7 0x00007fc4a69d9fed in index_mail_get_cached_virtual_size >> > > > (mail=mail@entry=0x7fc4a8128cd0, size_r=size_r@entry=0x7ffe23a98b20) >> at >> > > > index-mail.c:403 >> > > > #8 0x00007fc4a6987c1b in maildir_mail_get_virtual_size >> > > > (_mail=0x7fc4a8128cd0, size_r=0x7ffe23a98b20) at maildir-mail.c:388 >> > > > #9 0x00007fc4a69d9719 in index_mail_update_access_parts >> > > > (mail=mail@entry=0x7fc4a8128cd0) >> > > > at index-mail.c:1490 >> > > > #10 0x00007fc4a69dbb93 in index_mail_set_seq (_mail=0x7fc4a8128cd0, >> > > > seq=760, saving=<optimized out>) at index-mail.c:1521 >> > > > #11 0x00007fc4a69e28cb in search_more_with_mail >> (mail=0x7fc4a8128cd0, >> > > > ctx=0x7fc4a8132730) at index-search.c:1507 >> > > > #12 search_more_with_prefetching (mail_r=<optimized out>, >> ctx=<optimized >> > > > out>) at index-search.c:1579 >> > > > #13 search_more (ctx=ctx@entry=0x7fc4a8132730, >> > > > mail_r=mail_r@entry=0x7ffe23a98c20) >> > > > at index-search.c:1650 >> > > > #14 0x00007fc4a69e2ff4 in index_storage_search_next_nonblock >> > > > (_ctx=0x7fc4a8132730, mail_r=0x7fc4a81120d8, >> tryagain_r=0x7ffe23a98c87) >> > > at >> > > > index-search.c:1674 >> > > > #15 0x00007fc4a69bc4ef in mailbox_search_next_nonblock >> > > > (ctx=ctx@entry=0x7fc4a8132730, >> > > > mail_r=mail_r@entry=0x7fc4a81120d8, >> > > > tryagain_r=tryagain_r@entry=0x7ffe23a98c87) at >> mail-storage.c:1787 >> > > > #16 0x00007fc4a69bc55d in mailbox_search_next (ctx=0x7fc4a8132730, >> > > > mail_r=mail_r@entry=0x7fc4a81120d8) at mail-storage.c:1773 >> > > > #17 0x00007fc4a6e97874 in imap_fetch_more_int (ctx=ctx@entry >> > > =0x7fc4a8112078, >> > > > cancel=false) at imap-fetch.c:479 >> > > > #18 0x00007fc4a6e98852 in imap_fetch_more (ctx=0x7fc4a8112078, >> > > > cmd=cmd@entry=0x7fc4a8111ed0) >> > > > at imap-fetch.c:556 >> > > > #19 0x00007fc4a6e8c17d in cmd_fetch (cmd=0x7fc4a8111ed0) at >> > > cmd-fetch.c:284 >> > > > #20 0x00007fc4a6e9601c in command_exec (cmd=cmd@entry=0x7fc4a8111ed0) >> at >> > > > imap-commands.c:158 >> > > > #21 0x00007fc4a6e94f1f in client_command_input (cmd=cmd@entry >> > > =0x7fc4a8111ed0) >> > > > at imap-client.c:780 >> > > > #22 0x00007fc4a6e95005 in client_command_input (cmd=0x7fc4a8111ed0) >> at >> > > > imap-client.c:841 >> > > > #23 0x00007fc4a6e952fd in client_handle_next_command >> > > > (remove_io_r=<synthetic pointer>, client=0x7fc4a8111530) at >> > > > imap-client.c:879 >> > > > #24 client_handle_input (client=client@entry=0x7fc4a8111530) at >> > > > imap-client.c:891 >> > > > #25 0x00007fc4a6e956c5 in client_input (client=0x7fc4a8111530) at >> > > > imap-client.c:933 >> > > > #26 0x00007fc4a66e1a87 in io_loop_call_io (io=0x7fc4a811edd0) at >> > > > ioloop.c:388 >> > > > #27 0x00007fc4a66e290f in io_loop_handler_run >> > > > (ioloop=ioloop@entry=0x7fc4a80fc750) >> > > > at ioloop-epoll.c:220 >> > > > #28 0x00007fc4a66e15d8 in io_loop_run (ioloop=0x7fc4a80fc750) at >> > > > ioloop.c:412 >> > > > #29 0x00007fc4a668e9e3 in master_service_run >> (service=0x7fc4a80fc5e0, >> > > > callback=callback@entry=0x7fc4a6e9ed70 <client_connected>) at >> > > > master-service.c:571 >> > > > #30 0x00007fc4a6e89324 in main (argc=1, argv=0x7fc4a80fc390) at >> > > main.c:400 >> > > > >> > > > Thank you. >> > > > >> > > > Best regards, >> > > > Hongying Liu >> > > >> > > >> > >

1 0

[Bug] FTS invalid address parsing
by azurit＠pobox.sk 10 Apr '17

10 Apr '17

Hi, i found another bug in FTS while parsing quoted-printable/base64-encoded sender's name inside 'From' header (again, i was figuring out why some of messages cannot be searched). Header: From: =?UTF-8?Q?A=2CB?= <test(a)example.com> Data send to Solr by Dovecot: <field name="from">A@, B &lt;test(a)example.com&gt;</field> Header: From: =?UTF-8?Q?A_B=2CC?= <test(a)example.com> Data send to Solr by Dovecot: <field name="from">A@</field> Header: From: =?UTF-8?B?QSBCLEMK?= <test(a)example.com> Data send to Solr by Dovecot: <field name="from">A@</field> Dovecot 2.2.27. azur

2 2

[Bug] FTS double escaping
by azurit＠pobox.sk 09 Apr '17

09 Apr '17

Hi, i'm trying to resolve few problems with indexing 'From' headers using FTS/Solr. I was tcpdumping the communication between Dovecot and Jetty/Solr and noticed that 'From' headers, which includes also sender's name, are double escaped. This is what was Dovecot sending to Solr: </field><field name="from">Name Surname &lt;test(a)example.com&gt;</field></doc></add> As you can see, characters < and > were escaped to < and > which were, again, escaped to &lt; and &gt;. This is doing problems while trying to index whole e-mail address, as Solr sees it as '<test(a)example.com>'. I spend hours trying to figure out why i'm able to search in all parts of e-mail addresses but searching for full and exact e-mail address was successfull ONLY for messages which doesn't include sender's name in 'From' header. Finally, after i found this bug, this fixed all search problems: <filter class="solr.PatternReplaceFilterFactory" pattern="&lt;" replacement=""/> <filter class="solr.PatternReplaceFilterFactory" pattern="&gt;" replacement=""/> I hope that, at least, this bug, reported by me, will be fixed. Thank you. azur

3 5

sieve does not seem to be working
by Robert Moskowitz 09 Apr '17

09 Apr '17

my local.conf has: # 90-sieve.conf plugin { sieve_before = /home/sieve/globalfilter.sieve } and cat /home/sieve/globalfilter.sieve require ["fileinto","mailbox"]; if anyof ( header :contains "X-Spam-Flag" "YES", header :contains "subject" "***SPAM***" ) { fileinto :create "Spam"; } There IS a globalfilter.svbin when I tried: sendmail -i testit3(a)test.htt-consult.com < sample-spam-GTUBE-junk.txt amavis is flagging it as ***Spam*** but it stays in inbox. So I tried: sieve-test -e -l /home/vmail/test.htt-consult.com/testit3/ /home/sieve/globalfilter.sieve /home/vmail/test.htt-consult.com/testit3/cur/1491512409.M371278P6513.z9m9z.test.htt-consult.com\,S\=1823\,W\=1868\:2\, info: msgid=<GTUBE1.1010101(a)example.net>: stored mail into mailbox 'Spam'. sieve-test(root): Info: final result: success And it DID get copied to Spam, not moved. I am now seeing it in inbox and Spam. Of course ownership on the message in Spam were wrong (root:root instead of vmail:mail, but I fixed that). So two questions, probably linked: Why did sieve not work. Is the subject test case sensitive? If it is case sensitive, why did the sieve-test work? thanks

2 2

Pigeonhole Sieve Extprograms Plugin
by KT Walrus 09 Apr '17

09 Apr '17

Just discovered the Pigeonhole Sieve Extprograms plugin (https://wiki2.dovecot.org/Pigeonhole/Sieve/Plugins/Extprograms <https://wiki2.dovecot.org/Pigeonhole/Sieve/Plugins/Extprograms>)… I currently have Postfix configured to run a script to store all incoming messages into a Mysql DB and a batch job that retrieves the messages in the DB, processes them and delivers them to the recipients' Dovecot servers. Seems to me it might be better to have Postfix deliver all incoming messages directly to a single Dovecot mailbox and use this Sieve plugin to do the whole job of updating the DB, processing the message, and delivering to the recipients. Also, I have a need to implement updating the DB when the recipient reads a message for the first time (setting the \Seen flag). Would this work best to execute a script using this Sieve plugin from a IMAP Sieve script that watches for \Seen flag changes? This might be a whole lot better than the way I was thinking of doing it before. I’m basically implementing mailing lists where the senders receive a notification reply with a link to a web page where the message may be edited/deleted before it is sent to recipients (after a fixed amount of time has elapsed). This gives the sender the opportunity to change his mind before it is too late or to send to recipients immediately (by marking the message as Urgent). Also, even after the message has been sent out, I want to allow the sender to be able to delete it in the recipients mailboxes if they have not read it yet (downloaded it to their email client) or to see which recipients have read the message (and when they read/downloaded it for the first time). Both the sender and the recipients will have Dovecot mailboxes so I want to give more control over the messages for their entire lifetimes (both for senders and for recipients) than normal email does. Any thoughts? Kevin

1 0

Released Pigeonhole v0.4.18.rc1 for Dovecot v2.2.29.rc1.
by Stephan Bosch 09 Apr '17

09 Apr '17

Hello Dovecot users, This is a rather small release. It fixes one important bug in the new discard script feature. It also adds a couple of new features for IMAPSieve. Changelog v0.4.18: + imapsieve plugin: Implemented the copy_source_after rule action. When this is enabled for a mailbox rule, the specified Sieve script is executed for the message in the source mailbox during a "COPY" event. This happens only after the Sieve script that is executed for the corresponding message in the destination mailbox finishes running successfully. + imapsieve plugin: Added non-standard Sieve environment items for the source and destination mailbox. - multiscript: The execution of the discard script had an implicit "keep", rather than an implicit "discard". The release is available as follows: http://pigeonhole.dovecot.org/releases/2.2/rc/dovecot-2.2-pigeonhole-0.4.18… http://pigeonhole.dovecot.org/releases/2.2/rc/dovecot-2.2-pigeonhole-0.4.18… Refer to http://pigeonhole.dovecot.org and the Dovecot v2.x wiki for more information. Have fun testing this release candidate and don't hesitate to notify me when there are any problems. Regards, -- Stephan Bosch stephan(a)rename-it.nl

1 0

Updating mysql db when messages first read by IMAP user
by KT Walrus 09 Apr '17

09 Apr '17

I need to implement updating a mysql db when the \SEEN flag is set by IMAP. New message delivery is done by having Postfix store all new inbound messages in a mysql db and a batch job watching the db for new messages and delivering them to the correct Dovecot server for the recipients. The batch job leaves a log entry in the db (for each recipient) with the current timestamp and adds a header with the log id to the outgoing message that is sent to Dovecot. The log table has a column for the first read timestamp which is set to 0 initially. I plan on implementing a Sieve IMAP script that watches for changes to the \SEEN flag and sends a mailto: notify message that contains the log id (from the message header) and the current date to a mail address dedicated for keep track of \SEEN flag changes. The notify message will be delivered to this mail address where a batch job watches that mail address and updates the db for the log id in the notify message with the timestamp and the current date if the row in the log table has a first read timestamp of 0. I plan on providing a web page that the sender can use to see whether the messages they have sent have been seen by the recipients. The web page will show other info too, but the part that I need to implement next is updating the db when a sent message has been read by the recipients of the message. Is this a good way to do this? Or, is there a better way than using an IMAP Sieve script to send notify messages? Is there any other way to have a Sieve script update a mysql database? Or, is there some other mechanism in Dovecot to use instead of an IMAP Sieve script? Kevin

1 0

IMAPSieve Changed flags cause?
by MRob 09 Apr '17

09 Apr '17

RFC 6785 says I should be able to run scripts when a command changes flags on a message but I can't understand what to put in imapsieve_mailboxXXX_causes. Dovecot logs something like STORE as an invalid cause. How do I run an administrator Sieve script caused from change in flags?

2 5

LAYOUT=fs and subfolders listing
by Dovecot＠9livesdata 07 Apr '17

07 Apr '17

dovecot-2.2.28-1.el6_31.wing.x86_64 I've created this public shared namespace with namespace public2 { type = public separator = . prefix = Public2. location = maildir:/mail/public2:INDEX=/mail/%u/public:LAYOUT=fs:DIRNAME=.store subscriptions = no } and I'm using the "imap_client_workarounds = tb-extra-mailbox-sep" and filesystem structure listed at the end. The problem is that with this configuration thunderbird (and roundcubemail) shows the Public2 namespace but empty - without any folders. I've tried with another DIRNAME=StoR - same effect If I will not use DIRNAME at all(and no .stor directories) TB sees the f1 f2 folders but not the f2/s1 subfolder. Just like it would not list any subfolders for subscription. Within TB I can create subfolder say f1/mysub1 but after it's unsubscribed cannot be subscribed again(not shown in listing) Can You provide any hints? I can live without the DIRNAME= but it has to list subfolders for subscription. BTW: it works well without LAYOUT=fs - but it's kind of requirement here. /mail/public2/: drwxrwsr-x 4 nobody havemail 4096 Apr 7 15:07 f1 drwxrwsr-x 3 nobody havemail 4096 Apr 7 15:02 f2 /mail/public2/f1: -rw-r--r-- 1 root havemail 42 Apr 7 15:07 dovecot-acl -r--r--r-- 1 nobody havemail 0 Oct 14 2015 dovecot-shared -rw-rw-r-- 1 nobody havemail 0 Oct 15 2015 dovecot-uidlist drwxrwsr-x 3 nobody havemail 4096 Apr 7 15:02 s1 drwxrws--- 5 nobody havemail 4096 Apr 7 15:02 .store /mail/public2/f1/s1: -rw-r--r-- 1 root havemail 40 Oct 16 2015 dovecot-acl -r--r--r-- 1 nobody havemail 0 Oct 14 2015 dovecot-shared -rw-rw-r-- 1 nobody havemail 0 Oct 15 2015 dovecot-uidlist drwxrws--- 5 nobody havemail 4096 Apr 7 15:02 .store /mail/public2/f1/s1/.store: drwxrws--- 2 nobody havemail 4096 Oct 15 2015 cur drwxrws--- 2 nobody havemail 4096 Oct 15 2015 new drwxrws--- 2 nobody havemail 4096 Oct 15 2015 tmp /mail/public2/f1/.store: drwxrws--- 2 nobody havemail 4096 Oct 15 2015 cur drwxrws--- 2 nobody havemail 4096 Oct 15 2015 new drwxrws--- 2 nobody havemail 4096 Oct 15 2015 tmp /mail/public2/f2: -rw-r--r-- 1 root havemail 40 Oct 16 2015 dovecot-acl -r--r--r-- 1 nobody havemail 0 Oct 14 2015 dovecot-shared -rw-rw-r-- 1 nobody havemail 0 Oct 15 2015 dovecot-uidlist drwxrws--- 5 nobody havemail 4096 Apr 7 15:02 .store /mail/public2/f2/.store: drwxrws--- 2 nobody havemail 4096 Oct 15 2015 cur drwxrws--- 2 nobody havemail 4096 Oct 15 2015 new drwxrws--- 2 nobody havemail 4096 Oct 15 2015 tmp

1 0

Running sievec as user vmail
by Robert Moskowitz 07 Apr '17

07 Apr '17

My sieve problem ended up a permissions problem. I ran sievec as root and .svbin needs vmail:mail ownership. I could always just add the chown command to my process, but I wonder if there is some 'clean' way to run sievec as user vmail while logged in as root? thanks

2 2

Doubt with imap/imap-login processes in proxy server
by Angel L. Mateo 07 Apr '17

07 Apr '17

Hi, I have a question I have not cleared after reading https://wiki.dovecot.org/LoginProcess. I'm developing a proxy server (without director, because the backend server is specified by a ldap lookup). My question is: the limit of imap (or pop3) concurrently users that the proxy can handle is determined by the imap-login limit or the imap one? -- Angel L. Mateo Martínez Sección de Telemática Área de Tecnologías de la Información y las Comunicaciones Aplicadas (ATICA) http://www.um.es/atica Tfo: 868889150 Fax: 868888337

2 2

Re: abrt reported "imap killed by SIGBUS"
by Aki Tuomi 07 Apr '17

07 Apr '17

Please keep responses on list. Can you please run valgrind on this, as it appears to be some sort of memory corruption issue. Aki > On April 7, 2017 at 5:37 AM Hongying Liu <hongyliu(a)redhat.com> wrote: > > > Thanks for your response. > > (gdb) p cache > $1 = (struct mail_cache *) 0x7fc4a811a320 > (gdb) p cache->hdr > $2 = (const struct mail_cache_header *) 0x7fc4a6ddb000 > (gdb) p cache->hdr->file_seq > Cannot access memory at address 0x7fc4a6ddb008 <---- > (gdb) p reset_id > $3 = 1488892251 > > > 2017-04-06 19:34 GMT+08:00 Aki Tuomi <aki.tuomi(a)dovecot.fi>: > > > Hi! > > > > Responses in middle. > > > > Aki > > > > On 06.04.2017 06:05, Hongying Liu wrote: > > > Hi sbr-services, > > > > > > Could you give me some idea? > > > > > > ### abrt reported the error as below. > > > [root@cupop4 log]# abrt-cli list --since 1488267244 id > > > ad716dbfd3a68bbe0f055e32ebfe562f4f75df43 > > > reason: imap killed by SIGBUS > > > time: Sun Mar 19 2017 10:58:27 AM JST > > > cmdline: dovecot/imap > > > package: dovecot-2.2.10-7.el7 > > > uid: 80180 (acaa2325) > > > count: 2 > > > Directory: /var/spool/abrt/ccpp-2017-03-19-10:58:27-4904 > > > 'abrt-cli report を実行する/var/spool/abrt/ccpp-2017-03-19-10:58:27-4904' > > > > > > > > > ### /var/log/messages > > > Mar 19 10:58:27 cupop4 abrt-hook-ccpp: Process 4904 (imap) of user 80180 > > > killed by SIGBUS - dumping core > > > > > > And, there are lots of ldap error in /var/log/messages. Dovecot uses the > > > ldap as userdb and passwddb. > > > Is the ldap error related to imap crash? > > > > > > Mar 19 10:58:21 cupop4 nslcd[1534]: [a378de] <group/member="postfix"> > > > ldap_result() failed: Invalid DN syntax: Invalid DN > > > > This looks like an invalid DN syntax. > > > > > > > > ### /var/log/dovecot > > > > > > Mar 19 10:58:27 cupop4 dovecot: imap(acaa2325): Fatal: master: > > > service(imap): child 4904 killed with signal 7 (core dumped) > > > > > Can you do p cache, p cache->hdr, p cache->hdr->file_seq and p reset_id > > > > > ### gdb > > > > > > Core was generated by `dovecot/imap'. > > > Program terminated with signal 7, Bus error. > > > #0 0x00007fc4a69f293e in mail_cache_lookup_offset (cache=0x7fc4a811a320, > > > view=<optimized out>, seq=<optimized out>, offset_r=offset_r@entry > > > =0x7ffe23a98900) > > > at mail-cache-lookup.c:95 > > > 95 while (cache->hdr->file_seq != reset_id) { > > > (gdb) bt > > > #0 0x00007fc4a69f293e in mail_cache_lookup_offset (cache=0x7fc4a811a320, > > > view=<optimized out>, seq=<optimized out>, offset_r=offset_r@entry > > > =0x7ffe23a98900) > > > at mail-cache-lookup.c:95 > > > #1 0x00007fc4a69f2afa in mail_cache_lookup_iter_init > > > (view=view@entry=0x7fc4a81332b0, > > > seq=<optimized out>, ctx_r=ctx_r@entry=0x7ffe23a988e0) > > > at mail-cache-lookup.c:154 > > > #2 0x00007fc4a69f2f8f in mail_cache_seq (seq=<optimized out>, > > > view=0x7fc4a81332b0) at mail-cache-lookup.c:322 > > > #3 mail_cache_field_exists (view=view@entry=0x7fc4a81332b0, > > seq=seq@entry=760, > > > field=field@entry=4) at mail-cache-lookup.c:352 > > > #4 0x00007fc4a69f3151 in mail_cache_lookup_field (view=0x7fc4a81332b0, > > > dest_buf=dest_buf@entry=0x7ffe23a98a00, seq=760, > > field_idx=field_idx@entry > > > =4) > > > at mail-cache-lookup.c:413 > > > #5 0x00007fc4a69d9439 in index_mail_cache_lookup_field > > > (mail=mail@entry=0x7fc4a8128cd0, > > > buf=buf@entry=0x7ffe23a98a00, field_idx=field_idx@entry=4) > > > at index-mail.c:68 > > > #6 0x00007fc4a69d94a7 in index_mail_get_fixed_field > > (mail=0x7fc4a8128cd0, > > > field=<optimized out>, data=<optimized out>, data_size=8) at > > > index-mail.c:130 > > > #7 0x00007fc4a69d9fed in index_mail_get_cached_virtual_size > > > (mail=mail@entry=0x7fc4a8128cd0, size_r=size_r@entry=0x7ffe23a98b20) at > > > index-mail.c:403 > > > #8 0x00007fc4a6987c1b in maildir_mail_get_virtual_size > > > (_mail=0x7fc4a8128cd0, size_r=0x7ffe23a98b20) at maildir-mail.c:388 > > > #9 0x00007fc4a69d9719 in index_mail_update_access_parts > > > (mail=mail@entry=0x7fc4a8128cd0) > > > at index-mail.c:1490 > > > #10 0x00007fc4a69dbb93 in index_mail_set_seq (_mail=0x7fc4a8128cd0, > > > seq=760, saving=<optimized out>) at index-mail.c:1521 > > > #11 0x00007fc4a69e28cb in search_more_with_mail (mail=0x7fc4a8128cd0, > > > ctx=0x7fc4a8132730) at index-search.c:1507 > > > #12 search_more_with_prefetching (mail_r=<optimized out>, ctx=<optimized > > > out>) at index-search.c:1579 > > > #13 search_more (ctx=ctx@entry=0x7fc4a8132730, > > > mail_r=mail_r@entry=0x7ffe23a98c20) > > > at index-search.c:1650 > > > #14 0x00007fc4a69e2ff4 in index_storage_search_next_nonblock > > > (_ctx=0x7fc4a8132730, mail_r=0x7fc4a81120d8, tryagain_r=0x7ffe23a98c87) > > at > > > index-search.c:1674 > > > #15 0x00007fc4a69bc4ef in mailbox_search_next_nonblock > > > (ctx=ctx@entry=0x7fc4a8132730, > > > mail_r=mail_r@entry=0x7fc4a81120d8, > > > tryagain_r=tryagain_r@entry=0x7ffe23a98c87) at mail-storage.c:1787 > > > #16 0x00007fc4a69bc55d in mailbox_search_next (ctx=0x7fc4a8132730, > > > mail_r=mail_r@entry=0x7fc4a81120d8) at mail-storage.c:1773 > > > #17 0x00007fc4a6e97874 in imap_fetch_more_int (ctx=ctx@entry > > =0x7fc4a8112078, > > > cancel=false) at imap-fetch.c:479 > > > #18 0x00007fc4a6e98852 in imap_fetch_more (ctx=0x7fc4a8112078, > > > cmd=cmd@entry=0x7fc4a8111ed0) > > > at imap-fetch.c:556 > > > #19 0x00007fc4a6e8c17d in cmd_fetch (cmd=0x7fc4a8111ed0) at > > cmd-fetch.c:284 > > > #20 0x00007fc4a6e9601c in command_exec (cmd=cmd@entry=0x7fc4a8111ed0) at > > > imap-commands.c:158 > > > #21 0x00007fc4a6e94f1f in client_command_input (cmd=cmd@entry > > =0x7fc4a8111ed0) > > > at imap-client.c:780 > > > #22 0x00007fc4a6e95005 in client_command_input (cmd=0x7fc4a8111ed0) at > > > imap-client.c:841 > > > #23 0x00007fc4a6e952fd in client_handle_next_command > > > (remove_io_r=<synthetic pointer>, client=0x7fc4a8111530) at > > > imap-client.c:879 > > > #24 client_handle_input (client=client@entry=0x7fc4a8111530) at > > > imap-client.c:891 > > > #25 0x00007fc4a6e956c5 in client_input (client=0x7fc4a8111530) at > > > imap-client.c:933 > > > #26 0x00007fc4a66e1a87 in io_loop_call_io (io=0x7fc4a811edd0) at > > > ioloop.c:388 > > > #27 0x00007fc4a66e290f in io_loop_handler_run > > > (ioloop=ioloop@entry=0x7fc4a80fc750) > > > at ioloop-epoll.c:220 > > > #28 0x00007fc4a66e15d8 in io_loop_run (ioloop=0x7fc4a80fc750) at > > > ioloop.c:412 > > > #29 0x00007fc4a668e9e3 in master_service_run (service=0x7fc4a80fc5e0, > > > callback=callback@entry=0x7fc4a6e9ed70 <client_connected>) at > > > master-service.c:571 > > > #30 0x00007fc4a6e89324 in main (argc=1, argv=0x7fc4a80fc390) at > > main.c:400 > > > > > > Thank you. > > > > > > Best regards, > > > Hongying Liu > > > >

1 0

Spam instead of Junk folder
by Robert Moskowitz 07 Apr '17

07 Apr '17

Traditionally I have used 'Spam' as the folder name for all those emails that get tagged as, well Spam. But it seems that the standard is now 'Junk' as from 15-mailboxes.conf # Space separated list of IMAP SPECIAL-USE attributes as specified by # RFC 6154: \All \Archive \Drafts \Flagged \Junk \Sent \Trash #special_use = If I have in local.conf # 15-mailboxes.conf namespace inbox { mailbox Spam { special_use = \Junk } } This would auto make Spam, but: Would Junk (and all the others specified in 15-mailboxes.conf) still get created? What actually controls which folders get created?

1 1

Maybe it is an sql config error?
by Robert Moskowitz 06 Apr '17

06 Apr '17

I am looking at these messages in maillog: Apr 6 15:46:58 z9m9z dovecot: dict: Error: mysql(localhost): Connect failed to database (postfix): Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (13) - waiting for 25 seconds before retry Apr 6 15:46:58 z9m9z dovecot: dict: Error: mysql(localhost): Connect failed to database (postfix): Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (13) - waiting for 1 seconds before retry Apr 6 15:46:58 z9m9z dovecot: dict: Error: dict sql lookup failed: Not connected to database and wondering if my config is wrong. Here is what I have: in local.conf: # dovecot.conf protocols = imap pop3 lmtp sieve dict { sqlquota = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext } # 10-auth.conf !include conf.d/auth-sql.conf.ext # auth-sql.conf.ext userdb { driver = prefetch } # 90-quota.conf plugin { quota = dict:user::proxy::sqlquota trash = /etc/dovecot/dovecot-trash.conf.ext } dovecot-sql.conf.ext: driver = mysql connect = host=localhost dbname=postfix user=postfix password=mailpassword default_pass_scheme = MD5-CRYPT # following should all be on one line. password_query = SELECT username as user, password, concat('/home/vmail/', maild ir) as userdb_home, concat('maildir:/home/vmail/', maildir) as userdb_mail, 101 as userdb_uid, 12 as userdb_gid FROM mailbox WHERE username = '%u' AND active = '1' # following should all be on one line user_query = SELECT concat('/home/vmail/', maildir) as home, concat('maildir:/ho me/vmail/', maildir) as mail, 101 AS uid, 12 AS gid, CONCAT('*:messages=30000:by tes=', quota) as quota_rule FROM mailbox WHERE username = '%u' AND active = '1' [root@z9m9z dovecot]# dovecot-dict-sql.conf.ext: connect = host=localhost dbname=postfix user=postfix password=mailserv map { pattern = priv/quota/storage table = quota2 username_field = username value_field = bytes } map { pattern = priv/quota/messages table = quota2 username_field = username value_field = messages } Users ARE getting authenticated: # openssl s_client -connect z9m9z.test.htt-consult.com:993 CONNECTED(00000003) .... Cert stuff cut --- SSL handshake has read 1676 bytes and written 405 bytes --- New, TLSv1/SSLv3, Cipher is ECDHE-RSA-AES256-GCM-SHA384 .... Cert stuff cut --- * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE AUTH=PLAIN] Dovecot ready. a login faxit(a)test.htt-consult.com faxitpaaswd a OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS THREAD=ORDEREDSUBJECT MULTIAPPEND URL-PARTIAL CATENATE UNSELECT CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS SPECIAL-USE BINARY MOVE QUOTA] Logged in b list "" * * LIST (\HasNoChildren \Sent) "." Sent * LIST (\HasNoChildren \Trash) "." Trash * LIST (\HasNoChildren \Drafts) "." Drafts * LIST (\HasNoChildren) "." Spam * LIST (\HasNoChildren) "." INBOX b OK List completed. ====== So perhaps it is with the quota sql on sending/recv mail? thanks

1 0

Dovecot impatient with mysql?
by Robert Moskowitz 06 Apr '17

06 Apr '17

It seems dovecot is impatient with connecting with mysql, as I see in maillog entries like: Apr 6 11:48:30 z9m9z dovecot: dict: Error: mysql(localhost): Connect failed to database (postfix): Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (13) - waiting for 5 seconds before retry Apr 6 11:48:35 z9m9z dovecot: dict: Error: mysql(localhost): Connect failed to database (postfix): Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (13) - waiting for 25 seconds before retry I suspect it does connect eventually. This is a test system with only 1GB of memory and free reports: total used free shared buff/cache available Mem: 1025484 696344 24556 21528 304584 251552 Swap: 524284 92168 432116 The production box has 2GB, so if the problem is mysql is swapping out, that will be 'fixed', if it is processor, well this is an ARMv7 duo core, as is the production box. I am considering buying the new quad core. Is there anything I can do to get dovecot more patient with mysql, or just ignore there messages? thank you

3 4

abrt reported "imap killed by SIGBUS"
by Hongying Liu 06 Apr '17

06 Apr '17

Hi sbr-services, Could you give me some idea? ### abrt reported the error as below. [root@cupop4 log]# abrt-cli list --since 1488267244 id ad716dbfd3a68bbe0f055e32ebfe562f4f75df43 reason: imap killed by SIGBUS time: Sun Mar 19 2017 10:58:27 AM JST cmdline: dovecot/imap package: dovecot-2.2.10-7.el7 uid: 80180 (acaa2325) count: 2 Directory: /var/spool/abrt/ccpp-2017-03-19-10:58:27-4904 'abrt-cli report を実行する/var/spool/abrt/ccpp-2017-03-19-10:58:27-4904' ### /var/log/messages Mar 19 10:58:27 cupop4 abrt-hook-ccpp: Process 4904 (imap) of user 80180 killed by SIGBUS - dumping core And, there are lots of ldap error in /var/log/messages. Dovecot uses the ldap as userdb and passwddb. Is the ldap error related to imap crash? Mar 19 10:58:21 cupop4 nslcd[1534]: [a378de] <group/member="postfix"> ldap_result() failed: Invalid DN syntax: Invalid DN ### /var/log/dovecot Mar 19 10:58:27 cupop4 dovecot: imap(acaa2325): Fatal: master: service(imap): child 4904 killed with signal 7 (core dumped) ### gdb Core was generated by `dovecot/imap'. Program terminated with signal 7, Bus error. #0 0x00007fc4a69f293e in mail_cache_lookup_offset (cache=0x7fc4a811a320, view=<optimized out>, seq=<optimized out>, offset_r=offset_r@entry =0x7ffe23a98900) at mail-cache-lookup.c:95 95 while (cache->hdr->file_seq != reset_id) { (gdb) bt #0 0x00007fc4a69f293e in mail_cache_lookup_offset (cache=0x7fc4a811a320, view=<optimized out>, seq=<optimized out>, offset_r=offset_r@entry =0x7ffe23a98900) at mail-cache-lookup.c:95 #1 0x00007fc4a69f2afa in mail_cache_lookup_iter_init (view=view@entry=0x7fc4a81332b0, seq=<optimized out>, ctx_r=ctx_r@entry=0x7ffe23a988e0) at mail-cache-lookup.c:154 #2 0x00007fc4a69f2f8f in mail_cache_seq (seq=<optimized out>, view=0x7fc4a81332b0) at mail-cache-lookup.c:322 #3 mail_cache_field_exists (view=view@entry=0x7fc4a81332b0, seq=seq@entry=760, field=field@entry=4) at mail-cache-lookup.c:352 #4 0x00007fc4a69f3151 in mail_cache_lookup_field (view=0x7fc4a81332b0, dest_buf=dest_buf@entry=0x7ffe23a98a00, seq=760, field_idx=field_idx@entry =4) at mail-cache-lookup.c:413 #5 0x00007fc4a69d9439 in index_mail_cache_lookup_field (mail=mail@entry=0x7fc4a8128cd0, buf=buf@entry=0x7ffe23a98a00, field_idx=field_idx@entry=4) at index-mail.c:68 #6 0x00007fc4a69d94a7 in index_mail_get_fixed_field (mail=0x7fc4a8128cd0, field=<optimized out>, data=<optimized out>, data_size=8) at index-mail.c:130 #7 0x00007fc4a69d9fed in index_mail_get_cached_virtual_size (mail=mail@entry=0x7fc4a8128cd0, size_r=size_r@entry=0x7ffe23a98b20) at index-mail.c:403 #8 0x00007fc4a6987c1b in maildir_mail_get_virtual_size (_mail=0x7fc4a8128cd0, size_r=0x7ffe23a98b20) at maildir-mail.c:388 #9 0x00007fc4a69d9719 in index_mail_update_access_parts (mail=mail@entry=0x7fc4a8128cd0) at index-mail.c:1490 #10 0x00007fc4a69dbb93 in index_mail_set_seq (_mail=0x7fc4a8128cd0, seq=760, saving=<optimized out>) at index-mail.c:1521 #11 0x00007fc4a69e28cb in search_more_with_mail (mail=0x7fc4a8128cd0, ctx=0x7fc4a8132730) at index-search.c:1507 #12 search_more_with_prefetching (mail_r=<optimized out>, ctx=<optimized out>) at index-search.c:1579 #13 search_more (ctx=ctx@entry=0x7fc4a8132730, mail_r=mail_r@entry=0x7ffe23a98c20) at index-search.c:1650 #14 0x00007fc4a69e2ff4 in index_storage_search_next_nonblock (_ctx=0x7fc4a8132730, mail_r=0x7fc4a81120d8, tryagain_r=0x7ffe23a98c87) at index-search.c:1674 #15 0x00007fc4a69bc4ef in mailbox_search_next_nonblock (ctx=ctx@entry=0x7fc4a8132730, mail_r=mail_r@entry=0x7fc4a81120d8, tryagain_r=tryagain_r@entry=0x7ffe23a98c87) at mail-storage.c:1787 #16 0x00007fc4a69bc55d in mailbox_search_next (ctx=0x7fc4a8132730, mail_r=mail_r@entry=0x7fc4a81120d8) at mail-storage.c:1773 #17 0x00007fc4a6e97874 in imap_fetch_more_int (ctx=ctx@entry=0x7fc4a8112078, cancel=false) at imap-fetch.c:479 #18 0x00007fc4a6e98852 in imap_fetch_more (ctx=0x7fc4a8112078, cmd=cmd@entry=0x7fc4a8111ed0) at imap-fetch.c:556 #19 0x00007fc4a6e8c17d in cmd_fetch (cmd=0x7fc4a8111ed0) at cmd-fetch.c:284 #20 0x00007fc4a6e9601c in command_exec (cmd=cmd@entry=0x7fc4a8111ed0) at imap-commands.c:158 #21 0x00007fc4a6e94f1f in client_command_input (cmd=cmd@entry=0x7fc4a8111ed0) at imap-client.c:780 #22 0x00007fc4a6e95005 in client_command_input (cmd=0x7fc4a8111ed0) at imap-client.c:841 #23 0x00007fc4a6e952fd in client_handle_next_command (remove_io_r=<synthetic pointer>, client=0x7fc4a8111530) at imap-client.c:879 #24 client_handle_input (client=client@entry=0x7fc4a8111530) at imap-client.c:891 #25 0x00007fc4a6e956c5 in client_input (client=0x7fc4a8111530) at imap-client.c:933 #26 0x00007fc4a66e1a87 in io_loop_call_io (io=0x7fc4a811edd0) at ioloop.c:388 #27 0x00007fc4a66e290f in io_loop_handler_run (ioloop=ioloop@entry=0x7fc4a80fc750) at ioloop-epoll.c:220 #28 0x00007fc4a66e15d8 in io_loop_run (ioloop=0x7fc4a80fc750) at ioloop.c:412 #29 0x00007fc4a668e9e3 in master_service_run (service=0x7fc4a80fc5e0, callback=callback@entry=0x7fc4a6e9ed70 <client_connected>) at master-service.c:571 #30 0x00007fc4a6e89324 in main (argc=1, argv=0x7fc4a80fc390) at main.c:400 Thank you. Best regards, Hongying Liu

2 1

Replication for Pigeonhole ManageSieve
by Joe Nahmias 06 Apr '17

06 Apr '17

Hello, I currently have one machine running postfix SMTP server as MTA along with dovecot IMAP server for email. Although it only supports a handful of users, email service is important to us all; so I'm looking to make this a more fault-tolerant / highly-available system. To that end, I'm planning on configuring postfix to use deliver/dovecot-lda as my MDA (using procmail at the moment), spinning up another machine with postfix/dovecot and setting up master/master replication using dsync/doveadm-sync. My reading on the subject suggests that this should (given appropriate MX & SRV dns records) make traffic balanced across both nodes, and the system should be resilient if one of the nodes should fail without the need for much/any human intervention. In order to replace the functionality that procmail currently provides as MDA, I was thinking to use Sieve. Fortunately, it seems the Pigeonhole project provides almost everything I need on the server side to make this work. The one potential gap I have identified is the syncing of the sieve scripts between the two machines. Has any one dealt with this and come up with a good solution? Does dsync already handle this and I just haven't figured it out? Let me know if my question is best directed elsewhere. Thanks in advance for any help, --Joe PS - please cc me as I don't subscribe to this list.

2 1

Re: Getting error on port 995
by Joseph Tam 05 Apr '17

05 Apr '17

>> As a wild ass guess, I think maybe the client is using used "STARTTLS" >> intead of "SSL", or some other SSL requirement disagreement. > > I believe it has more to do with the encryption method (plain, login, > cram-md5) than with the TLS. The TLS encryption happens on the network > layer whereas the encryption method is used at the IMAP level. Those are authentication methods. However, Googling the heck out of the error message, it appears the OP's error message is a common problem fixed by resetting the PopProxy configuration https://social.technet.microsoft.com/Forums/ie/en-US/40eb0164-0bcf-499a-940… https://blog.zubairalexander.com/outlook-error-0x800ccc1/ Joseph Tam <jtam.home(a)gmail.com>

1 0

Problem with Dovecot and BlackBerry
by Luca Bertoncello 05 Apr '17

05 Apr '17

Hi all, i've got a strange behaviour with a BlackBerry Classic Phone (BBOS 10.3.2.2876) in combination with Dovecot 2.2.13 while trying to fetch mails. Before burying myself into debugging sessions, i try to get an understanding if the following is a Client- or a Server-specific error in the behaviour: CIGA8 UID FETCH 10009:10035 (UID FLAGS) (CHANGEDSINCE NOMODSEQ) CIGA8 BAD Error in IMAP command UID FETCH: Invalid CHANGEDSINCE modseq. Following the full conversation. ---- * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE STARTTLS AUTH=PLAIN AUTH=LOGIN AUTH=DIGEST-MD5 AUTH=CRAM-MD5] Dovecot on xxx ready. CIGA1 CAPABILITY * CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE STARTTLS AUTH=PLAIN AUTH=LOGIN AUTH=DIGEST-MD5 AUTH=CRAM-MD5 CIGA1 OK Pre-login capabilities listed, post-login capabilities have more. CIGA2 ID ("os" "BlackBerry 10" "os-version" "10.3.2.2876" "vendor" "rim" "device" "Classic" "name" "bbimap") * ID ("name" "Dovecot") CIGA2 OK ID completed. CIGA3 LOGIN xxx xxx * CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS THREAD=ORDEREDSUBJECT MULTIAPPEND URL-PARTIAL CATENATE UNSELECT CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS SPECIAL-USE BINARY MOVE CIGA3 OK Logged in CIGA4 CAPABILITY * CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS THREAD=ORDEREDSUBJECT MULTIAPPEND URL-PARTIAL CATENATE UNSELECT CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS SPECIAL-USE BINARY MOVE CIGA4 OK Capability completed. CIGA5 LIST "" "" * LIST (\Noselect) "." "" CIGA5 OK List completed. CIGA6 LIST "" "*" * LIST (\HasNoChildren) "." folder_a * LIST (\HasNoChildren) "." folder_b * LIST (\HasNoChildren) "." folder_c * LIST (\HasNoChildren) "." sent-mail * LIST (\HasNoChildren) "." folder_d * LIST (\HasNoChildren) "." folder_e * LIST (\HasNoChildren \Trash) "." Trash * LIST (\HasNoChildren \Drafts) "." Drafts * LIST (\HasNoChildren) "." folder_f * LIST (\HasNoChildren) "." folder_g * LIST (\HasNoChildren) "." INBOX CIGA6 OK List completed. CIGA7 SELECT INBOX (CONDSTORE) * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft \*)] Flags permitted. * 7 EXISTS * 0 RECENT * OK [UIDVALIDITY 1391686038] UIDs valid * OK [UIDNEXT 10036] Predicted next UID * OK [HIGHESTMODSEQ 1608] Highest CIGA7 OK [READ-WRITE] Select completed (0.000 secs). CIGA8 UID FETCH 10009:10035 (UID FLAGS) (CHANGEDSINCE NOMODSEQ) CIGA8 BAD Error in IMAP command UID FETCH: Invalid CHANGEDSINCE modseq. CIGA9 LOGOUT * BYE Logging out CIGA9 OK Logout completed. ---- Thanks in advance! Luca Bertoncello (lucabert(a)lucabert.de)

4 3

Problem with acl and shared mailboxes
by Fabian 04 Apr '17

04 Apr '17

Hi there, we are currently have the following problem: User gustav(a)agreatdomain.de shares his INBOX to brunhilde(a)agreatdomain.com. But brunhilde can't subscribe that mailbox. host:~ # more //var/spool/mail/agreatdomain.com/gustav/Maildir/dovecot-acl owner akxeilprwts user=brunhilde(a)agreatdomain.com lprws host:~ # Doveadm acl debug request: host:~ # doveadm acl debug -u sieglinde(a)agreatdomain.com shared/gustav doveadm(sieglinde(a)agreatdomain.com): Error: Mailbox 'shared.gustav' in namespace 'shared/gustav/' doesn't exist in /var/spool/mail/agreatdomain.com/gustav//Maildir/.shared.gustav host:~ # In the debug logfile I can see the following message: Apr 03 10:29:18 imap(brunhilde(a)agreatdomain.com): Debug: acl: acl username = brunhilde(a)agreatdomain.com Apr 03 10:29:18 imap(brunhilde(a)agreatdomain.com): Debug: acl: owner = 0 Apr 03 10:29:18 imap(brunhilde(a)agreatdomain.com): Debug: acl vfile: Global ACLs disabled Apr 03 10:29:18 imap(brunhilde(a)agreatdomain.com): Debug: acl vfile: file /var/spool/mail/agreatdomain.com/gustav/Maildir/.shared.gustav/dovecot-acl not found Apr 03 10:29:18 imap(brunhilde(a)agreatdomain.com): Debug: acl: No lookup right to mailbox: shared/gustav Why is dovecot searching in .shared/.gustav instead of Maildir/ directly? Any ideas? My configuration: host:~ # doveconf -n # 2.2.13: /etc/dovecot/dovecot.conf # OS: Linux 3.12.67-60.64.24-default x86_64 SUSE Linux Enterprise Server 12 (x86_64) ext3 auth_debug = yes auth_master_user_separator = * auth_mechanisms = plain login auth_verbose = yes debug_log_path = /var/log/dovecot.debug dict { sqlquota = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext } disable_plaintext_auth = no first_valid_uid = 480 lmtp_save_to_detail_mailbox = yes mail_debug = yes mail_gid = vmail mail_location = maildir:/var/spool/mail/%d/%u/Maildir:LAYOUT=fs mail_plugins = acl quota listescape mail_privileged_group = vmail mail_uid = dovecot 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 { hidden = yes inbox = yes list = no location = prefix = separator = / subscriptions = yes } namespace { list = yes location = maildir:%%h/Maildir:INDEXPVT=~/Maildir/shared/%%u prefix = shared/%%n/ separator = / subscriptions = no type = shared } namespace Public { list = children location = maildir:/var/mail/%d/public:INDEXPVT=~/public:LAYOUT=fs prefix = Public/ separator = / subscriptions = no type = public } namespace inbox { inbox = no 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 = / subscriptions = yes type = private } passdb { args = /etc/dovecot/masteruser.%s driver = passwd-file master = yes pass = yes } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { acl = vfile acl_anyone = allow acl_shared_dict = file:/var/spool/mail/%d/shared-mailboxes.db quota = dict:User quota::proxy::sqlquota quota2 = dict:Shared quota::proxy::sqlquota quota_rule2 = INBOX/Trash:storage=+100M sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } postmaster_address = postmaster(a)d8ox1.int.pro-ite.de protocols = imap pop3 lmtp sieve service auth-worker { user = dovecot } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-userdb { mode = 0666 } } service dict { unix_listener dict { group = vmail mode = 0660 user = dovecot } } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } service managesieve-login { inet_listener sieve { port = 4190 } } ssl = no userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } protocol lmtp { mail_plugins = acl quota listescape acl quota sieve } protocol lda { mail_plugins = acl quota listescape acl sieve } protocol imap { mail_plugins = acl quota listescape imap_quota imap_acl } host:~ # -- Kind regards, Fabian

2 3

Meaning of "protocol !indexer-worker"
by Angel L. Mateo 04 Apr '17

04 Apr '17

Hello, I'm configuring dovecot 2.2.28. Comparing with previous versions I have found now in 10-mail.conf the config: protocol !indexer-worker { # If folder vsize calculation requires opening more than this many mails from # disk (i.e. mail sizes aren't in cache already), return failure and finish # the calculation via indexer process. Disabled by default. This setting must # be 0 for indexer-worker processes. #mail_vsize_bg_after_count = 0 } I can see that indexer-worker is the index service in dovecot. But I don't what the '!' means in front of the service name. Any who can explain it to me? -- Angel L. Mateo Martínez Sección de Telemática Área de Tecnologías de la Información y las Comunicaciones Aplicadas (ATICA) http://www.um.es/atica Tfo: 868889150 Fax: 868888337

2 2

Users home path inside a sieve script
by Mark Constable 04 Apr '17

04 Apr '17

Perhaps I have not looked hard enough but is it possible to get at the current users auth userdb "home" (or $HOME) variable from inside a sieve script? Example?

3 3

Error: Virtual mailbox loops, Dovecot version 2.2.10
by dan＠redchops.com 03 Apr '17

03 Apr '17

I'm trying to follow the guide at https://wiki.dovecot.org/Plugins/Virtual for the 'Conversation' style virtual mailbox, but with a small change. I'd like the virtual mailboxes to be 'top level', which I found while searching through this list is accomplishable by putting the dovecot-virtual file in the root of the namespace location. My issue is this works perfectly fine for the All Mail virtual mailbox, but the Threaded mailbox fails with the error above. I tried creating a RealMail namespace, but that doesn't solve the issue either. I feel like I must be overlooking something simple; I could get this setup working if the virtual mailboxes shared a namespace and were subfolders, but I don't like that setup much (I'm trying to get my companies GMail users on to our own webmail client, it's features like this that I need to replicate with dovecot or they'll never leave their POP3 setups). I've attached the output of dovecot -n, and my virtual mailboxes look like this: # cat Threaded/dovecot-virtual All inthread refs x-mailbox INBOX # cat all/dovecot-virtual RealMail RealMail/* -RealMail/Trash -RealMail/Trash/* -RealMail/Spam -RealMail/Spam/* all I'd appreciate any insight in to this issue. If I try to access the Threaded Inbox through IMAP, I get this error specifically: a select "Threaded Inbox" a NO [SERVERBUG] Virtual mailbox open failed because of mailbox All: Internal error occurred. Refer to server log for more information. [2017-04-03 00:24:28] The relevant line being: Apr 3 00:24:28 mail dovecot: imap(dan(a)redchops.com): Error: Virtual mailbox loops: No information before or after. Thanks, -Dan

2 1

Re: Getting error on port 995
by Joseph Tam 03 Apr '17

03 Apr '17

Bhushan Bhosale writes: > I'm getting issue with port 995 by using Microsoft Outlook 2016 only. > The error on Microsoft Outlook showing "Your server does not support > the connection encryption type. Try changing the encryption method". > The error is only who is using Microsoft outlook2016. Kindly help. Help us help you. Please include output of "dovecot -n" and any relevant log entries. As a wild ass guess, I think maybe the client is using used "STARTTLS" intead of "SSL", or some other SSL requirement disagreement. Joseph Tam <jtam.home(a)gmail.com>

2 1

Mail list empty on my mailserver
by Philippe Forums 03 Apr '17

03 Apr '17

Hello, After changing NAS, I meet a problem when I go on my e-mail box with my webmail. Either e-mails do not appear anymore, or they appear but are "empty". When I look in the directory of the e-mails of my mailserver, these e-mails are present. I tried to rename files "dovecot.index*" and to restart dovecot but nothing can be done. To make the seesaw of a NAS towards an other one, I copied all the directory of mailserver to an external storage, and made the copy the other way on my new NAS. This directory is a mount to a NAS. Having well to look, it would seem whether it is a date problem, because the copy did not keep the real dates of e-mails and they thus find themselves dated the day of the copy. I know not at all how to get back all my e-mails in my webmail. Thank's for your help. PS : I'm french, sorry for my english. -- ##################### Philippe - Forums

2 2

Getting error on port 995
by Bhushan Bhosale 02 Apr '17

02 Apr '17

Dear Team, I'm getting issue with port 995 by using Microsoft Outlook 2016 only. The error on Microsoft Outlook showing "Your server does not support the connection encryption type. Try changing the encryption method". The error is only who is using Microsoft outlook2016. Kindly help. Thanks and Regards, Bhushan Bhosale

2 1

dsync replication
by George Dimakopoulos 31 Mar '17

31 Mar '17

Is it stable for dovecot 2.2.27 to implement DRBD (or HAST) on block level for maildir data replication instead of using dsync plugin? Regards, George

2 1

Slow performance with large folders over the Internet
by Shawn Heisey 31 Mar '17

31 Mar '17

Dovecot package version is 1:1.2.15-7+deb6u1. It is in Debian 6.0.10, using the Debian package. The server is in my basement at home, and is exposed to the Internet so I can fully access my mail from anywhere. I use IMAP for reading mail. I have a number of folders in my mailbox that have thousands of messages in them, from mailing lists. When I'm at home, I have a LAN connection to the server. It goes through a Cisco firewall that limits the connection speed to 100Mb/s. In this situation, I can open a folder with 25000 messages in it, click on the next unread message that Thunderbird did not know about before, and within a second or two, the message will download, allowing me to view it and reply. When I'm at work, with highly variable network latency between Thunderbird and the server, doing exactly the same thing takes a LOT longer. I have seen it take as long as 15 minutes for a single message. If I open a folder with only a few messages in it, it is fast. The server is not overloaded -- I can log into it with ssh and use "mutt -f" to open a folder directly. Loading thousands of messages into mutt takes a while, but I have no difficulty using the ssh connection and running commandline programs. This suggests that the IMAP communication between the server and the client involves a large amount of back and forth communication when the message count in the folder is high, possibly something for every message in the folder. It happens quickly on a LAN but crawls on a connection with high latency. I can understand it taking a few seconds longer on a high-latency link, but it takes minutes. I do plan on building a new server and migrating to Dovecot 2.x, but I haven't had the time to work on that. Is this a known problem? If so, is it fixed in 2.x? Thanks, Shawn

3 2

Studying dovecot source code (searching for mail_deliver_hook_set)
by chaouche yacine 30 Mar '17

30 Mar '17

Hello dovecot, I would like to study how dovecot manages quota, especially how it deals with the maildirsize file if one chooses to implement quota according to the maildir++ specification. I made a number of assumptions : 1. mail is (always/sometimes) delivered with the dovecot-lda binary, which source code is in src/lda. 2. mail is sent with the mail_deliver function which is called from src/lda/main.c and is defined in src/lib-lda/mail-deliver.c 3. mail_deliver function calls the deliver_mail function (it seems to be pointer to a function) 4. according to src/lib-lda/mail-deliver.h, deliver_mail is set with the mail_deliver_hook_set function. Here's what the comment says /* Sets the deliver_mail hook and returns the previous hook, which the new_hook should call if it's non-NULL. */ deliver_mail_func_t *mail_deliver_hook_set(deliver_mail_func_t *new_hook); The problem at this point is that I can't find where is this function called. A grep on the sources only reveals two results : -*- mode: grep; default-directory: "~/DOWNLOADS/APPS/dovecot-2.2.13/src/" -*- Grep started at Tue Mar 28 17:01:50 grep -nH -e 'mail_deliver_hook_set' -r . ./lib-lda/mail-deliver.c:428:deliver_mail_func_t *mail_deliver_hook_set(deliver_mail_func_t *new_hook) ./lib-lda/mail-deliver.h:103:deliver_mail_func_t *mail_deliver_hook_set(deliver_mail_func_t *new_hook); Grep finished (matches found) at Tue Mar 28 17:01:50 According to the changelog this function has been introduced back in 2010. I don't know if it's really used ? * I am working on the 2.2.13 sources because that's what's installed on my server. * I couldn't find a developers mailling listed in http://www.dovecot.org/mailinglists.html so I'm just posting this here. -- Yassine.

3 5

Email Push to Iphone
by mca＠caloro.ch 30 Mar '17

30 Mar '17

Hello Please exist in Dovecot 2.2.13 the E-Mail Push function? So that the Email on me Iphone are available at this moment that will be transfered, I see or found any other 3part software "Z-push", but it's this function are not included on dovecot? Thanks and regards Mauri

3 2

Using SpamProbe via only sieve scripts
by Mark Constable 30 Mar '17

30 Mar '17

FWIW this took me days to get right, and still needs tinkering, but it might make for a good starting point for anyone else needing something similar (ie; I don't use or need the overhead of spamassassin or rspamd). https://gist.github.com/markc/eeeb66ce30ea805af62631656cf86c4d Any comments or corrections on that page would be appreciated.

2 1

Re: cannot login to imap under load
by Gerard Ranke 29 Mar '17

29 Mar '17

Hi Maria, It does indeed run from systemd, so this is what's currently in the dovecot unit file ( /etc/systemd/system/dovecot.service ): [Unit] Description=Dovecot IMAP/POP3 email server After=local-fs.target network.target [Service] Type=simple ExecStart=/usr/sbin/dovecot -F NonBlocking=yes TasksMax=10000 LIMIT_NOFILE=10000 [Install] WantedBy=multi-user.target Unfortunately, it doesn't seem to work... Best, gerard On 29-03-17 13:13, María Arrea wrote: > > If you are running dovecot via systemd, increase NOFILES in the > dovecot startup script > > El 29/03/17 a las 13:07, Gerard Ranke escribió: >> Hi Steffen, >> >> On 29-03-17 12:38, Steffen Kaiser wrote: >>> On Tue, 28 Mar 2017, Gerard Ranke wrote: >>> >>>> dovecot: master: Error: service(imap): fork() failed: Resource >>>> temporarily unavailable >>>> dovecot: master: Error: service(imap): command startup failed, >>>> throttling for 2 secs >>> check out the ulimits for the Dovecot process. >>> >>> -- Steffen Kaiser >> Here they are: >> >> dovecot@mail:~> ulimit -a >> core file size (blocks, -c) 0 >> data seg size (kbytes, -d) unlimited >> scheduling priority (-e) 0 >> file size (blocks, -f) unlimited >> pending signals (-i) 256942 >> max locked memory (kbytes, -l) 64 >> max memory size (kbytes, -m) unlimited >> open files (-n) 10000 >> pipe size (512 bytes, -p) 8 >> POSIX message queues (bytes, -q) 819200 >> real-time priority (-r) 0 >> stack size (kbytes, -s) 8192 >> cpu time (seconds, -t) unlimited >> max user processes (-u) 256942 >> virtual memory (kbytes, -v) unlimited >> file locks (-x) unlimited >> >> This looks ok to me, but on startup, I still get: >> >> dovecot[9309]: Warning: fd limit (ulimit -n) is lower than required >> under max. load (1024 < 10000), because of service auth { client_limit } >> >> Strange thing is that dovecot still complains about the fd limit being >> 1024, while I set it to 10000. And how can a ulimit be too low 'because >> of service auth'? I don't get that at all. Thanks for your interest! >> >> gerard > >

3 3

cannot login to imap under load
by Gerard Ranke 29 Mar '17

29 Mar '17

Dear list, We moved our dovecot installation to a new vm, and ever since there are problems logging in to our imap server during office hours. ( Evenings and weekends are fine. ) Both the new and the old machine are dovecot 2.2.13. Symptoms: Logging in via imap gives: . OK Pre-login capabilities listed, post-login capabilities have more. a login <loginname> <passwd> * OK Waiting for authentication master process to respond.. closed whereas using the same credentials with pop3: +OK Dovecot ready. user <loginname> +OK pass <passwd> +OK Logged in. Our mail.err log gives lots of: dovecot: imap-login: Error: master(imap): Auth request timed out (received 0/12 bytes) dovecot: imap: Error: Login client disconnected too early dovecot: auth: Error: Master request 24000.918 not found dovecot: master: Error: service(imap): fork() failed: Resource temporarily unavailable dovecot: master: Error: service(imap): command startup failed, throttling for 2 secs Note thate we our users almost exclusively use imap. Normally we would have some 7 or 800 imap processes running and only a few pop3. Our doveconf -n output: # 2.2.13: /etc/dovecot/dovecot.conf # OS: Linux 4.4.38-93-default x86_64 SUSE Linux Enterprise Server 12 (x86_64) auth_mechanisms = plain login default_client_limit = 2000 default_process_limit = 2000 default_vsz_limit = 512 M disable_plaintext_auth = no imap_client_workarounds = tb-extra-mailbox-sep import_environment = TZ DEBUG_OUTOFMEM DOVECOT_HOSTDOMAIN 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.conf.ext driver = ldap } plugin { quota = maildir:User quota quota_rule = *:storage=1G quota_rule2 = Trash:storage=+10%% sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } protocols = imap pop3 lmtp sieve service anvil { client_limit = 8003 } service auth { client_limit = 10000 unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-userdb { group = dovecot mode = 0666 } } service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } process_min_avail = 4 service_count = 0 } service imap { process_limit = 2048 } service pop3-login { inet_listener pop3 { port = 110 } inet_listener pop3s { port = 995 ssl = yes } process_min_avail = 4 service_count = 0 } service pop3 { process_limit = 2048 } ssl_cert = </etc/ssl/certs/hkuwildcardthawte.crt ssl_key = </etc/ssl/certs/hkuwildcardthawte.key ssl_protocols = !SSLv2 !SSLv3 userdb { args = /etc/dovecot/dovecot-ldap-userdb.conf driver = ldap } protocol lmtp { mail_plugins = " quota sieve" } protocol lda { mail_plugins = " quota sieve" } protocol imap { mail_max_userip_connections = 10 mail_plugins = " quota imap_quota" } Thank you all for any insight, it will be much appreciated! Best regards, gerard

3 5

pigeonhole / vacation
by A. Schulze 29 Mar '17

29 Mar '17

Hello, we use the sieve vacation module to answer messages for certain mailboxes. vacation send back answers to most but not all messages wich is fine and intended. .dovecot.sieve looks like this: require ["vacation", "variables"]; if header :matches "subject" "*" { vacation :subject "Automatic response to: ${1}" "thanks for your message"; keep; } But now I would like to distinct messages that where answered from those where the vacation module did not send back a message. Is it possible to store answered messages in one folder and unanswered in an other? # probably invalid sieve syntax if vacation .... { fileinto "answered/"; stop; else fileinto "unanswered/"; stop; } After reading RFC 5230 I feel it's not possible at all :-/ Andreas

2 1

Re: Email Push to Iphone
by Ricardo Branco 29 Mar '17

29 Mar '17

there is this plugin to use APNS to notify phones, its a faf though as you need a legal OSX Server to generate the signing keys, I never ended up implementing it. https://github.com/st3fan/dovecot-xaps-daemon Aki Tuomi wrote on 29/03/2017 07:29: > > On 29.03.2017 07:24, mca(a)caloro.ch wrote: >> Hello >> >> >> >> Please exist in Dovecot 2.2.13 the E-Mail Push function? >> >> >> >> So that the Email on me Iphone are available at this moment that will be >> transfered, I see or found any other 3part software "Z-push", but it's this >> function are not included on dovecot? >> >> >> >> Thanks and regards >> >> Mauri >> >> > There exists a push notification framework for dovecot, but it does not support iPhone push directly. See https://wiki2.dovecot.org/Plugins/PushNotification > > Aki

1 0

Tip: update dovecot MD5 password from PAM
by Steinar Bang 29 Mar '17

29 Mar '17

This is a PAM module that listens for password changes, and will update the MD5 password for a user, in a file that dovecot can read, when the user's password is changed: https://github.com/steinarb/pam_dovecotmd5pwd Caveat emptor! (Works for me...! :-) )

5 9

The challenge of customizing Dovecot
by Robert Moskowitz 29 Mar '17

29 Mar '17

I have been running Dovecot for sometime, but I have just used someone else efforts on customizing it. Many of these throw out the dovecot/conf.d files for a single dovecot.conf with no explanation on what does what. So tell you a few conf.d files to edit. So over the past few days, I have rolled up my sleeves and did my best to work out how to modify the proper conf.d files. To 'stay true' to the Dovecot maintainer's config organization. The target is Centos7 with Dovecot 2.2.10-7 It was HARD! Besides dovecot.conf, I had to modify 13 conf.d files. Add 3 .ext files in /etc/dovecot, and set up sieve. I will soon have my total instructions available on my server, but to share with you what I have done for Dovecot customization and maybe to get some recommendations on improvements. For the most part, I have used SED to modify the conf files. I use a few env variables: your_domain_tld= your_host_only= your_host_tld=$your_host_only.$your_domain_tld Postfix_Database_Password= What follows are the pieces of my customization, all comments welcomed (this is NOT adequately tested! That is later in the week!): sed -i -e "/^#protocols/s/$/ sieve/w /dev/stdout" /etc/dovecot/dovecot.conf sed -i -e "s/^#protocols/protocols/w /dev/stdout" /etc/dovecot/dovecot.conf sed -i -e "s/#quota = /sqlquota = /w /dev/stdout" /etc/dovecot/dovecot.conf sed -i -e "/^auth_mechanisms/s/$/ login/w /dev/stdout" /etc/dovecot/conf.d/10-auth.conf sed -i -e 's/^#!include auth-sql.conf.ext/!include auth-sql.conf.ext/w /dev/stdout' /etc/dovecot/conf.d/10-auth.conf sed -i -e "0,/#userdb {/ s/#userdb {/userdb {/w /dev/stdout" /etc/dovecot/conf.d/auth-sql.conf.ext sed -i -e "s/# driver = prefetch/ driver = prefetch\n }/w /dev/stdout" /etc/dovecot/conf.d/auth-sql.conf.ext sed -i -e "/^#mail_location/s/$/maildir:\/home\/vmail\/%d\/%n/w /dev/stdout" /etc/dovecot/conf.d/10-mail.conf sed -i -e "s/^#mail_location/mail_location/w /dev/stdout" /etc/dovecot/conf.d/10-mail.conf sed -i -e "s/first_valid_uid = 1000/first_valid_uid = 101/w /dev/stdout" /etc/dovecot/conf.d/10-mail.conf sed -i -e "s/#first_valid_gid = 1/first_valid_gid = 12/w /dev/stdout" /etc/dovecot/conf.d/10-mail.conf sed -i "/unix_listener auth-userdb/ a mode = 0666\n user = vmail\n group = mail" /etc/dovecot/conf.d/10-master.conf sed -i "/#unix_listener \/var\/spool/ a mode = 0666\n user = postfix\n group = postfix\n }" /etc/dovecot/conf.d/10-master.conf sed -i -e "s/#unix_listener \/var\/spool/unix_listener \/var\/spool/w /dev/stdout" /etc/dovecot/conf.d/10-master.conf sed -i "/unix_listener dict/ a mode = 0666\n user = vmail\n group = mail" /etc/dovecot/conf.d/10-master.conf sed -i -e "s/^mode/ mode/w /dev/stdout" /etc/dovecot/conf.d/10-master.conf sed -i -e "s/dovecot\/certs\/dovecot.pem/tls\/certs\/$your_host_tld.crt/w /dev/stdout" /etc/dovecot/conf.d/10-ssl.conf sed -i -e "s/dovecot\/private\/dovecot.pem/tls\/private\/$your_host_tld.key/w /dev/stdout" /etc/dovecot/conf.d/10-ssl.conf sed -i -e "/^#postmaster_address/s/$/ postmaster@$your_domain_tld/w /dev/stdout" /etc/dovecot/conf.d/15-lda.conf sed -i -e "s/^#postmaster_address/postmaster_address/w /dev/stdout" /etc/dovecot/conf.d/15-lda.conf sed -i "/#mail_plugins/ a mail_plugins = quota sieve" /etc/dovecot/conf.d/15-lda.conf sed -i -e "s/^mail_plugins/ mail_plugins/w /dev/stdout" /etc/dovecot/conf.d/15-lda.conf sed -i -e "s/^#lda_mailbox_autocreate = no/lda_mailbox_autocreate = yes/w /dev/stdout" /etc/dovecot/conf.d/15-lda.conf sed -i -e "s/^#lda_mailbox_autosubscribe = no/lda_mailbox_autosubscribe = yes/w /dev/stdout" /etc/dovecot/conf.d/15-lda.conf sed -i "/#mail_plugins / a mail_plugins = quota imap_quota trash" /etc/dovecot/conf.d/20-imap.conf sed -i -e "s/^mail_plugins/ mail_plugins/w /dev/stdout" /etc/dovecot/conf.d/20-imap.conf sed -i "/#imap_client_workarounds/ a imap_client_workarounds = delay-newmail" /etc/dovecot/conf.d/20-imap.conf sed -i "/#mail_plugins/ a mail_plugins = sieve" /etc/dovecot/conf.d/20-lmtp.conf sed -i -e "s/^mail_plugins/ mail_plugins/w /dev/stdout" /etc/dovecot/conf.d/20-lmtp.conf sed -i -e "s/^#lmtp_save_to_detail_mailbox = no/lmtp_save_to_detail_mailbox = yes/w /dev/stdout" /etc/dovecot/conf.d/20-lmtp.conf sed -i -e "s/#service managesieve-login/service managesieve-login/w /dev/stdout" /etc/dovecot/conf.d/20-managesieve.conf sed -i -e "s/#inet_listener sieve {/inet_listener sieve {/w /dev/stdout" /etc/dovecot/conf.d/20-managesieve.conf sed -i -e "s/# port = 4190/ port = 4190\n }/w /dev/stdout" /etc/dovecot/conf.d/20-managesieve.conf sed -i "/#vsz_limit/ a }" /etc/dovecot/conf.d/20-managesieve.conf sed -i "/#mail_plugins/ a mail_plugins = quota" /etc/dovecot/conf.d/20-pop3.conf sed -i -e "s/^mail_plugins/ mail_plugins/w /dev/stdout" /etc/dovecot/conf.d/20-pop3.conf sed -i "/#pop3_client_workarounds/ a pop3_client_workarounds = outlook-no-nuls oe-ns-eoh" /etc/dovecot/conf.d/20-pop3.conf sed -i -e "s/#acl = /acl = /w /dev/stdout" /etc/dovecot/conf.d/90-acl.conf sed -i -e "s/#sieve_before =/sieve_before = \/home\/sieve\/globalfilter.sieve/w /dev/stdout" /etc/dovecot/conf.d/90-sieve.conf cat <<EOF>>/etc/dovecot/conf.d/90-quota.conf || exit 1 plugin { quota = dict:user::proxy::sqlquota trash = /etc/dovecot/dovecot-trash.conf.ext } EOF cat <<EOF>/etc/dovecot/dovecot-trash.conf.ext || exit 1 # Spam mailbox is emptied before Trash 1 Spam # Trash mailbox is emptied before Sent # 2 Trash # If both Sent and "Sent Messages" mailboxes exist, the next oldest message # to be deleted is looked up from both of the mailboxes. # 3 Sent # 3 Sent Messages EOF cat <<EOF>/etc/dovecot/dovecot-sql.conf.ext || exit 1 driver = mysql connect = host=localhost dbname=postfix user=postfix password=$Postfix_Database_Password default_pass_scheme = MD5-CRYPT # following should all be on one line. password_query = SELECT username as user, password, concat('/home/vmail/', maildir) as userdb_home, concat('maildir:/home/vmail/', maildir) as userdb_mail, 101 as userdb_uid, 12 as userdb_gid FROM mailbox WHERE username = '%u' AND active = '1' # following should all be on one line user_query = SELECT concat('/home/vmail/', maildir) as home, concat('maildir:/home/vmail/', maildir) as mail, 101 AS uid, 12 AS gid, CONCAT('*:messages=30000:bytes=', quota) as quota_rule FROM mailbox WHERE username = '%u' AND active = '1' EOF cat <<EOF>/etc/dovecot/dovecot-dict-sql.conf.ext || exit 1 connect = host=localhost dbname=postfix user=postfix password=$Postfix_Database_Password map { pattern = priv/quota/storage table = quota2 username_field = username value_field = bytes } map { pattern = priv/quota/messages table = quota2 username_field = username value_field = messages } EOF mkdir /home/sieve cat <<EOF>/home/sieve/globalfilter.sieve || exit 1 require "fileinto"; if header :contains "X-Spam-Flag" "YES" { fileinto "Spam"; } if header :contains "subject" "***SPAM***" { fileinto "Spam"; } EOF sievec /home/sieve/globalfilter.sieve chown -R vmail:mail /home/sieve

4 8

Re: UID Purge?
by Aki Tuomi 28 Mar '17

28 Mar '17

On 28.03.2017 10:55, Kevin Myers wrote: >> Does this happen if you do this on wire? >> >> telnet localhost 143 >> a LOGIN username password >> s SELECT INBOX >> s STORE 1:1 FLAGS (\Deleted) # or some other message-set >> n NOOP >> l LOGOUT >> >> Aki > Good point. No. And if I just delete it in Thunderbird (my client) it > does as it's told and just marks it deleted. Maybe it's a > Thunderbird/Dovecot thing? you could try looking at https://wiki2.dovecot.org/Debugging/Rawlog to find out. Aki

3 4

UID Purge?
by Kevin 28 Mar '17

28 Mar '17

Hi, I've just migrated to Dovecot from cyrus-imapd, and I notice that when I move emails from one folder to another they appear to be automatically marked deleted (expected) and also purged (not expected). With cyrus, I am used to emails being marked deleted, but still existing until a manual purge (expunge). Is this normal behaviour with Dovecot, and is it configurable? Thanks. Kevin.

2 1

replicator crashing - oom
by Daniel Miller 24 Mar '17

24 Mar '17

I have the following in my log: Mar 21 14:46:59 bubba dovecot: replicator: Panic: data stack: Out of memory when allocating 1073741864 bytes Mar 21 14:46:59 bubba dovecot: replicator: Error: Raw backtrace: /usr/local/lib/dovecot/libdovecot.so.0(+0x97c90) [0x7f4638a7cc90] -> /usr/local/lib/dovecot/libdovecot.so.0(+0x97d6e) [0x7f4638a7cd6e] -> /usr/local/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f4638a14322] -> /usr/local/lib/dovecot/libdovecot.so.0(+0x95e3f) [0x7f4638a7ae3f] -> /usr/local/lib/dovecot/libdovecot.so.0(+0x9608b) [0x7f4638a7b08b] -> /usr/local/lib/dovecot/libdovecot.so.0(+0xb15f8) [0x7f4638a965f8] -> /usr/local/lib/dovecot/libdovecot.so.0(+0x93c42) [0x7f4638a78c42] -> /usr/local/lib/dovecot/libdovecot.so.0(buffer_write+0x74) [0x7f4638a78fb4] -> dovecot/replicator(replicator_queue_push+0x13b) [0x40519b] -> dovecot/replicator() [0x4049c2] -> dovecot/replicator() [0x4040a8] -> dovecot/replicator() [0x404275] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x52) [0x7f4638a907d2] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0xe7) [0x7f4638a91d17] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x3c) [0x7f4638a9086c] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7f4638a90a28] -> /usr/local/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f4638a1dfc3] -> dovecot/replicator(main+0x17a) [0x40342a] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7f4638640ec5] -> dovecot/replicator() [0x4034c5] Mar 21 14:47:00 bubba dovecot: replicator: Fatal: master: service(replicator): child 15650 killed with signal 6 (core dumped) -- Daniel

4 7

One way dsync replication with dsync -R
by Wolfgang Hennerbichler 24 Mar '17

24 Mar '17

Hi dovecot users, I’ve found the -R parameter for dsync. Does this enable one-way syncing if enabled on the slave in replication_dsync_parameters? The documentation doesn’t mention much what happens if I enable this on the “replciation slave”. Before you ask: Two way synchronisation causes issues in my installation (see the unanswered thread here: http://www.dovecot.org/list/dovecot/2017-March/107431.html) it causes unread, deleted messages to re-appear. I would hope that one-way synchronisation would avoid this, but I’d also like to know if the -R parameter is safe to use. I am also still wondering if anybody has a perfectly working 2-way-synchronised dovecot installation (and I’m interested in your dovecot -n). wogri

2 5

FTS on shared/virtual folders
by Daniel Miller 24 Mar '17

24 Mar '17

A question on how FTS is implemented with regards to shared & virtual mailbox. In particular - with Solr. Does Dovecot treat each shared and virtual mailbox as completely independent - which means Solr would reindex each appearance independently? If that's the case, has any thought been given to potentially identifying such queries and passing them to Solr against the "native" or private mailboxes that are referenced? -- Daniel

1 0

"Connection queue full" error
by Mark Moseley 24 Mar '17

24 Mar '17

Just a quickie: why is "Connection queue full" logged under Info, instead of something like error? Or at least have the word 'error' in it? Seems like a pretty error-ish thing to happen. Anything that causes the connection to fail from the server side should show up in a grep -i for error. I.e. I don't care about clients failing to match up SSL cipher suites; that's fine as Info (SSL errors ironically do have 'error' in them, though I assume that's coming from the ssl libs). But the server dropping connections due to running out of available daemons (and any other "server isn't working right" conditions) is definitely worthy of Error.

1 0

dsync with namespaces
by Tom Sommer 23 Mar '17

23 Mar '17

I have a major dsync headache which I am hoping someone can help me with. I have to migrate mails from a 'namespace/inbox/prefix=INBOX.' server to a 'namespace/inbox/prefix=' server. So I'm trying # dsync -o 'namespace/inbox/prefix=' sync -1 -f -u xx(a)xx.com tcp:1.2.3.4 It works fine for some accounts, however for others many hundreds and sometimes thousands of mails go missing from the destination inbox, and a resync doesn't pick them up. The debug output doesn't recognize these either. If I remove the 'namespace/inbox/prefix=' part, then I get 'Error: Couldn't find namespace for mailbox X' errors. Both source and destination is running 2.2.27 I can't imapsync :S Thanks. -- Tom

1 0

Re: Can't verify remote server certs without trusted CAs (ssl_client_ca_* settings)
by Ralf Hildebrandt 23 Mar '17

23 Mar '17

* Aki Tuomi <aki.tuomi(a)dovecot.fi>: > Could you send us the gdb bt full backtrace for the core file? Currently I can't get it to create coredumps doveconf -n: # 2.2.devel (3f97702): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.devel (023f391) # OS: Linux 4.4.0-65-generic x86_64 Ubuntu 16.04.2 LTS auth_mechanisms = plain login default_vsz_limit = 1 G imapc_host = exchange-imap.charite.de imapc_port = 993 imapc_ssl = imaps imapc_ssl_verify = no listen = *,:: mail_gid = imapproxy mail_home = /home/imapproxy/%u mail_location = imapc:~/imapc mail_plugins = mail_log notify mail_uid = imapproxy passdb { args = host=exchange-imap.charite.de port=993 ssl=imaps default_fields = userdb_imapc_user=%u userdb_imapc_password=%w userdb_imapc_host=exchange-imap.charite.de userdb_imapc_ssl=imaps userdb_imapc_port=993 driver = imap } plugin { sieve = file:~/sieve;active=~/.dovecot.sieve } protocols = imap service auth { inet_listener { address = 127.0.0.1 port = 12345 } } ssl = required ssl_ca = </etc/ssl/certs/ca-certificates.crt ssl_cert = </etc/dovecot/dovecot.pem ssl_cipher_list = EECDH+ECDSA+AESGCM:EECDH+aRSA+AESGCM:EECDH+ECDSA+SHA384:EECDH+ECDSA+SHA256:EECDH+aRSA+SHA384:EECDH+aRSA+SHA256:EECDH+aRSA+RC4:EECDH:EDH+aRSA:!aNULL:!eNULL:!LOW:!3DES:!MD5:!EXP:!PSK:!SRP:!DSS:!RC4 ssl_client_ca_file = /etc/ssl/certs/ca-certificates.crt ssl_key = # hidden, use -P to show it ssl_prefer_server_ciphers = yes ssl_protocols = !SSLv2 !SSLv3 userdb { driver = prefetch } verbose_proctitle = yes 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 4

Ubuntu Dovecot 2.2.9 several Errors, Transaction log as well as BUG message
by Kein Name 23 Mar '17

23 Mar '17

Hello List, I am running an Ubuntu 14.04.5 LTS Server with Dovecot 2.2.9, only local filesystems and authentication done via mysql backend. Server is a Strato Virtual Server running 2.6.32-042stab120.11 #1 SMP Fri Mar 10 16:52:50 MSK 2017 i686 i686 i686 GNU/Linux Sometimes I see errors in the log like this for one user: Error: Transaction log /var/vmail/ example.net/jena/Maildir/.Archives.2017/dovecot.index.log: duplicate transaction log sequence (2) After seeing these, some time later, (mostly 2h), Dovecot starts to deny login from all clients with messages like this: Mar 23 01:32:27 h2312250 dovecot: auth: Error: BUG: Authentication client sent unknown handshake command: REQUEST?1804861441?19318?1?9ce500129289a0237e4e85a6c880a047?session_pid=19323... Mar 23 01:32:27 h2312250 dovecot: imap: Error: Authentication server didn't send valid SPID as expected: MECH#011PLAIN#011plaintext Mar 23 01:32:27 h2312250 dovecot: imap: Error: Disconnected from auth server, aborting (client-pid=19318 client-id=1) Mar 23 01:32:27 h2312250 dovecot: imap-login: Internal login failure (pid=19318 id=1) (internal failure, 1 successful auths): user=< user(a)example.net>, method=PLAIN, rip=X, lip=X, mpid=19323, session=<G9f4AltL4ABRqZ4X> I do not know if these problems have something to do with each other or not. But it happened several times now (maybe once or twice every month or so). When I restart Dovecot, the error seems gone for the moment, until it comes back in a month or some weeks. For reference, here is the running config: dovecot.conf # 2.2.9: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-042stab120.11 i686 Ubuntu 14.04.5 LTS auth_mechanisms = plain login auth_verbose = yes disable_plaintext_auth = no log_timestamp = "%Y-%m-%d %H:%M:%S " managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave passdb { args = /etc/dovecot/dovecot-mysql.conf driver = sql } plugin { quota = maildir:User quota quota_rule = *:bytes=10M sieve = ~/dovecot.sieve } protocols = imap pop3 sieve service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-master { mode = 0600 user = vmail } user = root } ssl_cert = </etc/postfix/sslcert/mailserver.crt ssl_key = </etc/postfix/sslcert/mailserver.key userdb { args = /etc/dovecot/dovecot-mysql.conf driver = sql } protocol pop3 { mail_plugins = quota pop3_uidl_format = %08Xu%08Xv } protocol imap { mail_plugins = quota imap_quota } protocol lda { auth_socket_path = /var/run/dovecot/auth-master mail_plugins = sieve quota postmaster_address = postmaster(a)example.net quota_full_tempfail = yes } dovecot-mysql.conf driver = mysql connect = host=localhost dbname=mail user=user password=XXX default_pass_scheme = CRYPT password_query = SELECT password FROM users WHERE email = '%u' user_query = SELECT CONCAT('/var/vmail/',SUBSTRING_INDEX(email,'@',-1),'/',SUBSTRING_INDEX(email,'@',1),'/') AS home, CONCAT('maildir:/var/vmail/',SUBSTRING_INDEX(email,'@',-1),'/',SUBSTRING_INDEX(email,'@',1),'/Maildir/') AS mail, 5000 AS uid, 5000 AS gid, concat('*:bytes=', quota) AS quota_rule FROM users WHERE email = '%u' Any help is appreciated. Thanks Stefan Koenig

2 2

dovecot configuration oops
by Liam Parker 23 Mar '17

23 Mar '17

Hi, I've just transitioned from using courier to dovecot. Thanks for making this possible. During the 'quite simple' transition process, I didn't do much prep as I'm in more of a more of a fix-compile-fix-compile mode rather than a 'read all the docs first' so you may just want to give up now :) If you are still with me, I just wanted to say, it wasn't completely obvious that I needed a password and a user database [PAM not virtual]. Maybe that's just me but anyway, I spent longer than I should have trying to get PAM to work before eventually realising 'internal error check server logs' meant 'where's your user database'. I guess I assumed PAM could cover it all. If you are in to that kind of thing (usability), it might be sensible to have some kind of "basic errors" check during the config file parse phase which picks up stuff like this and points out a more specific error. I did check the logs vigorously and I even turn on every kind of debug_ (to the extent I started getting plain text passwords in the log!) but the 'internal server error check logs' was actually the only log entry for this issue. In case the point is still unclear, I would have spent less time running in the wrong direction if the error message had been "At least one user database must be configured" or some such. I completely understand if your philosophy is "read the manual or suffer the consequences" and it wasn't a complete fail but a simple up front config check could have helped. Thanks for your time today, Kind Regards, Liam

2 1

Understanding quotas
by Robert Moskowitz 23 Mar '17

23 Mar '17

Just to level-set, I am using Centos7-arm which supplies Dovecot 2.2.10. I don't have access to a arm build or mock environment and use what is available (I DID try to install them but had dependency issues). Much of what I have is from campworld, but some I have picked up from other Centos mailserver builders. Also I am using Postfixadmin which provides quotas per user in mysql database. To access those quotas for dovecot, I have the following script: cat <<EOF>/etc/dovecot/dovecot-dict-quota.conf || exit 1 connect = host=localhost dbname=postfix user=postfix password=$Postfix_Database_Password map { pattern = priv/quota/storage table = quota2 username_field = username value_field = bytes } map { pattern = priv/quota/messages table = quota2 username_field = username value_field = messages } EOF Where $Postfix_Database_Password is an env variable in my install howto. I am setting up quota plugins as follows: sed -i "/#mail_plugins/ a mail_plugins = quota sieve" /etc/dovecot/conf.d/15-lda.conf sed -i "/#mail_plugins / a mail_plugins = quota imap_quota trash" /etc/dovecot/conf.d/20-imap.conf sed -i "/#mail_plugins/ a mail_plugins = quota" /etc/dovecot/conf.d/20-pop3.conf But I am having 'challenges' with how to actually enable quotas and understanding 90-quota.conf. I am starting from campworld's 'reduced' dovecot.conf seeing: dict { quotadict = mysql:/etc/dovecot/dovecot-dict-quota.conf } and plugin { quota = dict:user::proxy::quotadict acl = vfile:/etc/dovecot/acls trash = /etc/dovecot/trash.conf sieve_global_path = /home/sieve/globalfilter.sieve sieve = ~/dovecot.sieve sieve_dir = ~/sieve sieve_global_dir = /home/sieve/ #sieve_extensions = +notify +imapflags sieve_max_script_size = 1M } I have put the sieve plugin lines into the 90-sieve.conf and the acl into 10-acl.conf. Trash is a separate matter for a later question... So I am looking for guidance as to how to integrate the Postfixadmin quota information properly into 90-quota.conf thank you

2 3

Re: replicator crashing - oom
by Daniel Miller 22 Mar '17

22 Mar '17

Think I got it: #0 0x00007fddaf597c37 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 #1 0x00007fddaf59b028 in __GI_abort () at abort.c:89 #2 0x00007fddaf9c0c86 in default_fatal_finish (type=<optimized out>, status=status@entry=0) at failures.c:201 #3 0x00007fddaf9c0d6e in i_internal_fatal_handler (ctx=0x7fff7197d000, format=<optimized out>, args=<optimized out>) at failures.c:670 #4 0x00007fddaf958322 in i_panic (format=format@entry=0x7fddafa047b8 "data stack: Out of memory when allocating %lu bytes") at failures.c:275 #5 0x00007fddaf9bee3f in mem_block_alloc (min_size=536870912) at data-stack.c:341 #6 0x00007fddaf9bf08b in t_malloc_real (size=size@entry=536870912, permanent=permanent@entry=true) at data-stack.c:396 #7 0x00007fddaf9bf0ca in t_malloc (size=size@entry=536870912) at data-stack.c:442 #8 0x00007fddaf9da5f8 in pool_data_stack_realloc (pool=<optimized out>, mem=0x7fdd99f59038, old_size=268435449, new_size=536870912) at mempool-datastack.c:126 #9 0x00007fddaf9bcc42 in p_realloc (new_size=<optimized out>, old_size=<optimized out>, mem=<optimized out>, pool=<optimized out>) at mempool.h:88 #10 buffer_alloc (buf=buf@entry=0xf849a8, size=536870912) at buffer.c:36 #11 0x00007fddaf9bcfb4 in buffer_check_limits (data_size=32, pos=268435424, buf=0xf849a8) at buffer.c:75 #12 buffer_write (_buf=0xf849a8, pos=268435424, data=0xfa0420, data_size=32) at buffer.c:187 #13 0x000000000040519b in array_append_i (count=1, data=0xfa0420, array=<synthetic pointer>) at ../../../src/lib/array.h:168 #14 replicator_queue_handle_sync_lookups (user=0xfa3fc0, queue=0xf92260) at replicator-queue.c:278 ---Type <return> to continue, or q <return> to quit--- #15 replicator_queue_push (queue=0xf92260, user=0xfa3fc0) at replicator-queue.c:296 #16 0x00000000004049c2 in dsync_callback (reply=DSYNC_REPLY_OK, state=0xf84590 "AQAAAHX+sC3O3gNSjAoAAOEwx0RQoclMAwAAAAQ", 'A' <repeats 20 times>, "DAAAAEu2cNfSIZk0oMgAAO8QcX0yhyUwDAAAAlg", 'A' <repeats 20 times>, "IAAADFjqMEUPIEU+IlAACdtazLUaHJTAcAAAAI", 'A' <repeats 20 times>, "BwAAAEfYPTqXct9VYRMAAJ21"..., context=0xfa1560) at replicator-brain.c:121 #17 0x00000000004040a8 in dsync_callback (client=0xfa14a0, state=<optimized out>, reply=DSYNC_REPLY_OK) at dsync-client.c:65 #18 0x0000000000404275 in dsync_input_line (line=0xf84988 "+", client=0xfa14a0) at dsync-client.c:132 #19 dsync_input (client=0xfa14a0) at dsync-client.c:153 #20 0x00007fddaf9d47d2 in io_loop_call_io (io=0xfa15a0) at ioloop.c:599 #21 0x00007fddaf9d5d17 in io_loop_handler_run_internal (ioloop=ioloop@entry=0xf8c720) at ioloop-epoll.c:223 #22 0x00007fddaf9d486c in io_loop_handler_run (ioloop=ioloop@entry=0xf8c720) at ioloop.c:648 #23 0x00007fddaf9d4a28 in io_loop_run (ioloop=0xf8c720) at ioloop.c:623 #24 0x00007fddaf961fc3 in master_service_run (service=0xf8c5c0, callback=callback@entry=0x404720 <client_connected>) at master-service.c:641 #25 0x000000000040342a in main (argc=1, argv=0xf8c390) at replicator.c:112 Daniel On 3/22/2017 9:11 AM, Daniel Miller wrote: > Where would I find the core file? I'm not finding anything obvious. > > The replicator path is /usr/local/libexec/dovecot/replicator > > Daniel > > On 3/22/2017 12:52 AM, Aki Tuomi wrote: >> Can you provide us gdb bt full dump? >> >> gdb /usr/libexec/dovecot/replicator /path/to/core >> >> on some systems, it's /usr/lib/dovecot/replicator >> >> Aki >> >> On 21.03.2017 23:48, Daniel Miller wrote: >>> I have the following in my log: >>> >>> Mar 21 14:46:59 bubba dovecot: replicator: Panic: data stack: Out of >>> memory when allocating 1073741864 bytes >>> Mar 21 14:46:59 bubba dovecot: replicator: Error: Raw backtrace: >>> /usr/local/lib/dovecot/libdovecot.so.0(+0x97c90) [0x7f4638a7cc90] -> >>> /usr/local/lib/dovecot/libdovecot.so.0(+0x97d6e) [0x7f4638a7cd6e] -> >>> /usr/local/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f4638a14322] -> >>> /usr/local/lib/dovecot/libdovecot.so.0(+0x95e3f) [0x7f4638a7ae3f] -> >>> /usr/local/lib/dovecot/libdovecot.so.0(+0x9608b) [0x7f4638a7b08b] -> >>> /usr/local/lib/dovecot/libdovecot.so.0(+0xb15f8) [0x7f4638a965f8] -> >>> /usr/local/lib/dovecot/libdovecot.so.0(+0x93c42) [0x7f4638a78c42] -> >>> /usr/local/lib/dovecot/libdovecot.so.0(buffer_write+0x74) >>> [0x7f4638a78fb4] -> dovecot/replicator(replicator_queue_push+0x13b) >>> [0x40519b] -> dovecot/replicator() [0x4049c2] -> dovecot/replicator() >>> [0x4040a8] -> dovecot/replicator() [0x404275] -> >>> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x52) >>> [0x7f4638a907d2] -> >>> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0xe7) >>> >>> [0x7f4638a91d17] -> >>> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x3c) >>> [0x7f4638a9086c] -> >>> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_run+0x38) >>> [0x7f4638a90a28] -> >>> /usr/local/lib/dovecot/libdovecot.so.0(master_service_run+0x13) >>> [0x7f4638a1dfc3] -> dovecot/replicator(main+0x17a) [0x40342a] -> >>> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) >>> [0x7f4638640ec5] -> dovecot/replicator() [0x4034c5] >>> Mar 21 14:47:00 bubba dovecot: replicator: Fatal: master: >>> service(replicator): child 15650 killed with signal 6 (core dumped) >>>

1 0

Permission denied when logrotating dovecot.log
by Michael Heuberger 22 Mar '17

22 Mar '17

Hello guys Having headaches here how to make logrotation for dovecot log files work. Having permission issues: michael.heuberger@xxx /e/l/daily ❯❯❯ sudo logrotate -fv dovecot.daily ⏎ reading config file dovecot.daily Handling 1 logs rotating pattern: /var/log/dovecot*.log forced from command line (10 rotations) empty log files are rotated, old logs are removed considering log /var/log/dovecot.log error: skipping "/var/log/dovecot.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. This is my current logrotation conf for dovecot: /var/log/dovecot*.log { rotate 10 missingok sharedscripts postrotate doveadm log reopen endscript } And the /var/log folder has these permissions: drwxrwxr-x 12 root syslog 4.0K Mar 19 12:43 log Any clues what's wrong? Thanks Michael -- Binary Kitchen Michael Heuberger 1/33 Parrish Road Sandringham Auckland 1025 (New Zealand) Mobile (text only) ... +64 21 261 89 81 Email ................ michael(a)binarykitchen.com Website .............. http://www.binarykitchen.com

5 9

SIS and mailbox restore
by Jean-Luc Oms 22 Mar '17

22 Mar '17

Still on the problem with dovecot 2.2.27 .... I use the single instance storage, and mdbox format. I use 2 zfs file systems, one for mailboxes, the other for attachements. I use znapzend to generate many zfs snapshots for backup purpose (inode numbers are preserved but it is unusefull). When I try to restore a deleted/purged mailbox with doveadm import I get the error of the first attachement missing in the SIS and the process stops. Option 1: the python script is working but it's really too long. * I restore all the SIS missing files since the snapshot date, preserving hard link count; * I restore the mailbox * I purge all the mailbox to delete the large number of unnecessery files restored Option 2: looking in the list archive I see that doveadm dump can guive me the msg.ext-ref that was missing to my knowledge. I try this use of doveadm dump: doveadm dump /MySnapShot/vmail/user/mdbox/storage/m.* Is this correct to get all the information I need ? I have to write a script to get msg.ext-ref for a particular msf.guid, or a specific mailbox Is there a way with doveadm dump to extract this type of information for a particular mailbox ? Thanks for your support. -- __________________________________________ Jean-Luc Oms STI-RéseauX - LIRMM - CNRS/UM2 161 rue Ada - BAT 4 - CC 477 34095 Montpellier cedex 5 Tel +33 4 67 41 85 93 Urg +33 6 32 01 04 17 __________________________________________

1 0

[Sieve] Is the way to run external script to get attachment?
by Konstantin Shalygin 22 Mar '17

22 Mar '17

Hello. Read all about Extprograms, but have a question. Use case: Every day we have couple messages with attachment (from one sender, this is one-way communication). This attachment is uploads to ownCloud. By hand... need some automation. As I see, pipe cat execute scripts with text data USER/FROM/SUBJECT - and I think with variables it can be any text data, how about attachment? How I see this: script executes and as arg receives from sieve attachment file, or message file and we can parse it for attachment. When we have attachment - upload to ownCloud via RESTapi and purge message. Found some realization for encrypt messages https://github.com/EtiennePerot/gpgit/blob/master/encmaildir.sh but for me more easy just connect to IMAP and do what I want (but I love sieve). Thanks. <http://wiki.dovecot.org/Pigeonhole/Sieve/Plugins/Extprograms>

2 2

Problem with sieve_before
by Ger Hooton Scoil Chroí Íosa Blarney 22 Mar '17

22 Mar '17

Hi All, I cannot get the sieve_before to work. I have dovecot & sieve installed on Debian 7 as follows /etc/dovecot/conf.d/90-sieve.conf : plugin { # The path to the user's main active script. If ManageSieve is used, this the # location of the symbolic link controlled by ManageSieve. sieve = ~/.dovecot.sieve # The default Sieve script when the user has none. This is a path to a global # sieve script file, which gets executed ONLY if user's private Sieve script # doesn't exist. Be sure to pre-compile this script manually using the sievec # command line tool. # --> See sieve_before fore executing scripts before the user's personal # script. sieve_default = /var/lib/dovecot/sieve/default.sieve # Directory for :personal include scripts for the include extension. This # is also where the ManageSieve service stores the user's scripts. sieve_dir = ~/sieve/ # Directory for :global include scripts for the include extension. sieve_global_dir = /var/lib/dovecot/sieve/ # Path to a script file or a directory containing script files that need to be # executed before the user's script. If the path points to a directory, all # the Sieve scripts contained therein (with the proper .sieve extension) are # executed. The order of execution within a directory is determined by the # file names, using a normal 8bit per-character comparison. Multiple script # file or directory paths can be specified by appending an increasing number. sieve_before = /var/lib/dovecot/sieve/before #####sieve_before2 = /var/lib/dovecot/sieve/before/default2.sieve #sieve_before3 = (etc...) # Identical to sieve_before, only the specified scripts are executed after the # user's script (only when keep is still in effect!). Multiple script file or # directory paths can be specified by appending an increasing number. #sieve_after = #sieve_after2 = #sieve_after2 = (etc...) # Which Sieve language extensions are available to users. By default, all # supported extensions are available, except for deprecated extensions or # those that are still under development. Some system administrators may want # to disable certain Sieve extensions or enable those that are not available # by default. This setting can use '+' and '-' to specify differences relative # to the default. For example `sieve_extensions = +imapflags' will enable the # deprecated imapflags extension in addition to all extensions were already # enabled by default. #sieve_extensions = +notify +imapflags ................................. In /var/lib/dovecot/sieve/before I have : drwxrwxrwx 3 mail mail 4096 Mar 20 23:47 .. -rw-rw-rw- 1 root root 195 Mar 21 09:57 default2.svbin -rwxrwxrwx 1 mail mail 157 Mar 21 11:12 default2.sieve default2.sieve is as follows: require ["fileinto"]; if allof (header :matches "subject" "*JUNK*") { fileinto "INBOX.Junk"; } The users personal filters work. Thanks for your help. __________________________________________________ Please consider the environment before printing this email. Ger

3 13

getmail with dovecot delivering problems
by Samuel Reina Calvo 22 Mar '17

22 Mar '17

Hi there, I put together a mail server with postfix+dovecot+mysql with virtual users and it works just fine as internal mail server, but when i put ir under a multidrop email server it sends ok but so far coulnd make getmail to deliver mails correctly. the use of getmail + dovecot downloads email via pop3 but then put all the emails in the same inbox. my maildir is /var/vmail/[domain] getmalirc conf is [retriever]type = MultidropPOP3Retriver server username password envelope_recipient = delivered-to:1 [destination] type = MDA_external path = /usr/local/libexec/dovecot/deliverthen when i run sudo -H -u vmail bash -c 'getmail -g /etc/.getmail -r /etc/.getmail/getmailrc' i get all the time all the messages delivered into /var/vmail/vmail (being vmail the linux user who handles my virtual users) __________ Información de ESET NOD32 Antivirus, versión de la base de firmas de virus 14929 (20170213) __________ ESET NOD32 Antivirus ha comprobado este mensaje. http://www.eset.com

2 1

last_login LDAP - killed with signal 11 (core dumped)
by Leon Kyneur 22 Mar '17

22 Mar '17

Hi I am trying to configure the last_login plugin with LDAP dictionary which is causing dict service to crash. Not sure if this is a bug or some configuration parameter I'm getting wrong? Running latest dovecot but was having the same problem in earlier version 2.2.25 # dovecot --version 2.2.28 (bed8434) I have configured dovecot like so: dovecot.conf (before conf.d/*.conf: dict { #quota = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext #expire = sqlite:/etc/dovecot/dovecot-dict-sql.conf.ext lastlogin = ldap:/etc/dovecot/dovecot-ldap-dict.conf.ext } conf.d/10-master.conf service dict { # If dict proxy is used, mail processes should have access to its socket. # For example: mode=0660, group=vmail and global mail_access_groups=vmail unix_listener dict { mode = 0660 user = vmail group = vmail } } conf.d/20-imap.conf: protocol imap { # Space separated list of plugins to load (default is global mail_plugins). mail_plugins = $mail_plugins last_login # Maximum number of IMAP connections allowed for a user from each IP address. # NOTE: The username is compared case-sensitively. #mail_max_userip_connections = 10 } 90-plugins.conf plugin { #setting_name = value #last_login_dict = proxy::lastlogin last_login_dict = proxy:dict:lastlogin zlib_save = gz zlib_save_level = 6 } dovecot-ldap-dict.conf.ext: uri = ldap://ldap.internal bind_dn = cn=Manager,dc=mail,dc=com password = XXXX tls = no debug = 1 map { pattern = last-login/$user filter = (&(mail=%{user})(objectClass=mailUser)) # the () is required base_dn = o=domains,dc=mail,dc=com username_attribute = mail value_attribute = lastLoginTime fields { mail=$user } } I don't see dovecot ever making a connection to the LDAP server I've configured in the dovecot-ldap-dict.conf.ext file. Log shows ==> /var/log/dovecot.log <== Mar 22 07:49:30 imap-login: Info: Login: user=<leon(a)mail.com>, method=PLAIN, rip=X.X.X.X, lip=X.X.X.X, mpid=36105, secured, session=<o0Lu/0xL4N3LhgGR> Mar 22 07:49:30 dict: Fatal: master: service(dict): child 36107 killed with signal 11 (core dumped) Mar 22 07:49:30 imap(leon(a)mail.com): Error: dict-client: Commit may have failed: Connection closed (reply took 0.015 secs) Mar 22 07:49:30 imap(leon(a)mail.com): Error: last_login_dict: Write was unconfirmed (timeout or disconnect) for user leon(a)mail.com Backtrace: # gdb /var/core/36107 GNU gdb (GDB) Red Hat Enterprise Linux 7.6.1-94.el7 Copyright (C) 2013 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-redhat-linux-gnu". For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>... [New LWP 36107] Reading symbols from /usr/libexec/dovecot/dict...Reading symbols from /usr/lib/debug/usr/libexec/dovecot/dict.debug...done. done. Missing separate debuginfo for Try: yum --enablerepo='*debug*' install /usr/lib/debug/.build-id/b0/07fede01895dec1aca9d8b8993fe27d70a3a20 [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". Core was generated by `dovecot/dict'. Program terminated with signal 11, Segmentation fault. #0 0x0000000000000000 in ?? () (gdb) bt full #0 0x0000000000000000 in ?? () No symbol table info available. #1 0x00007fbcf11bd04f in cmd_begin (cmd=0x7fbcf2c02910, line=<optimized out>) at dict-commands.c:365 trans = 0x7fbcf2c029a0 id = 1 #2 0x00007fbcf11bdef8 in dict_command_input (conn=conn@entry=0x7fbcf2bf24d0, line=line@entry=0x7fbcf2bf48cb "B1") at dict-commands.c:625 cmd_func = 0x7fbcf13c85c0 <cmds+32> cmd = 0x7fbcf2c02910 ret = <optimized out> #3 0x00007fbcf11bc6ee in dict_connection_input_more (conn=0x7fbcf2bf24d0) at dict-connection.c:117 _data_stack_cur_id = 3 line = 0x7fbcf2bf48cb "B1" ret = <optimized out> #4 0x00007fbcf11bc7d2 in dict_connection_input (conn=0x7fbcf2bf24d0) at dict-connection.c:167 line = <optimized out> conn = 0x7fbcf2bf24d0 #5 0x00007fbcf0d1b2d2 in io_loop_call_io (io=0x7fbcf2bf2890) at ioloop.c:599 ioloop = 0x7fbcf2be0740 t_id = 2 __FUNCTION__ = "io_loop_call_io" #6 0x00007fbcf0d1c95f in io_loop_handler_run_internal (ioloop=ioloop@entry=0x7fbcf2be0740) at ioloop-epoll.c:223 ctx = 0x7fbcf2beded0 events = <optimized out> list = 0x7fbcf2bf28f0 io = <optimized out> tv = {tv_sec = 2147483, tv_usec = 0} events_count = <optimized out> msecs = <optimized out> ret = 1 i = 0 call = <optimized out> __FUNCTION__ = "io_loop_handler_run_internal" #7 0x00007fbcf0d1b36c in io_loop_handler_run (ioloop=ioloop@entry=0x7fbcf2be0740) at ioloop.c:648 No locals. #8 0x00007fbcf0d1b528 in io_loop_run (ioloop=0x7fbcf2be0740) at ioloop.c:623 __FUNCTION__ = "io_loop_run" #9 0x00007fbcf0ca4603 in master_service_run (service=0x7fbcf2be05e0, callback=callback@entry=0x7fbcf11be150 <client_connected>) at master-service.c:641 No locals. #10 0x00007fbcf11bbff9 in main (argc=1, argv=0x7fbcf2be0390) at main.c:161 set_roots = {0x7fbcf13c88a0 <dict_setting_parser_info>, 0x0} error = 0x0

2 3

Help
by Bhushan Bhosale 22 Mar '17

22 Mar '17

Hello, I'm getting below error in /var/log/dovecot-proxy.log. Please help. Thanks in advance. Mar 21 14:40:36 tejas3 dovecot: director: Error: Director 192.168.1.11/in disconnected: Connection closed: Illegal seek (connected 0 secs, in=0 out=43, handshake ME not received Regards, Bhushan

2 1

dovecot POP3 log shows too many identical RETR entries
by Bappasaheb Nirmal 22 Mar '17

22 Mar '17

Hello, Dovecot log is showing too many POP3 RETR entries which are identical lines. I also suspect that it is causing high pop traffic eating most of the network bandwidth. Here are some of the lines out of 11009 in a day. Such pattern is observed only for few users. dovecot version is 2.1.17. ============== Mar 20 00:00:07 pi3 dovecot: pop3(user(a)example.com): Disconnected: Logged out top=0/0, retr=1/64014, del=0/1429, size=478762716 Mar 20 00:00:07 pi3 dovecot: pop3-login: Login: user=<user(a)example.com>, method=PLAIN, rip=43.243.173.97, lip=192.168.1.18, mpid=26645, secured, session=<5CGrmRlLyAAr861h> Mar 20 00:00:10 pi3 dovecot: pop3(user(a)example.com): Disconnected: Logged out top=0/0, retr=1/64014, del=0/1429, size=478762716 Mar 20 00:00:11 pi3 dovecot: pop3-login: Login: user=<user(a)example.com>, method=PLAIN, rip=43.243.173.97, lip=192.168.1.18, mpid=29932, secured, session=<k6/gmRlL3gAr861h> Mar 20 00:00:12 pi3 dovecot: pop3(user(a)example.com): Disconnected: Logged out top=0/0, retr=1/64014, del=0/1429, size=478762716 Mar 20 00:00:13 pi3 dovecot: pop3-login: Login: user=<user(a)example.com>, method=PLAIN, rip=43.243.173.97, lip=192.168.1.18, mpid=26819, secured, session=<3DX6mRlLUQAr861h> Mar 20 00:00:14 pi3 dovecot: pop3(user(a)example.com): Disconnected: Logged out top=0/0, retr=1/64014, del=0/1429, size=478762716 Mar 20 00:00:15 pi3 dovecot: pop3-login: Login: user=<user(a)example.com>, method=PLAIN, rip=43.243.173.97, lip=192.168.1.18, mpid=9636, secured, session=<x5ghmhlLjwAr861h> Mar 20 00:00:16 pi3 dovecot: pop3(user(a)example.com): Disconnected: Logged out top=0/0, retr=1/64014, del=0/1429, size=478762716 Mar 20 00:00:17 pi3 dovecot: pop3-login: Login: user=<user(a)example.com>, method=PLAIN, rip=43.243.173.97, lip=192.168.1.18, mpid=4585, secured, session=<8Yw+mhlL0AAr861h> Mar 20 00:00:18 pi3 dovecot: pop3(user(a)example.com): Disconnected: Logged out top=0/0, retr=1/64014, del=0/1429, size=478762716 Mar 20 00:00:18 pi3 dovecot: pop3-login: Login: user=<user(a)example.com>, method=PLAIN, rip=43.243.173.97, lip=192.168.1.18, mpid=30049, secured, session=<UsJOmhlLmAAr861h> Mar 20 00:00:19 pi3 dovecot: pop3(user(a)example.com): Disconnected: Logged out top=0/0, retr=1/64014, del=0/1429, size=478762716 Mar 20 00:00:20 pi3 dovecot: pop3-login: Login: user=<user(a)example.com>, method=PLAIN, rip=43.243.173.97, lip=192.168.1.18, mpid=9636, secured, session=<B6VimhlLNgAr861h> Mar 20 00:00:20 pi3 dovecot: pop3(user(a)example.com): Disconnected: Logged out top=0/0, retr=1/64014, del=0/1429, size=478762716 Mar 20 00:00:20 pi3 dovecot: pop3-login: Login: user=<user(a)example.com>, method=PLAIN, rip=43.243.173.97, lip=192.168.1.18, mpid=4584, secured, session=<pVpxmhlLPwAr861h> Mar 20 00:00:21 pi3 dovecot: pop3(user(a)example.com): Disconnected: Logged out top=0/0, retr=1/64014, del=0/1429, size=478762716 Mar 20 00:00:23 pi3 dovecot: pop3-login: Login: user=<user(a)example.com>, method=PLAIN, rip=43.243.173.97, lip=192.168.1.18, mpid=4585, secured, session=<MlGam ============== What could be the possible reason? Thanks, Bappasaheb

2 2

Crash on doveadm index
by Larry Rosenman 22 Mar '17

22 Mar '17

http://www.lerctr.org/~ler/dovecot/doveadm-2017-03-20.txt doveconf –n attached and at: http://www.lerctr.org/~ler/dovecot/doveconf.n.txt -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 E-Mail: larryrtx(a)gmail.com US Mail: 17716 Limpia Crk, Round Rock, TX 78664-7281

2 4

Is it possible to use sieve when delivering via pipe to the dovecot deliver command ?
by Thomas Carrié 21 Mar '17

21 Mar '17

Hello, I am using Exim with this delivery configuration: virtual_delivery: driver = pipe command = /usr/lib/dovecot/deliver -d $local_part@$domain -f ... I have enabled manage-sieve and uploaded a simple sieve script that I can see on the server. man page of /usr/lib/dovecot/deliver says it supports sieve. Mail debug is enabled: $ dovecot -n | grep debug mail_debug = yes Delivering a mail shows only this line in dovecot log: Jan 21 17:38:51 myserver dovecot: lda(joe(a)something.com): msgid=<20170121183537.7313f219@homenetwork>: saved mail to INBOX According to page http://wiki2.dovecot.org/Pigeonhole/Sieve/Troubleshooting#Sieve_Scripts_are… I should have a log saying that the sieve plugin is loaded Here is the sieve relevant parts of dovecot -n: # 2.2.13: /etc/dovecot/dovecot.conf ... plugin { sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } ... protocols = " imap sieve pop3 sieve" ... protocol lda { mail_plugins = " sieve" } Is there a requirement to use delivery via service (unix socket) so that sieve is enabled? Or is there a configuration thing I forgot ? Thank you for your help Thomas

2 2

Re: Corruption & migration
by Daniel Miller 21 Mar '17

21 Mar '17

Now I'm seeing a bunch of these: 02:28 bubba dovecot: dsync-local(user(a)mydomain.com): Error: bzlib.read(/var/mail/mydomain.com/user/mdbox/storage/m.20): corrupted data at 24123649 Mar 21 11:02:28 bubba dovecot: dsync-local(user(a)mydomain.com): Error: dsync(oldserver.host): read(zlib(/var/mail/mydomain.com/user/mdbox/storage/m.20)) failed: read(/var/mail/mydomain.com/user/mdbox/storage/m.20) failed: bzlib.read(/var/mail/mydomain.com/user/mdbox/storage/m.20): corrupted data at 24123649 (last sent=mail, last recv=mail_request (EOL)) Mar 21 11:02:28 bubba dovecot: doveadm: Error: dsync-remote(user(a)mydomain.com): Error: dsync(localhost): read() failed: read((fd)) failed: dot-input stream ends without '.' line (last sent=mail_request (EOL), last recv=mail) Daniel On 3/20/2017 11:30 PM, Daniel Miller wrote: > I'm getting close - I believe I have one-way replication processing > now. It's amazing watching the mails magically appear in the new > server! I'll tender some updates to the wiki in the hopes it will > help others. > > At this time, I have two errors I haven't been able to eliminate with > config changes: > > dovecot: doveadm: Error: dsync-remote(user(a)mydomain.com): Warning: > Transaction log file > /var/mail/mydomain.com/user/sdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.log > was locked for 109 seconds (rotating while syncing) > Mar 20 23:22:04 bubba dovecot: dsync-local(user(a)mydomain.com): Error: > Remote command returned error 75: ssh -lvmail 192.168.0.4 doveadm > dsync-server -uuser(a)mydomain.com > > I don't know if the transaction lock issue will fix itself via > repeated replication runs. But I have no idea what the "error 75" is. > > Daniel > > > On 3/20/2017 10:05 PM, Daniel Miller wrote: >> I have an existing server using mdbox & sis. There is a quantity of >> corruption - I have no idea where it came in. I'd had a previous >> rebuild some years ago and I thought I had a clean datastore. By >> "corruption" I mean missing attachments and either missing or >> mixed-up emails. >> >> I've setup a new server on a virtual machine. Instead of copying the >> old configs I hand-adjusted individual settings using the current >> distribution example. The new server is running...but empty. >> >> So now my intent is to migrate the mail to the new machine. A few >> items to note: >> 1. The existing mail server is the virtual host. The mails are >> stored locally, in mdbox format, with sis enabled. And possibly zlib. >> 2. The new server, via VirtualBox, is presently configured for >> Maildir. I may change to sdbox - I'm now a little reserved about mdbox. >> 3. Instead of storing the mails within the virtual machine, I'm >> using the host's drive. This is via an exported NFS4 folder from the >> host, mounted on the guest, using the options: >> "auto,noatime,hard,intr,async,nordirplus". >> 4. My intent is to have the new virtual server become the primary >> mail server. The mail store will continue to be accessed by NFS4. No >> other servers or processes (besides backup) should access the mail >> store. >> >> So...my question is what is the best method for the migration? >> >> Reading the docs on Dovecot replication I'm still very unsure of how >> to implement it - particularly the "master-master" or "master-client" >> relationships. The docs are not 100% clear on which server gets >> which options. I can guess...which I'd really rather not do. But it >> seems to me getting one-way replication working would be the most >> "elegant" solution here. >> >> Manual dsync is also an option - but again I'm not on which machine I >> should execute which options. >> >> Imapsync is a possibility and the syntax is clear - but very slow in >> execution for 100k mails. >> >> Any suggestions or pointers would be welcome. >>

1 0

New Member
by Ger Hooton Scoil Chroí Íosa Blarney 21 Mar '17

21 Mar '17

Hi All, Before I start posting where /how can I check to see if the question I wish to ask about has already been covered? __________________________________________________ Please consider the environment before printing this email. Ger

3 2

Re: Dovecot can't connect to openldap over starttls [REQUEST OF OPENLDAP]
by info＠gwarband.de 21 Mar '17

21 Mar '17

Can sombody say something about this request? This is an email from the openldap-technical mailinglist from openldap. Systemdetails are mention in the other email. -------- Originalnachricht -------- Betreff: Re: Dovecot can't connect to openldap over starttls Datum: 2017-03-20 16:18 Absender: Dan White <dwhite(a)cafedemocracy.org> Empfänger: info(a)gwarband.de Kopie: openldap-technical(a)openldap.org On 03/20/17 16:06 +0100, info(a)gwarband.de wrote: >> Debug Dovecot's implementation of ldap_start_tls_s(). > I don't have any idea how to set a higher debug level to dovecot. In > my opinion I have the highest. So I can't deliver a greater log. I recommend consulting Dovecot's advice on how to run a debugger, or dig into the code which calls libldap.

2 8

doveadm-sync stateful
by Cédric ML 21 Mar '17

21 Mar '17

Hello, I'm trying to migrate mail accounts from an old server to a new one. As I need to migrate dozens of accounts which take about 1G each, I need to do stateful sync to make my migration in two times : 1 - I run a : doveadm -D -o mail_fsync=never -o imapc_user=user1(a)olddomain.fr sync -s "" -R -1 -u user1(a)newdomain.fr imapc: > /tmp/firstsync.log 2>&1 my accounts are synced, and I get a "state" string (AQAAAHm4+Jk=) as the output of doveadm sync command. 2 - Changes are made on the old server, and I expect next dsync will sync only the changes / new mails. So I run a : doveadm -D -o mail_fsync=never -o imapc_user=user1(a)olddomain.fr sync -s "AQAAAHm4+Jk=" -R -1 -u user1(a)newdomain.fr imapc: > /tmp/secondsync.log 2>&1 My problem is that state of messages are not synchronized (mails marked as read on old server are still unread on new server, mails moved on a folder on the old server are still in the INBOX of new server). The full debug of ran commands is available here : http://fpaste.scsys.co.uk/557551 The result of "doveconf -n" is available here : http://fpaste.scsys.co.uk/557552 I'm using version 2.2.27 Can anyone tell me if I'm doing something wrong ? How can I debug more ? Regards, Cédric

2 2

Re: Corruption & migration
by Daniel Miller 21 Mar '17

21 Mar '17

I'm getting close - I believe I have one-way replication processing now. It's amazing watching the mails magically appear in the new server! I'll tender some updates to the wiki in the hopes it will help others. At this time, I have two errors I haven't been able to eliminate with config changes: dovecot: doveadm: Error: dsync-remote(user(a)mydomain.com): Warning: Transaction log file /var/mail/mydomain.com/user/sdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.log was locked for 109 seconds (rotating while syncing) Mar 20 23:22:04 bubba dovecot: dsync-local(user(a)mydomain.com): Error: Remote command returned error 75: ssh -lvmail 192.168.0.4 doveadm dsync-server -uuser(a)mydomain.com I don't know if the transaction lock issue will fix itself via repeated replication runs. But I have no idea what the "error 75" is. Daniel On 3/20/2017 10:05 PM, Daniel Miller wrote: > I have an existing server using mdbox & sis. There is a quantity of > corruption - I have no idea where it came in. I'd had a previous > rebuild some years ago and I thought I had a clean datastore. By > "corruption" I mean missing attachments and either missing or mixed-up > emails. > > I've setup a new server on a virtual machine. Instead of copying the > old configs I hand-adjusted individual settings using the current > distribution example. The new server is running...but empty. > > So now my intent is to migrate the mail to the new machine. A few > items to note: > 1. The existing mail server is the virtual host. The mails are > stored locally, in mdbox format, with sis enabled. And possibly zlib. > 2. The new server, via VirtualBox, is presently configured for > Maildir. I may change to sdbox - I'm now a little reserved about mdbox. > 3. Instead of storing the mails within the virtual machine, I'm using > the host's drive. This is via an exported NFS4 folder from the host, > mounted on the guest, using the options: > "auto,noatime,hard,intr,async,nordirplus". > 4. My intent is to have the new virtual server become the primary > mail server. The mail store will continue to be accessed by NFS4. No > other servers or processes (besides backup) should access the mail store. > > So...my question is what is the best method for the migration? > > Reading the docs on Dovecot replication I'm still very unsure of how > to implement it - particularly the "master-master" or "master-client" > relationships. The docs are not 100% clear on which server gets which > options. I can guess...which I'd really rather not do. But it seems > to me getting one-way replication working would be the most "elegant" > solution here. > > Manual dsync is also an option - but again I'm not on which machine I > should execute which options. > > Imapsync is a possibility and the syntax is clear - but very slow in > execution for 100k mails. > > Any suggestions or pointers would be welcome. >

1 0

Corruption & migration
by Daniel Miller 21 Mar '17

21 Mar '17

I have an existing server using mdbox & sis. There is a quantity of corruption - I have no idea where it came in. I'd had a previous rebuild some years ago and I thought I had a clean datastore. By "corruption" I mean missing attachments and either missing or mixed-up emails. I've setup a new server on a virtual machine. Instead of copying the old configs I hand-adjusted individual settings using the current distribution example. The new server is running...but empty. So now my intent is to migrate the mail to the new machine. A few items to note: 1. The existing mail server is the virtual host. The mails are stored locally, in mdbox format, with sis enabled. And possibly zlib. 2. The new server, via VirtualBox, is presently configured for Maildir. I may change to sdbox - I'm now a little reserved about mdbox. 3. Instead of storing the mails within the virtual machine, I'm using the host's drive. This is via an exported NFS4 folder from the host, mounted on the guest, using the options: "auto,noatime,hard,intr,async,nordirplus". 4. My intent is to have the new virtual server become the primary mail server. The mail store will continue to be accessed by NFS4. No other servers or processes (besides backup) should access the mail store. So...my question is what is the best method for the migration? Reading the docs on Dovecot replication I'm still very unsure of how to implement it - particularly the "master-master" or "master-client" relationships. The docs are not 100% clear on which server gets which options. I can guess...which I'd really rather not do. But it seems to me getting one-way replication working would be the most "elegant" solution here. Manual dsync is also an option - but again I'm not on which machine I should execute which options. Imapsync is a possibility and the syntax is clear - but very slow in execution for 100k mails. Any suggestions or pointers would be welcome. -- Daniel

1 0

Re: Dovecot 2.2.27 proxy - enforcing per client IP connection limits
by Joseph Tam 21 Mar '17

21 Mar '17

Sami Ketola writes: >> Can anyone with Solr installed confirm/refute this: does installing >> Solr keep iOS clients from roofing the connection count? > > I doubt it, but since IMAP SEARCH goes all the way down to the backends > mail_max_userip_connections can be used to limit the number of > connections. Understood -- that's the current situation I'm in now. Our iOS users would launch a search resulting in a connection burst, hit the connection cap, log out all IMAP sessions out, then start the cycle again. This sometimes lasts for 10's of minutes. I'm not sure what the users sees. Sample logs entries: Mar 19 01:21:30 server dovecot: imap-login: Login: user=<user> ... [... 14 similar logins removed ...] Mar 19 01:21:41 server dovecot: imap-login: Login: user=<user> ... Mar 19 01:21:42 server dovecot: imap-login: Maximum number of connections from user+IP exceeded (mail_max_userip_connections=16) : user=<user> ... Mar 19 01:21:42 server dovecot: imap(user): Logged out in=425 out=1107 [... 14 similar logouts removed ...] Mar 19 01:21:42 server dovecot: imap(user): Logged out in=382 out=1107 Mar 19 01:21:42 server dovecot: imap-login: Login: user=<user> ... Mar 19 01:21:42 server dovecot: imap-login: Login: user=<user> ... Mar 19 01:21:43 server dovecot: imap-login: Login: user=<user> ... Mar 19 01:21:44 server dovecot: imap-login: Login: user=<user> ... Mar 19 01:21:44 server dovecot: imap(user): Logged out in=442 out=1173 Mar 19 01:21:44 server dovecot: imap(user): Logged out in=442 out=1155 Mar 19 01:21:44 server dovecot: imap(user): Logged out in=442 out=1166 Mar 19 01:21:44 server dovecot: imap(user): Logged out in=442 out=1174 Mar 19 01:21:44 server dovecot: imap-login: Login: user=<user> ... Mar 19 01:21:47 server dovecot: imap-login: Login: user=<user> ... Mar 19 01:21:47 server dovecot: imap-login: Login: user=<user> ... Mar 19 01:21:48 server dovecot: imap-login: Login: user=<user> ... Mar 19 01:21:48 server dovecot: imap-login: Login: user=<user> ... Mar 19 01:21:49 server dovecot: imap-login: Login: user=<user> ... { ... and on and on for the next 10 minutes ... } However, there is a pause between each login that might be long enough to squeeze the search results in if given quickly enough. From the I/O stats, most of these searches have empty results. It probably won't prevent the connection cap problem, but it might minimize the length and severity of these connection storms. Of course, the real fix is for iOS mail-app developers to stop assuming the IMAP server is owned exclusively by the user by configuring some reasonable connection throttles. Joseph Tam <jtam.home(a)gmail.com>

2 1

Dovecot can't connect to openldap over starttls
by info＠gwarband.de 20 Mar '17

20 Mar '17

Hello guys, actually I'm trying to configure dovecot to access openldap for passwordcheck. My openldap is only allow access over "secure ldap". The dovecot can communicate with the openldap server but there is maybe a failure in the sslhandshake. Additional information you can find in the logs or in the dump below. Also I have my ldap config from dovecot in the links below. I have already created an bug reporting in the system of openldap but the answer was to get support from her. All datalinks: https://gwarband.de/openldap/dovecot.log https://gwarband.de/openldap/dovecot-ldap.conf https://gwarband.de/openldap/openldap.log https://gwarband.de/openldap/trace.dump The bugreportinglink from openldap: http://www.openldap.org/its/index.cgi/Incoming?id=8615 I hope you can help me. Regards. Tobias Warband

2 10

Can't verify remote server certs without trusted CAs (ssl_client_ca_* settings)
by Ralf Hildebrandt 20 Mar '17

20 Mar '17

Hi! I upgraded the 2.2 packages today (from 2:2.2.28-1~auto+5 to 2:2.2.28-1~auto+8) I now I'm getting an error: Mar 20 13:25:58 mproxy dovecot: auth: Error: imapc(email.charite.de:993): Couldn't initialize SSL context: Can't verify remote server certs without trusted CAs (ssl_client_ca_* settings) I checked, and alas, I had ssl_client_ca_dir = ssl_client_ca_file = So I set: ssl_client_ca_file = </etc/ssl/certs/ca-certificates.crt But I'm still getting the error above. I addition, dovecot is crashing with SIGSEGV: Mar 20 13:28:23 mproxy dovecot: auth: Error: imapc(email.charite.de:993): Couldn't initialize SSL context: Can't verify remote server certs without trusted CAs (ssl_client_ca_* settings) Mar 20 13:28:23 mproxy dovecot: auth: Error: imapc(email.charite.de:993): No SSL context Mar 20 13:28:23 mproxy dovecot: auth: Error: imap(la***sch,87.77.180.61): Disconnected from server Mar 20 13:28:23 mproxy postfix/submission/smtpd[32682]: warning: zb43d.pia.fu-berlin.de[87.77.180.61]: SASL PLAIN authentication failed: Connection lost to authentication server Mar 20 13:28:23 mproxy dovecot: auth: Fatal: master: service(auth): child 32685 killed with signal 11 (core dumped) -- 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

2 5

doveadm proxy password
by Angel L. Mateo 20 Mar '17

20 Mar '17

Hi, I'm configuring a proxy host to connect to backend servers. As proxy is done based on an LDAP attribute of the user, I'm not using director. In the proxy server I have configured: doveadm_port = 24245 doveadm_password = secret And in the backend: service doveadm { inet_listener { port = 24245 } } local <mynetwork> { doveadm_password = secret } But when I run a doveadm command in the proxy I get: amateo_adm@musio10:/etc/dovecot/conf.d$ sudo doveadm quota get -u amateo(a)um.es doveadm(amateo(a)um.es): Error: doveadm authentication failed () doveadm(amateo(a)um.es): Error: myotis50.um.es:24245: Command quota get failed for amateo(a)um.es: EOF Quota name Type Value Limit % And in the backed I get: Mar 20 15:52:01 myotis50 dovecot: doveadm: Error: doveadm client authenticated with wrong password I have checked with tcpdump and in the command is sending the base64 encoding of "doveadmsecret" Any help? -- Angel L. Mateo Martínez Sección de Telemática Área de Tecnologías de la Información y las Comunicaciones Aplicadas (ATICA) http://www.um.es/atica Tfo: 868889150 Fax: 868888337

1 0

Re: Dovecot 2.2.27 proxy - enforcing per client IP connection limits
by Joseph Tam 20 Mar '17

20 Mar '17

Adi Pircalabu writes: > For us it is, we're periodically getting hammered by iOS devices that > try to open 300+ simultaneous IMAP connections for a single user from > the same IP, while the average hovers usually below 50 for the busier > mailboxes with many folders. Oh yeah, I've seen this. I think this happens when someone does a global pattern search, which causes the client to launch IMAP SEARCH commands on each and every mailbox. I've wondered whether installing Solr would alleviate this: it wouldn't directly address the connection limit problem, but perhaps it can return results fast enough to keep the concurrent connections count down. Can anyone with Solr installed confirm/refute this: does installing Solr keep iOS clients from roofing the connection count? Joseph Tam <jtam.home(a)gmail.com>

2 1

Mail restore and single storage attachement
by Jean-Luc Oms 20 Mar '17

20 Mar '17

Bonjour, I'm finishing the upgrade of an old installation of Dovecot/postfix mail system for my lab. In the configuration i plan ( dovecot 2.2.27 ), i choose to use: - mdbox format - single storage for attachements - 2 zfs file systems, one for mdboxes, the other for attachments The last tests before production concern my hability to restore a lost mail (or mailbox) ... (lot of changes when you are used to mbox format). 1) I uses doveadm import to restore part of mail from one of the zfs snapshot with a cde like: doveadm -Dv import -U bof2 -s -u bof2 mdbox:/mailpool/lirmm/.zfs/snapshot/zfs-auto-snap_frequent-2017-03-15-1645/vmail/bof2/mdbox Recup-AAAA mailbox AAAA I get this error: doveadm(bof2): Error: open() failed with file /mailpool/lirmm/.zfs/snapshot/zfs-auto-snap_frequent-2017-03-15-1645/vmail/bof2/mdbox/mailboxes/AAAA/dbox-Mails/dovecot.index.log: Read-only file system Thats right, my snapshot is ro, but why the import has to write to the source ? I'm missing something ? 2) I don't find any way to specify a source for attachements with the import command, then I first restore all the atachements from one snapshot, then make import, then purge. Is there a way to use a source for attachement file tree, or a command to find the mssing files for the import command ? Thanks -- __________________________________________ Jean-Luc Oms STI-RéseauX - LIRMM - CNRS/UM2 161 rue Ada - BAT 4 - CC 477 34095 Montpellier cedex 5 Tel +33 4 67 41 85 93 Urg +33 6 32 01 04 17 __________________________________________

1 1

Deploying Diffie-Hellman for TLS
by Jerry 20 Mar '17

20 Mar '17

I have been reading up on TLS and Dovecot and came across this URL: https://www.weakdh.org/sysadmin.html which recommended these settings for Dovecot. I would like to know if they are correct? Some much documentation on the web is pure garbage. Dovecot These changes should be made in /etc/dovecot.conf Cipher Suites 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_prefer_server_ciphers = yes (Dovecot 2.2.6 or greater) DH parameters #regenerates every week ssl_dh_parameters_length = 2048 Contrary to what the site recommends, I would have thought that changes should be made in the "10-ssl.conf" file. I am running "Dovecot 2.2.28" on a FreeBSD-11 machine with OpenSSL 1.0.2k, if that makes any difference. Thanks -- Jerry

2 1

Server migration
by Gandalf Corvotempesta 20 Mar '17

20 Mar '17

Hi to all. It's time to migrate an old server to a newer platform Some questions: 1) what happens by changing the pop3/IMAP server on the client? Is the client (Outlook, Thunderbird,...) smart enough to not download every message again? I'm asking this because the easier way to migrate would be move all mailboxes to the new server and then change the hostname on the client 2) what if I add a dovecot proxy on the new server, proxing back all requests to the older one, if the mailbox is still not migrated? Would the whole pop3/IMAP transaction happen through the proxy or there is something an http redirect (or anything similiar to the SIP protocol) ? 3) I think the response to this is no: is dovecot able to log the hostname used for the connection? I have multiple domains pointing to the same IP. Something like the Host header in Http.

2 1

[Bug] Mailbox aliases still broken
by azurit＠pobox.sk 20 Mar '17

20 Mar '17

Hi, about an year ago i was reporting a bug in mailbox aliases, which remains unfixed and unasnwered (probably totally ignored, don't understand why). I thought it was because the bug is old and already fixed but yesterday i upgraded to Dovecot 2.2.24 and problem persists. Here is the original report, everything, except the Dovecot version, is still correct: http://dovecot.org/list/dovecot/2015-June/101176.html Will this be fixed? Thanks for info. azur

4 7

dovecot problem with ssl
by Nilton Jose Rizzo 19 Mar '17

19 Mar '17

Hi all, I already searched for this error on google and nothing I never install dovecot, this is a first time. This error, I know, is too newbie and stupid, but I checked more than twice. root@server:/usr/local/etc/dovecot # sievec /home3/virtual/default.sieve doveconf: Fatal: Error in configuration file /usr/local/etc/dovecot/conf.d/10-ssl.conf line 7: Unknown setting: ssl root@server:/usr/local/etc/dovecot # I'm running a FreeBSD 12-current and compile all from ports (mysql, dovecot2, portfix3.1, and all needs ports, but this error don't leave. I'm fowling this tutorial to install all, but when I'll run a sievec this stop with this error. I'm not new in FreeBSD, I'm have good experience in FreeBSD. --- /************************************************* **Nilton José Rizzo UFRRJ **http://www.rizzo.eng.br http://www.ufrrj.br **http://lattes.cnpq.br/0079460703536198 **************************************************/

4 11

replication issues between to nodes
by Remko Lodder 18 Mar '17

18 Mar '17

Hi, Some time ago I posted the below but never got a reponse that I could work with. So i am retrying now in the hope that there might be a better idea/suggestion on how to approach this. Situation; I have two nodes, which should replicate to eachother. My main machine receives most mail and the other one receives mostly system messages and should get replicated. (This used to be delivered on both machines, but given the issues below I had to make sure that the customer email at least arrives on machine A, as detailed below). When a mail arrives on main machine (A) everything is fine and things are synchronised asap. Customers can see the email directly via webmail/imap. When a mail arrives on the secondary machine (B) the replication is not issued until machine A starts a sync session. Customers do not see the email on machine A via webmail/imap. When a mail arrives on A, the synchronisation occurs, and all messages on B, not yet on A, are synchronised as well. Customers can now see the email on machine A as well via webmail/imap. Sadly this can mean that emails that became visible are hours late (read: were delivered hours before, but not visible for the customer). Both machines are configured through puppet, only individual settings like IP addresses and certificates are different because well, they have to. I included the difference below, and both ‘doveconf -n’s. If someone has a suggestion on seeing why machine B is not issueing (or does not seem to issue) replication, let me know. I verified that I can connect to the remote machines via IPv4 and IPv6 (for doveadm / replication purposes). Difference between configurations; --- tmp1.txt 2017-03-18 15:18:41.000000000 +0100 +++ tmp2.txt 2017-03-18 15:18:56.000000000 +0100 @@ -55,7 +55,7 @@ imapsieve_mailbox2_name = * mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename mail_log_fields = uid box msgid size - mail_replica = tcps:mail.jr-hosting.nl:12346 + mail_replica = tcps:mail2.jr-hosting.nl:12346 sieve = ~/.dovecot.sieve sieve_dir = ~/sieve sieve_execute_bin_dir = /usr/local/lib/dovecot/sieve @@ -105,7 +105,7 @@ } service lmtp { inet_listener lmtp { - address = XXX/X 127.0.0.1 ::1 + address = YYYY/Y 127.0.0.1 ::1 port = 24 } unix_listener /var/spool/postfix/private/dovecot-lmtp { @@ -123,8 +123,8 @@ mode = 0666 } } -ssl_ca = </usr/local/etc/letsencrypt/live/mail2.jr-hosting.nl/fullchain.pem -ssl_cert = </usr/local/etc/letsencrypt/live/mail2.jr-hosting.nl/cert.pem +ssl_ca = </usr/local/etc/letsencrypt/live/mail.jr-hosting.nl/fullchain.pem +ssl_cert = </usr/local/etc/letsencrypt/live/mail.jr-hosting.nl/cert.pem ssl_client_ca_file = /usr/local/certificates/letsencrypt-ca.pem ssl_key = # hidden, use -P to show it ssl_protocols = !SSLv2 !SSLv3 Machine A (the best working machine) # 2.2.28 (bed8434): /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 0.4.17 (e179378) # OS: FreeBSD 11.0-RELEASE-p8 amd64 auth_mechanisms = plain login disable_plaintext_auth = no doveadm_password = # hidden, use -P to show it haproxy_trusted_networks = XXXX/X lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes lmtp_save_to_detail_mailbox = yes mail_debug = yes mail_fsync = always mail_location = mdbox:~/mdbox mail_plugins = " quota notify replication" managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date index ihave duplicate mime foreverypart extracttext imapsieve namespace { inbox = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Spam { auto = subscribe special_use = \Junk } mailbox Trash { auto = subscribe special_use = \Trash } prefix = separator = . } passdb { driver = pam } plugin { imapsieve_mailbox1_before = file:/usr/local/lib/dovecot/sieve/report-spam.sieve imapsieve_mailbox1_causes = COPY imapsieve_mailbox1_name = Spam imapsieve_mailbox2_before = file:/usr/local/lib/dovecot/sieve/report-ham.sieve imapsieve_mailbox2_causes = COPY imapsieve_mailbox2_from = Spam imapsieve_mailbox2_name = * mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename mail_log_fields = uid box msgid size mail_replica = tcps:mail2.jr-hosting.nl:12346 sieve = ~/.dovecot.sieve sieve_dir = ~/sieve sieve_execute_bin_dir = /usr/local/lib/dovecot/sieve sieve_global_dir = /usr/local/etc/dovecot/sieve/global/ sieve_global_extensions = +vnd.dovecot.pipe +vnd.dovecot.execute sieve_global_path = /usr/local/etc/dovecot/sieve/default.sieve sieve_pipe_bin_dir = /usr/local/lib/dovecot/sieve sieve_plugins = sieve_imapsieve sieve_extprograms } postmaster_address = postmaster(a)jr-hosting.nl protocols = imap pop3 lmtp sieve replication_dsync_parameters = -d -N -l 60 -U replication_max_conns = 100 service aggregator { fifo_listener replication-notify-fifo { mode = 0666 } unix_listener replication-notify { mode = 0666 } } service auth { unix_listener /var/spool/postfix/private/auth { mode = 0666 } } service doveadm { inet_listener { port = 12346 ssl = yes } } service imap-login { inet_listener imap_haproxy { haproxy = yes port = 10143 } inet_listener imaps_haproxy { haproxy = yes port = 10144 ssl = yes } service_count = 1 } service imap { process_limit = 1024 } service lmtp { inet_listener lmtp { address = XXXX/X 127.0.0.1 ::1 port = 24 } unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } service pop3 { process_limit = 1024 } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { mode = 0666 } } ssl_ca = </usr/local/etc/letsencrypt/live/mail.jr-hosting.nl/fullchain.pem ssl_cert = </usr/local/etc/letsencrypt/live/mail.jr-hosting.nl/cert.pem ssl_client_ca_file = /usr/local/certificates/letsencrypt-ca.pem ssl_key = # hidden, use -P to show it ssl_protocols = !SSLv2 !SSLv3 userdb { driver = passwd } verbose_proctitle = yes protocol lmtp { auth_username_format = %n mail_plugins = quota sieve postmaster_address = postmaster(a)jr-hosting.nl } protocol lda { mail_plugins = " quota notify replication sieve" } protocol imap { mail_max_userip_connections = 50 mail_plugins = " quota notify replication imap_quota imap_sieve” } Machine B: # 2.2.28 (bed8434): /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 0.4.17 (e179378) # OS: FreeBSD 11.0-RELEASE-p8 amd64 auth_mechanisms = plain login disable_plaintext_auth = no doveadm_password = # hidden, use -P to show it haproxy_trusted_networks = XXX/X lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes lmtp_save_to_detail_mailbox = yes mail_debug = yes mail_fsync = always mail_location = mdbox:~/mdbox mail_plugins = " quota notify replication" managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date index ihave duplicate mime foreverypart extracttext imapsieve namespace { inbox = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Spam { auto = subscribe special_use = \Junk } mailbox Trash { auto = subscribe special_use = \Trash } prefix = separator = . } passdb { driver = pam } plugin { imapsieve_mailbox1_before = file:/usr/local/lib/dovecot/sieve/report-spam.sieve imapsieve_mailbox1_causes = COPY imapsieve_mailbox1_name = Spam imapsieve_mailbox2_before = file:/usr/local/lib/dovecot/sieve/report-ham.sieve imapsieve_mailbox2_causes = COPY imapsieve_mailbox2_from = Spam imapsieve_mailbox2_name = * mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename mail_log_fields = uid box msgid size mail_replica = tcps:mail.jr-hosting.nl:12346 sieve = ~/.dovecot.sieve sieve_dir = ~/sieve sieve_execute_bin_dir = /usr/local/lib/dovecot/sieve sieve_global_dir = /usr/local/etc/dovecot/sieve/global/ sieve_global_extensions = +vnd.dovecot.pipe +vnd.dovecot.execute sieve_global_path = /usr/local/etc/dovecot/sieve/default.sieve sieve_pipe_bin_dir = /usr/local/lib/dovecot/sieve sieve_plugins = sieve_imapsieve sieve_extprograms } postmaster_address = postmaster(a)jr-hosting.nl protocols = imap pop3 lmtp sieve replication_dsync_parameters = -d -N -l 60 -U replication_max_conns = 100 service aggregator { fifo_listener replication-notify-fifo { mode = 0666 } unix_listener replication-notify { mode = 0666 } } service auth { unix_listener /var/spool/postfix/private/auth { mode = 0666 } } service doveadm { inet_listener { port = 12346 ssl = yes } } service imap-login { inet_listener imap_haproxy { haproxy = yes port = 10143 } inet_listener imaps_haproxy { haproxy = yes port = 10144 ssl = yes } service_count = 1 } service imap { process_limit = 1024 } service lmtp { inet_listener lmtp { address = XXXX/X 127.0.0.1 ::1 port = 24 } unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } service pop3 { process_limit = 1024 } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { mode = 0666 } } ssl_ca = </usr/local/etc/letsencrypt/live/mail2.jr-hosting.nl/fullchain.pem ssl_cert = </usr/local/etc/letsencrypt/live/mail2.jr-hosting.nl/cert.pem ssl_client_ca_file = /usr/local/certificates/letsencrypt-ca.pem ssl_key = # hidden, use -P to show it ssl_protocols = !SSLv2 !SSLv3 userdb { driver = passwd } verbose_proctitle = yes protocol lmtp { auth_username_format = %n mail_plugins = quota sieve postmaster_address = postmaster(a)jr-hosting.nl } protocol lda { mail_plugins = " quota notify replication sieve" } protocol imap { mail_max_userip_connections = 50 mail_plugins = " quota notify replication imap_quota imap_sieve” }

1 0

sievec
by Robert Moskowitz 17 Mar '17

17 Mar '17

I am building a new mailserver on Centos7. My sieve is created with: mkdir /home/sieve cat <<EOF>/home/sieve/globalfilter.sieve || exit 1 require "fileinto"; if exists "X-Spam-Flag" { if header :contains "X-Spam-Flag" "NO" { } else { fileinto "Spam"; stop; } } if header :contains "subject" ["***SPAM***"] { fileinto "Spam"; stop; } EOF chown -R vmail:mail /home/sieve But in 90-sieve.conf there is the comment: # A path to a global sieve script file, which gets executed ONLY # if user's private Sieve script doesn't exist. Be sure to # pre-compile this script manually using the sievec command line # tool. #sieve_global_path = /var/lib/dovecot/sieve/default.sieve Do I run sievec on this script? And I found the following comment on a blog, about 3 years old: 2: Having a user-defined sieve script will cancel out the global script for redirecting spam. In the dovecot.conf, get rid of the sieve_global_path and sieve_global_dir, and instead use: sieve_before = /path/to/global.sieve -- what this will do is make sure that the global script runs before any user scripts, which allows the spam redirecting to actually work. What is current situation on this? thank you

4 8

Do I need to configure director?
by Angel L. Mateo 17 Mar '17

17 Mar '17

Hi, I'm configuring a farm of dovecot proxies redirecting users to backend servers. The decision of which backend server is used for a user is based in its ldap account information. In my previous configuration I was using an inherited director configuration in these proxy servers, but now I was wondering that because the decision is made according to user information, I don't need to run director. Do it? Is there any advantage of running director in this scenario? -- Angel L. Mateo Martínez Sección de Telemática Área de Tecnologías de la Información y las Comunicaciones Aplicadas (ATICA) http://www.um.es/atica Tfo: 868889150 Fax: 868888337

2 2

Replication Troubles
by Wolfgang Hennerbichler 16 Mar '17

16 Mar '17

Hi Dovecot Users, I’ve configured dovecot dsync replication and I see troubles in the logs and get user complaints which I can’t explain. I found similar threads on this mailinglist, but I couldn’t find a solution anywhere. Does anybody have dsync running without problems on a high volume mailserver? I see the following logs, examples given: Feb 17 18:16:49 dovecot dovecot: imap(zoechi): Warning: /var/mail/zoechi/dovecot-uidlist: Duplicate file entry at line 10395: 1487350019.M138380P28563.dovecot.wogri.at,S=18930,W=19377 (uid 41092 -> 41093) - retrying by re-reading from beginning with this one I’m not sure - it might be that this is completely OK because due to replication UIDs clash. Maybe that’s OK, but I couldn’t find a confirmation. Feb 17 18:16:49 dovecot dovecot: imap(zoechi): Warning: Maildir /var/mail/zoechi: Expunged message reappeared, giving a new UID (old uid=41092, file=1487350019.M138380P28563.dovecot.wogri.at,S=18930,W=19377) This one is definitely a problem, deleted messages re-appear in the mailbox. I made sure that the 2 hosts doing replication have different hostnames. I run 2.2.27 (from debian-jessie backports). Config below. Thanks for hints (or pointers to other example configs where dsync works without problems) # dovecot -n # 2.2.27 (c0f36b0): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.16 (fed8554) # OS: Linux 4.8.14 x86_64 Debian 8.7 ext4 auth_verbose = yes debug_log_path = /var/log/dovecot.debug doveadm_password = # hidden, use -P to show it first_valid_gid = 106 first_valid_uid = 104 hostname = localhost last_valid_gid = 106 last_valid_uid = 104 mail_gid = dovecot mail_location = maildir:/var/mail/%n mail_plugins = quota fts fts_lucene virtual notify replication mail_temp_dir = /var/lib/dovecot/tmp mail_uid = dovecot 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 editheader namespace { list = children location = virtual:/var/mail/%n/virtual prefix = virtual. separator = . } namespace inbox { inbox = yes list = yes location = mailbox "Deleted Messages" { auto = subscribe special_use = \Trash } mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { auto = no special_use = \Sent } mailbox Spam { auto = subscribe special_use = \Junk } mailbox Trash { special_use = \Trash } prefix = separator = . subscriptions = yes type = private } passdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } plugin { default_language = de fts = lucene fts_lucene = whitespace_chars=@. mail_replica = tcp:172.16.1.1:12345 quota = maildir:User quota quota_rule = *:storage=5G quota_rule2 = Trash:storage=+200M quota_rule3 = Spam:ignore quota_warning = storage=95%% quota-warning 95 %u quota_warning2 = storage=80%% quota-warning 80 %u sieve = /etc/sieve/%n.sieve sieve_default = /etc/sieve/default.sieve sieve_dir = ~/sieve sieve_extensions = +editheader } pop3_deleted_flag = $POP3Deleted postmaster_address = postmaster(a)wogri.at protocols = " imap lmtp sieve pop3" service aggregator { fifo_listener replication-notify-fifo { user = dovecot } unix_listener replication-notify { user = dovecot } } service doveadm { inet_listener { port = 12345 } } service imap { process_limit = 1024 } service lmtp { inet_listener lmtp { port = 2003 } unix_listener lmtp { user = dovecot } user = dovecot } service managesieve-login { inet_listener sieve { port = 4190 } service_count = 1 } service pop3 { process_limit = 1024 } service quota-warning { executable = script /usr/local/sbin/quota-warning.sh unix_listener quota-warning { user = dovecot } user = dovecot } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { mode = 0600 } } ssl = required ssl_cert = </etc/dovecot/server.cert.pem ssl_key = # hidden, use -P to show it userdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } protocol lmtp { mail_plugins = quota sieve virtual notify replication } protocol lda { mail_plugins = quota fts fts_lucene virtual notify replication sieve } protocol imap { mail_max_userip_connections = 50 mail_plugins = quota fts fts_lucene virtual notify replication imap_quota } protocol pop3 { mail_plugins = quota fts fts_lucene virtual notify replication } local 2a00:XXX::/64 { doveadm_password = # hidden, use -P to show it }

3 4

Timeout Leak
by Luciano Mannucci 16 Mar '17

16 Mar '17

Hello all, I've got 3 occurences of this message in my log file: auth: Warning: Timeout leak: 0x805e480 (auth-request-handler.c:550) Can I ignore it, or is it a syhmptom of something wrong? I'm running dovecot 2.2.28 (bed8434). I'll post my doveconf -n if it is worth investigating further... Cheers, Luciano. -- /"\ /Via A. Salaino, 7 - 20144 Milano (Italy) \ / ASCII RIBBON CAMPAIGN / PHONE : +39 2 485781 FAX: +39 2 48578250 X AGAINST HTML MAIL / E-MAIL: posthamster(a)sublink.sublink.ORG / \ AND POSTINGS / WWW: http://www.lesassaie.IT/

2 2

'doveadm who' behind nginx mail proxy
by Edgaras Lukoševičius 16 Mar '17

16 Mar '17

Hello, we have configured nginx to work as mail proxy for backend dovecot servers. Dovecot servers behind nginx proxy are showing internal nginx ip address for every client when running 'doveadm who' instead of showing real client IP addresses. Is is possible to configure this setup to show real client IP addresses when running 'doveadm who' on internal dovecot servers or to configure nginx to show which user-ip pairs are proxied to which servers?

1 0

LDAP locking problems - home related
by Ganael Laplanche 16 Mar '17

16 Mar '17

Hi list, # dovecot --version 2.2.13 We use Dovecot LDA and I've discovered lots of messages stating that lock files cannot be written: Mar 16 12:02:03 mailhost dovecot: lda(someuser): Error: file_dotlock_open(/home/sg/someuser/.dovecot.lda-dupes) failed: No such file or directory That user's home directory is fetched from LDAP and does not exist locally on our 'mailhost' machine, so those error messages do make sense; I would like to fix that situation. In our current Dovecot configuration, only mail_location is set: mail_location = maildir:/var/mail/%u I would like to ignore the erroneous 'home' attribute fetched from LDAP and specify a common mail_home, i.e. set: mail_home = /var/mail/%u/home but if I understand correctly, that global mail_home configuration directive would still be overridden by the LDAP 'home' attribute fetched from passdb: [...] pass_attrs = supannAliasLogin=user,userPassword=password,\ homeDirectory=userdb_home,uidNumber=userdb_uid,gidNumber=userdb_gid [...] Can I just remove homeDirectory from pass_attrs to skip fetching 'home' from LDAP and then set the global mail_home ? Also, if that works: We would switch from a situation where a home is set (but wrong) to one where it becomes valid. Can there be any side-effect in that case (apart from fixing locking problems) ? Finally, will mail_home (leaf) directory be created if it does not exist yet (parent directory exists) ? Best regards, -- Ganael Laplanche <ganael.laplanche(a)centralesupelec.fr> Unix Systems Engineer @CentraleSupelec Rennes

1 1

Dovecot 2.2.27 proxy - enforcing per client IP connection limits
by Adi Pircalabu 16 Mar '17

16 Mar '17

Hi, Trying to keep abusive/buggy IMAP clients at bay on a number of Dovecot proxy servers, I've reconfigured them to use "mail_max_userip_connections = 50" in the "protocol imap" section, followed by restarting Dovecot. Yet, I'm still seeing 160+ established connections from a single IP address for the same email account. Am I missing anything? # 2.2.27 (c0f36b0): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.16 (fed8554) # OS: Linux 2.6.32-642.4.2.el6.x86_64 x86_64 CentOS release 6.8 (Final) auth_cache_negative_ttl = 5 mins auth_cache_size = 16 M auth_cache_ttl = 18 hours default_client_limit = 6120 default_process_limit = 500 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 imapflags notify mbox_write_locks = fcntl namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { sieve = file:~/sieve;active=~/.dovecot.sieve sieve_extensions = +notify +imapflags } protocols = imap pop3 lmtp sieve service auth { client_limit = 6120 } service imap-login { process_limit = 2048 process_min_avail = 20 service_count = 0 vsz_limit = 256 M } service imap { process_limit = 2048 } service managesieve-login { inet_listener sieve { port = 4190 } service_count = 0 vsz_limit = 128 M } service managesieve { process_limit = 1024 } service pop3 { process_limit = 1024 } [...] protocol imap { imap_capability = IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE mail_max_userip_connections = 50 } -- Adi Pircalabu

3 6

Postfix Ignoring lmtp, delivering straight to maildir
by Doug Barton 16 Mar '17

16 Mar '17

First I'd like to thank all the developers and contributors to dovecot. I've been using it for many years, and deeply appreciate your fine work. :) dovecot --version 2.2.22 (fe789d2) I have a working installation with postfix and dovecot, and I want to add sieve to it, so I am trying to configure postfix to use lmtp instead of 'virtual' for its delivery service. However it is ignoring that request, and for every message I get "status=sent (delivered to maildir)" and it shows up in my Inbox. On my mail host I have 1 normal user, let's say the username is 'myuser'. I have postfix configured to accept mail for several different domains, and each domain has a lot of different mail usernames (I use this for mailing lists and such). I use the virtual_maps feature of postfix, and have a map file that looks like this: abuse(a)dougbarton.us myuser hostmaster(a)dougbarton.us myuser dougb(a)dougbarton.us myuser ... All of this works great, and mail for all the different usernames and domains gets delivered into my one real user's Maildir, and I can see the mail with my IMAP clients. I've configured sieve in dovecot, and I can see the socket for lmtp in /var/spool/postfix/private/. I can also see the managesieve port in netstat, and I can use a sieve client to connect to it and edit scripts, etc. So according to all the tutorials I've read my next step is this in postfix' main.cf: virtual_transport = lmtp:unix:private/dovecot-lmtp which I did, and postfix restarts with no errors. But, it seems to avoid lmtp altogether, and as I mentioned above it delivers straight to my Maildir Inbox every time. I do have a sieve file, and the ~/dovecot.sieve symlink exists. I created a very simple filter: require ["fileinto", "imap4flags"]; if header :contains "Subject" "test" { fileinto "Junk"; } which my sieve client says is correct syntax. Still no joy. :-/ Any thoughts or suggestions are welcome. (And sorry this is so long, but based on my extensive searches it seems my configuration is a bit unique, so I explained it in some length.) Doug

3 5

Backing Up and Restoring mailboxes
by Jerry 15 Mar '17

15 Mar '17

I am going to be wiping clean my system and doing a complete upgrade. I have dovecot installed. I want to back up the mail system, and then be able to restore it. I thought that I could do this. doveadm -Dv backup -u user(a)example.com maildir:~/DoveBU Then I was going to gunzip that directory and put it onto a USB Drive. Now, after updating the system, I thought that I could just unzip the file from the USB drive. My question is, what command do I run to return the files to the same place they were originally. Assuming the structure was: "/var/mail/vmail/", what would I do? Thanks -- Jerry

1 0

FW: Unable to create needed folders
by Ken Zachreson 15 Mar '17

15 Mar '17

Never mind, I am stupid and did not read all available information. Needed to change permissions on /var/mail/* Thank You, Ken Z -----Original Message----- From: Ken Zachreson Sent: Wednesday, March 15, 2017 10:28 AM To: 'dovecot(a)dovecot.org' <dovecot(a)dovecot.org> Subject: Unable to create needed folders Greetings, The log reports that a process cannot create the needed folders. Please review and tell me what I have done wrong. dovecot 2.0.9 # 2.0.9: /etc/dovecot/dovecot.conf doveconf: Warning: NOTE: You can get a new clean config file with: doveconf -n > dovecot-new.conf doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:85: protocol { ssl_listen } has been replaced by service { inet_listener { address } } # OS: Linux 2.6.32-642.15.1.el6.x86_64 x86_64 CentOS release 6.8 (Final) auth_mechanisms = plain login last_valid_gid = 520 last_valid_uid = 520 mail_location = mbox:~/mail/:INBOX=/var/mail/%u mbox_write_locks = fcntl passdb { args = dovecot driver = pam } protocols = imap service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } } service imap-login { inet_listener imaps { address = * } } service pop3-login { inet_listener pop3s { address = * } } ssl_ca = /etc/pki/tls/certs/gd_bundle-g2-g1.crt ssl_cert = </etc/pki/tls/certs/c1e209e3ca2e1e5.crt ssl_key = </etc/pki/tls/private/gcrcnet.key userdb { driver = passwd } protocol pop3 { pop3_uidl_format = %08Xv%08Xu } ERROR Message from log Mar 15 10:14:03 MultiTronic6 dovecot: imap-login: Login: user=<wifi.adm>, method=LOGIN, rip=xx.xx.xx.xx, lip=yy.yy.yy.yy, mpid=5973, TLS Mar 15 10:14:03 MultiTronic6 dovecot: imap(wifi.adm): Error: chown(/home/wifi.adm/mail/.imap/INBOX, -1, 12(mail)) failed: Operation not permitted (egid=504(wifi.adm), group based on /var/mail/wifi.adm) Mar 15 10:14:03 MultiTronic6 dovecot: imap(wifi.adm): Error: mkdir(/home/wifi.adm/mail/.imap/INBOX) failed: Operation not permitted Mar 15 10:14:03 MultiTronic6 dovecot: imap(wifi.adm): Connection closed bytes=39/423 Thank You, Ken Zachreson IT Manager, Grand Canyon Resort Corp 928-769-2629 928-769-2638 Help Desk

1 0

Unable to create needed folders
by Ken Zachreson 15 Mar '17

15 Mar '17

Greetings, The log reports that a process cannot create the needed folders. Please review and tell me what I have done wrong. dovecot 2.0.9 # 2.0.9: /etc/dovecot/dovecot.conf doveconf: Warning: NOTE: You can get a new clean config file with: doveconf -n > dovecot-new.conf doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:85: protocol { ssl_listen } has been replaced by service { inet_listener { address } } # OS: Linux 2.6.32-642.15.1.el6.x86_64 x86_64 CentOS release 6.8 (Final) auth_mechanisms = plain login last_valid_gid = 520 last_valid_uid = 520 mail_location = mbox:~/mail/:INBOX=/var/mail/%u mbox_write_locks = fcntl passdb { args = dovecot driver = pam } protocols = imap service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } } service imap-login { inet_listener imaps { address = * } } service pop3-login { inet_listener pop3s { address = * } } ssl_ca = /etc/pki/tls/certs/gd_bundle-g2-g1.crt ssl_cert = </etc/pki/tls/certs/c1e209e3ca2e1e5.crt ssl_key = </etc/pki/tls/private/gcrcnet.key userdb { driver = passwd } protocol pop3 { pop3_uidl_format = %08Xv%08Xu } ERROR Message from log Mar 15 10:14:03 MultiTronic6 dovecot: imap-login: Login: user=<wifi.adm>, method=LOGIN, rip=xx.xx.xx.xx, lip=yy.yy.yy.yy, mpid=5973, TLS Mar 15 10:14:03 MultiTronic6 dovecot: imap(wifi.adm): Error: chown(/home/wifi.adm/mail/.imap/INBOX, -1, 12(mail)) failed: Operation not permitted (egid=504(wifi.adm), group based on /var/mail/wifi.adm) Mar 15 10:14:03 MultiTronic6 dovecot: imap(wifi.adm): Error: mkdir(/home/wifi.adm/mail/.imap/INBOX) failed: Operation not permitted Mar 15 10:14:03 MultiTronic6 dovecot: imap(wifi.adm): Connection closed bytes=39/423 Thank You, Ken Zachreson IT Manager, Grand Canyon Resort Corp 928-769-2629 928-769-2638 Help Desk

1 0

autocreate ONLY for new Users
by plataleas 15 Mar '17

15 Mar '17

Hi All We are currently migrating accounts to Dovecot. The existing accounts do have special folders with different names. (i.e. sent, sent-mail) The autocreate-function of "special folders" is useful. However we need this feature ONLY for new users. The existing accounts have a mapping for their own "special folders". There are discussions about this topic on the mailing list: /http://www.dovecot.org/list/dovecot/2014-August/097313.html https://dovecot.org/list/dovecot/2016-May/104296.html/ Did someone manage to implement this ? Are there workarounds? Thanks and regards plataleas

3 6

Custom cache_key for passdb-sql
by Tom Sommer 15 Mar '17

15 Mar '17

The cache_key for the SQL-passdb should be created automatically, but for some reason the service (%s) is not part of the key, and I need it to be I've tried to set a manual cache_key, but that fails: Mar 15 11:54:02 auth: Fatal: sql /etc/dovecot/dovecot-sql.conf cache_key=%s%u%{real_ip}: Can't open configuration file /etc/dovecot/dovecot-sql.conf cache_key=%s%u%{real_ip}: No such file or directory passdb { args = /etc/dovecot/dovecot-sql.conf cache_key=%s%u%{real_ip} driver = sql } Is this not possible? -- Tom

1 0

welcome plugin
by David Mehler 14 Mar '17

14 Mar '17

Hello, If anyone is using the welcome plugin in dovecot 2.2.x to sent a one-time new welcome email to new users can I get a look at your configuration? I'm stuck, I create a user and the welcome action does not execute. If you've got a script to send the mail can I get a look at that as well? Thanks. Dave.

3 2

Users with extra mailbox: namespace/mailbox in userdb lookup?
by MRob 14 Mar '17

14 Mar '17

Hello, We have a need for some users to have an additional folder created and subscribed for them. Is is possible to return an override for the default "namespace inbox" containing the needed mailbox definitions in the userdb lookup for such users? If so, how would the userdb lookup result be formatted? Presumably as just one long string, but how would the setting be named given there can't be a space in it? Can I replace the space with an underscore, e.g. userdb_namespace_inbox = '{ mailbox Drafts { auto=subscribe special_use = \Drafts } mailbox Trash { auto=subscribe special_use = \Trash } }' Or is there some other way to do this?

4 11

strange behaviour of dovecot
by Masaharu Kawada 14 Mar '17

14 Mar '17

Dear dovecot-list, Dovecot gives the below error messages and those errors go away after running 'systemctl restart dovecot'(Restarting dovecot service)', however, the same happens after a while later(like after 300 mails delivered). --- master : Error : service(anvil) : Initial Status notification no received in 30 seconds, killing the process master : Error : service(log) : Initial Status notification no received in 30 seconds, killing the process master : Error : service(ssl-params) : Initial Status notification no received in 30 seconds, killing the process master : Error : service(log) : child 3703 killed with signal 9 --- then the log process is not there so that no mail log gets captured in maillog: --- root 28036 0.0 0.0 19864 1604 ? Ss 11:45 0:00 /usr/sbin/dovecot -F dovecot 28074 0.0 0.0 9312 1000 ? S 11:46 0:00 dovecot/anvil root 28075 0.0 0.0 12324 2084 ? S 11:46 0:00 dovecot/config --- Does this have something to do with any limitation in dovecot configuration? If anyone in the list ever has similar or same experience, please give me a clue that shows where to look at from here. Thanks, -- Masaharu Kawada

2 2