- dovecot - dovecot.org

Upgrade to 2.2.9 breaks sasl auth
by Paul 15 Jun '16

15 Jun '16

Hi This is my 1st time here so please be gentle. I have encountered one problem since upgrading from 2.0.19 to 2.2.9 which has me beat. The system provides sasl auth services via inet to a postfix 2.11 system. Since the upgrade postfix complains of no sasl methods available. The same dovecot configuration is used on both versions. Now I get these results looking at the inet connection Version 2.0.19 root@larch:~# telnet 192.168.3.15 12345 Trying 192.168.3.15... Connected to 192.168.3.15. Escape character is '^]'. VERSION 1 1 MECH PLAIN plaintext MECH LOGIN plaintext MECH CRAM-MD5 dictionary active SPID 23223 CUID 1 COOKIE d0b71942d48585303f9ae4681baabf87 DONE Version 2.2.9 root@larch:~# telnet 192.168.3.112 12345 Trying 192.168.3.112... Connected to 192.168.3.112. Escape character is '^]'. VERSION 1 1 SPID 5300 Seems be something lacking in the response from 2.2.9 that fits the "no sasl methods" response from postfix I believe I should supply root@larchvm:/etc/dovecot-sasl# dovecot -n -c dovecot.conf # 2.2.9: dovecot.conf # OS: Linux 3.13.0-88-generic i686 Ubuntu 14.04.4 LTS auth_mechanisms = plain login cram-md5 auth_verbose_passwords = plain base_dir = /var/run/dovecot-sasl/ disable_plaintext_auth = no instance_name = sasl mail_chroot = /chroot/mail mail_location = maildir:~/Maildir mail_plugins = quota managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacati on subaddress comparator-i;ascii-numeric relational regex imap4flags copy includ e variables body enotify environment mailbox date ihave namespace { inbox = yes location = prefix = INBOX. type = private } passdb { args = /etc/dovecot-sasl/dovecot-sqlmd5.conf driver = sql } plugin { deleted_to_trash_folder = Trash quota = maildir:User quota quota:noenforcing quota_rule = Trash:ignore sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } service auth { inet_listener auth-userdb { address = 192.168.3.112 port = 12345 ssl = yes } unix_listener /var/spool/postfix/private/auth { mode = 0666 } unix_listener auth-userdb { mode = 0600 } } service imap-login { inet_listener imap { address = 213.210.16.65 port = 143 } inet_listener imaps { address = 213.210.16.65 port = 993 ssl = yes } } service managesieve-login { inet_listener sieve { address = 213.210.16.65 port = 4190 } } ssl_cert = </etc/ssl/certs/pe.pem ssl_key = </etc/ssl/private/pe.pem userdb { args = /etc/dovecot-sasl/dovecot-sql.conf driver = sql } protocol imap { mail_plugins = quota imap_quota deleted_to_trash } Any help or suggestion warmly welcomed

2 3

shutdown_clients has no effect on doveadm stop
by Roland Rosenfeld 14 Jun '16

14 Jun '16

I try to restart dovecot 2.2.24 (for changing limits) without killing all IMAP and POP3 sessions. dovecot(1) tells me: When shutdown_clients is set to no, existing sessions will continue to use the old settings, after a dovecot reload. Also all sessions will keep alive after a dovecot stop. By default all active sessions will be shut down. According to my "dovecot -n" (see below), I have set "shutdown_clients=no", so "doveadm stop" should keep my open sessions. But if I try this out with a simple telnet to port 143 during "doveadm stop", I see the following: $ telnet imap 143 Connected to imap. Escape character is '^]'. * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE AUTH=PLAIN AUTH=LOGIN] Dovecot ready. a login user(a)example.com XXXXX 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 BINARY MOVE QUOTA ACL RIGHTS=texk] Logged in * BYE Server shutting down. Connection closed by foreign host. The "BYE Server shutting down." happens exactly at the time, when I press return after "doveadm stop", "systemctl stop dovecot", or "systemctl restart dovecot" in the other shell. Only "systemctl reload dovecot" keeps the open sessions healthy. So it seems that either the man page is wrong, or shutdown_clients=no has no effect after dovecot stop... Greetings Roland dovecot -n # 2.2.24 (a82c823): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.14 (099a97c) # OS: Linux 3.16.0-4-amd64 x86_64 Debian 8.5 auth_cache_negative_ttl = 5 mins auth_cache_size = 100 M auth_cache_ttl = 15 mins auth_default_realm = netcologne.de auth_master_user_separator = * auth_mechanisms = plain login auth_verbose = yes dict { acl = mysql:/etc/dovecot/dovecot-dict-sql.conf } disable_plaintext_auth = no listen = * log_timestamp = "%Y-%m-%d %H:%M:%S " mail_fsync = always mail_gid = 999 mail_location = maildir:~/mail mail_plugins = acl quota zlib mail_uid = 999 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 mmap_disable = yes namespace { list = children location = maildir:%%h/mail:INDEX=~/mail/shared/%%u prefix = shared/%%u/ separator = / subscriptions = no type = shared } namespace inbox { inbox = yes location = prefix = separator = / type = private } passdb { args = /etc/dovecot/passwd.master driver = passwd-file master = yes pass = yes } passdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } plugin { acl = vfile acl_shared_dict = proxy::acl quota = maildir sieve = ~/.dovecot.sieve sieve_dir = ~/mail/sieve sieve_extensions = +imapflags zlib_save = gz } pop3_no_flag_updates = yes pop3_uidl_format = %v.%u protocols = imap pop3 sieve service auth { unix_listener auth-master { group = vmail mode = 0600 user = vmail } } service dict { unix_listener dict { group = vmail mode = 0600 user = vmail } } service imap { process_limit = 4000 } service managesieve-login { inet_listener sieve { port = 4190 } } service managesieve { process_limit = 100 } service pop3 { process_limit = 1000 } shutdown_clients = no ssl = no syslog_facility = local2 userdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } verbose_proctitle = yes protocol imap { mail_max_userip_connections = 10 mail_plugins = acl quota zlib imap_quota imap_acl } protocol pop3 { mail_plugins = acl quota zlib }

2 3

Alternate Storage and quota limits
by mailing lists 14 Jun '16

14 Jun '16

Hi all, is there any way of exclude messages storaged in alternate storage (*dbox mailbox format) from being included in the quota usage? I think this is not possible but let me ask.

1 0

Alternate Storage and quota limits
by mailing lists 14 Jun '16

14 Jun '16

Hi all, is there any way of exclude messages storaged in alternate storage (*dbox mailbox format) from being included in the quota usage? I think this is not possible but let me ask.

1 0

Advice on once a day message delivery setup
by KT Walrus 13 Jun '16

13 Jun '16

I’m adding once a day mail delivery to my site. Messages are marked by the sender as “overnight” or “once a week” delivery. The way I’m planning on implementing this is to queue messages until midnight in a MySQL database. Each mailbox will be kept in two Dovecot mailstores. The first mailstore will give the users IMAP access to their mailbox. A second mailstore will hold the next day’s new messages. At midnight, a cron job runs to send messages in the MySQL database out to the second mailstore. Then, at 6am, a second cron job will run to sync the two mailstores using doveadm sync. What I am expecting to happen is that during the day, notification messages (from the site) may be delivered to the first mailstore (the one providing IMAP access to the user) but no messages from other users sent during the day will come until after 6am the next day. Each time the user submits a new message, a notification message is sent back to the sender with a link for editing the queued message in the MySQL database and an indication of when it is scheduled for delivery. I am kind of assuming that the morning sync process is fast enough so it can easily complete before noon (in 6 hours) even if I end up having lots of mailboxes on each fully loaded Dovecot server. Is the doveadm sync process reliable and efficient enough for this type of “once a day” morning new message mail delivery? Or, should I just start delivering messages after midnight and not bother with the second mailstore and subsequent sync? Just looking for any advice… I kind of like the idea of modeling my mail service after the US Post Office where the mailman delivers new mail once a day rather than like Twitter/Facebook where messages are posted in real time to encourage users to monitor their boxes throughout the day. Kevin

3 2

doveadm-server protocol change?
by Heiko Schlittermann 13 Jun '16

13 Jun '16

Hi, I'm doing quota checks from a remote machine (the real setup is a bit more complex, if necessary I can explain it in more detail, but I just extracted the bits that are easily reproduceable) # nc backend1 24245 VERSION doveadm-server 1 0 PLAIN agrVMDvHgz0ya2HHzax5svwB2ZHS¹ + heiko quota get But since the backend is upgraded to 2.2.22 it's not possible anymore. The exuse in the log of the backend is: dovecot: doveadm(149.1.1.1¹): Fatal: USER environment is missing and -u option not used Running the `doveadm quota get -u heiko` locally on the backend works as expected. But using the the doveadm-server it doesn't. # 2.2.22 (fe789d2): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.13 (7b14904) # OS: Linux 4.4.0-22-generic x86_64 Ubuntu 16.04 LTS … auth_cache_negative_ttl = 0 auth_cache_ttl = 0 auth_master_user_separator = * base_dir = /run/dovecot/ imap_metadata = yes lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes login_log_format_elements = user=<%u> method=%m rip=%r lip=%l mpid=%e %c %k mail_attribute_dict = file:%h/dovecot-attributes mail_location = maildir:~:INBOX=/volumes/dovecot/inbox/%2.256Nn/%n:INDEX=/volumes/dovecot/cache/%2.256Nn/%n mail_plugins = quota mbox_md5 = all mmap_disable = yes namespace inbox { … passdb { args = /etc/dovecot/master-users driver = passwd-file master = yes } passdb { args = /etc/dovecot/dovecot-ldap.passdb.conf.ext driver = ldap } plugin { quota = maildir:User quota quota_grace = 10%% sieve = /volumes/dovecot/sieve/%2.256Nn/%n/.dovecot.sieve sieve_dir = /volumes/dovecot/sieve/%2.256Nn/%n } pop3_uidl_format = %v.%u protocols = " imap lmtp pop3" service auth { extra_groups = ssl-cert } service doveadm { inet_listener { port = 24245 } } service lmtp { inet_listener lmtp { port = 2525 } } ssl = required ssl_cert = </etc/ssl/certs/snakeoil-crt.pem ssl_key = </etc/ssl/private/snakeoil-key.pem userdb { driver = prefetch override_fields = home=/volumes/dovecot/home/%2.256Nn/%n uid=vmail gid=vmail } userdb { args = /etc/dovecot/dovecot-ldap.userdb.conf.ext driver = ldap override_fields = home=/volumes/dovecot/home/%2.256Nn/%n uid=vmail gid=vmail } verbose_proctitle = yes protocol lmtp { mail_plugins = quota sieve quota } protocol lda { mail_plugins = quota sieve } protocol imap { mail_plugins = quota imap_quota } local 149.1.1.0/24¹ { doveadm_password = # hidden, use -P to show it } ¹) It's changed :)

5 13

doveadm fts rescan <namespace> doesn't seem(!) to find <namespace>
by Larry Rosenman 13 Jun '16

13 Jun '16

thebighonker.lerctr.org ~ $ doveadm fts rescan \#ARCHIVE doveadm(ler): Error: Namespace prefix not found: #ARCHIVE thebighonker.lerctr.org ~ $ doveadm fts rescan #ARCHIVE thebighonker.lerctr.org ~ $ doveadm fts rescan inbox doveadm(ler): Error: Namespace prefix not found: inbox thebighonker.lerctr.org ~ $ Doveconf -n attached. -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 (c) E-Mail: larryrtx(a)gmail.com US Mail: 17716 Limpia Crk, Round Rock, TX 78664-7281

1 1

Potential bug report: Cannot use ":args" option via Pigeonhole Sieve pipe plugin
by Zeeshan Muhammad 13 Jun '16

13 Jun '16

Hi all, Following the instructions noted at http://wiki2.dovecot.org/Pigeonhole/Sieve/Plugins/Pipe , I am trying to make use of the Pigeonhole sieve pipe plugin to execute an application with custom arguments via my test sieve script: require ["vnd.dovecot.pipe"]; if address :is "to" "test(a)example.com" { pipe :args [ "first-arg", "second-arg" ] "sieve-pipe-example"; } I am editing my test sieve script via Mozilla Thunderbird v45.1.1 using the Sieve email-client addon (v0.2.3h, see https://github.com/thsmi/sieve#releases and https://addons.mozilla.org/en-US/thunderbird/addon/sieve/ ) When I attempt to save the example sieve script above, I get the following error returned by ManageSieve via Mozilla Thunderbird's Sieve addon: "The script could not be saved: Sieve mail filter: line 3: error: unknown tagged argument ':args' for the pipe command (reported only once at first occurrence). Sieve mail filter: error: validation failed." I have setup sieve-pipe-example as follows in my 90-sieve.conf configuration: service sieve-pipe-script { executable = script /usr/bin/echo user = dovenull # socket name is program-name in Sieve unix_listener sieve-pipe-example { } } I cannot see where I am going wrong. I have combed through the specification at http://hg.rename-it.nl/dovecot-2.2-pigeonhole/raw-file/tip/doc/rfc/spec-bos… as well as the official Dovecot/Pigeonhole wiki-pages and cannot find a solution. If I omit the :args option (and the arguments array), the sieve script successfully gets accepted by ManageSieve. Am I encountering a potential bug or am I doing something silly in my test setup? # Dovecot version: v2.2.24 # Pigeonhole version: v0.4.14 # Operating system: CentOS Linux release 7.2.1511 (Core) # CPU architecture: x86_64 # Dovecot -n output (I have filtered my IP addresses and mail server's FQDN): # 2.2.24 (a82c823): /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 0.4.14 (099a97c) # OS: Linux 3.10.0-327.18.2.el7.x86_64 x86_64 CentOS Linux release 7.2.1511 (Core) auth_default_realm = example.com base_dir = /var/run/dovecot/ default_login_user = vpopmail first_valid_uid = 500 info_log_path = /dev/stderr last_valid_uid = 500 lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes log_path = /dev/stderr mail_debug = yes mail_location = maildir:~/Maildir mail_max_userip_connections = 20 mail_plugins = " fts fts_lucene" 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 vnd.dovecot.pipe 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 = vpopmail } plugin { fts = lucene fts_autoindex = yes fts_lucene = whitespace_chars=@. sieve = file:~/sieve;active=~/.dovecot.sieve sieve_execute_socket_dir = sieve-execute sieve_extensions = +editheader +vnd.dovecot.pipe sieve_pipe_socket_dir = sieve-pipe sieve_plugins = sieve_extprograms } protocols = imap pop3 sieve service auth { unix_listener auth-userdb { group = vchkpw mode = 0666 user = vpopmail } } service imap-login { inet_listener imap { address = 127.0.0.1 port = 143 ssl = no } inet_listener imaps { address = 192.168.1.1 port = 993 ssl = yes } } service managesieve-login { inet_listener sieve { port = 4190 } } service pop3-login { inet_listener pop3 { address = 127.0.0.1 port = 110 ssl = no } inet_listener pop3s { address = 192.168.1.1 port = 995 ssl = yes } } service sieve-pipe-script { executable = script /usr/bin/echo group = dovenull user = dovenull } ssl_cert = </etc/ssl/certs/example.com.crt ssl_key = </etc/ssl/certs/example.com.key ssl_protocols = !SSLv2 !SSLv3 userdb { driver = vpopmail } verbose_proctitle = yes protocol lda { hostname = mail.example.com info_log_path = /var/log/dovecot/dovecot-lda.log log_path = /var/log/dovecot/dovecot-lda-errors.log mail_plugins = " fts fts_lucene sieve" postmaster_address = postmaster(a)example.com } protocol imap { mail_plugins = " fts fts_lucene imap_zlib" }

2 2

Marking an entire mailbox read
by ＠lbutlr 13 Jun '16

13 Jun '16

I have an archive mailbox that contains in excess of 100,000 mail messages (stored in maildir) that accidentally got marked as unread. It is too large for my mail client to select all the mail and mark it as read without throttling. Is there a simple way that I can use doveadm or something to simply mark every message in that maildir as read? Or do I just loop through every message and move it to <messaage>+S? find ~/Maildir/.Archive/cur/* -type f -name “1*:2” --exec mv {} {}S \; -- By the way, I think you might be the prettiest girl I've ever seen outside the pages of a really filthy magazine

2 2

sieve vacation script exclude based on sender email address
by Harondel J. Sibble 13 Jun '16

13 Jun '16

I thought I'd asked this question a few years ago but can't seem to find any eveidence of that so here goes. I've been looking at the sieve docs and recipes, done a lot of googling but no joy so far. Using stanard vacation script and that works great, however I want to exclude certain sender email addressess from ever receiving a vacation autoresponse, how do I go about adding that to my existing vacation recipe. I suspect my search terminology is what is causing me not to find anything as I typically am using exclude and similar search terms. -- Harondel J. Sibble Sibble Computer Consulting Ltd. Creating Solutions for the small and medium business computer user. harondel(a)pdscc.com (use pgp keyid 0x3CC3CFCE not 0x3AD5C11D) http://www.pdscc.com Blog: http://www.pdscc.com/blog (604) 739-3709 (voice)

2 3