- dovecot - dovecot.org

Trouble setting up dovecot/postfix/mysql with virtual mailboxes..
by Michael Segel 14 Apr '17

14 Apr '17

Hi, I’m building a new linux box to replace my current DNS/Mail server for my SOHO. I was going to set up postfix/dovecot/mysql so I can support virtual users. I also use Webmin to make admin easier. I ran in to a couple of snags. When I first got it set up, mail went to the virtmail user and I could use my Mac mail client to read the mail. Everything was working when testing it. I was working on my TLS certificates and I broke something. I don’t know what I did, but now it’s going to the local mailbox instead. (MailDir folder) Since most of my time is doing other things, I am hoping someone could point me in the right direction. Thx

2 3

Trouble compiling 2.2.29.1
by Marc Perkel 13 Apr '17

13 Apr '17

Not sure what I'm doing wrong but I run this: ./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --enable-maintainer-mode --with-mysql and it forks thousands of copies of config.guess and will eventually lock up the computer. What am I doing wrong?

1 0

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