- dovecot - dovecot.org

Lmtp logging, does not log
by Marc Roos 25 Nov '19

25 Nov '19

Looks like dovecot is not sending stuff to syslog anymore I am getting some message in /tmp/dovecot.log. However the lmtp log files are not even created. bash-5.0# doveconf | grep log_ auth_policy_log_only = no debug_log_path = deliver_log_format = msgid=%m: %$ doveadm_http_rawlog_dir = imapc_rawlog_dir = info_log_path = lmtp_proxy_rawlog_dir = /tmp/lmtp-proxy.log lmtp_rawlog_dir = /tmp/lmtp.log log_core_filter = log_debug = log_path = /tmp/dovecot.log log_timestamp = "%b %d %H:%M:%S " login_log_format = %$: %s login_log_format_elements = user=<%u> method=%m rip=%r lip=%l mpid=%e %c session=<%{session}> mail_index_log_rotate_max_size = 1 M mail_index_log_rotate_min_age = 5 mins mail_index_log_rotate_min_size = 32 k mail_index_rewrite_max_log_bytes = 128 k mail_index_rewrite_min_log_bytes = 8 k mail_log_prefix = "%s(%u)<%{pid}><%{session}>: " pop3c_rawlog_dir = rawlog_dir = submission_relay_rawlog_dir = syslog_facility = mail

1 0

proxy dual server setup clarification
by Marc Roos 25 Nov '19

25 Nov '19

I want to migrate mail users to a new environment. If I setup a new server next to the old server, and enable proxy on both. Is this then enough to migrate user by user with the passdb host=newsvr option to the new environment? Eg. I do not need to configure a director setup? I only need to enable proxy for imap and lmtp on both servers? (messages on the oldsvr will be proxied to the newsvr?)

2 2

Lmtp proxy help assertion failed: (conn->remote_port != 0
by Marc Roos 24 Nov '19

24 Nov '19

I have this in my 20-lmtp.conf file and created passdb-file, this should be enough to route a message to svr1? The port 24 is reachable from the proxy. bash-5.0# cat 20-lmtp.conf lmtp_proxy = yes protocol lmtp { # Space separated list of plugins to load (default is global mail_plugins). passdb { driver = passwd-file args = /etc/dovecot/special-passdb default_fields = proxy=y host=svr1 } } bash-5.0# cat /etc/dovecot/special-passdb test:password:1000:1000:(gecos):home:/bin/false:host=svr1

1 0

[Sieve] Multiple email recipients, how?
by Robert 24 Nov '19

24 Nov '19

Hi, First, I am very new to using Pigeonhole/Sieve with Dovecot and I am struggling with a problem which could be easy to solve but is just a lack of understanding on my end... We use a simple system for routing emails to different email users by postfixing the addresses with the actual user: xxxJohn@domain; yyyJohn@domain etc all will be delivered to user John. (This way John can invent a new email address on-the-fly and that will be delivered to his email box.) Delivering these emails to the right mailbox is easy: if address :contains "to" "John" ... All mail not matched will go to the general (catchall) mail box. The problem occurs when the email is sent to more addresses at the same domain. Eg. if an email is sent to xxxJohn@domain, zzzAlex@domain and info@domain Either, all emails also end up in the catch-all, or the email is delivered to the first matching rule only. I do not understand how to use the different TO addresses in the match rules. How can I determine that there are recipients other than xxxJohn or zzzAlex? Any help in pointing me in the right direction is appreciated! Robert

5 10

Virtual mailboxes: errors after renaming a folder
by André Rodier 24 Nov '19

24 Nov '19

Hello, I have a dovecot server, running fine, on Debian Stretch. Virtual folders are set up, and works correctly. For instance, I have Unread, All and Conversations, and everything works fine. However, when I rename a folder, I have error messages from Dovecot. For instance, I had a folder INBOX/Bills, which I renamed INBOX/Invoices. After that, I have these error messages: > The reported error was “Failed to select mailbox: Backend mailbox INBOX/Bills' added by another session. Reopen the virtual mailbox. (for backend mailbox Search/All) (0.000 + 0.000 secs).”. How can I avoid these errors, for instance, how can I rebuild the indexes every night or so? Kind regards, André

1 0

Dovecot proxy with ldap, complains about 'host not given'
by Marc Roos 24 Nov '19

24 Nov '19

It looks like the dovecot proxy can authenticate correctly but fails then on with this message Nov 23 23:33:33 test2 dovecot: pop3-login: Error: proxy: host not given: user=<test>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured, session=<LDTlHguYJth/AAAB> I have configured a host= in ldap for this user

3 4

chown(/var/dovecot/login/ipc-proxy
by Marc Roos 22 Nov '19

22 Nov '19

Can we remove/change this in the source? So we do not have to add the CAP_CHOWN with containers. chown(/var/dovecot/login/ipc-proxy) When run as root this has user dovenull, maybe this can be resolved by using a group dovenull? bash-5.0# ls -arlt total 4 srw-rw-rw- 1 root root 0 Nov 21 22:27 pop3 srw-rw-rw- 1 root root 0 Nov 21 22:27 login srw------- 1 dovenull root 0 Nov 21 22:27 ipc-proxy srw-rw-rw- 1 root root 0 Nov 21 22:27 imap drwxr-xr-x 1 dovecot dovecot 4096 Nov 21 22:27 .. drwxr-x--- 1 root dovenull 60 Nov 21 22:27 . Maybe this would work srw-rw---- 1 root dovenull 0 Nov 21 22:27 ipc-proxy

1 1

Virtual folder auto creation
by sergio 22 Nov '19

22 Nov '19

After switching on Virtual Plugin and configuring it as specified on https://doc.dovecot.org/configuration_manual/virtual_plugin/ the virtual folder is created for each user. Is it possible do not creater virtual folder automatically, only manually, for specific users? lda_mailbox_autocreate set to yes, but hope it's not related. -- sergio.

3 3

Lost quota, maildirsize with value S0
by grupodecorreo10 21 Nov '19

21 Nov '19

Hi,We have installed dovecot 2.2.22. we have servers as director dovecot and servers as dovecot backend. The mailboxes are estored in maildir format, over nfs (Emc Isilon).The problem we have is that sometimes some aleatory users loss her quota and the maildirsze show ilimited cuota, with S0 value in maildirsive file.The mails are stored in the mailboxes with maildrop and postfix, but we have done some test with postfix stoped. Only Dovecot openning the mailbox and the maildirsize is corrupted.I do not known where to look. We have configured dovecot with all the recomendarions for nfs.Thank you

1 0

virtual folder index logs
by sergio 21 Nov '19

21 Nov '19

A virtual folder is just really a saved search, but index log files are created. dovecot.list.index.log for the virtual folder itself and dovecot.index.log for all subfolders. Is it correct? Is it possible to disable index logs for virtual folder or it will only make dovecot worse? -- sergio.

1 0

Dovecot can't log in Virtual user - please help
by Andrej Rehak 20 Nov '19

20 Nov '19

Hello Im having issues login to dovecot using imap through telnet. Im running Linux 4.9.0-11-amd64 #1 SMP Debian 4.9.189-3+deb9u1 (2019-09-20) x86_64 GNU/Linux Im totally new to setting up mailservers. I havesetup a postfix for SMTP and it can receive emails. Postfix version is mail_version = 3.1.12 I have also installed Dovecot version:2.2.27 (c0f36b0) My configuration is such that POSTFIX is configured to use DOVECOT SASL through local socket. My system is configured to store emails in /var/mail/owndomain.org/<username>. For each domain i have my own passwd file where dovecot is supposed to lookup usernames and passwords. /var/mail/owndomain.org/passwd. I have created virtualuser for accessing mails and authenticating users. My dovecot (dovecot -n output) configuration is: ------------------------------------------------------------- # 2.2.27 (c0f36b0): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.16 (fed8554) # OS: Linux 4.9.0-11-amd64 x86_64 Debian 9.11 auth_debug = yes auth_mechanisms = plain login auth_verbose = yes debug_log_path = /var/log/dovecot-debug.log disable_plaintext_auth = no info_log_path = /var/log/dovecot-info.log listen = 192.168.2.2 log_path = /var/log/dovecot.log mail_home = /var/mail/home/%d/%n mail_location = mbox:~/mail:INBOX=/var/spool/mail/%d/%n mail_privileged_group = virtualmail 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 } passdb { args = username_format=%n /var/mail/%d/passwd driver = passwd-file } pop3_uidl_format = %g protocols = imap pop3 service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } user = dovecot } ssl = no userdb { driver = passwd } userdb { args = username_format=%n /var/mail/%d/passwd default_fields = uid=virtualmail gid=virtualmail home=/var/mail/%d/%n driver = passwd-file } verbose_proctitle = yes ---------------------------------------- Now the problem: I was testing the configuration using telnet. POSTFIX receives email, stores it. No problem. When i tried to log in onto Dovecot IMAP using Telnet i get this message: * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE AUTH=PLAIN AUTH-LOGIN] Dovecot ready. a login "username(a)owndomain.org" "test" a NO [UNAVAILABLE] Internal error occured. Refer to server log for more information. I have enabled verbose logging and this is the output of logs: /var/log/dovecot.log had this message: Nov 16 14:20:49 auth: Error: plain(username(a)owndomain.org,192.168.9.131,<RF4llXaXisPAqAmD>): user not found from any userdbs Nov 16 14:20:49 imap: Error: Authenticated user not found from userdb, auth lookup id=684589057 (client-pid=9601 client-id=1) /var/log/dovecot-debug.log had this message: Nov 16 14:20:18 auth: Debug: Loading modules from directory: /usr/lib/dovecot/modules/auth Nov 16 14:20:18 auth: Debug: Read auth token secret from /var/run/dovecot/auth-token-secret.dat Nov 16 14:20:18 auth: Debug: auth client connected (pid=9601) Nov 16 14:20:47 auth: Debug: client in: AUTH 1 PLAIN service=imap session=RF4llXaXisPAqAmD lip=192.168.2.2 rip=192.168.9.131 lport=143 rport=$ Nov 16 14:20:47 auth-worker(9603): Debug: Loading modules from directory: /usr/lib/dovecot/modules/auth Nov 16 14:20:47 auth-worker(9603): Debug: pam(username(a)owndomain.org,192.168.9.131,<RF4llXaXisPAqAmD>): lookup service=dovecot Nov 16 14:20:47 auth-worker(9603): Debug: pam(username(a)owndomain.org,192.168.9.131,<RF4llXaXisPAqAmD>): #1/1 style=1 msg=Password: Nov 16 14:20:49 auth: Debug: passwd-file /var/mail/owndomain.org/passwd: Read 2 users in 0 secs Nov 16 14:20:49 auth: Debug: passwd-file(username(a)owndomain.org,192.168.9.131,<RF4llXaXisPAqAmD>): lookup: user=username file=/var/mail/owndomain.org/passwd Nov 16 14:20:49 auth: Debug: client passdb out: OK 1 user=username(a)owndomain.org Nov 16 14:20:49 auth: Debug: master in: REQUEST 684589057 9601 1 a61dd67ee43390596ddf86e6c08db6f9 session_pid=9604 request_auth_token Nov 16 14:20:49 auth-worker(9603): Debug: passwd(username(a)owndomain.org,192.168.9.131,<RF4llXaXisPAqAmD>): lookup Nov 16 14:20:49 auth: Debug: passwd-file(username(a)owndomain.org,192.168.9.131,<RF4llXaXisPAqAmD>): lookup: user=username file=/var/mail/owndomain.org/passwd Nov 16 14:20:49 auth: Debug: master userdb out: NOTFOUND 684589057 And i am completelly clueless what is the problem. Because it seems as if the password was found but the user is not? Password and user are looked up in the same passwd file. Have i forgotten something to setup? Any help or guidance is appreciated! I have also posted the issue on: https://serverfault.com/questions/992108/dovecot-cant-login-virtual-user Thanks A.

2 3

ios12 clients not getting correct certificate, sni supported not? or config error?
by Marc Roos 20 Nov '19

20 Nov '19

I am having an ios12.4.1 client whine about access problems. He is getting the 'default' self signed ceritificate instead of the hostname alias. openssl s_client -servername mail.xxxxx.com -connect x.x.x.x:pop3s gives a 'Verify return code: 0 (ok)' I can't imagine this sni support is not available in recent versions. Should I remove this default certificate in the main section of 10-ssl.conf? These lines I have added to 10-ssl.conf ssl_cert = </etc/pki/tls/certs/mail-wildcard.crt ssl_key = </etc/pki/tls/private/mail-wildcard.key local 192.168.10.43 { ssl_key = </etc/pki/tls/private/xxxxxxx.local.key ssl_cert = </etc/pki/tls/certs/xxxxxxx.local.crt } local_name mail.xxxxx.com { ssl_key = </etc/pki/tls/private/mail.xxxxx.com.key ssl_cert = </etc/pki/tls/certs/mail.xxxxx.com.crt } local_name imap.xxxxxxx.net { ssl_key = </etc/pki/tls/private/imap.xxxxxxx.net.key ssl_cert = </etc/pki/tls/certs/imap.xxxxxxx.net.crt } [@ conf.d]# doveconf | egrep 'ssl_cert|ssl_key' ssl_cert = </etc/pki/tls/certs/mail-wildcard.crt ssl_cert_username_field = commonName ssl_key = # hidden, use -P to show it ssl_key_password = ssl_cert = </etc/pki/tls/certs/xxxxxxx.local.crt ssl_key = # hidden, use -P to show it ssl_cert = </etc/pki/tls/certs/mail.xxxxx.com.crt ssl_key = # hidden, use -P to show it ssl_cert = </etc/pki/tls/certs/imap.xxxxxxx.net.crt ssl_key = # hidden, use -P to show it

1 0

Error: Raw backtrace and index cache
by Maciej Milaszewski IQ PL 20 Nov '19

20 Nov '19

Hi I have "problem" with dovect 2.2.13 from repo debian8 and I don't know how to solve it ... Server is a virtual (kvm) with debian 8.11 (postfix + dovecot from repo) and storage is mounting via nfs (I have use only one dovecot with external storage) All works fine but sometime ( after a few hours ) I have got a problem with dovecot cache (i use indexes) logs -> http://paste.debian.net/1117072/ The store is mounted via nfs in /home/ index is local in /var/dovecot_indexes%h All go back to normal when i remove indexes like: find /var/dovecot_indexes/home/ -name 'dovecot*' -type f -delete but this is not good solution What am I doing wrong ? For tunning nfs in 10-mail.conf: --------- "mail_location = maildir:~/Maildir:INDEX=/var/dovecot_indexes%h namespace inbox { inbox = yes } mmap_disable = yes dotlock_use_excl = no mail_fsync = always mail_nfs_storage = no mail_nfs_index = no lock_method = fcntl mail_temp_dir = /tmp mail_plugins = quota expire notify mail_log mailbox_idle_check_interval = 30 secs mail_temp_scan_interval = 1w maildir_very_dirty_syncs = no ------------- doveconf -n # 2.2.13: /etc/dovecot/dovecot.conf # OS: Linux 3.16.0-9-amd64 x86_64 Debian 8.11 auth_mechanisms = plain login disable_plaintext_auth = no dotlock_use_excl = no lda_original_recipient_header = X-Original-To log_path = /var/log/dovecot/dovecot.mail133 mail_fsync = always mail_location = maildir:~/Maildir:INDEX=/var/dovecot_indexes%h mail_plugins = quota expire notify mail_log 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 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 = } passdb { driver = pam } 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 sieve = ~/dovecot.sieve sieve_default = /var/lib/dovecot/sieve/default.sieve sieve_dir = %h/sieve sieve_global_dir = /var/lib/dovecot/sieve/ } protocols = " imap lmtp sieve pop3" service auth { unix_listener auth-master { group = users mode = 0666 user = virtual } unix_listener auth-userdb { group = users user = virtual } } service lmtp { inet_listener lmtp { port = 24 } unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } user = virtual } service managesieve-login { inet_listener sieve { address = 127.0.0.1 94.124.15.58 port = 4190 } } ssl_ca = /etc/postfix/ssl/mail.maximail.pl.pem ssl_cert = </etc/postfix/ssl/mail.maximail.pl.pem ssl_key = </etc/postfix/ssl/mail.maximail.pl.key ssl_protocols = !SSLv2 !SSLv3 userdb { driver = passwd } userdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } protocol lmtp { info_log_path = /var/log/dovecot/dovecot.mali133 lmtp_save_to_detail_mailbox = yes mail_plugins = quota sieve notify push_notification } protocol lda { auth_socket_path = /var/run/dovecot/auth-master lda_mailbox_autocreate = yes log_path = /var/log/dovecot/dovecot-lda.mail133 mail_plugins = sieve postmaster_address = root }

2 4

Junk virtual forder
by sergio 20 Nov '19

20 Nov '19

Is it possible to create a virtual folder that selects all mails with imap Junk flag (set by pigeonhole imap4flags' setflag "Junk")? -- sergio.

3 4

Doveadm replicator ssl issues
by Miro Igov 20 Nov '19

20 Nov '19

Hello, I have 2 Dovecot 2.3.8 servers running SSL with valid wildcard certificates. Email clients connect fine, https://www.immuniweb.com/ssl/ tests show certificates are ok. However I can't make replication work when I add ssl = yes. Without ssl it works ok. I added verbose_ssl in config and error log shows: dovecot: doveadm(149.x.x.x): Error: SSL handshake failed: SSL_accept() failed: error:140760FC:SSL routines:SSL23_GET_CLIENT_HELLO:unknown protocol >From the other server 149.x.x.x I tested with openssl: openssl s_client -connect 188.x.x.x:12333 -crlf -CAfile /etc/pki/tls/cert.pem CONNECTED(00000003) depth=2 C = US, ST = New Jersey, L = Jersey City, O = The USERTRUST Network, CN = USERTrust RSA Certification Authority verify return:1 depth=1 C = GB, ST = Greater Manchester, L = Salford, O = Sectigo Limited, CN = Sectigo RSA Organization Validation Secure Server CA verify return:1 depth=0 C = FR, postalCode = 34980, ST = Occitanie, L = Montpellier, street = 123 Main str, O = My Company, OU = PremiumSSL Wildcard, CN = *.domain.com verify return:1 . . SSL-Session: Protocol : TLSv1.2 Cipher : ECDHE-RSA-AES256-SHA384 Session-ID: 95CF7F07702A50CB7CDC5D478986B5A4682EA945C487E770550EE48BFEA53EBC Session-ID-ctx: Master-Key: ECC14F2EE03C04474992A651B3695D78A27A0B07529DB35F61F6FB5F5A5D51395432BDFF37F2 41BD4B3C4B9E1AB6A929 Key-Arg : None Krb5 Principal: None PSK identity: None PSK identity hint: None Start Time: 1574108251 Timeout : 300 (sec) Verify return code: 0 (ok) The configuration of the 2 servers below. 188.x.x.x # 2.3.8 (9df20d2db): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.8 (b7b03ba2) # OS: Linux 2.6.32-754.6.3.el6.x86_64 x86_64 CentOS release 6.10 (Final) # Hostname: login.domain.com default_vsz_limit = 512 M doveadm_password = # hidden, use -P to show it mail_plugins = " notify replication" managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date index ihave duplicate mime foreverypart extracttext mbox_write_locks = fcntl namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { driver = pam } plugin { mail_replica = tcp:149.x.x.x:12333 sieve = file:~/sieve;active=~/.dovecot.sieve } protocols = imap pop3 replication_full_sync_interval = 10 mins service aggregator { fifo_listener replication-notify-fifo { mode = 0666 } unix_listener replication-notify { mode = 0666 } } service doveadm { inet_listener { port = 12333 ssl = yes } } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { mode = 0666 } } ssl_cert = </etc/dovecot/ssl_chain.pem ssl_cipher_list = ECDHE-RSA-AES256-SHA384:AES256-SHA256:AES256-SHA256:HIGH:MEDIUM:+TLSv1:+TLSv 1.1:+TLSv1.2:!RC4:!IDEA:!3DES:!MD5:!ADH:!aNULL:!eNULL:!NULL:!DH:!ADH:!EDH:!A ESGCM:!CAMELLIA:!SEED ssl_client_ca_file = /etc/pki/tls/cert.pem ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it userdb { driver = passwd } verbose_ssl = yes local 91.x.x.x { protocol imap { ssl_cert = </etc/dovecot/ssl_chain.pem ssl_key = # hidden, use -P to show it } } local 91.x.x.x { protocol pop3 { ssl_cert = </etc/dovecot/ssl_chain.pem ssl_key = # hidden, use -P to show it } } 149.x.x.x # 2.3.8 (9df20d2db): /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-754.6.3.el6.x86_64 x86_64 CentOS release 6.10 (Final) # Hostname: prime.domain.com auth_mechanisms = plain login default_vsz_limit = 1 G disable_plaintext_auth = no doveadm_password = # hidden, use -P to show it mail_location = maildir:~/Maildir mail_plugins = " notify replication" mbox_write_locks = fcntl namespace inbox { inbox = yes location = mailbox Archive { auto = subscribe special_use = \Archive } mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Spam { auto = subscribe special_use = \Junk } mailbox Trash { special_use = \Trash } prefix = } passdb { args = session=yes setcred=yes failure_show_msg=yes dovecot driver = pam } plugin { mail_replica = tcp:188.x.x.x:12333 } protocols = imap pop3 replication_full_sync_interval = 10 mins replication_max_conns = 11 service aggregator { fifo_listener replication-notify-fifo { mode = 0666 } unix_listener replication-notify { mode = 0666 } } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } } service doveadm { inet_listener { port = 12333 ssl = yes } } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { mode = 0666 } } ssl_cert = </etc/dovecot/ssl_chain.pem ssl_cipher_list = ECDHE-RSA-AES256-SHA384:AES256-SHA256:AES256-SHA256:HIGH:MEDIUM:+TLSv1:+TLSv 1.1:+TLSv1.2:!RC4:!IDEA:!3DES:!MD5:!ADH:!aNULL:!eNULL:!NULL:!DH:!ADH:!EDH:!A ESGCM:!CAMELLIA:!SEED ssl_client_ca_file = /etc/pki/tls/cert.pem ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it userdb { driver = passwd } protocol imap { mail_max_userip_connections = 50 } protocol pop3 { pop3_uidl_format = %08Xu%08Xv } local 178.x.x.x { protocol imap { ssl_cert = </etc/dovecot/ssl_chain.pem ssl_key = # hidden, use -P to show it } } local 178.x.x.x { protocol pop3 { ssl_cert = </etc/dovecot/ssl_chain.pem ssl_key = # hidden, use -P to show it } } Your help will be great appreciated.

2 2

[SOLVED] Doveadm replicator ssl issues
by Miro Igov 20 Nov '19

20 Nov '19

Solved, thank you. TCPS was the issue. From: Aki Tuomi <aki.tuomi(a)open-xchange.com> Sent: Wednesday, November 20, 2019 08:54 To: Miro Igov <miro.igov(a)gmail.com>; dovecot(a)dovecot.org Subject: Re: Doveadm replicator ssl issues On 18.11.2019 22.30, Miro Igov via dovecot wrote: Hello, I have 2 Dovecot 2.3.8 servers running SSL with valid wildcard certificates. Email clients connect fine, https://www.immuniweb.com/ssl/ tests show certificates are ok. However I can't make replication work when I add ssl = yes. Without ssl it works ok. I added verbose_ssl in config and error log shows: dovecot: doveadm(149.x.x.x): Error: SSL handshake failed: SSL_accept() failed: error:140760FC:SSL routines:SSL23_GET_CLIENT_HELLO:unknown protocol >From the other server 149.x.x.x I tested with openssl: openssl s_client -connect 188.x.x.x:12333 -crlf -CAfile /etc/pki/tls/cert.pem CONNECTED(00000003) depth=2 C = US, ST = New Jersey, L = Jersey City, O = The USERTRUST Network, CN = USERTrust RSA Certification Authority verify return:1 depth=1 C = GB, ST = Greater Manchester, L = Salford, O = Sectigo Limited, CN = Sectigo RSA Organization Validation Secure Server CA verify return:1 depth=0 C = FR, postalCode = 34980, ST = Occitanie, L = Montpellier, street = 123 Main str, O = My Company, OU = PremiumSSL Wildcard, CN = *.domain.com verify return:1 . . SSL-Session: Protocol : TLSv1.2 Cipher : ECDHE-RSA-AES256-SHA384 Session-ID: 95CF7F07702A50CB7CDC5D478986B5A4682EA945C487E770550EE48BFEA53EBC Session-ID-ctx: Master-Key: ECC14F2EE03C04474992A651B3695D78A27A0B07529DB35F61F6FB5F5A5D51395432BDFF37F2 41BD4B3C4B9E1AB6A929 Key-Arg : None Krb5 Principal: None PSK identity: None PSK identity hint: None Start Time: 1574108251 Timeout : 300 (sec) Verify return code: 0 (ok) The configuration of the 2 servers below. 188.x.x.x # 2.3.8 (9df20d2db): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.8 (b7b03ba2) # OS: Linux 2.6.32-754.6.3.el6.x86_64 x86_64 CentOS release 6.10 (Final) # Hostname: login.domain.com default_vsz_limit = 512 M doveadm_password = # hidden, use -P to show it mail_plugins = " notify replication" managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date index ihave duplicate mime foreverypart extracttext mbox_write_locks = fcntl namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { driver = pam } plugin { mail_replica = tcp:149.x.x.x:12333 sieve = file:~/sieve;active=~/.dovecot.sieve <file://~/sieve;active=~/.dovecot.sieve> } protocols = imap pop3 replication_full_sync_interval = 10 mins service aggregator { fifo_listener replication-notify-fifo { mode = 0666 } unix_listener replication-notify { mode = 0666 } } service doveadm { inet_listener { port = 12333 ssl = yes } } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { mode = 0666 } } ssl_cert = </etc/dovecot/ssl_chain.pem ssl_cipher_list = ECDHE-RSA-AES256-SHA384:AES256-SHA256:AES256-SHA256:HIGH:MEDIUM:+TLSv1:+TLSv 1.1:+TLSv1.2:!RC4:!IDEA:!3DES:!MD5:!ADH:!aNULL:!eNULL:!NULL:!DH:!ADH:!EDH:!A ESGCM:!CAMELLIA:!SEED ssl_client_ca_file = /etc/pki/tls/cert.pem ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it userdb { driver = passwd } verbose_ssl = yes local 91.x.x.x { protocol imap { ssl_cert = </etc/dovecot/ssl_chain.pem ssl_key = # hidden, use -P to show it } } local 91.x.x.x { protocol pop3 { ssl_cert = </etc/dovecot/ssl_chain.pem ssl_key = # hidden, use -P to show it } } 149.x.x.x # 2.3.8 (9df20d2db): /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-754.6.3.el6.x86_64 x86_64 CentOS release 6.10 (Final) # Hostname: prime.domain.com auth_mechanisms = plain login default_vsz_limit = 1 G disable_plaintext_auth = no doveadm_password = # hidden, use -P to show it mail_location = maildir:~/Maildir mail_plugins = " notify replication" mbox_write_locks = fcntl namespace inbox { inbox = yes location = mailbox Archive { auto = subscribe special_use = \Archive } mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Spam { auto = subscribe special_use = \Junk } mailbox Trash { special_use = \Trash } prefix = } passdb { args = session=yes setcred=yes failure_show_msg=yes dovecot driver = pam } plugin { mail_replica = tcp:188.x.x.x:12333 } protocols = imap pop3 replication_full_sync_interval = 10 mins replication_max_conns = 11 service aggregator { fifo_listener replication-notify-fifo { mode = 0666 } unix_listener replication-notify { mode = 0666 } } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } } service doveadm { inet_listener { port = 12333 ssl = yes } } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { mode = 0666 } } ssl_cert = </etc/dovecot/ssl_chain.pem ssl_cipher_list = ECDHE-RSA-AES256-SHA384:AES256-SHA256:AES256-SHA256:HIGH:MEDIUM:+TLSv1:+TLSv 1.1:+TLSv1.2:!RC4:!IDEA:!3DES:!MD5:!ADH:!aNULL:!eNULL:!NULL:!DH:!ADH:!EDH:!A ESGCM:!CAMELLIA:!SEED ssl_client_ca_file = /etc/pki/tls/cert.pem ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it userdb { driver = passwd } protocol imap { mail_max_userip_connections = 50 } protocol pop3 { pop3_uidl_format = %08Xu%08Xv } local 178.x.x.x { protocol imap { ssl_cert = </etc/dovecot/ssl_chain.pem ssl_key = # hidden, use -P to show it } } local 178.x.x.x { protocol pop3 { ssl_cert = </etc/dovecot/ssl_chain.pem ssl_key = # hidden, use -P to show it } } Hi! You need to use tcps in mail_replica. Aki

1 0

[SOLVED] Doveadm replicator ssl issues
by Miro Igov 20 Nov '19

20 Nov '19

Solved, thank you! TCPS was the problem. Hi! You need to use tcps in mail_replica. Aki

1 0

http API for IMAP
by Thomas Güttler 20 Nov '19

20 Nov '19

10 22

Panic: file smtp-client-connection.c: line 1142 (smtp_client_connection_established)
by Dirk 20 Nov '19

20 Nov '19

I'm using dovecot in a multi server setup. Two directors forward pop3, imap and smtp to backend dovecots with their central storage on NFS. Yesterday I stumbled upon these log lines: 2019-11-18 20:17:51 lmtp(17274): Info: Connect from 172.22.1.6 2019-11-18 20:17:51 lmtp(17274): Panic: file smtp-client-connection.c: line 1142 (smtp_client_connection_established): assertion failed: (!conn->connect_succeeded) 2019-11-18 20:17:51 lmtp(17274): Fatal: master: service(lmtp): child 17274 killed with signal 6 (core not dumped - https://dovecot.org/bugreport.html#coredumps - set /proc/sys/fs/suid_dumpable to 2) Is a core dump required to find the source of that error? Thanks for any help! $ doveconf -n # 2.3.4.1 (f79e8e7e4): /etc/dovecot/dovecot.conf # OS: Linux 4.9.0-8-amd64 x86_64 # Hostname: m03.company.com auth_cache_negative_ttl = 65 secs auth_cache_ttl = 3 mins auth_cache_verify_password_with_worker = yes auth_mechanisms = plain login auth_verbose = yes debug_log_path = /dev/stdout default_client_limit = 10400 default_process_limit = 1024 default_vsz_limit = 1 G deliver_log_format = msgid=%m: %s %{session_time} %$ director_mail_servers = 10.10.10.2 10.10.10.3 director_servers = 10.10.1.2 10.10.1.3 imap_id_log = * imap_max_line_length = 2 M import_environment = TZ CORE_OUTOFMEM CORE_ERROR info_log_path = /dev/stdout instance_name = dovecot_director listen = 10.10.1.3,:: lmtp_proxy = yes log_path = /dev/stderr log_timestamp = "%Y-%m-%d %H:%M:%S " login_log_format_elements = user=<%u> method=%m rip=%r lip=%l mpid=%e %c %k session=<%{session}> mail_max_userip_connections = 250 passdb { args = /etc/dovecot/sql/dovecot-dict-sql-passdb.conf driver = sql result_failure = return-fail result_internalfail = return-fail result_success = continue-ok } passdb { args = proxy=y starttls=any-cert master=director(a)m03.company.com pass=#hidden_use-P_to_show# nopassword=y driver = static skip = unauthenticated } pop3_logout_format = top=%t/%p, retr=%r/%b, del=%d/%m, size=%s, uidl=%u protocols = imap lmtp pop3 service auth-worker { user = $default_internal_user } service director { fifo_listener login/proxy-notify { mode = 0600 user = $default_login_user } inet_listener { port = 9090 } unix_listener director-userdb { mode = 0600 user = vmail } unix_listener login/director { mode = 0666 } } service imap-login { executable = imap-login director process_min_avail = 2 vsz_limit = 1 G } service lmtp { inet_listener lmtp { port = 24 } process_min_avail = 2 unix_listener lmtp { mode = 00 } user = vmail vsz_limit = 1 G } service log { user = dovenull } service pop3-login { executable = pop3-login director process_min_avail = 2 vsz_limit = 1 G } service pop3 { user = vmail } ssl_cert = </etc/ssl/mail/cert.pem ssl_client_ca_dir = /etc/ssl/certs/ ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it ssl_prefer_server_ciphers = yes submission_host = postfix:588 protocol lmtp { auth_socket_path = director-userdb }

2 1

Sieve and recipient_delimiter
by ＠lbutlr 17 Nov '19

17 Nov '19

I use recipient_delimiter addresseses quiet a bit, and I want to put several of them into a mailbox if anyof (header :contains ["to"] [ “FOO", “foo", “bar", “florin"]) { fileinto :create “later"; stop; } When I get an email addressed to me+FOO(a)example.com or me_florin(a)example.com, the messages end up in my inbox (Yes, I have both + and _ defined as delimiters in postfix and in dovecot). Is this because sieve is not seeing the delimiter? I am wondering this because I have another rule that seems to be working fine that is largely the same, but operates on domains: if anyof ( header :contains ["From"] [“kreme.com", “localdomain1.tld”, "localdomain2.tld", "localdomain3.tld", “covisp.net” ]){ fileinto :create "priority"; } -- She'd always tried to face towards the light. But the harder you stared into the brightness the harsher it burned into you until, at last, the temptation picked you up and bid you turn around to see how long, rich, strong and dark, streaming away behind you, your shadow had become- --Carpe Jugulum

2 2

Auto expunge log
by Michael Ludwig 16 Nov '19

16 Nov '19

Hi, I'm just setting up a new dovecot system and wonder why I get this error. On another dovecot system this works with no problems. Log entry when exiting MUA Thunderbird: =========================== Nov 16 20:16:35 myhostname dovecot: imap(info(a)mydomain.de): Error: autoexpunge: Couldn't create dovecot.autoexpunge.lock lock: file_create_locked(/var/mail/vmail/mydomain.de/info//dovecot.autoexpunge.lock) failed: safe_mkstemp(/var/mail/vmail/mydomain.de/info//dovecot.autoexpunge.lock) failed: No such file or directory =========================== Is this double slash between /info//dovecot.auto... okay? I believe there should be a "Mailbox" in between? Configuration in /etc/dovecot/conf.d/15-mailboxed.conf =========================== namespace inbox { mailbox Junk { auto = subscribe special_use = \Junk autoexpunge = 90d } =========================== Maybe you can help me a bit. ;-) Michael

2 1

Feature request: ssl-cert config
by Marc Roos 16 Nov '19

16 Nov '19

I am not sure why this </ is used in the configuration. But I hoped it would concatenate the ssl_cert to have multiple certificates. So one could use it multiple times, as needed. It would be nice to be able to specify the intermediate certificate (bundle) separate from the certificate, so when updating the certificate I just have to replace this file. Something like local_name mail.xxxxxx.xxx { ssl_key = </etc/pki/tls/private/mail.xxxxxx.xxx.key ssl_cert = </etc/pki/tls/certs/mail.xxxxxx.xxx.crt ssl_cert = </etc/pki/tls/certs/SectigoIntermediate.crt } Or local_name mail.xxxxxx.xxx { ssl_key = </etc/pki/tls/private/mail.xxxxxx.xxx.key ssl_cert = </etc/pki/tls/certs/mail.xxxxxx.xxx.crt ssl_int = </etc/pki/tls/certs/SectigoIntermediate.crt } dovecot-2.2.36-3.el7_7.1.x86_64

1 0

SCRAM-SHA-1-PLUS / SCRAM-SHA-224(-PLUS) / SCRAM-SHA-256(-PLUS), SCRAM-SHA-384(-PLUS) and SCRAM-SHA-512(-PLUS) supports
by - Neustradamus - 15 Nov '19

15 Nov '19

Dear all, I send you a new email to know what is the progress of SCRAM-SHA-***(-PLUS) supports? Currently there is only SCRAM-SHA-1: https://doc.dovecot.org/configuration_manual/authentication/password_scheme…. - RFC6331: Moving DIGEST-MD5 to Historic: https://tools.ietf.org/html/rfc6331 - RFC5802: Salted Challenge Response Authentication Mechanism (SCRAM) SASL and GSS-API Mechanisms: https://tools.ietf.org/html/rfc5802 - RFC7677: SCRAM-SHA-256 and SCRAM-SHA-256-PLUS Simple Authentication and Security Layer (SASL) Mechanisms: https://tools.ietf.org/html/rfc7677 - since 2015-11-02 I have seen several months ago, commits about SCRAM-SHA-256. For your information, Cyrus SASL supports: - SCRAM-SHA-1(-PLUS) - SCRAM-SHA-224(-PLUS) - SCRAM-SHA-256(-PLUS) - SCRAM-SHA-384(-PLUS) - SCRAM-SHA-512(-PLUS) -> https://cyrusimap.org/sasl/sasl/authentication_mechanisms.html You can see more and more informations here: https://github.com/scram-xmpp/info/issues/1 Thanks in advance. Regards, Neustradamus

1 0

ACL's with SQL/from mysql table
by Jorge Bastos 15 Nov '19

15 Nov '19

Howdy, Would someone point me to a good howto on how to implement ACL from an sql table? Thanks in advanced,

1 0

IMAP4 extensions for Visual Voicemail (VVM)
by Rajesh Bansal 15 Nov '19

15 Nov '19

Hi Team, I need to develop Visual VoiceMail solution. In this solution I need a IMAP4 server, from which I can get a hit for each mail retrieval. Can anyone help me if dovecot can be used for this purpose. BR, Rajesh Bansal

5 5

SASL AUTH with postfix
by Jorge Bastos 15 Nov '19

15 Nov '19

Hi, I just moved from Cyrus SASL to Dovecot SASL, with postfix. Works great, and no issue with non-ascii chars, has i had with Cyrus. With Cyrus i was getting the username/passwd via SQL, with this: sql_select: select password from smtp_auth_users where username='%u@%r' and status='true' worked ok for users with email addresses, and i had some special users that were just a name, like "user-1", and i was able to AUTH it. Postfix had: smtpd_sasl_local_domain = fastmail and in the database i had the username in the format: user-1@fastmail and worked ok. How can i have the same with dovecot SASL? Thanks in advanced,

3 7

Crash when moving mail from Inbox to Trash
by marvin alcantara 14 Nov '19

14 Nov '19

Hi, I am developing a dovecot plugin, and inside my plugin I am implementing my own expunge function. Inside my function, I am calling the following lines of code: if (storage->v.mail_open(mail, &offset, &mail->open_file) < 0) return -1; The mail_open virtual function is an invalid address. The storage should be mdbox however, it seems that it didn't get the correct mdbox_mail_open of mdbox-storage. Do you have any suggestions as to why this is happening? dovecot version:2.3.7 (a3d493f) Sincerely,Marvin

1 0

RFC 5258 violation: incomplete response for "LIST ($OPT RECURSIVEMATCH) ..."
by Guilhem Moulin 12 Nov '19

12 Nov '19

Hi there, RFC 5258 (IMAP4 LIST command extensions) defines a ‘RECURSIVEMATCH’ selection option which “forces the server to return information about parent mailboxes that don't match other selection options, but have some submailboxes that do.” (Section 3.5 makes the requirement even clearer.) However that's not what Dovecot 2.3.7 does. AFAICT no LIST response is returned for mailboxes that don't meet the selection criteria, regardless of whether they have a child that does. The violation is visible when reproducing example #9 from Section 5 [0]: $ env -i USER=user HOME=/dev/shm/dovecot-test/user PATH=/usr/bin:/bin \ doveadm -c /tmp/dovecot.conf mailbox create foo2 baz2 $ env -i USER=user HOME=/dev/shm/dovecot-test/user PATH=/usr/bin:/bin \ doveadm -c /tmp/dovecot.conf mailbox create -s \ foo2/{bar1,bar2} baz2/{bar2,bar22,bar222} eps2 eps2/mamba qux2/bar2 $ env -i USER=user HOME=/dev/shm/dovecot-test/user PATH=/usr/bin:/bin \ doveadm -c /tmp/dovecot.conf exec imap S: * PREAUTH [CAPABILITY IMAP4rev1 … LIST-EXTENDED …] Logged in as user C: D01 LIST "" "*" S: * LIST (\Noselect \HasChildren) "/" qux2 S: * LIST (\HasNoChildren) "/" qux2/bar2 S: * LIST (\HasChildren) "/" eps2 S: * LIST (\HasNoChildren) "/" eps2/mamba S: * LIST (\HasChildren) "/" baz2 S: * LIST (\HasNoChildren) "/" baz2/bar222 S: * LIST (\HasNoChildren) "/" baz2/bar22 S: * LIST (\HasNoChildren) "/" baz2/bar2 S: * LIST (\HasChildren) "/" foo2 S: * LIST (\HasNoChildren) "/" foo2/bar2 S: * LIST (\HasNoChildren) "/" foo2/bar1 S: * LIST (\HasNoChildren) "/" INBOX S: D01 OK List completed (0.006 + 0.000 + 0.005 secs). C: D02 LIST (SUBSCRIBED) "" "*" S: * LIST (\Subscribed) "/" foo2/bar1 S: * LIST (\Subscribed) "/" foo2/bar2 S: * LIST (\Subscribed) "/" baz2/bar2 S: * LIST (\Subscribed) "/" baz2/bar22 S: * LIST (\Subscribed) "/" baz2/bar222 S: * LIST (\Subscribed) "/" eps2 S: * LIST (\Subscribed) "/" eps2/mamba S: * LIST (\Subscribed) "/" qux2/bar2 S: D02 OK List completed (0.001 + 0.000 secs). A LIST command with ‘RECURSIVEMATCH SUBSCRIBED’ selection options produces an incomplete response: C: D03 LIST (RECURSIVEMATCH SUBSCRIBED) "" "*" S: * LIST (\Subscribed) "/" foo2/bar1 S: * LIST (\Subscribed) "/" foo2/bar2 S: * LIST (\Subscribed) "/" baz2/bar2 S: * LIST (\Subscribed) "/" baz2/bar22 S: * LIST (\Subscribed) "/" baz2/bar222 S: * LIST (\Subscribed) "/" eps2 (CHILDINFO ("SUBSCRIBED")) S: * LIST (\Subscribed) "/" eps2/mamba S: * LIST (\Subscribed) "/" qux2/bar2 S: D03 OK List completed (0.001 + 0.000 secs). The following untagged LIST responses for ‘foo2’ and ‘baz2’ are missing. RFC 5258 mandates their inclusion because even though they're not subscribed to themselves, they each have (at least) a subscribed child. S: * LIST () "/" "foo2" ("CHILDINFO" ("SUBSCRIBED")) S: * LIST () "/" "baz2" ("CHILDINFO" ("SUBSCRIBED")) Cheers, -- Guilhem. [0] https://tools.ietf.org/html/rfc5258#section-5

1 0

How to send a test message directly to lmtp, to test proxying
by Marc Roos 12 Nov '19

12 Nov '19

How to send a test message directly to lmtp, to test proxying?

2 2

Howto pin user in proxy/director <-> backend server setup
by Marc Roos 12 Nov '19

12 Nov '19

I have 1x proxy/director server 2x backend mail server The backend servers are using a ldap database and do not have the option to put a proxy=y value. So I put this as a default in the passdb option in the proxy/director config. When I do telnet localhost 110 on the proxy/director, I can authenticate with a test account on svr1.local 1. Will automatically all users be directed to the first server configured in director_mail_servers = svr1.local svr2.local, when the do not have a proxy=y or host=? If this is the case maybe, we should write this somewhere on https://wiki2.dovecot.org/Director https://doc.dovecot.org/configuration_manual/authentication/proxies/ 2. If I change the host= in the ldap server, I think the proxy/director has archived the previous host and still redirects to the old value. Is there a way around this? (stopping/starting dovecot -F resolves this) 3. Do I need the director even in this setup?

1 0

[SOLVED] dovecot -2.2.24 on Fedora 31
by Frank Elsner 12 Nov '19

12 Nov '19

Hello Aki, thanks for your patience and help. I solved my problems by compiling dovecot-2.3.8 and following the migration hints I got it working. Happy, Frank

1 0

postfix + spamassassin + dovecot-lda (with sieve support)
by Дмитрий До лженко 12 Nov '19

12 Nov '19

Hello, I have FreeBSD 12 server with postfix + spamassassin. Old config work fine. ------ old postfix master.cf spamfilter unix - n n - - pipe flags=R user=nobody argv=/usr/local/bin/spamc -e /usr/sbin/sendmail -oi -f ${sender} ${recipient} ------ I try to add dovecot-lda (with sieve support) as local delivery agent to postfix config ----------- postfix master.cf # Spamd filter spamfilter unix - n n - - pipe flags=DRhu user=nobody argv=/usr/local/bin/spamc -e /usr/local/libexec/dovecot/dovecot-lda -f ${sender} -d ${recipient} ----------- Test mail is bounced with report - --------- If you do so, please include this problem report. You can delete your own text from the attached returned message. The mail system <dol(a)mig.hys.msu.ru>: user unknown --------- /var/log/maillog Nov 11 22:40:49 mig postfix/smtpd[55978]: disconnect from acs366.hys.msu.ru[93.10.51.14] ehlo=1 mail=1 rcpt=1 data=1 quit=1 commands=5 Nov 11 22:40:49 mig dovecot[64447]: auth-worker(55751): passwd(dol(a)mig.hys.msu.ru): unknown user System user dol exist, but LDA try to deliver to dol(a)mig.hys.msu.ru Please, help me to solve this problem. I need to serve IMAP and POP3 clients with delivery to /var/mail/username mailboxes if no user sieve rules exists. Best regards, Dmitry.

2 1

dovecot -2.2.24 on Fedora 31
by Frank Elsner 12 Nov '19

12 Nov '19

Hi, I try to compile dovecot -2.2.24 on Fedora 31 and get the following error: iostream-openssl.c: In function ‘openssl_iostream_verify_client_cert’: iostream-openssl.c:118:37: error: dereferencing pointer to incomplete type ‘X509_STORE_CTX’ {aka ‘struct x509_store_ctx_st’} 118 | subject = X509_get_subject_name(ctx->current_cert); | ^~ make[3]: *** [Makefile:561: iostream-openssl.lo] Error 1 All openssl packages installed. What's the reason and how solve the problem? Kind regards, Frank Elsner

2 8

Login/director not created
by Marc Roos 11 Nov '19

11 Nov '19

I have this[0] config, yet the /var/run/dovecot/login/director is not created, what to check in the config? dovecot: imap-login: Error: auth: connect(director) failed: No such file or directory [0] service director { unix_listener login/director { #mode = 0666 } fifo_listener login/proxy-notify { #mode = 0666 } unix_listener director-userdb { #mode = 0600 } inet_listener { #port = } }

2 4

gssapi without passdb
by David Wells 11 Nov '19

11 Nov '19

Good afternoon. I'm configuring dovecot to authenticate users against a samba server running as an active directory domain controller. I followed the instructions as stated in the page https://wiki.dovecot.org/Authentication/Kerberos and considering the sentence that states [...]The Kerberos authentication mechanism doesn't require having a passdb, but you do need a userdb[...] I produced a configuration file that looked like this > auth_gssapi_hostname = $ALL > auth_krb5_keytab = /etc/dovecot/dovecot.keytab > auth_mechanisms = gssapi > auth_username_format = %u > mail_location = > maildir:~/Maildir:INDEX=/var/lib/dovecot/%d/%n:CONTROL=/var/lib/dovecot/%d/%n:UTF-8 > managesieve_notify_capability = mailto > managesieve_sieve_capability = fileinto reject envelope > encoded-character vacation subaddress comparator-i;ascii-numeric > relational regex imap4flags copy include variables body enotify > environment mailbox date index ihave duplicate mime foreverypart > extracttext > namespace inbox { > inbox = yes > location = > mailbox Drafts { > special_use = \Drafts > } > mailbox Junk { > special_use = \Junk > } > mailbox Sent { > special_use = \Sent > } > mailbox "Sent Messages" { > special_use = \Sent > } > mailbox Trash { > special_use = \Trash > } > prefix = > } > plugin { > sieve = file:~/sieve;active=~/.dovecot.sieve > } > protocols = imap > ssl_ca = /etc/ssl/certs/cacertificate.crt > ssl_cert = </etc/ssl/certs/certificate.crt > ssl_key = # hidden, use -P to show it > userdb { > args = uid=vmail gid=vmail home=/var/vmail/%d/%n allow_all_users=yes > driver = static > } When I ran these settings I would get an error that read > Nov 8 17:00:00 mail dovecot: auth: Error: > gssapi(user(a)KERBEROSPRINCIPAL,192.168.182.137,<IQMcOtuWI+3AqLaJ>): All > password databases were skipped > Nov 8 17:00:02 mail dovecot: imap-login: Disconnected (auth service > reported temporary failure): user=<user@KERBEROSPRINCIPAL>, > method=GSSAPI, rip=192.168.182.137, lip=192.168.182.4, TLS, > session=<IQMcOtuWI+3AqLaJ> After Trying many things I finally modified my config > auth_gssapi_hostname = $ALL > auth_krb5_keytab = /etc/dovecot/dovecot.keytab > auth_mechanisms = gssapi > auth_username_format = %u > mail_location = > maildir:~/Maildir:INDEX=/var/lib/dovecot/%d/%n:CONTROL=/var/lib/dovecot/%d/%n:UTF-8 > managesieve_notify_capability = mailto > managesieve_sieve_capability = fileinto reject envelope > encoded-character vacation subaddress comparator-i;ascii-numeric > relational regex imap4flags copy include variables body enotify > environment mailbox date index ihave duplicate mime foreverypart > extracttext > namespace inbox { > inbox = yes > location = > mailbox Drafts { > special_use = \Drafts > } > mailbox Junk { > special_use = \Junk > } > mailbox Sent { > special_use = \Sent > } > mailbox "Sent Messages" { > special_use = \Sent > } > mailbox Trash { > special_use = \Trash > } > prefix = > } > passdb { > args = /etc/dovecot/dovecot-ldap.conf.ext > driver = ldap > } > plugin { > sieve = file:~/sieve;active=~/.dovecot.sieve > } > protocols = imap > ssl_ca = /etc/ssl/certs/cacertificate.crt > ssl_cert = </etc/ssl/certs/certificate.crt > ssl_key = # hidden, use -P to show it > userdb { > args = uid=vmail gid=vmail home=/var/vmail/%d/%n allow_all_users=yes > driver = static > } The dovecot-ldap.conf.ext file looks like this > hosts = dc1:3268 > tls = yes > auth_bind = yes > auth_bind_userdn = %u > base = With this configuration I can authenticate to the imap server sending user@KERBEROSPRINCIPAL as my username and without setting a password so I'm wondering if the wiki page needs to be updated or if there is something wrong with my first setup. Thanks in advance. Best regards, David Wells.

2 1

Sieve vacation :addresses match only case-sensitive?
by Philipp Faeustlin 11 Nov '19

11 Nov '19

The recipients in the vacation :addresses String list are matched case-sensitive. If the recipient gets a mail with wrong case, the message is discarded with: "discarding vacation response for implicitly delivered message; no known (envelope) recipient address found in message headers" I think the matching should be case-insensitive. Is this a bug or do I miss some option? I'm using Dovecot 2.3.7.2, Pigeonhole version 0.5.7.2. -- Philipp Fäustlin

5 9

Proxy testing in container( chown failed /var/dovecot/login)
by Marc Roos 11 Nov '19

11 Nov '19

I am testing a bit with the proxy, and trying to run dovecot as a normal user. (with cap bind_service). I was wondering what the minimum configuration is for running like a proxy. I am now getting issues like unable to chown on /var/dovecot/login, but I do not need this in such a setup do I? passdb { driver = static args = proxy=y host=192.168.11.10 nopassword=y }

2 3

Error: Corrupted index cache file and Error: Maildir filename has wrong S value
by Brent Clark 11 Nov '19

11 Nov '19

Good day Guys I have been met with a very interesting set of error messages. Here is the snippet(s) https://pastebin.com/raw/nFf79Ebc (Sorry for all the redacted REMOVED_*.) Google is proving to be a bit challenging in helping and explaining. Could anyone please share how something like this happens, but more importantly how to recover from this. doveadm index -u <username> INBOX do the trick? I also would like to ask the community, is there any tips or tricks any of you guys do to mitigate index / cache corruptions. Many thanks Regards Brent Clark

2 5

User found but password failure
by Mauricio Tavares 11 Nov '19

11 Nov '19

Trying to figure out which step is causing me not to be able to login. I am using a password file, passdb { driver = passwd-file args = scheme=SHA512-CRYPT username_format=%u /etc/dovecot/passwd } We will assume that the pw I created using 'doveadm pw -s SHA512-CRYPT' matches the password I will be using to login below. I crank the debugging mode, auth_debug_passwords = yes auth_debug = yes And then try to login [root@mail ~]# nc -t localhost 143 * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE STARTTLS AUTH=PLAIN AUTH=LOGIN AUTH=GSSAPI] Howdy a login raub(a)example.com password [blank] which from what I gathered from /var/log/dovecot means it found matching username but did not match password: secured session=lyJttvyQ9I0AAAAAAAAAAAAAAAAAAAAB lip=::1 rip=::1 lport=143 rport=36340 resp=base64-reply (previous base64 data may contain sensitive data) Aug 26 03:25:52 auth: Debug: passwd-file(raub@example.com,::1,<lyJttvyQ9I0AAAAAAAAAAAAAAAAAAAAB>): lookup: user=raub(a)example.com file=/etc/dovecot/passwd Aug 26 03:25:52 auth: Debug: client passdb out: OK 1 user=raub(a)example.com Aug 26 03:25:52 auth: Debug: master in: REQUEST 1520959489 26560 1 63ee7f45236f85fd39573a5c8a2eb46a session_pid=26563 request_auth_token Aug 26 03:25:52 auth-worker(26562): Debug: passwd(raub@example.com,::1,<lyJttvyQ9I0AAAAAAAAAAAAAAAAAAAAB>): lookup Aug 26 03:25:52 auth-worker(26562): Info: passwd(raub@example.com,::1,<lyJttvyQ9I0AAAAAAAAAAAAAAAAAAAAB>): unknown user Aug 26 03:25:52 auth: Debug: passwd-file(raub@example.com,::1,<lyJttvyQ9I0AAAAAAAAAAAAAAAAAAAAB>): lookup: user=raub(a)example.com file=/etc/dovecot/passwd Aug 26 03:25:52 auth: Error: plain(raub@example.com,::1,<lyJttvyQ9I0AAAAAAAAAAAAAAAAAAAAB>): user not found from any userdbs Aug 26 03:25:52 auth: Debug: master userdb out: NOTFOUND 1520959489 Aug 26 03:25:52 imap: Error: Authenticated user not found from userdb, auth lookup id=1520959489 (auth connected 1 msecs ago, handshake 0 msecs ago, request took 1 msecs, client-pid=26560 client-id=1) Aug 26 03:25:52 imap-login: Info: Internal login failure (pid=26560 id=1) (internal failure, 1 successful auths): user=<raub(a)example.com>, method=PLAIN, rip=::1, lip=::1, mpid=26563, secured, session=<lyJttvyQ9I0AAAAAAAAAAAAAAAAAAAAB> Per [1] I decided to see what the response (base64-reply) I am submitting to dovecot looks like: echo 'base64-reply' | base64 -d raub(a)example.compassword Which has the right username and password but follows the userpassword format, not useruserpassword as I was led to believe by [1]. Is that to be expected? If it is then the issue is further down the line. [1] https://wiki.dovecot.org/Debugging/Authentication

3 5

Dovecot on CentOS8 / RHEL8
by Aki Tuomi 11 Nov '19

11 Nov '19

If you are planning to run dovecot on CentOS8 or RedHat 8 using native packages, please be aware that pigeonhole is not currently available (but they are working on it), see https://bugzilla.redhat.com/show_bug.cgi?id=1766985 . We are working on getting our CentOS8 packages available on repo.dovecot.org. Aki

1 0

MariaDB database for users and passwords?
by Ken Wright 10 Nov '19

10 Nov '19

Greetings, All! I've got an email server set up with Postfix and Dovecot, but Dovecot can't find any users. I'd ilke to use the database I set up in MariaDB for users (referenced by Postfix), but I'm just not sure how to do it. There's a line in dovecot.conf specifying /etc/dovecot/passwd.db, but obviously that's not the one I set up in MariaDB. Is what I want even possible? Ken -- Registered Linux user #483005 If you ever think international relations make sense, remember this: because a Serb shot an Austrian in Bosnia, Germany invaded Belgium.

8 14

G Suite migration using dsync
by Paul Pace 09 Nov '19

09 Nov '19

Hello, I am trying to migrate a domain from G Suite using dsync and am not clear on how to configure so I am getting failures. This is the configuration in dovecot.conf: imapc_host = imap.gmail.com imapc_port = 993 imapc_password = 1234 imapc_ssl = imaps imapc_ssl_verify = yes imapc_features = gmail-migration I also tried with imapc_ssl_verify commented. For simplicity, both the username and password are the same for G Suite and Dovecot and are verified to access the G Suite account with other tools. Here is the command (from the wiki) and output: # doveadm backup -a 'virtual/All' -O '-$GmailHaveLabels' -R -u user(a)example.com imapc: dsync(user(a)example.com): Info: imapc(imap.gmail.com:993): Connected to 2607:f8b0:4003:c0f::6c:993 (local IPv6:port) dsync(user(a)example.com): Warning: imapc(imap.gmail.com:993): Server disconnected unexpectedly: SSL_connect() failed: error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure: SSL alert number 40 - reconnecting (delay 0 ms) dsync(user(a)example.com): Info: imapc(imap.gmail.com:993): Connected to 74.125.30.109:993 (local IPv4:port) dsync(user(a)example.com): Error: imapc(imap.gmail.com:993): Server disconnected unexpectedly: SSL_connect() failed: error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure: SSL alert number 40 - disconnecting dsync(user(a)example.com): Error: User initialization failed: imapc: Login to imap.gmail.com failed: Disconnected from server In reading through the wiki, it seems I am missing something, but I can't figure out what is missing and internet searches don't provide further useful information on the dovecot tools. Thank you, Paul

1 0

Reading config-value from file does not work.
by Jakobus Schürz 08 Nov '19

08 Nov '19

Hi guys! In https://doc.dovecot.org/configuration_manual/config_file/config_file_syntax/ i ca see this: Reading value from file It’s possible to read the value for a setting from a file: key = </path/to/file The value is read exactly as the entire contents of the file. This includes all the whitespace and newlines. The paths are relative to the currently parsed config file’s directory, similar to how !include works. The file is read immediately whenever parsing the configuration file, so if it changes afterwards it requires a configuration reload to see the changes. This functionality is especially useful for reading SSL certificates and keys. So i thought it's a good idea, to write the password for dnpass for my ldap in this notation in my config dnpass = <private/dnpass /etc/dovecot/private/dnpass contains only this myVerYSecretLdApPAssworD no space, no newline. But dovecot cannot authenticate on the ldap-host. I also tried dnpass = </private/dnpass dnpass = </etc/dovecot/private/dnpass Then i tried a file /etc/dovecot/conf.d/00-dnpass.conf with dnpass = myVerYSecretLdApPAssworD It should be included with dovecot.conf !include conf.d/*.conf The only notation that works is the line dnpass = myVerYSecretLdApPAssworD in /etc/dovecot/dovecot-ldap-userdb.conf.ext I thought it's a good idea to write it in an extra file, so i have to manipulate only one small file with ansible, when i renew the password. Is it a bug or does it work as designed, and the doc is wrong? thank you Jakob

1 1

dovecot ignores users sieve-script
by Jakobus Schürz 08 Nov '19

08 Nov '19

Hi there! I recognized that dovecot ignores users sieve-script. The global and the post-sieve-scripts are working, but users sievescript is ignored. You can see the sieve trace-files last lines 65: finishing match with result: not matched 65: jump if result is true 65: not jumping 65: jumping to line 67 67: jumping to line 77 ## Finished executing script 'global' ## Started executing script 'junk' 2: header test 2: starting `:contains' match with `i;ascii-casemap' comparator: 2: extracting `X-Spam' headers from message 2: finishing match with result: not matched 2: jump if result is false 2: jumping to line 6 ## Finished executing script 'junk' Between global and junk-Script should sieve run users sieve script. Before the Upgrade to 2.3.8 sieve was working correct. Now ALL messages go to INBOX, no one is filtered anymore. compiling the sievescript with sudo -u vmail sievec sievefilter.sieve gives no errormessage... My users sievefilter is: /var/mail/jakobus.schuerz/sieve/sievefilter.sieve This directory contains: lrwxrwxrwx 1 vmail vmail 17 Nov 7 12:44 jakobus.schuerz.sieve -> sievefilter.sieve -rw------- 1 vmail vmail 36834 Nov 7 13:25 jakobus.schuerz.svbin -rw------- 1 vmail vmail 45588 Nov 7 11:43 sievefilter.sieve The dovecot conf dump: # 2.3.8 (9df20d2db): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.8 (b7b03ba2) # OS: Linux 4.19.0-6-amd64 x86_64 Debian 10.1 # Hostname: mail.mydomain.example auth_mechanisms = plain login cram-md5 digest-md5 auth_socket_path = /var/run/dovecot/auth-userdb disable_plaintext_auth = no first_valid_uid = 1000 imap_capability = +XDOVECOT +SPECIAL-USE imap_client_workarounds = tb-extra-mailbox-sep tb-lsub-flags delay-newmail lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes listen = *, ::1 login_log_format_elements = user=<%u> method=%m rip=%r lip=%l mpid=%e %c tls=%k login_trusted_networks = 127.0.0.1/8 192.168.0.0/24 192.168.1.0/24 172.17.0.0/24 172.18.0.0/24 mail_gid = vmail mail_home = /var/mail/%u mail_location = maildir:~/Maildir:LAYOUT=fs:INDEX=/var/lib/dovecot/db/indexes/Maildir/%u:CONTROL=/var/lib/dovecot/db/control/Maildir/%u mail_plugins = zlib quota acl listescape mail_log notify virtual fts fts_lucene mail_privileged_group = vmail mail_server_admin = mailto:user@mydomain.example mail_shared_explicit_inbox = yes mail_uid = vmail managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date index ihave duplicate mime foreverypart extracttext imapsieve vnd.dovecot.imapsieve namespace Geteilt { hidden = no inbox = no list = children location = maildir:/var/mail/%%u/Maildir:LAYOUT=fs:INDEXPVT=/var/lib/dovecot/db/indexes/shared/%u/%%u prefix = Geteilt/%%n/ separator = / subscriptions = no type = shared } namespace History { hidden = no inbox = no list = children location = maildir:/var/mail/archiv/%u/:LAYOUT=fs:INDEX=/var/lib/dovecot/db/indexes/archiv/%u:CONTROL=/var/lib/dovecot/db/control/archiv/%u mailbox Archiv { auto = subscribe special_use = \Archive } prefix = Archiv/ separator = / subscriptions = no type = private } namespace Synoptic { hidden = no ignore_on_failure = no list = children location = virtual:/var/mail/virtual/synoptic:INDEX=/var/lib/dovecot/db/indexes/virtual/synoptic/%u mailbox AKTUELL { auto = subscribe special_use = \All } mailbox Markierte { auto = subscribe special_use = \Flagged } mailbox Neue { auto = subscribe } mailbox Rechnungen { auto = subscribe } mailbox WICHTIG { auto = subscribe } prefix = Synoptic/ separator = / subscriptions = no } namespace Tulln { list = children location = maildir:/var/mail/public/tulln:SUBSCRIPTIONS=subscriptions/%u:LAYOUT=fs:INDEXPVT=/var/lib/dovecot/db/indexes/public/tulln/%u mailbox Familie { auto = subscribe } mailbox Versicherungen { auto = subscribe } mailbox familyextracard { auto = subscribe } prefix = Tulln/ separator = / subscriptions = no type = public } namespace inbox { hidden = no inbox = yes location = mailbox "Deleted Messages" { auto = no autoexpunge = 30 days special_use = \Trash } mailbox Drafts { auto = no special_use = \Drafts } mailbox Entwürfe { auto = no special_use = \Drafts } mailbox "Gelöschte Elemente" { auto = no autoexpunge = 30 days special_use = \Trash } mailbox "Gelöschte Objekte" { auto = no autoexpunge = 30 days special_use = \Trash } mailbox Gesendet { auto = no special_use = \Sent } mailbox "Gesendete Elemente" { auto = no special_use = \Sent } mailbox "Gesendete Objekte" { auto = no special_use = \Sent } mailbox Junk { auto = subscribe autoexpunge = 30 days special_use = \Junk } mailbox Mistkübel { auto = no autoexpunge = 30 days special_use = \Trash } mailbox Papierkorb { auto = no autoexpunge = 30 days special_use = \Trash } mailbox Sent { auto = subscribe special_use = \Sent } mailbox "Sent Messages" { auto = no special_use = \Sent } mailbox Spam { auto = no autoexpunge = 30 days special_use = \Junk } mailbox Synoptic/AKTUELL { auto = no comment = All my messages special_use = \All } mailbox Trash { auto = no autoexpunge = 30 days special_use = \Trash } prefix = INBOX/ separator = / subscriptions = no type = private } namespace subscriptions { hidden = yes list = no location = prefix = subscriptions = yes } passdb { args = /etc/dovecot/dovecot-ldap-passdb-user.conf.ext driver = ldap name = user } passdb { args = /etc/dovecot/dovecot-ldap-passdb-admin.conf.ext driver = ldap name = admin } passdb { args = /etc/dovecot/dovecot-ldap-passdb-others.conf.ext driver = ldap name = others } plugin { acl = vfile:/etc/dovecot/dovecot-acl:cache_secs=300 acl_shared_dict = file:/var/lib/dovecot/db/shared-mailboxes.db fts = lucene fts_autoindex = yes fts_autoindex_max_recent_msgs = 80 fts_index_timeout = 90 fts_lucene = whitespace_chars=@. normalize no_snowball imapsieve_mailbox1_before = file:/etc/dovecot/sieve/report-spam.sieve imapsieve_mailbox1_causes = COPY imapsieve_mailbox1_name = INBOX/Junk imapsieve_mailbox2_before = file:/etc/dovecot/sieve/report-ham.sieve imapsieve_mailbox2_causes = COPY imapsieve_mailbox2_from = INBOX/Junk imapsieve_mailbox2_name = * mail_home = /var/mail/%u mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename mail_log_fields = uid box msgid subject from flags setting_name = sieve, managedsieve sieve = file:/var/mail/%u/sieve/;active=/var/mail/%u/sieve/%u.sieve sieve_after = /etc/dovecot/sieve/after.d/ sieve_before = /etc/dovecot/sieve/global.sieve sieve_global_dir = /etc/dovecot/sieve/ sieve_global_extensions = +vnd.dovecot.pipe sieve_pipe_bin_dir = /etc/dovecot/sieve sieve_plugins = sieve_imapsieve sieve_extprograms sieve_trace_dir = /var/log/dovecot/sieve/trace sieve_trace_level = matching sieve_user_log = /var/mail/%u/sieve/sieve.log } postmaster_address = postmaster@localhost protocols = " imap lmtp lmtp sieve pop3 sieve" service anvil { client_limit = 199999 unix_listener anvil-auth-penalty { mode = 0700 } } service auth { unix_listener auth-client { group = vmail mode = 0666 user = Debian-exim } unix_listener auth-userdb { group = vmail mode = 0666 user = vmail } } service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } process_min_avail = 1 service_count = 1 } service imap-postlogin { executable = script-login -d rawlog /etc/dovecot/acl_groups.py unix_listener imap-postlogin { group = vmail user = vmail } } service imap { executable = imap imap-postlogin process_limit = 1024 vsz_limit = 400 M } service lmtp { user = Debian-exim vsz_limit = 400 M } service stats { unix_listener stats-writer { group = vmail mode = 0600 user = vmail } } ssl = required ssl_cert = </etc/letsencrypt/live/imap.mydomain.example/fullchain.pem ssl_cipher_list = ALL:!ADH:!LOW:!SSLv2:!SSLv3:!EXP:!aNULL:+HIGH:+MEDIUM ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it userdb { args = /etc/dovecot/dovecot-ldap-userdb.conf.ext default_fields = home=/var/mail/%u uid=vmail gid=vmail driver = ldap } verbose_proctitle = yes protocol lmtp { auth_username_format = %Ln mail_plugins = zlib quota acl listescape mail_log notify virtual fts fts_lucene quota sieve acl } protocol lda { info_log_path = log_path = mail_plugins = zlib quota acl listescape mail_log notify virtual fts fts_lucene quota sieve acl } protocol imap { mail_max_userip_connections = 60 mail_plugins = zlib quota acl listescape mail_log notify virtual fts fts_lucene imap_quota imap_acl imap_sieve rawlog_dir = %h/rawlog } Thanks for your help

2 2

[2.3.8] possible replication issue
by KOCIK Fabien (Acoss) 08 Nov '19

08 Nov '19

Hi, I'm dealing for few days with replication issues between two dovecot containerized instances in Kubernetes environment. After some search, I found this thread that reports exactly the same symptoms I encountered : https://dovecot.org/pipermail/dovecot/2019-October/117353.html I can confirm that downgrade of dovecot to 2.3.7.2 fixes the issue. Testing usage of -T parameter with a very low value (10s) on 2.3.8 version is reducing perceptible impact of the issue (mails are replicated within the following five minutes). I'm not expert in dovecot architecture but I tried to put an eye in the code and I'm wondering if this commit is not creating a potential phantom stalled I/O timeout ? https://github.com/dovecot/core/commit/ec817bb2185bb21b34ba6bdd83b32af16dd0… In fact, I was unable to see when the counter incremented by io_set_pending is decremented ? Hoping that this information can help... Regards. Fabien. +--------+ For technical details : Container images are based on Arch Linux distro image. Here is the configuration of Dovecot server : dovecot -n # 2.3.7.2 (3c910f64b): /etc/dovecot/dovecot.conf # OS: Linux 4.19.66-coreos x86_64 ext4 # Hostname: mailstore-0.mailstore.piafe.svc.cluster.local disable_plaintext_auth = no doveadm_password = # hidden, use -P to show it doveadm_port = 12345 login_greeting = PIAFE Mail Server Ready mail_location = mdbox:/var/mail/%Ld/%Ln mail_plugins = " notify replication quota" namespace inbox { hidden = no inbox = yes list = yes location = mailbox Brouillons { auto = subscribe special_use = \Drafts } mailbox Corbeille { auto = subscribe special_use = \Trash } mailbox "Courrier indésirable" { auto = subscribe special_use = \Junk } mailbox Envoyés { auto = subscribe special_use = \Sent } prefix = separator = / subscriptions = yes type = private } passdb { args = /etc/dovecot/ldap.conf.ext driver = ldap } plugin { mail_replica = tcp:mailstore-1.mailstore.piafe.svc.cluster.local quota = dirsize:User quota quota_grace = 10%% quota_max_mail_size = 20M quota_rule = *:storage=1G quota_rule2 = Trash:storage=+200M quota_status_access = DUNNO quota_status_nouser = DUNNO quota_status_overquota = 552 5.5.2 Mailbox is full } postmaster_address = postmaster(a)piafe.recouv.fr replication_dsync_parameters = -d -N -l 30 -U -T 10 service aggregator { fifo_listener replication-notify-fifo { user = mailer } unix_listener replication-notify { user = mailer } } service doveadm { inet_listener { port = 12345 } inet_listener http { port = 8080 } } service lmtp { inet_listener lmtp { address = * port = 24 } } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { group = mailer mode = 0660 } } ssl = no userdb { args = /etc/dovecot/ldap.conf.ext default_fields = uid=500 gid=500 home=/var/mail/%Ld/%Ln driver = ldap } protocol imap { mail_plugins = " notify replication quota quota" }

1 0

Sendmail lmtp delivery and director
by Marc Roos 07 Nov '19

07 Nov '19

If I have sendmail configured to deliver to dovecot lmpt and use the director are incoming messages directed to the correct/configured server? Sendmail.mc with: FEATURE(`local_lmtp',`[IPC]',`FILE /var/run/dovecot/lmtp')dnl

1 0

Using attachment_dir with plugin zlib corrupt mails
by MAREN ZUBIZARRETA 06 Nov '19

06 Nov '19

Hello: I have found the same problem reported above by Patrick Cernko affecting our system and corrupting our messages. Even worse, Outlook 2016 will no synchronize and the clients cannot see any message, even if there is only one corrupted mail per mailbox. I cannot figure out a feasible workaround for our system, and I can see that in new version 2.38 the bug is not fixed. Will this issue be treated soon? Thanks a lot Maren Zubizarreta WARNING: using attachment_dir with plugin zlib can corrupt mails Patrick Cernko pcernko at mpi-klsb.mpg.de<mailto:dovecot%40dovecot.org?Subject=Re:%20Re%3A%20WARNING%3A%20using%20attachment_dir%20with%20plugin%20zlib%20can%20corrupt%20mails&In-Reply-To=%3C1ab8edcc-bef4-3b41-d09a-c523674a5031%40mpi-klsb.mpg.de%3E> Fri Jul 19 17:52:37 EEST 2019 * Previous message: index worker 2.3.7 undefined symbol errors<https://dovecot.org/list/dovecot/2019-July/116617.html> * Next message: Address family not supported by protocol<https://dovecot.org/list/dovecot/2019-July/116571.html> * Messages sorted by: [ date ]<https://dovecot.org/list/dovecot/2019-July/date.html#116570> [ thread ]<https://dovecot.org/list/dovecot/2019-July/thread.html#116570> [ subject ]<https://dovecot.org/list/dovecot/2019-July/subject.html#116570> [ author ]<https://dovecot.org/list/dovecot/2019-July/author.html#116570> ________________________________ Hello list, hello Dovecot developers, this week, I discovered a serious bug in Dovecot, that lead to several broken mails on our servers. The bug corrupts the first few characters of the mail header during saving. On our setup, it was almost always only the very first line of text, that was corrupted. Depending on the IMAP client (they seem to request different header fields, ... during mail access), the bug causes the imap process to hang up the TCP connection and log errors like this: > imap(USERNAME)<4767><TeQP4ASOTK5/AAAB>: Error: Corrupted record in index cache file /IMAP/mail/mailboxes/USERNAME/mdbox/mailboxes/Trash/dbox-Mails/dovecot.index.cache: UID 489113: Broken fields in mailbox Trash: read(attachments-connector(zlib(/IMAP/mail/mailboxes/USERNAME/mdbox/storage/m.813))): FETCH BODY[HEADER.FIELDS (RETURN-PATH SUBJECT)] got too little data: 2 vs 122 In our case that finally grabbed my attention, the client was the users iphone that did not display any new messages but his Thunderbird did. The bug seems to be triggered by a bad "interaction" of attachment_dir option and zlib plugin. If you use both, you most likely are affected, too, except you only use zlib plugin for reading previously compressed stored mails. That's also the workaround we use now: zlib plugin only enabled in mail_plugins but no plugin/zlib_save set. The bug occurs on very specific mails. Due to privacy reasons I could not provide sample mails here. Storing such mails seems to trigger the bug reproducible. I attached a very minimal doveconf -n config, that can be used to trigger the bug. If one of the developers is interested, I can try to generate an "anonymized" version of such a specific mail that still causes the issue. I discovered the bug on our productive systems, running latest Dovecot 2.2 release, but the latest 2.3 I used during debugging is affected, too. During debugging, I also found one hint, that might help find the bug: If you store a problematic mail with zlib_save=gz (or zlib_save=bz2) and then disable the zlib plugin in mail_plugins, you can call doveadm fetch -u test hdr all | grep -v ^hdr: | gzip --decompress on test's mailbox with only that one broken mail. This will display the beginning of the rfc822 mail text until gzip terminates with "gzip: stdin: unexpected end of file", approximately after twice the length of the mail HEADER. This might indicate, that dovecot stores the uncompressed size of the header in it's data structures although the mail is stored compressed. I also found a very efficient way to find all affected mails in our setup: doveadm -f flow fetch -A 'user guid mailbox uid seq flags hdr' all | \ grep -a "^[^ ]+ user=" | \ grep -avF ' hdr=Return-path: ' | \ grep -av '.* hdr=[[:print:][:space:]]*$' (runtime for ~6M mails on our servers was 20-30min) This can be even more optimized if you have a powerful storage system with GNU parallel: > doveadm user '*' | parallel "doveadm -f flow fetch -u '{}' 'user guid mailbox uid seq flags hdr' all | grep -a '^user=' | grep -avF ' hdr=Return-path: ' | grep -av '.* hdr=[[:print:][:space:]]*$' || true" (runtime for ~6M mails on our servers was ~4min) The command will give you a list of mails that possibly are affected, check the full output of doveadm fetch -u USERNAME hdr guid GUID | less to verify that the header is really broken. On our systems I found 39 mails within ~12M mails. I was able to recover these mails "manually" by reconstructing the Return-Path header line, importing the fixed mails and expunging the corrupt ones. Before importing, I had to disable zlib_save option obviously. Best regards, -- Patrick Cernko <pcernko at mpi-klsb.mpg.de<https://dovecot.org/mailman/listinfo/dovecot>> +49 681 9325 5815 Joint Administration: Information Services and Technology Max-Planck-Institute fuer Informatik & Softwaresysteme

6 11

Trying to replace anti spam plugin with IMAPSieve; no joy
by Brad Koehn 06 Nov '19

06 Nov '19

I’m trying to follow the instructions on the wiki to move from antispam to IMAPSieve, but it’s not working at all. A bit of a background: dovecot-core 2:2.3.8-4~buster dovecot-imapd 2:2.3.8-4~buster dovecot-lmtpd 2:2.3.8-4~buster dovecot-managesieved 2:2.3.8-4~buster dovecot-pgsql 2:2.3.8-4~buster dovecot-pop3d 2:2.3.8-4~buster dovecot-sieve 2:2.3.8-4~buster dovecot-solr 2:2.3.8-4~buster My regular sieve scripts work fine for messages arriving through LMTP. I’ve updated my 20-imap.conf thusly: ## ## IMAP specific settings ## protocol imap { mail_max_userip_connections = 30 # Space separated list of plugins to load (default is global mail_plugins). mail_plugins = $mail_plugins imap_acl imap_sieve } plugin { sieve_plugins = sieve_imapsieve sieve_extprograms sieve_trace_dir = /tmp sieve_trace_level = matching # From elsewhere to Spam folder imapsieve_mailbox1_name = Spam imapsieve_mailbox1_causes = COPY imapsieve_mailbox1_before = file:/usr/lib/dovecot/sieve/report-spam.sieve # From Spam folder to elsewhere imapsieve_mailbox2_name = * imapsieve_mailbox2_from = Spam imapsieve_mailbox2_causes = COPY imapsieve_mailbox2_before = file:/usr/lib/dovecot/sieve/report-ham.sieve sieve_pipe_bin_dir = /usr/lib/dovecot/sieve sieve_global_extensions = +vnd.dovecot.pipe +vnd.dovecot.environment } ======== I created the report-spam.sieve and report-ham.sieve scripts in /usr/lib/dovecot/sieve and compiled them with sievec: require ["vnd.dovecot.pipe", "copy", "imapsieve", "environment", "variables"]; if environment :matches "imap.mailbox" "*" { set "mailbox" "${1}"; } if string "${mailbox}" "Trash" { stop; } pipe :copy "sa-learn-pipe.sh" [ "ham" ]; ======== require ["vnd.dovecot.pipe", "copy", "imapsieve", "environment", "variables"]; pipe :copy "sa-learn-pipe.sh" [ "spam" ]; ======== Lastly, I have the sa-learn-pipe.sh script in /usr/lib/dovecot/sieve: #!/bin/bash echo "`date` learning $*" >> /tmp/sa-learn # We run amavisd-new on another Kubernetes pod and communicate with it via socat on both ends; this worked with the old antispam plugin. if [ "$*" = "ham" ] ; then socat - TCP:amavis:4443 else socat - TCP:amavis:4444 fi exit 0 ======== The /usr/lib/dovecot/sieve directory looks like this: drwxr-xr-x 1 root root 4096 Nov 4 20:49 . drwxr-xr-x 1 root root 4096 Nov 3 20:06 .. -rwxr-xr-x 1 root root 237 Nov 3 15:56 report-ham.sieve -rw-r--r-- 1 root root 384 Nov 4 20:49 report-ham.svbin -rwxr-xr-x 1 root root 122 Nov 3 15:56 report-spam.sieve -rw-r--r-- 1 root root 290 Nov 4 20:49 report-spam.svbin -rwxr-xr-x 1 root root 208 Nov 3 17:58 sa-learn-pipe.sh When the sieve scripts run when mail arrives during LMTP delivery they dutifully log their work in /tmp, so I know sieve works and sieve logging works too. The sieve scripts above never log anything, nor does /tmp/sa-learn ever get created as it would if sa-learn-pipe.sh were ever run. As far as I can tell I’ve duplicated the configuration from the wiki almost exactly, but dovecot is just not running the sieve scripts when messages are moved into/out of Junk. What am I missing?

2 1

newbie question on a dovecot buffer
by Richard Bown 06 Nov '19

06 Nov '19

Hi apologies for what will seem a daft question I'm getting problems with my mail provider who is using dovecot. I've loaded Dovecot on a 8 core ARMHF SBC version 2.2.33.2 on Ubuntu 18.04. The SBC is headless. and the load looks very light and only needs to store/cache 4GB of mail Can I use Dovecot as a buffer between my mail providers Dovecot servers and the several IMAP mail clients on my own network ? ie, so Dovecot would mirror the mail on my account with my mail provider, So my local dovecot server downloads mail and caches/stores on the local SBC and all the local users use IMAP from that, instead of from my mail provider. Can I import the same directory structure as help on my mail providers server ? I'm trying to avoid the timeout problem I get when using IMAP from my mail provider. Can it be done ? and can you withstand the questions on configuration, I haven't used Dovecot before so its a vertical learning curve Thanks -- Best wishes /73 Richard Bown Email : richard(a)g8jvm.com HTTP : http://www.g8jvm.com ###################################################################### Ham Call: G8JVM . QRV: 50-432 MHz + Microwave Maidenhead QRA: IO82SP38, LAT. 52 39.720' N LONG. 2 28.171 W QRV 6mtrs 200W, 4mtrs 150W, 2mtrs 300W, 70cms 200W, Microwave 1296MHz 110W, 2320MHz 100W, 5760MHz 10W & 10368MHz 5W OS: Linux Mint 19.2 x86_64 Tina, on a Dell Inspiron 3580 laptop ###################################################################### Come back Guy Fawkes, all is forgiven

3 3

sievec *.sieve problem.
by Reio Remma 05 Nov '19

05 Nov '19

Hello! For the second time I've tripped onto this banana peel. :) I had 2 sieve files in a directory that I wanted to compile: sievec *.sieve The result of this is that first.sieve is compiled into second.sieve instead of first.svbin, thus destroying the source of second.sieve. Please consider this a bug report. :) Good luck, Reio

2 2

Help with master user
by Marcio Merlone 04 Nov '19

04 Nov '19

Hi, Trying to implement a master user (1) for auditing purposes without luck. Ubuntu 18.04.3, canonical official repos only, no ppa nor self-compiled anything. From the log below I understand the master password succeeds but AD auth fails. I am pretty sure I missed something here. Also, notice the messages "Ignoring unknown passdb extra field: original_user". Log: Nov 1 14:02:32 netuno dovecot: auth: Debug: client in: AUTH#0112#011PLAIN#011service=imap#011secured#011session=H2WM7kuWFKYKCQgI#011lip=10.9.8.8#011rip=10.9.8.8#011lport=143#011rport=42516#011resp=<hidden> Nov 1 14:02:32 netuno dovecot: auth: Debug: passwd-file(master,10.9.8.8,master,<H2WM7kuWFKYKCQgI>): Master user lookup for login: test.account Nov 1 14:02:32 netuno dovecot: auth: Debug: passwd-file(master,10.9.8.8,master,<H2WM7kuWFKYKCQgI>): lookup: user=master file=/etc/dovecot/master-users Nov 1 14:02:32 netuno dovecot: auth: passwd-file(master,10.9.8.8,master,<H2WM7kuWFKYKCQgI>): Master user logging in as test.account Nov 1 14:02:32 netuno dovecot: auth: ldap(test.account,10.9.8.8,<H2WM7kuWFKYKCQgI>): invalid credentials Nov 1 14:02:34 netuno dovecot: auth: Debug: client passdb out: FAIL#0112#011user=test.account#011authz#011original_user=master#011auth_user=master Nov 1 14:02:34 netuno dovecot: imap-login: Debug: Ignoring unknown passdb extra field: original_user Nov 1 14:02:34 netuno dovecot: imap-login: Debug: Ignoring unknown passdb extra field: auth_user Nov 1 14:02:42 netuno dovecot: imap-login: Aborted login (auth failed, 1 attempts in 10 secs): user=<test.account>, method=PLAIN, rip=10.9.8.8, lip=10.9.8.8, secured, session=<H2WM7kuWFKYKCQgI> doveconf -n: https://pastebin.com/3cAvfNqB root@netuno:/etc/dovecot# grep -v "^\s*#\|^\s*$" /etc/dovecot/dovecot-ldap.conf.ext hosts = ad.example.net auth_bind = yes auth_bind_userdn = cn=%Lu,CN=Users,DC=ad,DC=example,DC=net base = DC=ad,DC=example,DC=net scope = base user_attrs = \ =home=/mnt/maildirs/%Lu, \ =uid=vmail,\ =gid=vmail user_filter = (&(objectClass=person)(uid=%Lu)(mail=*(a)example.net)) root@netuno:/etc/dovecot# root@netuno:/etc/dovecot# cat /etc/dovecot/global-acls * user=master lr root@netuno:/etc/dovecot# (1) https://doc.dovecot.org/configuration_manual/authentication/master_users/ Best regards -- *Marcio Merlone*

1 1

Bug report
by Peter Nabbefeld 02 Nov '19

02 Nov '19

Hello, I've got a problem fetching my emails using getmail. First question is, of course, what's causing the problems. I'm going to think that getmail get's an error code from dovecot when trying to connect and just signals the most common error, so it seems to be a problem with dovecot. Sorry but I cannot upload any files with the silly web interface of my provider, so I cannot attach a core dump here. :-( Kind regards Peter ~/.getmail/log ========= 2019-11-01 21:44:20 Delivery error (command deliver 42245 error (127, exec of command deliver failed (change UID/GID to vmail/vmail failed ([Errno 1] Operation not permitted)))) dovecot-info.log ========== Oct 31 20:27:00 lda(mein.name(a)gmx.de)<42409><2+iBJIQ1u12ppQAA7IIYzw>: Panic: file istream-crlf.c: line 24 (i_stream_crlf_read_common): assertion failed: (ret != -2) Oct 31 20:27:00 lda(mein.name(a)gmx.de)<42409><2+iBJIQ1u12ppQAA7IIYzw>: Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0xff784) [0x7f4ec8e62784] -> /usr/lib/dovecot/libdovecot.so.0(+0xff7c1) [0x7f4ec8e627c1] -> /usr/lib/dovecot/libdovecot.so.0(+0x493aa) [0x7f4ec8dac3aa] -> /usr/lib/dovecot/libdovecot.so.0(+0x4bf62) [0x7f4ec8daef62] -> /usr/lib/dovecot/libdovecot.so.0(+0x111076) [0x7f4ec8e74076] -> /usr/lib/dovecot/libdovecot.so.0(i_stream_read_memarea+0x81) [0x7f4ec8e70291] -> /usr/lib/dovecot/libdovecot.so.0(i_stream_read+0x37) [0x7f4ec8e70477] -> /usr/lib/dovecot/libdovecot.so.0(+0x1164a8) [0x7f4ec8e794a8] -> /usr/lib/dovecot/libdovecot.so.0(i_stream_read_memarea+0x81) [0x7f4ec8e70291] -> /usr/lib/dovecot/libdovecot.so.0(i_stream_read+0x37) [0x7f4ec8e70477] -> /usr/lib/dovecot/libdovecot.so.0(i_stream_read_data+0x4c) [0x7f4ec8e70f3c] -> /usr/lib/dovecot/libdovecot.so.0(io_stream_copy+0x8a) [0x7f4ec8e8bbea] -> /usr/lib/dovecot/libdovecot.so.0(+0x12aa86) [0x7f4ec8e8da86] -> /usr/lib/dovecot/libdovecot.so.0(o_stream_send_istream+0x4f) [0x7f4ec8e8b86f] -> /usr/lib/dovecot/libdovecot-storage.so.0(index_storage_save_continue+0x2e) [0x7f4ec901114e] -> /usr/lib/dovecot/libdovecot-storage.so.0(maildir_save_continue+0x27) [0x7f4ec8fafbe7] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_save_continue+0x47) [0x7f4ec8f815b7] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_storage_copy+0xe8) [0x7f4ec8f72388] -> /usr/lib/dovecot/libdovecot-storage.so.0(maildir_copy+0x6d) [0x7f4ec8fab99d] -> /usr/lib/dovecot/libdovecot-lda.so.0(+0x3c46) [0x7f4ec90a2c46] -> /usr/lib/dovecot/modules/lib20_fts_plugin.so(+0x11004) [0x7f4ec8af0004] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0x59b0c) [0x7f4ec8f81b0c] -> /usr/lib/dovecot/libdovecot-sieve.so.0(+0x4edb8) [0x7f4ec67e0db8] -> /usr/lib/dovecot/libdovecot-sieve.so.0(sieve_result_execute+0x54d) [0x7f4ec67d65cd] -> /usr/lib/dovecot/libdovecot-sieve.so.0(+0x57a79) [0x7f4ec67e9a79] -> /usr/lib/dovecot/libdovecot-sieve.so.0(sieve_multiscript_run+0xa9) [0x7f4ec67eac49] -> /usr/lib/dovecot/modules/lib90_sieve_plugin.so(+0x376b) [0x7f4ec685c76b] -> /usr/lib/dovecot/libdovecot-lda.so.0(mail_deliver+0x199) [0x7f4ec90a46d9] dovecot -n ======= # 2.3.8 (9df20d2db): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.8 (b7b03ba2) # OS: Linux 5.3.7-arch1-2-ARCH x86_64 Arch Linux # Hostname: mein.host.name auth_verbose = yes disable_plaintext_auth = no info_log_path = /var/log/dovecot-info.log log_path = /var/log/dovecot.log mail_location = maildir:~/Maildir:LAYOUT=fs mail_plugins = " 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 index ihave duplicate mime foreverypart extracttext editheader namespace inbox { inbox = yes location = mailbox Entwürfe { special_use = \Drafts } mailbox Gesendet { special_use = \Sent } mailbox Spamverdacht { special_use = \Junk } mailbox Trash { special_use = \Trash } prefix = } passdb { args = username_format=%u /etc/dovecot/passwd driver = passwd-file } plugin { fts = solr fts_solr = url=http://localhost:8983/solr/ sieve = file:/home/vmail/sieve;active=/home/vmail/.dovecot.sieve sieve_extensions = +editheader } service stats { unix_listener stats-reader { group = vmail mode = 0666 user = vmail } unix_listener stats-writer { group = vmail mode = 0666 user = vmail } } ssl = no ssl_dh = # hidden, use -P to show it userdb { args = uid=vmail gid=vmail home=/home/vmail/%d/%n driver = static } protocol lda { mail_plugins = " fts fts_solr sieve" postmaster_address = mein.name(a)gmx.de }

3 2

warning: NFS hangs with dovecot 2.3.8 on Debian buster
by Jan-Pieter Cornet 01 Nov '19

01 Nov '19

A warning to those considering to upgrade to Debian 10 (buster): we have seen occasional NFS hangs with dovecot when using the stock debian buster kernel (4.19.67-2+deb10u1). When we downgrade to the debian stretch kernel (4.9.189-3+deb9u1), the issue does not occur. Note that we *only* downgraded the kernel, the rest of the OS is still debian buster. Dovecot 2.3.8. A little more info: we have a dovecot cluster, using mdbox for storage, on an NFS server (netapp Cmode version 9.6P2). We use a dovecot director layer, so a user is always connected to the same back-end dovecot server. The NFS hang occurs on the back-end server. Once the process hangs, other processes trying to write to the same mailbox, will get an error like this: Timeout (180s) while waiting for lock for transaction log file /var/mail/.../index/storage/dovecot.map.index.log (WRITE lock held by pid XXXX) The stuck process itself doesn't seem to do anything, is stuck in "D" disk state, "strace" doesn't show anything (and after attaching, strace itself needs a kill -KILL to stop). The only way to unwedge the process seems to be to do a kill -KILL of the stuck process. Reading from the mailbox is still possible. We are in the process of contacting the linux-nfs folks about this, but I'm trying to reproduce this on a test-cluster first, to be able to present a well-documented case. Since this hang doesn't happen immediately, but takes a few hours to a day to occur in the wild, or a few thousand writes to the same mailbox, it's a bit hard to debug. -- Jan-Pieter Cornet <johnpc(a)xs4all.net> Systeembeheer XS4ALL Internet bv www.xs4all.nl

1 1

Dovecot and MySQL aborted connections.
by Benjamin Connelly 01 Nov '19

01 Nov '19

We also spotted these sql connections getting aborted, upon upgrading MySQL from 5.6 to 5.7. (Going back to 5.6 we don't see them!) Turning on mysql general query logging we can see it is Dovecot's mysql connections that inquire about or update quota usage in particular: *** /logs//mysql.log *** 2019-10-30T10:52:22.624690-07:00 2 Connect dovecot@localhost on npomail using Socket 2019-10-30T10:52:40.019780-07:00 2 Query SELECT bytes FROM quota2 WHERE username = 'a@bla' 2019-10-30T10:52:40.020948-07:00 2 Query SELECT messages FROM quota2 WHERE username = 'a@bla' 2019-10-30T10:53:40.113374-07:00 2 [Note] Aborted connection 2 to db: 'npomail' user: 'dovecot' host: 'localhost' (Got an error reading communication packets) Increasing mysqld's net_read_timeout and net_write_timeout values to 3600 does not stop the aborted connections. It seems asymptomatic. If the connection to mysql is still there to do quota operations, Dovecot seems to use it. If it's been aborted by the server, Dovecot seems to just (re)connect. . . But I'd love to help find the root or file a bug report or learn what it is we've configured wrong. . . Benjamin

4 5

dovecot and ldap
by Maciej Milaszewski IQ PL 01 Nov '19

01 Nov '19

Hi Sorry for my question... I use dovecot+ldap How realy works (in dovecot-2.2.x ) lists of LDAP hosts to use ? ------ dovecot.conf ---- hosts = ldap.domain.pl:389 ldap-slave.domain.pl:389 #uris = -------- This is simpe HA ? I mean if ldap.domain.pl have problem another request go to ldap-slave.domain.pl ?

2 1

Broken uids: Director lmtp proxy able to change the destination address?
by Erik de Waard 31 Oct '19

31 Oct '19

Hi, Director -> Backends -> NFS setup. Problem: Broken dovecot-uidlists because of our postfix LMTP delivery using a different address than the IMAP client lookups Error: Mailbox INBOX: Broken file dovecot-uidlist line 169: Invalid data: example: LMTP delivery: lmtp(info#domain.nl(a)mail.local) IMAP lookup: info(a)domain.nl doveadm director status info#domain.nl(a)mail.local Current: 10.0.10.223 (expires 2019-11-01 08:52:42) Hashed: 10.0.10.223 Initial config: 10.0.10.223 doveadm director status info(a)domain.nl Current: 10.0.10.113 (expires 2019-11-01 13:47:27) Hashed: 10.0.10.113 Initial config: 10.0.10.113 On the backends these would write to the same NFS maildir: Now Director would assign these addresses to different backend servers and thus result in the expected corrupted control files. at this time i'm unable to reconfigure the Postfix LMTP delivery in a way that these use the same lookup format. Questions: 1. Disable LMTP updating dovecot-uidlist and indexes. Perhaps using Maildir:CONTROL=/dev/null :INDEX=MEMORY for lmtp-sql.conf? 2. Since i'm using director/proxy is it possible to rewrite the address using SQL in the passdb query? 3. What would be the best settings to avoid corruption in this broken setup.

1 0

encrypt incoming emails with public gpg key before they are stored to maildir
by Fourhundred Thecat 31 Oct '19

31 Oct '19

Hello, I have asked on the postfix mailing list for a solution, how to encrypt incoming emails with public gpg key My original idea was to use a smtpd-milter, which would encrypt all incoming plaintext messages of given user, using the users public gpg key. This way, it would look as if the original sender has sent the message encrypted. Somebody suggested this might be better done in Dovecot, as it is Dovecot who stores the emails in Maildir. Does anybody have any suggestions how to implement this scheme in Dovecot ? I am including the original email below: > when new email arrives, and it is not already encrypted, I would like to > run it through a filter, which would encrypt the message with my public > gpg key, as if the original sender has sent the email encrypted. > > Why do I want to do this ? Why not ask the sender to send encrypted > messages to start with ? > > Lets say my bank sends me emails. I cannot force my bank to use gpg > encryption. I am happy they use email at all, instead of paper mail. > > My email server is untrusted. It can be hacked into and emails stolen. > Full disk encryption will not help, because the disk must be decrypted > during runtime. > > With my scheme, all emails would be stored encrypted on my server, and > decryption key does not exist on the server (emails are decrypted on my > local client) > > What would be the best way to implement this ? > > Can such filter work, without ever storing plaintext email on disk ? thanks,

3 2

Dovecot HSM
by Júlio Covolato 31 Oct '19

31 Oct '19

Hi. I'm looking for a tutorial/how-to for a HSM (Hierarchical /Storage/ Management). keeping old messages for a user in a cheap storage and recent messages in a faster one. I see on dovecot2 wiki an alternative for hsm as "Alternate storage", but I don't now if it's a good solution for me. The expected result is a faster imap/pop access for new messages on a "heavy mail users" mailbox, and obviously low cost! Thanks in advance. -- ---------------------------------- _ Engº Julio Cesar Covolato 0v0 <julio(a)psi.com.br> /(_)\ F: +55 11 99175-9260 ^ ^ PSI INTERNET ----------------------------------

2 1

Re: Dovecot HSM
by Marc Roos 30 Oct '19

30 Oct '19

1 0

How do I search for "greetings of the day"
by Ralf Hildebrandt 30 Oct '19

30 Oct '19

My users say that "greetings of the day" occurs in academic spam a lot. Since I don't trust my users, I opted to verify this bold claim. But how do I search for a sequence of multiple words? doveadm import -u restore(a)backup.invalid mdbox:/home/copymail/mdbox "" mailbox INBOX BODY "Greetings of the day" doveadm import -u restore(a)backup.invalid mdbox:/home/copymail/mdbox "" mailbox INBOX TEXT "Greetings of the day" (what's the difference betweeen BODY and TEXT?) Is it even possible, given that "the" and "of" are probably stop words? -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebrandt(a)charite.de | https://www.charite.de

2 1

Recovering emails from "dead" server
by Mark | Small World Systems 29 Oct '19

29 Oct '19

I have a Linix server that won't boot. I've patched in a live CD and mounted the original HDDs so I can browse the files using SSH. I am trying to find where all my customer emails are stored so that I can (hopefully) copy them off this "dead" server onto a new server which is also running cPanel and Dovecot. Does anyone know where Dovecot stores emails for each email account when it runs under cPanel? I can see a directory called /home/<cpanel username>/mail/<domain name>/<mail username> (I've used <xxxxx> in place of the actual text to obviscate the actual user information). If I navigate to that directory I can see lots of interesting sub directories e.g. cur, new and tmp plus some files such as: dovecot.index.cache, dovecote.index, dovecote-uidlist But then I'm stumped. I was hoping to find a big fat directory that contained all the mail files. Is anyone able to tell me what I need to copy across to get all the old emails off the "dead" server onto the new one? Thank you.

3 2

Sieve problem - Timeout while waiting for lock
by Domenico Pastore 29 Oct '19

29 Oct '19

Hi, I have an issue with dovecot 2.3.7.2. When lmtp stores a message into INBOX, I get this error: 2019-10-29 16:32:53 lmtp(“test@XXXX”)<28874><4IPiEytbuF3KcAAAioI89A>: Error: sieve: Execution of script /config/dovecot/common/default.sieve was aborted due to temporary failure 2019-10-29 16:32:53 lmtp(“test@XXXX”)<23470>: Error: sieve: msgid=CE595339-2976-6DFD-FDAD-EEA15CC53218@XXXX: failed to store into mailbox ‘INBOX’: Timeout while waiting for lock This problem only occurs for one mailbox and when it receives a big amount of messages. With the previous version (dovecot 2.2.15) this did never occur. The file /config/dovecot/common/default.sieve is in local server, no on NFS filesystem BR, Domenico ----------------- # 2.3.7.2 (3c910f64b): /config/dovecot/dovecot/dovecot.conf # Pigeonhole version 0.5.7.2 (7372921a) # OS: Linux 3.10.0-1062.1.2.el7.x86_64 x86_64 CentOS Linux release 7.7.1908 (Core) auth_debug = yes auth_master_user_separator = * auth_username_format = base_dir = /data/dovecot/var/run/dovecot default_client_limit = 8192 default_vsz_limit = 768 M dict { sqlquota = mysql:/config/dovecot/common/dovecot-dict-sql.conf.ext } disable_plaintext_auth = no doveadm_password = # hidden, use -P to show it first_valid_gid = 101 first_valid_uid = 102 imap_id_send = import_environment = TZ info_log_path = /LOGS/dovecot/dovecot.log instance_name = dovecot listen = dovecot log_path = /LOGS/dovecot/dovecot.log log_timestamp = "%Y-%m-%d %H:%M:%S " mail_gid = 101 mail_location = maildir:%h/Maildir mail_max_userip_connections = 50 mail_plugins = quota fts fts_solr mail_log notify virtual mail_uid = 102 maildir_broken_filename_sizes = yes managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date index ihave duplicate mime foreverypart extracttext vnd.dovecot.debug mbox_write_locks = fcntl namespace { hidden = yes list = no location = virtual:/config/dovecot/common/virtual:INDEX=~/virtual:SUBSCRIPTIONS=.subscriptions/%u prefix = Messaggi in arrivo. separator = . subscriptions = no } namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = INBOX. separator = . subscriptions = yes type = private } passdb { args = /config/dovecot/common/passwd.masterusers driver = passwd-file master = yes } passdb { args = /config/dovecot/dovecot/dovecot-ldap.conf driver = ldap } passdb { args = /config/dovecot/common/dovecot-ldap-multiuser.conf driver = ldap master = yes } passdb { args = /config/dovecot/common/dovecot-ldap-webmail.conf.ext driver = ldap master = yes } plugin { fts = solr fts_autoindex = yes fts_autoindex_max_recent = 1000 fts_solr = url=https://192.160.10.81:8983/solr/dovecot/ mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename flag_change save mailbox_create mail_log_fields = uid box msgid size flags quota = dict:User quota::proxy::sqlquota quota_rule2 = INBOX.Trash:storage=+100M sieve_default = /dovecot/common/default.sieve sieve_extensions = +vnd.dovecot.debug } postmaster_address = posta(a)XXXX.it service anvil { client_limit = 8000 } service auth { client_limit = 12000 unix_listener auth-userdb { mode = 0600 } } service dict { process_limit = 7500 process_min_avail = 10 unix_listener dict { mode = 0600 user = dovecot } } service doveadm { chroot = client_limit = 1 drop_priv_before_exec = no executable = doveadm-server extra_groups = group = idle_kill = 0 inet_listener { port = 924 } privileged_group = process_limit = 0 process_min_avail = 10 protocol = service_count = 100 type = unix_listener doveadm-server { group = mode = 0600 user = } user = vsz_limit = 18446744073709551615 B } service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } process_limit = 5000 process_min_avail = 10 } service imap { drop_priv_before_exec = yes process_limit = 5000 process_min_avail = 10 } service lmtp { inet_listener lmtp { port = 24 } process_limit = 2500 process_min_avail = 10 } service managesieve-login { inet_listener sieve { port = 4190 } process_min_avail = 0 service_count = 1 vsz_limit = 64 M } service managesieve { drop_priv_before_exec = yes process_limit = 1024 } service pop3-login { inet_listener pop3 { port = 110 } inet_listener pop3s { port = 995 ssl = yes } process_limit = 1000 process_min_avail = 5 } service pop3 { drop_priv_before_exec = yes process_limit = 1000 process_min_avail = 5 } ssl_cert = </config/dovecot/common/certs/dovecot.pem ssl_client_ca_file = /config/solr-certs/solr-ssl.pem ssl_key = # hidden, use -P to show it userdb { args = /config/dovecot/dovecot/dovecot-ldap.conf driver = ldap } protocol lmtp { mail_plugins = quota mail_log notify sieve virtual fts fts_solr } protocol lda { mail_plugins = quota mail_log notify sieve virtual } protocol imap { mail_plugins = quota imap_quota mail_log notify virtual fts fts_solr } protocol pop3 { mail_plugins = quota mail_log notify virtual pop3_uidl_format = UID%u-%v }

1 1

Error: Mailbox INBOX: Broken file dovecot-uidlist: Invalid data
by Dirk 29 Oct '19

29 Oct '19

Hi list, today a user reported messages are disappearing from his INBOX and I discovered a two digit number of mailboxes with broken dovecot-uidlist files. The log says: Oct 29 08:51:34 mail02 dovecot: lmtp(info(a)example.com)<5270><QOoVJIbvt12WFAAAJOVBUw>: Error: Mailbox INBOX: Broken file /var/vmail/example.com/info/dovecot-uidlist line 88: Invalid data: And the respective files do look broken: 4596 :1572344253.M529133P14861.mail03.example.com,S=53053,W=54233 ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@4597 :1572344797.M93833P15905.mail03.example.com,S=126866,W=129256 Setup : Behind a director I am running two dovecot backend servers sharing the vmail directory via NFS. Do you have an idea where this might come from? How can I debug this further? Cheers, Dirk

1 0

changing cipher for imap clients
by Fourhundred Thecat 29 Oct '19

29 Oct '19

When my client connects, I see this in my log: dovecot: imap-login: TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits) Whereas, when client connects to my postfix server, I see: Anonymous TLS connection established from * TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits) how can I tell dovecot to use AES256, instead of AES128 ? is this set by ssl_cipher_list ? Here are my current values (defaults) # doveconf ssl_cipher_list ssl_cipher_list = ALL:!kRSA:!SRP:!kDHd:!DSS:!aNULL:!eNULL:!EXPORT:!DES:!3DES:!MD5:!PSK:!RC4:!ADH:!LOW@STRENGTH # dovecot --version 2.3.4.1 thanks,

4 4

Dovecot and MySQL aborted connections.
by Reio Remma 28 Oct '19

28 Oct '19

Is anyone else using Dovecot (2.3.8) with MySQL (5.7) seeing a lot of these in MySQL logs? 2019-10-28T11:08:20.384428+02:00 58378 [Note] Aborted connection 58378 to db: 'vmail' user: 'vmail' host: 'localhost' (Got an error reading communication packets) 2019-10-28T11:10:09.821171+02:00 58420 [Note] Aborted connection 58420 to db: 'vmail' user: 'vmail' host: 'localhost' (Got an error reading communication packets) 2019-10-28T11:11:26.170015+02:00 58441 [Note] Aborted connection 58441 to db: 'vmail' user: 'vmail' host: 'localhost' (Got an error reading communication packets) 2019-10-28T11:13:14.091426+02:00 58459 [Note] Aborted connection 58459 to db: 'vmail' user: 'vmail' host: 'localhost' (Got an error reading communication packets) They've plagued my logs for as long as I can remember. Is Dovecot not closing connections to the database properly or something similar? Reio

3 3

Dovecot list breaks DKIM.
by Reio Remma 28 Oct '19

28 Oct '19

Hello again, I noticed mails from the Dovecot list break DKIM signatures. Perhaps it's something to look at? Most lists I'm on manage to pass messages with DKIM intact. Authentication-Results: abc.abc.abc; dkim=fail (rsa verify failed) header.d=mrstuudio.ee header.s=mr header.b=M03Fp5lE; dmarc=pass (policy=none) header.from=dovecot.org; spf=pass Thanks, Reio

1 0

SQL iterate_query
by Daniel Miller 28 Oct '19

28 Oct '19

I've been hunting some ghost mailboxes - and I *think* I found the source. I use the complete email address as the username, and store such in a database. The storage structure is location=/var/mail/%d/%n. Not unusual I think. So all I *should* see from "ls /var/mail" would be a list of domains. But I keep seeing empty mailboxes being created at this level. Having corrected a few other errors I *hope* I've found the last one - but if I'm right I believe the docs need updating: The examples given for SQL userdb's include: iterate_query = SELECT userid AS username, domain FROM users So this means the username is returned for *both* the username and domain. Even if I'm wrong as to the cause of my own troubles this can't be right. It just can't. Or am I mistaken? So, given that the complete address is used as the username I now use: iterate_query = SELECT username FROM mailbox (I'm using postfixadmin to administer this - and "mailbox" is the default user table name) I believe the alternative would be an explicit: iterate_query = SELECT username, domain AS username, domain FROM users I don't *think* that would make any security difference for my use case so why add the extra processing? I believe the documentation should be updated, or at least clarified, on this issue. -- Daniel

2 1

Configure to only receive recent mail?
by lty 28 Oct '19

28 Oct '19

I am looking for imap or pop3 to receive only the most recent emails. Virtual-plugin seems to meet my needs https://doc.dovecot.org/configuration_manual/virtual_plugin/#virtual-plugin > List messages from past 48 hours (syntax is in seconds): > # ~/Maildir/virtual/recent/dovecot-virtual > INBOX > work/* > all younger 172800 but this will create a virtual/*, I want to control the real INBOX. The user can set the email for how long it takes to set itself, for example, within 3 months by default.This way you can use all the mail to display to the client. Does dovecot support such a configuration?

1 0

Dovecot Index Corruption and dovecot-uidlist Issues
by Billy Luedtke 25 Oct '19

25 Oct '19

Hello, We have recently implemented dovecot directors to resolve an ongoing NFS lock/corruption issue. Everything was working great! So we updated our servers from centos 7.3 to 7.7 and dovecot 2.2.10 to 2.3.8 This was a bit of a failure and we were getting spammed with corrupt index files and logs. After we clear the index files with rm rf/mail/d/e/username/Maildir/dovecot*, they just come back in. From: dovecot-mysql-2.3.8-4.x86_64 dovecot-2.3.8-4.x86_64 dovecot-pigeonhole-2.3.8-4.x86_64 To: dovecot-2.2.10-8.el7.x86_64 dovecot-mysql-2.2.10-8.el7.x86_64 dovecot-pigeonhole-2.2.10-8.el7.x86_64 We rolled back nfs-utils and libs due to a case on redhats bug report "https://bugzilla.redhat.com/show_bug.cgi?id=1521071" libnfsidmap-0.25-19.el7.x86_64 nfs-utils-1.3.0-0.65.el7.x86_64 to libnfsidmap-0.25-15.el7.x86_64 nfs-utils-1.3.0-0.33.el7.x86_64 We rolled back our dovecot version to 2.2.10 and are still getting the following logs. Any advice would help Network view: |Dovecot Directors x 3| | |Dovecot servers x4| Storage is shared between all 4 servers | |Netapp NFSv3 Storage| Nothing changed here Oct 25 01:33:25 <IP> dovecot: imap(<username>): Error: Log synchronization error at seq=89,offset=32340 for /mail/j/k/<username>/Maildir/dovecot.index: Extension record update for invalid uid=6798 Oct 25 01:33:25 <IP> dovecot: imap(<username>): Error: Log synchronization error at seq=89,offset=32384 for /mail/j/k/<username>/Maildir/dovecot.index: Extension record update for invalid uid=6798 Oct 25 01:33:25 <IP> dovecot: imap(<username>): Error: Synchronization corrupted index header /mail/j/k/<username>/Maildir/dovecot.index: first_recent_uid 6799 > next_uid 6798 Oct 25 01:33:25 <IP> dovecot: imap(<username>): Warning: fscking index file /mail/j/k/<username>/Maildir/dovecot.index Oct 25 01:33:25 <IP> dovecot: imap(<username>): Error: Fixed index file /mail/j/k/<username>/Maildir/dovecot.index: first_recent_uid 6799 -> 6798 Oct 25 01:33:26 <IP> dovecot: imap(<username>): Error: Broken file /mail/j/k/<username>/Maildir/dovecot-uidlist line 6461: Invalid data: Oct 25 01:33:26 <IP> dovecot: imap(<username>): Error: Log synchronization error at seq=89,offset=32488 for /mail/j/k/<username>/Maildir/dovecot.index: Append with UID 6798, but next_uid = 6799 Oct 25 01:33:26 <IP> dovecot: imap(<username>): Warning: fscking index file /mail/j/k/<username>/Maildir/dovecot.index Oct 25 01:47:14 <IP> dovecot: imap(<username>): Warning: fscking index file /mail/d/e/<username>/Maildir/dovecot.index Oct 25 01:47:14 <IP> dovecot: imap(<username>): Error: Failed to map transaction log /mail/d/e/<username>/Maildir/dovecot.index.log at sync_offset=9900 after locking: pread() failed: Stale file handle Oct 25 01:47:14 <IP> dovecot: imap(<username>): Error: Index /mail/d/e/<username>/Maildir/dovecot.index: Lost log for seq=16 offset=192: Missing middle file seq=16 (between 16..4294967295, we have seqs 14): Requested newer log than exists: Log inode is unchanged (initial_mapped=1, reason=Index mapped) Oct 25 01:51:14 <IP> dovecot: imap(<username>): Error: Broken file /mail/d/e/<username>/Maildir/dovecot-uidlist line 65: Invalid data: Dovecot -n # 2.2.10: /etc/dovecot/dovecot.conf # OS: Linux 3.10.0-1062.1.2.el7.x86_64 x86_64 CentOS Linux release 7.7.1908 (Core) auth_mechanisms = plain login auth_username_format = %Ln auth_verbose = yes auth_verbose_passwords = plain disable_plaintext_auth = no first_valid_uid = 300 lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes mail_fsync = always mail_location = maildir:~/Maildir mail_nfs_index = yes mail_nfs_storage = yes maildir_very_dirty_syncs = yes managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave mmap_disable = yes namespace inbox { inbox = yes location = mailbox 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/sql.conf.ext driver = sql } plugin { sieve = ~/.dovecot.sieve sieve_dir = ~/sieve sieve_global_dir = /mail/sieve/global/ sieve_global_path = /mail/sieve/default.sieve } postmaster_address = postmaster@%d protocols = imap pop3 lmtp sieve service auth { client_limit = 0 inet_listener { port = 11010 } process_limit = 1 process_min_avail = 0 service_count = 0 } service dict { unix_listener dict { group = vmail mode = 0600 user = vmail } } service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } process_limit = 2 process_min_avail = 2 service_count = 0 } service imap { client_limit = 1 executable = imap process_limit = 2048 process_min_avail = 50 service_count = 1 } service lmtp { client_limit = 1 process_limit = 0 process_min_avail = 0 service_count = 0 unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0660 user = postfix } } service managesieve-login { inet_listener sieve { port = 4190 } } service pop3-login { inet_listener pop3 { port = 110 } inet_listener pop3s { port = 995 ssl = yes } process_limit = 2 process_min_avail = 2 service_count = 0 } service pop3 { client_limit = 1 executable = pop3 process_limit = 256 process_min_avail = 25 service_count = 1 } ssl_ca = </etc/ssl/mdc/mdc.ca ssl_cert = </etc/ssl/mdc/mdc.crt ssl_cipher_list = !RC4:HIGH:MEDIUM:+TLSv1:!MD5:!SSLv2:+SSLv3:!ADH:!aNULL:!eNULL:!NULL:!DH:!ADH:!EDH:!AESGCM ssl_key = </etc/ssl/mdc/mdc.key ssl_protocols = !SSLv2 !SSLv3 userdb { args = /etc/dovecot/sql.conf.ext driver = sql override_fields = plain_pass=%w } protocol lmtp { mail_plugins = " quota sieve" } protocol imap { mail_max_userip_connections = 40 } protocol sieve { info_log_path = /var/log/dovecot-sieve.log log_path = /var/log/dovecot-sieve-errors.log managesieve_implementation_string = dovecot managesieve_max_line_length = 65536 } Billy Luedtke, Microsoft MCP System Administrator II, WIN

1 0

subscription namespace
by Daniel Miller 25 Oct '19

25 Oct '19

The current documentation makes mention of a "special" subscription namespace. The example given: namespace subscriptions { subscriptions = yes prefix = "" list = no hidden = yes } namespace inbox { inbox = yes location = subscriptions = no [...] results in a startup error as both namespaces have the same prefix. Was the intent for the "inbox" namespace to have an explicit "INBOX/" prefix? If this is configured for an existing server that previously had no such "INBOX/" prefix namespace - will clients need to be reconfigured? -- Daniel

1 0

Still trying to get past authorization problems
by Steve Matzura 24 Oct '19

24 Oct '19

Got all the Postfix errors fixed but maybe one, so I don't think that's involved in this mix any more. I had a domain definition problem, got that sorted. The accounts' logins are correct. I tried several from the shell, and they let me in. Here's the minus-n output, not very different from the first time I posted it: # 2.2.33.2 (d6601f4ec): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.21 (92477967) # OS: Linux 4.15.0-64-generic x86_64 Ubuntu 18.04.3 LTS ext4 base_dir = /var/run/dovecot/ first_valid_gid = 109 first_valid_uid = 105 last_valid_gid = 109 last_valid_uid = 105 log_path = /var/log/dovecot.log mail_gid = postfix mail_location = maildir:/var/mail/vmail/%d/%n mail_uid = postfix 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 lmtp" service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } unix_listener auth-userdb { group = postfix mode = 0666 user = postfix } } service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } process_min_avail = 0 service_count = 1 } service lmtp { unix_listener lmtp { mode = 0666 } } service pop3-login { inet_listener pop3 { port = 110 } inet_listener pop3s { port = 995 ssl = yes } } service pop3 { process_limit = 1024 } ssl = required ssl_cert = </etc/ssl/private/tgv2018.crt ssl_key = # hidden, use -P to show it userdb { driver = passwd } These from dovecot.log just keep going round and round. Oct 24 02:23:57 imap-login: Info: Aborted login (auth failed, 1 attempts in 3 secs): user=<chrissie(a)theglobalvoice.info>, method=PLAIN, rip=86.148.44.160, lip=95.142.174.193, TLS, session=<7SCVuZ6VScBWlCyg> Oct 24 02:25:55 imap-login: Info: Disconnected (auth failed, 2 attempts in 132 secs): user=<yourvoice(a)theglobalvoice.info>, method=PLAIN, rip=108.41.57.11, lip=95.142.174.193, TLS, session=<ZErquJ6VpMpsKTkL> Oct 24 02:25:55 imap-login: Info: Disconnected (auth failed, 2 attempts in 132 secs): user=<yourvoice(a)theglobalvoice.info>, method=PLAIN, rip=108.41.57.11, lip=95.142.174.193, TLS, session=<6bnquJ6VpcpsKTkL> Oct 24 02:57:58 imap-login: Info: Disconnected (auth failed, 4 attempts in 43 secs): user=<yourvoice(a)theglobalvoice.info>, method=PLAIN, rip=108.41.57.11, lip=95.142.174.193, TLS, session=<CRHUMJ+V59JsKTkL> Oct 24 03:06:23 imap-login: Info: Disconnected (no auth attempts in 0 secs): user=<>, rip=49.51.34.136, lip=95.142.174.193, session=<jGWJUZ+VAM8xMyKI> Oct 24 03:06:24 imap-login: Info: Disconnected: Too many invalid commands (no auth attempts in 0 secs): user=<>, rip=49.51.34.136, lip=95.142.174.193, session=<agCMUZ+V8JMxMyKI> Oct 24 03:07:55 imap-login: Info: Disconnected (auth failed, 2 attempts in 13 secs): user=<yourvoice(a)theglobalvoice.info>, method=PLAIN, rip=108.41.57.11, lip=95.142.174.193, TLS, session=<ivc4Vp+V79VsKTkL>

3 3

RE: dovecot disk space settings
by Marc Roos 22 Oct '19

22 Oct '19

Ok, what about placing a dummy file of 5GB or so on the partition, that you can remove when necessary? -----Original Message----- Subject: Re: dovecot disk space settings >> I don't want to restrict each mailbox size. It's just to prevent > running out space completely. > > Why? (If I may ask) > > To provide mailboxes with unlimited space. And to make it easier to administrate. My question is about an emergency option if someone has forgotten to migrate to new hardware. It's possible but a bit harder if the partition is out of space and there is no free byte left. Best, Marcel

4 3

dovecot.conf from problem installation
by Steve Matzura 22 Oct '19

22 Oct '19

*** dovecot.conf *** ## Dovecot configuration file # If you're in a hurry, see http://wiki2.dovecot.org/QuickConfiguration # "doveconf -n" command gives a clean output of the changed settings. Use it # instead of copy&pasting files when posting to the Dovecot mailing list. # '#' character and everything after it is treated as comments. Extra spaces # and tabs are ignored. If you want to use either of these explicitly, put the # value inside quotes, eg.: key = "# char and trailing whitespace " # Most (but not all) settings can be overridden by different protocols and/or # source/destination IPs by placing the settings inside sections, for example: # protocol imap { }, local 127.0.0.1 { }, remote 10.0.0.0/8 { } # Default values are shown for each setting, it's not required to uncomment # those. These are exceptions to this though: No sections (e.g. namespace {}) # or plugin settings are added by default, they're listed only as examples. # Paths are also just examples with the real defaults being based on configure # options. The paths listed here are for configure --prefix=/usr # --sysconfdir=/etc --localstatedir=/var # Enable installed protocols !include_try /usr/share/dovecot/protocols.d/*.protocol # A comma separated list of IPs or hosts where to listen in for connections. # "*" listens in all IPv4 interfaces, "::" listens in all IPv6 interfaces. # If you want to specify non-default ports or anything more complex, # edit conf.d/master.conf. #listen = *, :: # Base directory where to store runtime data. #base_dir = /var/run/dovecot/ # Name of this instance. In multi-instance setup doveadm and other commands # can use -i <instance_name> to select which instance is used (an alternative # to -c <config_path>). The instance name is also added to Dovecot processes # in ps output. #instance_name = dovecot # Greeting message for clients. #login_greeting = Dovecot ready. # Space separated list of trusted network ranges. Connections from these # IPs are allowed to override their IP addresses and ports (for logging and # for authentication checks). disable_plaintext_auth is also ignored for # these networks. Typically you'd specify your IMAP proxy servers here. #login_trusted_networks = # Space separated list of login access check sockets (e.g. tcpwrap) #login_access_sockets = # With proxy_maybe=yes if proxy destination matches any of these IPs, don't do # proxying. This isn't necessary normally, but may be useful if the destination # IP is e.g. a load balancer's IP. #auth_proxy_self = # Show more verbose process titles (in ps). Currently shows user name and # IP address. Useful for seeing who are actually using the IMAP processes # (eg. shared mailboxes or if same uid is used for multiple accounts). #verbose_proctitle = no # Should all processes be killed when Dovecot master process shuts down. # Setting this to "no" means that Dovecot can be upgraded without # forcing existing client connections to close (although that could also be # a problem if the upgrade is e.g. because of a security fix). #shutdown_clients = yes # If non-zero, run mail commands via this many connections to doveadm server, # instead of running them directly in the same process. #doveadm_worker_count = 0 # UNIX socket or host:port used for connecting to doveadm server #doveadm_socket_path = doveadm-server # Space separated list of environment variables that are preserved on Dovecot # startup and passed down to all of its child processes. You can also give # key=value pairs to always set specific settings. #import_environment = TZ ## ## Dictionary server settings ## # Dictionary can be used to store key=value lists. This is used by several # plugins. The dictionary can be accessed either directly or though a # dictionary server. The following dict block maps dictionary names to URIs # when the server is used. These can then be referenced using URIs in format # "proxy::<name>". dict { #quota = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext #expire = sqlite:/etc/dovecot/dovecot-dict-sql.conf.ext } # Most of the actual configuration gets included below. The filenames are # first sorted by their ASCII value and parsed in that order. The 00-prefixes # in filenames are intended to make it easier to understand the ordering. !include conf.d/*.conf # A config file can also tried to be included without giving an error if # it's not found: !include_try local.conf log_path = /var/log/dovecot.log passdb { driver = static args = noauthenticate temp_user=%u user=%Ln } passdb { driver = pam } passdb { driver = static args = noautenticate user=%{passdb:temp_user} skip = unauthenticated } *** End *** If I try to start the daemon, or even attempt 'dovecot -n output', I get: # 2.2.33.2 (d6601f4ec): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.21 (92477967) doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf line 107: Expecting '{' Line 107 is where the first passdb block begins. If I remove the three passdb blocks--everything below line 106--I get a clean startup, but the log looks like this: *** Begin *** Oct 22 12:22:04 auth-worker(13722): Info: pam(yourvoice(a)theglobalvoice.info,108.41.57.11,<BXn+2H6VKelsKTkL>): pam_authenticate() failed: Authentication failure (password mismatch?) (given password: redacted) Oct 22 12:22:06 auth: Debug: client passdb out: FAIL 1 user=yourvoice(a)theglobalvoice.info Oct 22 12:22:06 auth: Debug: client in: AUTH 2 PLAIN service=imap secured session=BXn+2H6VKelsKTkL lip=95.142.174.193 rip=108.41.57.11 lport=993 rport=59689 local_name=mail.theglobalvoice.info resp=AHlvdXJ2b2ljZUB0aGVnbG9iYWx2b2ljZS5pbmZvAFRoJEJvYTQxMFlu (previous base64 data may contain sensitive data) Oct 22 12:22:10 auth-worker(13722): Debug: pam(yourvoice(a)theglobalvoice.info,108.41.57.11,<BXn+2H6VKelsKTkL>): lookup service=dovecot Oct 22 12:22:10 auth-worker(13722): Debug: pam(yourvoice(a)theglobalvoice.info,108.41.57.11,<BXn+2H6VKelsKTkL>): #1/1 style=1 msg=Password: Oct 22 12:22:12 auth-worker(13722): Info: pam(yourvoice(a)theglobalvoice.info,108.41.57.11,<BXn+2H6VKelsKTkL>): pam_authenticate() failed: Authentication failure (password mismatch?) (given password: redacted) Oct 22 12:22:14 auth: Debug: client passdb out: FAIL 2 user=yourvoice(a)theglobalvoice.info Oct 22 12:22:14 imap-login: Debug: SSL alert: close notify [108.41.57.11] Oct 22 12:22:14 imap-login: Debug: SSL alert: close notify [108.41.57.11] Oct 22 12:22:14 imap-login: Info: Disconnected (auth failed, 2 attempts in 12 secs): user=<yourvoice(a)theglobalvoice.info>, method=PLAIN, rip=108.41.57.11, lip=95.142.174.193, TLS, session=<BXn+2H6VKelsKTkL>

1 0

dovecot disk space settings
by marcel bendler 22 Oct '19

22 Oct '19

Hi, is there an option to leave some disk space free? Let's say, don't store new mails if the storage mount point has less than 1% free disk space. What's the way to go? I don't want to restrict each mailbox size. It's just to prevent running out space completely. Thanks! Best regards, Marcel

4 3

More on problems with new install
by Steve Matzura 22 Oct '19

22 Oct '19

Sorry for having lost the original chain of this problem. It's been a very long day. New output from 'dovecot -n output', including the contents of dovecot.conf, conf.d/10-master.conf, conf.d/10-mail.conf and conf.d/10-ssl.conf: # 2.2.33.2 (d6601f4ec): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.21 (92477967) # OS: Linux 4.15.0-64-generic x86_64 Ubuntu 18.04.3 LTS ext4 auth_debug = yes auth_debug_passwords = yes first_valid_gid = 109 first_valid_uid = 105 last_valid_gid = 109 last_valid_uid = 105 log_path = /var/log/dovecot.log mail_debug = yes mail_gid = postfix mail_location = maildir:/var/mail/vmail/%d/%n mail_uid = postfix 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 lmtp" service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } unix_listener auth-userdb { group = postfix mode = 0666 user = postfix } } service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } process_min_avail = 0 service_count = 1 } service lmtp { unix_listener lmtp { mode = 0666 } } service pop3-login { inet_listener pop3 { port = 110 } inet_listener pop3s { port = 995 ssl = yes } } service pop3 { process_limit = 1024 } ssl = required ssl_cert = </etc/ssl/private/tgv2018.crt ssl_key = # hidden, use -P to show it userdb { driver = passwd } verbose_ssl = yes The two key files are where it says they are, although the hidden one isn't shown, it's there and properly owned and permissioned. Here's the only thing from tailing the log: Oct 22 07:24:50 master: Info: Dovecot v2.2.33.2 (d6601f4ec) starting up for imap, lmtp (core dumps disabled) This may help - from a message delivery failure email: *** Begin *** Message Delivery Failure This is an automatically generated Delivery Status Notification. Delivery to the following recipients failed permanently: * rock(a)theglobalvoice.info Reason: There was an error while attempting to deliver your message with [Subject: "Testing again"] to rock(a)theglobalvoice.info. MTA p3plsmtpa11-09.prod.phx3.secureserver.net received this response from the destination host IP - 95.142.174.193 - 550 , 550 5.1.1 <rock(a)theglobalvoice.info>: Recipient address rejected: User unknown in local recipient table . Reporting-MTA: dns; p3plsmtpa11-09.prod.phx3.secureserver.net [68.178.252.101] Received-From-MTA: dns; [192.168.1.140] [108.41.57.11] Arrival-Date: Mon, 21 Oct 2019 23:39:25 -0700 Final-recipient: rfc822; rock(a)theglobalvoice.info Diagnostic-Code: smtp; 550 5.1.1 <rock(a)theglobalvoice.info>: Recipient address rejected: User unknown in local recipient table Last-attempt-Date: Tue, 22 Oct 2019 00:23:38 -0700 Received: from [192.168.1.140] ([108.41.57.11]) by :SMTPAUTH: with ESMTPSA id MnpFiaSdxUnHgMnpFiYE6m; Mon, 21 Oct 2019 23:39:25 -0700 To: rock(a)theglobalvoice.info From: Steve Matzura <number6(a)noisynotes.com> Subject: Testing again Message-ID: <61b4f0c2-89fa-c4de-8288-871a8708f2d0(a)noisynotes.com> Date: Tue, 22 Oct 2019 02:39:26 -0400 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-CMAE-Envelope: MS4wfC8H5kkZhXB1zicGDqvcQlC1Tl3lMTOcElvh0Efz70YGRgQalgb4N6/9XVLjnqOVd5XtxwgTWuvuCEhwp/JZ2oHrdLkl4d7unSyOefbSkgcd/M5tlQn5 m+FMjUC5HJopO89WJXHQNp0ruK6VmVwHwxMAn0YDVu4FQQqVIUkN6KVyOfdC/TYD6t6vxOqv2OUxKQ== Subject: Testing again From: Steve Matzura <number6(a)noisynotes.com> Date: 10/22/2019, 2:39 AM To: rock(a)theglobalvoice.info Let's see what happens now. *** End *** There is no user 'rock', it's just a Postfix mailbox.

2 6

Problems with new installation
by Steve Matzura 22 Oct '19

22 Oct '19

I had Dovecot running very well on Ubuntu 14.04. Then I decided that since That version of Ubuntu was now out of support, I would build a new server on 18.04, which has been done. I thought I could take the old dovecot.conf and everything in conf.d that had been customized and drop it in place, and everything would just work. That has proven not to be correct. The files that had been edited were the main /etc/dovecot/dovecot.conf, and in conf.d, 10-master.conf, 10-ssl.conf, and 10-mail.conf. I have restored the original package-supplied versions of these files and restarted Dovecot, but still no one can connect. Here's my configuration, with the version number at the top: # 2.2.33.2 (d6601f4ec): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.21 (92477967) # OS: Linux 4.15.0-64-generic x86_64 Ubuntu 18.04.3 LTS auth_debug = yes auth_debug_passwords = yes mail_debug = yes mail_location = mbox:~/mail:INBOX=/var/mail/%u 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 lmtp" userdb { driver = passwd } verbose_ssl = yes The edits that were made to the aforementioned files were not actually done by me, so I can't explain why certain choices were made, except for obvious ones such as SSL key paths. But I figured the system should work at least on a vanilla configuration. Postfix is also involved in this, so the problems may not at all be with Dovecot, but with Postfix. I think I just need to draw the line between them and be able to know definitely that at least one half of the system is functioning correctly so I know I can mark that part as working, and proceed with debugging the other. My bet at this point is that it's not a Dovecot problem, but I'm not clear on how to determine this, with or without my changed files. Thanks in advance.

2 1

Dovecot v2.3.8 released
by Aki Tuomi 20 Oct '19

20 Oct '19

https://dovecot.org/releases/2.3/dovecot-2.3.8.tar.gz https://dovecot.org/releases/2.3/dovecot-2.3.8.tar.gz.sig Binary packages in https://repo.dovecot.org/ Changes + Added mail_delivery_started and mail_delivery_finished events, see https://doc.dovecot.org/admin_manual/list_of_events/ for details. + dsync-replication: Don't replicate users who have "noreplicate" extra field in userdb. + doveadm service status: Show total number of processes created. + When logging to syslog, use instance_name setting's value for the ident. This commonly is added as a log prefix. + Base64 encoding/decoding code was rewritten with additional features. It shouldn't cause any user visible changes. - v2.3.7 regression: If a folder only receives new mails without any other mail access, dovecot.index.log keeps growing forever and dovecot.index keeps being rewritten for every mail delivery. - dsync-replication may lose keywords after syncing mails restored from another replica. This only happened if the mail only had keywords and no system flags. - event filters: Non-textual event fields could not be filtered using wildcards. - auth: Scope parameter was missing from OAuth password grant request. - doveadm client-server communication may hang in some situations. It is also using unnecessarily small TCP/IP packet sizes. - doveadm who and kick did not flush protocol output correctly. - imap: SETMETADATA with literal value would delete the metadata value instead of updating it. - imap: When client issues FETCH PREVIEW (LAZY=FUZZY) command, the caching decisions should be updated so that newly saved mails will have the preview cached. - With mail_nfs_index=yes and/or mail_nfs_storage=yes setuid/setgid permission bits in some files may have become dropped with some NFS servers. Changed NFS flushing to now use chmod() instead of chown(). - quota: warnings did not work if quota root was noenforcing - acl: Global ACL file ignored the last line if it didn't end with LF. - doveadm stats dump: With JSON formatter output numbers using the number type instead of as strings - lmtp_proxy: Ensure that real_* variables are correctly set when using lmtp_proxy. - event exporter: http-post driver had hardcoded timeout and did not support DNS lookups or TLS connections. - auth: Fix user iteration to work with userdb passwd with glibc v2.28. - auth: auth service can crash if auth-policy JSON response is invalid or returned too fast. - In some rare situations "ps" output could have shown a lot of "?" characters after Dovecot process titles. - When dovecot.index.pvt is empty, an unnecessary error is logged: Error: .../dovecot.index.pvt reset, view is now inconsistent - SMTP address encoder duplicated initial double quote character when the localpart of an address ended in '..'. For example "user+..(a)example.com" became ""user+.."@example.com in a sieve redirect. --- Aki Tuomi Open-Xchange Oy

5 9

BUG: Mailbox renaming algorithm got into a potentially infinite loop, aborting
by Alex Ha 20 Oct '19

20 Oct '19

Hi all! I have two dovecot servers with dsync replication over tcp. Replication works fine except for one user. # doveadm replicator status username priority fast sync full sync success sync failed customer(a)example.com none 00:00:33 07:03:23 03:22:31 y If i run dsync manually, i get the following error message: dsync-local(customer(a)example.com): Debug: brain M: -- Mailbox renamed, restart sync -- dsync-local(customer(a)example.com): Error: BUG: Mailbox renaming algorithm got into a potentially infinite loop, aborting dsync-local(customer(a)example.com): Error: Mailbox INBOX.Foldername sync: mailbox_rename failed: Invalid mailbox name 'Foldername-temp-1': Missing namespace prefix 'INBOX.' For more info see the attached sync_loop.log Thanks for your help, Alex

3 5

Coredump v2.3.8 specific msg fetch, corrupted record in index cache, Broken physical size
by Erik de Waard 20 Oct '19

20 Oct '19

Hi, i'm getting a coredump on a specific msg, i've attached the gdb. file on disk i noticed W=<vsize> is missing. 1571209735.M744550P1608.rwvirtual65,S=15886:2,S Best regards, mail.log Oct 18 14:41:39 rwvirtual10 dovecot: imap(johndoe(a)company.nl)<15868><qjTFpy6VPsMKAAok>: Error: Mailbox INBOX.Debug: UID=1041: read(/data/mail/ company.nl/users/johndoe/Maildir/.Debug/cur/1571209735.M744550P1608.rwvirtual65,S=15886:2,S) failed: Cached message size smaller than expected (15886 < 16367, box=INBOX.Debug, UID=1041) (read reason=mail stream) Oct 18 14:41:39 rwvirtual10 dovecot: imap(johndoe(a)company.nl)<15868><qjTFpy6VPsMKAAok>: Error: Corrupted record in index cache file /data/indexes/ johndoe(a)company.nl/.Debug/dovecot.index.cache: UID 1041: Broken physical size in mailbox INBOX.Debug: read(/data/mail/ company.nl/users/johndoe/Maildir/.Debug/cur/1571209735.M744550P1608.rwvirtual65,S=15886:2,S) failed: Cached message size smaller than expected (15886 < 16367, box=INBOX.Debug, UID=1041) Oct 18 14:41:39 rwvirtual10 dovecot: imap(johndoe(a)company.nl)<15868><qjTFpy6VPsMKAAok>: Panic: file istream.c: line 315 (i_stream_read_memarea): assertion failed: (old_size <= _stream->pos - _stream->skip) Oct 18 14:41:39 rwvirtual10 dovecot: imap(johndoe(a)company.nl)<15868><qjTFpy6VPsMKAAok>: Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0xe5c31) [0x7f5237d8cc31] -> /usr/lib/dovecot/libdovecot.so.0(+0xe5cd1) [0x7f5237d8ccd1] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f5237ce4103] -> /usr/lib/dovecot/libdovecot.so.0(i_stream_read_memarea+0x300) [0x7f5237d9abd0] -> /usr/lib/dovecot/libdovecot.so.0(i_stream_read+0x35) [0x7f5237d9aca5] -> /usr/lib/dovecot/libdovecot.so.0(i_stream_read_data+0x3d) [0x7f5237d9b64d] -> /usr/lib/dovecot/libdovecot.so.0(+0xc4da1) [0x7f5237d6bda1] -> /usr/lib/dovecot/libdovecot.so.0(+0xc5d4b) [0x7f5237d6cd4b] -> /usr/lib/dovecot/libdovecot.so.0(message_parser_parse_next_block+0x65) [0x7f5237d6da05] -> /usr/lib/dovecot/libdovecot.so.0(message_parser_parse_body+0x31) [0x7f5237d6dcf1] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xc19d4) [0x7f52381099d4] -> /usr/lib/dovecot/libdovecot-storage.so.0(index_mail_init_stream+0x3aa) [0x7f5238109e9a] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0x74b25) [0x7f52380bcb25] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_get_stream_because+0x70) [0x7f52380833a0] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0x748d7) [0x7f52380bc8d7] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_get_virtual_size+0x44) [0x7f5238082ea4] -> dovecot/imap [johndoe(a)company.nl 10.0.10.36 FETCH](+0x21523) [0x561f6425f523] -> dovecot/imap [johndoe(a)company.nl 10.0.10.36 FETCH](+0x1f759) [0x561f6425d759] -> dovecot/imap [ johndoe(a)company.nl 10.0.10.36 FETCH](imap_fetch_more+0x39) [0x561f6425eb99] -> dovecot/imap [johndoe(a)company.nl 10.0.10.36 FETCH](cmd_fetch+0x342) [0x561f6424ef32] -> dovecot/imap [johndoe(a)company.nl 10.0.10.36 FETCH](command_exec+0x7c) [0x561f6425bb0c] -> dovecot/imap [ johndoe(a)company.nl 10.0.10.36 FETCH](+0x1bb72) [0x561f64259b72] -> dovecot/imap [johndoe(a)company.nl 10.0.10.36 FETCH](+0x1bc04) [0x561f64259c04] -> dovecot/imap [johndoe(a)company.nl 10.0.10.36 FETCH](client_handle_input+0x1a5) [0x561f6425a025] -> dovecot/imap [ johndoe(a)company.nl 10.0.10.36 FETCH](client_input+0x82) [0x561f6425a6c2] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x75) [0x7f5237da6845] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x11b) [0x7f5237da825b] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x59) [0x7f5237da6959] Oct 18 14:41:39 rwvirtual10 dovecot: imap(johndoe(a)company.nl)<15868><qjTFpy6VPsMKAAok>: Fatal: master: service(imap): child 15868 killed with signal 6 (core dumps disabled - https://dovecot.org/bugreport.html#coredumps)

2 2

dovecot 2.3.7.2-1~bionic: Performance issues caused by excessive IO to ~/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.tmp
by Ralf Hildebrandt 16 Oct '19

16 Oct '19

I set up system copying all mails to a backup system. This used to work without a hitch - now in the last few days mails would pile up in the Postfix Queue, waiting to be delivered using the lmtp transport into dovecot. So dovecot was being slow, but why? After all, nothing changed. After reading some articles on stackoverflow I found a way of finding out which file gets the most IO: % sysdig -c topfiles_bytes; This command quickly pointed to ~/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.tmp That file was written excessively. I then put ~/mdbox/mailboxes/INBOX/dbox-Mails/ into tmpfs and alas, the queue would drain quickly. But why is that? Why would the index file be updated so often? This is dovecot 2.3.7.2-1~bionic # 2.3.7.2 (3c910f64b): /etc/dovecot/dovecot.conf # OS: Linux 5.0.0-29-generic x86_64 Ubuntu 18.04.3 LTS default_vsz_limit = 2 G lmtp_user_concurrency_limit = 10000 mail_attachment_dir = /home/copymail/attachments mail_attachment_hash = %{sha256} mail_fsync = never mail_location = mdbox:~/mdbox mail_plugins = zlib fts fts_lucene mdbox_rotate_size = 128 M namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { args = username_format=%u /etc/dovecot/passwd driver = passwd-file } plugin { fts = lucene fts_languages = de,en fts_lucene = whitespace_chars=@. } protocols = " imap lmtp" service imap-login { inet_listener imap { address = 127.0.0.1 port = 143 } inet_listener imaps { port = 993 ssl = yes } } service lmtp { inet_listener lmtp { address = 10.0.5.208 port = 1025 } process_min_avail = 5 unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0660 user = postfix } } ssl_ca = /etc/ssl/certs/ca-certificates.crt ssl_cert = </etc/ssl/certs/mail-cbf.pem ssl_cipher_list = EECDH+ECDSA+AESGCM:EECDH+aRSA+AESGCM:EECDH+ECDSA+SHA384:EECDH+ECDSA+SHA256:EECDH+aRSA+SHA384:EECDH+aRSA+SHA256:EECDH+aRSA+RC4:EECDH:EDH+aRSA:!aNULL:!eNULL:!LOW:!3DES:!MD5:!EXP:!PSK:!SRP:!DSS:!RC4 ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it ssl_prefer_server_ciphers = yes userdb { args = username_format=%u /etc/dovecot/passwd driver = passwd-file } protocol lmtp { mail_plugins = zlib fts fts_lucene } -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebrandt(a)charite.de | https://www.charite.de

3 9

Vacation Fcc
by Gregory Heytings 14 Oct '19

14 Oct '19

Hi list, I use Dovecot's Pigeonhole Sieve implementation, and there is one little feature I'm missing: When a vacation message is sent, I'd like to keep a copy of that message in my "sent" mailbox. There is an RFC draft (draft-ietf-extra-sieve-fcc-09) for this, which adds a ":fcc" argument to vacation, but apparently it's not supported by Pigeonhole. I have two questions: Will ":fcc" be supported in the future? In the meantime (or if supporting ":fcc" is not planned), is it possible to achieve the same result with the existing Sieve extensions? (I can imagine a way to do this at the MTA level by checking the presence of the "Auto-Submitted:" header, but did not test it.) Thanks, Gregory

2 3

Sieve replication - Debian 9.11 - Dovecot 2.2.7 - script changes not replicated
by Daniel Botting 14 Oct '19

14 Oct '19

Hi, I am trying to setup Sieve replication, it is almost working: 1/ Create a script - sync'd across 2/ Activate/de-activate a script - change sync'd 3/ Delete a script - change sync'd But if I make a change to a script it is not replicated, unless I de-activate and activate again. I am seeing in the logs the below during this process (de-activating/activating): Oct 9 17:01:39 hostname dovecot: dsync-local(a_user): Debug: doveadm-sieve: Iterating Sieve mailbox attribute: vendor/vendor.dovecot/pvt/server/sieve/files/0910-active-1640 Oct 9 17:01:39 hostname dovecot: dsync-local(a_user): Debug: doveadm-sieve: Value missing for key `vendor/vendor.dovecot/pvt/server/sieve/default' (last change: 2019-10-09 17:01:37) # 2.2.27 (c0f36b0): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.16 (fed8554) # OS: Linux 4.9.0-3-amd64 x86_64 Debian 9.11 auth_debug = yes auth_debug_passwords = yes auth_verbose = yes default_vsz_limit = 0 doveadm_password = # hidden, use -P to show it first_valid_gid = 8 first_valid_uid = 8 last_valid_gid = 8 last_valid_uid = 8 lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes mail_debug = yes mail_gid = 8 mail_location = maildir:~/Maildir mail_plugins = " notify replication" mail_uid = 8 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 imapflags namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } plugin { mail_replica = tcps:replication_server_url:port_number sieve = ~/.dovecot.sieve sieve_dir = ~/sieve sieve_extensions = +editheader +imapflags } protocols = " imap sieve pop3" replication_max_conns = 4 service aggregator { fifo_listener replication-notify-fifo { user = mail } unix_listener replication-notify { user = mail } } service auth { unix_listener /var/run/dovecot-exim-bridge { mode = 0660 user = Debian-exim } } service doveadm { inet_listener { port = 12345 ssl = yes } } service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } process_limit = 512 process_min_avail = 4 service_count = 1 } service imap { process_limit = 1024 } service managesieve-login { inet_listener sieve { port = 4190 } process_min_avail = 1 service_count = 8 vsz_limit = 256 M } service managesieve { process_limit = 1024 } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { mode = 0666 } } ssl = required ssl_cert = </path/certs/a_domain/fullchain.pem ssl_client_ca_dir = /etc/ssl/certs ssl_key = # hidden, use -P to show it userdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap override_fields = home=/var/mail/%u uid=mail gid=mail } verbose_ssl = yes protocol lda { mail_plugins = " notify replication sieve" } protocol imap { mail_max_userip_connections = 32 mail_plugins = " notify replication" } protocol sieve { mail_max_userip_connections = 10 managesieve_logout_format = bytes=%i/%o managesieve_max_line_length = 65536 } Kind regards -- Daniel Botting

2 1

Password issue
by ＠lbutlr 13 Oct '19

13 Oct '19

One of my accounts was having login failures when trying to send mail, but was able to check mail. I tried everything I could think of to see what the issue might be, but eventually went in and reset the password in the sql database (I knew the password, so I reset it to the same password). {SHA256-CRYPT}$5$VuS… {SHA256-CRYPT}$5$VI7… So the password was updated properly. Clients can still login to check mail, but are failing to send mail, so the password was not the issue. First, logins in to check mail and succeeds > Oct 09 16:02:16 imap-login: Info: Login: user=<myuser(a)covisp.net>, xx.xx.xx.xx, PLAIN, TLS Sends device MUA info > Oct 09 16:02:16 imap(myuser(a)covisp.net)<84553><bP4acIGUJttJDqGg>: Info: ID sent: name=iPad Mail, version=17A860, os=iOS, os-version=13.1.2 (17A860) Fails to send mail > Oct 09 16:02:50 imap-login: Info: Aborted login (auth failed, 5 attempts in 33 secs): user=<myuser(a)covisp.net>, xx.xx.xx.xx, PLAIN, TLS Postfix logs "Client host rejected: Access denied” but as I said, other accounts can submit and there’s nothing special in the submission service in master.cf. Passwords are all copied/pasted so identical in both IMAP (p993) and SMTP (p587) settings. Settings for the SMTP server are identical to the other accounts using the same server. I don’t know how to login to IMAP via the openssl command line interface, but this is what happens when I login to the submission port.  % openssl s_client -connect mail.covisp.net:587 -starttls smtp … auth login 334 VXNlcm5hbWU6 base64(username)= 334 UGFzc3dvcmQ6 base64(pasword)= DONE (Same results without the terminating ‘=‘) I’m sure I am missing something really obvious? -- Lithium will no longer be available on credit

6 12

Error: SSL_accept() syscall failed
by C. James Ervin 11 Oct '19

11 Oct '19

In setting up my new mail server, I am getting the following in the logs: Oct 11 07:10:59 kumo dovecot[5704]: imap-login: Disconnected (no auth attempts in 0 secs): user=<>, rip=24.53.79.10, lip=172.26.12.90, *TLS handshaking: SSL_accept() syscall failed: Success*, session=<B9OokqCUD+UYNU8K> I have tried various ssl_protocols entries, but for now have defaulted back to ssl_protocols = !SSLv3 (the "out of the box" setting). The certificate (ssl_cert = </etc/ssl/certs/certificate_and_key.crt) is valid and the same one used by postfix. However, I belive the error appeared only after removing the self signed certificate and installing the one I purchased. Warning: though I was a sysadmin a long long time, it has been a while! I have not run a mail server in 15 years, but am moving my mail back "in-house" as I approach retirement! I searched for a forum where I could post this issue, but only found this list. # 2.2.33.2 (d6601f4ec): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.21 (92477967) # OS: Linux 4.15.0-1051-aws x86_64 Ubuntu 18.04.1 LTS auth_mechanisms = plain login mail_location = maildir:~/Maildir 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 mime foreverypart extracttext namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { driver = pam } plugin { sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } protocols = " imap sieve pop3" service auth { unix_listener /var/spool/postfix/private/dovecot-auth { group = postfix mode = 0660 user = postfix } } ssl_cert = </etc/ssl/certs/certificate_and_key.crt ssl_cipher_list = ALL:!ADH:!LOW:!EXP:!aNULL:+HIGH:+MEDIUM ssl_client_ca_dir = /etc/ssl/certs ssl_key = # hidden, use -P to show it userdb { driver = passwd } protocol lda { deliver_log_format = msgid=%m: %$ mail_plugins = sieve postmaster_address = postmaster quota_full_tempfail = yes rejection_reason = Your message to <%t> was automatically rejected:%n%r } protocol imap { imap_client_workarounds = delay-newmail mail_max_userip_connections = 10 } protocol pop3 { mail_max_userip_connections = 10 pop3_client_workarounds = outlook-no-nuls oe-ns-eoh }

3 3

Re: Broken link on doc.dovecot.org
by Karen Woodman 11 Oct '19

11 Oct '19

Hi again, I wanted to check in and see if you got my note about the broken link on your site. Thanks! Karen On Monday, October 7, 2019 at 5:05 PM, Karen Woodman <karen(a)getmailbird.co> wrote: > Hi there, > > I noticed that you have a broken link to a website called Qmail.org. That > site was first published 23 years ago (back in 1996!) but unfortunately, it > is no longer a working website. > > You link to Qmail.org on this page: > https://doc.dovecot.org/configuration_manual/authentication/checkpassword/ > > We just published an article that explores what happened to the site. I think > it's an interesting story, and it could be useful to your readers. > > In addition, since all of the original articles are gone, we included a > curated list of the best Qmail resources and mirrors. > > Here's the article if you want to take a look: > https://www.getmailbird.com/what-resources-are-available-now-that-qmail-org… > > Would you consider swapping out the broken link for our article? > > Please let me know if you have any questions and thank you for your time. > > Sincerely, > -Karen > > -- > Karen Woodman, Editor > 5 Ross Rd > Durham, NH 03824 > > By the way, if you didn't like getting this email you can unsubscribe > <http://ec2-52-26-194-35.us-west-2.compute.amazonaws.com/x/u?u=df0298ca-a3e4…> and > I won't email you anymore. :) >

2 1

Using maldet
by Ignacio García 10 Oct '19

10 Oct '19

Hi there. Sometimes I notice that some malware gets through amavis+clamav+postfix and lands in the user's maildir files. I wonder if it would make sense, or even if it would be advisable to scan and clean those files using a program as maldet Thanks for your help. Ignacio

1 0

Case sensitivity in :addresses in sieve vacation scripts
by Julian Kippels 10 Oct '19

10 Oct '19

Hi, I have recently updated from Dovecot 2.2 to 2.3. Since I have noticed that vacation responses from sieve are not working the same anymore. For example, my sieve script looks like this: vacation :days 1 :addresses ["Kippels(a)hhu.de","julian.kippels(a)hhu.de"] it used to be that I got a vacation response if I sent a mail to kippels(a)hhu.de and Kippels(a)hhu.de. Now I only get a response for Kippels(a)hhu.de, not for kippels(a)hhu.de. I cant say for sure, but I suppose this behaviour changed with the update. If not, why could this have happened? And in any case, how can I enable case insensitivity? Thanks Julian

2 2

Show messages within 60 days
by jacky HU 10 Oct '19

10 Oct '19

Hello, Can my inbox be set up, for example, only for messages within 60 days? I don't want to create a new virtual mailbox. Can anyone help me?

2 1

Dovecot core debug
by MediumDave 10 Oct '19

10 Oct '19

Hi all, I have a Dovecot core that I am trying to track down, in an attempt to replicate so I can log a bug report, and am hoping others might be able to help me as I’m reaching my limit. My working theory is that two user sessions are active at the same time, one of the sessions is “mid-search” (or perhaps in idle state) on a virtual folder where the number of results is zero (due to a null results array), when another session either performs an append or perhaps a new message arrives in the virtual view and qualifies for the search. It seems that the current list of UID’s in the search results is zero (null), and new messages are being appended to the search results, which results in a divide by zero. But I have not been able to create a scenario to replicate this on my test box, but is occurring regularly (every hour or so) on my mail server. I have been able to replicate on my test box using a single account by performing many random operations over and over again, with multiple sessions, but took over 24 hours and I can’t isolate the action that caused it. Dovecot version is 2.2.36 (1f10bfa63) as shipped with Centos 7 (latest update). If I can reproduce, I can then test the latest 2.3 and see if this is still a problem in that version. Here is the full back trace: #0 0x00007f8d40636e58 in array_count_i (array=0x557be80cc168) at array.h:155 No locals. #1 array_get_i (count_r=<synthetic pointer>, array=0x557be80cc168) at array.h:209 No locals. #2 seq_range_lookup (array=0x557be80cc168, seq=2222, idx_r=0x7ffead4141d4) at seq-range-array.c:14 data = <optimized out> idx = <optimized out> left_idx = <optimized out> right_idx = <optimized out> count = <optimized out> #3 0x00007f8d406379ae in seq_range_exists (array=array@entry=0x557be80cc168, seq=seq@entry=2222) at seq-range-array.c:391 idx = 32766 #4 0x00007f8d408fd3d9 in mailbox_search_result_add (result=result@entry=0x557be80cc150, uid=2222) at mailbox-search-result.c:121 __FUNCTION__ = "mailbox_search_result_add" #5 0x00007f8d40962f30 in index_search_result_update_appends (result=result@entry=0x557be80cc150, old_messages_count=<optimized out>) at index-search-result.c:168 t = 0x557be7fb1820 search_ctx = 0x557be7fef860 mail = 0x557be8100198 search_arg = {next = 0x557be7fab460, type = SEARCH_SEQSET, value = {subargs = 0x0, seqset = {arr = {buffer = 0x557be7f69208, element_size = 8}, v = 0x557be7f69208, v_modifiable = 0x557be7f69208}, str = 0x0, time = 0, size = 0, flags = 0, search_flags = (unknown: 0), date_type = 0, thread_type = MAIL_THREAD_NONE, modseq = 0x0, search_result = 0x0, mime_part = 0x0}, initialized = {search_args = 0x0, keywords = 0x0, mailbox_glob = 0x0}, context = 0x0, hdr_field_name = 0x0, match_not = 0, match_always = 0, nonmatch_always = 0, fuzzy = 0, no_fts = 0, result = -1} message_count = 2008 ret = <optimized out> __FUNCTION__ = "index_search_result_update_appends" #6 0x00007f8d4096dc37 in search_result_update (result=0x557be80cc150, ctx=0x557be7ff8950) at index-sync-search.c:78 No locals. #7 index_sync_search_results_update (ctx=ctx@entry=0x557be7ff8950) at index-sync-search.c:88 results = 0x557be7f9d480 i = <optimized out> count = <optimized out> #8 0x00007f8d4096e4b4 in index_mailbox_sync_deinit (_ctx=0x557be7ff8950, status_r=0x557be7ff0108) at index-sync.c:353 ctx = 0x557be7ff8950 sync_rec = {seq1 = 0, seq2 = 0, type = MAILBOX_SYNC_TYPE_EXPUNGE} delayed_expunges = false ret = <optimized out> #9 0x00007f8d40950400 in mailbox_list_index_sync_deinit (ctx=0x557be7ff8950, status_r=0x557be7ff0108) at mailbox-list-index.c:976 ---Type <return> to continue, or q <return> to quit--- ibox = 0x557be7fd0bf0 box = 0x557be7f9d078 #10 0x00007f8d408ed568 in mailbox_sync_deinit (_ctx=<optimized out>, status_r=<optimized out>) at mail-storage.c:1953 ctx = <optimized out> box = <optimized out> errormsg = <optimized out> error = MAIL_ERROR_NONE ret = <optimized out> #11 0x0000557be6613431 in imap_sync_finish (ctx=ctx@entry=0x557be7ff0090, aborting=aborting@entry=false) at imap-sync.c:279 client = 0x557be7f8a6d8 ret = 0 #12 0x0000557be6613fed in imap_sync_more (ctx=0x557be7ff0090) at imap-sync.c:594 str = <optimized out> ret = 1 __FUNCTION__ = "imap_sync_more" #13 0x0000557be6614676 in cmd_sync_continue (sync_cmd=0x557be7f8be88) at imap-sync.c:629 cmd = 0x557be7f75e40 prev = <optimized out> client = 0x557be7f8a6d8 ctx = 0x557be7ff0090 ret = <optimized out> __FUNCTION__ = "cmd_sync_continue" #14 0x0000557be6614b34 in cmd_sync_client (sync_cmd=0x557be7f8be88) at imap-sync.c:720 ctx = <optimized out> flags = <optimized out> client = 0x557be7f8a6d8 imap_flags = <optimized out> no_newmail = <optimized out> #15 cmd_sync_delayed_real (client=0x557be7f8a6d8) at imap-sync.c:833 cmd = <optimized out> first_expunge = <optimized out> first_nonexpunge = <optimized out> #16 cmd_sync_delayed (client=client@entry=0x557be7f8a6d8) at imap-sync.c:841 _data_stack_cur_id = 3 #17 0x0000557be6607a18 in client_handle_input (client=client@entry=0x557be7f8a6d8) at imap-client.c:1233 remove_io = <optimized out> handled_commands = <optimized out> __FUNCTION__ = "client_handle_input" #18 0x0000557be6607eb5 in client_input (client=0x557be7f8a6d8) at imap-client.c:1264 ---Type <return> to continue, or q <return> to quit--- cmd = 0xcfee4 output = 0x557be7f8bd90 bytes = 2052 __FUNCTION__ = "client_input" #19 0x00007f8d40624be2 in io_loop_call_io (io=0x557be7f84cb0) at ioloop.c:600 ioloop = 0x557be7f719c0 t_id = 2 __FUNCTION__ = "io_loop_call_io" #20 0x00007f8d406262cf in io_loop_handler_run_internal (ioloop=ioloop@entry=0x557be7f719c0) at ioloop-epoll.c:223 ctx = 0x557be7f734e0 events = <optimized out> list = 0x557be7f74f40 io = <optimized out> tv = {tv_sec = 1795, tv_usec = 114881} events_count = <optimized out> msecs = <optimized out> ret = 1 i = 0 call = <optimized out> __FUNCTION__ = "io_loop_handler_run_internal" #21 0x00007f8d40624c7c in io_loop_handler_run (ioloop=ioloop@entry=0x557be7f719c0) at ioloop.c:649 No locals. #22 0x00007f8d40624e38 in io_loop_run (ioloop=0x557be7f719c0) at ioloop.c:624 __FUNCTION__ = "io_loop_run" #23 0x00007f8d405a9c03 in master_service_run (service=0x557be7f71860, callback=callback@entry=0x557be6614e30 <client_connected>) at master-service.c:724 No locals. #24 0x0000557be65fa262 in main (argc=1, argv=0x557be7f715f0) at main.c:484 set_roots = {0x557be6825700 <imap_setting_parser_info>, 0x7f8d40df95a0, 0x0} login_set = {auth_socket_path = 0x557be7f69048 "\001", postlogin_socket_path = 0x0, postlogin_timeout_secs = 60, callback = 0x557be6615600 <login_client_connected>, failure_callback = 0x557be6614f40 <login_client_failed>, request_auth_token = 1} service_flags = <optimized out> storage_service_flags = <optimized out> username = 0x0 auth_socket_path = <optimized out> c = <optimized out> And the output of array in frame #0: (gdb) f 0 #0 0x00007f8d40636e58 in array_count_i (array=0x557be80cc168) at array.h:155 155 return array->buffer->used / array->element_size; (gdb) p *array $2 = {buffer = 0x0, element_size = 0} Here is the virtual folder config in use: # cat /etc/dovecot/virtual/combined/dovecot-virtual !INBOX INBOX/Sent INBOX/Drafts all Any help would be greatly appreciated in diagnosing the cause here. Thanks, Dave

1 0

Panic at "doveadm backup" (mailbox_symlink_exists): assertion failed: (ret > 0)
by Alex La 09 Oct '19

09 Oct '19

Hi. I try to sync from a dovecot server to another server via the following command. doveadm -D -o mail_fsync=never -o imapc_user=info(a)DOMAIN.COM -o imapc_password='PASS' backup -R -u info(a)DOMAIN.COM imapc: After some short runtime I get the following panic. ``` dsync(info(a)DOMAIN.COM): Panic: file mailbox-alias-plugin.c: line 77 (mailbox_symlink_exists): assertion failed: (ret > 0) dsync(info(a)DOMAIN.COM): Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(+0xa17ce) [0x7ff2f4da77ce] -> /usr/lib64/dovecot/libdovecot.so.0(default_fatal_handler+0x2a) [0x7ff2f4da783a] -> /usr/lib64/dovecot/libdovecot.so.0(i_fatal+0) [0x7ff2f4d36dd7] -> /usr/lib64/dovecot/lib20_mailbox_alias_plugin.so(+0x133e) [0x7ff2f3afa33e] -> /usr/lib64/dovecot/lib20_mailbox_alias_plugin.so(+0x14d4) [0x7ff2f3afa4d4] -> /usr/lib64/dovecot/lib01_acl_plugin.so(+0xf2aa) [0x7ff2f432a2aa] -> /usr/lib64/dovecot/lib01_acl_plugin.so(+0xf908) [0x7ff2f432a908] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mailbox_list_iter_next+0x44) [0x7ff2f50ec5e4] -> doveadm(dsync_mailbox_tree_fill+0x19b) [0x558004586e5b] -> doveadm(dsync_brain_mailbox_trees_init+0x124) [0x55800457b204] -> doveadm(dsync_brain_run+0x3d7) [0x558004578317] -> doveadm(+0x29b71) [0x55800455eb71] -> doveadm(+0x2bd2c) [0x558004560d2c] -> doveadm(+0x2c92a) [0x55800456192a] -> doveadm(doveadm_mail_try_run+0x215) [0x558004562285] -> doveadm(main+0x46a) [0x5580045513fa] -> /lib64/libc.so.6(__libc_start_main+0xf5) [0x7ff2f495a505] -> doveadm(+0x1c565) [0x558004551565] ``` There is this message in the archive wich mention that similar directory names could be a problem. https://dovecot.org/list/dovecot/2016-December/106528.html I have cleanuped the similar directories but I still get the panic. This are the main folders in the Account ``` ... some custom folders =Trash =Sent Messages =Junk =Drafts =Coaching =Archiv =INBOX ``` Dovecot version # 2.2.36.4 (baf9232c1): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.24.2 (aaba65b7) # OS: Linux 3.10.0-1062.1.2.el7.x86_64 x86_64 CentOS Linux release 7.7.1908 (Core) Thanks for any help Regards Alex

1 0

Recommendations for shared storage
by Dan 09 Oct '19

09 Oct '19

Hello all, This email is by no means an "Educate me step by step" query, But more of an inquiry about which direction to go based on your experience. I've been working with Dovecot for some years now, so the configuration of that piece is no stranger. However, Choosing the right style of shared storage has proven to be somewhat of a challenge. A bit of background of what I need to provide service for: ~80,000 users, that will potentially grow throughout the future ~100 unique domains Ability to scale horizontally. As resources grow, adding a node (or group of nodes) with the exact configuration as the other nodes. Director should be able to send the connection to a node that has the same data as it's neighbors, Allowing high availability. What I've experimented with so far: _Server pairs, using dsync to replicate data between the nodes - Director to send users to a specific pair (director_tag returned from passdb) _ Pros: - Easy way to replicate data, without the need for external tools Cons: - Limited to one pair of nodes - dsync doesn't replicate all sieve files, for example, one file that tracks out of office replies has not been replicated in my experience _NFS storage managed by corosync and pacemaker - Director to send users to any backend _ Pros: - One location for all data. New nodes that get stood up will be easy to configure Cons: - Complex to set up In your experience, what did you choose for mail storage? Thanks.

1 0

Buster packages available
by Aki Tuomi 09 Oct '19

09 Oct '19

Hi! We have now buster packages available starting from 2.3.8. You can find them from https://repo.dovecot.org/ In related news, we are planning on dropping packages for Debian Jessie, Ubuntu 18 and CentOS6 starting from 2.3.9. --- Aki Tuomi Open-Xchange oy

2 2

CentOS 8 / 7
by Günther J. Niederwimmer 08 Oct '19

08 Oct '19

Hello List, I have to install a "new" system, what is the best way for this. I like to install a CentOS System but I only found dovecot for CentOS 7 is this compatible for CentOS 8 or have I to setup a CentOS 7 System ? The onboard dovecot is 2.2.36-5 :-( Thanks for a answer, -- mit freundlichen Grüßen / best regards Günther J. Niederwimmer

3 2

Pigeonhole v0.5.8 released
by Aki Tuomi 08 Oct '19

08 Oct '19

https://pigeonhole.dovecot.org/releases/2.3/dovecot-2.3-pigeonhole-0.5.8.ta… https://pigeonhole.dovecot.org/releases/2.3/dovecot-2.3-pigeonhole-0.5.8.ta… Binary packages in https://repo.dovecot.org/ Changes - Sieve may leak resources in rare cases when a redirect, vacation or report action fails to send the message. This mainly applies when Sieve is executed in IMAP context; i.e., for the IMAPSIEVE or FILTER=SIEVE capabilities. --- Aki Tuomi Open-Xchange Oy

1 0

ITERINDEX not showing subfolders.
by Erik de Waard 08 Oct '19

08 Oct '19

# 2.3.4.1 (f79e8e7e4): /etc/dovecot/dovecot.conf Hello, we're using mail on NFS and the indexes on localdisk, with a director setup. (18K+ users) now to get more performance i thought to use the ITERINDEX option. however this has the side-effect on some mailboxes that it doesn't show the subfolders under INBOX. they seem 'disappeared'. Removing the ITERINDEX option fixes this again. Deleting the local indexes to be recreated doesn't solve the problem. What could cause this? and how to fix it. # 2.3.4.1 (f79e8e7e4): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.4 () # OS: Linux 4.9.0-11-amd64 x86_64 Debian 9.11 # Hostname: somemail.host.domain auth_cache_negative_ttl = 0 auth_cache_size = 10 M auth_cache_ttl = 1 days auth_username_chars = "abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@#" default_client_limit = 1500 default_vsz_limit = 1 G disable_plaintext_auth = no info_log_path = /dev/null listen = * log_timestamp = "%Y-%m-%d %H:%M:%S " login_trusted_networks = 10.0.10.0/24 mail_fsync = never mail_max_userip_connections = 100 mail_prefetch_count = 10 mail_privileged_group = mail mailbox_list_index_include_inbox = yes 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 = INBOX. separator = . type = private } passdb { args = username_format=%{rip} /etc/dovecot/passdb default_fields = noauthenticate=y driver = passwd-file } passdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } plugin { sieve_execute_bin_dir = /etc/dovecot/sieve-executables sieve_global_extensions = +vnd.dovecot.execute sieve_plugins = sieve_extprograms } protocols = imap lmtp service anvil { unix_listener anvil-auth-penalty { mode = 0600 } } service auth { user = root } service imap-login { client_limit = 6000 process_limit = 4 process_min_avail = 4 service_count = 0 vsz_limit = 600 M } service imap { client_limit = 1 process_limit = 1024 service_count = 50 } service lmtp { inet_listener lmtp { port = 24 } } ssl = no ssl_cert = </etc/dovecot/dovecot.crt ssl_key = # hidden, use -P to show it userdb { driver = prefetch } userdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } verbose_proctitle = yes protocol lmtp { mail_fsync = optimized mail_plugins = " sieve" plugin { sieve = ~/filters.sieve sieve_after = /etc/dovecot/sieve/after.sieve sieve_before = /etc/dovecot/sieve/before.sieve } userdb { args = /etc/dovecot/dovecot-sql-lmtp.conf driver = sql name = } } dovecot-sql.conf driver = mysql connect = host=10.0.10.150 dbname=maildb user=mail password=5ecret! default_pass_scheme = SHA password_query = select login as user, crypt_sha1 as password, home as userdb_home, uid AS userdb_uid, gid AS userdb_gid, concat('maildir:',maildir,':INDEX=/data/indexes/',login,':ITERINDEX',':VOLATILEDIR=/data/indexes/',login) as userdb_mail from mailbox left join aliases on aliases.systemid = aliasid where login = '%u' and inactive = 0; user_query = select home, maildir as mail, uid, gid from mailbox left join aliases on aliases.systemid = aliasid where login = '%u' and inactive = 0; iterate_query = select distinct login as user from mailbox;

2 1

Is imap "list" required before imap "select" for shared folder?
by Gene Smith 08 Oct '19

08 Oct '19

I set up a shared mailbox with dovecot and it basically works. However, before I can imap SELECT or STATUS the shared mailbox I have to first do an imap LIST, i.e, . list "" * If list is not done first, the imap select or status command on the shared mailbox results in a "NO" response with "mailbox doesn't exist" response text. I can provide more information if this is not expected behavior. -gene

2 2

Sieve redirect is broken in 2.3.7.2 - signal 11
by Demonhost 07 Oct '19

07 Oct '19

Hi, If we use sieve redirect under dovecot 2.3.7.2 we end up with Oct 04 03:30:31 dockerhost docker[12154]: 2019-10-04T03:30:31 53ac2ae27650 postfix: 0605F207B0F36: to=<xxxx(a)xxxx.xx>, relay=127.0.0.1[127.0.0.1]:10024, delay=1.5, delays=0.36/0/0/1.1, dsn=2.0.0, status=sent (250 2.0.0 from MTA(smtp:[127.0.0.1]:10025): 250 2.0.0 Ok: queued as 6FC89207B0F38) Oct 04 03:30:31 dockerhost docker[12154]: 2019-10-04T03:30:31 53ac2ae27650 postfix: 6FC89207B0F38: to=<xxxx(a)xxxx.xx>, relay=dovecot, delay=0.31, delays=0.05/0/0/0.26, dsn=4.3.0, status=deferred (Command died with signal 11: "/usr/libexec/dovecot/dovecot-lda") Using docker with official alpine image. / # cat /etc/alpine-release 3.8.4 / # apk info -v | grep dovecot WARNING: Ignoring APKINDEX.adfa7ceb.tar.gz: No such file or directory WARNING: Ignoring APKINDEX.efaa1f73.tar.gz: No such file or directory dovecot-2.3.7.2-r0 dovecot-fts-solr-2.3.7.2-r0 dovecot-ldap-2.3.7.2-r0 dovecot-pigeonhole-plugin-2.3.7.2-r0 dovecot-pigeonhole-plugin-ldap-2.3.7.2-r0 Sieve rule is: # rule:[test] if header :contains "subject" "test" { redirect "testemail(a)gmail.com"; } In host's dmesg we found the following: [213184.882341] traps: dovecot-lda[6128] general protection ip:7ff6cf8144f7 sp:7fff5f800b30 error:0 in libdovecot.so.0.0.0[7ff6cf724000+360000] Sorry, not knowledgeable enough on how to do the GBD debug. ----------------- We went back to previous version and issue disappeared. 8b45bb255b67:/# cat /etc/alpine-release 3.8.4 8b45bb255b67:/# apk info -v | grep dovecot WARNING: Ignoring APKINDEX.adfa7ceb.tar.gz: No such file or directory WARNING: Ignoring APKINDEX.efaa1f73.tar.gz: No such file or directory dovecot-2.3.6-r0 dovecot-fts-solr-2.3.6-r0 dovecot-ldap-2.3.6-r0 dovecot-pigeonhole-plugin-2.3.6-r0 dovecot-pigeonhole-plugin-ldap-2.3.6-r0 Anyone else already had this problem or you know how to fix it? Thanks in advance.

2 10

Dovecot proxying to some backend using LOGIN proxy_mech
by Sébastien Riccio 06 Oct '19

06 Oct '19

Hello list, I am currently testing a setup for a PoC wit this configuration. - 1 x Frontend dovecot for proxying IMAP/POP3/LMTP/ManageSieve/Submission - 2 x Backend dovecot with local mail storage The frontend does the user authentification and communicate with the backends using a master password The fronted accepts PLAIN and LOGIN auth mechanisms and talk with backends using PLAIN auth mechanism (with the master password). This works very well, it's cool. Then, I've added to this setup an existing mail server (running another mailserver software) as a 3rd backend, and would like the frontend to also proxy for this, but this time not using master password. This is working for IMAP/POP3 when it uses PLAIN auth, but not for Submission. The backend server in this case only accepts LOGIN auth and not PLAIN on port 587. So I found out there is a field in the passdb we can add (proxy_mech), and I've set it to LOGIN. The frontend seems to now use LOGIN auth mech to talk to this 3rd backend, but the authentication still fails. According to the backend logs, tt seems dovecot proxy is now using LOGIN auth, but sends garbage as username and/or password. Also IMAP that was working when using PLAIN doesn't work anymore with LOGIN. Might this be a bug or this setup shouldn't be supported at all ? Passdb MySQL table on frontend: mysql> describe users; +-------------+--------------+------+-----+---------+-------+ | Field | Type | Null | Key | Default | Extra | +-------------+--------------+------+-----+---------+-------+ | user | varchar(255) | NO | PRI | NULL | | | domain | varchar(255) | NO | PRI | NULL | | | password | varchar(255) | YES | | NULL | | | displayname | varchar(255) | YES | | NULL | | | host | varchar(16) | NO | | NULL | | | usemaster | tinyint(1) | NO | | 1 | | | proxy_mech | varchar(20) | YES | | NULL | | | starttls | varchar(20) | YES | | NULL | | +-------------+--------------+------+-----+---------+-------+ mailstore-01/02 are dovecot backends otherhost is the other mailserver I also would like to proxy through dovecot proxy +---------+-----------------+-----------------------------------------+----------------+--------------+-----------+------------+----------+ | user | domain | password | displayname | host | usemaster | proxy_mech | starttls | +---------+-----------------+-----------------------------------------+----------------+--------------+-----------+------------+----------+ | user1 | somedomain.com | {SHA512-CRYPT}<some_crypted_pass> | Joe Black | mailstore-01 | 1 | NULL | NULL | | user2 | otherdomain.com | {SHA512-CRYPT}<some_crypted_pass> | Mr. Smith | mailstore-02 | 1 | NULL | NULL | | user3 | area13.com | NULL | Donald Duck | otherhost | 0 | LOGIN | any-cert | | user4 | area13.com | NULL | Thanks Obama | otherhost | 0 | LOGIN | any-cert | +---------+-----------------+-----------------------------------------+----------------+--------------+-----------+------------+----------+ Passdb query : password_query = \ SELECT concat(user, '@', domain) AS user, password, host, 'Y' AS proxy, \ IF(usemaster is TRUE, 'supermasteruserl', NULL) as master, \ IF(usemaster is TRUE, 'supermasterpassword', pass) as pass, \ IF(usemaster is FALSE, 'Y', NULL) as nopassword, \ proxy_mech, \ starttls \ FROM users WHERE user = '%n' AND domain = '%d' Some questions I'm asking myself: Is proxying using LOGIN proxy_mech supported at all to auth on backends ? Is dovecot proxying to "otherhost" supposed to decode original client auth (using PLAIN) and translate it to LOGIN format to auth with "otherhost" ? # otherhost port 587 log Without specifying proxy_mech [2019.09.19] 09:27:22.167 [192.168.60.220][3070269] cmd: EHLO dovecotproxy.local.domain [2019.09.19] 09:27:22.167 [192.168.60.220][3070269] rsp: 250-dovecotproxy.local.domain Hello [192.168.60.220]250-SIZE 52428800250-AUTH LOGIN CRAM-MD5250-STARTTLS250-8BITMIME250-DSN250 OK [2019.09.19] 09:27:22.167 [192.168.60.220][3070269] cmd: AUTH PLAIN <base64string> [2019.09.19] 09:27:22.167 [192.168.60.220][3070269] rsp: 504 Unrecognized authentication type. When using proxy_mech LOGIN [2019.09.20] 08:24:45.201 [192.168.60.220][24148464] cmd: AUTH LOGIN = [2019.09.20] 08:24:45.201 [192.168.60.220][24148464] Exception: The input is not a valid Base-64 string as it contains a non-base 64 character, more than two padding characters, or an illegal character among the padding characters. [2019.09.20] 08:24:45.201 [192.168.60.220][24148464] rsp: 535 Authentication failed # otherhost port 143 log Works without specyfing proxy_mech When using proxy_mech LOGIN (fails) [2019.09.20] 03:37:20.896 [192.168.60.220][26310645] connected at 20.09.2019 03:37:20 [2019.09.20] 03:37:20.896 [192.168.60.220][26310645] command: C CAPABILITY [2019.09.20] 03:37:20.896 [192.168.60.220][26310645] response: * CAPABILITY IMAP4rev1 AUTH=CRAM-MD5 AUTH=PLAIN UIDPLUS QUOTA XLIST CHILDREN ENABLE IDLE STARTTLS [2019.09.20] 03:37:20.896 [192.168.60.220][26310645] response: C OK CAPABILITY completed [2019.09.20] 03:37:20.896 [192.168.60.220][26310645] command: L AUTHENTICATE LOGIN [2019.09.20] 03:37:20.927 [192.168.60.220][26310645] disconnected at 20.09.2019 03:37:20 I hope I explained my setup so it's kinda understandable. I'm not good at explaining things :) Thank you for your help! root@mailfront-01:~# dovecot --version 2.3.7.2 (3c910f64b) Sébastien RICCIO SYSTEM ADMINISTRATOR

2 2

imapsieve administrator scripts are not executed in the order they are defined
by frankagainstthemachine＠gmx.de 06 Oct '19

06 Oct '19

Dear dovecot developers, I have an issue with the Pigeonhole IMAPSieve Plugin and the order in which administrator scripts are executed. Although I cannot find anything about the order in which the scripts are executed, I would expect they are executed in the order they are defined: the one defined by imapsieve_mailbox1_* before the one defined by imapsieve_mailbox2_* in case both match. I defined several administrator scripts; among them one that should be executed when copying a mail to mailbox "Inbox", and one that should be executed when copying a mail from a mailbox "*.Spam" to any other mailbox. No matter in which order I define the two scripts, the one related to "Inbox" is always executed first when I move a mail from "blah.Spam" to "Inbox", see the snipped from my logs below. I guess there might be a bug in file imap-sieve-storage.c, function imap_sieve_mailbox_rules_match(...): The comment in this function states "Insert sorted by rule index", but in case the index of the rule to be inserted is higher than any index already in the "rules" array, the rule is inserted in position 0 instead of being appended to the end, because "insert_idx" is initialized with 0. Since the rule for "*.Spam" is a pattern rule, it is the first rule to be inserted into "rules" (in imap_sieve_mailbox_rules_match_patterns(...)). Afterwards the rule for "Inbox" is always inserted at position 0 (in imap_sieve_mailbox_rules_match(...)), no matter if its rule index is higher or lower than the index of the other rule. The following change could fix this: - unsigned int insert_idx = 0; + unsigned int insert_idx = array_count(rules); Best regards, Frank ----- log ----- [...] Oct 4 23:51:12 somehost dovecot[22918]: imap(user)<22927><oLq3sRyU0t/AqLwV>: Debug: imapsieve: mailbox INBOX: MOVE event Oct 4 23:51:12 somehost dovecot[22918]: imap(user)<22927><oLq3sRyU0t/AqLwV>: Debug: sieve: Pigeonhole version 0.5.7.2 (7372921a) initializing Oct 4 23:51:12 somehost dovecot[22918]: imap(user)<22927><oLq3sRyU0t/AqLwV>: Debug: sieve: Sieve Extprograms plugin for Pigeonhole version 0.5.7.2 (7372921a) loaded Oct 4 23:51:12 somehost dovecot[22918]: imap(user)<22927><oLq3sRyU0t/AqLwV>: Debug: imapsieve: Static mailbox rule [1]: mailbox=`*.Spam' from=`*' causes=(COPY) => before=`file:/usr/lib/dovecot/sieve/spamassassin-learn- spam.sieve' after=(none) Oct 4 23:51:12 somehost dovecot[22918]: imap(user)<22927><oLq3sRyU0t/AqLwV>: Debug: imapsieve: Static mailbox rule [2]: mailbox=`*' from=`*.Spam' causes=(COPY) => before=`file:/usr/lib/dovecot/sieve/spamassassin-learn- ham.sieve' after=(none) Oct 4 23:51:12 somehost dovecot[22918]: imap(user)<22927><oLq3sRyU0t/AqLwV>: Debug: imapsieve: Static mailbox rule [3]: mailbox=`INBOX' from=`*' causes=(COPY APPEND) => before=`file:~/.dovecot.sieve' after=(none) Oct 4 23:51:12 somehost dovecot[22918]: imap(user)<22927><oLq3sRyU0t/AqLwV>: Debug: imapsieve: Matched static mailbox rule [2] Oct 4 23:51:12 somehost dovecot[22918]: imap(user)<22927><oLq3sRyU0t/AqLwV>: Debug: imapsieve: Matched static mailbox rule [3] Oct 4 23:51:12 somehost dovecot[22918]: imap(user)<22927><oLq3sRyU0t/AqLwV>: Debug: sieve: file storage: Using Sieve script path: /var/spool/mail/ user/.dovecot.sieve Oct 4 23:51:12 somehost dovecot[22918]: imap(user)<22927><oLq3sRyU0t/AqLwV>: Debug: sieve: file script: Opened script `.dovecot' from `/var/spool/mail/ user/.dovecot.sieve' Oct 4 23:51:12 somehost dovecot[22918]: imap(user)<22927><oLq3sRyU0t/AqLwV>: Debug: sieve: file storage: Using Sieve script path: /usr/lib/dovecot/sieve/ spamassassin-learn-ham.sieve Oct 4 23:51:12 somehost dovecot[22918]: imap(user)<22927><oLq3sRyU0t/AqLwV>: Debug: sieve: file script: Opened script `spamassassin-learn-ham' from `/usr/ lib/dovecot/sieve/spamassassin-learn-ham.sieve' Oct 4 23:51:12 somehost dovecot[22918]: imap(user)<22927><oLq3sRyU0t/AqLwV>: Debug: sieve: Opening script 1 of 2 from `/var/spool/mail/user/.dovecot.sieve' Oct 4 23:51:12 somehost dovecot[22918]: imap(user)<22927><oLq3sRyU0t/AqLwV>: Debug: sieve: Loading script /var/spool/mail/user/.dovecot.sieve [...] ----- dovecot -n ----- # 2.3.7.2 (3c910f64b): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.7.2 (7372921a) # OS: Linux 5.1.18-gentoo x86_64 Gentoo Base System release 2.6 ext4 # Hostname: somehost.de auth_username_format = %Ln mail_debug = yes mail_home = /var/spool/mail/%u mail_location = maildir:/var/spool/mail/%u/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 mime foreverypart extracttext vnd.dovec ot.debug 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 = scheme=CRYPT username_format=%u /etc/dovecot/users driver = passwd-file } plugin { imapsieve_mailbox1_before = file:/usr/lib/dovecot/sieve/spamassassin-learn- spam.sieve imapsieve_mailbox1_causes = COPY imapsieve_mailbox1_name = *.Spam imapsieve_mailbox2_before = file:/usr/lib/dovecot/sieve/spamassassin-learn- ham.sieve imapsieve_mailbox2_causes = COPY imapsieve_mailbox2_from = *.Spam imapsieve_mailbox2_name = * imapsieve_mailbox3_before = file:~/.dovecot.sieve imapsieve_mailbox3_causes = COPY APPEND imapsieve_mailbox3_name = Inbox mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename append sieve = file:~/sieve;active=~/.dovecot.sieve sieve_execute_bin_dir = /usr/lib/dovecot/sieve sieve_extensions = +vnd.dovecot.debug sieve_filter_bin_dir = /usr/lib/dovecot/sieve sieve_filter_exec_timeout = 300s sieve_filter_input_eol = lf sieve_global = /usr/lib/dovecot/sieve sieve_global_extensions = +vnd.dovecot.pipe +vnd.dovecot.execute +vnd.dovecot.filter sieve_pipe_bin_dir = /usr/lib/dovecot/sieve sieve_pipe_exec_timeout = 300s sieve_pipe_input_eol = lf sieve_plugins = sieve_extprograms } postmaster_address = postmaster(a)frankagainstthemachine.de protocols = imap lmtp sieve sieve service imap-login { inet_listener imap { port = 0 } } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0666 user = postfix } } ssl = required ssl_cert = </etc/ssl/dovecot/somehost.cert.pem ssl_cipher_list = ALL:!DH:!kRSA:!SRP:!kDHd:!DSS:!aNULL:!eNULL:!EXPORT:!DES:! 3DES:!MD5:!PSK:!RC4:!ADH:!LOW@STRENGTH ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it ssl_prefer_server_ciphers = yes userdb { args = username_format=%u /etc/dovecot/users driver = passwd-file } verbose_ssl = yes protocol lmtp { mail_plugins = " sieve" } protocol lda { mail_plugins = sieve } protocol imap { mail_plugins = " imap_sieve" } protocol sieve { mail_debug = yes }

2 1

Is it possible to create and use some lookup table to replace (for instance) %u in mail_location?
by Gerben Wierda 06 Oct '19

06 Oct '19

Suppose my mail_location is: mail_location = maildir:/private/var/mail/nl.rna.mail/%u But I would like to use a simple lookup table to replace %u with another value, say '8DB4E345-9144-4F92-8C9F-9D47BB61CBF8’ instead of ‘username’. Is there a (simple) way to do this? Gerben Wierda Chess and the Art of Enterprise Architecture <http://enterprisechess.com/> Mastering ArchiMate <http://masteringarchimate.com/> Architecture for Real Enterprises <https://www.infoworld.com/blog/architecture-for-real-enterprises/> at InfoWorld On Slippery Ice <https://eapj.org/on-slippery-ice/> at EAPJ

2 1