- dovecot - dovecot.org

sievec prints an error if no dovecot running with mail_plugins = stats
by SATOH Fumiyasu 25 Jun '18

25 Jun '18

Dovecot 2.2.36 + Pigeonhole 0.4.24 Is this an intended behavior? ``` # service dovecot status dovecot is stopped # doveconf mail_plugins mail_plugins = stats # ls foo.* foo.sieve # sievec foo.sieve sievec(root): Error: stats: open(/var/run/dovecot/stats-mail) failed: No such device or address # echo $? 0 # ls foo.* foo.sieve foo.svbin ``` -- -- Name: SATOH Fumiyasu @ OSS Technology Corp. (fumiyas @ osstech co jp) -- Business Home: https://www.OSSTech.co.jp/ -- GitHub Home: https://GitHub.com/fumiyas/ -- PGP Fingerprint: BBE1 A1C9 525A 292E 6729 CDEC ADC2 9DCA 5E1C CBCA

2 1

sieve for systemusers
by ratatouille 25 Jun '18

25 Jun '18

Hello! I enabled LDA for systemusers bei adding mailbox_command = /usr/lib/dovecot/dovecot-lda -f "$SENDER" -a "$RECIPIENT" to main.cf of postfix. I have done this because I want to use sieve for systemusers too, not only for virtual users. But the sievescripts do not work for those systemusers. What else needs to be done to get sieve to work for systemusers? Kind regards Andreas

2 1

upgrade 2.2 to 2.3, diffie-hellman, ssl_min_protocol
by tai74＠vfemail.net 25 Jun '18

25 Jun '18

hi sorry if question was asked already. Was reading https://wiki2.dovecot.org/Upgrading/2.3 first I'm confused on diffie hellman parameters file. I never set up ssl-parameters.dat before (should i have? do I have one that was automatically made for me by dovecot?) Do I need to make a fresh dh.pem? The upgrade doc tells how to convert ssl-parameters.dat but how to make a new one? other question is if I copy ssl_min_protocol from example config into my existing config is that enough? do experts on this list recommend any tweaks that increase client requirements more than dovecot developers are comfortable with but will ensure more secure protocol usage? ------------------------------------------------- ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of the NSA's hands! $24.95 ONETIME Lifetime accounts with Privacy Features! 15GB disk! No bandwidth quotas! Commercial and Bulk Mail Options!

3 5

Dovecot as transparent proxy for Exchange<->Dovecot<->Yahoo.com/Yandex.com with mail synchronization between servers !
by CpServiceSPb 25 Jun '18

25 Jun '18

We have Exchange as internal mail server, also we have gate where we plant to install Dovecot, also we have external mail at servers such as yahoo.com ort yandex.com. There are some mailboxes at Exchange, for example: user1(a)internal.ltd to user10(a)internal.ltd. There are some mailboxes at Ynadex.com, for example: personel1(a)external.com to personel10(a)external.com. 1. For messages flow: We need that Dovecot would act as at least transparent IMAP proxy for Exchange/Yandex and vise versa. For incoming messages - some messages comes to personel5(a)external.com located at Yandex.com, then Dovecot gets it from Yandex using IMAP IDLE, tnen stores it locally (where Dovecot is installed) to MySQL (using DBMail) or at least maildir format and after that sends it forward (using IMAP PUSH) to appropriate account user5(a)internal.ltd or triggers (signals) Fetchmail to sends forward it to specified Exchange acoount. And so on - for each external/interla pairs of accounts (Yandex.com/Exchange) . For outgoing messages - Exchange send out it using Exim4, Exim4 stores it locally (where Dovecot is installed) to MySQL (using DBMail) and then Exim4 sends it out to Yandex.com and in the same time Dovecot uploads this message to Yandex.com to "Sent" folder. And this messages is sent through Yandex.com. 2. For messages storage: When messages are deleted at Exchange, it are deleted from Dovecot (MySQL storage) and deleted from Yandex.com as well. Or when messages are deleted from Yandex.com, it are deleted from Dovecot (MySQL storage) and deleted from Exchange as well. Is it possible to set up Dovecot and may be some other soft (Fetchmail, imapsyncd and so on) to get point 1 working or point 1 and point 2 working ?

1 0

More and better logging
by Tom Sommer 25 Jun '18

25 Jun '18

In general I feel there is a lack of debug and "when things go wrong"-logging in Dovecot (information that should perhaps be provided with a verbose toggle). I was debugging problems with sasl user logins and a generic "SASL CRAM-MD5 authentication failed: Connection lost to authentication server" error in postfix, but nothing is logged in Dovecot when the error occurs. After extensive debugging I finally discovered auth-penalty and auth_penalty_to_secs after digging in the code. I suspect this to be the cause, but truly I have no way of confirming this, since no log is provided when this is triggered? - it would be nicer if events such as these were simply logged for better debugging and troubleshooting. Two cents :) Thanks -- Tom

2 1

Released Pigeonhole v0.5.2.rc1 for Dovecot v2.3.2.rc1.
by Stephan Bosch 24 Jun '18

24 Jun '18

Hello Dovecot users, Here is the Pigeonhole release candidate that goes with the Dovecot v2.3.2 release candidate. Much like version 0.4.24 for Dovecot v2.2, this release consists mostly of fixes that accumulated over the last few months. Beyond that, this release contains the new IMAP FILTER=SIEVE capability, which was also released earlier with 2.2.24 (with a few additional fixes). Changelog v0.5.2: + Implement plugin for the a vendor-defined IMAP capability called "FILTER=SIEVE". It adds the ability to manually invoke Sieve filtering in IMAP. More information can be found in doc/plugins/imap_filter_sieve.txt. - The Sieve address test caused an assertion panic for invalid addresses with UTF-8 codepoints in the localpart. Fixed by properly detecting invalid addresses with UTF-8 codepoints in the localpart and skipping these like other invalid addresses while iterating addresses for the address test. - Make the length of the subject header for the vacation response configurable and enforce the limit in UTF-8 codepoints rather than bytes. The subject header for a vacation response was statically truncated to 256 bytes, which is too limited for multi-byte UTF-8 characters. - Sieve editheader extension: Fix assertion panic occurring when it is used to manipulate a message header with a very large header field. - Properly abort execution of the sieve_discard script upon error. Before, the LDA Sieve plugin attempted to execute the sieve_discard script when an error occurs. This can lead to the message being lost. - Fix the interaction between quota and the sieve_discard script. When quota was used together with a sieve_discard script, the message delivery did not bounce when the quota was exceeded. The release is available as follows: http://pigeonhole.dovecot.org/releases/2.3/rc/dovecot-2.3-pigeonhole-0.5.2.… http://pigeonhole.dovecot.org/releases/2.3/rc/dovecot-2.3-pigeonhole-0.5.2.… Refer to http://pigeonhole.dovecot.org and the Dovecot wiki for more information. Have fun testing this release candidate and don't hesitate to notify me when there are any problems. Regards, -- Stephan Bosch stephan(a)rename-it.nl

1 0

Can't build pigeonhole against dovecot 2.3.2rc1
by tai74＠vfemail.net 22 Jun '18

22 Jun '18

Help? ntfy-mailto.c: In function ‘ntfy_mailto_send’: ntfy-mailto.c:505:5: error: too few arguments to function ‘smtp_address_create_from_msg_temp’ sieve_get_postmaster(senv)); ^ In file included from ./../../../sieve-types.h:5:0, from ./../../../sieve-common.h:7, from ntfy-mailto.c:30: /usr/local/include/dovecot/smtp-address.h:101:5: note: declared here int smtp_address_create_from_msg_temp(const struct message_address *msg_addr, ^ ntfy-mailto.c: In function ‘ntfy_mailto_action_execute’: ntfy-mailto.c:682:4: error: too few arguments to function ‘smtp_address_create_from_msg_temp’ sieve_get_postmaster(senv)); ^ In file included from ./../../../sieve-types.h:5:0, from ./../../../sieve-common.h:7, from ntfy-mailto.c:30: /usr/local/include/dovecot/smtp-address.h:101:5: note: declared here int smtp_address_create_from_msg_temp(const struct message_address *msg_addr, ^ make[6]: *** [ntfy-mailto.lo] Error 1 ------------------------------------------------- ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of the NSA's hands! $24.95 ONETIME Lifetime accounts with Privacy Features! 15GB disk! No bandwidth quotas! Commercial and Bulk Mail Options!

2 2

variable forwarding buglet
by Jan-Pieter Cornet 22 Jun '18

22 Jun '18

I wanted to forward information from the director to the backend dovecot (original login name), so I had the userdb on the director return a forward_ologin variable. However, when I tried to use that variable in the "password_key" query on the backend dovecot, ${forward_ologin} was expanded to UNSUPPORTED_VARIABLE_forward_ologin. After testing a bit and looking around in the source a bit, and turning on debugging logging, it appeared that the forwarded variables actually appear as "passdb/userdb extra fields". So in my case, the forwarded information is available as %{passdb:forward_ologin}. So, problem solved, but this is either an implementation bug, or a documentation bug, or oversight. -- Jan-Pieter Cornet <johnpc(a)xs4all.net> Systeembeheer XS4ALL Internet bv www.xs4all.nl

1 0

Location of dovecot.sieve
by ratatouille 22 Jun '18

22 Jun '18

Hello! If I set sieve = file:~/sieve;active=~/.dovecot.sieve in dovecot.conf like I read in the documentation I get Jun 22 16:36:01 lda(a.meyer): Error: sieve: sieve file backend: invalid option `active=~/.dovecot.sieve' Jun 22 16:36:01 lda(a.meyer): Error: sieve: failed to access user's Sieve script file:~/sieve;active=~/.dovecot.sieve (temporary failure) What is wrong with this one? Kind regards Andreas

1 0

enable dovecot.sieve.log
by ratatouille 22 Jun '18

22 Jun '18

Hello! How do I enable dovecot.sieve.log? I see nothing about that in 90-sieve.conf Kind regards Andreas

1 1

doveadm backup -A does not create user dirs
by Vladimir Tiukhtin 20 Jun '18

20 Jun '18

Hello doveadm backup -A mdbox:/tmp/test does not create per user folders, instead it tries to override same catalog again and again doveadm backup -A mdbox:/tmp/test/%u does not work as well Is there a solution for local backups? Thanks Vladimir

2 1

v2.3.2 release candidate released
by Timo Sirainen 18 Jun '18

18 Jun '18

https://dovecot.org/releases/2.3/rc/dovecot-2.3.2.rc1.tar.gz https://dovecot.org/releases/2.3/rc/dovecot-2.3.2.rc1.tar.gz.sig v2.3.2 is mainly a bugfix release. It contains all the changes in v2.2.36, as well as a bunch of other fixes (mainly for v2.3-only bugs). * old-stats plugin: Don't temporarily enable PR_SET_DUMPABLE while opening /proc/self/io. This may still cause security problems if the process is ptrace()d at the same time. Instead, open it while still running as root. + doveadm: Added mailbox cache decision&remove commands. See doveadm-mailbox(1) man page for details. + doveadm: Added rebuild attachments command for rebuilding $HasAttachment or $HasNoAttachment flags for matching mails. See doveadm-rebuild(1) man page for details. + cassandra: Use fallback_consistency on more types of errors + lmtp proxy: Support outgoing SSL/TLS connections + lmtp: Add lmtp_rawlog_dir and lmtp_proxy_rawlog_dir settings. + submission: Add support for rawlog_dir + submission: Add submission_client_workarounds setting. + lua auth: Add password_verify() function and additional fields in auth request. - doveadm-server: TCP connections are hanging when there is a lot of network output. This especially caused hangs in dsync-replication. - Using multiple type=shared mdbox namespaces crashed - mail_fsync setting was ignored. It was always set to "optimized". - lua auth: Fix potential crash at deinit - SSL/TLS servers may have crashed if client disconnected during handshake. - SSL/TLS servers: Don't send extraneous certificates to client when alt certs are used. - lda, lmtp: Return-Path header without '<' may have assert-crashed. - lda, lmtp: Unencoded UTF-8 in email address headers may assert-crash - lda: -f parameter didn't allow empty/null/domainless address - lmtp, submission: Message size limit was hardcoded to 40 MB. Exceeding it caused the connection to get dropped during transfer. - lmtp: Fix potential crash when delivery fails at DATA stage - lmtp: login_greeting setting was ignored - Fix to work with OpenSSL v1.0.2f - systemd unit restrictions were too strict by default - Fix potential crashes when a lot of log output was produced - SMTP client may have assert-crashed when sending mail - IMAP COMPRESS: Send "end of compression" marker when disconnecting. - cassandra: Fix consistency=quorum to work - dsync: Lock file generation failed if home directory didn't exist - Snippet generation for HTML mails didn't ignore &entities inside blockquotes, producing strange looking snippets. - imapc: Fix assert-crash if getting disconnected and after reconnection all mails in the selected mailbox are gone. - pop3c: Handle unexpected server disconnections without assert-crash - fts: Fixes to indexing mails via virtual mailboxes. - fts: If mails contained NUL characters, the text around it wasn't indexed. - Obsolete dovecot.index.cache offsets were sometimes used. Trying to fetch a field that was just added to cache file may not have always found it.

1 0

TCP replication: high connection rate and looping in incomplete state
by tok 16 Jun '18

16 Jun '18

Hi, I am trying to establish TCP(s)-based replication between two FreeBSD 11.1 machines, both running Dovecot 2.2.35 (via pkg) with 10 virtual users and 1.2GB maildir. I followed the Wiki description (https://wiki2.dovecot.org/Replication) just skipped the SSH part. My resulting configurations are attached below. Problem: After reloading both Dovecot instances, a few seconds later they start to initiate connections in an absurdly high rate (30-50 new connections during 10 secs, closing old ones after 2-3 secs) and even after 1 hour they do not „calm down". E-mails are copied, but judging by size and file count, not completely (approx. 1GB and maybe 90% of files are getting synced). What is going on here? On the destination host (with empty storage before replication) I see "incremental - Waiting for dsync to finish“ in dsync-status, constantly flipping between handshake and waiting, for solely 4 out of 10 accounts. Replicator status says 0 requests and 10 total users. On the source host, replicator status says 4 queued full resyncs, 3 waiting failed and 10 total users. I already tried both tcps and tcp; activating debug log did not reveal any errors (e.g. SSL). Would be happy for any advice to track this down. Best regards, tok Config source host: ----- # 2.2.35 (b1cb664): /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 0.4.23 (b2e41927) # OS: FreeBSD 11.1-RELEASE-p10 amd64 zfs # Hostname: srv1.TLD auth_mechanisms = plain login doveadm_password = # hidden, use -P to show it doveadm_port = 12345 lmtp_save_to_detail_mailbox = yes login_trusted_networks = 172.16.1.110/32 mail_location = maildir:/srv/mail/vhosts/%d/%n mail_plugins = quota mailbox_alias notify replication namespace inbox { […] } passdb { args = scheme=CRYPT username_format=%u /usr/local/etc/dovecot/users driver = passwd-file } plugin { mail_replica = tcps:srv2.TLD:12345 quota = maildir:User quota quota_grace = 10%% quota_max_mail_size = 50M quota_rule = *:storage=1G quota_rule2 = Trash:storage=+10%% quota_rule3 = Junk:storage=+20%% quota_status_nouser = DUNNO quota_status_overquota = 552 5.2.2 Mailbox is over quota / full quota_status_success = DUNNO quota_warning = storage=95%% quota-warning 95 %u quota_warning2 = storage=80%% quota-warning 80 %u quota_warning3 = -storage=100%% quota-warning below %u [...] } postmaster_address = postmaster@TLD quota_full_tempfail = yes service aggregator { fifo_listener replication-notify-fifo { mode = 0666 user = vmail } unix_listener replication-notify { mode = 0666 user = vmail } } service auth-worker { user = $default_internal_user } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } } service config { unix_listener config { user = vmail } } service doveadm { inet_listener { port = 12345 ssl = yes } } service imap-login { process_min_avail = 1 service_count = 1 } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } service pop3-login { process_min_avail = 1 service_count = 1 } service quota-status { client_limit = 1 executable = quota-status -p postfix inet_listener { address = 127.0.0.1 port = 12340 } } service quota-warning { executable = script /usr/local/bin/dovecot-quota-warning.sh user = vmail } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { group = vmail mode = 0666 } } ssl_cert = </usr/local/etc/ssl/acme.sh/srv1.TLD/fullchain.pem ssl_client_ca_file = /etc/ssl/cert.pem userdb { args = username_format=%u /usr/local/etc/dovecot/users driver = passwd-file } protocol lmtp { mail_plugins = quota mailbox_alias notify replication quota sieve } protocol lda { mail_plugins = quota mailbox_alias notify replication sieve } protocol imap { mail_plugins = quota mailbox_alias notify replication imap_quota imap_sieve } ----- Diff config of destination host: ----- 4c4 < # Hostname: srv2.TLD --- > # Hostname: srv1.TLD 9a10 > login_trusted_networks = 172.16.1.110/32 60c61 < mail_replica = tcps:srv1.TLD:12345 --- > mail_replica = tcps:srv2.TLD:12345 156c157 < ssl_cert = </usr/local/etc/ssl/acme.sh/srv1.TLD/fullchain.pem --- > ssl_cert = </usr/local/etc/ssl/acme.sh/srv1.TLD/fullchain.pem -----

1 0

failed: Stream is smaller than expected (0 < 5098)
by Vladimir Tiukhtin 15 Jun '18

15 Jun '18

Hi Looks like I have got in a situation with missing or corrupted attachments. I am getting from time to time lmtp(17147, user1(a)example.com) Error: read(attachments-connector(zlib(/var/spool/mail/example.com/user2/mail/stor… failed: read(/srv/attachments/user2/4a/e0/4ae062027dd745f56c2cc1c43fa4f349f52986a0-2bcf4e063994235bfb4200006f28d014[base64:19 b/l]) failed: Stream is smaller than expected (0 < 5098) Replication works, but is there a way to recover the logic even with empty files or cleaning indices? Thanks Vladimir

2 2

After logrotation Dovecot still writes to old log file
by Michael Heuberger 15 Jun '18

15 Jun '18

Hi there This is weird. On my latest Ubuntu server Dovecot seems to write to /var/log/dovecot.log.1 instead of a recently created /var/log/dovecot.log Here my logrotate config for Dovecot: /var/log/dovecot.log { su root syslog rotate 7 missingok copytruncate create 666 root syslog sharedscripts postrotate doveadm log reopen endscript } Doveadm should reopen it but no, still writes to old log file. Not sure, maybe it's someone else, not dovecot, writing to the log file? And here the versions: # 2.2.33.2 (d6601f4ec): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.21 (92477967) # OS: Linux 4.14.49-rh65-20180612025235.xenU.x86_64 x86_64 Ubuntu 18.04 LTS How can we investigate best? Or is there a mistake in the above logrotate config? - Michael -- Binary Kitchen Michael Heuberger 1/33 Parrish Road Sandringham Auckland 1025 (New Zealand) Mobile (text only) ... +64 21 261 89 81 Email ................ michael(a)binarykitchen.com Website .............. http://www.binarykitchen.com

3 4

new problem
by Walter Ulmke 14 Jun '18

14 Jun '18

1) my inbox is "Posteingang". should I officially declare it somewhere? I now get the following error messages: Jun 14 00:23:32 ulmke2 dovecot[3981]: imap(ulw)<3997><4O/Xbo1uotLAqGQd>: Error: opendir(/u/ulw/Mail) failed: Permission denied (euid=503(ulw) egid=100(users) UNIX perms appear ok (ACL/MAC wrong?)) Jun 14 00:23:32 ulmke2 dovecot[3981]: imap(ulw)<3997><4O/Xbo1uotLAqGQd>: Error: opendir(/u/ulw/Mail) failed: Permission denied (euid=503(ulw) egid=100(users) UNIX perms appear ok (ACL/MAC wrong?)) Jun 14 00:23:32 ulmke2 dovecot[3981]: imap(ulw)<3997><4O/Xbo1uotLAqGQd>: Error: Couldn't create mailbox list lock /u/ulw/Mail/mailboxes.lock: file_create_locked(/u/ulw/Mail/mailboxes.lock) failed: safe_mkstemp(/u/ulw/Mail/mailboxes.lock) failed: Permission denied Jun 14 00:23:33 ulmke2 dovecot[3981]: Error: imap(ulw)<3997><4O/Xbo1uotLAqGQd>: open(/u/ulw/Mail/dovecot.index.log) failed: Permission denied (euid=503(ulw) egid=100(users) UNIX perms appear ok (ACL/MAC wrong?)) Jun 14 00:23:33 ulmke2 dovecot[3981]: Error: imap(ulw)<3997><4O/Xbo1uotLAqGQd>: Mailbox INBOX: file_dotlock_create(/u/ulw/Mail/dovecot-uidlist) failed: Permission denied (euid=503(ulw) egid=100(users) UNIX perms appear ok (ACL/MAC wrong?)) Jun 14 00:23:33 ulmke2 dovecot[3981]: Error: imap(ulw)<3997><4O/Xbo1uotLAqGQd>: Mailbox INBOX: open(/u/ulw/Mail/dovecot-uidlist) failed: Permission denied Jun 14 00:23:43 ulmke2 dovecot[3981]: Error: imap(ulw)<3997><4O/Xbo1uotLAqGQd>: open(/u/ulw/Mail/dovecot.index.log) failed: Permission denied (euid=503(ulw) egid=100(users) UNIX perms appear ok (ACL/MAC wrong?)) Also, when I start Thunderbird I get the following error message: "der aktuelle Vorgang in "Posteingang" ist fehlgeschlagen. Der Server des Kontos antwortete (Serverbug) Internal error ocurred. Refer to server log WHERE IS THE SERVER LOG? -- -- Best Regards, Walter Ulmke Ulmke Machine Tools, 48496 Hopsten, Germany Tel. ++49/5458/93345-0 Fax. ++49/5458/93345-45 Mobile: ++49/172/5357999 eMail: ulw(a)ulmke.com Dipl.-Ing. Walter Ulmke e.K. AG Steinfurt HRA 4384

5 6

Namespaces for Apple Client
by Janzen, Tobias 14 Jun '18

14 Jun '18

Hi, i have a plesk server with postfix an dovecot. Webmail is roundcube. Version of Dovecot is 2.3.0.1 I want apple clients to use the default special folders. My config for namespaces worked till last week. Now I cant get it to work again. Hope someone can help me. # 2.3.0.1 (ffd8a29): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.0.1 (d33dca20) # OS: Linux 4.4.0-042stab130.1 x86_64 Ubuntu 16.04.4 LTS reiserfs auth_mechanisms = plain login digest-md5 cram-md5 apop auth_username_chars = abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890&.-_@' disable_plaintext_auth = no first_valid_uid = 30 imap_client_workarounds = delay-newmail imap_logout_format = rcvd=%i, sent=%o mail_home = /var/qmail/mailnames/%Ld/%Ln mail_location = maildir:/var/qmail/mailnames/%Ld/%Ln/Maildir mail_log_prefix = "service=%s, user=%u, ip=[%r]. " mail_plugins = " quota" managesieve_logout_format = rcvd=%i, sent=%o managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date index ihave duplicate mime foreverypart extracttext imapflags notify namespace inbox { inbox = yes location = mailbox Sent { auto = subscribe special_use = \Sent } mailbox "Sent Messages" { auto = create special_use = \Sent } prefix = INBOX. separator = . type = private } passdb { driver = plesk } plugin { mail_crypt_global_private_key = <ecprivkey.pem mail_crypt_global_public_key = <ecpubkey.pem mail_crypt_save_version = 2 quota = maildir:User quota quota_grace = 0 sieve = ~/.dovecot.sieve sieve_dir = ~/sieve sieve_extensions = +notify +imapflags } pop3_client_workarounds = outlook-no-nuls oe-ns-eoh pop3_logout_format = rcvd=%i, sent=%o, top=%t/%p, retr=%r/%b, del=%d/%m, size=%s protocols = imap pop3 sieve service auth-worker { group = user = } service auth { group = unix_listener auth-userdb { group = popuser mode = 0600 user = popuser } user = } service imap { process_limit = 1024 service_count = 1 } service pop3 { process_limit = 1024 service_count = 1 } ssl_cert = </etc/dovecot/private/ssl-cert-and-key.pem ssl_cipher_list = HIGH:!aNULL:!MD5 ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it ssl_prefer_server_ciphers = yes userdb { args = uid=popuser gid=popuser driver = static } protocol imap { mail_plugins = " quota imap_quota" } protocol pop3 { pop3_uidl_format = UID%u-%v } protocol lda { mail_plugins = " quota sieve" } HEIM & HAUS Produktion und Vertrieb GmbH Hochstra?e 7-9, 47169 Duisburg Telefon: +49 203 40644-0 Telefax: +49 203 407312 E-Mail: service-du(a)heimhaus.de Internet: http://www.heimhaus.de USt-IdNr.: DE 272301801 Sitz Duisburg, HRB 22438 Gesch?ftsf?hrer: Michael Demming, Dipl.-Ing. Klaus Rappers

1 0

can't login to Dovecot solved
by Walter Ulmke 14 Jun '18

14 Jun '18

solved. It was doen to not being able to log in in "plain" -- -- Best Regards, Walter Ulmke Ulmke Machine Tools, 48496 Hopsten, Germany Tel. ++49/5458/93345-0 Fax. ++49/5458/93345-45 Mobile: ++49/172/5357999 eMail: ulw(a)ulmke.com Dipl.-Ing. Walter Ulmke e.K. AG Steinfurt HRA 4384

1 0

cant login to Dovecot
by Walter Ulmke 13 Jun '18

13 Jun '18

Hi all, I can't login. This is a dovecot server for a small inhouse network, and I doon't use any encryption, and just want to login using the standard Linux login dovecot status gives me the following error messages: un 12 12:30:06 ulmke2 dovecot[5814]: auth: Fatal: APOP mechanism can't be supported with given passdbs Jun 12 12:30:06 ulmke2 dovecot[5811]: master: Error: service(auth): command startup failed, throttling for 32 secs Jun 12 12:30:06 ulmke2 dovecot[5814]: imap-login: Disconnected: Auth process broken (disconnected before auth was ready, waited 10 secs): user=<>, rip=192.168.100.29, lip=192.168.100.2, session=<qXOLWW9uBNPAqGQd> Jun 12 12:30:06 ulmke2 dovecot[5814]: imap-login: Warning: Timeout leak: 0x7fa8a7d372a0 (auth-server-connection.c:397) Jun 12 12:30:16 ulmke2 dovecot[5814]: imap-login: Warning: Auth process not responding, delayed sending initial response (greeting): user=<>, rip=192.168.100.29, lip=192.168.100.2, session=<pw8lWm9uBtPAqGQd> Jun 12 12:30:36 ulmke2 dovecot[5814]: imap-login: Error: Timeout waiting for handshake from auth server. my pid=5874, input bytes=0 Jun 12 12:30:36 ulmke2 dovecot[5814]: imap-login: Disconnected: Auth process broken (disconnected before auth was ready, waited 30 secs): user=<>, rip=192.168.100.29, lip=192.168.100.2, session=<pw8lWm9uBtPAqGQd> Jun 12 12:30:38 ulmke2 dovecot[5814]: auth: Error: stats: open(old-stats-user) failed: Permission denied Jun 12 12:30:38 ulmke2 dovecot[5814]: auth: Fatal: APOP mechanism can't be supported with given passdbs Jun 12 12:30:38 ulmke2 dovecot[5811]: master: Error: service(auth): command startup failed, throttling for 60 secs I'm moving to a new server. stats: open(old-stats-user) failed: Permission denied This file may be somewhere on the old server. Can anyone help me? -- -- Best Regards, Walter Ulmke

4 8

can't login to Dovecot
by Walter Ulmke 13 Jun '18

13 Jun '18

I've managed to turn on "plain" and now it seems I can logon. Jun 13 17:24:20 ulmke2 dovecot[1973]: imap(ulw)<2474><+kyqk4du5M7AqGQd>: Namespace '': Mail storage autodetection failed with home=/u/ulw in=0 out=373 deleted=0 expunged=0 trashed=0 hdr_count=0 hdr_bytes=0 body_count=0 body_bytes=0 Jun 13 17:24:20 ulmke2 dovecot[1973]: imap-login: Login: user=<ulw>, method=PLAIN, rip=192.168.100.29, lip=192.168.100.2, mpid=2476, session=<GJCrk4du5s7AqGQd> Jun 13 17:24:20 ulmke2 dovecot[1973]: imap(ulw)<2476><GJCrk4du5s7AqGQd>: Error: Namespace '': Mail storage autodetection failed with home=/u/ulw All users mailboxes are $HOME/Mail How do I tell Dovecot this? -- -- Best Regards, Walter Ulmke Ulmke Machine Tools, 48496 Hopsten, Germany Tel. ++49/5458/93345-0 Fax. ++49/5458/93345-45 Mobile: ++49/172/5357999 eMail: ulw(a)ulmke.com Dipl.-Ing. Walter Ulmke e.K. AG Steinfurt HRA 4384

2 1

can't login to Dovecot
by Walter Ulmke 13 Jun '18

13 Jun '18

I have now deleted EVERYTHING and installed fresh. Now at least it starts doveconf -n: 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 = passdb { driver = pam } plugin { sieve = file:~/sieve;active=~/.dovecot.sieve } ssl_cipher_list = ALL:!aNULL:!eNULL:!EXPORT:!DES:!3DES:!MD5:!PSK:!RC4:!ADH:!LOW@STRENGTH ssl_options = no_compression ssl_prefer_server_ciphers = yes userdb { driver = passwd } ----------------------------------- looks like PAM is already configured. I CAN'T LOKIN USING PLAIN TEXT. HOW DO i TURN THIS OFF?? -- -- Best Regards, Walter Ulmke Ulmke Machine Tools, 48496 Hopsten, Germany Tel. ++49/5458/93345-0 Fax. ++49/5458/93345-45 Mobile: ++49/172/5357999 eMail: ulw(a)ulmke.com Dipl.-Ing. Walter Ulmke e.K. AG Steinfurt HRA 4384

1 0

Re: 2.3.1 Replication is throwing scary errors
by Thore Bödecker 13 Jun '18

13 Jun '18

Aaaaand I forgot to CC the list, sorry for that, it's way too early in the morning :P On 07.06.18 - 07:39, Thore Bödecker wrote: > What does the output of these two commands show after that error has > been logged? > > doveadm replicator status > > doveadm replicator dsync-status > > If there are *waiting failed* requests, that never make it "through" > (after being temporarily in state *queued failed* and then returning > to *waiting failed*) this means there is something wrong with the > replication. > > You can try forcing replication of all known users using > > doveadm replicator replicate '*' > > And see if that resolves the failed requests, but I doubt it. > > Please let us know how your status outputs look like. > > > Cheers, > Thore > > -- > Thore Bödecker > > GPG ID: 0xD622431AF8DB80F3 > GPG FP: 0F96 559D 3556 24FC 2226 A864 D622 431A F8DB 80F3 > > > On 07.06.18 - 15:21, Reuben Farrelly wrote: > > Still not quite right for me. > > > > Jun 7 15:11:33 thunderstorm.reub.net dovecot: doveadm: Error: > > dsync(lightning.reub.net): I/O has stalled, no activity for 600 seconds > > (last sent=mail, last recv=mail (EOL)) > > Jun 7 15:11:33 thunderstorm.reub.net dovecot: doveadm: Error: Timeout > > during state=sync_mails (send=mails recv=recv_last_common) > > > > I'm not sure if there is an underlying replication error or if the message > > is just cosmetic, though. > > > > Reuben > > > > > > On 7/06/2018 4:55 AM, Remko Lodder wrote: > > > Hi Timo, > > > > > > Yes this seems to work fine so far. I’ll ask the people to add it to the > > > current FreeBSD version.. > > > > > > Cheers > > > Remko > > > > > > > On 6 Jun 2018, at 19:34, Timo Sirainen <tss(a)iki.fi > > > > <mailto:tss@iki.fi>> wrote: > > > > > > > > Should be fixed by https://github.com/dovecot/core/commit/a952e178943a5944255cb7c053d970f8e6d4… > > > > > > >

1 2

2.3.1: Core dump on quota reach
by Tom Sommer 12 Jun '18

12 Jun '18

Just upgraded from 2.2.34 to 2.3.1: Jun 12 16:06:38 lmtp(example(a)example.name)<46176><8JrHEW7TH1tgtAAAd9aEAw>: Info: msgid=<iOIOOFTVyrtapfaoLCJKLCGX2P21E2eVWiGnXPfSSik.ezvWGm_MVMKKL2i0I81WDbYtapg7RisY9PCL91ga0WQ(a)ketopasuse.date>: save failed to INBOX: The email account that you tried to reach is over quota (Mailbox is full). Jun 12 16:06:38 lmtp(example(a)example.name)<46176><8JrHEW7TH1tgtAAAd9aEAw>: Fatal: master: service(lmtp): child 46176 killed with signal 11 (core dumps disabled - https://dovecot.org/bugreport.html#coredumps) And also, unrelated: Jun 12 16:21:32 lmtp(53430): Error: lmtp-server: conn director.local:39204 [6]: Connection lost during data transfer: read(director.local:39204 [6]) failed: <no error> -- Tom

2 1

Race condition when setting flags (\Deleted) + expunge quickly, leaving mails not deleted
by Tomas Forsman 12 Jun '18

12 Jun '18

Hello. I seem to have found a race condition, when setting flags on multiple emails rapidly. 5 commands including login to reproduce. Problem found using mutt in real world usage. Seems to happen both with UID STORE 1:3 and UID STORE 1,2,3 .. I have tried with the following packages, with a minimized config in a throwaway vm: https://packages.debian.org/stretch/dovecot-core Package: dovecot-core (1:2.2.27-3+deb9u2) https://packages.debian.org/stretch-backports/dovecot-core Package: dovecot-core (1:2.2.34-2~bpo9+1) Also tested pristine: https://dovecot.org/releases/2.3/dovecot-2.3.0.1.tar.gz https://dovecot.org/releases/2.2/dovecot-2.2.34.tar.gz https://dovecot.org/releases/2.2/dovecot-2.2.35.tar.gz .. built on Debian9 with: # apt-get build-dep dovecot-core # bash configure --prefix=/scratch/dovecot-test Tried with both mailbox over NFS (backed by ext4), and also mailbox on ext4. On my test systems, I am only able to reproduce it with mbox_lazy_writes=no, but with production settings on a Ubuntu 14.04 with 1:2.2.9-1ubuntu2.4 that has mbox_lazy_writes=yes it is still reproducable with mutt. I have found two different ways to reproduce it with netcat + cut'n'paste, below is done with 2.2.34/35. All servers are VMs in Ganeti/kvm clusters (Debian hosts in one cluster&organization, Ubuntu host in another cluster&organization). Debian minimized config: > doveconf -n # 2.2.34 (874deae): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.22 (22940fb7) # OS: Linux 4.9.0-6-amd64 x86_64 Debian 9.4 # Hostname: mail2-vm.cs.umu.se auth_mechanisms = plain login auth_verbose = yes debug_log_path = syslog info_log_path = syslog mail_location = mbox:~/Mail:INBOX=/var/mail/%u mail_privileged_group = mail mbox_lazy_writes = no namespace inbox { inbox = yes location = prefix = } passdb { driver = pam } protocols = imap service auth { client_limit = 2500 unix_listener auth-client { group = postfix mode = 0660 } } service imap-login { inet_listener imap { port = 143 } } service imap { executable = imap } ssl = no syslog_facility = local1 userdb { driver = passwd } Attached is a mailbox that can be used to reproduce the problem, called "error-box", anonymized with mbox-anonymize.pl. It was created by sending test messages with mutt 1.7.2 through Dovecot/Postfix/Amavis. **** Method 1, with IDLE: Setup a local account, MY-USER / MY-PASSWORD (replace below). > mkdir Mail > cp error-box Mail/error1 > nc -v localhost 143 Paste the following 3 lines in a go: a0000 LOGIN "MY-USER" "MY-PASSWORD" a0010 SELECT "error1" a0020 IDLE then wait a second.. then paste the following 3 in a go: DONE a0030 UID STORE 1:3 +FLAGS (\Deleted) a0040 EXPUNGE Notice that the results from UID STORE + EXPUNGE gives: * 2 FETCH (UID 2 FLAGS (\Recent)) * 3 FETCH (UID 3 FLAGS (\Recent)) * 1 EXPUNGE * 3 RECENT a0030 OK Store completed (0.004 + 0.000 + 0.003 secs). a0040 OK Expunge completed (0.004 + 0.000 + 0.003 secs). Verify what's left in the mailbox with: a0050 UID FETCH 1:4 FLAGS * 1 FETCH (UID 2 FLAGS (\Recent)) * 2 FETCH (UID 3 FLAGS (\Recent)) * 3 FETCH (UID 4 FLAGS (\Recent)) a0050 OK Fetch completed (0.001 + 0.000 secs). Since 1 to 3 should be \Deleted and then EXPUNGEd, we should only have UID 4 left, not uid 2-4 without Deleted flag. Try same again, but with 1 inserted delay (use a new mailbox name for every test, otherwise UID numbering will vary, indexes etc): > cp error-box Mail/error2 > nc -v localhost 143 Paste the following 3 lines in a go: a0000 LOGIN "MY-USER" "MY-PASSWORD" a0010 SELECT "error2" a0020 IDLE then wait a second.. then paste 1 line: DONE then [newly introduced] wait a second.. then paste 2 lines: a0030 UID STORE 1:3 +FLAGS (\Deleted) a0040 EXPUNGE Notice that the results from UID STORE + EXPUNGE gives: * 1 FETCH (UID 1 FLAGS (\Deleted \Recent)) * 2 FETCH (UID 2 FLAGS (\Deleted \Recent)) * 3 FETCH (UID 3 FLAGS (\Deleted \Recent)) a0030 OK Store completed (0.003 + 0.000 + 0.002 secs). * 3 EXPUNGE * 2 EXPUNGE * 1 EXPUNGE * 1 RECENT a0040 OK Expunge completed (0.003 + 0.000 + 0.002 secs). Verify what's left in the mailbox with: a0050 UID FETCH 1:4 FLAGS * 1 FETCH (UID 4 FLAGS (\Recent)) a0050 OK Fetch completed (0.001 + 0.000 secs). So if I wait some between DONE and UID STORE, it seems to be ok. If I, in the problem-triggering method, change a0030 UID STORE 1:3 +FLAGS (\Deleted) a0040 EXPUNGE to a0030 UID STORE 1:3 +FLAGS (\Deleted) a0035 UID FETCH 1:4 FLAGS a0040 EXPUNGE The untagged responses become: * 1 FETCH (UID 1 FLAGS (\Deleted \Recent)) * 2 FETCH (UID 2 FLAGS (\Deleted \Recent)) * 3 FETCH (UID 3 FLAGS (\Deleted \Recent)) * 4 FETCH (UID 4 FLAGS (\Recent)) * 2 FETCH (UID 2 FLAGS (\Recent)) * 3 FETCH (UID 3 FLAGS (\Recent)) * 1 EXPUNGE * 3 RECENT Full transcript (in&out from screen) from first, failing, run: localhost [127.0.0.1] 143 (imap2) open * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE AUTH=PLAIN AUTH=LOGIN] Dovecot (Debian) ready. a0000 LOGIN "MY-USERNAME" "MY-PASSWORD" a0010 SELECT "error1" a0020 IDLE a0000 OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS THREAD=ORDEREDSUBJECT MULTIAPPEND URL-PARTIAL CATENATE UNSELECT CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS BINARY MOVE SNIPPET=FUZZY] Logged in * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft \*)] Flags permitted. * 4 EXISTS * 4 RECENT * OK [UNSEEN 1] First unseen. * OK [UIDVALIDITY 1520944853] UIDs valid * OK [UIDNEXT 5] Predicted next UID a0010 OK [READ-WRITE] Select completed (0.003 + 0.000 + 0.004 secs). + idling DONE a0030 UID STORE 1:3 +FLAGS (\Deleted) a0040 EXPUNGE a0020 OK Idle completed (7.805 + 7.804 + 7.804 secs). * 2 FETCH (UID 2 FLAGS (\Recent)) * 3 FETCH (UID 3 FLAGS (\Recent)) * 1 EXPUNGE * 3 RECENT a0030 OK Store completed (0.004 + 0.000 + 0.003 secs). a0040 OK Expunge completed (0.004 + 0.000 + 0.003 secs). a0050 UID FETCH 1:4 FLAGS * 1 FETCH (UID 2 FLAGS (\Recent)) * 2 FETCH (UID 3 FLAGS (\Recent)) * 3 FETCH (UID 4 FLAGS (\Recent)) a0050 OK Fetch completed (0.001 + 0.000 secs). Full transcript (in&out from screen) from the second, slower, run: localhost [127.0.0.1] 143 (imap2) open * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE AUTH=PLAIN AUTH=LOGIN] Dovecot (Debian) ready. a0000 LOGIN "MY-USERNAME" "MY-PASSWORD" a0010 SELECT "error2" a0020 IDLE a0000 OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS THREAD=ORDEREDSUBJECT MULTIAPPEND URL-PARTIAL CATENATE UNSELECT CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS BINARY MOVE SNIPPET=FUZZY] Logged in * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft \*)] Flags permitted. * 4 EXISTS * 4 RECENT * OK [UNSEEN 1] First unseen. * OK [UIDVALIDITY 1520944957] UIDs valid * OK [UIDNEXT 5] Predicted next UID a0010 OK [READ-WRITE] Select completed (0.003 + 0.000 + 0.004 secs). + idling DONE a0020 OK Idle completed (2.830 + 2.829 + 2.829 secs). a0030 UID STORE 1:3 +FLAGS (\Deleted) a0040 EXPUNGE * 1 FETCH (UID 1 FLAGS (\Deleted \Recent)) * 2 FETCH (UID 2 FLAGS (\Deleted \Recent)) * 3 FETCH (UID 3 FLAGS (\Deleted \Recent)) a0030 OK Store completed (0.003 + 0.000 + 0.002 secs). * 3 EXPUNGE * 2 EXPUNGE * 1 EXPUNGE * 1 RECENT a0040 OK Expunge completed (0.003 + 0.000 + 0.002 secs). a0050 UID FETCH 1:4 FLAGS * 1 FETCH (UID 4 FLAGS (\Recent)) a0050 OK Fetch completed (0.001 + 0.000 secs). Transcript from .muttdebug0 when using mutt 1.7.2 against the production server with NFS backed storage, marking message 1-3 for deletion and hitting $ for sync. This is how the problem was first found. [2018-03-12 13:46:28] 5> a0020 IDLE^M [2018-03-12 13:46:28] 5< + idling ... [2018-03-12 13:46:29] Marking 3 messages deleted... [2018-03-12 13:46:29] Expunging messages from server... [2018-03-12 13:46:29] 5> DONE^M a0021 UID STORE 1:3 +FLAGS.SILENT (\Deleted)^M a0022 EXPUNGE^M [2018-03-12 13:46:29] 5< a0020 OK Idle completed (0.001 + 1.634 + 1.633 secs). [2018-03-12 13:46:29] 5< * 2 FETCH (FLAGS (\Recent)) [2018-03-12 13:46:29] Handling FETCH [2018-03-12 13:46:29] FETCH response ignored for this message [2018-03-12 13:46:29] 5< * 3 FETCH (FLAGS (\Recent)) [2018-03-12 13:46:29] Handling FETCH [2018-03-12 13:46:29] FETCH response ignored for this message [2018-03-12 13:46:29] 5< * 1 EXPUNGE [2018-03-12 13:46:29] Handling EXPUNGE [2018-03-12 13:46:29] 5< * 3 RECENT [2018-03-12 13:46:29] 5< a0021 OK Store completed (0.001 + 0.000 + 0.001 secs). [2018-03-12 13:46:29] 5< a0022 OK Expunge completed (0.001 + 0.000 secs). [2018-03-12 13:46:29] IMAP queue drained [2018-03-12 13:46:29] imap_cmd_finish: Expunging mailbox *** Method 2, without IDLE (seems to require that I fetch flags before the wait/store) Copy'n'paste the following: a0000 LOGIN "MY-USER" "MY-PASSWORD" a0010 SELECT "error20" a0015 FETCH 1:4 (UID FLAGS) <wait a second, then paste the next two in one go> a0020 UID STORE 1:3 +FLAGS (\Deleted) a0025 EXPUNGE Gives the following transcript: mail3-vm:~/Mail> nc -v localhost 143 localhost [127.0.0.1] 143 (imap2) open * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE AUTH=PLAIN AUTH=LOGIN] Dovecot ready. a0000 LOGIN "MY-USER" "MY-PASSWORD" a0010 SELECT "error20" a0015 FETCH 1:4 (UID FLAGS) a0000 OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS THREAD=ORDEREDSUBJECT MULTIAPPEND URL-PARTIAL CATENATE UNSELECT CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS BINARY MOVE SNIPPET=FUZZY] Logged in * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft \*)] Flags permitted. * 4 EXISTS * 4 RECENT * OK [UNSEEN 1] First unseen. * OK [UIDVALIDITY 1521552107] UIDs valid * OK [UIDNEXT 5] Predicted next UID a0010 OK [READ-WRITE] Select completed (0.001 + 0.000 + 0.001 secs). * 1 FETCH (UID 1 FLAGS (\Recent)) * 2 FETCH (UID 2 FLAGS (\Recent)) * 3 FETCH (UID 3 FLAGS (\Recent)) * 4 FETCH (UID 4 FLAGS (\Recent)) a0015 OK Fetch completed (0.001 + 0.000 secs). a0020 UID STORE 1:3 +FLAGS (\Deleted) a0025 EXPUNGE * 2 FETCH (UID 2 FLAGS (\Recent)) * 3 FETCH (UID 3 FLAGS (\Recent)) * 1 EXPUNGE * 3 RECENT a0020 OK Store completed (0.001 + 0.000 secs). a0025 OK Expunge completed (0.001 + 0.000 secs). /Tomas -- Tomas Forsman, stric(a)cs.umu.se, http://people.cs.umu.se/stric/ `- SysAdmin at Computing Science, University of Umeå

2 3

outlook hangs using TLS
by Vladimir Tiukhtin 11 Jun '18

11 Jun '18

Hello I am using dovecot 2.2.10 on CentOS 7 Any Outlook versions (2007, 2010, 2013...) hang if I tried to use TLS, it works if I switch in client TLS to SSL. Thunderbird works perfect both scenarios Please find debug log mail dovecot[24287]: imap-login: Debug: SSL: where=0x10, ret=1: before/accept initialization [X.X.X.X] mail dovecot[24287]: imap-login: Debug: SSL: where=0x2001, ret=1: before/accept initialization [X.X.X.X] mail dovecot[24287]: imap-login: Debug: SSL: where=0x2002, ret=-1: SSLv2/v3 read client hello A [X.X.X.X] mail dovecot[24287]: imap-login: Debug: SSL: elliptic curve secp384r1 will be used for ECDH and ECDHE key exchanges mail dovecot[24287]: imap-login: Debug: SSL: elliptic curve secp384r1 will be used for ECDH and ECDHE key exchanges mail dovecot[24287]: auth: Debug: auth client connected (pid=24300) mail dovecot[24287]: imap-login: Disconnected (no auth attempts in 31 secs): user=<>, rip=X.X.X.X, lip=X.X.X.X, TLS handshaking: Disconnected, session=<bivt8iNuBgA+A08O> Please find my config # 2.2.10: /etc/dovecot/dovecot.conf # OS: Linux 3.10.0-862.3.2.el7.x86_64 x86_64 CentOS Linux release 7.5.1804 (Core) auth_cache_size = 16 M auth_cache_ttl = 1 days auth_debug = yes auth_mechanisms = plain login auth_username_chars = abcdefghijklmnopqrstuvwxyz.@ auth_verbose = yes default_client_limit = 1024 default_process_limit = 16 doveadm_password = mysecretpasswordsharedamongservers first_valid_uid = 1000 mail_attachment_dir = /srv/attachments mail_attachment_min_size = 4 k mail_debug = yes mail_home = /var/spool/mail/%d/%n mail_location = mdbox:~/mail mail_plugins = replication notify 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 ihave mbox_write_locks = fcntl namespace inbox { inbox = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox "Sent Messages" { auto = subscribe special_use = \Sent } mailbox Spam { auto = create special_use = \Junk } mailbox Trash { auto = subscribe special_use = \Trash } mailbox virtual/All { auto = no special_use = \All } prefix = type = private } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } protocols = imap lmtp service aggregator { fifo_listener replication-notify-fifo { mode = 0666 user = $default_internal_user } unix_listener replication-notify { mode = 0666 user = $default_internal_user } } service auth { unix_listener auth-userdb { mode = 0666 } } service doveadm { inet_listener { port = 55555 } } service imap-login { inet_listener imap { port = 0 } inet_listener imaps { port = 993 ssl = yes } process_min_avail = 2 service_count = 1 } service imap { client_limit = 0 } service lmtp { unix_listener lmtp { group = postfix mode = 0600 user = postfix } } ssl = required ssl_cert = </etc/letsencrypt/live/mail.example.com/fullchain.pem ssl_dh_parameters_length = 2048 ssl_key = </etc/letsencrypt/live/mail.example.com/privkey.pem ssl_prefer_server_ciphers = yes ssl_protocols = !SSLv2 !SSLv3 TLSv1 TLSv1.1 TLSv1.2 userdb { driver = prefetch } userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } verbose_ssl = yes protocol imap { imap_client_workarounds = tb-extra-mailbox-sep delay-newmail }

4 6

Doveadm sync: Can't create mailbox mail_public/public: Permission denied if synchronize all the available namespaces
by vkosharskiy＠gmail.com 09 Jun '18

09 Jun '18

I have old dovecot server: (# 2.2.33.2 (d6601f4ec): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.21 (92477967) # OS: Linux 4.14.15-3.el7xen.x86_64 x86_64 CentOS Linux release 7.4.1708 (Core) and new dovecot server: # 2.3.1 (c5a5c0c82): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.devel (61b47828) # OS: Linux 4.14.47-5.el7xen.x86_64 x86_64 CentOS Linux release 7.5.1804 (Core) I try to sync old server with doveadm sync with parameter -N (Synchronize all the available namespaces) Sync successfull in log, but destination server in log have "Can't create mailbox mail_public/public: Permission denied." Config dumps, logs in attaches.

1 0

Re: 2.3.1 Replication is throwing scary errors
by Reuben Farrelly 09 Jun '18

09 Jun '18

Hi Andy, Funny you say that - I've been testing this very problem for some time today to narrow down the commits where I think the problem started occurring. So far I have been able to roll forward to commit from git: 74ef8506dcb946acc42722683e49fdcb964eed19 >> "doveadm: Unref header search context after use" . So far I have been running on that code for a few hours and I'm not yet seeing the problem, which indicates the issue is probably subsequent to this. I'm of the view that the problem started occurring somewhere between that commit above on 6 March and the final 2.3.1 release on 27 March. There are a lot of changes between those two dates, and testing to narrow down to one specific commit is extremely time consuming. It would be really helpful if even one of the Dovecot developers could comment on this and give us some direction (or candidate commits to investigate) or just let us know if the root cause has been found. This bug is a showstopper and has stopped me tracking master-2.3 for over 3 months now, as I can't test later builds or even upgrade to the 2.3.1 release while replication is so broken. Reuben > Message: 1 > Date: Sun, 6 May 2018 13:21:57 +1000 > From: Andy Weal <andy(a)bizemail.com.au> > To: dovecot(a)dovecot.org > Subject: 2.3.1 Replication is throwing scary errors > Message-ID: <f4274128-350b-9a74-a344-8e6caeffa112(a)bizemail.com.au> > Content-Type: text/plain; charset="utf-8"; Format="flowed" > > Hi all, > > New to the mailing lists but have joined up because of above */2.3.1 > Replication is throwing scary errors > > > /*Brief system configuration > ??? MX1 - Main > ??? ??? Freebsd 11.1-Release-p9 > ??? ??? Hosted on a Vultr VM in Sydney AU > ??? ??? MTA = Postfix 3.4-20180401 > ??? ??? Dovecot = 2.3.1 > ??? ??? File system = ufs > ??? MX2 - Backup > ??? ??? Freebsd 11.1-Release-p9 > ??? ???? Running on bare metal - no VM or jails > ??? ??? MTA = Postfix 3.4-20180401 > ??? ??? Dovecot = 2.3.1 > ??? ??? File system = ufs ( on SSD) > > */ > /*Brief sequence of events > > 1. ??? apx 10 days back upgraded both mx1 and mx2 to dovecot 2.3.1_2 > from 2.3.0 ? (service dovecot stop, portmaster upgrade, service > dovecot start) > 2. ??? both systems ran ok with no errors for 10 days. > 3. ??? Last night I shutdown mx2 and restarted it a few hours later > 4. ??? within minutes i was getting the following types of errors on mx2 > > ???????? May 06 12:56:29 doveadm: Error: Couldn't lock > /var/mail/vhosts/example.net/user1/.dovecot-sync.lock: > fcntl(/var/mail/vhosts/example.net/user1/.dovecot-sync.lock, write-lock, > F_SETLKW) locking failed: Timed out after 30 seconds (WRITE lock held by > pid 1960) > > ? Before i venture down the rabbit hole of fault finding and excess > coffee consumption I was wondering if any of you had any updates on the > problems discussed below. > > > Cheers for now, > Andy > > > > Hi, > > [Formatting is a bit rough, replying from a trimmed digest email] > >> /Message: 1 />/Date: Fri, 6 Apr 2018 15:04:35 +0200 />/From: Michael Grimm <trashcan at ellael.org > <https://dovecot.org/mailman/listinfo/dovecot>> />/To: Dovecot Mailing List <dovecot at dovecot.org > <https://dovecot.org/mailman/listinfo/dovecot>> />/Subject: Re: 2.3.1 Replication is throwing scary errors />/Message-ID: <E7E7A927-68F8-443F-BA59-E66CED8FE878 at ellael.org > <https://dovecot.org/mailman/listinfo/dovecot>> />/Content-Type: text/plain; charset=utf-8 />//>/Reuben Farrelly wrote: />>/From: Michael Grimm <trashcan at ellael.org > <https://dovecot.org/mailman/listinfo/dovecot>> />//>>>/[This is Dovecot 2.3.1 at FreeBSD STABLE-11.1 running in two jails at > distinct servers.] />>>/I did upgrade from 2.2.35 to 2.3.1 today, and I do become pounded by > error messages at server1 (and vice versa at server2) as follows: />>>/| Apr 2 17:12:18 <mail.err> server1.lan dovecot: doveadm: Error: > dsync(server2.lan): I/O has stalled, \ />>>/no activity for 600 seconds (last sent=mail_change, last > recv=mail_change (EOL)) />>>/| Apr 2 17:12:18 <mail.err> server1.lan dovecot: doveadm: Error: Timeout > during state=sync_mails \ />>>/(send=changes recv=mail_requests) />>>/[?] />>>/| Apr 2 18:59:03 <mail.err> server1.lan dovecot: doveadm: Error: > dsync(server2.lan): I/O has stalled, \ />>>/no activity for 600 seconds (last sent=mail, last recv=mail (EOL)) />>>/| Apr 2 18:59:03 <mail.err> server1.lan dovecot: doveadm: Error: Timeout > during state=sync_mails \ />>>/(send=mails recv=recv_last_common) />>>/I cannot see in my personal account any missing replications, *but* I > haven't tested this thoroughly enough. I do have customers being > serviced at these productive servers, *thus* I'm back to 2.2.35 until I > do understand or have learned what is going on. />//>/In my reply to this statement of mine I mentioned that I have seen those > timeouts quite some times during the past year. Thus, I upgraded to > 2.3.1 again, and boom: after some hours I ended up in hanging processes > [1] like (see Remko's mail in addition) ... />//>/doveadm-server: [IP4/6 <USER1> SOME/MAILBOX import:0/0] (doveadm-server) />//>/? at server2 paired with a file like ? />//>/-rw------- 1 vmail dovecot uarch 0 Apr 3 16:52 > /home/to/USER1/.dovecot-sync.lock />//>/Corresponding logfile entries at server2 are like ? />//>/Apr 3 17:10:49 <mail.err> server2.lan dovecot: doveadm: Error: Couldn't > lock /home/to/USER1/.dovecot-sync.lock: \ />/fcntl(/home/to/USER1/.dovecot-sync.lock, write-lock, F_SETLKW) locking > failed: Timed out after 30 seconds \ />/(WRITE lock held by pid 51110) />//>/[1] Even stopping dovecot will not end those processes. One has to > manually kill those before restarting dovecot. />//>/After one day of testing 2.3.1 with a couple of those episodes of > locking/timeout, and now missing mails depending with server your MUA > will connect to, I went back to 2.2.35. After two days at that version I > never had such an episode again. />//>>/It's not just you. This issue hit me recently, and it was impacting />>/replication noticeably. I am following git master-2.3 . />/[...] />>/There is also a second issue of a long standing race with replication />>/occurring somewhere whereby if a mail comes in, is written to disk, is />>/replicated and then deleted in short succession, it will reappear />>/again to the MUA. I suspect the mail is being replicated back from />>/the remote. A few people have reported it over the years but it's not />>/reliable or consistent, so it has never been fixed. />>/And lastly there has been an ongoing but seemingly minor issue />>/relating to locking timing out after 30s particularly on the remote />>/host that is being replicated to. I rarely see the problem on my />>/local disk where almost all of the mail comes in, it's almost always />>/occurring on the replicate/remote system. />//>/It might be time to describe our setups in order to possibly find co > mmon > grounds that might trigger this issue you describe and Rimko and myself > ran into as well. />//>/Servers: Cloud Instances (both identical), around 25ms latency apart. />/Intel Core Processor (Haswell, no TSX) (3092.91-MHz K8-class CPU) />/Both servers are connected via IPsec/racoon tunnels />/OS: FreeBSD 11.1-STABLE (both servers) />/Filesystem: ZFS />/MTA: postfix 3.4-20180401 (postfix delivers via dovecot's LMTP) />/IMAP: dovecot running in FreeBSD jails (issues with 2.3.1, fine with > 2.2.35) />/Replication: unsecured tcp / master-master />/MUA: mainly iOS or macOS mail.app, rarely roundcube / > For me: > > Servers: Main: VM on a VMWare ESXi local system (light > load), local SSD disks (no NFS) > Redundant: Linode VM in Singapore, around 250ms away > Also no NFS. Linode use SSDs for IO. > There is native IPv6 connectivity between both VMs. > As I am using TCPs I don't have a VPN between them - > just raw IPv6 end to end. > OS: Gentoo Linux x86_64 kept well up to date > Filesystem: EXT4 for both > MTA: Postfix 3.4-x (same as you) > IMAP: Dovecot running natively on the machine (no jail/chroot) > Replication: Secured TCP / master-master (but only one master is > actively used for SMTP and MUA access) > MUA: Thunderbird, Maildroid, MS Mail, Gmail client, > Roundcube, LG Mail client on handset etc > >> /I believe it is worthwhile to mention here that I run a poor man's > fail-over approach (round-robin DNS) as follows: />//>/DNS: mail.server.tld resolves to one IP4 and one IP6 address of each > server, thus 4 IP addresses in total / > For me I have a simple pair of servers that replicate mail to each > other. Clients connect to the main server only, which is where mail > comes in. The second one that experiences the problem with locking is > only a redundant server which is a secondary MX, that only gets > occasional SMTP deliveries from time to time. So the amount of > replication back from the "secondary" is very minimal; the vast bulk of > the replication is the primary replicating changes out. > > Reuben >

8 20

sieve, pigeonhole; reject message
by dovecot-user 08 Jun '18

08 Jun '18

Hello everybody. I use the version of dovecot 2.3.0.1 and postfix 3.3.0 on my test computer. Postfix pass incoming messages to Dovecot via the LMTP protocol. I want to understand how to fine tune the "reject" action in sieve-scripts. The task: in my installation I use the translation of a set of aliases into the (hidden) target email address inside postfix (postfix directives: canonical_classes = envelope_recipient; canonical_maps = hash://etc/postfix/canonical), so in dovecot the mails fall into one mailbox; However, the original headers (for example, the alias of the recipient) can be extracted with sieve scripts (the "Received" header). In my case, when I use the "reject" action in the sieve script, dovecot generates a message to the sender with the text: "Your message to <hidden(a)domain.tld> was automatically rejected ..", but this behavior opens the address to the sender of what is hidden behind the alias. Is it possible to redefine the text of the reject message using the extracting values from the "Received" header so that the email address hidden behind the alias does not appear there? Or some other way to customize the reject-message? Thank you.

1 0

dovecot-pigeonhole Missing sieve_imapsieve Plugin?
by Will Foster 07 Jun '18

07 Jun '18

Hi Folks, I am having a problem configuring imapsieve via dovecot-pidgeonhole on CentOS7. After following the docs here: https://wiki2.dovecot.org/Pigeonhole/Sieve/Plugins/IMAPSieve I get: dovecot[22026]: managesieve: Fatal: Plugin 'sieve_imapsieve' not found from directory /usr/lib64/dovecot/sieve dovecot[22026]: doveconf: Error: managesieve-login: dump-capability process returned 89 There doesn't seem to be that plugin present or provided by dovecot-pigeonhole # ls -lah /usr/lib64/dovecot/sieve/ total 56K drwxr-xr-x. 2 root root 46 Jun 5 12:16 . drwxr-xr-x. 7 root root 4.0K Jun 5 12:16 .. -rwxr-xr-x. 1 root root 52K Aug 3 2017 lib90_sieve_extprograms_plugin.so Am I doing something wrong? This is provided via the CentOS EPEL package Here's my system details: * dovecot-pigeonhole-2.2.10-8.el7.x86_64 * CentOS 7.5 on XFS * Rainloop Webmail / Mutt / IMAP access Here's my dovecot -n ------------ # 2.2.10: /etc/dovecot/dovecot.conf managesieve(root): Fatal: Plugin 'sieve_imapsieve' not found from directory /usr/lib64/dovecot/sieve doveconf: Error: managesieve-login: dump-capability process returned 89 # OS: Linux 3.10.0-862.2.3.el7.x86_64 x86_64 CentOS Linux release 7.5.1804 (Core) first_valid_uid = 1000 info_log_path = /var/log/dovecot-info.log log_path = /var/log/dovecot.log mail_location = mbox:~/Mail:INBOX=/home/%u/Mail/INBOX_MAIL mail_privileged_group = mail mbox_write_locks = fcntl namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { args = %s driver = pam } passdb { driver = pam } plugin { imapsieve_url = sieve://localhost:4190 sieve = file:~/sieve;active=~/.dovecot.sieve sieve_after = /etc/dovecot/sieve-after sieve_dir = ~/sieve sieve_plugins = sieve_imapsieve sieve_extprograms sieve_user_log = ~/.dovecot.sieve.log } protocols = imap sieve sieve service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } } service managesieve-login { inet_listener sieve { port = 4190 } process_min_avail = 0 service_count = 1 vsz_limit = 64 M } ssl = required ssl_cert = </etc/pki/tls/certs/example.net.crt ssl_key = </etc/pki/tls/private/example.net.key userdb { driver = passwd } userdb { driver = passwd } protocol lmtp { mail_plugins = " sieve" } protocol lda { mail_plugins = " sieve" } protocol imap { mail_plugins = " imap_sieve" } ------------- Thanks for any guidance here. -- @sadsfae // gpg: A31F27E0 // irc: sadsfae come have a squat at https://hobo.house

2 2

Re: 2.3.1 Replication is throwing scary errors
by Michael Grimm 07 Jun '18

07 Jun '18

Am 2018-06-07 08:48, schrieb Remko Lodder: > On Thu, Jun 07, 2018 at 08:04:49AM +0200, Michael Grimm wrote: >> Conclusion: After 12 hours of running a patched FBSD port I do get >> those >> error messages but replictaion seems to work now. But, I still have >> the >> feeling that there might something else going wrong. > > I agree with that. Are you using the new pkg that ler@ prepared ? That > includes > the patch and is a 'native' package.. Yes, I am running this new port from ler@. And: Thanks for his very fast modification! Regards, Michael

1 0

Shared mailboxes, index files and 'per-user-seen' flags
by Thomas Robers 07 Jun '18

07 Jun '18

Hello, i have a dovecot server version 2.3.1 under CentOS 6.9 and we're using shared mailboxes with index files shared. With this configuration I can see a lot of error messages like: Jun 6 13:20:31 mail dovecot: Error: imap(userA(a)tutech.de)<4513> <onjjWPdtDuLAqG3R>: /export/home/imap/userA(a)tutech.de/shared /userB(a)tutech.de/folder/dovecot.index.pvt view is inconsistent In 10-mail.conf the location setting is: location = maildir:%%h/Maildir:INDEXPVT=%h/shared/%%u I thought setting the index files to "not shared" might help to get rid of the errors, so I changed the setting to: location = maildir:%%h/Maildir:INDEX=%h/shared/%%u:INDEXPVT=%h /shared/%%u like it's mentioned in the Dovecot wiki. But that doesn't work as I expected, because the 'per-user-seen' flags do not work correctly anymore, i think. If UserA, who has UserB as shared mailbox, changes the seen flags of UserBs INBOX, UserBs seen flags are also changed. The other way, if UserB changes seen flags in his INBOX they are not changed in the shared view of UserA. Is this the supposed way to work or do i have an error in the configuration? Any help is appreciated. Thanks, Thomas. Here's my currently used configuration: # 2.3.1 (c5a5c0c82): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.devel (61b47828) # OS: Linux 2.6.32-696.23.1.el6.x86_64 x86_64 CentOS release 6.9 (Final) ext4 # Hostname: mail.tutech.de auth_master_user_separator = * auth_mechanisms = plain login auth_verbose = yes disable_plaintext_auth = no doveadm_password = # hidden, use -P to show it doveadm_port = 12345 imap_max_line_length = 2 M mail_debug = yes mail_location = maildir:/export/home/imap/%Lu/Maildir mail_plugins = acl zlib mail_log notify mail_prefetch_count = 1 mailbox_idle_check_interval = 10 secs 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 { hidden = no ignore_on_failure = no inbox = no list = children location = maildir:%%h/Maildir:INDEXPVT=%h/shared/%%u prefix = shared/%%u/ separator = / subscriptions = yes type = shared } namespace inbox { hidden = no inbox = yes list = 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 = /etc/dovecot/master-users driver = passwd-file master = yes } passdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } plugin { acl = vfile:/etc/dovecot/global-acls:cache_secs=300 acl_shared_dict = file:/export/home/shared-db/shared-mailboxes mail_log_events = append delete undelete expunge copy mailbox_delete mailbox_rename flag_change mail_log_fields = uid box msgid size from flags mail_replica = tcp:mail2.tutech.de sieve = ~/.dovecot.sieve sieve_dir = ~/sieve sieve_global = /var/lib/dovecot/sieve/global/ sieve_user_log = ~/.dovecot.sieve.log zlib_save = gz zlib_save_level = 6 } protocols = imap pop3 lmtp sieve sieve service aggregator { fifo_listener replication-notify-fifo { mode = 0666 user = vmail } unix_listener replication-notify { mode = 0666 user = vmail } } service auth { unix_listener /var/spool/postfix/private/auth { mode = 0666 } unix_listener auth-userdb { group = vmail mode = 0660 user = vmail } } service config { unix_listener config { user = vmail } } service doveadm { inet_listener { port = 12345 } user = vmail } service imap-login { inet_listener imaps { port = 993 ssl = yes } process_limit = 500 process_min_avail = 20 } service imap { executable = imap } service lmtp { inet_listener lmtp { address = 127.0.0.1 port = 24 } } service managesieve-login { inet_listener sieve { port = 4190 } inet_listener sieve_deprecated { port = 2000 } } service pop3-login { inet_listener pop3s { port = 995 ssl = yes } } service pop3 { executable = pop3 } service replicator { unix_listener replicator-doveadm { mode = 0666 } } ssl = required ssl_cert = </etc/pki/dovecot/certs/mail.tutech.de.crt_chain ssl_cipher_list = ALL:!LOW:!SSLv2:!EXP:!aNULL:!EXPORT ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it syslog_facility = local6 userdb { args = /etc/dovecot/dovecot-ldap-userdb.conf.ext driver = ldap } protocol lmtp { mail_plugins = acl zlib mail_log notify sieve } protocol imap { mail_max_userip_connections = 100 mail_plugins = acl zlib mail_log notify imap_zlib imap_acl rawlog_dir = /tmp/rawlog/%u }

2 1

Header DATE field not returned when placed after MIME section
by Xavier Guerin 06 Jun '18

06 Jun '18

Hello, I am using Dovecot 2.2.34p0 on OpenBSD 6.3 stable. I am writting an application using the vmime (http://www.vmime.org) library (x-ref issue: https://github.com/kisli/vmime/issues/199) I noticed through testing over my own e-mail server that in some situations the DATE field is not returned upon ENVELOPE or HEADER.FIELDS request. The e-mails at fault happen to have the DATE field at the very end of the header, after the MIME section. Example 1: Delivered-To: Received: Return-Path: Delivered-To: DKIM-Signature: From: To: Message-ID: Subject: MIME-Version: 1.0 Content-Type: text/html;charset=UTF-8 Content-Transfer-Encoding: 7bit Date: Fri, 01 Jun 2018 17:44:44 -0400 Example 2: Return-Path: Delivered-To: Received: Delivered-To: DKIM-Signature: From: Reply-To: To: Subject: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_338_1573405959.1527768044781" X-Mailer: EMail_2.0 Date: Fri, 01 Jun 2018 17:36:01 -0400 Thanks in advance for the insight,

3 2

offtopic: Solr compatible IMAP client
by Andy Smith 04 Jun '18

04 Jun '18

Hi, not sure if I'm allowed to go this off topic on here, sorry if not! I've just installed Solr FTS for Dovecot and its great, as is Dovecot! ;) It works perfectly for fast searches using Roundcube, but can anyone suggest any Windows and/or Linux mail clients that work well with IMAP searches rather than doing their own searches on local copies of mails? I've had a look at Thunderbird and you can use IMAP search, buy you have to manually select it from an advanced search dialogue and it seems you cannot make this the default behaviour. I also tried OperaMail but it doesn't appear to work at all (only header is searchable without downloading local copies). I'm pretty sure Outlook will only use its own search engine on its local copy of data. thanks a lot, Andy. PS this guide was really helpful for setting up Solr FTS with a recent release of Solr (I'm using 6.5), might be worth including a link somewhere on the Dovecot wiki?: http://mor-pah.net/2016/08/15/dovecot-2-2-with-solr-6-or-5

4 7

Re: SSL error after upgrading to 2.31
by Aki Tuomi 01 Jun '18

01 Jun '18

You forgot to cc the list. ssl_ca is used only for validating client certificates. ---Aki TuomiDovecot oy -------- Original message --------From: Marc Perkel <marc(a)perkel.com> Date: 21/05/2018 18:25 (GMT+02:00) To: Aki Tuomi <aki.tuomi(a)dovecot.fi> Subject: Re: SSL error after upgrading to 2.31 On 05/21/2018 07:54 AM, Aki Tuomi wrote: Does ssl_cert file contain intermediates? No - but the ssl_ca does. --- Aki Tuomi Dovecot oy -------- Original message -------- From: Marc Perkel <marc(a)perkel.com> Date: 21/05/2018 16:32 (GMT+02:00) To: dovecot(a)dovecot.org Subject: SSL error after upgrading to 2.31 After upgrading to 2.31 I'm getting this error. Not sure what I'm doing wrong. No (No signatures could be verified because the chain contains only one certificate and it is not self signed.) ssl = yes ssl_cert = </etc/exim/certs/ctyme.com.crt ssl_key = </etc/exim/certs/ctyme.com.key ssl_ca = </etc/exim/certs/ca.crt local mail.ctyme.com { protocol imap { ssl_cert = </etc/exim/certs/ctyme.com.crt ssl_key = </etc/exim/certs/ctyme.com.key ssl_ca = </etc/exim/certs/ca.crt } protocol pop3 { ssl_cert = </etc/exim/certs/ctyme.com.crt ssl_key = </etc/exim/certs/ctyme.com.key ssl_ca = </etc/exim/certs/ca.crt } } local mail.junkemailfilter.com { protocol imap { ssl_cert = </etc/exim/certs/junkemailfilter.com.crt ssl_key = </etc/exim/certs/junkemailfilter.com.key ssl_ca = </etc/exim/certs/ca.crt } protocol pop3 { ssl_cert = </etc/exim/certs/junkemailfilter.com.crt ssl_key = </etc/exim/certs/junkemailfilter.com.key ssl_ca = </etc/exim/certs/ca.crt } }

3 9

Struggling with sieve, fileinto and variables.
by Barry Pearce 31 May '18

31 May '18

Hi, Im on Manjaro linux fully up to date running dovecot 2.3.1-2 pigeonhole 0.5.1-2 All is running well except I am having problems with fileinto - it refuses to use variables, and mailboxexists is also failing for me. Im just dealing with plus addressing - should be simple but the behaviour Im experiencing isnt right. require ["variables", "envelope", "fileinto", "subaddress", "mailbox"]; if envelope :matches :detail "to" "*" { set :lower "name" "${1}"; } fileinto :create "folder3"; This works, but changing the last line to: fileinto :create "${name}"; fails and files into inbox. As does: fileinto :create "${1}"; It makes no difference if the fileinto is placed inside the if statement or otherwise. Using sieve-test suggests the basic script it should work and traces show the right action. On a related matter the script Im actually trying to get to work is: require ["variables", "envelope", "fileinto", "subaddress", "mailbox"]; if envelope :matches :detail "to" "*" { set :lower "name" "${1}"; } if mailboxexists "${name}" { fileinto :create "${name}"; } But fails and files in the inbox. Modifying the script to: require ["variables", "envelope", "fileinto", "subaddress", "mailbox"]; if envelope :matches :detail "to" "*" { set :lower "name" "${1}"; } if mailboxexists "${name}" { fileinto :create "folder7"; } else { fileinto :create "folder8"; } Files into folder8. So the mailboxexists is failing. ## Started executing script 'plus-addressing' 3: envelope test 3: starting `:matches' match with `i;ascii-casemap' comparator: 3: getting `to' part from message envelope 3: extracting `detail' part from address <test+folder4(a)test.net> 3: matching value `folder4' 3: with key `*' => 1 3: finishing match with result: matched 3: jump if result is false 3: not jumping 4: set command 7: modify :lower "folder4" => "folder4" 7: assign `name' [0] = "folder4" 7: mailboxexists test 7: mailbox `folder4' cannot be opened 7: some mailboxes are unavailable 7: jump if result is false 7: jumping to line 9 10: fileinto action 10: store message in mailbox `folder8' ## Finished executing script 'plus-addressing' Here folder4 actually does exist - so the sieve-test confirms that issue. Im at a loss as to whats going on. Im particularly perplexed by the difference in behaviour between sieve-test and the result under the live server. Any ideas?

2 3

strange misflagging of incoming mail as trash
by Robb Aley Allan 31 May '18

31 May '18

Setting up postfix/dovecot on a clean FreeBSD cloud server, and have discovered a strange problem resulting from the interaction of Mac OS X Mail and dovecot (using the Maildir file structure). Essentially, under very specific circumstances, Mail somehow tells dovecot that a new incoming message is trash, dovecot marks it as such, and the message effectively vanishes. The specific circumstance is as follows: 1. A message is sent to a server running postfix. It is placed in the Maildir mail structure in the “new” directory. 2. OS X Mail is used to retrieve mail via IMAP, and dovecot transfers the message from “new” to “cur”. 3. OS X Mail has a rule that seeks to transfer an incoming message to a subfolder if the message sender belongs to a group created in the Contacts app (IOW the sender is matched against an OS-internal contacts database). 4. IF the sender is the user, AND the user is in the group against which the rule is compared, the message is marked as trash (suffix “T”) and is never loaded into the mail client, either in the inbox or in the trash folder. For all intents and purposes, it disappears. The connection log shows the following line: "WROTE May 30 23:38:11.960 [kCFStreamSocketSecurityLevelTLSv1_2] -- host:cloud.helical.com -- port:993 -- socket:0x6080004b6c80 -- thread:0x604000678e40 12.3 UID STORE 125 +FLAGS.SILENT (\Deleted)” which appears to be the client instructing dovecot to mark the message as deleted. I have the log files from the connection on both sides, and the console log from the Mac, but can’t understand 1. how Mail decides that the message should be deleted, and 2. why Mail “loses” the message (doesn’t appear in the Trash mailbox or anywhere else). _____ Robb Aley Allan

1 0

imapsieve: mailbox Trash: FLAG event
by Peter Schiffer 30 May '18

30 May '18

Hi all, after upgrade from Dovecot 2.2 to 2.3 I started to see that emails from Trash folder are automatically deleted after ~7 days. Email clients are not configured to automatically expunge or empty trash on log out (I see this behavior for multiple mailboxes, with different clients). With mail_debug enabled, I see this log message for every email that gets deleted from Trash: May 29 08:02:17 hostname dovecot: imap(some@mail)<7725><xxb6+VFtL+JT0CE 8>: Debug: imapsieve: mailbox Trash: FLAG event (changed flags: \Deleted) I have Dovecot 2.3.1 (8e2f634) and Pigeonhole 0.5.1 for sieve. My configuration can be found here: https://github.com/pschiffe/mailcow-dockerized/tree/master/data/conf/dovecot There is enabled support for sieve config in sql, but all sieve tables are empty, and there are no sieve filters for Trash flagging. Do you know how to find the source of that Trash flag event? I need to disable it or to configure it so it deletes emails at least couple of months old. Thanks all, peter

2 1

Re: Fatal: nfs flush requires mail_fsync=always
by Juan C. Blanco 30 May '18

30 May '18

Hello, any news about the attached error? I'm preparing the 2.2 to 2.3 upgrade and having the same error. We have the mail stores in an NFS filer. Regards > On 19.01.2018 11:55, Søren Skou wrote: >> Hiya all, >> >> I'm seeing this "Fatal: nfs flush requires mail_fsync=always" error on >> my testbed. The issue is that from what I can see, mail_fsync is set >> to always : >> >> # doveconf -n | grep mail_fs >> mail_fsync = always >> >> The result is that the client does not connect at all, which is not >> really what I wanted to happen :) >> >> Any idea what is going wrong here? >> >> Best regards >> Søren P. Skou >> >> doveconf -n >> >> # 2.3.1.alpha0 (bdfa22623) [XI:2:2.3.1~alpha0-1~auto+14]: >> /etc/dovecot/dovecot.conf >> # Pigeonhole version 0.5.1.alpha0 (d5f710e0) >> # OS: Linux 4.9.0-4-amd64 x86_64 Debian 9.3 nfs >> auth_worker_max_count = 200 >> dict { >> expire = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext >> quota = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext >> sqlquota = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext >> } >> disable_plaintext_auth = no >> lock_method = dotlock >> mail_fsync = always >> mail_location = maildir:/mnt/virtual_mail/%d/%n >> mail_nfs_index = yes >> mail_nfs_storage = yes >> mail_plugins = quota >> mailbox_list_index = no >> metric imap_select_no { >> event_name = imap_command_finished >> filter { >> name = SELECT >> tagged_reply_state = NO >> } >> } >> mmap_disable = yes >> namespace inbox { >> inbox = yes >> location = >> mailbox Drafts { >> special_use = \Drafts >> } >> mailbox Junk { >> auto = subscribe >> special_use = \Junk >> } >> mailbox Sent { >> special_use = \Sent >> } >> mailbox "Sent Messages" { >> special_use = \Sent >> } >> mailbox Trash { >> special_use = \Trash >> } >> prefix = >> } >> passdb { >> args = /etc/dovecot/dovecot-sql.conf.ext >> driver = sql >> } >> plugin { >> quota = dict:User quota::proxy::sqlquota >> quota_grace = 10%% >> quota_rule = *:storage=1000m:messages=300000 >> quota_rule2 = Trash:storage=+10%%:messages=+10%% >> quota_rule3 = Junk:storage=+20%%:messages=+20%% >> quota_status_nouser = DUNNO >> quota_status_overquota = 552 5.2.2 Mailbox is full >> quota_status_success = DUNNO >> quota_warning = storage=75%%:messages=75%% quota-warning 75 %u >> quota_warning2 = storage=95%%:messages=95%% quota-warning 95 %u >> quota_warning3 = -storage=100%%:messages=100%% quota-warning below %u >> sieve = /etc/dovecot/sieve/default.sieve >> sieve_global_dir = /etc/dovecot/sieve >> } >> protocols = " imap pop3" >> service dict { >> unix_listener dict { >> mode = 0600 >> user = vmail >> } >> } >> service imap { >> executable = imap >> } >> service quota-status { >> client_limit = 1000 >> executable = quota-status -p postfix >> inet_listener { >> address = 127.0.0.1 >> port = 12340 >> } >> } >> service quota-warning { >> executable = script /usr/local/bin/quota-warning.sh >> user = vmail >> } >> ssl_ca = /etc/ssl/certs/ca-root.crt >> ssl_cert = </etc/ssl/certs/stjerne.danskkabeltv.dk-2019.crt >> ssl_cipher_list = TLSv1+HIGH !SSLv2 !RC4 !aNULL !eNULL !3DES-CBC !3DES @STRENGTH >> ssl_dh = # hidden, use -P to show it >> ssl_key = # hidden, use -P to show it >> userdb { >> args = uid=2000 gid=2000 home=/mnt/virtual_mail/%d/%n >> driver = static >> } >> protocol lmtp { >> mail_plugins = quota >> } >> protocol lda { >> mail_plugins = quota >> } >> protocol imap { >> mail_plugins = quota imap_quota >> rawlog_dir = /tmp/rawlog/%u >> } > > Hi! > > Thanks, we'll look into it. > > Aki -- +-------------------------------------------------------------------+ | Juan C. Blanco | | | | Centro de Calculo | | | E.T.S. Ingenieros Informáticos | E-mail: jcblanco(a)fi.upm.es | | Universidad Politécnica de Madrid | | | Campus de Montegancedo | | | Boadilla del Monte | Tel.: (+34) 91 067 2771 | | 28660 MADRID (Spain) | Fax : (+34) 91 336 7412 | +-------------------------------------------------------------------+

2 2

Second rule isn't apply when first rule matches
by daniel_1983＠protonmail.com 30 May '18

30 May '18

Dear list, I want to define two concurrent rules : 1. I want to flag an e-mail containing the word "cloud" in the body 2. I want to move mail sent explicitly to me (as opposed to mail sent to an alias I am part of) going to "INOBX.I must answere this" If I put rule (1) first, everything works as expected. If put rule (2) first, only that rule applies. Here's a small test case you should be able to reproduce on your setup. Let's work on this fake test e-mail : $ cat testmail.eml Date: Mon, 28 May 2018 12:41:53 +0100 From: friend(a)otherdomain.tld To: me(a)mydomain.tld Subject: dur dur la vie mon frère, le cloud c'est le top du top Here's the first, broken version of the script $ cat test.sieve require ["body","fileinto","imap4flags","vacation"]; # rule:[Mail about me] if anyof (header :contains "to" "me(a)mydomain.tld", body :text :contains "ahmed") { fileinto "INBOX.I must answere this"; } # rule:[Mail about the Cloud] if body :text :contains "cloud" { addflag "\\Flagged"; } Let's test it out, the two rules should be applied : $ sieve-test test.sieve testmail.eml Performed actions: * store message in folder: INBOX.I must answere Implicit keep: (none) sieve-test(root): Info: final result: success $ Notice that the last rule isn't applied although it matches. Now we invert the order of the rules and apply the script on the same test e-mail : $ cat test.sieve require ["body","fileinto","imap4flags","vacation"]; # rule:[Mail about the Cloud] if body :text :contains "cloud" { addflag "\\Flagged"; } # rule:[Mail about me] if anyof (header :contains "to" "me(a)mydomain.tld", body :text :contains "ahmed") { fileinto "INBOX.I must answere this"; } Running the test again : $ sieve-test test.sieve testmail.eml Performed actions: * store message in folder: INBOX.I must answere + add IMAP flags: \flagged Implicit keep: (none) sieve-test(root): Info: final result: success $ The IMAP flag was set ! Any ideas ?

2 3

Problem in Pigeonhole sievec
by Thorsten Hater 30 May '18

30 May '18

Dear all, I stumbled upon the following behaviour of Pigeonhole, which I consider to be problematic. A user deployed a Sieve script similar to the following snippet if not anyof (address :is ["from","cc"] ["...", ..., "...@... GARBAGE", ...] { fileinto "inbox.Trash"; stop; } Note the extra line break before GARBAGE. This script is obviously broken, but gets accepted by sievec and only fails later, at runtime with line X: error: found stray carriage-return (CR) character in quoted string started at line X. So, the question is whether line breaks in strings are allowed in general and the runtime error is unavoidable, or should sievec return an error? Best regards, Thorsten

3 3

OAUTH2 + proxying [host=??]
by DevOps 30 May '18

30 May '18

All, We currently use a proxy configuration with an sql query to authenticate and discover which backend server an address belongs to and proxy the connection to that host to authenticate and retrieve mail. We are looking to move to OAUTH2 for authentication and am just trying to figure how how to get that extra host information as part of the passdb query when using this mechanism. Looking at doco if we were running a director setup (which we are not) that process seems to be able to poke that info into response but is there any other way of doing this ? Should we be getting or can we get OAUTH2 to return extra fields and configure the pass_attrs to be host=%{passdb:proxyToHost} or something like that ? Any information/thoughts would be good to hear. rgds Matt

2 1

Bug: Dovecot index loosing sync with FTS despite "fts_autoindex = yes"
by kfx 29 May '18

29 May '18

dovecot 2.2.34 solr 7.2 I only see new messages after typing on the server "doveadm fts rescan -u username" though I've followed the wiki and added "fts_autoindex = yes" in 90-plugin.conf . Subsequent search for the same pattern always gives the same result, ignoring new emails with that particular pattern. Solr is working correctly and the correct search results comes immediately (whatever the searched word) after a "doveadm fts rescan" # doveconf | grep fts mail_plugins = " quota stats fts fts_solr" fts = solr fts_autoindex = yes fts_solr = url=http://localhost:8983/solr/dovecot/ [POP] mail_plugins = " quota stats fts fts_solr sieve virtual" [IMAP] mail_plugins = " quota stats fts fts_solr imap_quota virtual imap_stats"

4 14

Search problem
by Federico Bartolucci 28 May '18

28 May '18

Hello, when doing a simple search through the lucene indexes in some mailboxes (with actually many subfolders) the search terminates after a few seconds with no result and the dovecot log shows this error: Fatal: master: service(imap): child 15433 killed with signal 6 (core not dumped) Any clue about the reasons? the lucene indexes have been already rebuilt and look OK. Regards -federico

3 3

Re: Best mail encryption solution for per-user
by Aki Tuomi 27 May '18

27 May '18

> On 26 May 2018 at 10:36 mail(a)sjemm.net wrote: > > > May 23, 2018 10:10 AM, mail(a)sjemm.net wrote: > > May 23, 2018 9:46 AM, "Aki Tuomi" <aki.tuomi(a)dovecot.fi> wrote: > > > >> On 23.05.2018 10:15, mail(a)sjemm.net wrote: > >> > >>> May 23, 2018 8:31 AM, "Aki Tuomi" <aki.tuomi(a)dovecot.fi> wrote: > >> > >> On 23.05.2018 09:13, mail(a)sjemm.net wrote: > >>> May 20, 2018 8:01 PM, mail(a)sjemm.net wrote: > >>> May 20, 2018 2:47 PM, "Aki Tuomi" <aki.tuomi(a)dovecot.fi> wrote: > >>> On 19 May 2018 at 16:40 mail(a)sjemm.net wrote: > >>> > >>> May 18, 2018 10:01 PM, "Aki Tuomi" <aki.tuomi(a)dovecot.fi> wrote: > >>> On 18 May 2018 at 21:44 mail(a)sjemm.net wrote: > >>> > >>> May 18, 2018 4:43 PM, "Aki Tuomi" <aki.tuomi(a)dovecot.fi> wrote: > >>> On 18 May 2018 at 17:38 mail(a)sjemm.net wrote: > >>> > >>> May 18, 2018 4:05 PM, "Aki Tuomi" <aki.tuomi(a)dovecot.fi> wrote: > >>> On 18 May 2018 at 16:43 mail(a)sjemm.net wrote: > >>> > >>> Hi Tai74 and Aki, > >>> I followed your conversation with interest on how to setup per user encryption in dovecot. > >>> I have setup my dovecot with the following in a conf file: > >>> > >>> ============== > >>> > >>> mail_attribute_dict = file:%h/Maildir/dovecot-attributes > >>> mail_plugins = $mail_plugins mail_crypt > >>> plugin { > >>> > >>> mail_crypt_curve = secp521r1 > >>> > >>> mail_crypt_save_version = 2 > >>> > >>> } > >>> > >>> ============== > >>> > >>> This works nice, all emails are being encrypted and every user/folder has keys. > >>> But as I understood from your conversation these keys are not protected. And I want them to be > >>> protected by the users password used by imap. > >>> > >>> Those passwords are stored in a mysql DB file. ( I used a guide from workaround [dot] org to set up > >>> the DB and postfix/dovecot) > >>> > >>> but how would i set it so, that the users password from the DB is used to encrypt the keys? > >>> > >>> should i use mail_crypt_private_password = ? > >>> how do i point it to the mysql db then? > >>> im unsure about this > >>> > >>> Do you have any hints on this? > >>> > >>> Kind regards, > >>> Zjemm > >>> > >>> The passwords in your MySQL database are, hopefully, not in plaintext. If you want to secure your > >>> user's keys using user's login password, you must have a TOOL that manages this. > >>> > >>> You can use mail_crypt_private_password = %w in (mysql) passdb fields to provide the user's login > >>> password as private password. You might want to run it thru some hash, so %{sha1:password} might be > >>> a good option. > >>> > >>> You can change the key password using 'doveadm mailbox cryptokey', this needs to be done every time > >>> user changes his password. > >>> > >>> Also note that if you go down this road, and the user forgets his password, you will not be able to > >>> recover the emails without backup copy of the private key. > >>> > >>> Aki > >>> > >>> Hi Aki > >>> > >>> I used the following command: > >>> dovecot pw -s SHA256-CRYPT > >>> > >>> the output on the chosen password looks like: {SHA256-CRYPT}$5$Rokc06a7In4SF3bO$OQpGQWqg........ > >>> > >>> This output is used to store in the password fields in the database. So no plain text passwords no > >>> :) > >>> > >>> You can use mail_crypt_private_password = %w in (mysql) passdb fields to provide the user's login > >>> password as private password. > >>> > >>> can you explain this a bit more for me? > >>> > >>> for now i have in the 10-auth.conf file the following: > >>> ============== > >>> passdb { > >>> driver = sql > >>> > >>> # Path for SQL configuration file, see example-config/dovecot-sql.conf.ext > >>> args = /etc/dovecot/dovecot-sql.conf.ext > >>> } > >>> > >>> and: > >>> > >>> userdb { > >>> driver = static > >>> args = uid=vmail gid=vmail home=/var/vmail/%d/%n > >>> } > >>> ============== > >>> > >>> then i have in dovecot-sql.conf.ext > >>> ============== > >>> driver = mysql > >>> connect = host=x.x.x.x dbname=mailserver user=mailuser password=mailpasswordexample > >>> default_pass_scheme = SHA256-CRYPT > >>> password_query = SELECT email as user, password FROM virtual_users WHERE email='%u'; > >>> ============== > >>> Where do i need to set : mail_crypt_private_password = %w ? > >>> > >>> password as private password. You might want to run it thru some hash, so %{sha1:password} might be > >>> a good option. > >>> > >>> the passwords are allready hashed in the DB using: dovecot pw -s SHA256-CRYPT to genereate the has. > >>> so this step isnt nesesary anymore am i right? > >>> > >>> Thank you for your quick response, very helpfull > >>> > >>> Zjemm > >>> > >>> You misunderstood a bit. The idea is to use the *plaintext* password as the password for the > >>> private key. Otherwise anyone could just decrypt it by looking at your database where the hashed > >>> password is.. > >>> > >>> So: > >>> > >>> password_query = SELECT email as user, password, '%w' AS userdb_mail_crypt_private_password FROM > >>> virtual_users WHERE email='%u' > >>> > >>> Aki > >>> > >>> Hi Aki, > >>> > >>> Thank you very much for your help, i realy appreciate that. > >>> > >>> Ok so if i understand it correctly i'll have to use: > >>> > >>> password_query = SELECT email as user, password, '%w' AS userdb_mail_crypt_private_password FROM > >>> virtual_users WHERE email='%u' > >>> > >>> in my dovecot-sql.conf.ext file > >>> > >>> This query selects the user, the password, and %w > >>> > >>> if i run a little query myself: > >>> MariaDB [mailserver]> SELECT email as user, password, '%w' AS userdb_mail_crypt_private_password > >>> FROM virtual_users; > >>> +------------------+----------------------------------+------------------------------------+ > >>> | user | password | userdb_mail_crypt_private_password | > >>> +------------------+----------------------------------+------------------------------------+ > >>> | john(a)example.org | {SHA256-CRYPT}$5$M/GWzmtjsLroRWI | %w | > >>> +------------------+----------------------------------+------------------------------------+ > >>> > >>> %w is a dovecot variable, and stands for the plaintext password, but the password is not stored as > >>> plaintext in the DB, %w get filled with the actual plaintext password by dovecot upon the user that > >>> is typing in the password when authenticating. > >>> > >>> is this correct? > >>> > >>> yes. > >>> > >>> so then i have the username the hashed password en the plaintext password as a result of the query. > >>> > >>> yes > >>> > >>> now userdb_mail_crypt_private_password = the plaintext password > >>> do i need to reference it somewhere? or is userdb_mail_crypt_private_password autmatically used by > >>> the dovecot mail_crypt plugin to encrypt the keys? or should it be mail_crypt_private_password? > >>> > >>> It gets injected into the mail process as 'mail_crypt_private_password', as if it was set in plugin > >>> {} section. > >>> > >>> if i have this setup working i'm going to write a blog post on this topic to share this knowledge > >>> > >>> Thanks again and have a great weekend. > >>> > >>> Zjemm > >>> > >>> Aki > >>> > >>> Hi Aki, > >>> > >>> Cool i'm testing it right now. > >>> I have set up a new mailserver (life is great with lxc containers :) ) > >>> > >>> postfix and dovecot are working like normal > >>> > >>> next i enable mail_crypt > >>> > >>> i did create a file: /etc/dovecot/conf.d/10-mailcrypt.conf > >>> ========================== > >>> mail_attribute_dict = file:%h/Maildir/dovecot-attributes > >>> > >>> mail_plugins = $mail_plugins mail_crypt > >>> > >>> plugin { > >>> mail_crypt_curve = secp521r1 > >>> mail_crypt_save_version = 2 > >>> } > >>> ========================== > >>> > >>> and then i changed the file: /etc/dovecot/dovecot-sql.conf.ext > >>> > >>> so the query is now the new query: > >>> password_query = SELECT email as user, password, '%w' AS userdb_mail_crypt_private_password FROM > >>> virtual_users WHERE email='%u'; > >>> > >>> then i restarted dovecot and postfix and send a test email to the one and only testuser that is in > >>> there. > >>> > >>> when i open the mailbox with the tool mutt, i can see the new email, and when openening the email > >>> the mutt client drops the connection. > >>> > >>> in the log i can see: > >>> > >>> May 19 13:34:48 mailserver1.example.local dovecot[600]: imap-login: Login: user=<john(a)example.org>, > >>> method=PLAIN, rip=::1, lip=::1, mpid=713, TLS, session=<E3PnIY9sNM4AAAAAAAAAAAAAAAAAAAAB> > >>> May 19 13:34:49 mailserver1.example.local dovecot[600]: imap(john(a)example.org): Error: read() > >>> failed: > >>> read(/var/vmail/example.org/john/Maildir/cur/1526736378.M161472P641.mailser…, > >>> =571:2,) failed: Private key not available: Cannot decrypt key > >>> bfc5bb25b1bf64290eea6dc14b516c6a0a25b64551b6e4f0f8677ba7274887cb: error:03070068:bignum > >>> routines:BN_mpi2bn:encoding error (FETCH BODY[] for mailbox INBOX UID 8) > >>> > >>> i think i missed a step, but witch one? > >>> > >>> the userpassword hasnt been changed (that would be the next step in the testing process) > >>> > >>> should i've use doveadm first to encrypt the key with that userpassword? i thought it would do that > >>> on the fly, because the initial keys where only just created when enabling the mail_crypt plugin > >>> > >>> please let me know your thougts > >>> Zjemm > >>> I noticed you replied directly to me, and not to the list, too... fixed that for you. > >>> > >>> mail_crypt_private_password is used when key is created, but if you have created it before using > >>> password, you'll need to encrypt it before turning the setting on. > >>> > >>> Aki > >>> Hi, Ok i'm sorry about that, thank you for fixing that. i'm a bit new to mailing lists :) > >>> > >>> are you a dovecot devoloper? or a enthusiastic user? > >>> > >>> anyway, i managed to get it working now with all your help :) > >>> > >>> to start fresh i did a: > >>> rm -rf /var/vmail/example.org > >>> > >>> so all email is gone, and i assume all dovecot keys are gone that way. > >>> > >>> Then i tried to set a password first: > >>> > >>> root@mailserver1:/var/vmail# doveadm mailbox cryptokey password -u john(a)example.org -n summersun > >>> result: Changed password for 0 key(s) > >>> > >>> (summersun = the password for this user) > >>> > >>> but then it says there are 0 keys, so then i send the test user an email and try to open the > >>> mailbox, i'll get: > >>> > >>> imap(john(a)example.org): Error: read() failed: > >>> read(/var/vmail/example.org/john/Maildir/cur/1526827992.M149712P883.mailser…, > >>> =561:2,) failed: Private key not available: Cannot decrypt key > >>> 71849013a70b0c631c06112077e7c2fe39b0b2737b4933b219793841209d4e7f: error:03070068:bignum > >>> routines:BN_mpi2bn:encoding error > >>> > >>> but hey, now the key's are created, so i tried to set the password again: > >>> > >>> root@mailserver1:/var/vmail# doveadm mailbox cryptokey password -u john(a)example.org -n summersun > >>> result: dcrypt_key_load_private(787701bd677dd69a26842547a3926cbaa625b0b5a91751f06678c3e9708343d9) > >>> failed: password missing > >>> ========= > >>> > >>> Lets start over again, i did a new: > >>> rm -rf /var/vmail/example.org > >>> > >>> i disabled the mail_crypt_private_password in the sql query and send an email to the test user. > >>> now again new keys are generated. > >>> > >>> then i did set the password via doveadm: > >>> > >>> root@mailserver1:/var/vmail# doveadm mailbox cryptokey password -u john(a)example.org -n summersun > >>> result: Changed password for 1 key(s) > >>> > >>> i enabled the mail_crypt_private_password again in the sql query part and now it works :) > >>> > >>> YESSS!!! > >>> > >>> if i now change the password for the user, i cannot read the email anymore. that is what should > >>> happen. > >>> so now i changed the password for this user also with doveadm: > >>> - doveadm mailbox cryptokey password -u john(a)example.org -n qwerty -o summersun > >>> > >>> and now i'm able to read the emails again. so it all works now as expected. > >>> > >>> i have now only one thing remaining. > >>> > >>> when i want to add a new user, i have to somehow: > >>> - create the new user in the mysql DB > >>> - start with dovecot not using mail_crypt_private_password (so disabled) > >>> - send an initial email to let the users mailbox be created and generate the keys > >>> - set the users password with doveadm > >>> - restart dovecot again with mail_crypt_private_password (so enabled) > >>> > >>> but this would be disruptive to existing users, and i would have to script the whole thing as a > >>> "add-new-user" script to make it usable i guess. > >>> > >>> do you know of a more easy way of acomplishing this? > >>> could i use doveadm for all steps, and get around the mail_crypt_private_password disable part? > >>> > >>> or could i add a column in the mysql db called userdb_mail_crypt_private_password and fill that > >>> column with %w for users that allready exist, and empty for new users. > >>> when being empty, it might not set the mail_crypt_private_password for new users > >>> > >>> or is this the wrong way of thinking? > >>> > >>> let me know your thoughts on this. > >>> > >>> And last but not least, i really want to thank you for all your help. It is a really nice > >>> experience. > >>> Bless you! > >>> > >>> Zjemm > >>> Hi Aki, > >>> > >>> You did fix the posting on the mail archive, i can see our conversation on there, all but the last > >>> email i send to you. > >>> Maybe you did not received the last email? > >>> > >>> would you be willing to take a look at my last question in the email See below: > >>> Thank you very much. > >>> > >>> ================================ > >>> i have now only one thing remaining. > >>> > >>> when i want to add a new user, i have to somehow: > >>> - create the new user in the mysql DB > >>> - start with dovecot not using mail_crypt_private_password (so disabled) > >>> - send an initial email to let the users mailbox be created and generate the keys > >>> - set the users password with doveadm > >>> - restart dovecot again with mail_crypt_private_password (so enabled) > >>> > >>> but this would be disruptive to existing users, and i would have to script the whole thing as a > >>> "add-new-user" script to make it usable i guess. > >>> > >>> do you know of a more easy way of acomplishing this? > >>> could i use doveadm for all steps, and get around the mail_crypt_private_password disable part? > >>> > >>> or could i add a column in the mysql db called userdb_mail_crypt_private_password and fill that > >>> column with %w for users that allready exist, and empty for new users. > >>> when being empty, it might not set the mail_crypt_private_password for new users > >>> > >>> or is this the wrong way of thinking? > >>> > >>> let me know your thoughts on this. > >>> > >>> And last but not least, i really want to thank you for all your help. It is a really nice > >>> experience. > >>> Bless you! > >>> > >>> Zjemm > >> > >> If you have mail_crypt_private_password set *when* keys are generated, > >> dovecot should use that password to encrypt the user key. > >> > >> Aki > >>> Hi Aki, > >>> > >>> well, if there is a new email user setup in the mysql DB, and no email has been send to that new > >>> user. at that point there are no keys. > >>> > >>> So trying to set a password on those key's wont work. see: > >>> root@mailserver1:/var/vmail/example.org# doveadm mailbox cryptokey password -u john2(a)example.org -n > >>> qwerty > >>> result: Changed password for 0 key(s) > >>> > >>> the keys need to be generated first. And that only happens when sending a mail to that new user. > >>> Also, at the point of creating the keys, the mail_crypt_private_password should be disabled > >>> otherwise the keys are generated and also encrypted with no user password, and then im unable to > >>> set a new pasword for that key > >>> > >>> How can i set the password before the keys are generated? > >>> or can i manually generate key's and then set the password? > >>> > >>> so at this point i have to do the following: > >> > >> You can use doveadm mailbox cryptokey generate -u user -U > >> > >> to generate a user key. > >> > >> Aki > >> > >>> - create the new user in the mysql DB > >>> - start with dovecot not using mail_crypt_private_password (so disabled) > >>> - send an initial email to let the users mailbox be created and generate the keys > >>> - set the users password with doveadm > >>> - restart dovecot again with mail_crypt_private_password (so enabled) > >>> can i somehow enable the mail_crypt_private_password per user? > >>> because this mysql query always returns: %w > >>> and thus allways sets: userdb_mail_crypt_private_password > >>> SELECT email as user, password, '%w' AS userdb_mail_crypt_private_password FROM virtual_users; > > > > Hi Aki, > > > > You are correct > > > > doveadm mailbox cryptokey generate -u user -U generates the keys, but i have to first remove: > > '%w' AS userdb_mail_crypt_private_password > > from dovecot configuration and restart dovecot. > > > > if i don't do that, the keys are generated, but also somehow encrypted using: no > > password/empty/something else (i don't know) > > > > here you can see that happening: > > > > root@mailserver1:/var/vmail/example.org# doveadm mailbox cryptokey generate -u john2(a)example.org -U > > Folder Public ID > > ✓ <userkey> 53004acf9886f887ca081c83d7392a5aa3fac4b5a20ce013db91a341fb4644c4 > > root@mailserver1:/var/vmail/example.org# doveadm mailbox cryptokey password -u john2(a)example.org -n > > qwerty > > result: dcrypt_key_load_private(53004acf9886f887ca081c83d7392a5aa3fac4b5a20ce013db91a341fb4644c4) > > failed: password missing > > > > it expects an old password wich is never set in my opinion. > > > > so the last part of this setup would be to figure out a way to disable '%w' AS > > userdb_mail_crypt_private_password for new users without manually removing that part from the query > > and restarting dovecot. As that would mean connection interruption while adding new users > > > > if we could add new users to the DB and somehow not give '%w' AS userdb_mail_crypt_private_password > > for that new user in the query, we can add the password afterward, and then enable '%w' AS > > userdb_mail_crypt_private_password in the query for this user > > > > could we add a column in the user db lets say called: encrypted (yes/no) > > > > and then change the existing query: SELECT email as user, password, '%w' AS > > userdb_mail_crypt_private_password FROM virtual_users; > > > > to firrt check if encryption is set to 'yes', if so retrun: > > SELECT email as user, password, '%w' AS userdb_mail_crypt_private_password FROM virtual_users; > > > > if not return: > > SELECT email as user, password FROM virtual_users; > > > > but then in one mysql query so dovecot can work with it > > > > ? > > > Hi Aki, > > would you be willing to respond to my last question i had send to you last week? > its this one: > ================================== > > doveadm mailbox cryptokey generate -u user -U generates the keys, but i have to first remove: > > '%w' AS userdb_mail_crypt_private_password > > from dovecot configuration and restart dovecot. > > > > if i don't do that, the keys are generated, but also somehow encrypted using: no > > password/empty/something else (i don't know) > > > > here you can see that happening: > > > > root@mailserver1:/var/vmail/example.org# doveadm mailbox cryptokey generate -u john2(a)example.org -U > > Folder Public ID > > ✓ <userkey> 53004acf9886f887ca081c83d7392a5aa3fac4b5a20ce013db91a341fb4644c4 > > root@mailserver1:/var/vmail/example.org# doveadm mailbox cryptokey password -u john2(a)example.org -n > > qwerty > > result: dcrypt_key_load_private(53004acf9886f887ca081c83d7392a5aa3fac4b5a20ce013db91a341fb4644c4) > > failed: password missing > > > > it expects an old password wich is never set in my opinion. > > could this be a bug? or am i doing it wrong? if needed i could send in a bug report? > > or might we need to enable the userdb_mail_crypt_private_password "per user" ? > > > > > so the last part of this setup would be to figure out a way to disable '%w' AS > > userdb_mail_crypt_private_password for new users without manually removing that part from the query > > and restarting dovecot. As that would mean connection interruption while adding new users > > > > if we could add new users to the DB and somehow not give '%w' AS userdb_mail_crypt_private_password > > for that new user in the query, we can add the password afterward, and then enable '%w' AS > > userdb_mail_crypt_private_password in the query for this user > > > > could we add a column in the user db lets say called: encrypted (yes/no) > > > > and then change the existing query: SELECT email as user, password, '%w' AS > > userdb_mail_crypt_private_password FROM virtual_users; > > > > to firrt check if encryption is set to 'yes', if so retrun: > > SELECT email as user, password, '%w' AS userdb_mail_crypt_private_password FROM virtual_users; > > > > if not return: > > SELECT email as user, password FROM virtual_users; > > > > but then in one mysql query so dovecot can work with it > > Please let me know your thougts, after this last thing im done :) > also let me know if i can support this project in some way, im willing to contribute > > Zjemm You can select it as userdb_mail_crypt_save_version=0 to disable encryption (it won't disable decryption). You can use value '2' for enabling encryption. DO NOT USE 1. Also I tried the SQL based thing, and if you had EMPTY mail_crypt_private_password, try these to change the password. If the one that works is the second one, let me know =) doveadm mailbox cryptokey password -u testuser -nnewpass -o "" doveadm mailbox cryptokey password -u testuser -nnewpass -o "yes" Aki

1 0

lda / postfix / dovecot -- bounced messages not working
by Scott Ruckh 25 May '18

25 May '18

I saw another thread about this topic, but I did not understand the solution. . . I recently discovered my bounced messages were not getting delivered. Obviously since I was not getting any messages, I thought everything was fine. Anyway, my maillog has entries similar to below for bounced messages: Mar 29 10:48:09 firewall postfix/pipe[9089]: 19565807: to=<myuser(a)my.domain>, relay=dovecot, delay=0.11, delays=0.02/0.01/0/0.08, dsn=5.3.0, status=bounced (command line usage error. Command output: lda: Fatal: Invalid -f parameter: Missing domain ) In the previous thread discussing this issue it mentioned that this was a dovecot error and possibly due to a dovecot 2.3.0 upgrade. I am running dovecot-2.3.0-1.1 on a CentOS 7 server. The solution from the other thread simply stated that the original poster is instead using lmtp instead of lda, or at least that it was I got from the thread. If using lmtp instead of lda is the correct solution, could I get an example of what configuration changes need to be made to make that happen? Otherwise, has anyone else seen this error and know the solution to make it work. My current dovecot configuration for postfix (master.cf) is using the de-facto standard from many web docs: dovecot unix - n n - - pipe flags=DRhu user=vmail:vmail argv=/usr/libexec/dovecot/deliver -f ${sender} -d ${recipient} This is the same configuration that was originally setup and has worked for years; until the bounced message problem was recently discovered. If anyone has seen this error and knows the solution, I would appreciate the help. Thank You. Scott

2 1

last login tracking error
by David Mehler 25 May '18

25 May '18

Hello, I'm running dovecot 2.2 and trying to do last login tracking. I am using a MySQL database. When a user logs in I get this in the log: 2018-04-07 16:55:14 imap(user(a)example.com)<54415><BmevY0hpMN5/AAAB>: Error: last_login_dict: Failed to write value for user user(a)example.com: dict-server returned failure: sql dict: commit failed: Field 'name' doesn't have a default value (reply took 0.018 secs (0.000 in dict wait, 0.009 in other ioloops, 0.001 in locks, async-id reply 0.000 secs ago, started on dict-server 0.006 secs ago, took 0.006 secs)) Here's an excerpt from my dovecot-dict-sql.conf.ext file: map { pattern = shared/last-login/$user table = accounts value_field = last_login value_type = uint fields { username = $user } } The username does have a value. Can anyone see what I've got wrong? Thanks. Dave. doveconf -n 2018-04-07 16:55:14 imap(user(a)example.com)<54415><BmevY0hpMN5/AAAB>: Error: last_login_dict: Failed to write value for user user(a)example.com: dict-server returned failure: sql dict: commit failed: Field 'name' doesn't have a default value (reply took 0.018 secs (0.000 in dict wait, 0.009 in other ioloops, 0.001 in locks, async-id reply 0.000 secs ago, started on dict-server 0.006 secs ago, took 0.006 secs)) # 2.3.1 (8e2f634): /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 0.5.1 (d9bc6dfe) # OS: FreeBSD 11.1-RELEASE-p4 amd64 # Hostname: localhost auth_cache_size = 24 M auth_cache_ttl = 18 hours auth_default_realm = example.com auth_mechanisms = plain login auth_realms = example.com nickandwill.com dict { acl = mysql:/usr/local/etc/dovecot/dovecot-dict-sql.conf.ext lastlogin = mysql:/usr/local/etc/dovecot/dovecot-dict-sql.conf.ext quota = mysql:/usr/local/etc/dovecot/dovecot-dict-sql.conf.ext } first_valid_gid = 999 first_valid_uid = 999 hostname = mail.example.com imap_idle_notify_interval = 10 mins last_valid_gid = 999 last_valid_uid = 999 lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes lda_original_recipient_header = X-Original-To listen = 127.0.0.1 66.228.47.34 log_path = /var/log/dovecot/dovecot.log log_timestamp = "%Y-%m-%d %H:%M:%S " mail_access_groups = vmail mail_gid = vmail mail_home = /home/vmail/mailboxes/%d/%n mail_location = maildir:~/mail:LAYOUT=fs mail_plugins = acl mail_log notify quota trash virtual welcome zlib mail_privileged_group = vmail mail_server_admin = mailto:postmaster@example.com mail_uid = vmail mailbox_idle_check_interval = 59 secs 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 spamtest spamtestplus virustest editheader imapflags notify imapsieve vnd.dovecot.imapsieve namespace { location = maildir:/home/vmail/public/:CONTROL=~/mail/public:INDEX=~/mail/public mailbox TestFolder { auto = subscribe comment = Public Folder for message sharing } prefix = Public/ separator = / subscriptions = yes type = public } namespace { hidden = no location = maildir:/home/vmail/shared/office/.Maildir:CONTROL=~/.Maildir/control/office:INDEX=~/.Maildir/index/office prefix = office/ separator = / } namespace inbox { inbox = yes location = mailbox Archives { auto = subscribe special_use = \Archive } mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Sent { auto = subscribe special_use = \Sent } mailbox Spam { auto = subscribe autoexpunge = 30 days special_use = \Junk } mailbox Trash { auto = subscribe autoexpunge = 30 days special_use = \Trash } mailbox virtual/All { comment = All my messages special_use = \All } prefix = separator = / type = private } namespace virtual { location = virtual:/usr/local/etc/dovecot/virtual:INDEX=~/virtual:CONTROL=~/virtual prefix = virtual/ separator = / } passdb { args = /usr/local/etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { acl = vfile:/usr/local/etc/dovecot/global-acls:cache_secs=300 acl_anyone = allow acl_globals_only = yes acl_shared_dict = proxy::acl 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:/home/vmail/sieve/global/learn-spam.sieve imapsieve_mailbox1_causes = COPY imapsieve_mailbox1_name = Spam imapsieve_mailbox2_before = file:/home/vmail/sieve/global/learn-ham.sieve imapsieve_mailbox2_causes = COPY imapsieve_mailbox2_from = Spam imapsieve_mailbox2_name = * last_login_dict = proxy::lastlogin last_login_key = last-login/%n mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename mail_log_fields = uid box msgid size quota = dict:User quota::proxy::quota quota_exceeded_message = Storage quota for this account has been exceeded, please try again later. quota_grace = 10%% quota_status_nouser = DUNNO quota_status_overquota = 552 5.2.2 Mailbox is full quota_status_success = DUNNO quota_vsizes = true quota_warning = storage=100%% quota-exceeded 100 %u quota_warning2 = storage=95%% quota-warning 95 %u quota_warning3 = storage=90%% quota-warning 90 %u quota_warning4 = storage=85%% quota-warning 85 %u quota_warning5 = storage=75%% quota-warning 75 %u sieve = ~/.dovecot.sieve sieve_before = /home/vmail/sieve/before.d sieve_default = /home/vmail/sieve/default.sieve sieve_dir = ~/sieve sieve_extensions = +notify +imapflags +spamtest +spamtestplus +virustest +editheader sieve_global_dir = /home/vmail/sieve sieve_global_extensions = +vnd.dovecot.pipe +vnd.dovecot.execute +vnd.dovecot.environment sieve_max_redirects = 30 sieve_max_script_size = 1M sieve_pipe_bin_dir = /home/vmail/sieve sieve_plugins = sieve_imapsieve sieve_extprograms sieve_spamtest_max_header = X-Spamd-Result: default: [[:alnum:]]+ \[-?[[:digit:]]+\.[[:digit:]]+ / (-?[[:digit:]]+\.[[:digit:]]+)\] sieve_spamtest_status_header = X-Spamd-Result: default: [[:alnum:]]+ \[(-?[[:digit:]]+\.[[:digit:]]+) / -?[[:digit:]]+\.[[:digit:]]+\] sieve_spamtest_status_type = score sieve_user_log = /home/vmail/sieve/sieve_error.log sieve_virustest_status_header = X-Virus-Scan: Found to be (.+)\. sieve_virustest_status_type = text sieve_virustest_text_value1 = clean sieve_virustest_text_value5 = infected trash = /usr/local/etc/dovecot/trash.conf welcome_script = welcome %u postmaster@%d welcome_wait = yes } postmaster_address = postmaster(a)example.com protocols = imap lmtp sieve sendmail_path = /usr/local/sbin/sendmail service auth-worker { user = vmail } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } unix_listener auth-userdb { group = vmail mode = 0666 user = vmail } } service dict { unix_listener dict { group = vmail mode = 0660 user = vmail } user = root } service imap-login { inet_listener imap { address = 127.0.0.1 } inet_listener imaps { address = 66.228.47.34 port = 993 ssl = yes } } service imap-postlogin { executable = script-login /usr/local/etc/dovecot/trackauth.sh user = vmail } service imap { executable = imap } service lmtp { executable = lmtp unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0666 user = postfix } } service managesieve-login { inet_listener sieve { address = 127.0.0.1 port = 4190 } } service quota-status { client_limit = 1 executable = quota-status -p postfix unix_listener /var/spool/postfix/private/dovecot-quota { group = postfix mode = 0660 user = postfix } } service quota-warning { executable = script /usr/local/etc/dovecot/quota-warning.sh unix_listener quota-warning { group = vmail mode = 0660 user = vmail } user = vmail } service welcome { executable = script /usr/local/etc/dovecot/welcome.sh unix_listener welcome { user = vmail } user = vmail } ssl = required ssl_cert = </usr/local/etc/ssl/acme/example.com/fullchain.pem ssl_cipher_list = ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA256 ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it ssl_min_protocol = TLSv1.2 ssl_prefer_server_ciphers = yes userdb { args = /usr/local/etc/dovecot/dovecot-sql.conf.ext driver = sql } protocol lmtp { info_log_path = /var/log/dovecot/dovecot-lmtp.log log_path = /var/log/dovecot/dovecot-lmtp-errors.log mail_plugins = acl mail_log notify quota trash virtual welcome zlib sieve } protocol lda { mail_plugins = acl mail_log notify quota trash virtual welcome zlib sieve } protocol imap { mail_max_userip_connections = 20 mail_plugins = acl mail_log notify quota trash virtual welcome zlib imap_acl imap_quota imap_sieve imap_zlib last_login fts fts_lucene } protocol sieve { info_log_path = /var/log/dovecot/dovecot-sieve.log log_path = /var/log/dovecot/dovecot-sieve-errors.log }

2 1

Bug: subscriptions file
by Rupert Gallagher 24 May '18

24 May '18

Dovecot does not clear the subscription file from non-existent folders.

5 10

question on setting ulimit on debian
by Sophie Loewenthal 24 May '18

24 May '18

Hi, I’ve been trying to increase the number of open files for the dovecot user on Debian 9 and have so far, failed! I’ve tried this: # cat /etc/security/limits.d/limits_dovecot.conf dovecot soft nofile 2048 dovecot hard nofile 8192 # cat /etc/systemd/system/dovecot.service.d/service.conf LimitNOFILE=8192 But to no avail: # prlimit -p 27208|grep -i nofile NOFILE max number of open files 1024 4096 files Lost me :( Any ideas? Thanks,Sophie.

2 2

Dovecot send duplicated certificates when using ssl_alt_cert
by Jean-Daniel Dupas 24 May '18

24 May '18

Hello, I'm running dovecot 2.3.1 (c5a5c0c82) and trying to experiment with using both RSA and ECDSA certificates. My configuration is as follow: ssl_alt_cert = </path/to/my.rsa.key ssl_alt_key = </path/to/my.rsa.key ssl_cert = </path/to/my.ecdsa.pem ssl_key = </path/to/my.ecdsa.key Both certificates are let's encrypt certificate, so both are using the same intermediate CA. The certificate chain are: for rsa: - my certificate - Let's Encrypt Authority X3 - DST Root CA X3 for ecdsa: - my certificate - Let's Encrypt Authority X3 - DST Root CA X3 My problem is that when connecting, dovecot includes 2 copies of Let's Encrypt Authority X3 in the certificate chain. I think this is a bug. When building the chain, dovecot should ignore duplicated certificates and when opening the connection, it should only send intermediates related to the used certificate (either RSA or ECDSA). (and as a side note, when using dovecot -n, dovecot hides the ssl_key (ssl_key = # hidden, use -P to show it) but not the ssl_alt_key. This is probably a bug too). --------------- openssl s_client -showcerts -host imap.example.com -port 993 -servername imap.example.com CONNECTED(00000005) depth=1 C = US, O = Let's Encrypt, CN = Let's Encrypt Authority X3 verify error:num=20:unable to get local issuer certificate verify return:0 --- Certificate chain 0 s:/CN=imap.example.com i:/C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3 -----BEGIN CERTIFICATE----- MIIHPDCCBiSgAwIBAgISA2e3bP2o1mpdOr9kTDm/R/zuMA0GCSqGSIb3DQEBCwUA … -----END CERTIFICATE----- 1 s:/C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3 i:/O=Digital Signature Trust Co./CN=DST Root CA X3 -----BEGIN CERTIFICATE----- MIIEkjCCA3qgAwIBAgIQCgFBQgAAAVOFc2oLheynCDANBgkqhkiG9w0BAQsFADA/ MSQwIgYDVQQKExtEaWdpdGFsIFNpZ25hdHVyZSBUcnVzdCBDby4xFzAVBgNVBAMT … -----END CERTIFICATE----- 2 s:/C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3 i:/O=Digital Signature Trust Co./CN=DST Root CA X3 -----BEGIN CERTIFICATE----- MIIEkjCCA3qgAwIBAgIQCgFBQgAAAVOFc2oLheynCDANBgkqhkiG9w0BAQsFADA/ MSQwIgYDVQQKExtEaWdpdGFsIFNpZ25hdHVyZSBUcnVzdCBDby4xFzAVBgNVBAMT … -----END CERTIFICATE----- --- Server certificate subject=/CN=imap.example.com issuer=/C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3 --- No client certificate CA names sent --- SSL handshake has read 5140 bytes and written 468 bytes --- New, TLSv1/SSLv3, Cipher is ECDHE-RSA-AES256-GCM-SHA384 Server public key is 4096 bit Secure Renegotiation IS supported Compression: NONE Expansion: NONE No ALPN negotiated SSL-Session: Protocol : TLSv1.2 Cipher : ECDHE-RSA-AES256-GCM-SHA384 Session-ID: 591240C021A02B399CCB010F37AF7AD83227DC1770C606F73B3EEA3514AF07FB Session-ID-ctx: Master-Key: 7D5A5BFC1B4B8EECF4F41DC084265AF6D32B82130F381B8DDF685B589D54D9BDEBFC20F1DD80E150CD56850C0D062E9E TLS session ticket lifetime hint: 300 (seconds) TLS session ticket: 0000 - 3a 72 98 05 72 af 3d ed-26 a9 e7 2b 68 6b 0a 25 :r..r.=.&..+hk.% … Start Time: 1526482021 Timeout : 300 (sec) Verify return code: 0 (ok) ---

3 3

Re: lazy_expuge + mdbox
by Matt Bryant 24 May '18

24 May '18

To a degree I agree .. given mdbox doesnt delete until purge .. but then would be nice if purge took a dovecot search rather than just ditch everything with refcount=0 ... in that way could say purge everything thats been marked as delete according to a specified criteria. rgds Matt completly unrelated moved mailserver back home and listed on cyren so atm getting bounced by dovecot.fi .. have requested de-listing > Aki Tuomi <mailto:aki.tuomi@dovecot.fi> > 24 May 2018 at 3:35 pm > > I am not sure if lazy expunge makes much sense with mdbox, at least if > you use the same mdbox storage with it. It might make sense with > separate mdbox/sdbox/something for .EXPUNGED. > > Aki > Matt Bryant <mailto:matt@the-bryants.net> > 24 May 2018 at 11:53 am > So moving on from earlier issue now looking at converting mail inbox to > mdbox and keeping lazy_expunge as mdbox also .. but again seeing some > wierdness so questions .... > > 1) When i purge trash folder I seem to get 2 copies of the message in > .EXPUNGED/Trash folder .. however if I set > lazy_expunge_only_last_instance = yes then dont seem to get ANY copy .. > just nothing. > > 2) If I go into Trash and delete a message ... then it does not get > moved .. I assume that a delete in Trash is not actually an expunge on > TB and hence does get caught by the plugin. > > 3) Since mdbox doesnt delte anything anyway until purged would it be > better not to use lazy-expunge but just have a job that moves any > messages in mdbox_deleted: storage to the hidden .EXPUNGED namespace .. > does doveadm move work with mdbox_deleted ??? > > any help appreciated > > rgds > > Matt

2 1

lazy_expuge + mdbox
by Matt Bryant 24 May '18

24 May '18

So moving on from earlier issue now looking at converting mail inbox to mdbox and keeping lazy_expunge as mdbox also .. but again seeing some wierdness so questions .... 1) When i purge trash folder I seem to get 2 copies of the message in .EXPUNGED/Trash folder .. however if I set lazy_expunge_only_last_instance = yes then dont seem to get ANY copy .. just nothing. 2) If I go into Trash and delete a message ... then it does not get moved .. I assume that a delete in Trash is not actually an expunge on TB and hence does get caught by the plugin. 3) Since mdbox doesnt delte anything anyway until purged would it be better not to use lazy-expunge but just have a job that moves any messages in mdbox_deleted: storage to the hidden .EXPUNGED namespace .. does doveadm move work with mdbox_deleted ??? any help appreciated rgds Matt

1 0

Released Pigeonhole v0.4.24 for Dovecot v2.2.36.
by Stephan Bosch 24 May '18

24 May '18

Hello Dovecot users, Here is the Pigeonhole release that goes with the new Dovecot v2.2.36 release. Apart from the changes that were already in the RC, this final release adds one new feature: a plugin for the IMAP FILTER=SIEVE capability. The is a vendor-defined feature that adds the ability to manually invoke Sieve filtering in IMAP. Changelog v0.4.24: + Implement plugin for the a vendor-defined IMAP capability called "FILTER=SIEVE". It adds the ability to manually invoke Sieve filtering in IMAP. More information can be found in doc/plugins/imap_filter_sieve.txt. - Fix assert panics triggered by empty messages that are being forwarded using redirect or vnd.dovecot.report. This does not likely normally occur, but this is seen as a result of certain benign failures in object storage. - Make the length of the subject header for the vacation response configurable and enforce the limit in UTF-8 codepoints rather than bytes. The subject header for a vacation response was statically truncated to 256 bytes, which is too limited for multi-byte UTF-8 characters. - Sieve editheader extension: Fix assertion panic occurring when it is used to manipulate a message header with a very large header field. - Properly abort execution of the sieve_discard script upon error. Before, the LDA Sieve plugin attempted to execute the sieve_discard script when an error occurs. This can lead to the message being lost. - Fix the interaction between quota and the sieve_discard script. When quota was used together with a sieve_discard script, the message delivery did not bounce when the quota was exceeded. The release is available as follows: https://pigeonhole.dovecot.org/releases/2.2/dovecot-2.2-pigeonhole-0.4.24.t… https://pigeonhole.dovecot.org/releases/2.2/dovecot-2.2-pigeonhole-0.4.24.t… Refer to http://pigeonhole.dovecot.org and the Dovecot v2.x wiki for more information. Have fun testing this release and don't hesitate to notify me when there are any problems. Regards, -- Stephan Bosch stephan(a)rename-it.nl

1 0

Autofile Junk for all users
by ＠lbutlr 23 May '18

23 May '18

How would I get the rule if header :contains "X-spam-flag" "YES" { fileinto "Junk"; } To apply to all users mail at delivery time?

4 4

Creating users on the fly, for testing?
by Eric Abrahamsen 23 May '18

23 May '18

I'm trying to set up a reproducible test environment for a MUA I'm working on, with accounts and dummy data that can be trashed and restored while testing. I'd like to exercise the IMAP client part of the MUA, and am looking into using a local dovecot instance to do that. I'm trying to make this as minimal-config as possible: ideally the test environment could create a dummy (virtual) user, insert dummy message data, allow the MUA to log in and manipulate the messages, and then destroy both user and message data at the end of the session. I have the sense that I'll be able to get there by shipping a custom config file along with the test library, that sets up a virtual user with a mail_location under /tmp, and then all operations are done with dovecot -c customconfig.conf Then the temp folder is trashed at the end of the session. Is this likely to work? Is anything likely to bite me? Thanks, Eric

1 0

v2.2.36 released
by Timo Sirainen 23 May '18

23 May '18

https://dovecot.org/releases/2.2/dovecot-2.2.36.tar.gz https://dovecot.org/releases/2.2/dovecot-2.2.36.tar.gz.sig This is the last planned v2.2.x release. We didn't fix everything reported (especially build changes) to try to minimize any unexpected breakages. v2.3.2 will be out with a lot of fixes hopefully in a few weeks. That will start becoming the recommended version to run then. * login-proxy: If ssl_require_crl=no, allow revoked certificates. Also don't do CRL checks for incoming client certificates. * stats plugin: Don't temporarily enable PR_SET_DUMPABLE while opening /proc/self/io. This may still cause security problems if the process is ptrace()d at the same time. Instead, open it while still running as root. + doveadm: Added mailbox cache decision&remove commands. See doveadm-mailbox(1) man page for details. + doveadm: Added rebuild attachments command for rebuilding $HasAttachment or $HasNoAttachment flags for matching mails. See doveadm-rebuild(1) man page for details. + cassandra: Use fallback_consistency on more types of errors - cassandra: Fix consistency=quorum to work - dsync: Lock file generation failed if home directory didn't exist - In some configs if namespace root directory didn't yet exist, Dovecot failed to create mailboxes.lock when trying to create mailboxes - Snippet generation for HTML mails didn't ignore &entities inside blockquotes, producing strange looking snippets. - imapc: Fix assert-crash if getting disconnected and after reconnection all mails in the selected mailbox are gone. - pop3c: Handle unexpected server disconnections without assert-crash - fts: Fixes to indexing mails via virtual mailboxes. - fts: If mails contained NUL characters, the text around it wasn't indexed. - Obsolete dovecot.index.cache offsets were sometimes used. Trying to fetch a field that was just added to cache file may not have always found it. - dict-sql: Fix crash when reading NULL value from database

1 0

XMPP notifications
by André Rodier 23 May '18

23 May '18

Hello all, What is the best way, using sieve, to send XMPP notifications? I am using Debian Stretch, with Dovecot core / sieve packages version 2.2.27-3+deb9u2. Should I use the enotify extension, or a script with extprograms extension? Thanks for your answers. -- André Rodier

2 2

Re: Lmtp issues on dovecot 2.3.x with big messages
by Michael Tratz 23 May '18

23 May '18

> >> Messages are being sent to dovecot LMTP by postfix. If I change this email > >> to another server with dovecot 2.2.x the same message are delivered > >> immediately. > > Confirmed. Starts to fail here around 30Mb. Tested with Swaks. > > > > Working on a fix... > > Problem found. It is an explicit limit of 40Mb (for the 30Mb I saw in my > tests, there was also a base64 encoding I forgot about). > > Will fix both the unhelpful error and the fact that there should be no > limit (currently) for LMTP. > Stephan, I’m having the same issue with LMTP and large messages with dovecot 2.3.x. Can you tell me which commit fixes this issue? I looked through the GitHub commits, but it’s not clear to me which commit fixes this issue. I’d like to apply the patch and re-compile dovecot for my machines instead of having to downgrade to 2.2.35. Thanks, Michael

3 3

lazy_expunge ...
by Matt Bryant 23 May '18

23 May '18

So I decided to configure this plugin and take it for a test drive .. configured using mdbox (main namespace is Maildir) .. So as per Wiki have the following namespaces defined ... location is held within db ... but basically Maildir:~/Maildir for inbox namespace ==== 8< =============== namespace inbox { list = yes type = private inbox = yes prefix = INBOX/ separator = / mailbox Drafts { auto = create special_use = \Drafts } mailbox Spam { auto = create special_use = \Junk } mailbox Trash { auto = create special_use = \Trash } mailbox Sent { auto = create special_use = \Sent } mailbox Archive { auto = create special_use = \Archive } } namespace lazyexpunge { prefix = .EXPUNGED/ hidden = yes list = children subscriptions = no separator = / location = mdbox:~/mdbox:INDEX=~/mdbox:MAILBOXDIR=expunged:LISTINDEX=expunged.list.index } ==================== Can see its working since can see files in the mdbox storage along with indexs etc ... but there seems little to no documentation on how to delete from the expunged namespace and atm trying to even search doesnt seem to work .. doveadm -Dvvv search -u matt(a)the-bryants.net mailbox .EXPUNGED/* subject space gets errors below .. and although says refer to server log .. nothing in there either .. mail_debug is on ... doveadm(matt(a)the-bryants.net): Debug: fts: Indexes disabled for namespace '' doveadm(matt(a)the-bryants.net): Debug: .EXPUNGED/Trash: Mailbox opened because: search doveadm(matt(a)the-bryants.net): Error: fts: Failed to sync mailbox .EXPUNGED: Mailbox doesn't exist: .EXPUNGED doveadm(matt(a)the-bryants.net): Error: Searching mailbox .EXPUNGED/Trash failed: Internal error occurred. Refer to server log for more information. [2018-05-23 15:07:21] doveadm(matt(a)the-bryants.net): Debug: .EXPUNGED/Trash/cobbler: Mailbox opened because: search doveadm(matt(a)the-bryants.net): Error: fts: Failed to sync mailbox .EXPUNGED: Mailbox doesn't exist: .EXPUNGED doveadm(matt(a)the-bryants.net): Error: Searching mailbox .EXPUNGED/Trash/cobbler failed: Internal error occurred. Refer to server log for more information. [2018-05-23 15:07:21] Any ideas is there any better doco around this plugin and use etc ... thanks & rgds Matt

2 6

Upgrading dovecot 2.2 to 2.3 without downtime when using proxy/director?
by Niels Kobschätzki 23 May '18

23 May '18

Hi, I have a setup with several dovecot-servers (2.2.35) and I use dovecot proxy. I upgraded one server to 2.3.1 and got the configs fixed so far that it started again. But when I tried to add it into the proxying again with "doveadm director add" I see the following in the logfiles: May 6 07:19:30 host dovecot: director: Warning: Director xxx.xxx.xxx.176:9090/out disconnected us with reason: Invalid input: OPTIONS May 6 07:19:30 $host dovecot: director: Connecting to xxx.xxx.xxx.171:9090 (as xxx.xxx.xxx.176): Reconnecting after error xxx.xxx.xxx.176 is the upgraded host, xxx.xxx.xxx.171 is one of the other hosts (the applicable hosts are in the range xxx.xxx.xxx.171-176). Do I have to remove all the hosts from the proxy, upgrade them and then add them again? Or is there a way to handle the upgrade without a downtime? After all one of the reasons I use several hosts is that I do not want to have a downtime. Niels

3 3

Re: Best mail encryption solution for per-user
by Aki Tuomi 23 May '18

23 May '18

On 23.05.2018 10:15, mail(a)sjemm.net wrote: > May 23, 2018 8:31 AM, "Aki Tuomi" <aki.tuomi(a)dovecot.fi> wrote: >> On 23.05.2018 09:13, mail(a)sjemm.net wrote: >> >>> May 20, 2018 8:01 PM, mail(a)sjemm.net wrote: >>>> May 20, 2018 2:47 PM, "Aki Tuomi" <aki.tuomi(a)dovecot.fi> wrote: >>> On 19 May 2018 at 16:40 mail(a)sjemm.net wrote: >>> >>> May 18, 2018 10:01 PM, "Aki Tuomi" <aki.tuomi(a)dovecot.fi> wrote: >>> On 18 May 2018 at 21:44 mail(a)sjemm.net wrote: >>> >>> May 18, 2018 4:43 PM, "Aki Tuomi" <aki.tuomi(a)dovecot.fi> wrote: >>> On 18 May 2018 at 17:38 mail(a)sjemm.net wrote: >>> >>> May 18, 2018 4:05 PM, "Aki Tuomi" <aki.tuomi(a)dovecot.fi> wrote: >>> On 18 May 2018 at 16:43 mail(a)sjemm.net wrote: >>> >>> Hi Tai74 and Aki, >>> I followed your conversation with interest on how to setup per user encryption in dovecot. >>> I have setup my dovecot with the following in a conf file: >>> >>> ============== >>> >>> mail_attribute_dict = file:%h/Maildir/dovecot-attributes >>> mail_plugins = $mail_plugins mail_crypt >>> plugin { >>> >>> mail_crypt_curve = secp521r1 >>> >>> mail_crypt_save_version = 2 >>> >>> } >>> >>> ============== >>> >>> This works nice, all emails are being encrypted and every user/folder has keys. >>> But as I understood from your conversation these keys are not protected. And I want them to be >>> protected by the users password used by imap. >>> >>> Those passwords are stored in a mysql DB file. ( I used a guide from workaround [dot] org to set up >>> the DB and postfix/dovecot) >>> >>> but how would i set it so, that the users password from the DB is used to encrypt the keys? >>> >>> should i use mail_crypt_private_password = ? >>> how do i point it to the mysql db then? >>> im unsure about this >>> >>> Do you have any hints on this? >>> >>> Kind regards, >>> Zjemm >>> >>> The passwords in your MySQL database are, hopefully, not in plaintext. If you want to secure your >>> user's keys using user's login password, you must have a TOOL that manages this. >>> >>> You can use mail_crypt_private_password = %w in (mysql) passdb fields to provide the user's login >>> password as private password. You might want to run it thru some hash, so %{sha1:password} might be >>> a good option. >>> >>> You can change the key password using 'doveadm mailbox cryptokey', this needs to be done every time >>> user changes his password. >>> >>> Also note that if you go down this road, and the user forgets his password, you will not be able to >>> recover the emails without backup copy of the private key. >>> >>> Aki >>> >>> Hi Aki >>> >>> I used the following command: >>> dovecot pw -s SHA256-CRYPT >>> >>> the output on the chosen password looks like: {SHA256-CRYPT}$5$Rokc06a7In4SF3bO$OQpGQWqg........ >>> >>> This output is used to store in the password fields in the database. So no plain text passwords no >>> :) >>> >>> You can use mail_crypt_private_password = %w in (mysql) passdb fields to provide the user's login >>> password as private password. >>> >>> can you explain this a bit more for me? >>> >>> for now i have in the 10-auth.conf file the following: >>> ============== >>> passdb { >>> driver = sql >>> >>> # Path for SQL configuration file, see example-config/dovecot-sql.conf.ext >>> args = /etc/dovecot/dovecot-sql.conf.ext >>> } >>> >>> and: >>> >>> userdb { >>> driver = static >>> args = uid=vmail gid=vmail home=/var/vmail/%d/%n >>> } >>> ============== >>> >>> then i have in dovecot-sql.conf.ext >>> ============== >>> driver = mysql >>> connect = host=x.x.x.x dbname=mailserver user=mailuser password=mailpasswordexample >>> default_pass_scheme = SHA256-CRYPT >>> password_query = SELECT email as user, password FROM virtual_users WHERE email='%u'; >>> ============== >>> Where do i need to set : mail_crypt_private_password = %w ? >>> >>> password as private password. You might want to run it thru some hash, so %{sha1:password} might be >>> a good option. >>> >>> the passwords are allready hashed in the DB using: dovecot pw -s SHA256-CRYPT to genereate the has. >>> so this step isnt nesesary anymore am i right? >>> >>> Thank you for your quick response, very helpfull >>> >>> Zjemm >>> >>> You misunderstood a bit. The idea is to use the *plaintext* password as the password for the >>> private key. Otherwise anyone could just decrypt it by looking at your database where the hashed >>> password is.. >>> >>> So: >>> >>> password_query = SELECT email as user, password, '%w' AS userdb_mail_crypt_private_password FROM >>> virtual_users WHERE email='%u' >>> >>> Aki >>> >>> Hi Aki, >>> >>> Thank you very much for your help, i realy appreciate that. >>> >>> Ok so if i understand it correctly i'll have to use: >>> >>> password_query = SELECT email as user, password, '%w' AS userdb_mail_crypt_private_password FROM >>> virtual_users WHERE email='%u' >>> >>> in my dovecot-sql.conf.ext file >>> >>> This query selects the user, the password, and %w >>> >>> if i run a little query myself: >>> MariaDB [mailserver]> SELECT email as user, password, '%w' AS userdb_mail_crypt_private_password >>> FROM virtual_users; >>> +------------------+----------------------------------+------------------------------------+ >>> | user | password | userdb_mail_crypt_private_password | >>> +------------------+----------------------------------+------------------------------------+ >>> | john(a)example.org | {SHA256-CRYPT}$5$M/GWzmtjsLroRWI | %w | >>> +------------------+----------------------------------+------------------------------------+ >>> >>> %w is a dovecot variable, and stands for the plaintext password, but the password is not stored as >>> plaintext in the DB, %w get filled with the actual plaintext password by dovecot upon the user that >>> is typing in the password when authenticating. >>> >>> is this correct? >>> >>> yes. >>> >>> so then i have the username the hashed password en the plaintext password as a result of the query. >>> >>> yes >>> >>> now userdb_mail_crypt_private_password = the plaintext password >>> do i need to reference it somewhere? or is userdb_mail_crypt_private_password autmatically used by >>> the dovecot mail_crypt plugin to encrypt the keys? or should it be mail_crypt_private_password? >>> >>> It gets injected into the mail process as 'mail_crypt_private_password', as if it was set in plugin >>> {} section. >>> >>> if i have this setup working i'm going to write a blog post on this topic to share this knowledge >>> >>> Thanks again and have a great weekend. >>> >>> Zjemm >>> >>> Aki >>> >>> Hi Aki, >>> >>> Cool i'm testing it right now. >>> I have set up a new mailserver (life is great with lxc containers :) ) >>> >>> postfix and dovecot are working like normal >>> >>> next i enable mail_crypt >>> >>> i did create a file: /etc/dovecot/conf.d/10-mailcrypt.conf >>> ========================== >>> mail_attribute_dict = file:%h/Maildir/dovecot-attributes >>> >>> mail_plugins = $mail_plugins mail_crypt >>> >>> plugin { >>> mail_crypt_curve = secp521r1 >>> mail_crypt_save_version = 2 >>> } >>> ========================== >>> >>> and then i changed the file: /etc/dovecot/dovecot-sql.conf.ext >>> >>> so the query is now the new query: >>> password_query = SELECT email as user, password, '%w' AS userdb_mail_crypt_private_password FROM >>> virtual_users WHERE email='%u'; >>> >>> then i restarted dovecot and postfix and send a test email to the one and only testuser that is in >>> there. >>> >>> when i open the mailbox with the tool mutt, i can see the new email, and when openening the email >>> the mutt client drops the connection. >>> >>> in the log i can see: >>> >>> May 19 13:34:48 mailserver1.example.local dovecot[600]: imap-login: Login: user=<john(a)example.org>, >>> method=PLAIN, rip=::1, lip=::1, mpid=713, TLS, session=<E3PnIY9sNM4AAAAAAAAAAAAAAAAAAAAB> >>> May 19 13:34:49 mailserver1.example.local dovecot[600]: imap(john(a)example.org): Error: read() >>> failed: >>> read(/var/vmail/example.org/john/Maildir/cur/1526736378.M161472P641.mailser…, >>> =571:2,) failed: Private key not available: Cannot decrypt key >>> bfc5bb25b1bf64290eea6dc14b516c6a0a25b64551b6e4f0f8677ba7274887cb: error:03070068:bignum >>> routines:BN_mpi2bn:encoding error (FETCH BODY[] for mailbox INBOX UID 8) >>> >>> i think i missed a step, but witch one? >>> >>> the userpassword hasnt been changed (that would be the next step in the testing process) >>> >>> should i've use doveadm first to encrypt the key with that userpassword? i thought it would do that >>> on the fly, because the initial keys where only just created when enabling the mail_crypt plugin >>> >>> please let me know your thougts >>> Zjemm >>> I noticed you replied directly to me, and not to the list, too... fixed that for you. >>> >>> mail_crypt_private_password is used when key is created, but if you have created it before using >>> password, you'll need to encrypt it before turning the setting on. >>> >>> Aki >>>> Hi, Ok i'm sorry about that, thank you for fixing that. i'm a bit new to mailing lists :) >>>> >>>> are you a dovecot devoloper? or a enthusiastic user? >>>> >>>> anyway, i managed to get it working now with all your help :) >>>> >>>> to start fresh i did a: >>>> rm -rf /var/vmail/example.org >>>> >>>> so all email is gone, and i assume all dovecot keys are gone that way. >>>> >>>> Then i tried to set a password first: >>>> >>>> root@mailserver1:/var/vmail# doveadm mailbox cryptokey password -u john(a)example.org -n summersun >>>> result: Changed password for 0 key(s) >>>> >>>> (summersun = the password for this user) >>>> >>>> but then it says there are 0 keys, so then i send the test user an email and try to open the >>>> mailbox, i'll get: >>>> >>>> imap(john(a)example.org): Error: read() failed: >>>> read(/var/vmail/example.org/john/Maildir/cur/1526827992.M149712P883.mailser…, >>>> =561:2,) failed: Private key not available: Cannot decrypt key >>>> 71849013a70b0c631c06112077e7c2fe39b0b2737b4933b219793841209d4e7f: error:03070068:bignum >>>> routines:BN_mpi2bn:encoding error >>>> >>>> but hey, now the key's are created, so i tried to set the password again: >>>> >>>> root@mailserver1:/var/vmail# doveadm mailbox cryptokey password -u john(a)example.org -n summersun >>>> result: dcrypt_key_load_private(787701bd677dd69a26842547a3926cbaa625b0b5a91751f06678c3e9708343d9) >>>> failed: password missing >>>> ========= >>>> >>>> Lets start over again, i did a new: >>>> rm -rf /var/vmail/example.org >>>> >>>> i disabled the mail_crypt_private_password in the sql query and send an email to the test user. >>>> now again new keys are generated. >>>> >>>> then i did set the password via doveadm: >>>> >>>> root@mailserver1:/var/vmail# doveadm mailbox cryptokey password -u john(a)example.org -n summersun >>>> result: Changed password for 1 key(s) >>>> >>>> i enabled the mail_crypt_private_password again in the sql query part and now it works :) >>>> >>>> YESSS!!! >>>> >>>> if i now change the password for the user, i cannot read the email anymore. that is what should >>>> happen. >>>> so now i changed the password for this user also with doveadm: >>>> - doveadm mailbox cryptokey password -u john(a)example.org -n qwerty -o summersun >>>> >>>> and now i'm able to read the emails again. so it all works now as expected. >>>> >>>> i have now only one thing remaining. >>>> >>>> when i want to add a new user, i have to somehow: >>>> - create the new user in the mysql DB >>>> - start with dovecot not using mail_crypt_private_password (so disabled) >>>> - send an initial email to let the users mailbox be created and generate the keys >>>> - set the users password with doveadm >>>> - restart dovecot again with mail_crypt_private_password (so enabled) >>>> >>>> but this would be disruptive to existing users, and i would have to script the whole thing as a >>>> "add-new-user" script to make it usable i guess. >>>> >>>> do you know of a more easy way of acomplishing this? >>>> could i use doveadm for all steps, and get around the mail_crypt_private_password disable part? >>>> >>>> or could i add a column in the mysql db called userdb_mail_crypt_private_password and fill that >>>> column with %w for users that allready exist, and empty for new users. >>>> when being empty, it might not set the mail_crypt_private_password for new users >>>> >>>> or is this the wrong way of thinking? >>>> >>>> let me know your thoughts on this. >>>> >>>> And last but not least, i really want to thank you for all your help. It is a really nice >>>> experience. >>>> Bless you! >>>> >>>> Zjemm >>> Hi Aki, >>> >>> You did fix the posting on the mail archive, i can see our conversation on there, all but the last >>> email i send to you. >>> Maybe you did not received the last email? >>> >>> would you be willing to take a look at my last question in the email See below: >>> Thank you very much. >>> >>> ================================ >>> i have now only one thing remaining. >>> >>> when i want to add a new user, i have to somehow: >>> - create the new user in the mysql DB >>> - start with dovecot not using mail_crypt_private_password (so disabled) >>> - send an initial email to let the users mailbox be created and generate the keys >>> - set the users password with doveadm >>> - restart dovecot again with mail_crypt_private_password (so enabled) >>> >>> but this would be disruptive to existing users, and i would have to script the whole thing as a >>> "add-new-user" script to make it usable i guess. >>> >>> do you know of a more easy way of acomplishing this? >>> could i use doveadm for all steps, and get around the mail_crypt_private_password disable part? >>> >>> or could i add a column in the mysql db called userdb_mail_crypt_private_password and fill that >>> column with %w for users that allready exist, and empty for new users. >>> when being empty, it might not set the mail_crypt_private_password for new users >>> >>> or is this the wrong way of thinking? >>> >>> let me know your thoughts on this. >>> >>> And last but not least, i really want to thank you for all your help. It is a really nice >>> experience. >>> Bless you! >>> >>> Zjemm >> If you have mail_crypt_private_password set *when* keys are generated, >> dovecot should use that password to encrypt the user key. >> >> Aki > > Hi Aki, > > well, if there is a new email user setup in the mysql DB, and no email has been send to that new user. at that point there are no keys. > > So trying to set a password on those key's wont work. see: > root@mailserver1:/var/vmail/example.org# doveadm mailbox cryptokey password -u john2(a)example.org -n qwerty > result: Changed password for 0 key(s) > > the keys need to be generated first. And that only happens when sending a mail to that new user. Also, at the point of creating the keys, the mail_crypt_private_password should be disabled otherwise the keys are generated and also encrypted with no user password, and then im unable to set a new pasword for that key > > > How can i set the password before the keys are generated? > or can i manually generate key's and then set the password? > > so at this point i have to do the following: You can use doveadm mailbox cryptokey generate -u user -U to generate a user key. Aki >>> - create the new user in the mysql DB >>> - start with dovecot not using mail_crypt_private_password (so disabled) >>> - send an initial email to let the users mailbox be created and generate the keys >>> - set the users password with doveadm >>> - restart dovecot again with mail_crypt_private_password (so enabled) > can i somehow enable the mail_crypt_private_password per user? > because this mysql query always returns: %w > and thus allways sets: userdb_mail_crypt_private_password > SELECT email as user, password, '%w' AS userdb_mail_crypt_private_password FROM virtual_users;

1 0

Re: Best mail encryption solution for per-user
by Aki Tuomi 23 May '18

23 May '18

On 23.05.2018 09:13, mail(a)sjemm.net wrote: > May 20, 2018 8:01 PM, mail(a)sjemm.net wrote: >> May 20, 2018 2:47 PM, "Aki Tuomi" <aki.tuomi(a)dovecot.fi> wrote: >> >>>> On 19 May 2018 at 16:40 mail(a)sjemm.net wrote: >>>> >>>> May 18, 2018 10:01 PM, "Aki Tuomi" <aki.tuomi(a)dovecot.fi> wrote: >>>> On 18 May 2018 at 21:44 mail(a)sjemm.net wrote: >>>> >>>> May 18, 2018 4:43 PM, "Aki Tuomi" <aki.tuomi(a)dovecot.fi> wrote: >>>> On 18 May 2018 at 17:38 mail(a)sjemm.net wrote: >>>> >>>> May 18, 2018 4:05 PM, "Aki Tuomi" <aki.tuomi(a)dovecot.fi> wrote: >>>> On 18 May 2018 at 16:43 mail(a)sjemm.net wrote: >>>> >>>> Hi Tai74 and Aki, >>>> I followed your conversation with interest on how to setup per user encryption in dovecot. >>>> I have setup my dovecot with the following in a conf file: >>>> >>>> ============== >>>> >>>> mail_attribute_dict = file:%h/Maildir/dovecot-attributes >>>> mail_plugins = $mail_plugins mail_crypt >>>> plugin { >>>> >>>> mail_crypt_curve = secp521r1 >>>> >>>> mail_crypt_save_version = 2 >>>> >>>> } >>>> >>>> ============== >>>> >>>> This works nice, all emails are being encrypted and every user/folder has keys. >>>> But as I understood from your conversation these keys are not protected. And I want them to be >>>> protected by the users password used by imap. >>>> >>>> Those passwords are stored in a mysql DB file. ( I used a guide from workaround [dot] org to set up >>>> the DB and postfix/dovecot) >>>> >>>> but how would i set it so, that the users password from the DB is used to encrypt the keys? >>>> >>>> should i use mail_crypt_private_password = ? >>>> how do i point it to the mysql db then? >>>> im unsure about this >>>> >>>> Do you have any hints on this? >>>> >>>> Kind regards, >>>> Zjemm >>>> >>>> The passwords in your MySQL database are, hopefully, not in plaintext. If you want to secure your >>>> user's keys using user's login password, you must have a TOOL that manages this. >>>> >>>> You can use mail_crypt_private_password = %w in (mysql) passdb fields to provide the user's login >>>> password as private password. You might want to run it thru some hash, so %{sha1:password} might be >>>> a good option. >>>> >>>> You can change the key password using 'doveadm mailbox cryptokey', this needs to be done every time >>>> user changes his password. >>>> >>>> Also note that if you go down this road, and the user forgets his password, you will not be able to >>>> recover the emails without backup copy of the private key. >>>> >>>> Aki >>>> >>>> Hi Aki >>>> >>>> I used the following command: >>>> dovecot pw -s SHA256-CRYPT >>>> >>>> the output on the chosen password looks like: {SHA256-CRYPT}$5$Rokc06a7In4SF3bO$OQpGQWqg........ >>>> >>>> This output is used to store in the password fields in the database. So no plain text passwords no >>>> :) >>>> >>>> You can use mail_crypt_private_password = %w in (mysql) passdb fields to provide the user's login >>>> password as private password. >>>> >>>> can you explain this a bit more for me? >>>> >>>> for now i have in the 10-auth.conf file the following: >>>> ============== >>>> passdb { >>>> driver = sql >>>> >>>> # Path for SQL configuration file, see example-config/dovecot-sql.conf.ext >>>> args = /etc/dovecot/dovecot-sql.conf.ext >>>> } >>>> >>>> and: >>>> >>>> userdb { >>>> driver = static >>>> args = uid=vmail gid=vmail home=/var/vmail/%d/%n >>>> } >>>> ============== >>>> >>>> then i have in dovecot-sql.conf.ext >>>> ============== >>>> driver = mysql >>>> connect = host=x.x.x.x dbname=mailserver user=mailuser password=mailpasswordexample >>>> default_pass_scheme = SHA256-CRYPT >>>> password_query = SELECT email as user, password FROM virtual_users WHERE email='%u'; >>>> ============== >>>> Where do i need to set : mail_crypt_private_password = %w ? >>>> >>>> password as private password. You might want to run it thru some hash, so %{sha1:password} might be >>>> a good option. >>>> >>>> the passwords are allready hashed in the DB using: dovecot pw -s SHA256-CRYPT to genereate the has. >>>> so this step isnt nesesary anymore am i right? >>>> >>>> Thank you for your quick response, very helpfull >>>> >>>> Zjemm >>>> >>>> You misunderstood a bit. The idea is to use the *plaintext* password as the password for the >>>> private key. Otherwise anyone could just decrypt it by looking at your database where the hashed >>>> password is.. >>>> >>>> So: >>>> >>>> password_query = SELECT email as user, password, '%w' AS userdb_mail_crypt_private_password FROM >>>> virtual_users WHERE email='%u' >>>> >>>> Aki >>>> >>>> Hi Aki, >>>> >>>> Thank you very much for your help, i realy appreciate that. >>>> >>>> Ok so if i understand it correctly i'll have to use: >>>> >>>> password_query = SELECT email as user, password, '%w' AS userdb_mail_crypt_private_password FROM >>>> virtual_users WHERE email='%u' >>>> >>>> in my dovecot-sql.conf.ext file >>>> >>>> This query selects the user, the password, and %w >>>> >>>> if i run a little query myself: >>>> MariaDB [mailserver]> SELECT email as user, password, '%w' AS userdb_mail_crypt_private_password >>>> FROM virtual_users; >>>> +------------------+----------------------------------+------------------------------------+ >>>> | user | password | userdb_mail_crypt_private_password | >>>> +------------------+----------------------------------+------------------------------------+ >>>> | john(a)example.org | {SHA256-CRYPT}$5$M/GWzmtjsLroRWI | %w | >>>> +------------------+----------------------------------+------------------------------------+ >>>> >>>> %w is a dovecot variable, and stands for the plaintext password, but the password is not stored as >>>> plaintext in the DB, %w get filled with the actual plaintext password by dovecot upon the user that >>>> is typing in the password when authenticating. >>>> >>>> is this correct? >>>> >>>> yes. >>>> >>>> so then i have the username the hashed password en the plaintext password as a result of the query. >>>> >>>> yes >>>> >>>> now userdb_mail_crypt_private_password = the plaintext password >>>> do i need to reference it somewhere? or is userdb_mail_crypt_private_password autmatically used by >>>> the dovecot mail_crypt plugin to encrypt the keys? or should it be mail_crypt_private_password? >>>> >>>> It gets injected into the mail process as 'mail_crypt_private_password', as if it was set in plugin >>>> {} section. >>>> >>>> if i have this setup working i'm going to write a blog post on this topic to share this knowledge >>>> >>>> Thanks again and have a great weekend. >>>> >>>> Zjemm >>>> >>>> Aki >>>> >>>> Hi Aki, >>>> >>>> Cool i'm testing it right now. >>>> I have set up a new mailserver (life is great with lxc containers :) ) >>>> >>>> postfix and dovecot are working like normal >>>> >>>> next i enable mail_crypt >>>> >>>> i did create a file: /etc/dovecot/conf.d/10-mailcrypt.conf >>>> ========================== >>>> mail_attribute_dict = file:%h/Maildir/dovecot-attributes >>>> >>>> mail_plugins = $mail_plugins mail_crypt >>>> >>>> plugin { >>>> mail_crypt_curve = secp521r1 >>>> mail_crypt_save_version = 2 >>>> } >>>> ========================== >>>> >>>> and then i changed the file: /etc/dovecot/dovecot-sql.conf.ext >>>> >>>> so the query is now the new query: >>>> password_query = SELECT email as user, password, '%w' AS userdb_mail_crypt_private_password FROM >>>> virtual_users WHERE email='%u'; >>>> >>>> then i restarted dovecot and postfix and send a test email to the one and only testuser that is in >>>> there. >>>> >>>> when i open the mailbox with the tool mutt, i can see the new email, and when openening the email >>>> the mutt client drops the connection. >>>> >>>> in the log i can see: >>>> >>>> May 19 13:34:48 mailserver1.example.local dovecot[600]: imap-login: Login: user=<john(a)example.org>, >>>> method=PLAIN, rip=::1, lip=::1, mpid=713, TLS, session=<E3PnIY9sNM4AAAAAAAAAAAAAAAAAAAAB> >>>> May 19 13:34:49 mailserver1.example.local dovecot[600]: imap(john(a)example.org): Error: read() >>>> failed: >>>> read(/var/vmail/example.org/john/Maildir/cur/1526736378.M161472P641.mailser…, >>>> =571:2,) failed: Private key not available: Cannot decrypt key >>>> bfc5bb25b1bf64290eea6dc14b516c6a0a25b64551b6e4f0f8677ba7274887cb: error:03070068:bignum >>>> routines:BN_mpi2bn:encoding error (FETCH BODY[] for mailbox INBOX UID 8) >>>> >>>> i think i missed a step, but witch one? >>>> >>>> the userpassword hasnt been changed (that would be the next step in the testing process) >>>> >>>> should i've use doveadm first to encrypt the key with that userpassword? i thought it would do that >>>> on the fly, because the initial keys where only just created when enabling the mail_crypt plugin >>>> >>>> please let me know your thougts >>>> Zjemm >>> I noticed you replied directly to me, and not to the list, too... fixed that for you. >>> >>> mail_crypt_private_password is used when key is created, but if you have created it before using >>> password, you'll need to encrypt it before turning the setting on. >>> >>> Aki >> Hi, Ok i'm sorry about that, thank you for fixing that. i'm a bit new to mailing lists :) >> >> are you a dovecot devoloper? or a enthusiastic user? >> >> anyway, i managed to get it working now with all your help :) >> >> to start fresh i did a: >> rm -rf /var/vmail/example.org >> >> so all email is gone, and i assume all dovecot keys are gone that way. >> >> Then i tried to set a password first: >> >> root@mailserver1:/var/vmail# doveadm mailbox cryptokey password -u john(a)example.org -n summersun >> result: Changed password for 0 key(s) >> >> (summersun = the password for this user) >> >> but then it says there are 0 keys, so then i send the test user an email and try to open the >> mailbox, i'll get: >> >> imap(john(a)example.org): Error: read() failed: >> read(/var/vmail/example.org/john/Maildir/cur/1526827992.M149712P883.mailser…, >> =561:2,) failed: Private key not available: Cannot decrypt key >> 71849013a70b0c631c06112077e7c2fe39b0b2737b4933b219793841209d4e7f: error:03070068:bignum >> routines:BN_mpi2bn:encoding error >> >> but hey, now the key's are created, so i tried to set the password again: >> >> root@mailserver1:/var/vmail# doveadm mailbox cryptokey password -u john(a)example.org -n summersun >> result: dcrypt_key_load_private(787701bd677dd69a26842547a3926cbaa625b0b5a91751f06678c3e9708343d9) >> failed: password missing >> ========= >> >> Lets start over again, i did a new: >> rm -rf /var/vmail/example.org >> >> i disabled the mail_crypt_private_password in the sql query and send an email to the test user. >> now again new keys are generated. >> >> then i did set the password via doveadm: >> >> root@mailserver1:/var/vmail# doveadm mailbox cryptokey password -u john(a)example.org -n summersun >> result: Changed password for 1 key(s) >> >> i enabled the mail_crypt_private_password again in the sql query part and now it works :) >> >> YESSS!!! >> >> if i now change the password for the user, i cannot read the email anymore. that is what should >> happen. >> so now i changed the password for this user also with doveadm: >> - doveadm mailbox cryptokey password -u john(a)example.org -n qwerty -o summersun >> >> and now i'm able to read the emails again. so it all works now as expected. >> >> i have now only one thing remaining. >> >> when i want to add a new user, i have to somehow: >> - create the new user in the mysql DB >> - start with dovecot not using mail_crypt_private_password (so disabled) >> - send an initial email to let the users mailbox be created and generate the keys >> - set the users password with doveadm >> - restart dovecot again with mail_crypt_private_password (so enabled) >> >> but this would be disruptive to existing users, and i would have to script the whole thing as a >> "add-new-user" script to make it usable i guess. >> >> do you know of a more easy way of acomplishing this? >> could i use doveadm for all steps, and get around the mail_crypt_private_password disable part? >> >> or could i add a column in the mysql db called userdb_mail_crypt_private_password and fill that >> column with %w for users that allready exist, and empty for new users. >> when being empty, it might not set the mail_crypt_private_password for new users >> >> or is this the wrong way of thinking? >> >> let me know your thoughts on this. >> >> And last but not least, i really want to thank you for all your help. It is a really nice >> experience. >> Bless you! >> >> Zjemm > Hi Aki, > > You did fix the posting on the mail archive, i can see our conversation on there, all but the last email i send to you. > Maybe you did not received the last email? > > would you be willing to take a look at my last question in the email See below: > Thank you very much. > > ================================ > i have now only one thing remaining. > > when i want to add a new user, i have to somehow: > - create the new user in the mysql DB > - start with dovecot not using mail_crypt_private_password (so disabled) > - send an initial email to let the users mailbox be created and generate the keys > - set the users password with doveadm > - restart dovecot again with mail_crypt_private_password (so enabled) > > but this would be disruptive to existing users, and i would have to script the whole thing as a "add-new-user" script to make it usable i guess. > > do you know of a more easy way of acomplishing this? > could i use doveadm for all steps, and get around the mail_crypt_private_password disable part? > > or could i add a column in the mysql db called userdb_mail_crypt_private_password and fill that column with %w for users that allready exist, and empty for new users. > when being empty, it might not set the mail_crypt_private_password for new users > > or is this the wrong way of thinking? > > let me know your thoughts on this. > > And last but not least, i really want to thank you for all your help. It is a really nice experience. > Bless you! > > Zjemm If you have mail_crypt_private_password set *when* keys are generated, dovecot should use that password to encrypt the user key. Aki

1 0

Cannot delete folder
by Yves Goergen 22 May '18

22 May '18

Hi there, I cannot delete IMAP folders in new mailboxes. When trying to delete a folder in Thunderbird I get the error message "renaming not supported across conflicting directory permissions". Looking up the error on the web led me to checking the mailbox directory's permissions. They're inconsistent in new mailboxes. While every single directory in an old mailbox has "drwx--S---", some of the directories in a new mailbox have "drwxr-sr-x" instead. I'm not sure what that means. The folders with the later permissions are "Drafts", "Sent" and "Trash". Folders with the first permissions are "Junk", "Archives" and "Archives.2018". All folders were created by Thunderbird automatically. Now I wanted to delete "Archives.2018". What's the issue here? Why do folders created by the same MUA in the same event on the same mail server have different permissions and why can't I delete one of them (which would probably move it into the trash folder first)? Dovecot version is 2.2.22 on Ubuntu 16.04, Thunderbird is 52.6.0 on Windows 10. -Yves

7 19

(no subject)
by Rebel Mee 21 May '18

21 May '18

0b4a77c09cb4c18c49177e4ad76e0b62e3ec5ae0

1 0

(no subject)
by Rebel Mee 21 May '18

21 May '18

1 0

Dovecot blacklist?
by Marc Perkel 21 May '18

21 May '18

Just wondering if there is an easy way to have dovecot do a blacklist lookup as a negative authentication so that if the IP is on a blacklist then authentification fails even if they get the password right. If this works I have a blacklist everyone can use.

2 3

SSL error after upgrading to 2.31
by Marc Perkel 21 May '18

21 May '18

After upgrading to 2.31 I'm getting this error. Not sure what I'm doing wrong. No (No signatures could be verified because the chain contains only one certificate and it is not self signed.) ssl = yes ssl_cert = </etc/exim/certs/ctyme.com.crt ssl_key = </etc/exim/certs/ctyme.com.key ssl_ca = </etc/exim/certs/ca.crt local mail.ctyme.com { protocol imap { ssl_cert = </etc/exim/certs/ctyme.com.crt ssl_key = </etc/exim/certs/ctyme.com.key ssl_ca = </etc/exim/certs/ca.crt } protocol pop3 { ssl_cert = </etc/exim/certs/ctyme.com.crt ssl_key = </etc/exim/certs/ctyme.com.key ssl_ca = </etc/exim/certs/ca.crt } } local mail.junkemailfilter.com { protocol imap { ssl_cert = </etc/exim/certs/junkemailfilter.com.crt ssl_key = </etc/exim/certs/junkemailfilter.com.key ssl_ca = </etc/exim/certs/ca.crt } protocol pop3 { ssl_cert = </etc/exim/certs/junkemailfilter.com.crt ssl_key = </etc/exim/certs/junkemailfilter.com.key ssl_ca = </etc/exim/certs/ca.crt } }

2 1

install dovecot 2.2.35 debian jessie
by Webert de Souza Lima 21 May '18

21 May '18

Hi, I can't figure how to install latest stable dovecot version 2.2.35 in Debian Jessie If I follow this guide <https://repo.dovecot.org/>, it ends up installing 2.3 If I follow this guide <https://wiki.dovecot.org/PrebuiltBinaries#preview>, it ends up installing either 2.2.13 if I use "stable" or 2.2.36 alpha if I use "jessie" I see that 2.2.35 seems to be missing here too: http://xi.dovecot.fi/debian/pool/jessie-auto/dovecot-2.2/ Thanks. Regards, Webert Lima DevOps Engineer at MAV Tecnologia *Belo Horizonte - Brasil* *IRC NICK - WebertRLZ*

3 7

Dovecot fts script with solr
by André Rodier 21 May '18

21 May '18

Hello again, I have created a parser script, a little bit more advanced than the one provided with Dovecot. The main feature is probably to index documents inside zip/rar/tgz archives... I am using Ansible, swaks and doveadm to run automatic tests for each supported content. For specific reasons, I am not yet able to add Apache Tika to the distribution. However, I already made some tests with it. For now, I want to talk about the indexing script. I also have noticed a few weird behaviours. I will mention them at the end, albeit I am not 100% sure where they are coming from. I realised last week that using QEMU snapshots was not working as expected, so I am now more careful with this feature. For the developers or users who would be interested and the Dovecot team members to understand my questions, here how the tests are working: To run my tests, I have a set of files in various formats, with a UUID inside. They are office files, text files, or even archives with a text file inside... The first test I am running is the script alone. I check that the script can convert the file to text, and then I use grep to check the UUID is present. This works *perfectly* for all the content, except ppt, but it's minor. The second test is full: - I use swaks to send the email with an attachment and the appropriate mime type. - I then refresh the index using doveadm rescan. - I check that fts search returns a line, with doveadm fts search. - I then expunge the mailbox to be sure that the next test is valid. For the second test, it works almost all the time, except in the following situations: - When the attachment is an email (mime type message/rfc822) - RTF (could be a bug in my script) - Text file in UTF16 (Even if this file is converted to UTF8) *Questions:* 1 - Is there any limitation or special case for the mime message/rfc822 2 - Is the mime type received coming from the email headers? 3 - When the script is called without arguments, what is the purpose of the extension at the end of each supported mime types? 4 - Can I return a wildcard in the supported mime types, for instance "text/* *" ? 5 - I would like to handle attachments of types application/octet-stream. I have added "application/octet-stream *", but I am not sure if dovecot will pass the attachments with these mime type or not. *Notes:* 1 - I used netcat to monitor the solr server. I realise that sometimes, the data sent to the solr server only contains the headers of the email, not the text returned by the parser. Especially with rfc822 messages. I will do more tests. 2 - I just finished to write the script, it's not yet refactored, but at list it is well documented. I will do a full security audit later. I am actually testing an associated AppArmor profile. 3 - I will do more intensive test on the script on bigger mail boxes with more attachments. 4 - I may rewrite the script in Python 5 - Suggestions welcome. I initially attached the current version of the script, but the email is probably pending for review...In this case, the last development version is on Github: https://github.com/progmaticltd/homebox/blob/dev/install/playbooks/roles/do… The configuration of supported mime types is a simple file, accessible on github as well: https://github.com/progmaticltd/homebox/blob/dev/install/playbooks/roles/do… Thanks for your advices or suggestions.

2 1

Re: Best mail encryption solution for per-user
by Aki Tuomi 20 May '18

20 May '18

> On 19 May 2018 at 16:40 mail(a)sjemm.net wrote: > > > May 18, 2018 10:01 PM, "Aki Tuomi" <aki.tuomi(a)dovecot.fi> wrote: > >> On 18 May 2018 at 21:44 mail(a)sjemm.net wrote: > >> > >> May 18, 2018 4:43 PM, "Aki Tuomi" <aki.tuomi(a)dovecot.fi> wrote: > >> On 18 May 2018 at 17:38 mail(a)sjemm.net wrote: > >> > >> May 18, 2018 4:05 PM, "Aki Tuomi" <aki.tuomi(a)dovecot.fi> wrote: > >> On 18 May 2018 at 16:43 mail(a)sjemm.net wrote: > >> > >> Hi Tai74 and Aki, > >> I followed your conversation with interest on how to setup per user encryption in dovecot. > >> I have setup my dovecot with the following in a conf file: > >> > >> ============== > >> > >> mail_attribute_dict = file:%h/Maildir/dovecot-attributes > >> mail_plugins = $mail_plugins mail_crypt > >> plugin { > >> > >> mail_crypt_curve = secp521r1 > >> > >> mail_crypt_save_version = 2 > >> > >> } > >> > >> ============== > >> > >> This works nice, all emails are being encrypted and every user/folder has keys. > >> But as I understood from your conversation these keys are not protected. And I want them to be > >> protected by the users password used by imap. > >> > >> Those passwords are stored in a mysql DB file. ( I used a guide from workaround [dot] org to set up > >> the DB and postfix/dovecot) > >> > >> but how would i set it so, that the users password from the DB is used to encrypt the keys? > >> > >> should i use mail_crypt_private_password = ? > >> how do i point it to the mysql db then? > >> im unsure about this > >> > >> Do you have any hints on this? > >> > >> Kind regards, > >> Zjemm > >> > >> The passwords in your MySQL database are, hopefully, not in plaintext. If you want to secure your > >> user's keys using user's login password, you must have a TOOL that manages this. > >> > >> You can use mail_crypt_private_password = %w in (mysql) passdb fields to provide the user's login > >> password as private password. You might want to run it thru some hash, so %{sha1:password} might be > >> a good option. > >> > >> You can change the key password using 'doveadm mailbox cryptokey', this needs to be done every time > >> user changes his password. > >> > >> Also note that if you go down this road, and the user forgets his password, you will not be able to > >> recover the emails without backup copy of the private key. > >> > >> Aki > >> > >> Hi Aki > >> > >> I used the following command: > >> dovecot pw -s SHA256-CRYPT > >> > >> the output on the chosen password looks like: {SHA256-CRYPT}$5$Rokc06a7In4SF3bO$OQpGQWqg........ > >> > >> This output is used to store in the password fields in the database. So no plain text passwords no > >> :) > >> > >> You can use mail_crypt_private_password = %w in (mysql) passdb fields to provide the user's login > >> password as private password. > >> > >> can you explain this a bit more for me? > >> > >> for now i have in the 10-auth.conf file the following: > >> ============== > >> passdb { > >> driver = sql > >> > >> # Path for SQL configuration file, see example-config/dovecot-sql.conf.ext > >> args = /etc/dovecot/dovecot-sql.conf.ext > >> } > >> > >> and: > >> > >> userdb { > >> driver = static > >> args = uid=vmail gid=vmail home=/var/vmail/%d/%n > >> } > >> ============== > >> > >> then i have in dovecot-sql.conf.ext > >> ============== > >> driver = mysql > >> connect = host=x.x.x.x dbname=mailserver user=mailuser password=mailpasswordexample > >> default_pass_scheme = SHA256-CRYPT > >> password_query = SELECT email as user, password FROM virtual_users WHERE email='%u'; > >> ============== > >> Where do i need to set : mail_crypt_private_password = %w ? > >> > >> password as private password. You might want to run it thru some hash, so %{sha1:password} might be > >> a good option. > >> > >> the passwords are allready hashed in the DB using: dovecot pw -s SHA256-CRYPT to genereate the has. > >> so this step isnt nesesary anymore am i right? > >> > >> Thank you for your quick response, very helpfull > >> > >> Zjemm > >> > >> You misunderstood a bit. The idea is to use the *plaintext* password as the password for the > >> private key. Otherwise anyone could just decrypt it by looking at your database where the hashed > >> password is.. > >> > >> So: > >> > >> password_query = SELECT email as user, password, '%w' AS userdb_mail_crypt_private_password FROM > >> virtual_users WHERE email='%u' > >> > >> Aki > >> > >> Hi Aki, > >> > >> Thank you very much for your help, i realy appreciate that. > >> > >> Ok so if i understand it correctly i'll have to use: > >> > >> password_query = SELECT email as user, password, '%w' AS userdb_mail_crypt_private_password FROM > >> virtual_users WHERE email='%u' > >> > >> in my dovecot-sql.conf.ext file > >> > >> This query selects the user, the password, and %w > >> > >> if i run a little query myself: > >> MariaDB [mailserver]> SELECT email as user, password, '%w' AS userdb_mail_crypt_private_password > >> FROM virtual_users; > >> +------------------+----------------------------------+------------------------------------+ > >> | user | password | userdb_mail_crypt_private_password | > >> +------------------+----------------------------------+------------------------------------+ > >> | john(a)example.org | {SHA256-CRYPT}$5$M/GWzmtjsLroRWI | %w | > >> +------------------+----------------------------------+------------------------------------+ > >> > >> %w is a dovecot variable, and stands for the plaintext password, but the password is not stored as > >> plaintext in the DB, %w get filled with the actual plaintext password by dovecot upon the user that > >> is typing in the password when authenticating. > >> > >> is this correct? > > > > yes. > > > >> so then i have the username the hashed password en the plaintext password as a result of the query. > > > > yes > > > >> now userdb_mail_crypt_private_password = the plaintext password > >> do i need to reference it somewhere? or is userdb_mail_crypt_private_password autmatically used by > >> the dovecot mail_crypt plugin to encrypt the keys? or should it be mail_crypt_private_password? > > > > It gets injected into the mail process as 'mail_crypt_private_password', as if it was set in plugin > > {} section. > > > >> if i have this setup working i'm going to write a blog post on this topic to share this knowledge > >> > >> Thanks again and have a great weekend. > >> > >> Zjemm > > > > Aki > > Hi Aki, > > Cool i'm testing it right now. > I have set up a new mailserver (life is great with lxc containers :) ) > > postfix and dovecot are working like normal > > next i enable mail_crypt > > i did create a file: /etc/dovecot/conf.d/10-mailcrypt.conf > ========================== > mail_attribute_dict = file:%h/Maildir/dovecot-attributes > > mail_plugins = $mail_plugins mail_crypt > > plugin { > mail_crypt_curve = secp521r1 > mail_crypt_save_version = 2 > } > ========================== > > and then i changed the file: /etc/dovecot/dovecot-sql.conf.ext > > so the query is now the new query: > password_query = SELECT email as user, password, '%w' AS userdb_mail_crypt_private_password FROM virtual_users WHERE email='%u'; > > then i restarted dovecot and postfix and send a test email to the one and only testuser that is in there. > > when i open the mailbox with the tool mutt, i can see the new email, and when openening the email the mutt client drops the connection. > > in the log i can see: > > May 19 13:34:48 mailserver1.example.local dovecot[600]: imap-login: Login: user=<john(a)example.org>, method=PLAIN, rip=::1, lip=::1, mpid=713, TLS, session=<E3PnIY9sNM4AAAAAAAAAAAAAAAAAAAAB> > May 19 13:34:49 mailserver1.example.local dovecot[600]: imap(john(a)example.org): Error: read() failed: read(/var/vmail/example.org/john/Maildir/cur/1526736378.M161472P641.mailser… failed: Private key not available: Cannot decrypt key bfc5bb25b1bf64290eea6dc14b516c6a0a25b64551b6e4f0f8677ba7274887cb: error:03070068:bignum routines:BN_mpi2bn:encoding error (FETCH BODY[] for mailbox INBOX UID 8) > > > i think i missed a step, but witch one? > > the userpassword hasnt been changed (that would be the next step in the testing process) > > should i've use doveadm first to encrypt the key with that userpassword? i thought it would do that on the fly, because the initial keys where only just created when enabling the mail_crypt plugin > > please let me know your thougts > Zjemm I noticed you replied directly to me, and not to the list, too... fixed that for you. mail_crypt_private_password is used when key is created, but if you have created it before using password, you'll need to encrypt it before turning the setting on. Aki

1 0

Disconnecting unauthenticated IMAP entities faster?
by David Hubbard 20 May '18

20 May '18

Hello, given the 2015 revision date, I was curious if anyone can confirm https://wiki2.dovecot.org/Timeouts is still accurate where the 'before login' IMAP timeout remains hard coded? We're having an issue where blocks of IP's from China and similar locations are crawling IP ranges trying common login credentials, and hanging the connections open in the process. We have clients who have large numbers of employees at single locations, so it isn't possible to reduce the mail_max_userip_connections (assuming it even applies to pre-auth sessions) to a low value. The end result is these connections chew up all the imap-login processes because they sit there until the three-minute timeout is hit, blocking legit users. The only workaround is to raise both the imap and imap-login processes to a massive amount to support all the pre-auth hung open connections. It would be a lot easier to find a reasonable process limit if we could boot these unauthenticated connections off in a more reasonable amount of time, like 5-10 seconds, but I'm not seeing a way to accomplish that? Thanks

3 2

indexer-worker issues on dovecot 2.3.0
by Ricardo Machini Barbosa 18 May '18

18 May '18

Hello, I have some mailbox with error on index-worker process on dovecot 2.3.0 If I move the same mailbox to dovecot 2.2.33.2 this problem dos not happen. See below the backtrace: May 18 10:33:55 Error: imap(xxxxx)<249924><Xpj77npscpYKAQMQ>: indexer failed to index mailbox INBOX May 18 10:33:55 Fatal: indexer-worker(xxxxx)<281701><Xpj77npscpYKAQMQ:UK9sNELW/lplTAQAF3haWw>: master: service(indexer-worker): child 281701 killed with signal 6 (core dumps disabled) May 18 10:34:55 Panic: indexer-worker(xxxxx)<307016><Xpj77npscpYKAQMQ:oEUqNn7W/lpIrwQAF3haWw>: file unichar.c: line 160 (uni_ucs4_to_utf8_c): assertion failed: (uni_is_valid_ucs4(chr)) May 18 10:34:55 Error: indexer-worker(xxxxxxxx)<307016><Xpj77npscpYKAQMQ:oEUqNn7W/lpIrwQAF3haWw>: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(+0xc9804) [0x7f157c8eb804] -> /usr/lib64/dovecot/libdovecot.so.0(+0xc98be) [0x7f157c8eb8be] -> /usr/lib64/dovecot/libdovecot.so.0(i_fatal+0) [0x7f157c85e34b] -> /usr/lib64/dovecot/libdovecot.so.0(uni_ucs4_to_utf8_c+0xc0) [0x7f157c9220b0] -> /usr/lib64/dovecot/libdovecot.so.0(+0xaadc9) [0x7f157c8ccdc9] -> /usr/lib64/dovecot/libdovecot.so.0(mail_html2text_more+0xc5) [0x7f157c8ccf85] -> /usr/lib64/dovecot/lib20_fts_plugin.so(+0xc563) [0x7f157be14563] -> /usr/lib64/dovecot/lib20_fts_plugin.so(fts_parser_more+0x27) [0x7f157be14307] -> /usr/lib64/dovecot/lib20_fts_plugin.so(fts_build_mail+0x440) [0x7f157be121a0] -> /usr/lib64/dovecot/lib20_fts_plugin.so(+0x10266) [0x7f157be18266] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_precache+0x2e) [0x7f157cbd56ae] -> dovecot/indexer-worker [rogerio(a)alfacorcorretora.com.br INBOX - 200/734](+0x2794) [0x55bff457f794] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_call_io+0x65) [0x7f157c902df5] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x10f) [0x7f157c90469f] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run+0x52) [0x7f157c902ef2] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7f157c903118] -> /usr/lib64/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f157c880ce3] -> dovecot/indexer-worker [rogerio(a)alfacorcorretora.com.br INBOX - 200/734](main+0xdb) [0x55bff457f18b] -> /lib64/libc.so.6(__libc_start_main+0xf5) [0x7f157c480c05] -> dovecot/indexer-worker [rogerio(a)alfacorcorretora.com.br INBOX - 200/734](+0x2252) [0x55bff457f252] May 18 10:34:55 Error: indexer: Indexer worker disconnected, discarding 1 requests for xxxxxx May 18 10:34:55 Error: imap(xxxxx)<249924><Xpj77npscpYKAQMQ>: indexer failed to index mailbox INBOX May 18 10:34:55 Fatal: indexer-worker(xxxxx)<307016><Xpj77npscpYKAQMQ:oEUqNn7W/lpIrwQAF3haWw>: master: service(indexer-worker): child 307016 killed with signal 6 (core dumps disabled) uname -a Linux mailsrv01 2.6.32-696.23.1.el6.x86_64 #1 SMP Tue Mar 13 22:44:18 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux dovecot --version 2.3.0.1 (ffd8a29) dovecot -n # 2.3.0.1 (ffd8a29): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.devel (61b47828) # OS: Linux 2.6.32-696.23.1.el6.x86_64 x86_64 CentOS release 6.9 (Final) # Hostname: mailsrv01 auth_master_user_separator = * auth_verbose_passwords = sha1 default_client_limit = 2000 deliver_log_format = subject=%s from:%f sender:%e to: %{to_envelope} size:%p msgid=%m status=%$ delivery_time=%{delivery_time} session_time=%{session_time} disable_plaintext_auth = no doveadm_allowed_commands = quota get,dsync-server,kick,purge,fts rescan,altmove,mailbox list,expunge,mailbox status doveadm_password = # hidden, use -P to show it lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes lmtp_rcpt_check_quota = yes login_greeting = IMAP4. login_trusted_networks = x.x.x.x/24 mail_fsync = never mail_gid = xxx mail_location = mdbox:~/mdbox:ALT=/altstorage%h/mdbox mail_plugins = quota quota_clone fts fts_solr zlib mail_uid = xxx 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 duplicate vnd.dovecot .filter namespace inbox { inbox = yes list = yes location = mailbox "Itens Enviados" { auto = subscribe special_use = \Sent } mailbox "Itens Excluídos" { auto = subscribe special_use = \Trash } mailbox Rascunhos { auto = subscribe special_use = \Drafts } mailbox Spam { auto = subscribe special_use = \Junk } prefix = separator = . } passdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } plugin { fts = solr fts_solr = url=http://x.x.x.x:8983/solr/dovecot/ imapsieve_mailbox1_before = file:/etc/dovecot/antispam/report-spam.sieve imapsieve_mailbox1_causes = COPY imapsieve_mailbox1_name = Spam imapsieve_mailbox2_before = file:/etc/dovecot/antispam/report-ham.sieve imapsieve_mailbox2_causes = COPY imapsieve_mailbox2_from = Spam imapsieve_mailbox2_name = * last_login_dict = redis:host=x.x.x.x:port=6379 quota = count:User quota quota_clone_dict = redis:host=x.x.x.x:port=6379 quota_rule = *:bytes=0 quota_rule2 = Itens Excluídos:storage=+xM quota_vsizes = yes quota_warning = storage=95%% quota-warning 95 %u quota_warning2 = storage=80%% quota-warning 80 %u sieve = ~/.dovecot.sieve sieve_before = /etc/dovecot/sieve/audit.sieve sieve_before2 = /etc/dovecot/sieve/duplicate.sieve sieve_before3 = /etc/dovecot/sieve/spam.sieve sieve_dir = ~/sieve sieve_global_extensions = +vnd.dovecot.pipe sieve_pipe_bin_dir = /etc/dovecot/antispam sieve_plugins = sieve_imapsieve sieve_extprograms sieve_vacation_default_period = 7d sieve_vacation_max_period = 30d sieve_vacation_min_period = 1h } protocols = imap pop3 lmtp sieve service anvil { client_limit = 2000 } service auth { client_limit = 2000 } service doveadm { inet_listener { port = 9011 } inet_listener http { port = 9010 } vsz_limit = 768 M } service imap-login { process_limit = 800 process_min_avail = 200 service_count = 1 vsz_limit = 512 M } service imap-postlogin { executable = script-login dovecot-postlogin imap unix_listener imap-postlogin { user = mail } user = $default_internal_user } service imap { executable = imap imap-postlogin process_limit = 20000 vsz_limit = 768 M } service indexer-worker { vsz_limit = 512 M } service lmtp { inet_listener lmtp { address = * port = 24 } vsz_limit = 512 M } service managesieve-login { inet_listener sieve { port = 4190 } process_min_avail = 10 } service managesieve { process_limit = 512 } service pop3-postlogin { executable = script-login dovecot-postlogin pop3 unix_listener pop3-postlogin { user = mail } user = $default_internal_user } service pop3 { executable = pop3 pop3-postlogin } service quota-warning { executable = script quota-warning unix_listener quota-warning { user = mail } } service stats { chroot = empty client_limit = 20000 drop_priv_before_exec = no executable = stats extra_groups = group = idle_kill = 4294967295 secs privileged_group = process_limit = 1 process_min_avail = 0 protocol = service_count = 0 type = unix_listener stats-reader { group = mode = 0600 user = } unix_listener stats-writer { group = mode = 0600 user = } user = $default_internal_user vsz_limit = 18446744073709551615 B } ssl = no submission_host = x.x.x.x userdb { driver = prefetch } userdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } verbose_proctitle = yes protocol lda { mail_fsync = optimized mail_plugins = quota quota_clone sieve } protocol imap { imap_max_line_length = 128 k mail_max_userip_connections = 30 mail_plugins = quota quota_clone fts fts_solr zlib imap_quota last_login imap_sieve } protocol lmtp { mail_fsync = optimized mail_plugins = quota quota_clone sieve } protocol pop3 { mail_max_userip_connections = 10 mail_plugins = quota quota_clone fts fts_solr zlib last_login pop3_logout_format = in=%i out=%o top=%t/%p, retr=%r/%b, del=%d/%m, size=%s pop3_no_flag_updates = yes pop3_save_uidl = yes pop3_uidl_format = %08Xu%08Xv } Regards, Ricardo

2 1

vacation stumbles over invalid headers
by Militades Sunfire 18 May '18

18 May '18

# 2.2.13: /etc/dovecot/dovecot.conf # OS: Linux 3.16.0-4-amd64 x86_64 Debian 8.10 the vacation feature stumbles over invalid headers in several cases, causing an even more invalid header f.ex. if the original mail contains a line with only spaces in the vacation reply the header breaks apart displying not only the inteded vacation message but also parts of the message header. depends a bit on the client what happends of course, thunderbird and the mac client are two examples. Greetings

1 0

Decryption method for Maildir messages stored by mail_crypt plugin
by Ben Harrison 17 May '18

17 May '18

I've successfully implemented the mail_crypt plugin on v2.2.27 and it's working like a champ, but some of our administrative operations require access to Maildir messages in plaintext. I've found numerous threads detailing help with mail_crypt setup, but none of my research has yielded a method of decrypting the stored messages. Relevant plugin config: mail_crypt_curve = prime256v1 mail_crypt_global_private_key = <pirvkey> mail_crypt_global_public_key = <pubkey> mail_crypt_save_version = 2 Method I attempted for manual decryption is listed below: openssl pkeyutl -derive -inkey mailcrypt.key -peerkey mailcrypt.pub -out shared_secret.bin openssl enc -aes256 -base64 -k $(base64 shared_secret.bin) -d -in test.enc -out test.txt Openssl reports an error reading the input file, but it isn't permissions related. I started looking for the encryption/decryption method in the source but figure it's worth seeing if there's some existing methodology I can employ here. Appreciate any feedback. Thanks, -- -- -- *Ben Harrison* *BHarrison.IT*843.492.4870

2 1

External Program for Authentication?
by Marc Perkel 17 May '18

17 May '18

Is it possible to run a bash script for authentication where a 0 exit code indicates success and a non-zero is failure? What I'm trying to do is create a shadow IMAP server that authenticates against a different server. That way my server will use the same passwords as an existing server. So what I would need is for dovecot to pass the username and password to my script, I attempt to log in remotely and if I succeed I allow access on my side. My side will be used to configure black lists and where spam is dragged from their side to my side. (I'm a spam filtering company)

4 3

Maillog warning
by forums＠mehl-family.fr 16 May '18

16 May '18

Hi, In my maillog I see this warning message at every reception of e-mail: _STATUS=SENT (DELIVERED VIA DOVECOT SERVICE (DOVECONF: WARNING: /ETC/DOVECOT/CONF.D/90-QUOTA.CONF LINE 39: GLOBAL SETTING MAIL_PLUGINS WON'T CHAN....._ It is just a warning, the e-mail was delivered. I don't find where is the problem. Thank's. -- ########## Philippe - Forums

3 10

dovecot + cephfs - sdbox vs mdbox
by Webert de Souza Lima 16 May '18

16 May '18

I'm sending this message to both dovecot and ceph-users ML so please don't mind if something seems too obvious for you. Hi, I have a question for both dovecot and ceph lists and below I'll explain what's going on. Regarding dbox format (https://wiki2.dovecot.org/MailboxFormat/dbox) when using sdbox, a new file is stored for each email message. When using mdbox, multiple messages are appended to a single file until it reaches/passes the rotate limit. I would like to understand better how the mdbox format impacts on IO performance. I think it's generally expected that fewer larger file translate to less IO and more troughput when compared to more small files, but how does dovecot handle that with mdbox? If dovecot does flush data to storage upon each and every new email is arrived and appended to the corresponding file, would that mean that it generate the same ammount of IO as it would do with one file per message? Also, if using mdbox many messages will be appended to a said file before a new file is created. That should mean that a file descriptor is kept open for sometime by dovecot process. Using cephfs as backend, how would this impact cluster performance regarding MDS caps and inodes cached when files from thousands of users are opened and appended all over? I would like to understand this better. Why? We are a small Business Email Hosting provider with bare metal, self hosted systems, using dovecot for servicing mailboxes and cephfs for email storage. We are currently working on dovecot and storage redesign to be in production ASAP. The main objective is to serve more users with better performance, high availability and scalability. * high availability and load balancing is extremely important to us * On our current model, we're using mdbox format with dovecot, having dovecot's INDEXes stored in a replicated pool of SSDs, and messages stored in a replicated pool of HDDs (under a Cache Tier with a pool of SSDs). All using cephfs / filestore backend. Currently there are 3 clusters running dovecot 2.2.34 and ceph Jewel (10.2.9-4). - ~25K users from a few thousands of domains per cluster - ~25TB of email data per cluster - ~70GB of dovecot INDEX [meta]data per cluster - ~100MB of cephfs metadata per cluster Our goal is to build a single ceph cluster for storage that could expand in capacity, be highly available and perform well enough. I know, that's what everyone wants. Cephfs is an important choise because: - there can be multiple mountpoints, thus multiple dovecot instances on different hosts - the same storage backend is used for all dovecot instances - no need of sharding domains - dovecot is easily load balanced (with director sticking users to the same dovecot backend) On the upcoming upgrade we intent to: - upgrade ceph to 12.X (Luminous) - drop the SSD Cache Tier (because it's deprecated) - use bluestore engine I was said on freenode/#dovecot that there are many cases where SDBOX would perform better with NFS sharing. In case of cephfs, at first, I wouldn't think that would be true because more files == more generated IO, but thinking about what I said in the beginning regarding sdbox vs mdbox that could be wrong. Any thoughts will be highlt appreciated. Regards, Webert Lima DevOps Engineer at MAV Tecnologia *Belo Horizonte - Brasil* *IRC NICK - WebertRLZ*

2 2

Re: [ceph-users] dovecot + cephfs - sdbox vs mdbox
by Webert de Souza Lima 16 May '18

16 May '18

Hello Jack, yes, I imagine I'll have to do some work on tuning the block size on cephfs. Thanks for the advise. I knew that using mdbox, messages are not removed but I though that was true in sdbox too. Thanks again. We'll soon do benchmarks of sdbox vs mdbox over cephfs with bluestore backend. We'll have to do some some work on how to simulate user traffic, for writes and readings. That seems troublesome. Thanks for the plugins recommendations. I'll take the change and ask you how is the SIS status? We have used it in the past and we've had some problems with it. Regards, Webert Lima DevOps Engineer at MAV Tecnologia *Belo Horizonte - Brasil* *IRC NICK - WebertRLZ* On Wed, May 16, 2018 at 4:19 PM Jack <ceph(a)jack.fr.eu.org> wrote: > Hi, > > Many (most ?) filesystems does not store multiple files on the same block > > Thus, with sdbox, every single mail (you know, that kind of mail with 10 > lines in it) will eat an inode, and a block (4k here) > mdbox is more compact on this way > > Another difference: sdbox removes the message, mdbox does not : a single > metadata update is performed, which may be packed with others if many > files are deleted at once > > That said, I do not have experience with dovecot + cephfs, nor have made > tests for sdbox vs mdbox > > However, and this is a bit out of topic, I recommend you look at the > following dovecot's features (if not already done), as they are awesome > and will help you a lot: > - Compression (classic, https://wiki.dovecot.org/Plugins/Zlib) > - Single-Instance-Storage (aka sis, aka "attachment deduplication" : > https://www.dovecot.org/list/dovecot/2013-December/094276.html) > > Regards, > On 05/16/2018 08:37 PM, Webert de Souza Lima wrote: > > I'm sending this message to both dovecot and ceph-users ML so please > don't > > mind if something seems too obvious for you. > > > > Hi, > > > > I have a question for both dovecot and ceph lists and below I'll explain > > what's going on. > > > > Regarding dbox format (https://wiki2.dovecot.org/MailboxFormat/dbox) > when > > using sdbox, a new file is stored for each email message. > > When using mdbox, multiple messages are appended to a single file until > it > > reaches/passes the rotate limit. > > > > I would like to understand better how the mdbox format impacts on IO > > performance. > > I think it's generally expected that fewer larger file translate to less > IO > > and more troughput when compared to more small files, but how does > dovecot > > handle that with mdbox? > > If dovecot does flush data to storage upon each and every new email is > > arrived and appended to the corresponding file, would that mean that it > > generate the same ammount of IO as it would do with one file per message? > > Also, if using mdbox many messages will be appended to a said file > before a > > new file is created. That should mean that a file descriptor is kept open > > for sometime by dovecot process. > > Using cephfs as backend, how would this impact cluster performance > > regarding MDS caps and inodes cached when files from thousands of users > are > > opened and appended all over? > > > > I would like to understand this better. > > > > Why? > > We are a small Business Email Hosting provider with bare metal, self > hosted > > systems, using dovecot for servicing mailboxes and cephfs for email > storage. > > > > We are currently working on dovecot and storage redesign to be in > > production ASAP. The main objective is to serve more users with better > > performance, high availability and scalability. > > * high availability and load balancing is extremely important to us * > > > > On our current model, we're using mdbox format with dovecot, having > > dovecot's INDEXes stored in a replicated pool of SSDs, and messages > stored > > in a replicated pool of HDDs (under a Cache Tier with a pool of SSDs). > > All using cephfs / filestore backend. > > > > Currently there are 3 clusters running dovecot 2.2.34 and ceph Jewel > > (10.2.9-4). > > - ~25K users from a few thousands of domains per cluster > > - ~25TB of email data per cluster > > - ~70GB of dovecot INDEX [meta]data per cluster > > - ~100MB of cephfs metadata per cluster > > > > Our goal is to build a single ceph cluster for storage that could expand > in > > capacity, be highly available and perform well enough. I know, that's > what > > everyone wants. > > > > Cephfs is an important choise because: > > - there can be multiple mountpoints, thus multiple dovecot instances on > > different hosts > > - the same storage backend is used for all dovecot instances > > - no need of sharding domains > > - dovecot is easily load balanced (with director sticking users to the > > same dovecot backend) > > > > On the upcoming upgrade we intent to: > > - upgrade ceph to 12.X (Luminous) > > - drop the SSD Cache Tier (because it's deprecated) > > - use bluestore engine > > > > I was said on freenode/#dovecot that there are many cases where SDBOX > would > > perform better with NFS sharing. > > In case of cephfs, at first, I wouldn't think that would be true because > > more files == more generated IO, but thinking about what I said in the > > beginning regarding sdbox vs mdbox that could be wrong. > > > > Any thoughts will be highlt appreciated. > > > > Regards, > > > > Webert Lima > > DevOps Engineer at MAV Tecnologia > > *Belo Horizonte - Brasil* > > *IRC NICK - WebertRLZ* > > > > > > > > _______________________________________________ > > ceph-users mailing list > > ceph-users(a)lists.ceph.com > > http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com > > > > _______________________________________________ > ceph-users mailing list > ceph-users(a)lists.ceph.com > http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com >

1 0

2.3.1 with quota and lmtp; message may be sent more than once
by Frank Ebert 16 May '18

16 May '18

Hi, I have another problem with dovecot 2.3.1 on FreeBSD (smtpd is postfix 3.3.0). When one mail is sent with different recipients and the quota limit of one user is exceeded, the message will be delivered repeatedly to all users. The queue from postfix says: (lost connection with mailserver.foo.bar[private/lmtp-dovecot] while sending end of data -- message may be sent more than once) The problem started with dovecot 2.3.1. With 2.2.3x everything was fine. Any ideas? Thanx Frank doveconf -n: auth_mechanisms = plain login auth_use_winbind = yes auth_winbind_helper_path = /usr/local/bin/ntlm_auth disable_plaintext_auth = no info_log_path = /var/log/dovecot listen = * mail_location = mdbox:~/mdbox mail_plugins = zlib quota acl mail_log notify managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacati on subaddress comparator-i;ascii-numeric relational regex imap4flags copy includ e variables body enotify environment mailbox date index ihave duplicate mime for everypart extracttext namespace { location = mdbox:/home/vmail/foo.domain/foo/mdbox prefix = Foo/ separator = / subscriptions = yes type = public } namespace { location = mdbox:/home/vmail/bar.domain/bar/mdbox prefix = Bar/ separator = / subscriptions = yes type = public } namespace { location = mdbox:/home/vmail/foobar.domain/foobar/mdbox prefix = Foobar/ separator = / subscriptions = yes type = public } namespace inbox { inbox = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { auto = subscribe special_use = \Trash } prefix = INBOX/ separator = / } passdb { args = /usr/local/etc/dovecot/dovecot-ldap.conf.ext driver = ldap } plugin { acl = vfile:/usr/local/etc/dovecot/global-acls acl_shared_dict = file:/var/lib/dovecot/shared-mailboxes mail_log_events = flag_change delete undelete expunge copy mailbox_delete mail box_rename mail_log_fields = uid box msgid size flags quota = dict:User quota::file:%h/dovecot-quota quota_warning = storage=95%% quota-warning 95 %u quota_warning2 = storage=80%% quota-warning 80 %u sieve = ~/.dovecot.sieve sieve_dir = ~/sieve stats_command_min_time = 1 mins stats_domain_min_time = 12 hours stats_ip_min_time = 12 hours stats_memory_limit = 16 M stats_refresh = 30 stats_session_min_time = 15 mins stats_track_cmds = yes stats_user_min_time = 1 hours zlib_save = gz zlib_save_level = 6 } postmaster_address = postmaster(a)foo.bar protocols = imap lmtp sieve service auth { unix_listener /var/spool/postfix/private/auth { mode = 0666 } unix_listener auth-userdb { group = vmail user = vmail } } service lmtp { unix_listener /var/spool/postfix/private/lmtp-dovecot { group = postfix user = postfix } } service managesieve-login { inet_listener sieve { port = 4190 } process_min_avail = 0 service_count = 0 } service managesieve { process_limit = 1024 } service quota-warning { executable = script /usr/local/bin/quota-warning.sh unix_listener quota-warning { user = vmail } user = vmail } service stats { fifo_listener stats-mail { mode = 0600 user = vmail } } ssl_cert = </etc/ssl/certs/dovecot.pem ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it userdb { driver = prefetch } userdb { args = /usr/local/etc/dovecot/dovecot-ldap-userdb.conf.ext driver = ldap } protocol lmtp { mail_plugins = zlib quota acl mail_log notify sieve } protocol lda { mail_plugins = zlib quota acl mail_log notify sieve } protocol imap { mail_plugins = zlib quota acl mail_log notify imap_zlib imap_quota imap_acl }

3 6

dovecot 2.3 on Ubuntu 18.04 LTS
by Jean-Daniel Dupas 16 May '18

16 May '18

Hello, I'm running dovecot 2.3 from repo.dovecot.org <http://repo.dovecot.org/> on ubuntu 16.04 LTS, and I'm wondering if there is a scheduled date for the release of the bionic package in that repository. The Ubuntu mainstream version is based on the 2.2 branch, which prevent us to use it. Thanks.

1 0

end-to-end encryption
by Gandalf Corvotempesta 16 May '18

16 May '18

Hi to all I was looking at protonmail.com Is possible to implement and end-to-end encryption with dovecot, where server-side there is no private key to decrypt messages? If I understood properly, on protonmail the private key is encrypted with user's password, so that only an user is able to decrypt the mailbox. Anything similiar ?

5 10

Postfix/Dovecot permissions for new mailboxes
by telsch 16 May '18

16 May '18

Hello, the wiki page describe that permission should copied from root mail directory https://wiki2.dovecot.org/SharedMailboxes/Permissions The permissions for the root mail directory are set to 2770: drwxrws--- 36 root mail 4096 Apr 15 02:30 /var/spool/mail/ But newly created mailboxes get following permissions: drwx--S--- 5 newuser mail 4096 Apr 23 19:31 /var/spool/mail/newuser/ In /etc/dovecot/conf.d/10-mail.conf follow options are set: mail_gid = mail mail_privileged_group = mail mail_access_groups = mail I'm missing something to get right group permissions for new mailboxes?

2 9

sieve trace directory: error
by André Rodier 15 May '18

15 May '18

Hello, I am using a custom directory for sieve logs and trace and it apparently generate an error, in some corner case. - I have an IMAP global sieve script, that is run when appending emails into the "Archives" folder. - I have Thunderbird configured to archive emails by year When archiving an email, for instance in "Archives/2018", I often have an error message like this: Mar 31 08:03:02 homebox dovecot[14078]: imap(andre): Error: sieve: trace: creat(/home/users/andre/mails/sieve/logs//andre.Archives/2018.3.20180331-080302.14235.5.trace) failed: No such file or directory I have this configuration (amongst) for sieve logs: sieve_user_log = ~/mails/sieve/logs/ sieve_trace_dir = ~/mails/sieve/logs/ sieve_trace_level = commands sieve_trace_debug = yes sieve_trace_addresses = yes Did I a misconfigured something? Thanks for your help, André -- https://github.com/progmaticltd/homebox

3 5

dsync migration from maildir layout=fs to maildir seperator / - folders or inbox but not both
by Matt Bryant 13 May '18

13 May '18

Am attempting to bring my mailserver back to home server post house move and whilst I could use rsync have been trying to get to grips with dsync. However, I seem to have an issue - my current server specifies mail_location as maildir:/var/vmail/%d/%n/Maildir:LAYOUT=fs and my imapc config on new server is as follows ... imapc_host = old.mailserver.host imapc_user = %u imapc_master_user = master imapc_password = ********** imapc_features = $imapc_features rfc822.size fetch-headers imapc_list_prefix = INBOX imapc_port = 993 imapc_ssl = imaps imapc_ssl_verify = no the trouble is if I leave imapc_list_prefix = INBOX I get the inbox only - no folders ... If I comment this out delete maildir on target and re-run .. I get the folders but no inbox but folders are in fs layout format rather than being converted to INBOX.folder.subfolder bug perhaps ???? or am I doing something wrong ??? src dovecot version 2.0.9 tgt dovecot version 2.2.33.2 Any ideas would be appreciated ... rgds Matt -- <https://www.postbox-inc.com/?utm_source=email&utm_medium=siglink&utm_campai…>

2 3

Marks as read on mover to Archive
by ＠lbutlr 13 May '18

13 May '18

How would I setup dovecot so that when messages are moved to the Archive mailbox, they are marked as read? Would it be similar to the imap-sieve for spam tagging? imapsieve_mailbox1_name = Junk imapsieve_mailbox1_causes = COPY imapsieve_mailbox1_before = file:/usr/lib/dovecot/sieve/report-spam.sieve Or is there a simpler method? If it matters: mailbox Archive { auto = subscribe special_use = \Archive -- According to the philosopher Ly Tin Weedle, chaos is found in greatest abundance wherever order is being sought. It always defeats order, because it is better organized.

3 3

lmtp panic with many recipients
by Olaf Hopp 12 May '18

12 May '18

Hi, I had an email with 58 recipients in the "To" and 13 in the "CC" Delivering it from exim to dovecot lmtp panics (see below) Panic: file smtp-address.c: line 533 (smtp_address_write): assertion failed: (smtp_char_is_qpair(*p)) # 2.3.1 (c5a5c0c82): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.devel (61b47828) # OS: Linux 2.6.32-696.23.1.el6.x86_64 x86_64 CentOS release 6.9 (Final) Regards, Olaf May 8 10:01:52 irams2 dovecot: lmtp(17557): Debug: none: root=, index=, indexpvt=, control=, inbox=, alt= May 8 10:01:52 irams2 dovecot: lmtp(17557): Connect from local May 8 10:01:52 irams2 dovecot: lmtp(ms2test(a)irams2.ira.uka.de)<17557><30+oHXBZ8VqVRAAApw0JKA>: Debug: Loading modules from directory: /usr/lib64/dovecot May 8 10:01:52 irams2 dovecot: lmtp(ms2test(a)irams2.ira.uka.de)<17557><30+oHXBZ8VqVRAAApw0JKA>: Debug: Module loaded: /usr/lib64/dovecot/lib90_sieve_plugin.so May 8 10:01:52 irams2 dovecot: lmtp(ms2test(a)irams2.ira.uka.de)<17557><30+oHXBZ8VqVRAAApw0JKA>: Debug: auth USER input: ms2test system_groups_user=ms2test uid=10852 gid=1602 home=/home/atis/ms2test May 8 10:01:52 irams2 dovecot: lmtp(ms2test(a)irams2.ira.uka.de)<17557><30+oHXBZ8VqVRAAApw0JKA>: Debug: changed username to ms2test May 8 10:01:52 irams2 dovecot: lmtp(17557, ms2test): Debug: Effective uid=10852, gid=1602, home=/home/atis/ms2test May 8 10:01:52 irams2 dovecot: lmtp(17557, ms2test): Debug: Namespace inbox: type=private, prefix=INBOX., sep=., inbox=yes, hidden=no, list=yes, subscriptions=yes location=maildir:~/Maildir May 8 10:01:52 irams2 dovecot: lmtp(17557, ms2test): Debug: maildir++: root=/home/atis/ms2test/Maildir, index=, indexpvt=, control=, inbox=/home/atis/ms2test/Maildir, alt= May 8 10:01:52 irams2 dovecot: lmtp(17557, ms2test): Debug: Namespace : type=private, prefix=, sep=, inbox=no, hidden=yes, list=no, subscriptions=no location=fail::LAYOUT=none May 8 10:01:52 irams2 dovecot: lmtp(17557, ms2test): Debug: none: root=, index=, indexpvt=, control=, inbox=, alt= May 8 10:01:52 irams2 dovecot: lmtp(ms2test)<17557><30+oHXBZ8VqVRAAApw0JKA>: Debug: sieve: Pigeonhole version 0.5.devel (61b47828) initializing May 8 10:01:52 irams2 dovecot: lmtp(ms2test)<17557><30+oHXBZ8VqVRAAApw0JKA>: Debug: sieve: include: sieve_global is not set; it is currently not possible to include `:global' scripts. May 8 10:01:52 irams2 dovecot: lmtp(ms2test)<17557><30+oHXBZ8VqVRAAApw0JKA>: Debug: sieve: file storage: Using active Sieve script path: /home/atis/ms2test/.dovecot.sieve May 8 10:01:52 irams2 dovecot: lmtp(ms2test)<17557><30+oHXBZ8VqVRAAApw0JKA>: Debug: sieve: file storage: Using script storage path: /home/atis/ms2test/sieve May 8 10:01:52 irams2 dovecot: lmtp(ms2test)<17557><30+oHXBZ8VqVRAAApw0JKA>: Debug: sieve: file storage: Relative path to sieve storage in active link: sieve/ May 8 10:01:52 irams2 dovecot: lmtp(ms2test)<17557><30+oHXBZ8VqVRAAApw0JKA>: Debug: sieve: file storage: Using Sieve script path: /home/atis/ms2test/.dovecot.sieve May 8 10:01:52 irams2 dovecot: lmtp(ms2test)<17557><30+oHXBZ8VqVRAAApw0JKA>: Debug: sieve: file script: Opened script `ingo' from `/home/atis/ms2test/.dovecot.sieve' May 8 10:01:52 irams2 dovecot: lmtp(ms2test)<17557><30+oHXBZ8VqVRAAApw0JKA>: Debug: sieve: file storage: Using Sieve script path: /etc/dovecot/sieve-master May 8 10:01:52 irams2 dovecot: lmtp(ms2test)<17557><30+oHXBZ8VqVRAAApw0JKA>: Debug: sieve: file script: Opened script `sieve-master' from `/etc/dovecot/sieve-master' May 8 10:01:52 irams2 dovecot: lmtp(ms2test)<17557><30+oHXBZ8VqVRAAApw0JKA>: Debug: sieve: Executed before user's personal Sieve script(1): /etc/dovecot/sieve-master May 8 10:01:52 irams2 dovecot: lmtp(ms2test)<17557><30+oHXBZ8VqVRAAApw0JKA>: Debug: sieve: Using the following location for user's Sieve script: /home/atis/ms2test/.dovecot.sieve May 8 10:01:52 irams2 dovecot: lmtp(ms2test)<17557><30+oHXBZ8VqVRAAApw0JKA>: Debug: Mailbox <lmtp DATA local>: Opened mail UID=1 because: header Message-ID (Cache file is unusable) May 8 10:01:52 irams2 dovecot: lmtp(ms2test)<17557><30+oHXBZ8VqVRAAApw0JKA>: Debug: sieve: Opening script 1 of 2 from `/etc/dovecot/sieve-master' May 8 10:01:52 irams2 dovecot: lmtp(ms2test)<17557><30+oHXBZ8VqVRAAApw0JKA>: Debug: sieve: Loading script /etc/dovecot/sieve-master May 8 10:01:52 irams2 dovecot: lmtp(ms2test)<17557><30+oHXBZ8VqVRAAApw0JKA>: Debug: sieve: Script binary /etc/dovecot/sieve-master.svbin successfully loaded May 8 10:01:52 irams2 dovecot: lmtp(ms2test)<17557><30+oHXBZ8VqVRAAApw0JKA>: Debug: sieve: binary save: not saving binary /etc/dovecot/sieve-master.svbin, because it is already stored May 8 10:01:52 irams2 dovecot: lmtp(ms2test)<17557><30+oHXBZ8VqVRAAApw0JKA>: Debug: sieve: Executing script from `/etc/dovecot/sieve-master.svbin' May 8 10:01:52 irams2 dovecot: lmtp(ms2test)<17557><30+oHXBZ8VqVRAAApw0JKA>: Debug: Mailbox <lmtp DATA local>: Opened mail UID=1 because: header List-Id (Cache file is unusable) May 8 10:01:52 irams2 dovecot: lmtp(ms2test)<17557><30+oHXBZ8VqVRAAApw0JKA>: Panic: file smtp-address.c: line 533 (smtp_address_write): assertion failed: (smtp_char_is_qpair(*p)) May 8 10:01:52 irams2 dovecot: lmtp(ms2test)<17557><30+oHXBZ8VqVRAAApw0JKA>: Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(+0xca92a) [0x7fd7b6d0a92a] -> /usr/lib64/dovecot/libdovecot.so.0(i_syslog_fatal_handler+0x33) [0x7fd7b6d0b003] -> /usr/lib64/dovecot/libdovecot.so.0(+0x3ce61) [0x7fd7b6c7ce61] -> /usr/lib64/dovecot/libdovecot.so.0(+0x403fb) [0x7fd7b6c803fb] -> /usr/lib64/dovecot/libdovecot.so.0(smtp_address_encode+0x29) [0x7fd7b6c80429] -> /usr/lib64/dovecot/libdovecot-sieve.so.0(+0x46892) [0x7fd7b4146892] -> /usr/lib64/dovecot/libdovecot-sieve.so.0(sieve_match+0xbf) [0x7fd7b41475ff] -> /usr/lib64/dovecot/libdovecot-sieve.so.0(+0x4d9ec) [0x7fd7b414d9ec] -> /usr/lib64/dovecot/libdovecot-sieve.so.0(sieve_interpreter_continue+0x71) [0x7fd7b413c4b1] -> /usr/lib64/dovecot/libdovecot-sieve.so.0(sieve_interpreter_run+0x2b) [0x7fd7b413d07b] -> /usr/lib64/dovecot/libdovecot-sieve.so.0(+0x522fb) [0x7fd7b41522fb] -> /usr/lib64/dovecot/libdovecot-sieve.so.0(sieve_multiscript_run+0x5a) [0x7fd7b415252a] -> /usr/lib64/dovecot/lib90_sieve_plugin.so(+0x36ad) [0x7fd7b43bb6ad] -> /usr/lib64/dovecot/libdovecot-lda.so.0(mail_deliver+0xd2) [0x7fd7b7314942] -> dovecot/lmtp [local DATA](+0x6ffe) [0x7fd7b7756ffe] -> dovecot/lmtp [local DATA](lmtp_local_data+0x156) [0x7fd7b7757466] -> dovecot/lmtp [local DATA](cmd_data_continue+0x218) [0x7fd7b7756088] -> /usr/lib64/dovecot/libdovecot.so.0(+0x4ee3d) [0x7fd7b6c8ee3d] -> /usr/lib64/dovecot/libdovecot.so.0(+0x4f242) [0x7fd7b6c8f242] -> /usr/lib64/dovecot/libdovecot.so.0(+0x4f837) [0x7fd7b6c8f837] -> /usr/lib64/dovecot/libdovecot.so.0(smtp_server_command_next_to_reply+0x3b) [0x7fd7b6c9212b] -> /usr/lib64/dovecot/libdovecot.so.0(+0x55a30) [0x7fd7b6c95a30] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_call_io+0x55) [0x7fd7b6d21785] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run+0x95) [0x7fd7b6d218b5] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7fd7b6d21a98] -> /usr/lib64/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7fd7b6c9f493] -> dovecot/lmtp [loc May 8 10:01:52 irams2 dovecot: lmtp: Fatal: master: service(lmtp): child 17557 killed with signal 6 (core dumps disabled - https://dovecot.org/bugreport.html#coredumps) -- Karlsruher Institut für Technologie (KIT) ATIS - Abt. Technische Infrastruktur, Fakultät für Informatik Dipl.-Geophys. Olaf Hopp - Leitung IT-Dienste - Am Fasanengarten 5, Gebäude 50.34, Raum 009 76131 Karlsruhe Telefon: +49 721 608-43973 Fax: +49 721 608-46699 E-Mail: Olaf.Hopp(a)kit.edu atis.informatik.kit.edu www.kit.edu KIT – Die Forschungsuniversität in der Helmholtz-Gemeinschaft Das KIT ist seit 2010 als familiengerechte Hochschule zertifiziert.

3 8

Dovecot 2.2.36-rc1 and $HasAttachment
by Alessio Cecchi 10 May '18

10 May '18

Hi, I installed dovecot 2.2.36-rc1 and enabled: mail_attachment_detection_options = add-flags-on-save but when messages are delivery via dovecot-lda into mailbox (Maildir) keywords are not added. Only when the messages is open keywords ($HasAttachment or $HasNoAttachment) are added. From the wiki "attachments are detected and marked during save", delivery via LDA is "save"? For info, doveadm rebuild attachments works fine. Since 2.2.36 will be the last v2.2.x release I hope that this feature will be fixed since is very useful. Thanks -- Alessio Cecchi Postmaster @ http://www.qboxmail.it https://www.linkedin.com/in/alessice

2 1

Error compiling with --with-storages=
by Andrea Gabellini 10 May '18

10 May '18

Hello, Usually I compile Dovecot with option --with-storages=maildir Starting with 2.2.30 and up to 2.2.36 RC this option cause the compilation to fail with this error: .libs/quota-imapc.o: In function `imapc_quota_refresh': quota-imapc.c:(.text+0x82d): undefined reference to `imapc_client_get_capabilities' quota-imapc.c:(.text+0x87d): undefined reference to `imapc_simple_context_init' quota-imapc.c:(.text+0x887): undefined reference to `imapc_simple_callback' quota-imapc.c:(.text+0x89d): undefined reference to `imapc_client_cmd' quota-imapc.c:(.text+0x8ba): undefined reference to `imapc_command_sendf' quota-imapc.c:(.text+0x8c2): undefined reference to `imapc_simple_run' quota-imapc.c:(.text+0xa2a): undefined reference to `imapc_storage_client_register_untagged' quota-imapc.c:(.text+0xa4d): undefined reference to `imapc_storage_client_register_untagged' quota-imapc.c:(.text+0xa8e): undefined reference to `imapc_simple_context_init' quota-imapc.c:(.text+0xa98): undefined reference to `imapc_simple_callback' quota-imapc.c:(.text+0xaae): undefined reference to `imapc_client_cmd' quota-imapc.c:(.text+0xacb): undefined reference to `imapc_command_sendf' quota-imapc.c:(.text+0xad3): undefined reference to `imapc_simple_run' collect2: ld returned 1 exit status Compiling without this option or with --with-storages=maildir,imapc works Thanks, Andrea -- ---------------------------------------------------------------- The most likely way for the world to be destroyed, most experts agree, is by accident. That's where we come in; We're computer professionals. We cause accidents. ---------------------------------------------------------------- Ing. Andrea Gabellini Email: andrea.gabellini(a)telecomitalia.sm Skype: andreagabellini Tel: (+378) 0549 886111 Fax: (+378) 0549 886188 Telecom Italia San Marino S.p.A. Via XXVIII Luglio, 212 - Piano -2 47893 Borgo Maggiore Republic of San Marino http://www.telecomitalia.sm

2 2

mmap failed messages in syslog
by Shawn Heisey 10 May '18

10 May '18

I'm getting mmap failed messages in syslog on version 1.2.15 for dovecot.index.cache files. This old dovecot version is installed with debian packages. The OS and all software is 64-bit. I've found info on this log message, with a suggested fix of raising vsz_limit ... but this seems to be a config option for dovecot 2.x, not 1.x. The file it complains about being unable to mmap is only 90MB, and the biggest cache file I have found on the system is only 180MB. The system has 4GB of total memory with about 1GB of that allocated to OS disk cache right now. The mmap functionality provided by the OS doesn't use *actual* memory, so the amount of memory I have should be irrelevant. Checking 'ulimit -a' with several users shows that vmemory is unlimited for all of them. How do I go about allowing docevot 1.x to use more virtual memory? I do have a migration planned to Ubuntu 16, where I can run a 2.x version, but that's not going to happen for a while. Thanks, Shawn

2 3

possible to disable dh_key/ssl-parameters.dat generation when only using ECDHE ciphers.
by Erik de Waard 09 May '18

09 May '18

Hi, I want to disable dh_key/ssl-parameters.dat entirely since i'm only using ECDHE ciphers. > # 2.2.34 (874deae): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.22 (22940fb7) # OS: Linux 4.9.0-6-amd64 x86_64 Debian 9.4 # Hostname: somehost.com 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 = 600 M disable_plaintext_auth = no info_log_path = /var/log/mail.log.info listen = * log_timestamp = "%Y-%m-%d %H:%M:%S " mail_debug = yes mail_max_userip_connections = 100 mail_privileged_group = mail 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 = /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_cert = </etc/dovecot/dovecot.crt ssl_cipher_list = ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA256 ssl_key = # hidden, use -P to show it ssl_prefer_server_ciphers = yes userdb { driver = prefetch } userdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } verbose_proctitle = yes protocol lmtp { 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 = } }

2 1

replicator: User listing returned failure
by Alexey 09 May '18

09 May '18

Hello. I've tried to configure TCP replication to slave server. But I got some errors... mx1:~# dovecot --version 2.2.27 (c0f36b0) From dovecot.log: May 07 19:27:41 auth-worker(34348): Warning: mysql: Query failed, retrying: Unknown column 'username' in 'field list' May 07 19:27:41 auth-worker(34348): Debug: sql(*): SELECT username, domain FROM users May 07 19:27:41 auth-worker(34348): Error: sql: Iterate query failed: Unknown column 'username' in 'field list' (using built-in default iterate_query: SELECT username, domain FROM users) May 07 19:27:41 auth-worker(34348): Debug: sql(*): SELECT id AS username, domain FROM users May 07 19:27:41 replicator: Error: User listing returned failure May 07 19:27:41 replicator: Error: listing users failed, can't replicate existing data mx1:~# doveadm replicator status Queued 'sync' requests 0 Queued 'high' requests 0 Queued 'low' requests 0 Queued 'failed' requests 0 Queued 'full resync' requests 0 Waiting 'failed' requests 2 Total number of known users 2 mx1:~# doveadm replicator status '*' username priority fast sync full sync success sync failed abuse(a)example.com none 00:03:01 01:06:36 - y admin(a)exmaple.com none 00:03:41 01:31:49 - y From slave: mx2:~# cat /etc/dovecot/conf.d/90-replication.conf # use tcp:hostname as the dsync target plugin { mail_replica = tcp:mx1 # use doveadm_port } As I can see nothing happens automatically. But mx2:~# doveadm -D sync -u abuse(a)example.com -d -N -l 30 -U successfully executed and getting mails from mx1. dovecot-sql.conf.ext: driver = mysql connect = host=localhost dbname=vmail user=sqlmail password=sqL_hidden033|TGPAS default_pass_scheme = SHA512-CRYPT password_query = SELECT id AS username, password, domain FROM users WHERE id = '%n' AND domain = '%d' AND active = 'Y' user_query = SELECT id AS username, uid, gid, home, concat('*:storage=', quota, 'M' ) as quota_rule FROM users WHERE id = '%n' AND domain = '%d' iterate_query = SELECT id AS username, domain FROM users Regards, Alexey mx1:~# dovecot -n # 2.2.27 (c0f36b0): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.16 (fed8554) # OS: Linux 4.9.0-6-amd64 x86_64 Debian 9.4 auth_master_user_separator = * auth_verbose = yes auth_verbose_passwords = sha1 default_vsz_limit = 512 M doveadm_password = # hidden, use -P to show it doveadm_port = 994 hostname = mx1.example.com imap_client_workarounds = delay-newmail tb-extra-mailbox-sep tb-lsub-flags imap_idle_notify_interval = 12 mins lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes lmtp_save_to_detail_mailbox = yes log_path = /var/log/dovecot/dovecot.log mail_access_groups = mail mail_location = mdbox:~/mdbox:UTF-8 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 namespace inbox { inbox = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk { auto = subscribe special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox Trash { auto = subscribe special_use = \Trash } prefix = } passdb { args = /etc/dovecot/dovecot-sql-master.conf.ext driver = sql master = yes pass = yes } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { quota = dict:User quota::proxy::quota quota_rule = *:storage=100G quota_rule2 = Trash:storage=+10G quota_warning = storage=95%% quota-warning 95 %u quota_warning2 = storage=80%% quota-warning 80 %u sieve_before = /srv/vmail/dovecot_global_filter.sieve sieve_dir = ~/sieve sieve_global_extensions = +vnd.dovecot.duplicate } postmaster_address = postmaster(a)example.com protocols = " imap lmtp sieve" service aggregator { fifo_listener replication-notify-fifo { group = mail mode = 0660 user = dovecot } unix_listener replication-notify { group = mail mode = 0660 user = dovecot } } service auth { unix_listener auth-client { group = mail mode = 0660 } unix_listener auth-userdb { group = mail } } service dict { unix_listener dict { group = mail mode = 0660 user = dovecot } } service doveadm { inet_listener { port = 994 } } service lmtp { executable = lmtp -L unix_listener lmtp { group = mail mode = 0660 } } service managesieve-login { inet_listener sieve { port = 4190 } } service quota-warning { executable = script /usr/local/bin/quota-warning.sh unix_listener quota-warning { user = mail } user = dovecot } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { group = mail mode = 0660 user = dovecot } } ssl = required ssl_cert = </etc/ssl/example.com/fullchain-combo.crt ssl_cipher_list = ALL:HIGH:!SSLv2:!SSLv3:!MEDIUM:!LOW:!EXP:!RC4:!MD5:!aNULL:@STRENGTH ssl_key = # hidden, use -P to show it userdb { args = /etc/dovecot/dovecot-sql-master.conf.ext driver = sql } userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } protocol lmtp { log_path = /var/log/dovecot/lmtp.log mail_plugins = " notify replication sieve" } protocol lda { log_path = /var/log/dovecot/lda.log mail_plugins = " notify replication sieve" } protocol imap { mail_plugins = " notify replication" }

2 6

[sieve][regex] Matching multiple strings in the "Received" header
by Adi Pircalabu 08 May '18

08 May '18

Hi, I'm trying to use this expression in Sieve, but for some reason the filter doesn't work: require ["fileinto","regex"]; # rule:[gmail-outlook-yahoo-aol-friends] if header :regex "received" ".from.*(outbound.protection.outlook.com|.google.com|.yahoo.com|mx.aol.com)." { fileinto "INBOX.gmail-hotmail-yahoo-aol-friends"; stop; } However, it's working fine with egrep: egrep ".from.*(outbound.protection.outlook.com|.google.com|.yahoo.com|mx.aol.com)." * 1525657297.M401428P1459.host01.quick.net.au,S=10073,W=10275:2,S:Received: from APC01-PU1-obe.outbound.protection.outlook.com (mail-oln040092254061.outbound.protection.outlook.com [40.92.254.61]) Am I using Sieve correctly here? Is ".from.*(outbound.protection.outlook.com|.google.com|.yahoo.com|mx.aol.com)." expression valid for Sieve? Or do I have to split it in an array as per https://wiki2.dovecot.org/Pigeonhole/Sieve/Examples#Flagging_or_Highlightin… example? Thanks, -- Adi Pircalabu

4 6

Released Pigeonhole v0.4.24.rc1 for Dovecot v2.2.36.rc1.
by Stephan Bosch 08 May '18

08 May '18

Hello Dovecot users, Here's a first release candidate for the upcoming Pigeonhole release for Dovecot v2.2.36. It only contains bugfixes for now. There's one experimental plugin still in the pipeline. Changelog v0.4.24: - Fix assert panics triggered by empty messages that are being forwarded using redirect or vnd.dovecot.report. This does not likely normally occur, but this is seen as a result of certain benign failures in object storage. - Make the length of the subject header for the vacation response configurable and enforce the limit in UTF-8 codepoints rather than bytes. The subject header for a vacation response was statically truncated to 256 bytes, which is too limited for multi-byte UTF-8 characters. - Sieve editheader extension: Fix assertion panic occurring when it is used to manipulate a message header with a very large header field. - Properly abort execution of the sieve_discard script upon error. Before, the LDA Sieve plugin attempted to execute the sieve_discard script when an error occurs. This can lead to the message being lost. - Fix the interaction between quota and the sieve_discard script. When quota was used together with a sieve_discard script, the message delivery did not bounce when the quota was exceeded. The release is available as follows: http://pigeonhole.dovecot.org/releases/2.2/rc/dovecot-2.2-pigeonhole-0.4.24… http://pigeonhole.dovecot.org/releases/2.2/rc/dovecot-2.2-pigeonhole-0.4.24… Refer to http://pigeonhole.dovecot.org and the Dovecot wiki for more information. Have fun testing this release candidate and don't hesitate to notify me when there are any problems. Regards, -- Stephan Bosch stephan(a)rename-it.nl

1 0

2.3.1 Replication is throwing scary errors
by Andy Weal 06 May '18

06 May '18

Hi all, New to the mailing lists but have joined up because of above */2.3.1 Replication is throwing scary errors /*Brief system configuration MX1 - Main Freebsd 11.1-Release-p9 Hosted on a Vultr VM in Sydney AU MTA = Postfix 3.4-20180401 Dovecot = 2.3.1 File system = ufs MX2 - Backup Freebsd 11.1-Release-p9 Running on bare metal - no VM or jails MTA = Postfix 3.4-20180401 Dovecot = 2.3.1 File system = ufs ( on SSD) */ /*Brief sequence of events 1. apx 10 days back upgraded both mx1 and mx2 to dovecot 2.3.1_2 from 2.3.0 (service dovecot stop, portmaster upgrade, service dovecot start) 2. both systems ran ok with no errors for 10 days. 3. Last night I shutdown mx2 and restarted it a few hours later 4. within minutes i was getting the following types of errors on mx2 May 06 12:56:29 doveadm: Error: Couldn't lock /var/mail/vhosts/example.net/user1/.dovecot-sync.lock: fcntl(/var/mail/vhosts/example.net/user1/.dovecot-sync.lock, write-lock, F_SETLKW) locking failed: Timed out after 30 seconds (WRITE lock held by pid 1960) Before i venture down the rabbit hole of fault finding and excess coffee consumption I was wondering if any of you had any updates on the problems discussed below. Cheers for now, Andy Hi, [Formatting is a bit rough, replying from a trimmed digest email] >/Message: 1 />/Date: Fri, 6 Apr 2018 15:04:35 +0200 />/From: Michael Grimm <trashcan at ellael.org <https://dovecot.org/mailman/listinfo/dovecot>> />/To: Dovecot Mailing List <dovecot at dovecot.org <https://dovecot.org/mailman/listinfo/dovecot>> />/Subject: Re: 2.3.1 Replication is throwing scary errors />/Message-ID: <E7E7A927-68F8-443F-BA59-E66CED8FE878 at ellael.org <https://dovecot.org/mailman/listinfo/dovecot>> />/Content-Type: text/plain; charset=utf-8 />//>/Reuben Farrelly wrote: />>/From: Michael Grimm <trashcan at ellael.org <https://dovecot.org/mailman/listinfo/dovecot>> />//>>>/[This is Dovecot 2.3.1 at FreeBSD STABLE-11.1 running in two jails at distinct servers.] />>>/I did upgrade from 2.2.35 to 2.3.1 today, and I do become pounded by error messages at server1 (and vice versa at server2) as follows: />>>/| Apr 2 17:12:18 <mail.err> server1.lan dovecot: doveadm: Error: dsync(server2.lan): I/O has stalled, \ />>>/no activity for 600 seconds (last sent=mail_change, last recv=mail_change (EOL)) />>>/| Apr 2 17:12:18 <mail.err> server1.lan dovecot: doveadm: Error: Timeout during state=sync_mails \ />>>/(send=changes recv=mail_requests) />>>/[?] />>>/| Apr 2 18:59:03 <mail.err> server1.lan dovecot: doveadm: Error: dsync(server2.lan): I/O has stalled, \ />>>/no activity for 600 seconds (last sent=mail, last recv=mail (EOL)) />>>/| Apr 2 18:59:03 <mail.err> server1.lan dovecot: doveadm: Error: Timeout during state=sync_mails \ />>>/(send=mails recv=recv_last_common) />>>/I cannot see in my personal account any missing replications, *but* I haven't tested this thoroughly enough. I do have customers being serviced at these productive servers, *thus* I'm back to 2.2.35 until I do understand or have learned what is going on. />//>/In my reply to this statement of mine I mentioned that I have seen those timeouts quite some times during the past year. Thus, I upgraded to 2.3.1 again, and boom: after some hours I ended up in hanging processes [1] like (see Remko's mail in addition) ... />//>/doveadm-server: [IP4/6 <USER1> SOME/MAILBOX import:0/0] (doveadm-server) />//>/? at server2 paired with a file like ? />//>/-rw------- 1 vmail dovecot uarch 0 Apr 3 16:52 /home/to/USER1/.dovecot-sync.lock />//>/Corresponding logfile entries at server2 are like ? />//>/Apr 3 17:10:49 <mail.err> server2.lan dovecot: doveadm: Error: Couldn't lock /home/to/USER1/.dovecot-sync.lock: \ />/fcntl(/home/to/USER1/.dovecot-sync.lock, write-lock, F_SETLKW) locking failed: Timed out after 30 seconds \ />/(WRITE lock held by pid 51110) />//>/[1] Even stopping dovecot will not end those processes. One has to manually kill those before restarting dovecot. />//>/After one day of testing 2.3.1 with a couple of those episodes of locking/timeout, and now missing mails depending with server your MUA will connect to, I went back to 2.2.35. After two days at that version I never had such an episode again. />//>>/It's not just you. This issue hit me recently, and it was impacting />>/replication noticeably. I am following git master-2.3 . />/[...] />>/There is also a second issue of a long standing race with replication />>/occurring somewhere whereby if a mail comes in, is written to disk, is />>/replicated and then deleted in short succession, it will reappear />>/again to the MUA. I suspect the mail is being replicated back from />>/the remote. A few people have reported it over the years but it's not />>/reliable or consistent, so it has never been fixed. />>/And lastly there has been an ongoing but seemingly minor issue />>/relating to locking timing out after 30s particularly on the remote />>/host that is being replicated to. I rarely see the problem on my />>/local disk where almost all of the mail comes in, it's almost always />>/occurring on the replicate/remote system. />//>/It might be time to describe our setups in order to possibly find common grounds that might trigger this issue you describe and Rimko and myself ran into as well. />//>/Servers: Cloud Instances (both identical), around 25ms latency apart. />/Intel Core Processor (Haswell, no TSX) (3092.91-MHz K8-class CPU) />/Both servers are connected via IPsec/racoon tunnels />/OS: FreeBSD 11.1-STABLE (both servers) />/Filesystem: ZFS />/MTA: postfix 3.4-20180401 (postfix delivers via dovecot's LMTP) />/IMAP: dovecot running in FreeBSD jails (issues with 2.3.1, fine with 2.2.35) />/Replication: unsecured tcp / master-master />/MUA: mainly iOS or macOS mail.app, rarely roundcube / For me: Servers: Main: VM on a VMWare ESXi local system (light load), local SSD disks (no NFS) Redundant: Linode VM in Singapore, around 250ms away Also no NFS. Linode use SSDs for IO. There is native IPv6 connectivity between both VMs. As I am using TCPs I don't have a VPN between them - just raw IPv6 end to end. OS: Gentoo Linux x86_64 kept well up to date Filesystem: EXT4 for both MTA: Postfix 3.4-x (same as you) IMAP: Dovecot running natively on the machine (no jail/chroot) Replication: Secured TCP / master-master (but only one master is actively used for SMTP and MUA access) MUA: Thunderbird, Maildroid, MS Mail, Gmail client, Roundcube, LG Mail client on handset etc >/I believe it is worthwhile to mention here that I run a poor man's fail-over approach (round-robin DNS) as follows: />//>/DNS: mail.server.tld resolves to one IP4 and one IP6 address of each server, thus 4 IP addresses in total / For me I have a simple pair of servers that replicate mail to each other. Clients connect to the main server only, which is where mail comes in. The second one that experiences the problem with locking is only a redundant server which is a secondary MX, that only gets occasional SMTP deliveries from time to time. So the amount of replication back from the "secondary" is very minimal; the vast bulk of the replication is the primary replicating changes out. Reuben

2 1

Re: expiring mail from root's Maildirs?
by LuKreme 05 May '18

05 May '18

(Sorry about previous mail) > On May 4, 2018, at 07:45, Aki Tuomi <aki.tuomi(a)dovecot.fi> wrote: > Dovecot has hardcoded root prevention. For delivery, too. So dovecot cannot expire, reindex, clean, repair, etc root mail? The mail is crontab mail that is sent out to users via mutt. What would be the "right” way to do this? (The cron tasks run as root because they are scanning system logs on behalf of certain users and those scans cannot be run as the user.) -- My main job is trying to come up with new and innovative and effective ways to reject even more mail. I'm up to about 97% now.

6 14

dovecot fts hangs on search
by André Rodier 05 May '18

05 May '18

Hello, I am trying to use Doevecot fts, with solr the script provided. To rebuild the index, I use the command: doveadm -D index -u mirina 'inbox' To rescan, I use: doveadm -D fts rescan -u mirina But when I do a search, with doveadm, the program hangs: doveadm -D search -u mirina text Madagascar > Debug: Loading modules from directory: /usr/lib/dovecot/modules > Debug: Module loaded: /usr/lib/dovecot/modules/lib10_quota_plugin.so > Debug: Module loaded: /usr/lib/dovecot/modules/lib20_fts_plugin.so > Debug: Module loaded: /usr/lib/dovecot/modules/lib21_fts_solr_plugin.so > Debug: Loading modules from directory: /usr/lib/dovecot/modules/doveadm > Debug: Skipping module doveadm_acl_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/lib10_doveadm_acl_plugin.so: undefined symbol: acl_lookup_dict_iterate_visible_next (this is usually intentional, so just ignore this message) > Debug: Skipping module doveadm_expire_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/lib10_doveadm_expire_plugin.so: undefined symbol: expire_set_deinit (this is usually intentional, so just ignore this message) > Debug: Module loaded: /usr/lib/dovecot/modules/doveadm/lib10_doveadm_quota_plugin.so > Debug: Module loaded: /usr/lib/dovecot/modules/doveadm/lib10_doveadm_sieve_plugin.so > Debug: Skipping module doveadm_fts_lucene_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/lib20_doveadm_fts_lucene_plugin.so: undefined symbol: lucene_index_iter_deinit (this is usually intentional, so just ignore this m$ > ssage) > Debug: Module loaded: /usr/lib/dovecot/modules/doveadm/lib20_doveadm_fts_plugin.so > Debug: Skipping module doveadm_mail_crypt_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/libdoveadm_mail_crypt_plugin.so: undefined symbol: mail_crypt_box_get_pvt_digests (this is usually intentional, so just ignore thi$ message) > doveadm(mirina): Debug: auth USER input: mirina home=/home/users/mirina uid=1002 gid=1001 mail=mirina(a)homebox.space > doveadm(mirina): Debug: Added userdb setting: mail=mirina(a)homebox.space doveadm(mirina): Debug: Effective uid=1002, gid=1001, home=/home/users/mirina > doveadm(mirina): Debug: Quota root: name=User quota backend=maildir args= > doveadm(mirina): Debug: Quota rule: root=User quota mailbox=* bytes=2147483648 messages=0 > doveadm(mirina): Debug: Quota grace: root=User quota bytes=214748364 (10%) > doveadm(mirina): Debug: Namespace inbox: type=private, prefix=, sep=/, inbox=yes, hidden=no, list=yes, subscriptions=yes location=maildir:~/mails/maildir:INDEX=~/mails/indexes/ > doveadm(mirina): Debug: maildir++: root=/home/users/mirina/mails/maildir, index=/home/users/mirina/mails/indexes, indexpvt=, control=, inbox=/home/users/mirina/mails/maildir, alt= > doveadm(mirina): Debug: quota: quota_over_flag check: STORAGE ret=1 value=134 limit=2097152 > doveadm(mirina): Debug: quota: quota_over_flag check: MESSAGE ret=0 value=3 limit=0 > doveadm(mirina): Debug: quota: quota_over_flag=0((null)) vs currently overquota=0 > doveadm(mirina): Debug: Namespace : Using permissions from /home/users/mirina/mails/maildir: mode=0700 gid=default > doveadm(mirina): Debug: http-client: host localhost: Host created > doveadm(mirina): Debug: http-client: host localhost: DNS lookup successful; got 2 IPs > doveadm(mirina): Debug: http-client: peer [::1]:8080: Peer created > doveadm(mirina): Debug: http-client: queue http://localhost:8080: Setting up connection to [::1]:8080 (1 requests pending) > doveadm(mirina): Debug: http-client: peer [::1]:8080: Linked queue http://localhost:8080 (1 queues linked) > doveadm(mirina): Debug: http-client: queue http://localhost:8080: Started new connection to [::1]:8080 > doveadm(mirina): Debug: http-client: request [Req1: GET http://localhost:8080/solr/select?fl=uid,score&rows=1&sort=uid+asc&q=%7b!lu… > ina]: Submitted > doveadm(mirina): Debug: http-client: Waiting for 1 requests to finish > doveadm(mirina): Debug: http-client: peer [::1]:8080: Creating 1 new connections to handle requests (already 0 usable, connecting to 0, closing 0) > doveadm(mirina): Debug: http-client: peer [::1]:8080: Making new connection 1 of 1 > doveadm(mirina): Debug: http-client: conn [::1]:8080 [0]: HTTP connection created (1 parallel connections exist) > doveadm(mirina): Debug: http-client: conn [::1]:8080 [0]: Connected > doveadm(mirina): Debug: http-client: conn [::1]:8080 [0]: Ready for requests > doveadm(mirina): Debug: http-client: peer [::1]:8080: Successfully connected (connections=1) > doveadm(mirina): Debug: http-client: peer [::1]:8080: Using 1 idle connections to handle 1 requests (1 total connections ready) > doveadm(mirina): Debug: http-client: queue http://localhost:8080: Connection to peer [::1]:8080 claimed request [Req1: GET http://localhost:8080/solr/select?fl=uid,score&rows=1&sort=uid+asc&q=%7b!lu… > :Madagascar)&fq=%2Bbox:838a1701af1ae65a3e12000032c62018+%2Buser:mirina] > doveadm(mirina): Debug: http-client: conn [::1]:8080 [0]: Claimed request [Req1: GET http://localhost:8080/solr/select?fl=uid,score&rows=1&sort=uid+asc&q=%7b!lu… > a3e12000032c62018+%2Buser:mirina] > [...] > doveadm(mirina): Debug: http-client: request [Req5: GET http://localhost:8080/solr/select?fl=uid,score&rows=1&sort=uid+asc&q=%7b!lu…] Sent header > doveadm(mirina): Debug: http-client: peer [::1]:8080: No more requests to service for this peer (1 connections exist) > doveadm(mirina): Debug: http-client: conn [::1]:8080 [0]: Got 200 response for request [Req5: GET http://localhost:8080/solr/select?fl=uid,score&rows=1&sort=uid+asc&q=%7b!lu…] (took 2 ms + 0 ms in queue) > doveadm(mirina): Debug: http-client: conn [::1]:8080 [0]: Response payload stream destroyed (0 ms after initial response) > doveadm(mirina): Debug: http-client: request [Req5: GET http://localhost:8080/solr/select?fl=uid,score&rows=1&sort=uid+asc&q=%7b!lu…] Finished > doveadm(mirina): Debug: http-client: queue http://localhost:8080: Dropping request [Req5: GET http://localhost:8080/solr/select?fl=uid,score&rows=1&sort=uid+asc&q=%7b!lu…] > doveadm(mirina): Debug: http-client: host localhost: Host is idle (timeout = 1799974 msecs) > doveadm(mirina): Debug: http-client: request [Req5: GET http://localhost:8080/solr/select?fl=uid,score&rows=1&sort=uid+asc&q=%7b!lu…] Free (requests left=1) > doveadm(mirina): Debug: http-client: All requests finished When I do the search with an imap client, I have this error after a long timeout: > May 01 07:08:58 homebox dovecot[5683]: imap(mirina): Panic: file imap-client.c: line 854 (client_check_command_hangs): assertion failed: (client->io != NULL || (client->output_cmd_lock != NULL && client->output_cmd_lock != client->input_lock)) > May 01 07:08:58 homebox dovecot[5683]: imap(mirina): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x95e92) [0x7f216b6f6e92] -> /usr/lib/dovecot/libdovecot.so.0(+0x95f8d) [0x7f216b6f6f8d] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f216b68ca91] -> dovecot/imap(client_continue_pending_input+0x1fc) [0x55f44a7eb15c] -> dovecot/imap(client_input+0x120) [0x55f44a7eb460] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x52) [0x7f216b70b9f2] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x109) [0x7f216b70d029] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x3c) [0x7f216b70ba8c] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7f216b70bc38] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f216b692fd3] -> dovecot/imap(main+0x328) [0x55f44a7dde68] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1) [0x7f216b2e22e1] -> dovecot/imap(_start+0x2a) [0x55f44a7ddfea] > May 01 07:08:58 homebox dovecot[5683]: imap(mirina): Fatal: master: service(imap): child 6149 killed with signal 6 (core dumps disabled) > May 01 07:08:58 homebox in.imapproxyd[20305]: Raw_Proxy(): IMAP server unexpectedly closed the connection on sd 11 My 10-master.conf: service decode2text { executable = script /usr/local/bin/decode2text.sh user = dovecot unix_listener decode2text { mode = 0666 } } And my 90-plugins.cof: # Add dovecot fts config fts = solr fts_autoindex = no fts_solr = url=http://localhost:8080/solr/ debug fts_decoder = decode2text Am I doing anything wrong? Thanks for your help. André

2 6

Warning message
by forums＠mehl-family.fr 05 May '18

05 May '18

Hi, In my maillog I see this warning message at every reception of e-mail: _STATUS=SENT (DELIVERED VIA DOVECOT SERVICE (DOVECONF: WARNING: /ETC/DOVECOT/CONF.D/90-QUOTA.CONF LINE 39: GLOBAL SETTING MAIL_PLUGINS WON'T CHAN....._ It is just a warning, the e-mail was delivered. I don't find where is the problem. Thank's.

3 2

v2.2.36 release candidate released
by Timo Sirainen 04 May '18

04 May '18

https://dovecot.org/releases/2.2/rc/dovecot-2.2.36.rc1.tar.gz https://dovecot.org/releases/2.2/rc/dovecot-2.2.36.rc1.tar.gz.sig v2.2.36 is hopefully going to be the last v2.2.x release. Please test this RC well, so we'll have a good final release! v2.3.2 is still going to take a couple of months before it's ready. * login-proxy: If ssl_require_crl=no, allow revoked certificates. Also don't do CRL checks for incoming client certificates. * stats plugin: Don't temporarily enable PR_SET_DUMPABLE while opening /proc/self/io. This may still cause security problems if the process is ptrace()d at the same time. Instead, open it while still running as root. + doveadm: Added mailbox cache decision&remove commands. See doveadm-mailbox(1) man page for details. + doveadm: Added rebuild attachments command for rebuilding $HasAttachment or $HasNoAttachment flags for matching mails. See doveadm-rebuild(1) man page for details. - dsync: Lock file generation failed if home directory didn't exist - Snippet generation for HTML mails didn't ignore &entities inside blockquotes, producing strange looking snippets. - imapc: Fix assert-crash if getting disconnected and after reconnection all mails in the selected mailbox are gone. - pop3c: Handle unexpected server disconnections without assert-crash - fts: If mails contained NUL characters, the text around it wasn't indexed. - Obsolete dovecot.index.cache offsets were sometimes used. Trying to fetch a field that was just added to cache file may not have always found it.

3 4

expiring mail from root's Maildirs?
by ＠lbutlr 04 May '18

04 May '18

I would like to delete old mail from root's sent mailbox but doveadm throws errors when I try to do this, not wanting to process root's mail at all (I am running the commands as root, naturally) # doveadm expunge -u root mailbox Sent SENTBEFORE 1-Apr-2018 doveadm(root): Error: Invalid settings in userdb: userdb returned 0 as uid doveadm(root): Error: User lookup failed: Invalid user settings. Refer to server log for more information. The error makes me think this is intentional, and I can see that makes a sort of sense, but it still leaves me with a Sent box that grow forever until I manually go in and remove old mails. I am using passed for userdb and pam for passdb: passdb { username_filter = "!*@*" driver = pam } userdb { driver = passwd } Can I do this with doveadm or am going to have to resort to either manually removing the mail (hah!) or just crontabbing a task to remove the files more than 30 days old?

2 1

Use of NO-NOSELECT in mail_location
by Joseph Tam 03 May '18

03 May '18

I enabled NO-NOSELECT in mail_location as it seemed to be an optimization without negative consequences. The wiki states NO-NOSELECT : Automatically delete any \NoSelect mailboxes that have no children. These mailboxes are sometimes confusing to users. Also if a \NoSelect mailbox is attempted to be created with "CREATE box/", it's created as selectable mailbox instead. The last sentence is important: if you allow this, you won't be able to create folders (i.e. directories); this caught me offguard. If you use mbox, this is something you don't want to enable. Joseph Tam <jtam.home(a)gmail.com>

1 0

v2.3.1: Event leaked (parent=(nil)): http-client.c:137 and 439
by Milan Knížek 03 May '18

03 May '18

Hi, After upgrade to dovecot 2.3.1, many IMAP clients cause errors in dovecot log: May 01 20:15:51 tiger dovecot[21985]: imap: Warning: Event 0x555fd3c01630 leaked (parent=(nil)): http-client.c:137 May 01 20:15:51 tiger dovecot[21985]: imap: Warning: Event 0x555fd3c00140 leaked (parent=(nil)): http-client.c:439 Namely: * roundcube 1.3.3 * offlineimap * nextcloud mail app Despite the errors, the basic functionality seems to work - mails are received by the client. However, the GUI clients display an "internal server error" message window on each refresh. Some other clients do not create any issues: * MailDroid (Android) * getmail Anybody got a similar behaviour? -- Milan Knížek | knizek.confy(a)gmail.com

2 2