- dovecot - dovecot.org

Dovecot - Postfix with HAproxy
by Michael JOIGNY 13 Oct '15

13 Oct '15

Hi Everyone, I wouldlike to set up a postfix-dovecot with HA using HAproxy but im facing issues. I've followed this documentation : http://wiki2.dovecot.org/HAProxy (pour dovecot) http://blog.haproxy.com/2012/06/30/efficient-smtp-relay-infrastructure-with… (pour postfix) Package's version : dovecot : 2:2.2.19 (>= 2.2.19 pour proxy protocol) haproxy : 1.5.14 postfix : 2.11.2-1 (>2.10 pour postscreen) A part of my configuration : ##HAPROXY #postfix listen smtp bind mail.xx.xx:465 balance roundrobin timeout client 1m timeout connect 5s no option http-server-close mode tcp option smtpchk option tcplog server tst tst.xxx:10465 send-proxy server tst2 tst2.xxx:10465 send-proxy server tst3 tst3.xxx:10465 send-proxy #dovecot listen imap bind mail.xxx.xx:993 timeout client 1m no option http-server-close balance leastconn stick store-request src stick-table type ip size 200k expire 30m mode tcp option tcplog server tst tst.xxx:10993 send-proxy-v2 server tst2tst2.xxx:10993 send-proxy-v2 server tst3 tst3.xxx:10993 send-proxy-v2 ##POSTFIX postix main.cf #Haproxy proxy protocol postscreen_upstream_proxy_protocol = haproxy postfix master.cf #haproxy 10465 inet n – n – 1 postscreen smtpd pass – – n – – smtpd S ##DOVECOT # 2.2.19 (719e7f8fd70b): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.9 # OS: Linux 2.6.32-41-pve x86_64 Debian 7.9 simfs auth_debug = yes auth_verbose = yes disable_plaintext_auth = no *haproxy_timeout = 5 secs** **haproxy_trusted_networks = x.x.x.x* log_timestamp = "%Y-%m-%d %H:%M:%S " mail_location = maildir:/mailbox/%d/%n mail_max_userip_connections = 0 mail_privileged_group = mail managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date index ihave duplicate passdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } plugin { sieve = ~/.dovecot.sieve sieve_dir = ~/sieve sieve_global_path = /mailbox/globalsieverc } protocols = sieve pop3 imap service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-master { mode = 0660 user = mailboxes } unix_listener auth-userdb { group = mail mode = 0666 user = dovecot } user = root } service imap-login { inet_listener imap { port = 0 } inet_listener imap_haproxy { haproxy = yes port = 10993 } inet_listener imaps { address = * port = 993 } process_limit = 450 } service pop3-login { inet_listener pop3 { address = * port = 110 } process_limit = 180 } ssl_cert = </etc/ssl/certs/dovecot.pem ssl_key = </etc/ssl/private/star.key userdb { args = uid=5000 gid=5000 home=/mailbox/%d/%n/ allow_all_users=yes driver = static } protocol imap { imap_client_workarounds = } protocol pop3 { pop3_uidl_format = %08Xu%08Xv } protocol sieve { mail_location = maildir:/mailbox } protocol lda { auth_socket_path = /var/run/dovecot/auth-master hostname = xxx.yyy.com log_path = /var/log/dovecot/deliver.log mail_plugin_dir = /usr/lib/dovecot/modules mail_plugins = sieve postmaster_address = postmaster(a)xxx.yyy rejection_reason = Your message to <%t> was automatically rejected:%n%r rejection_subject = Rejected: %s sendmail_path = /usr/sbin/sendmail } With my mail client : With an IMAP connection, logs below, i don't understand why my login is empty ... dovecot: imap-login: Disconnected: Too many invalid commands (no auth attempts in 0 secs): *user=<>*, rip=mon_ip_publique, lip=ip_publique_haproxy, session= xxx With a SMTP connection, logs below, i have a timeout. postfix/postscreen[16654]: CONNECT from [my public ip]:49942 to [my haproxy public ip]:465 postfix/postscreen[16654]: PREGREET 166 after 0 from [mon ip publique]:49942: \22\3\1\161\1\157\3\3+0E\b\213\131\177\173>\r/\213\177i\223k”FjA#\144\145\153\vP\\\155HL\190 If someone could help me, thanks. Kind regards. --

2 1

Dualstack IPv4/IPv6 setup with directors
by Heiko Schlittermann 13 Oct '15

13 Oct '15

Hi, still using 2.2.9, I've two directors, and these directors use both IPv4/IPv6 addresses. `host directors.<domain>` returns one A and AAA for each of the two directors: directors.<domain> has address 149.x.y.96 (director1) directors.<domain> has address 149.x.y.97 (director2) directors.<domain> has IPv6 address 2001:x:y:f33::5:1 (director1) directors.<domain> has IPv6 address 2001:x:y:f33::5:2 (director2) But connecting the the neighbor director gives: Oct 13 21:23:29 director1 dovecot: director: Warning: Director 2001:x:y:f33::5:2:9090/left disconnected us with reason: Invalid input: ME 149.x.y.96 9090 Oct 13 21:23:29 director1 dovecot: director: Error: director(149.x.y.97:9090/out): connect() failed: Connection refused Oct 13 21:23:29 director1 dovecot: director: Warning: net_connect_ip(): ip->family != my_ip->family Oct 13 21:23:29 director1 dovecot: director: Error: Remote director thinks it's someone else (connected to 2001:x:y:f33::5:1:9090, remote says it's 149.x.y.96:9090) I assume it's because the director uses only one (IPv4 OR IPv6) address for it's own identity, right? Best regards from Dresden/Germany Viele Grüße aus Dresden Heiko Schlittermann -- SCHLITTERMANN.de ---------------------------- internet & unix support - Heiko Schlittermann, Dipl.-Ing. (TU) - {fon,fax}: +49.351.802998{1,3} - gnupg encrypted messages are welcome --------------- key ID: F69376CE - ! key id 7CBF764A and 972EAC9F are revoked since 2015-01 ------------ -

2 2

Storage Design (Regligious War, Whatever)
by Kelsey Cummings 13 Oct '15

13 Oct '15

We've been running dovecot director setup using MAILDIR++ spools on NFS served by 4 (aging) Netapp clustered filers and are considering modernizing our storage. There's nothing particularly wrong with the existing storage except the age, density and power consumption don't compare well when against new systems. Refreshing the Netapps is an option but they come at a substantial cost. The last time we were looking one of the recommended hot DIY setups was Linux NFS backed by XFS on N mirrors but this predated the availability of stable ZFS in FreeBSD or Linux as well as products like FreeNAS. A FreeBSD NFS/ZFS filer on commodity hardware with zil/l2arc on a PCIe SSD seems like an attractive, affordable and easily scaled out solution which also would allow us to leverage compression at the filesystem layer. Does anyone have any experience running ZFS spool storage? If so, how do you handle DR/HA for spool storage? Thoughts on how this might compare to using DRBD? Any pitfalls to watch out for or general pointers? Suggestions on pool configuration? -K

1 0

Unknown cache fields?
by Larry Rosenman 13 Oct '15

13 Oct '15

I assume this is expected, but just checking. I do NOT use POP3. Oct 5 09:41:20 thebighonker dovecot: indexer-worker(mrm): Debug: Ignoring unknown cache field: pop3.order Oct 5 09:41:20 thebighonker dovecot: indexer-worker(mrm): Debug: Ignoring unknown cache field: binary.parts Oct 5 09:41:20 thebighonker dovecot: indexer-worker(mrm): Debug: Ignoring unknown cache field: body.snippet -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 (c) E-Mail: larryrtx(a)gmail.com US Mail: 7011 W Parmer Ln, Apt 1115, Austin, TX 78729-6961

2 1

doveadm index assertion failed
by Nick Rosier 13 Oct '15

13 Oct '15

Hi, one of my mailboxes returns following error when I run doveadm index on it: Panic: file charset-iconv.c: line 85 (charset_to_utf8_try): assertion failed: (srcleft <= CHARSET_MAX_PENDING_BUF_SIZE) OS: FreeBSD 10.2 Dovecot: 2.1.19 Tika: 1.10 SOLR: 5.3.1 Running doveadm -D index does not show any more information indicating what causes this error (mail/folder/...) How I can find what is causing this error? Rgds, N.

2 1

Re: bug report: dovecot-imapd core dump
by Tamas Papp 13 Oct '15

13 Oct '15

Hi, could not find it -- back to the list, maybe someone can suggest a fix/workaround. Best, Tamas On Wed, Oct 07 2015, Dominik Breu wrote: > Hello, > > yeah this one looks familiar to me can you search the list back in > september there was a somewhat similar bug with thunderbird imho timo > posted a notice about it. > > greetings, > > dominik > > Am Mittwoch, den 07.10.2015, 15:53 +0200 schrieb Tamas Papp: >> Hi Dominik, >> >> Thanks for the help, the backtrace is here (I did not sent it to the >> list since I am not sure if it contains password or message >> information, >> sorry but I am unfamiliar with these things). >> >> Core was generated by `dovecot/imap'. >> Program terminated with signal SIGSEGV, Segmentation fault. >> #0 0x00007f404e58e3b6 in mail_index_keywords_unref >> #(_keywords=_keywords@entry=0x7ffecb8adeb8) at mail-index.c:383 >> 383 mail-index.c: No such file or directory. >> (gdb) bt full >> #0 0x00007f404e58e3b6 in mail_index_keywords_unref >> #(_keywords=_keywords@entry=0x7ffecb8adeb8) at mail-index.c:383 >> keywords = 0x7f404e27066d <buffer_alloc+45> >> __FUNCTION__ = "mail_index_keywords_unref" >> #1 0x00007f404e559975 in mailbox_keywords_unref >> (keywords=keywords@entry=0x7ffecb8adeb8) at mailbox-keywords.c:94 >> No locals. >> #2 0x00007f404ea254ad in cmd_append_handle_args >> (nonsync_r=0x7ffecb8ade8f, >> #args=<optimized out>, cmd=0x7f4050bc3250) at cmd-append.c:602 >> ctx = 0x7f4050bc3348 >> flags_list = 0x7f4050bcc840 >> flags = 9 >> keywords_list = 0x7f4050bc33f0 >> internal_date_str = 0x7f4050bcca00 "17-Sep-2015 14:19:23 >> +0200" >> internal_date = -1 >> timezone_offset = 0 >> keywords = 0x0 >> ret = <optimized out> >> client = 0x7f4050bc2670 >> cat_list = 0x0 >> input = <optimized out> >> valid = <optimized out> >> #3 cmd_append_parse_new_msg (cmd=cmd@entry=0x7f4050bc3250) at >> cmd-append.c:770 >> client = <optimized out> >> ctx = 0x7f4050bc3348 >> args = 0x7f4050bcc488 >> msg = <optimized out> >> arg_min_count = <optimized out> >> fatal = 255 >> nonsync = true >> last_literal = <optimized out> >> ret = <optimized out> >> __FUNCTION__ = "cmd_append_parse_new_msg" >> #4 0x00007f404ea25a17 in cmd_append (cmd=0x7f4050bc3250) at >> cmd-append.c:932 >> client = 0x7f4050bc2670 >> ctx = 0x7f4050bc3348 >> mailbox = 0x7f4050bafb78 "Cemex" >> #5 0x00007f404ea30e4c in command_exec (cmd=cmd@entry=0x7f4050bc3250) >> at >> imap-commands.c:158 >> hook = 0x7f4050bad0d0 >> ret = <optimized out> >> #6 0x00007f404ea2fd62 in client_command_input (cmd=0x7f4050bc3250) >> at >> imap-client.c:780 >> client = 0x7f4050bc2670 >> command = <optimized out> >> __FUNCTION__ = "client_command_input" >> #7 0x00007f404ea2fe16 in client_command_input (cmd=0x7f4050bc3250) >> at >> imap-client.c:841 >> client = 0x7f4050bc2670 >> command = <optimized out> >> __FUNCTION__ = "client_command_input" >> #8 0x00007f404ea3014d in client_handle_next_command >> (remove_io_r=<synthetic >> pointer>, client=0x7f4050bc2670) at imap-client.c:879 >> ---Type <return> to continue, or q <return> to quit--- >> No locals. >> #9 client_handle_input (client=0x7f4050bc2670) at imap-client.c:891 >> _data_stack_cur_id = 3 >> remove_io = false >> handled_commands = false >> client = 0x7f4050bc2670 >> #10 0x00007f404ea304f5 in client_input (client=0x7f4050bc2670) at >> imap-client.c:933 >> cmd = 0xf013c >> output = 0x7f4050bc30a0 >> bytes = 135 >> __FUNCTION__ = "client_input" >> #11 0x00007f404e285247 in io_loop_call_io (io=0x7f4050bc3170) at >> ioloop.c:388 >> ioloop = 0x7f4050bac720 >> t_id = 2 >> #12 0x00007f404e286079 in io_loop_handler_run >> (ioloop=ioloop@entry=0x7f4050bac720) at ioloop-epoll.c:220 >> ctx = 0x7f4050bad3b0 >> io = <optimized out> >> tv = {tv_sec = 1799, tv_usec = 999282} >> events_count = <optimized out> >> msecs = <optimized out> >> ret = 1 >> i = 0 >> j = <optimized out> >> call = <optimized out> >> __FUNCTION__ = "io_loop_handler_run" >> #13 0x00007f404e284d88 in io_loop_run (ioloop=0x7f4050bac720) at >> ioloop.c:412 >> __FUNCTION__ = "io_loop_run" >> #14 0x00007f404e231de3 in master_service_run (service=0x7f4050bac5b0, >> callback=<optimized out>) at master-service.c:566 >> No locals. >> #15 0x00007f404ea2424e in main (argc=1, argv=0x7f4050bac390) at >> main.c:400 >> set_roots = {0x7f404ec489c0 <imap_setting_parser_info>, 0x0} >> login_set = {auth_socket_path = 0x7f4050ba4048 "\001", >> postlogin_socket_path = 0x0, postlogin_timeout_secs = 60, callback = >> 0x7f404ea39f40 <login_client_connected>, >> failure_callback = 0x7f404ea39c20 <login_client_failed>, >> request_auth_token = 1} >> service_flags = <optimized out> >> storage_service_flags = <optimized out> >> username = 0x0 >> c = <optimized out> >> (gdb) quit >> >> Best, >> >> Tamas >> >> On Wed, Oct 07 2015, Dominik Breu wrote: >> >> > Hello >> > >> > Tamas it would be a better backtace when you have installed the >> > dovecot >> > debug symboly mostly located under dovecote-dbg in apt. Further >> > debug >> > help can you find in the wiki. >> > >> > greetings >> > >> > dominik >> > >> > Am Mittwoch, den 07.10.2015, 15:09 +0200 schrieb Tamas Papp: >> > > Typical log message: >> > > >> > > Oct 7 11:39:36 hostname dovecot: imap(username): Fatal: master: >> > > service(imap): child 14864 killed with signal 11 (core dumped) >> > > >> > > What triggers the problem: >> > > >> > > User moving multiple messages to a subfolder via IMAP (from >> > > another >> > > account, on another server, client: Thunderbird). Moving single >> > > messages >> > > either does not trigger the problem, or with much lower >> > > probability >> > > (could not reproduce). >> > > >> > > Version: >> > > $ dpkg -l 'dovecot*' >> > > Desired=Unknown/Install/Remove/Purge/Hold >> > > > Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig >> > > > -aWait/Trig-pend >> > > > / Err?=(none)/Reinst-required (Status,Err: uppercase=bad) >> > > > > / Name Version >> > > > > Architecture Description >> > > +++-=====================================-======================= >> > > -======================= >> > > -================================================================ >> > > ==== >> > > ============ >> > > un dovecot-common <none> >> > > <none> (no description available) >> > > ii dovecot-core 1:2.2.9-1ubuntu5 >> > > amd64 secure POP3/IMAP server - core files >> > > un dovecot-gssapi <none> >> > > <none> (no description available) >> > > ii dovecot-imapd 1:2.2.9-1ubuntu5 >> > > amd64 secure POP3/IMAP server - IMAP daemon >> > > un dovecot-ldap <none> >> > > <none> (no description available) >> > > un dovecot-lmtpd <none> >> > > <none> (no description available) >> > > un dovecot-managesieved <none> >> > > <none> (no description available) >> > > un dovecot-mysql <none> >> > > <none> (no description available) >> > > un dovecot-pgsql <none> >> > > <none> (no description available) >> > > un dovecot-pop3d <none> >> > > <none> (no description available) >> > > un dovecot-sieve <none> >> > > <none> (no description available) >> > > un dovecot-solr <none> >> > > <none> (no description available) >> > > un dovecot-sqlite <none> >> > > <none> (no description available) >> > > tamas@szob:~$ lsb_release -a >> > > No LSB modules are available. >> > > Distributor ID: Ubuntu >> > > Description: Ubuntu 15.04 >> > > Release: 15.04 >> > > Codename: vivid >> > > >> > > Also tried 2.2.18 from Ubuntu wiley, same results. >> > > >> > > Backtrace (I am not sure this is useful, extraced core from >> > > Ubuntu's >> > > Apport): >> > > >> > > (gdb) bt full >> > > #0 0x00007f404e58e3b6 in mail_index_keywords_unref () from >> > > /usr/lib/dovecot/libdovecot-storage.so.0 >> > > No symbol table info available. >> > > #1 0x00007f404ea254ad in _start () >> > > No symbol table info available. >> > > >> > > Any help would be appreciated, I am happy to provide more info if >> > > necessary. >> > > >> > > Tamas

2 2

dovecot as proxy and verification of the backends certificate
by Heiko Schlittermann 13 Oct '15

13 Oct '15

Hello, I'm using a dovecot as proxy, connecting to one or more backends. The backends use X.509 certificates. The proxy's passdb returns extra fields: user=foo proxy host=backend1.<domain> ssl=yes nopassword=y Thus the proxy connects to the backend but can't verify the backends certificate. The following comment suggests using ssl_client_ca_file for that. # Directory and/or file for trusted SSL CA certificates. These are used only # when Dovecot needs to act as an SSL client (e.g. imapc backend). The # directory is usually /etc/ssl/certs in Debian-based systems and the file is # /etc/pki/tls/cert.pem in RedHat-based systems. #ssl_client_ca_dir = #ssl_client_ca_file = ssl_client_ca_file = /tmp/certs/ca-local.pem But that does not work! Instead I've to use ssl_ca # PEM encoded trusted certificate authority. Set this only if you intend to use # ssl_verify_client_cert=yes. The file should contain the CA certificate(s) # followed by the matching CRL(s). (e.g. ssl_ca = </etc/ssl/certs/ca.pem) # ssl_ca = ssl_ca = </tmp/certs/ca-local.pem Bug or feature? Mainly I'm asking because the comments do not indicate that I should have used ssl_ca for this type of operation (dovecot as a SSL client) Best regards from Dresden/Germany Viele Grüße aus Dresden Heiko Schlittermann -- SCHLITTERMANN.de ---------------------------- internet & unix support - Heiko Schlittermann, Dipl.-Ing. (TU) - {fon,fax}: +49.351.802998{1,3} - gnupg encrypted messages are welcome --------------- key ID: F69376CE - ! key id 7CBF764A and 972EAC9F are revoked since 2015-01 ------------ -

2 2

Dovecot auth-ldap ignores tls_* settings when using ldaps://
by Heiko Schlittermann 13 Oct '15

13 Oct '15

Hi, I'm using dovecot 2.2.9 (but after checking src/auth/db-ldap.c in 2.2.13 there seems to be the same bug/feature). The userdb and passdb use LDAP. All further configuration is done in auth-ldap.conf.ext. uri = ldaps://<host>/ # tls = tls_cert_file = /etc/ssl/certs/client-cert.pem tls_key_file = /etc/ssl/certs/client-key.file Dovecot ignores the tls_* options. If I use an ldap:// URI and switch on TLS using tls=yes it works as expected. But I do not see any reason why LDAPS should not read the tls_* settings. This small patch solved it for me --- dovecot-2.2.9/src/auth/db-ldap.c 2013-11-24 14:37:39.000000000 +0100 +++ dovecot-2.2.9.hs12/src/auth/db-ldap.c 2015-10-08 21:24:47.051446465 +0200 @@ -1043,7 +1043,7 @@ static void db_ldap_set_tls_options(struct ldap_connection *conn) { - if (!conn->set.tls) + if (!(conn->set.tls || strncmp(conn->set.uris, "ldaps:", 6) == 0)) return; #ifdef OPENLDAP_TLS_OPTIONS It would be great, if somebody can confirm this and if this or some equivalent patch could make it upstream. Best regards from Dresden/Germany Viele Grüße aus Dresden Heiko Schlittermann -- SCHLITTERMANN.de ---------------------------- internet & unix support - Heiko Schlittermann, Dipl.-Ing. (TU) - {fon,fax}: +49.351.802998{1,3} - gnupg encrypted messages are welcome --------------- key ID: F69376CE - ! key id 7CBF764A and 972EAC9F are revoked since 2015-01 ------------ -

2 2

Multiple core solr support
by Daniel Miller 13 Oct '15

13 Oct '15

Is it possible to use variables, such as domain or username, in the plugin url declaration? This would allow using multiple cores to separate the stored indexes. So when my own giant mailbox gets corrupt...I don't have to rebuild everybody's... Something like url=http://mysolr.server.com:8983/solr/%u -- Daniel

2 1

fts solr ignores new mailboxes until fts rescan
by Giorgio Paolucci 13 Oct '15

13 Oct '15

Hello, on my debian wheezy installation, I implemented fts plugin with solr as indexing system. I noticed that if a user creates a new folder, that folder it is ignored by dovecot indexing until a doveadm fts rescan is performed for that user. From that time on everything works ok on that folder. As a test I set fts_autoindex=yes and put in that folder a brand new mail never indexed before. in my logs indexer-worker says it indexed 0 messages Obviously this is a major issue as users often create new folders, but a search always returns empty results. My system is a debian wheezy with dovecot packages from backports dovecot 2.2.13-11~bpo70+1. Am I missing something? Any clue would be appreciated. Thank you all in advance. Bests Giorgio Paolucci ============================= doveconf -n # 2.2.13: /etc/dovecot/dovecot.conf # OS: Linux 3.2.0-4-amd64 x86_64 Debian 7.8 auth_default_realm = xxx disable_plaintext_auth = no log_path = /var/log/dovecot/dovecot.log mail_fsync = always mail_nfs_index = yes mail_nfs_storage = yes mail_plugins = quota listescape mail_log notify fts fts_solr 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 mdbox_rotate_interval = 1 days mdbox_rotate_size = 10 M mmap_disable = yes namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = separator = / } passdb { args = /etc/dovecot/conf.d/dovecot-sql.conf.ext driver = sql } passdb { args = /etc/dovecot/conf.d/dovecot-sqlSSO.conf.ext driver = sql } plugin { fts = solr fts_solr = url=http://%n.%1n.solr.csia:8983/solr/ mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename mail_log_fields = uid box msgid size pop3_migration_mailbox = INBOX quota = dict:User quota::file:/SYSTEM/USERS/homes/%d/%1u/%u/%u.quota quota_rule = *:storage=7000M quota_rule2 = Trash:storage=+100M quota_warning = storage=95%% quota-warning 95 %u quota_warning2 = storage=80%% quota-warning 80 %u sieve = /SYSTEM/USERS/mailbox/%d/%1n/%u/.dovecotactive.sieve sieve_default = /etc/dovecot/default.sieve sieve_dir = /SYSTEM/USERS/mailbox/%d/%1n/%u/sieve } pop3c_host = 147.162.10.68 protocols = imap pop3 lmtp sieve service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-userdb { group = vmail mode = 0600 user = vmail } } service imap-login { inet_listener imaps { ssl = no } process_min_avail = 20 service_count = 1 } service imap { executable = imap postlogin process_limit = 4096 } service lmtp { executable = lmtp inet_listener lmtp { port = 2223 } process_min_avail = 15 } service pop3-login { inet_listener pop3s { ssl = no } } service pop3 { process_limit = 256 } service postlogin { executable = script-login -d rawlog user = vmail } service quota-warning { executable = script /SYSTEM/DOVECOT/scripts/quota-warning.sh unix_listener quota-warning { user = vmail } user = vmail } ssl = no userdb { driver = prefetch } userdb { args = /etc/dovecot/conf.d/dovecot-sql.conf.ext driver = sql } userdb { driver = prefetch } userdb { args = /etc/dovecot/conf.d/dovecot-sqlSSO.conf.ext driver = sql } protocol lmtp { info_log_path = /tmp/dovecot-lmtp-info.log log_path = /tmp/dovecot-lmtp.log mail_plugins = quota listescape mail_log notify sieve } protocol lda { mail_plugins = quota listescape mail_log notify } protocol imap { imap_max_line_length = 128 k mail_max_userip_connections = 20 mail_plugins = quota listescape mail_log notify fts fts_solr imap_quota } protocol doveadm { mail_plugins = quota listescape mail_log notify fts fts_solr pop3_migration } protocol pop3 { pop3_no_flag_updates = yes pop3_uidl_format = %10v.%09u

2 3

Problems sync with mail client MAC and dovecot-2.2.10-4.el7_0.1.el7_0.1.x86_64
by grupo correo 13 Oct '15

13 Oct '15

Hello, i have installed Centos 7.1.1503 with Dovecot 2.2.10-4.el7_0.1. With Thunderbird all works fine, but when i configure the email client of Mac (Yosemite) with IMAP i can see a error in the log and the client not see the emails: Oct 9 14:31:34 localhost dovecot: imap(xxxxxxx@xxxxxxx): Fatal: master: service(imap): child 18639 killed with signal 11 (core dumps disabled) I have read the instructions of http://www.dovecot.org/bugreport.html, but core file is not writing. Does anyone have this issues? I think that can be a problem in the configuration Best regards

2 1

iterate users with passwd-file passdb?
by Eric Abrahamsen 12 Oct '15

12 Oct '15

Apologies for the basic question, but I've been googling and can't figure out if this is possible or not. Simply: Is it possible to iterate over users if I'm using the passwd-file passdb driver? Do I need a SQL-based driver if I want to iterate? Here's what I've got right now. I don't have many users, and would prefer to retain the simplicity of the passwd-file if possible. Thanks! passdb { driver = passwd-file args = username_format=%u scheme=ssha512 /etc/dovecot/passwd.db deny = no master = no pass = no skip = never result_failure = continue result_internalfail = continue result_success = return-ok } userdb { driver = static args = uid=5000 gid=5000 home=/var/mail/vmail/%d/%n }

1 0

Syncronizing two IMAP servers
by Timothy Murphy 10 Oct '15

10 Oct '15

I spend time in two places, in different countries. I have a local network in each place, with IMAP servers on each network. I collect email by fetchmail from various servers, and read email on my laptop with KMail. I tried using just one IMAP server, but this proved impractical. So I have two collections of the same sub-folders, on the two servers. I have two questions: 1. Is there a simpler way of organizing my email? 2. Given the current method, is there a way of syncronizing folders on the two servers? -- Timothy Murphy gayleard /at/ eircom.net School of Mathematics, Trinity College, Dublin

4 3

Maildir: ACLs/Unix perms and unable to see content of specific mailbox
by Olaf Marzocchi 10 Oct '15

10 Oct '15

Dear Dovecot users, hello. I will merge two issues I have into a single email because they may be related. I used dovecot on a OmniOS server since 2014 (currently OmniOS r151014) with the following configuration (it shows 2.2.18 because I recently updated dovecot, skipping only the PostgreSQL plugin): # 2.2.18: /etc/dovecot/dovecot.conf # OS: SunOS 5.11 i86pc zfs mail_location = maildir:/tank/home/%u/Maildir mail_privileged_group = mail namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { driver = pam } protocols = imap ssl = required ssl_cert = </etc/dovecot/certs/dovecot.pem ssl_key = </etc/dovecot/private/dovecot.pem userdb { driver = passwd } You can see that I set the Maildir folder inside the shared home folders of my server (it is only one user, anyway). It always worked perfectly, but one-two months ago I changed the permissions of my whole home folder, recursively, to add proper ACLs. I needed them because the clients started using illumos kernel SMB (relying on ACLs) instead of Netatalk/AFP (relying on Unix perms only). I didn't realise I applied the ACLs also to the Maildir folder. Dovecot worked for several weeks fine, I noticed the issue only yesterday when a mailbox (see below) appeared in Thunderbird completely empty even if the "cur" subfolder on the server still contains all the mails. Dovecot was throwing some errors like: dovecot: [ID 583609 mail.error] imap(olaf): Error: rename(/tank/home/olaf/Maildir/.&A6k- Mailing Lists.Log/dovecot.index.cache) failed: Permission denied (euid=501(olaf) egid=501(olaf) UNIX perms appear ok (ACL/MAC wrong?)) dovecot: [ID 583609 mail.error] imap(olaf): Error: rename(/tank/home/olaf/Maildir/.&A6k- Mailing Lists.Log/dovecot.index.tmp, /tank/home/olaf/Maildir/.&A6k- Mailing Lists.Log/dovecot.index) failed: Permission denied dovecot: [ID 583609 mail.error] imap(olaf): Error: unlink(/tank/home/olaf/Maildir/subscriptions.lock) failed: Permission denied dovecot: [ID 583609 mail.error] imap(olaf): Error: rename(/tank/home/olaf/Maildir/subscriptions.lock, /tank/home/olaf/Maildir/subscriptions) failed: Permission denied I will post here the current permissions of the folder containing Maildir, of the Maildir itself, of its contents, and of the folder that appears empty when browsed with a client (Thunderbird). /tank/home/olaf $ ls -lV .. drwx------+ 16 olaf olaf 17 Sep 19 01:52 olaf user:olaf:rwxpdDaARWcCos:fd-----:allow group:2147483648:rwxpdDaARWcCos:fd-----:allow everyone@:rwxpdDaARWcCos:fd-----:deny /tank/home/olaf $ ls -lV drwxrwx--- 348 olaf olaf 359 Sep 19 01:51 Maildir owner@:rwxp--aARWcCos:-------:allow group@:rwxp--a-R-c--s:-------:allow everyone@:------a-R-c--s:-------:allow /tank/home/olaf $ ls -lV Maildir/ drwxrwx--- 2 olaf olaf 2 Jan 30 2014 cur owner@:rwxp--aARWcCos:-------:allow group@:rwxp--a-R-c--s:-------:allow everyone@:------a-R-c--s:-------:allow -rwxrwx--- 1 olaf olaf 21 Jan 30 2014 dovecot-keywords owner@:rwxp--aARWcCos:-------:allow group@:rwxp--a-R-c--s:-------:allow everyone@:------a-R-c--s:-------:allow (ALL THE SAME PERMISSIONS FOR THE OTHER FILES EXCEPT...) -rwxrwx--- 1 olaf olaf 13735 Jan 24 2015 subscriptions owner@:rwxp--aARWcCos:-------:allow group@:rwxp--a-R-c--s:-------:allow everyone@:------a-R-c--s:-------:allow -rw-rw---- 1 olaf olaf 13709 Sep 19 01:51 subscriptions.lock owner@:rw-p--aARWcCos:-------:allow group@:rw-p--a-R-c--s:-------:allow everyone@:------a-R-c--s:-------:allow The folder that appears empty: /tank/home/olaf $ ls -lV Maildir/.Generiche/ total 513 drwxrwx--- 2 olaf olaf 949 Sep 18 01:42 cur owner@:rwxp--aARWcCos:-------:allow group@:rwxp--a-R-c--s:-------:allow everyone@:------a-R-c--s:-------:allow -rwxrwx--- 1 olaf olaf 46 May 18 2014 dovecot-keywords owner@:rwxp--aARWcCos:-------:allow group@:rwxp--a-R-c--s:-------:allow everyone@:------a-R-c--s:-------:allow (ALL THE SAME PERMISSIONS FOR THE OTHER FILES) I really hope you will have the time to help me because I already applied the permissions recursively and I removed the ACLs, almost as it was before my mistake. I specified "almost" because originally (I checked the backups) the Maildir folder had an ACL that gave access permissions also to the group "mail": drwxrwx---+349 olaf olaf 359 Feb 16 2014 Maildir group:mail:rwxpdDaARWcCos:fd-----:allow owner@:rwxpdDaARWcCos:fd----I:allow group@:rwxpdDaARWcCos:fd----I:allow everyone@:rwxpdDaARWcCos:fd----I:deny Yesterday I haven't replicated it because from the documentation I understood it was not necessary. My questions, in short: - what are the permissions I need to give to the Maildir folder? I understood from the documentation it's 700, with my user/group (the one of the user accessing the mail). What about ACLs? and what about group "mail"? - the (only!) subfolder which appears empty in Thunderbird, may it depend on the permissions? maybe due to them the index was not updated and UIDs don't match. If after applying the correct permissions I still cannot see its contents, is there a way to recover the mails? the files are all still there. Sorry for the long email, but after several tries yesterday I exhausted my ideas. Regards, Olaf

2 4

Double Dots
by Ken Mandelberg 09 Oct '15

09 Oct '15

I've noticed lately that Dovecot seems to be inserting an extra dot in some url's contained in html email. The most consistent example I see is in the newsletters from the Washington Post. For example, if I look at the raw email on the mail server I see text that starts <http://link.washingtonpost.com/click But if I look at what Thunderbird shows it starts http://link..washingtonpost.com/click/ I don't think its Thunderbird adding the dot, since K9 mail on my Android phone shows the same issue. It's only after the IMAP delivery that the extra dot appears. We are running dovecot 2.0.12 Incidentally, the newsletter is full of these link.washington post url's. For each article it appears 3 times, once on title, once on a "read full article" link, and one on a picture. Its only the one on title, that gets the extra dot after its been through dovecot. Furthermore, it only happens from the second article on. Any ideas?

2 1

Dovecot plugin and Push Mail
by Steffan Cline 08 Oct '15

08 Oct '15

I’m posting this here and will in a couple other places to see if anyone has any experience with this and knows what I can do. My setup is CentOS 6 with postfix, procmail and dovecot administered via Virtualmin. Postfix of course receives the email. Procmail uses it’s hooks to run the email through spam assassin and clamd. After than procmail hands it off to dovecot/deliver to drop it in the user’s mail box. I use the following plugin for dovecot with the daemon to provide Apple push mail for iPhones. https://github.com/st3fan/dovecot-xaps-daemon https://github.com/st3fan/dovecot-xaps-plugin For the most part, this works awesome but have run into a bit of a race issue with notification of mail in a particular instance. On my computer I use Outlook for Mac which says it supports IDLE but is broken. When an email comes in, I ALWAYS get the notification via the dovecpt plugin for a push since Outlook is checking IMAP every 2 minutes. On a buddy’s setup, he uses Apple Mail which supports IDLE that actually works. When his email client is connected from his laptop, it does actually maintain a persistent connection and NEVER receives a notification from the dovecot plugin because I’m guessing dovecot/deliver sees that the email was received by the desktop client. I’m not sure how to make the plugin ALWAYS give a push. Is it a dovecot config? A bug in the plugin? I’m not sure. Suggestions? Thank you, Steffan Cline 602-793-0014

1 1

how to treat synonymous domain names as one
by Nikolai Krot 08 Oct '15

08 Oct '15

Hallo List Users, I am curious if there is a way to rewrite domain name to another domain name. My goal is to provide authentication and mailboxes for the synonymous domains in a single source while keeping all other domains separate. I have setup: auth_username_format = %Lu mail_location = /var/vmail/%d/%u/Maildir in userdb/passdb (passwd-file): /etc/dovecot/%d/users Say I have two synonymous domain names my-domain-1.com my-long-named-domain-1.com I want both to resolve to my-domain-1.com when %d variable is used in Dovecot configs, so that passwd-file is /etc/dovecot/my-domain-1.com/users mailbox is /var/vmail/my-domain-1.com/user/Maildir while keeping other domains unchanged my-other-domain-2.com should resolve to: passwd-file is /etc/dovecot/my-other-domain-2.com/users mailbox is /var/vmail/my-other-domain-2.com/user/Maildir thanks, Nikolai

2 2

bug report: dovecot-imapd core dump
by Tamas Papp 07 Oct '15

07 Oct '15

Typical log message: Oct 7 11:39:36 hostname dovecot: imap(username): Fatal: master: service(imap): child 14864 killed with signal 11 (core dumped) What triggers the problem: User moving multiple messages to a subfolder via IMAP (from another account, on another server, client: Thunderbird). Moving single messages either does not trigger the problem, or with much lower probability (could not reproduce). Version: $ dpkg -l 'dovecot*' Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-=====================================-=======================-=======================-================================================================================ un dovecot-common <none> <none> (no description available) ii dovecot-core 1:2.2.9-1ubuntu5 amd64 secure POP3/IMAP server - core files un dovecot-gssapi <none> <none> (no description available) ii dovecot-imapd 1:2.2.9-1ubuntu5 amd64 secure POP3/IMAP server - IMAP daemon un dovecot-ldap <none> <none> (no description available) un dovecot-lmtpd <none> <none> (no description available) un dovecot-managesieved <none> <none> (no description available) un dovecot-mysql <none> <none> (no description available) un dovecot-pgsql <none> <none> (no description available) un dovecot-pop3d <none> <none> (no description available) un dovecot-sieve <none> <none> (no description available) un dovecot-solr <none> <none> (no description available) un dovecot-sqlite <none> <none> (no description available) tamas@szob:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 15.04 Release: 15.04 Codename: vivid Also tried 2.2.18 from Ubuntu wiley, same results. Backtrace (I am not sure this is useful, extraced core from Ubuntu's Apport): (gdb) bt full #0 0x00007f404e58e3b6 in mail_index_keywords_unref () from /usr/lib/dovecot/libdovecot-storage.so.0 No symbol table info available. #1 0x00007f404ea254ad in _start () No symbol table info available. Any help would be appreciated, I am happy to provide more info if necessary. Tamas

1 0

separate passdb for unix_listener
by Damon 07 Oct '15

07 Oct '15

I want to use a separate passed for the unix_listener (postfix smtp-auth) so i can limit access to the smtp server by user/domain using the postfixadmin database. I want to let users access map to receive email but not be able to send. Any ideas? Thanks Damon

3 2

Dovecot don't erase mails from storage.
by Carlos Baptista 05 Oct '15

05 Oct '15

Hi, I have a dovecot installation with a strange problem: all the mails stays in storage after deleted from users mailbox. If user logon after the mails are deleted, they don't receive them any more, but the m.## files aren’t deleted. This happens with pop3 (default for this installation) and/or imap. The dovecot is installed along postfix with mysql and multi-domains support Here's the dovecot conf ######################## dovecot -n # 2.1.7: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-042stab111.11 x86_64 Debian 7.9 auth_mechanisms = plain login first_valid_uid = 111 last_valid_uid = 111 lda_mailbox_autocreate = yes mail_debug = yes mail_gid = vmail mail_plugins = " quota" mail_privileged_group = vmail mail_uid = vmail namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } plugin { mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename mail_log_fields = uid box msgid size quota = dict:User quota::file:%h/mail/dovecot-quota quota_rule = *:storage=500MB } postmaster_address = sysadmin(a)inside.pt protocols = " imap pop3" service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0660 user = postfix } } ssl_cert = </etc/dovecot/dovecot.pem ssl_key = </etc/dovecot/private/dovecot.pem userdb { driver = prefetch } userdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } protocol lmtp { mail_plugins = " quota sieve" } protocol lda { mail_plugins = " quota" } protocol imap { mail_plugins = " quota imap_quota" } ############################### Here is an example of log file with debug Oct 02 17:50:38 auth: Debug: auth client connected (pid=11621) Oct 02 17:50:38 auth: Debug: client in: AUTH 1 PLAIN service=pop3 secured session=Xiif9iEhmgBV80+u lip=xxx.xxx.xxx.xxx rip=xxx.xxx.xxx.xxx lport=995 rport=53914 resp=<hidden> Oct 02 17:50:38 auth-worker(11561): Debug: sql(carla.franjoso(a)xxxxxxx.xx,xxx.xxx.xxx.xxx): query: /* dovecot-sql.conf password_query */ SELECT '/var/vmail/xxxxxx.xx/carla.franjoso' AS userdb_home, 'mdbox:~/mail' AS userdb_mail, 111 AS userdb_uid, 114 AS userdb_gid, CONCAT('*:bytes=', CAST(m.quota AS CHAR)) AS userdb_quota_rule, CONCAT(m.local_part, '@', d.name) AS user, m.password AS password FROM mailboxes AS m LEFT JOIN domains AS d ON m.domain_id = d.id WHERE m.local_part = 'carla.franjoso' AND d.name = 'xxxxxxx.xx' AND m.is_active AND d.is_active Oct 02 17:50:38 auth: Debug: client out: OK 1 user=carla.franjoso(a)xxxxxx.xx Oct 02 17:50:38 auth: Debug: master in: REQUEST 3537633281 11621 1 41ef179d4a37a603ce38c43fab768f78 Oct 02 17:50:38 auth: Debug: prefetch(carla.franjoso(a)xxxxxx.xx,xxx.xxx.xxx.xxx,<Xiif9iEhmgBV80+u>): success Oct 02 17:50:38 auth: Debug: master out: USER 3537633281 carla.franjoso(a)xxxxx.xx home=/var/vmail/xxxxxxxx/carla.franjoso mail=mdbox:~/mail uid=1 11 gid=114 quota_rule=*:bytes=104857600 Oct 02 17:50:38 pop3: Debug: Loading modules from directory: /usr/lib/dovecot/modules Oct 02 17:50:38 pop3: Debug: Module loaded: /usr/lib/dovecot/modules/lib10_quota_plugin.so Oct 02 17:50:38 pop3: Debug: Added userdb setting: mail=mdbox:~/mail Oct 02 17:50:38 pop3: Debug: Added userdb setting: plugin/quota_rule=*:bytes=104857600 Oct 02 17:50:38 pop3(carla.franjoso(a)xxxxx.xx): Debug: Effective uid=111, gid=114, home=/var/vmail/xxxxxxxx.xx/carla.franjoso Oct 02 17:50:38 pop3(carla.franjoso(a)xxxxx.xx): Debug: Quota root: name=User quota backend=dict args=:file:/var/vmail/xxxxxxxxx.xx/carla.franjoso/mail/dovecot-quota Oct 02 17:50:38 pop3(carla.franjoso(a)xxxxx.xx): Debug: Quota rule: root=User quota mailbox=* bytes=104857600 messages=0 Oct 02 17:50:38 pop3(carla.franjoso(a)xxxxx.xx): Debug: dict quota: user=carla.franjoso(a)xxxx.xx, uri=file:/var/vmail/xxxxxx,xx/carla.franjoso/mail/dovecot-quot a, noenforcing=0 Oct 02 17:50:38 pop3(carla.franjoso(a)xxxxx.xx): Debug: Namespace inbox: type=private, prefix=, sep=, inbox=yes, hidden=no, list=yes, subscriptions=yes locatio n=mdbox:~/mail Oct 02 17:50:38 pop3(carla.franjoso(a)xxxxx.xx): Debug: fs: root=/var/vmail/ assis.pt/carla.franjoso/mail, index=, control=, inbox=, alt= Oct 02 17:50:38 pop3(carla.franjoso(a)xxxxx.xx): Debug: Namespace : Using permissions from /var/vmail/xxxxxxx.xx/carla.franjoso/mail: mode=0700 gid=-1 What is "gid=-1" at the end of the log? Can anyone help? Thanks Carlos Baptista

2 1

Compiling v2.2.19 - internal compiler error: segmentation fault (test-timing.c -> int64_t issue?)
by Guest-X 05 Oct '15

05 Oct '15

Hi, I am trying to compile a 64-build of the latest dovecot v2.2.19 on my SuSE Linux Enterprise Server 10 (x64) system. I've run ./configure with two parameters, the --prefix one and the --with-ssldir one. During the make stage, I am getting the following 'internal compiler error' message : --------------------------------------------- [...] gcc -DHAVE_CONFIG_H -I. -I../.. -I../../src/lib-test -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -fno-builtin-strftime -Wstrict-aliasing=2 -MT test_lib-test-timing.o -MD -MP -MF .deps/test_lib-test-timing.Tpo -c -o test_lib-test-timing.o `test -f 'test-timing.c' || echo './'`test-timing.c test-timing.c: In function ‘test_timing’: test-timing.c:48: internal compiler error: Segmentation fault Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://bugs.opensuse.org> for instructions. make[4]: *** [test_lib-test-timing.o] Error 1 ---------------------------------------------- The lines that seem to be causing the problem are the following ( from src/lib/test-timing.c ) : 45: void test_timing(void) 46: { 47: static int64_t test_input1[] = { 48: 20, 19, 18, 1, 2, 3, 4, 5, 6, 7, 8, 49: 9, 10, 11, 12, 13, 14, 15, 16, 17, -1 50: }; This is the first time that any version of dovecot (the v2.2 branch) couldn't compile on my system, and I've literally compiled every single release up to now. My gcc version is a very old one (4.1.2) : ---------------------------------------------- Using built-in specs. Target: x86_64-suse-linux Configured with: ../configure --enable-threads=posix --prefix=/usr --with-local-prefix=/usr/local --infodir=/usr/share/info --mandir=/usr/share/man --libdir=/usr/lib64 --libexecdir=/usr/lib64 --enable-languages=c,c++,objc,fortran,obj-c++,java,ada --enable-checking=release --with-gxx-include-dir=/usr/include/c++/4.1.2 --enable-ssp --disable-libssp --disable-libgcj --with-slibdir=/lib64 --with-system-zlib --enable-shared --enable-__cxa_atexit --enable-libstdcxx-allocator=new --program-suffix= --enable-version-specific-runtime-libs --without-system-libunwind --with-cpu=generic --host=x86_64-suse-linux Thread model: posix gcc version 4.1.2 20070115 (prerelease) (SUSE Linux) ----------------------------------------------- Don't know whether this helps, but I've noticed that if I change the int64_t to uint64_t in the following lines of the same file : 61: static int64_t *test_inputs[] = { 62: test_input1, test_input2, test_input3 63: }; ..then compilation finishes without errors, but I'm not certain what the practical consequences of this action might be. Can somebody help me please ? Thank you for your time.

1 0

Released Pigeonhole v0.4.9 for Dovecot v2.2.19
by Stephan Bosch 05 Oct '15

05 Oct '15

Hello Dovecot users, Here is the definitive 0.4.9 release. Only a few minor fixes were done since RC1. Changelog v0.4.9: * Properly implemented checking of ABI version for Sieve interpreter plugins, much like Dovecot itself does for plugins. This will prevent plugin ABI mismatches. + Implemented a vnd.dovecot.environment extension. This builds upon the standard environment extension and adds a few more environment items, such as username and default mailbox. It also creates a variables namespace so that environment items can be accessed directly. I am still thinking about more environment items that can be added. + Sieve extprograms plugin: Made line endings of the input passed to the external programs configurable. This can be configured separately for each of the three extensions. + ManageSieve: Implemented proxy XCLIENT support. This allows the proxy to pass client information to the back-end. - ManageSieve: Fixed an assert failure occurring when a client disconnects during the GETSCRIPT command. - doveadm sieve plugin: Fixed incorrect initialization of mail user. This caused a few memory leaks. - sieve-filter command line tool: Fixed handling of failure-related implicit keep when there is an explicit default destination folder. This caused message duplication. - lib-sieve: Fixed bug in RFC5322 header folding. Words longer than the optimal line length caused empty lines in the output, which would break the resulting message header. This surfaced in References: headers with very long message IDs. The release is available as follows: http://pigeonhole.dovecot.org/releases/2.2/dovecot-2.2-pigeonhole-0.4.9.tar… http://pigeonhole.dovecot.org/releases/2.2/dovecot-2.2-pigeonhole-0.4.9.tar… Refer to http://pigeonhole.dovecot.org and the Dovecot v2.x wiki for more information. Have fun testing this new release and don't hesitate to notify me when there are any problems. Regards, -- Stephan Bosch stephan(a)rename-it.nl

1 0

v2.2.19 released
by Timo Sirainen 03 Oct '15

03 Oct '15

http://dovecot.org/releases/2.2/dovecot-2.2.19.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.19.tar.gz.sig * pop3_deleted_flag has been broken since v2.2.10. Using it would cause buffer overflows, which could be exploitable. However, this bug would have become visible quite soon after users had deleted some POP3 mails, because the pop3 processes would have started crashing all the time even in normal use. * "doveadm director flush" command has a changed meaning now: It safely moves users to their wanted backends, instead of simply forgetting the mapping entirely and leaving the existing connections untouched. Use -F parameter to get the original unsafe behavior. + Added imap-hibernate processes (see imap_hibernate_timeout setting). IDLEing IMAP connections can be hibernated, which saves memory. + Optimized tracking mailboxes' vsizes (= sum of all messages' sizes). If mailbox_list_index=yes, it's also stored in there. This makes it very efficient to look up vsizes for all mailboxes. + Added a quota "count" backend, which uses the mailbox vsizes to get the current quota usage. It requires using the new quota_vsizes=yes setting, which tracks the messages' "virtual sizes" rather than "physical sizes". Their distiction is minor and mostly irrelevant nowadays (if mail sizes should be counted with LF or CRLF newlines). + "doveadm director up/down" commands added. The monitoring script should be using these commands instead of changing the vhost count. This allows admin to manually disable a server by changing the vhost count to 0 without the monitoring script changing it back. + Added support for HAProxy protocol: http://wiki2.dovecot.org/HAProxy + Added push-notification plugin framework, which can be used to easily implement push notifications to various backends. Implemented "ox" backend for notifying Open-Xchange via HTTP/json. + imap_logout_format supports more variables now, e.g. number of deleted messages. + pop3: Added pop3_delete_type setting (related to pop3_deleted_flag). + plugin { fts_enforced=yes } setting now fails body searches unless it can be done via the full text search engine. + Added %{passdb:*} and %{userdb:*} variables to various places + auth: Added ":protected" suffix for passdb and userdb fields. If used, the field doesn't overwrite an existing field. + IMAP/POP3 proxy: If a backend server dies, avoid client reconnection spikes by slowly disconnecting clients over time. This is enabled by setting login_proxy_max_disconnect_delay=secs passdb extra field. + imap: Added new read-only METADATA entries: /private/specialuse, /shared/comment, /shared/admin + imap: If client disconnects in the middle of a command, log how long the command had been running. - mdbox: Rebuilding could have caused message's reference count to overflow the 16bit number in some situations, causing problems when trying to expunge the duplicates. - Various search fixes (fts, solr, tika, lib-charset, indexer) - Various virtual plugin fixes - Various fixes and optimizations to dsync, imapc and pop3-migration - imap: Various RFC compliancy and crash fixes to NOTIFY

3 6

Re: dovecot quota service for postfix
by Michael Peter 03 Oct '15

03 Oct '15

Hello, Thanks for the clarifications plugin { quota = maildir:User quota quota_rule = *:storage=1G quota_grace = 10%% # 10% is the default quota_status_success = DUNNO quota_status_nouser = DUNNO quota_status_overquota = "552 5.2.2 Mailbox is full" } The above configurations is my default for all users. but my mail system is using mbox format and not maildir.... so what should i change in the above configuration to use mbox INSTEAD of maildir ?? Also for the quota paramater, can i use (myquota = maildir:User quota) INSTEAD of (quota = maildir:User quota) ?? or it must "QUOTA =" and not any thing else to work ? same for quota_rule parameter, should i add (_rule) after quota to work ??? can i add for example qouta_restriction INSTEAD of quota_rules ?? i am asking this question to better understand how dovecot work.. also last question when i use the following command to get quota for existing system user called michael , it gives me an error as follow, so why dovecot is not able to get the quota for the system users? doveadm quota get -u michael doveadm(michael): Fatal: User doesn't exist Many thanks >> Incase user is underquota, then the email is returned back to postfix for >> processing and delivering email to user mbox, incase user has no sufficient quota then dovecot will inform postfix to reject email. Please confirm if what i mentioned above is correct and that i >> understand >> correctly how dove-cot policy works with postfix. > Your understanding is mor or less correct, except that postfix never passes the email itself to dovecot when performing the quota check. It simply sends a message to the quota policy service asking if the recipient is over quota. If the recipient is over quota, dovecot provides postfix with the response configured in quota_status_overquota. If the recipient is under quota, dovecot provides postfix with the response configured in quota_status_success. If dovecot does not know the user, it provides postfix with the response configured in > quota_status_nouser. >> Kindly check my configuration below and advise the missing parts to add... > I don't see anything wrong with your configuration on first appraisal, but if it isn't working I would recommend you perform the following troubleshooting steps. > 1. Verify the user's mailbox is over or under quota in alignment with your expectations > - `doveadm quota -u $RECIPIENT` > 2. Test that the quota service provides the response you expect it to > - `echo "recipient=$RECIPIENT" | nc -q1 localhost 12340` > On 09/26/2015 01:40 AM, Michael Peter wrote: >> Hello, >> I am trying to use dovecot quota service for postfix in order set quota for some users. >> i configure postfix policy service to ask dovecot if user quota is sufficient to accept the email or not. >> (dovecot in this case acts only as policy server to postfix as it only ACCEPT/REJECT email according to user quota, but it is not used to deliver >> email , because postfix will deliver the email to user mailbox) Incase user is underquota, then the email is returned back to postfix for >> processing and delivering email to user mbox, incase user has no sufficient quota then dovecot will inform postfix to reject email. Please confirm if what i mentioned above is correct and that i >> understand >> correctly how dove-cot policy works with postfix. >> Kindly check my configuration below and advise the missing parts to add... >> plugin { >> quota_rule = *:storage=1G >> quota_grace = 10%% >> # 10% is the default >> quota_status_success = DUNNO >> quota_status_nouser = DUNNO >> quota_status_overquota = "552 5.2.2 Mailbox is full" >> ... >> } >> The above configurations is for all users which is not override by quota >> rules in userdb's extra fields in my password file below. >> Is the above configuration missing some thing ? i am using mbox format for >> emails storage. do you i have to add (quota= SOMETHING) before >> (quote_rule >> = *:storage=1G) and what to do add to make dovecot support mbox quota? smtpd_recipient_restrictions = >> check_policy_service inet:SERVER-HIDDEN-FOR-SECRUITY.com:12340 >> service quota-status { >> executable = quota-status -p postfix >> inet_listener { >> port = 12340 >> } >> client_limit = 1 >> } >> now in order to configure dovecot specific quota for user named (user1) i >> use passwd-file as follow >> user1:{plain}pass3:1002:1002::/home/user1::userdb_mail=mbox:~/mymail:INBOX=/var/mail/user1 userdb_quota_rule=*:bytes=300M >> All other users except users1 should have 1GB storage according to this configuration. which user1 will only have 300MB >> Please advise what is my configuration is missing and if i need to add any >> thing to run without issues. >> Many thanks >> Michael Peter

1 0

imap_logout_format improvements / ideas
by Timo Sirainen 03 Oct '15

03 Oct '15

http://hg.dovecot.org/dovecot-2.2/rev/93bba97afb2a http://hg.dovecot.org/dovecot-2.2/rev/e0a17714f0c9 So all in all, you can now add to imap_logout_format: # %i - total number of bytes read from client # %o - total number of bytes sent to client # %{fetch_hdr_count} - Number of mails with mail header data sent to client # %{fetch_hdr_bytes} - Number of bytes with mail header data sent to client # %{fetch_body_count} - Number of mails with mail body data sent to client # %{fetch_body_bytes} - Number of bytes with mail body data sent to client # %{deleted} - Number of mails where client added \Deleted flag # %{expunged} - Number of mails that client expunged # %{trashed} - Number of mails that client copied/moved to the # special_use=\Trash mailbox. Any thoughts on what else would be useful? I was also thinking about separating (deletes and) expunges from Trash vs non-Trash, but I'm not sure how useful that would be (and what would it be called?) It's also a bit annoying that a copy+expunge to a Trash will return expunged=1 trashed=1, but a move to Trash (via IMAP MOVE) will return expunged=0 trashed=1. But trying to fix that would be too much trouble.

4 4