- dovecot - dovecot.org

mail_filter plugin: failed: EOF without input
by 刘莹莹 07 Feb '20

07 Feb '20

some import  configure: plugin {   mail_filter = mail-filter %u # %u = username given to the script as first   mail_filter_out = mail-filter-out %u } service mail-filter {  executable = script /usr/local/bin/mail-filter.sh  user = dovecot  unix_listener mail-filter {    mode = 0600    user = vmail  } } service mail-filter-out {  executable = script /usr/local/bin/mail-filter-out.sh  user = dovecot  unix_listener mail-filter-out {    mode = 0600    user = vmail  } } protocol lda {     mail_plugins = quota sieve expire autocreate mail_filter     auth_socket_path = /var/run/dovecot/auth-master     rejection_subject = Rejected: %s     lda_mailbox_autocreate = yes     lda_mailbox_autosubscribe = yes     sendmail_path = /usr/sbin/sendmail } cat mail-filter-out.sh #!/bin/sh cat > tempfile cat  mail-filter.sh #!/bin/sh USER=$1 cat > tempfile Some important Error logs： Feb 07 15:49:19 lda(q1(a)a.com)<53648><rY6oIH8WPV6Q0QAA0J78UA>: Error: Mailbox INBOX: Saving mail: write(/home/a.com/q1/storage/m.1) failed: EOF without input Feb 07 15:49:19 lda(q1(a)a.com)<53648><rY6oIH8WPV6Q0QAA0J78UA>: Info: msgid=<77z2kkfmm1-7846bu3tx6(a)nsmail6.0>: save failed to INBOX: Mailbox INBOX: Saving mail: write(/home/a.com/q1/storage/m.1) failed: EOF without input Feb 07 15:49:19 lda(q1(a)a.com)<53648><rY6oIH8WPV6Q0QAA0J78UA>: Debug: auth-master: conn unix:/var/run/dovecot/auth-master (pid=10651,uid=0): Disconnected: Connection closed (fd=11)

2 1

mail_filter plugin: failed: EOF without input
by 刘莹莹 07 Feb '20

07 Feb '20

some import  configure: plugin {   mail_filter = mail-filter %u # %u = username given to the script as first   mail_filter_out = mail-filter-out %u } service mail-filter {  executable = script /usr/local/bin/mail-filter.sh  user = dovecot  unix_listener mail-filter {    mode = 0600    user = vmail  } } service mail-filter-out {  executable = script /usr/local/bin/mail-filter-out.sh  user = dovecot  unix_listener mail-filter-out {    mode = 0600    user = vmail  } } protocol lda {     mail_plugins = quota sieve expire autocreate mail_filter     auth_socket_path = /var/run/dovecot/auth-master     rejection_subject = Rejected: %s     lda_mailbox_autocreate = yes     lda_mailbox_autosubscribe = yes     sendmail_path = /usr/sbin/sendmail } cat mail-filter-out.sh #!/bin/sh cat > tempfile cat  mail-filter.sh #!/bin/sh USER=$1 cat > tempfile Some important Error logs： Feb 07 15:49:19 lda(q1(a)a.com)<53648><rY6oIH8WPV6Q0QAA0J78UA>: Error: Mailbox INBOX: Saving mail: write(/home/a.com/q1/storage/m.1) failed: EOF without input Feb 07 15:49:19 lda(q1(a)a.com)<53648><rY6oIH8WPV6Q0QAA0J78UA>: Info: msgid=<77z2kkfmm1-7846bu3tx6(a)nsmail6.0>: save failed to INBOX: Mailbox INBOX: Saving mail: write(/home/a.com/q1/storage/m.1) failed: EOF without input Feb 07 15:49:19 lda(q1(a)a.com)<53648><rY6oIH8WPV6Q0QAA0J78UA>: Debug: auth-master: conn unix:/var/run/dovecot/auth-master (pid=10651,uid=0): Disconnected: Connection closed (fd=11)

1 0

re: Dovecot - Upgrade Solr 7.7.2 to 8.4.1
by Francis Augusto Medeiros-Logeay 05 Feb '20

05 Feb '20

On 1/23/20 7:03 AM, Domenico Pastore wrote: >> So, with Dovecot is it possible to use Apache Solr 8.4? >> High RAM usage is the only problem? > I'm using 8.4.0 and it works flawlessly. I want to install fts-solr, but must tutorials are mentioning solr 7.7.0. Any heads-up on what one must pay attention to when installing 8.4.0? Do I need to update the version on the schemas, for example? Best, Francis

2 1

auth-client via SSL?
by Heiko Schlittermann 05 Feb '20

05 Feb '20

Hello, does dovecot support tls-on-connect for AF INET based auth-client sockets? Rationale behind my question: Exim can use the Dovecot auth-client socket to delegate the SMTP-AUTH authentication to Dovecot. Currently Exim supports the AF UNIX only for this socket. Jeremy makes progress in extending this to use AF INET sockets too. While it works with clear text communication already, during testing I was to setup the auch-client socket as an TLS server (tls-on-connect). It doesn't seem to work as I'd expect. The socket still offers clear-text only. Here my configuration snippets regarding this socket ssl = yes ssl_cert = </etc/dovecot/private/server.pem ssl_key = </etc/dovecot/private/server.pem service auth { … unix_listener auth-client { group = _exim mode = 0660 } inet_listener auth-client { name = exim port = 4711 ssl = yes } } SSL connections to :993 work as expected. Best regards from Dresden/Germany Viele Grüße aus Dresden Heiko Schlittermann -- SCHLITTERMANN.de ---------------------------- internet & unix support - Heiko Schlittermann, Dipl.-Ing. (TU) - {fon,fax}: +49.351.802998{1,3} - gnupg encrypted messages are welcome --------------- key ID: F69376CE - ! key id 7CBF764A and 972EAC9F are revoked since 2015-01 ------------ -

2 3

Submission service, XCLIENT and HELO
by Riccardo Alfieri 04 Feb '20

04 Feb '20

Hello, I'm using version 2.3.4.1 and I have a fairly simple setup based on a submission server where I run dovecot and a relay server with postfix. The relevant part of dovecot's config is as follows (sanitized): hostname = submission.domain.local submission_client_workarounds = whitespace-before-path submission_relay_host = 192.168.1.1 <- postfix submission_relay_port = 25 submission_relay_trusted = yes Postfix is configured as follows: smtpd_authorized_xclient_hosts = 192.168.1.2 <- submission server Everything apparently works as expected, meaning that I can correctly authenticate on the submission server and the email is relayed to postfix, where I can see the original MUA's IP correctly logged. There is, however, a little problem with the client HELO string that is not being forwarded to postfix. Instead of having the MUA HELO, I see the submission server HELO, as shown in the following tcpdump taken on the postfix server: 220 postfix.domain.local ESMTP Postfix (Ubuntu) EHLO submission.domain.local 250-postfix.domain.local 250-PIPELINING 250-SIZE 10240000 250-VRFY 250-ETRN 250-STARTTLS 250-AUTH DIGEST-MD5 CRAM-MD5 NTLM PLAIN LOGIN 250-AUTH=DIGEST-MD5 CRAM-MD5 NTLM PLAIN LOGIN 250-XCLIENT NAME ADDR PROTO HELO REVERSE_NAME PORT LOGIN DESTADDR DESTPORT 250-ENHANCEDSTATUSCODES 250-8BITMIME 250-DSN 250 SMTPUTF8 XCLIENT ADDR=192.168.1.3 PORT=57116 LOGIN=riccardo-at-domain.local 220 postfix.domain.local ESMTP Postfix (Ubuntu) EHLO submission.domain.local 250-postfix.domain.local 250-PIPELINING ... As you can see the first EHLO is correctly done with the submission server's hostname, but the subsequent one after XCLIENT is -still- the same hostname, while I was expecting that to be the one forwarded from the MUA, or possibly a "HELO=somethingelse" in the XCLIENT line. I've looked almost everywhere and I couldn't find a way to make dovecot use the MUA's HELO string. The question I'm asking is if there is a way to have the MUA's HELO forwarded to the relay server in some way, or if this is a bug or an expected behaviour. Thanks for any help you could give -- Best regards, Riccardo Alfieri Spamhaus Technology https://www.spamhaustech.com/

1 0

Vacation use different SMTP server
by azurit＠pobox.sk 03 Feb '20

03 Feb '20

Hi, in our setup, we have two SMTP servers: - one for receiving messages (this one is using Dovecot's LMTP for delivery) - one for sending messages (this one is used by our users as outgoing SMTP server) Only the first one has list of local domains, local e-mail accoutns etc. so the second one will ALWAYS use MX records for delivery - with this setup, we can allow to our users to add any domain to their accounts (for example, if someone will add gmail.com and create e-mail accounts on it, it's complete safe because we will never deliver mail for gmail.com locally). The only problem seems to be vacation messages (maybe other messages send by sieve), as Dovecot is using the first SMTP server for sending. My questions: Can i set different SMTP server for sieve messages? How exactly is Dovecot/Sieve choosing which SMTP server will be used? Thanks. azur

3 6

mail_filter and mail_filter_out broken somewhere between 2.2.27 and 2.3.4, problem still exists in git
by Michael Fincham 03 Feb '20

03 Feb '20

Hi Dovecot folks, I recently reported this bug in Debian (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939442) after a stretch -> buster upgrade, however since I can reproduce it using the latest 2.4 from git I thought perhaps I ought to take it straight upstream. Here's the text I provided Debian about the issue, and below that I've included a syslog snip showing the same issue in a fresh build of git master as well. mail_filter_out seems to fully panic (backtrace below), whereas mail_filter is just behaving oddly. Thanks :) ***************************** Package: dovecot-core Version: 2.3.4.1-5+deb10u1 Severity: important Hi Dovecot maintainers, After upgrading from the latest stretch version of dovecot-core (2.2.27-3+deb9u5) to buster (2.3.4.1-5+deb10u1) the "mail filter" interface seems to have broken. This problem is also present in the sid version (2.3.7.2-1). Mail filter is used to run the content of messages being stored or retrieved through an arbitrary process. The interface used for the external process is described here: https://wiki.dovecot.org/Plugins/MailFilter It is expected that the process will be called with the arguments specified in the configuration then supplied a message body on stdin, however since upgrading it seems that the arguments are not being correctly passed, instead being all jammed in to $1 and separated by tabs, rather than expanded in to argv. Even stranger the first few lines of the body of the message appear in argv rather than in stdin... These reproduction steps were carried out on a fresh install of Debian Buster with the "dovecot-core" package installed initially from stretch then upgraded to the buster version, however this behaviour has also been observed on stretch systems after upgrading to buster. To reproduce, drop this minimalised config in to /etc/dovecot/conf.d/repro.conf: # Minimal maildir setup for LDA first_valid_uid = 0 mail_location = maildir:~/Maildir userdb { driver = static args = allow_all_users=yes uid=mail gid=mail home=/tmp/%u } # Mail filter configuration mail_plugins = $mail_plugins mail_filter plugin { mail_filter = mail-filter read %u mail_filter_out = mail-filter write %u } service mail-filter { executable = script /usr/local/bin/mail-filter.sh user = dovecot unix_listener mail-filter { mode = 0666 } } And create the example script in /usr/local/bin/mail-filter.sh with executable permissions: #!/bin/bash echo "arguments were: $@" 1>&2 tempfile=$(mktemp) cat > "${tempfile}" cat "${tempfile}" rm "${tempfile}" This script simply logs the arguments it recieves, writes stdin to a file then retrieves it again from the file. Here's a sample session of me using dovecot-lda to pass a message through this script, then retrieve it again with doveadm: root@scratch-b6fd8bdd:~# /usr/lib/dovecot/dovecot-lda -d fincham@scratch-b6fd8bdd -f 'Test <scratch-b6fd8bdd>' < /root/test.eml root@scratch-b6fd8bdd:~# doveadm fetch -u 'fincham@scratch-b6fd8bdd' hdr subject Test hdr: To: Test <fincham@scratch-b6fd8bdd> From: Test <fincham@scratch-b6fd8bdd> Subject: This is the test e-mail root@scratch-b6fd8bdd:~# tail /var/log/syslog | grep mail-filter Sep 5 00:07:48 scratch-b6fd8bdd dovecot: mail-filter: Error: arguments were: write fincham@scratch-b6fd8bdd Sep 5 00:07:50 scratch-b6fd8bdd dovecot: mail-filter: Error: arguments were: read fincham@scratch-b6fd8bdd However after upgrading dovecot to the buster version this process no longer works, and the logged argv of the example script is very strange: root@scratch-b6fd8bdd:~# apt dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following NEW packages will be installed: liblua5.3-0 libsodium23 ssl-cert The following packages will be upgraded: dovecot-core [...] root@scratch-b6fd8bdd:~# /usr/lib/dovecot/dovecot-lda -d fincham@scratch-b6fd8bdd -f scratch-b6fd8bdd < /root/test.eml Aborted root@scratch-b6fd8bdd:~# doveadm fetch -u 'fincham@scratch-b6fd8bdd' hdr subject Test hdr: Hello! doveadm(fincham@scratch-b6fd8bdd): Error: Mailbox INBOX: UID=1: read() failed: Cached message size larger than expected (115 > 7, box=INBOX, UID=1) (read reason=mail stream) doveadm(fincham@scratch-b6fd8bdd): Error: Corrupted record in index cache file /tmp/fincham(a)scratch-b6fd8bdd/Maildir/dovecot.index.cache: UID 1: Broken physical size in mailbox INBOX: read() failed: Cached message size larger than expected (115 > 7, box=INBOX, UID=1) doveadm(fincham@scratch-b6fd8bdd): Error: read() failed: Cached message size larger than expected (115 > 7, box=INBOX, UID=1) doveadm(fincham@scratch-b6fd8bdd): Error: fetch(hdr) failed for box=INBOX uid=1: read() failed: Cached message size larger than expected (115 > 7, box=INBOX, UID=1) root@scratch-b6fd8bdd:~# tail /var/log/syslog | grep mail-filter Sep 5 00:07:48 scratch-b6fd8bdd dovecot: mail-filter: Error: arguments were: write fincham@scratch-b6fd8bdd Sep 5 00:07:50 scratch-b6fd8bdd dovecot: mail-filter: Error: arguments were: read fincham@scratch-b6fd8bdd Sep 5 00:12:11 scratch-b6fd8bdd dovecot: mail-filter: Error: arguments were: write#011fincham@scratch-b6fd8bdd#011 To: Test <fincham@scratch-b6fd8bdd> From: Test <fincham@scratch-b6fd8bdd> Subject: This is the test e-mail Sep 5 00:12:14 scratch-b6fd8bdd dovecot: mail-filter: Error: arguments were: read#011fincham@scratch-b6fd8bdd#011 To: Test <fincham@scratch-b6fd8bdd> From: Test <fincham@scratch-b6fd8bdd> Subject: This is the test e-mail -- Package-specific info: dovecot configuration --------------------- # 2.3.4.1 (f79e8e7e4): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.4 () # OS: Linux 4.19.0-5-cloud-amd64 x86_64 Debian 10.0 # Hostname: scratch-b6fd8bdd first_valid_uid = 0 mail_location = maildir:~/Maildir mail_plugins = " mail_filter" mail_privileged_group = mail namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { driver = pam } plugin { mail_filter = mail-filter read %u mail_filter_out = mail-filter write %u } service mail-filter { executable = script /usr/local/bin/mail-filter.sh unix_listener mail-filter { mode = 0666 } user = dovecot } ssl = no userdb { driver = passwd } userdb { args = allow_all_users=yes uid=mail gid=mail home=/tmp/%u driver = static } -- System Information: Debian Release: 10.0 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-5-cloud-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages dovecot-core depends on: ii adduser 3.118 ii libapparmor1 2.13.2-10 ii libbz2-1.0 1.0.6-9.1 ii libc6 2.28-10 ii libexttextcat-2.0-0 3.4.5-1 ii libicu63 63.1-6 ii liblua5.3-0 5.3.3-1.1 ii liblz4-1 1.8.3-1 ii liblzma5 5.2.4-1 ii libpam-runtime 1.3.1-5 ii libpam0g 1.3.1-5 ii libsodium23 1.0.17-1 ii libssl1.1 1.1.1c-1 ii libstemmer0d 0+svn585-1+b2 ii libwrap0 7.6.q-28 ii lsb-base 10.2019051400 ii openssl 1.1.1c-1 ii ssl-cert 1.0.39 ii ucf 3.0038+nmu1 ii zlib1g 1:1.2.11.dfsg-1 dovecot-core recommends no packages. Versions of packages dovecot-core suggests: pn dovecot-gssapi <none> pn dovecot-imapd <none> pn dovecot-ldap <none> pn dovecot-lmtpd <none> pn dovecot-lucene <none> pn dovecot-managesieved <none> pn dovecot-mysql <none> pn dovecot-pgsql <none> pn dovecot-pop3d <none> pn dovecot-sieve <none> pn dovecot-solr <none> pn dovecot-sqlite <none> pn dovecot-submissiond <none> ii ntp 1:4.2.8p12+dfsg-4 Versions of packages dovecot-core is related to: ii dovecot-core [dovecot-common] 1:2.3.4.1-5+deb10u1 pn dovecot-dev <none> pn dovecot-gssapi <none> pn dovecot-imapd <none> pn dovecot-ldap <none> pn dovecot-lmtpd <none> pn dovecot-managesieved <none> pn dovecot-mysql <none> pn dovecot-pgsql <none> pn dovecot-pop3d <none> pn dovecot-sieve <none> pn dovecot-sqlite <none> -- no debconf information ***************************** And here it is on 2.4 from git: Sep 5 02:18:10 scratch-b6fd8bdd dovecot: master: Dovecot v2.4.devel () starting up for imap, pop3, lmtp Sep 5 02:18:10 scratch-b6fd8bdd systemd[1]: Started LSB: Dovecot init script. Sep 5 02:18:12 scratch-b6fd8bdd dovecot: mail-filter: Error: arguments were: write#011fincham@scratch-b6fd8bdd#011 To: Test <fincham@scratch-b6fd8bdd> From: Test <fincham@scratch-b6fd8bdd> Subject: This is the test e-mail Sep 5 02:18:12 scratch-b6fd8bdd dovecot: lda(fincham@scratch-b6fd8bdd)<4213><94f8BWRwcF11EAAA/w3Ckw>: Panic: file ostream.c: line 201 (o_stream_flush): assertion failed: (stream->stream_errno != 0) Sep 5 02:18:12 scratch-b6fd8bdd dovecot: lda(fincham@scratch-b6fd8bdd)<4213><94f8BWRwcF11EAAA/w3Ckw>: Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0xef5fb) [0x7f85ed0715fb] -> /usr/lib/dovecot/libdovecot.so.0(+0xef661) [0x7f85ed071661] -> /usr/lib/dovecot/libdovecot.so.0(+0x4e808) [0x7f85ecfd0808] -> /usr/lib/dovecot/libdovecot.so.0(+0x52ec1) [0x7f85ecfd4ec1] -> /usr/lib/dovecot/libdovecot-storage.so.0(maildir_save_finish+0x96) [0x7f85ed1b24d6] -> /usr/lib/dovecot/libdovecot-lda.so.0(+0x4395) [0x7f85ed294395] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_save_finish+0x82) [0x7f85ed189e52] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_storage_copy+0xd9) [0x7f85ed17c409] -> /usr/lib/dovecot/libdovecot-storage.so.0(maildir_copy+0x52) [0x7f85ed1aea02] -> /usr/lib/dovecot/libdovecot-lda.so.0(+0x4221) [0x7f85ed294221] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0x5c1bc) [0x7f85ed18a1bc] -> /usr/lib/dovecot/libdovecot-lda.so.0(mail_deliver_save+0x1b0) [0x7f85ed295390] -> /usr/lib/dovecot/libdovecot-lda.so.0(mail_deliver+0x2f6) [0x7f85ed295ad6] -> /usr/libexec/dovecot/dovecot-lda(main+0x81b) [0x560cba869f4b] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xeb) [0x7f85ecdde09b] -> /usr/libexec/dovecot/dovecot-lda(_start+0x2a) [0x560cba86a65a]

2 3

Sieve prevents tigger of quota-warning
by Tom Sommer 31 Jan '20

31 Jan '20

Hi All I have a few reports from Sieve users, that they are not receiving quota warnings. It appears that when a mailbox is reaching quota, and sieve is responsible for moving mail the mail due to a rule, the quota-warning directive is not triggered? It works fine if Sieve is not part of the flow, and lmtp is alone in handling mail saving. Does anyone have a fix or insights into this? 2.3.9.2 Thanks -- Tom

2 1

Split storage & solr
by Daniel Miller 30 Jan '20

30 Jan '20

Is it possible to setup the following: 1. Primary mailserver with SMTP solutions and Dovecot. 2. Primary server will store recent mails. 3. Secondary server for archival storage and Solr. So I'm not looking for a distributed cluster - simply a splitting of designated functions. Clients would only be connecting to the primary server. I know Dovecot supports an alternate storage location - that's what made me think this was possible. What I'm more uncertain of is Solr. My (probably flawed) thinking is to take advantage of a low-cost high-availability cloud server to provide primary email services. Dovecot, Postfix, and even ASSP don't have significant memory or processor requirements by themselves - especially for my smaller user base. However - storage in the cloud can be at a premium. Therefore I'm thinking of continuing to self-host the archives. And my own server has the raw power & memory to handle Solr easily. What's triggering this is our ISP's quality has been deteriorating - and the alternates don't appear much better. Initial visualization would have a VPN/SSH connection between the servers, and NFS mounting my storage to the cloud server for archives. If our connection drops - in theory "current" mail handling is unaffected. My concerns/questions: 1. If Dovecot is unable to reach the remote Solr - upon re-connection will Solr be told about the new messages to index? Or do I need to setup a periodic re-scan? 2. Is there a "better" method of accessing the archive storage area than NFS? Either a different network file system or is there a way to do it with Dovecot directly? 3. What am I not taking into consideration in this setup that you think will be a problem? --- Daniel

2 1

IMAP compatible Notes app for Android
by Rupert Gallagher 29 Jan '20

29 Jan '20

Hello! Please share your favourite open-source Notes app for Android, as I am struggling to find one compatible with IMAP. Thank you, and happy 2020!

2 2

imap panic: file array.c: line 10 (array_idx_modifiable_i)
by mabi 29 Jan '20

29 Jan '20

Hello, I just migrated a few dovecot IMAP mailbox (Maildir format) from a Dovecot 2.1.7 (Debian 7) mailbox server to a Dovecot 2.3.4 (Debian 10) mailbox server and one particular mailbox does not work properly and generates the following error log entries: Jan 21 09:39:21 Panic: imap(EMAIL_ADDRESS)<7741><UTsrWKKcasoAAAAAAAAAAAAAAAAAAAAB>: file array.c: line 10 (array_idx_modifiable_i): assertion failed: (idx * array->element_size < array->buffer->used) Jan 21 09:39:21 Error: imap(EMAIL_ADDRESS)<7741><UTsrWKKcasoAAAAAAAAAAAAAAAAAAAAB>: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0xdb15b) [0x7fa18def215b] -> /usr/lib/dovecot/libdovecot.so.0(+0xdb1f1) [0x7fa18def21f1] -> /usr/lib/dovecot/libdovecot.so.0(+0x4a001) [0x7fa18de61001] -> /usr/lib/dovecot/libdovecot.so.0(+0x493bf) [0x7fa18de603bf] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xde920) [0x7fa18e084920] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_index_sync_commit+0x22f) [0x7fa18e096a3f] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0x85b4b) [0x7fa18e02bb4b] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0x8862a) [0x7fa18e02e62a] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0x88937) [0x7fa18e02e937] -> /usr/lib/dovecot/libdovecot-storage.so.0(maildir_storage_sync_init+0xa3) [0x7fa18e02ece3] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_sync_init+0x57) [0x7fa18e002497] -> dovecot/imap [EMAIL_ADDRESS ::1 UID STORE](imap_sync_init+0x91) [0x563d342e16e1] -> dovecot/imap [EMAIL_ADDRESS ::1 UID STORE](cmd_sync_delayed+0x236) [0x563d342e25f6] -> dovecot/imap [EMAIL_ADDRESS ::1 UID STORE](client_handle_input+0x268) [0x563d342d58f8] -> dovecot/imap [EMAIL_ADDRESS ::1 UID STORE](client_input+0x7e) [0x563d342d5d6e] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x6f) [0x7fa18df0860f] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x136) [0x7fa18df09c06] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x4c) [0x7fa18df086ac] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x40) [0x7fa18df08810] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7fa18de88fd3] -> dovecot/imap [EMAIL_ADDRESS ::1 UID STORE](main+0x325) [0x563d342c7bf5] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xeb) [0x7fa18dc7309b] -> dovecot/imap [EMAIL_ADDRESS ::1 UID STORE](_start+0x2a) [0x563d342c7d8a] Jan 21 09:39:21 Fatal: imap(EMAIL_ADDRESS)<7741><UTsrWKKcasoAAAAAAAAAAAAAAAAAAAAB>: master: service(imap): child 7741 killed with signal 6 (core dumps disabled - https://dovecot.org/bugreport.html#coredumps) Does anyone have any idea what could be going wrong here? Maybe I need to run some kind of conversion or re-generate some indexes? Best regards, Mabi

3 10

Emails in Public folders aren't showing up in Outlook
by Barry Ralphs 29 Jan '20

29 Jan '20

Hi, I've inherited our Devocot setup from someone else & don't know much about it. I can view our Public email folders fine in Thunderbird, but when I try it with Outlook 2013, I can see the folder structure fine, but when I click on a folder it doesn't show any emails. Here's a screen shot of Outlook: https://imgur.com/CHIDJOr And Thunderbird: https://imgur.com/WxmsUTM Here's the version info & config output: # 2.2.36 (1f10bfa63): /etc/dovecot/dovecot.conf # OS: Linux 3.10.0-1062.1.1.el7.x86_64 x86_64 CentOS Linux release 7.7.1908 (Core) ext4 # Hostname: nikola auth_mechanisms = plain login auth_verbose = yes debug_log_path = syslog disable_plaintext_auth = no info_log_path = syslog mail_location = maildir:/home/%n/Maildir mbox_write_locks = fcntl namespace TMpublic { location = maildir:/iscsi/public/Maildir:INDEX=~/Maildir/public/index prefix = Public/ separator = / subscriptions = no type = public } namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Sent { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = separator = / type = private } passdb { driver = pam } ssl_cert = </etc/pki/dovecot/certs/dovecot.pem ssl_key = # hidden, use -P to show it userdb { driver = passwd } Any suggestions on how to get the Public folders to show the emails in Outlook? Thanks for the help.

1 0

error: include: personal location for included script `foo is unavailable
by Rudolf Schmidt 28 Jan '20

28 Jan '20

Hi, I want to split my active script into smaller chunks but I have issues with the include directive. My doveconf -n is # 2.3.9.2 (cf2918cac): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.9 (db4e9a2f) # OS: Linux 5.1.15-arch1-1-ARCH x86_64 Arch Linux auth_mechanisms = plain login auth_verbose = yes mail_location = maildir:~/mail managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date index ihave duplicate mime foreverypart extracttext passdb { args = scheme=plain /etc/dovecot/plain.pwd driver = passwd-file } plugin { sieve = file:~/sieve;active=~/.dovecot.sieve } protocols = imap lmtp service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } service stats { unix_listener stats-writer { mode = 0777 } } ssl = required ssl_cert = </etc/letsencrypt/live/domain.com/fullchain.pem ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it userdb { args = uid=vmail gid=vmail home=/var/mail/virtual/%Ld/%Ln driver = static } protocol lmtp { mail_plugins = " sieve" postmaster_address = rs@domain } I have a script vendors.sieve that I put into ~/sieve (my mails I store in ~/mails) and it does not find the script. include :personal "vendors"; Any ideas? -- Best Regards, Mit freundlichen Grüßen, Rudolf Schmidt

1 1

dict passdb: redis nil values
by Eirik Rye 28 Jan '20

28 Jan '20

Hi, I am trying to implement a dict lookup for disabled accounts, where both the passdb lookup and the disabled lookup is done in the same passdb. I was hoping that this configuration would work: passdb { name = redis driver = dict args = /etc/dovecot/dovecot-redis.conf.ext } --- uri = redis:host=127.0.0.1 key disabled { key = users/%u/disabled/%s format = value default_value = } key user { key = users/%u format = json } passdb_objects = user passdb_fields { fail = %{dict:disabled} } Unfortunately, this will always set the fail passdb_field regardless of whether the disabled key returns its empty default_value. Removing the default_value setting will cause the passdb lookup to fail if key lookup fails, as mentioned in the documentation. Is there a way to have the dict driver handle redis nil values similarly to how the sql driver handles NULL values? A working alternative I found is to set an invalid password if the disabled key is set: passdb_fields { password = %{if;%{dict:disabled};eq;;%{dict:user.password};} } However, this feels hacky. It also makes the auth-worker to log the following error (despite it being functional): dovecot: auth-worker(16229): Error: redis(test,127.0.0.1,<Kd3zJDOdfs1/AAAB>): Multiple password values not supported Any other suggestions, or should I simply fall back to using a separate passdb with deny=yes? Best regards, Eirik

1 0

Dovecot authentication through proxy
by Daniel Niewerth 28 Jan '20

28 Jan '20

Hi everybody, I run two redundant Dovecot servers with a shared Maildir on a GlusterFS volume and a SQL authentication backend based on a mirrored MariaDB database. Because of the splitbrain situation I would like to add two Dovecot Director as proxies. Since a few days I am trying to get the setup running. In the meantime I have achieved that the clients can successfully authenticate on the proxy and that the client connections are forwarded to the backend servers. Unfortunately I still have the problem that no authentication attempts are made on the backend servers. Can someone explain me how to solve this problem? I have read that it is eventually possible to work with Master Users. But I guess that won't work for me, because I use the mailcrypt plugin and the client password is also the password for the encryption key. Best regards Daniel ### Proxy Log ### ############### Jan 23 19:48:21 vsrv-***-prx01 dovecot: auth-worker(20760): Debug: sql(***(a)***.**,192.168.1.100,<sNTHFdOcbeDAqAFk>): Finished passdb lookup Jan 23 19:48:21 vsrv-***-prx01 dovecot: auth-worker(20760): Debug: conn unix:auth-worker (pid=20753,uid=112): auth-worker<1>: Finished Jan 23 19:48:21 vsrv-***-prx01 dovecot: auth: Debug: sql(***(a)***.**,192.168.1.100,<sNTHFdOcbeDAqAFk>): username changed ***(a)***.** -> *** Jan 23 19:48:21 vsrv-***-prx01 dovecot: auth: Debug: sql(***,192.168.1.100,<sNTHFdOcbeDAqAFk>): username changed *** -> ***(a)***.** Jan 23 19:48:21 vsrv-***-prx01 dovecot: auth: Debug: sql(***(a)***.**,192.168.1.100,<sNTHFdOcbeDAqAFk>): Finished passdb lookup Jan 23 19:48:21 vsrv-***-prx01 dovecot: auth: Debug: auth(***(a)***.**,192.168.1.100,<sNTHFdOcbeDAqAFk>): Auth request finished Jan 23 19:48:21 vsrv-***-prx01 dovecot: auth: Debug: client passdb out: OK#0111#011user=***@***.**#011proxy#011ssl=any-cert#011starttls=any-cert#011lip=192.168.20.49#011lport=993#011pass=<hidden> Jan 23 19:48:21 vsrv-***-prx01 dovecot: imap-login: Debug: Ignoring unknown passdb extra field: lip Jan 23 19:48:21 vsrv-***-prx01 dovecot: imap-login: Debug: Ignoring unknown passdb extra field: lport ### Backend Log ### ################### Jan 23 18:48:51 vsrv-***-mta01 dovecot: imap-login: Disconnected (no auth attempts in 30 secs): user=<>, rip=192.168.20.49, lip=192.168.20.28, TLS handshaking: Connection closed, session=<r9yRF9OcZODAqBQx> Jan 23 18:48:51 vsrv-***-mta01 dovecot: imap-login: Disconnected (no auth attempts in 30 secs): user=<>, rip=192.168.20.49, lip=192.168.20.28, TLS handshaking: Connection closed, session=<4C+SF9OcauDAqBQx> Jan 23 18:48:51 vsrv-***-mta01 dovecot: imap-login: Disconnected (no auth attempts in 30 secs): user=<>, rip=192.168.20.49, lip=192.168.20.28, TLS handshaking: Connection closed, session=<KDGSF9OcZuDAqBQx> Jan 23 18:48:51 vsrv-***-mta01 dovecot: imap-login: Disconnected (no auth attempts in 30 secs): user=<>, rip=192.168.20.49, lip=192.168.20.28, TLS handshaking: Connection closed, session=<lwKTF9OcbuDAqBQx> ### Proxy Config ### #################### # 2.3.9.2 (cf2918cac): /etc/dovecot/dovecot.conf # OS: Linux 4.15.0-74-generic x86_64 Ubuntu 18.04.3 LTS # Hostname: vsrv-***-prx01 auth_debug = yes director_mail_servers = 192.168.20.28 192.168.20.29 director_servers = 192.168.20.49:9090 192.168.20.58:9090 disable_plaintext_auth = no mail_location = mbox:~/mail:INBOX=/var/mail/%u namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } passdb { driver = pam } protocols = " imap" service director { inet_listener { port = 9090 } unix_listener login/director { mode = 0666 } } service imap-login { executable = imap-login director } service pop3-login { executable = pop3-login director } ssl = required ssl_cert = </etc/dovecot/private/***-**-fullchain.pem ssl_cipher_list = EDH+CAMELLIA:EDH+aRSA:EECDH+aRSA+AESGCM:EECDH+aRSA+SHA256:EECDH:+CAMELLIA128:+AES128:+SSLv3:!aNULL:!eNULL:!LOW:!3DES:!MD5:!EXP:!PSK:!DSS:!RC4:!SEED:!IDEA:!ECDSA:kE$ ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it ssl_prefer_server_ciphers = yes userdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } protocol lmtp { auth_socket_path = director-userdb } ### Backend Config ### ###################### # 2.3.9.2 (cf2918cac): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.9 (db4e9a2f) # OS: Linux 4.15.0-72-generic x86_64 Ubuntu 18.04.3 LTS # Hostname: vsrv-**-mta01.**.**.***.** auth_debug = yes auth_mechanisms = plain login mail_attribute_dict = file:%h/Maildir/dovecot-attributes mail_fsync = always mail_gid = vmail mail_home = /var/vmail/mailboxes/%d/%n mail_location = maildir:~/mail:LAYOUT=fs mail_nfs_index = yes mail_nfs_storage = yes mail_plugins = " notify mail_crypt" mail_privileged_group = vmail mail_uid = vmail managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date index ihave duplicate mime foreverypart extracttext imapsieve vnd.dovecot.imapsieve mmap_disable = yes namespace inbox { inbox = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Sent { auto = subscribe special_use = \Sent } mailbox Spam { auto = subscribe special_use = \Junk } mailbox Trash { auto = subscribe special_use = \Trash } prefix = } passdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } plugin { imapsieve_mailbox1_before = file:/var/vmail/sieve/global/learn-spam.sieve imapsieve_mailbox1_causes = COPY imapsieve_mailbox1_name = Spam imapsieve_mailbox2_before = file:/var/vmail/sieve/global/learn-ham.sieve imapsieve_mailbox2_causes = COPY imapsieve_mailbox2_from = Spam imapsieve_mailbox2_name = * mail_crypt_curve = brainpoolP512r1 mail_crypt_require_encrypted_user_key = # hidden, use -P to show it mail_crypt_save_version = 2 quota = maildir:User quota quota_exceeded_message = Benutzer %u hat das Speichervolumen überschritten. / User %u has exhausted allowed storage space. sieve = file:/var/vmail/sieve/%d/%n/scripts;active=/var/vmail/sieve/%d/%n/active-script.sieve sieve_before = /var/vmail/sieve/global/spam-global.sieve sieve_global_extensions = +vnd.dovecot.pipe sieve_pipe_bin_dir = /usr/bin sieve_plugins = sieve_imapsieve sieve_extprograms } protocols = imap lmtp sieve service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-userdb { group = vmail mode = 0660 user = vmail } } service imap-login { inet_listener imap { port = 143 } } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0660 user = postfix } user = vmail } service managesieve-login { inet_listener sieve { port = 4190 } } ssl = required ssl_cert = </etc/letsencrypt/live/******/fullchain.pem ssl_cipher_list = EDH+CAMELLIA:EDH+aRSA:EECDH+aRSA+AESGCM:EECDH+aRSA+SHA256:EECDH:+CAMELLIA128:+AES128:+SSLv3:!aNULL:!eNULL:!LOW:!3DES:!MD5:!EXP:!PSK:!DSS:!RC4:!SEED:!IDEA:!ECDSA:kEDH:CAMELLIA128-SHA:AES128-SHA ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it ssl_prefer_server_ciphers = yes userdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } protocol imap { imap_idle_notify_interval = 29 mins mail_max_userip_connections = 20 mail_plugins = " notify mail_crypt quota imap_quota imap_sieve" } protocol lmtp { mail_plugins = " notify mail_crypt sieve" postmaster_address = postmaster(a)***.** } -- This email was Malware checked by vsrv-dus6-fwl01

2 2

Number of imap-login processes always keeps growing, never goes down
by Jasper Siepkes 26 Jan '20

26 Jan '20

Hi all! I've bumped into an issue which Dovecot which has me a bit stumped; All of a sudden (ie. no obvious changes made to the config as far as I know) Dovecot seems to never stop 'imap-login' processes. This continues to the point where it will hit the 'process_limit'. For a 50-ish user install the limit was set to 100 but I increased it to 512. The only thing this changes it that Dovecot takes a little longer to hit the limit. I started having this problem with Dovecot version 2.3.2.1. After which I updated to the latest version of Dovecot (2.3.9.2) to see if that would fix my problem. However I'm still experiencing the same issue. For a bit of context; We use Dovecot with Open-Xchange where users login via OIDC, get a token and then use that token with Dovecot with the 'oauthbearer' auth method. However users can also login via a username / password combo stored in LDAP for clients that don't support 'oauthbearer' (ie. about all the mail clients ;-). We run Dovecot on SmartOS (ie. Illumos, a Solaris derivative). Oddly enough 'doveadm' is under the impression there are only 3 users loggedin (when there are 512 imap-login processes). I think 'doveadm who' doesn't show users who are authenticated via an token (oauthbearer) because I only see 3 users and I don't see my own user which is logged in via Open-Xchange by using oauthbearer as auth method. I've anonimized the output but you get the idea: ----8<-------------------- # doveadm who username # proto (pids) (ips) foo1(a)foo.nl 2 imap (78393 78391) (52.XXX.XXX.XXX) foo2(a)foo.nl 2 imap (72548 72547) (52.XXX.XXX.XXX) foo3(a)foo.nl 2 imap (480893 481231) (54.XXX.XXX.XXX 54.XXX.XXX.XXX) ----8<-------------------- I don't know if the above issue is related to my problem but the oauthbearer sessions not showing up seems like a bug? Meanwhile there are 512 Dovecot imap-login processes: ----8<-------------------- # ptree | grep imap-login | wc -l 513 ----8<-------------------- I realise that the 'imap-login' process also works as a IMAP proxy and that it stays alive during the entire session of the client since it handles the TLS part of the connection. However there are nowhere near 512 connections active. As far as I know IMAP doesn't support multiplexing (ie. multiple IMAP sessions in a single TCP connection) so with 512 imap-login proccess I would expect to see a lot more connections then I'm seeing: ----8<-------------------- # netstat -a TCP: IPv4 Local Address Remote Address Swind Send-Q Rwind Recv-Q State -------------------- -------------------- ------ ------ ------ ------ ----------- *.ssh *.* 0 0 1048576 0 LISTEN dovecot-1.inst.sp-prod.nl1.cns.supersecretcorp.nl.imaps 52.XXX.XXX.XXX.53136 178176 0 1049580 0 ESTABLISHED dovecot-1.inst.sp-prod.nl1.cns.supersecretcorp.nl.imaps 52.XXX.XXX.XXX.53188 126848 0 1049580 0 ESTABLISHED dovecot-1.inst.sp-prod.nl1.cns.supersecretcorp.nl.imaps 83.XXX.XXX.XXX.64845 132352 0 1048960 0 ESTABLISHED dovecot-1.inst.sp-prod.nl1.cns.supersecretcorp.nl.imaps 10.100.2.2.7937 16384 0 1049800 0 CLOSE_WAIT dovecot-1.inst.sp-prod.nl1.cns.supersecretcorp.nl.imaps 10.100.2.3.4983 16384 0 1049800 0 CLOSE_WAIT dovecot-1.inst.sp-prod.nl1.cns.supersecretcorp.nl.imaps 10.100.2.2.34369 16384 0 1049800 0 CLOSE_WAIT dovecot-1.inst.sp-prod.nl1.cns.supersecretcorp.nl.imaps 10.100.2.3.15041 16384 0 1049800 0 CLOSE_WAIT dovecot-1.inst.sp-prod.nl1.cns.supersecretcorp.nl.imaps 10.100.2.2.49044 16384 0 1049800 0 CLOSE_WAIT dovecot-1.inst.sp-prod.nl1.cns.supersecretcorp.nl.imaps 10.100.2.3.6340 16384 0 1049800 0 CLOSE_WAIT dovecot-1.inst.sp-prod.nl1.cns.supersecretcorp.nl.imaps 10.100.2.2.11331 16384 0 1049800 0 CLOSE_WAIT dovecot-1.inst.sp-prod.nl1.cns.supersecretcorp.nl.imaps 52.XXX.XXX.XXX.49920 94976 0 1049580 0 ESTABLISHED dovecot-1.inst.sp-prod.nl1.cns.supersecretcorp.nl.58569 10.100.3.84.ldap 1049792 0 1049800 0 ESTABLISHED dovecot-1.inst.sp-prod.nl1.cns.supersecretcorp.nl.33749 10.100.3.84.ldap 1049792 0 1049800 0 ESTABLISHED dovecot-1.inst.sp-prod.nl1.cns.supersecretcorp.nl.imaps 52.XXX.XXX.XXX.49966 46464 0 1049580 0 ESTABLISHED *.4190 *.* 0 0 1048576 0 LISTEN *.24 *.* 0 0 1048576 0 LISTEN *.imap2 *.* 0 0 1048576 0 LISTEN *.imaps *.* 0 0 1048576 0 LISTEN dovecot-1.inst.sp-prod.nl1.cns.supersecretcorp.nl.imaps ec2-54-210-254-232.compute-1.amazonaws.com.32892 107904 0 1049800 0 ESTABLISHED dovecot-1.inst.sp-prod.nl1.cns.supersecretcorp.nl.ssh 10.101.2.14.59256 64128 35 1049880 0 ESTABLISHED dovecot-1.inst.sp-prod.nl1.cns.supersecretcorp.nl.imaps ec2-54-167-34-137.compute-1.amazonaws.com.3890 549632 0 1049800 0 ESTABLISHED TCP: IPv6 Local Address Remote Address Swind Send-Q Rwind Recv-Q State If --------------------------------- --------------------------------- ------ ------ ------ ------ ----------- ----- *.ssh *.* 0 0 1048576 0 LISTEN Active UNIX domain sockets Address Type Vnode Conn Local Address Remote Address ----8<-------------------- This is the running Dovecot config: ----8<-------------------- # doveconf -n -c /etc/dovecot/dovecot.conf # 2.3.9.2 (cf2918cac): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.9 (db4e9a2f) # OS: SunOS 5.11 i86pc # Hostname: dovecot-1.inst.sp-prod.nl1.cns.supersecretcorp.nl auth_failure_delay = 3 secs auth_mechanisms = plain oauthbearer xoauth2 base_dir = /var/run/dovecot/ disable_plaintext_auth = no first_valid_uid = 1000 hostname = imap.supersecretcorp.nl instance_name = dovecot-1 listen = * lmtp_rcpt_check_quota = yes log_path = /dev/stderr mail_attachment_dir = /var/lib/dovecot/attachments mail_attachment_fs = sis-queue /var/lib/dovecot/attachments/queue:posix mail_attachment_hash = %{sha256} mail_attribute_dict = file:~/mdbox/dovecot-attributes mail_gid = vmail mail_home = /var/lib/dovecot/vmail/%d/%n mail_location = mdbox:~/mdbox mail_plugins = " quota notify" mail_server_admin = mailto:it@ask.supersecretcorp.nl mail_temp_dir = /var/lib/dovecot/tmp mail_uid = vmail managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date index ihave duplicate mime foreverypart extracttext metric imap_command_fetch_ok { event_name = imap_command_finished filter { name = FETCH tagged_reply_stat = OK } } metric imap_command_list { event_name = imap_command_finished filter { name = LIST tagged_reply_state = OK } } metric imap_command_search { event_name = imap_command_finished filter { name = SEARCH tagged_reply_stat = OK } } metric imap_command_select { event_name = imap_command_finished filter { name = SELECT tagged_reply_state = OK } } metric imap_select_no { event_name = imap_command_finished filter { name = SELECT tagged_reply_state = NO } } metric imap_select_no_notfound { event_name = imap_command_finished filter { name = SELECT tagged_reply = NO*Mailbox doesn't exist:* } } metric storage_http_gets { categories = storage event_name = http_request_finished filter { method = get } } 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 "Sent objects" { special_use = \Sent } mailbox Spam { special_use = \Junk } mailbox Trash { special_use = \Trash } prefix = separator = / subscriptions = yes type = private } passdb { args = /etc/dovecot/dovecot-oauth2.conf.ext driver = oauth2 mechanisms = oauthbearer xoauth2 } passdb { args = /etc/dovecot/dovecot-ldap-passdb.conf.ext driver = ldap } plugin { push_notification_driver = ox:url=http://#hidden_use-P_to_show#@open-xchange.svc.sp-prod.nl1.cns.supersecretcorp.nl:8009/preliminary/http-notify/v1/notify user_from_metadata quota = count:User quota quota_rule2 = Trash:storage=+25M quota_vsizes = yes sieve = file:~/sieve;active=~/.dovecot.sieve sieve_max_actions = 32 sieve_max_redirects = 4 sieve_max_script_size = 1M sieve_quota_max_scripts = 500 sieve_quota_max_storage = 10M sieve_vacation_send_from_recipient = yes } postmaster_address = postmaster(a)supersecretcorp.nl protocols = imap lmtp sieve service auth-worker { user = $default_internal_user } service auth { unix_listener auth-userdb { group = vmail mode = 0770 user = dovecot } user = $default_internal_user } service imap-login { process_limit = 512 process_min_avail = 1 service_count = 1 } service imap { process_limit = 512 } service lmtp { inet_listener lmtp { address = * port = 24 } user = vmail } service managesieve-login { inet_listener sieve { port = 4190 } process_min_avail = 0 service_count = 1 } service managesieve { process_limit = 256 } service stats { unix_listener stats-reader { group = vmail mode = 0660 user = vmail } unix_listener stats-writer { group = vmail mode = 0660 user = vmail } } ssl_client_ca_dir = /opt/local/etc/openssl/certs ssl_dh = # hidden, use -P to show it ssl_min_protocol = TLSv1.2 submission_host = postfix.svc.sp-prod.nl1.cns.supersecretcorp.nl:25 userdb { args = /etc/dovecot/dovecot-ldap-userdb.conf.ext driver = ldap } protocol imap { mail_plugins = " quota notify imap_quota" ssl_cert = </etc/dovecot/pki/imap.supersecretcorp.nl.crt ssl_key = # hidden, use -P to show it } protocol submission { ssl_cert = </etc/dovecot/pki/smtp.supersecretcorp.nl.crt ssl_key = # hidden, use -P to show it } protocol lmtp { mail_plugins = quota sieve notify push_notification postmaster_address = postmaster(a)supersecretcorp.nl } remote 10.100.2.0/23 { protocol imap { imap_metadata = yes } } ----8<-------------------- Hoping anyone can offer any insights! Kind regards, Jasper

1 0

Lookup master userdb used with GSSAPI causes auth-worker to report "Error: BUG: PASSL had invalid passdb ID"
by Filip Matijević 25 Jan '20

25 Jan '20

Hello to everybody, I'm in the process of setting up test mail server (Ubuntu 19.10 amd64 running as VM under Hyper-V) and got stuck on configuring master user authentication. I use GSSAPI authentication in parallel with PLAIN/LOGIN (pam backend that authenticates against my Active Directory domain) and this works as intended. I then tried adding simple static master passdb that simply returns nopassword='y' and k5principals=... for test and it also works OK. Sadly, using any other backend (I've tried lua and sql) for master passdb instead of static in combination with GSSAPI client causes auth-worker to report "Error: BUG: PASSL had invalid passdb ID". I took a look at the code and my best guess is that in case of GSSAPI + sql/lua master passdb we end up with call to auth_worker_handle_passl with id that auth_worker_handle_passl considers invalid. Continuing with guesswork, I imagine that since GSSAPI doesn't really need passdb in config "virtual" passdb is generated "on the fly" in code. I even tried explicitly defining static passdb with mechanisms set to gssapi to try to force dovecot to use that one instead but it didn't make any difference. At the same time, below configuration works OK when client authenticates with plain/login. dovecot -n (some settings omitted for brevity): # 2.3.4.1 (f79e8e7e4): /etc/dovecot/dovecot.conf auth_gssapi_hostname = $ALL auth_krb5_keytab = /etc/dovecot/dovecot.keytab auth_master_user_separator = * auth_mechanisms = plain login gssapi passdb { args = /etc/dovecot/dovecot-sql-master.conf driver = sql master = yes } passdb { driver = pam } userdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } Any help is appreciated, even if it requires code changes - I can set up machine with everything needed for building/debugging the source code. Thanks, Filip

1 0

sieve size match with multiple of 4GB not matching (BUG?)
by Matthias Lay 24 Jan '20

24 Jan '20

Hi, I have noticed a strange behaviour when using size matches with GB in sieve. If I use filter that matches mails smaller then 4, or 8GB it does not match in any case. same filter matches with 3,5,6,7 GB example filter: require "vnd.dovecot.debug"; if allof (size :under 4G) { debug_log "MATCH"; } else { debug_log "NO MATCH"; } # sieve-filter -u johnd filter.sieve INBOX >> Filtering message: ID: <5167DFC8.8040207@XXXXXX> Date: Fri, 12 Apr 2013 12:19:52 +0200 Size: 1820898 bytes Subject: Fwd: Multi-media mail demonstration info: DEBUG: NO MATCH. ************************************************************************** same mail with this sieve rule: if allof (size :under 5G) { debug_log "MATCH"; } else { debug_log "NO MATCH"; } # sieve-filter -u johnd filter.sieve INBOX >> Filtering message: ID: <5167DFC8.8040207@XXXXXX> Date: Fri, 12 Apr 2013 12:19:52 +0200 Size: 1820898 bytes Subject: Fwd: Multi-media mail demonstration info: DEBUG: MATCH. same for M. 4096M => NO MATCH 4097M => MATCH Greetz Matze

1 0

Re: Namespace problem? duplicated folders...
by Daniel Miller 24 Jan '20

24 Jan '20

And I should have seen that from your first post but output from "doveconf" is definitive. -- Daniel On 1/23/2020 6:57 PM, Daniel Miller wrote: > Keeping in mind I'm 0% Dovecot certified and 100% certifiable... > > I'm guessing you have your namespace definition separate from your > special-use mailbox declarations. Possibly in 10-mail.conf and > 15-mailboxes.conf? Not that it matters. > > First sugggestion - that first namespace definition. Change it from: > > namespace { > > to > > namespace inbox { > > and see what happens. > > -- > Daniel > > > On 1/23/2020 4:40 PM, Gregory Sloop wrote: >> >> >> *DM> Interesting. >> >> DM> While I don't use mbox (dbox or maildir) I wouldn't think that would >> DM> matter. Your namespace layout looks nearly the same as my own. But to >> DM> verify what's going on - post the output of "doveconf namespace". >> >> DM> Possibly just reviewing that output may tell you enough - otherwise >> DM> share it (fully) here. >> >> DM> -- >> DM> Daniel >> >> *namespace { >> disabled = no >> hidden = no >> ignore_on_failure = no >> inbox = yes >> list = yes >> location = >> order = 0 >> prefix = INBOX/ >> separator = / >> subscriptions = yes >> type = private >> } >> namespace inbox { >> disabled = no >> hidden = no >> ignore_on_failure = no >> inbox = no >> list = yes >> location = >> mailbox Drafts { >> auto = no >> autoexpunge = 0 >> comment = >> driver = >> special_use = \Drafts >> } >> mailbox Junk { >> auto = no >> autoexpunge = 0 >> comment = >> driver = >> special_use = \Junk >> } >> mailbox Sent { >> auto = no >> autoexpunge = 0 >> comment = >> driver = >> special_use = \Sent >> } >> mailbox "Sent Messages" { >> auto = no >> autoexpunge = 0 >> comment = >> driver = >> special_use = \Sent >> } >> mailbox Trash { >> auto = no >> autoexpunge = 0 >> comment = >> driver = >> special_use = \Trash >> } >> order = 0 >> prefix = >> separator = >> subscriptions = yes >> type = private >> } >> > >

1 0

wrong Messages in virtual Folder
by Frank-Ulrich Sommer 24 Jan '20

24 Jan '20

Hello, I created a virtual Folder that should contain all Mails from several different Folders and their subfolders. Recently I added a new folder to the dovecot-virtual file and then found that most Mails from this folder were missing. I always restartet dovecot (is this necessary?) after any change. The system is running Debian Stretch and I am using the supplied dovecot 2.2.7 (see below for output of doveconf -n). To narrow this down I removed all other directories from the dovecot-virtual file and then found that the number of mails is correct, but most mails are the wrong ones from other directories. The dovecot-virtual file currently contains only the source directory and in the last line 4 spaces followed by the keyword "all" and a newline. Mails that where moved there after the directory was added to the virtual folder seemed to be displayed correct. If I move one Mail away from the source diectory a totally different Mail in the virtual Folder disappers. After moving the file back to the source folder it correctly appears in the virtual folder. What might be the cause and how can I fix it? Thanks, Frank Output of "doveconf -n": # 2.2.27 (c0f36b0): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.16 (fed8554) # OS: Linux 4.9.0-11-amd64 x86_64 Debian 9.11 zfs auth_verbose = yes log_path = /var/log/dovecot.log mail_location = maildir:/home/bananamail/Maildir:INDEX=/var/dovecot_indexes/%u mail_plugins = " virtual fts fts_solr" mailbox_list_index = yes managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date index ihave duplicate mime foreverypart extracttext namespace { location = virtual:~/Maildir/virtual prefix = _virtual. separator = . type = private } namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { args = scheme=CRYPT username_format=%u /etc/dovecot/users driver = passwd-file } plugin { fts = solr fts_autoindex = yes fts_enforced = yes fts_solr = break-imap-search url=http://localhost:8080/solr/ sieve = file:~/sieve;active=~/.dovecot.sieve } postmaster_address = postmaster@localhost protocols = imap service imap-login { inet_listener imaps { port = XXXX ssl = yes } } ssl = required ssl_cert = <XXXXXXXXX/fullchain.pem ssl_cipher_list = ALL:!LOW:!SSLv2:!SSLv3:!EXP:!aNULL ssl_dh_parameters_length = 2048 ssl_key = # hidden, use -P to show it ssl_protocols = !SSLv3 !TLSv1 userdb { args = username_format=%u /etc/dovecot/users driver = passwd-file } protocol imap { mail_max_userip_connections = 200 }

1 0

intermittant passdb error
by NeuralNET 23 Jan '20

23 Jan '20

I'm having great difficulty debugging this problem.. I'm having intermittant problems connecting to dovecot. This started a couple of days ago following an apt-get update on the server. I'm running Ubuntu 14.04, dovecot 2.2.9. Here's my dovecot -n --- # 2.2.9: /etc/dovecot/dovecot.conf # OS: Linux 3.19.0-59-generic x86_64 Ubuntu 14.04.4 LTS auth_mechanisms = plain login mail_location = maildir:~/Maildir namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { driver = pam } plugin { sieve_dir = ~/sieve } protocols = imap service auth { unix_listener /var/spool/postfix/private/auth { mode = 0666 } user = $default_internal_user } ssl = required ssl_cert = </etc/dovecot/box.neuralnet.org.uk_crt.pem ssl_key = </etc/dovecot/box.neuralnet.org.uk_key.pem ssl_protocols = !SSLv2 !SSLv3 userdb { driver = passwd } --- Pretty standard stuff. In addition disable_plaintext_auth = yes is set in 10-auth.conf This showed up in the mail.err after the reboot; --- May 17 09:04:51 server dovecot: imap-login: Error: read(anvil) failed: EOF May 17 09:04:51 server dovecot: auth: Error: read(anvil-auth-penalty) failed: EOF May 17 09:04:51 server dovecot: auth: Error: net_connect_unix(anvil-auth-penalty) failed: Permission denied --- At that point The following commands were run on the server a few minutes apart with no changes made in the interim; --- username@box /etc/dovecot $ doveadm user username field valueuserdb lookup: user username doesn't exist username@box /etc/dovecot $ doveadm user username field value uid 1000 gid 1000 home /home/username mail maildir:~/Maildir system_groups_user username --- so, passdb wasn't accessible, but now it is ? Imap logins are showing in mail.log as failing, but thunderbird is currently connected; --- May 18 12:00:58 box dovecot: imap-login: Disconnected (auth failed, 3 attempts in 19 secs): user=<username>, method=PLAIN, rip=10.0.0.3, lip=10.0.0.99, TLS, session=<********> May 18 12:08:27 box dovecot: imap-login: Disconnected (auth failed, 3 attempts in 20 secs): user=<username>, method=PLAIN, rip=10.0.0.3, lip=10.0.0.99, TLS, session=<********> May 18 12:08:50 box dovecot: imap-login: Disconnected (auth failed, 3 attempts in 12 secs): user=<username>, method=PLAIN, rip=10.0.0.3, lip=10.0.0.99, TLS, session=<********> --- do I conclude that method=plain is failing, whereas method=login succeeds ? I tried setting auth_debug_password=yes and get the following; --- May 18 12:26:42 box dovecot: auth: Debug: client in: CONT#0111#011A********== (previous base64 data may contain sensitive data) May 18 12:26:42 box dovecot: auth-worker(12214): Debug: Loading modules from directory: /usr/lib/dovecot/modules/auth May 18 12:26:42 box dovecot: auth-worker(12214): Debug: pam(expert,10.0.0.3): lookup service=dovecot May 18 12:26:42 box dovecot: auth-worker(12214): Debug: pam(expert,10.0.0.3): #1/1 style=1 msg=Password: May 18 12:26:42 box dovecot: auth-worker(12211): pam(username,10.0.0.3): pam_authenticate() failed: Authentication failure (password mismatch?) (given password: ******) May 18 12:26:44 box dovecot: auth: Debug: client passdb out: FAIL#0112#011user=username --- Any assistance debugging this further is greatly recieved! Thanks.

2 2

Bug: Regex doesn't match ungreedy
by Lorenz Steinert 23 Jan '20

23 Jan '20

Hello, first the mandatory dovecot specs: - dovecot 2.3.9.2-1 - Operating system: Archlinux - x84 cpu - ext4 filesystem My problem is that the sieve regex filter doesn't seem to match ungreedely so the regex: ^(Re: |)\\[(.*?)\\/(.*?)\\] evaluates the last capturing group of [matrix-org/synapse] [Don't merge!!] Backport fix for MAU limits to v1.8.0 (#6763) to synapse] [Don't merge!! wich should have been synapse Best Regards Lorenz Steinert

2 1

Is it possible to enable push notifications for iOS/macOS mail clients on a stock dovecot?
by Gerben Wierda 23 Jan '20

23 Jan '20

Now that Apple has abandoned mail server capabilities in macOS Server.app we have to move to an open source solution. I have done this using Macports and it works well (no thanks to Apple as it never published the in 2018 promised migration info for mail services). The MacPorts Apple Push Notification variant based on a patch written a few years ago for dovecot supports APNS but it requires you to export a certificate form your old High Sierra Server.app. With the patch and that certificate, dovecot tells an email client it supports XAPPLEPUSHSERVICE and that makes Apple mail clients think they are talking to macOS Server and they switch to push notifications for updates. Now, that certificate needs to be renewed yearly by Server.app and imported by hand etc. At some point this will stop working (apart from that you need to keep an old macOS Server around to renew) Is there another way to get this working with an open source dovecot, outside of using Apple’s push notification service? Some other standard? Some other service? Probably not, right? G

5 5

Using dsync for a single mailbox?
by Wim Lewis 23 Jan '20

23 Jan '20

Is it possble to use `doveadm sync` to migrate a single mailbox? I'm migrating accounts from another IMAP server,and most of the mailboxes are in mbox or maildir format, but a few are in MBX. As far as I can tell the only recommended way to "convert" an MBX mailbox is to sync it via imap. But dsync fails in inscrutable ways, and the documentation is kind of scant on how to control what it does. Even just an example command line showing how to copy remote mailbox FOO into dovecot mailbox BAR would be extremely helpful.

2 4

Dovecot - Upgrade Solr 7.7.2 to 8.4.1
by Domenico Pastore 23 Jan '20

23 Jan '20

Hello, I have Dovecot configured with Solr for the indexes. I have need your support for upgrade solr 7.7.2 to 8.4.1. Solr 7.7.2 has a security issue CVE-2019-12409. It's possible upgrade of Solr? Dovecot work correctly with Solr 8.x? The Solr documentation recommended after updating: "It is always strongly recommended that you fully reindex your documents after a major version upgrade." There are tips for Dovecot? Br, Domenico

4 4