- dovecot - dovecot.org

Dovecot installation problem (libssl_iostream_openssl.so is not portable!)
by Dimitri 31 Jan '22

31 Jan '22

Hi there, i try to install dovecot from source with the following configuration: > ./configure --prefix=/test/core/dovecot --with-ssldir=/test/core/dovecot/tls the configuration runs fine with the following output at the end: > Install prefix . : /test/core/dovecot > File offsets ... : 64bit > I/O polling .... : epoll > I/O notifys .... : inotify > SSL ............ : yes (OpenSSL) > GSSAPI ......... : no > passdbs ........ : static passwd passwd-file shadow checkpassword > : -pam -bsdauth -ldap -sql > userdbs ........ : static prefetch passwd passwd-file checkpassword > : -ldap -sql > CFLAGS ......... : -std=gnu99 -g -O2 -fstack-protector-strong -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -mfunction-return=keep -mindirect-branch=keep -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -fno-builtin-strftime -Wstrict-aliasing=2 -I/test/dep/openssl/include > SYSTEMD ........ : notify - /lib/systemd/system/dovecot.service > SQL drivers .... : > : -pgsql -mysql -sqlite -cassandra > Full text search : squat > : -lucene -solr But when i start to build (make) after a while i get the following error: > *** Warning: Linking the executable test-iostream-ssl against the loadable module > *** libssl_iostream_openssl.so is not portable! > libtool: link: gcc -std=gnu99 -g -O2 -fstack-protector-strong -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -mfunction-return=keep -mindirect-branch=keep -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -fno-builtin-strftime -Wstrict-aliasing=2 -I/test/dep/openssl/include -o .libs/test-iostream-ssl test-iostream-ssl.o ./.libs/libssl_iostream_openssl.so ./.libs/libssl_iostream.a ../lib-test/.libs/libtest.a ../lib/.libs/liblib.a -L/test/dep/openssl/lib64 -lssl -lcrypto -ldl -Wl,-rpath -Wl,/test/core/dovecot/lib/dovecot > /usr/bin/ld: ./.libs/libssl_iostream_openssl.so: undefined reference to `ERR_free_strings' > /usr/bin/ld: ./.libs/libssl_iostream_openssl.so: undefined reference to `ENGINE_cleanup' > /usr/bin/ld: ./.libs/libssl_iostream_openssl.so: undefined reference to `SSL_library_init' > /usr/bin/ld: ./.libs/libssl_iostream_openssl.so: undefined reference to `OBJ_cleanup' > /usr/bin/ld: ./.libs/libssl_iostream_openssl.so: undefined reference to `CRYPTO_cleanup_all_ex_data' > /usr/bin/ld: ./.libs/libssl_iostream_openssl.so: undefined reference to `OpenSSL_add_all_algorithms' > /usr/bin/ld: ./.libs/libssl_iostream_openssl.so: undefined reference to `SSL_CTX_set_tmp_rsa_callback' > /usr/bin/ld: ./.libs/libssl_iostream_openssl.so: undefined reference to `EVP_cleanup' > /usr/bin/ld: ./.libs/libssl_iostream_openssl.so: undefined reference to `SSL_load_error_strings' > /usr/bin/ld: ./.libs/libssl_iostream_openssl.so: undefined reference to `SSL_CTX_need_tmp_RSA' > collect2: error: ld returned 1 exit status > make[3]: *** [Makefile:655: test-iostream-ssl] Error 1 > make[3]: Leaving directory '/test/tmp/dovecot-2.3.17.1/src/lib-ssl-iostream' > make[2]: *** [Makefile:573: all-recursive] Error 1 > make[2]: Leaving directory '/test/tmp/dovecot-2.3.17.1/src' > make[1]: *** [Makefile:702: all-recursive] Error 1 > make[1]: Leaving directory '/test/tmp/dovecot-2.3.17.1' > make: *** [Makefile:546: all] Error 2 I've searched for the error and find some posts about set explicitly CPPFLAGS and LDFLAGS and something about missing shared libraries of openssl. My openssl have shared libraries (libcrypto.so libssl.so ...) and the explicit use of CPPFLAGS and LDFLAGS to my openssl hasn't changed anything I use Openssl 3.0 but i've tested also 1.1.1m and 1.1.1g for example, same error! Dovecot is the latest 2.3.17.1 My OS is Ubuntu 21.04 Can anyone help me with this please? Thanks!

2 1

Sync via ssh fails when ssl is active
by Johan 31 Jan '22

31 Jan '22

I have computers at two different locations and one computer running dovecot at each place. I sync my emails between these two servers using ssh and I haven't had any problems with this lately until I upgraded dovecot recently. I now get the following error at location "alfa" when trying to sync with dovecot at location "delta" Jan 20 16:13:09 doveadm: Error: doveconf: Fatal: Error in configuration file /etc/dovecot/conf.d/10-ssl.conf line 16: ssl_cert: Can't open file /etc/letsencrypt/live/delta.oxyl.net/fullchain.pem: Permission denied Jan 20 16:13:09 dsync-local(johan(a)oxyl.net)<FWBVNQN86WH52iQA1AGq6A>: Error: read(vmail(a)192.168.119.12) failed: EOF (version not received) Jan 20 16:13:09 dsync-local(johan(a)oxyl.net)<FWBVNQN86WH52iQA1AGq6A>: Error: Remote command returned error 89: ssh -q -p 22 -o StrictHostKeyChecking=no -i /datastorage/epost/vmail/.ssh/id_ecdsa -lvmail 192.168.119.12 doveadm dsync-server -ujohan(a)oxyl.net Trying to sync from "delta" i get the same error but the domain is changed in the error-message to 'alfa.oxyl.net' I can read mail at both locations using STARTTLS. There is no error in dovecot.log when I restart the service. If I disable ssl and comment out ssl_cert/ssl_key in 10-ssl.conf I have no trouble performing sync between servers. If I run the ssh-command in the error-message as user vmail I get the same ssl-error as above. Any ideas how to solve this? /Johan Pålsson

4 6

Dsync replication - delayed replication (Sync lock)
by Daniel Botting 31 Jan '22

31 Jan '22

Hi, *Our setup:* Two Debian 10 machines that are setup to replicate mail between them, we have round robin DNS setup so a user can connect to either server. *What should happen:* Mail is delivered to either server and replicated across straight away to their mailbox on the other server so it does not matter which one they are connected to they will receive it fairly soon after delivery. *What actually happens:* In some instances the user will experience a delayed receipt of messages if they are not connected to the server that the message is initially delivered to, sometimes the delay is 5/10 minutes, we had a recent support ticket submitted where it was over an hour. Error message seen in mail.err: Sep 1 10:16:15 <host name> dovecot: dsync-local(<username>)<WELSGEERTl8FEAAAZJ7A9A>: Error: Couldn't lock /path/to/mailbox/.dovecot-sync.lock: fcntl(/path/to/mailbox/.dovecot-sync.lock, write-lock, F_SETLKW) locking failed: Timed out after 30 seconds (WRITE lock held by pid 3697) Process 3697 is dovecot/doveadm-server. *Doveconf -n output:* # 2.3.10.1 (a3d0e1171): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.10 (67bf5bd7) # OS: Linux 4.19.0-10-amd64 x86_64 Debian 10.5 # Hostname: <server hostname> auth_verbose = yes default_vsz_limit = 0 doveadm_password = # hidden, use -P to show it first_valid_gid = 8 first_valid_uid = 8 last_valid_gid = 8 last_valid_uid = 8 lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes mail_gid = 8 mail_location = maildir:~/Maildir mail_plugins = " notify replication" mail_uid = 8 managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex im ap4flags copy include variables body enotify environment mailbox date index ihave duplicate mime foreverypart extracttext editheader imapfla gs namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } plugin { mail_replica = tcps:<server being replicated to>:<port being used> sieve = ~/.dovecot.sieve sieve_dir = ~/sieve sieve_extensions = +editheader +imapflags } postmaster_address = postmaster@<domain address> protocols = " imap sieve pop3" replication_max_conns = 12 service aggregator { fifo_listener replication-notify-fifo { user = mail } unix_listener replication-notify { user = mail } } service auth { unix_listener /var/run/dovecot-exim-bridge { mode = 0660 user = Debian-exim } } service doveadm { inet_listener { port = <port being used for replication> ssl = yes } } service imap-login { inet_listener imap { port = 143 } } inet_listener imaps { port = 993 ssl = yes } process_limit = 512 process_min_avail = 4 service_count = 1 } service imap { process_limit = 1024 } service managesieve-login { inet_listener sieve { port = <sieve port> } process_min_avail = 1 service_count = 8 vsz_limit = 256 M } service managesieve { process_limit = 1024 } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { mode = 0666 } } ssl = required ssl_cert = </path/to/ssl/cert/fullchain.pem ssl_cipher_list = ALL:!LOW:!SSLv2:!EXP:!aNULL ssl_client_ca_dir = /etc/ssl/certs ssl_key = # hidden, use -P to show it ssl_min_protocol = TLSv1.2 userdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap override_fields = home=/var/mail/%u uid=mail gid=mail } protocol lda { mail_plugins = " notify replication sieve" } protocol imap { mail_max_userip_connections = 32 mail_plugins = " notify replication" } protocol sieve { mail_max_userip_connections = 10 managesieve_logout_format = bytes=%i/%o managesieve_max_line_length = 65536 } Kind regards Daniel

3 3

NTLM fails: dovecot: auth: Fatal: Unknown authentication mechanism 'NTLM'
by David Koski 31 Jan '22

31 Jan '22

After upgrading Debian to 11 I found Dovecot at version 2.3.13 (89f716dc2). Now auth method NTLM fails and is not even listed: # doveadm pw -l SHA1 SSHA512 SCRAM-SHA-256 BLF-CRYPT PLAIN HMAC-MD5 OTP SHA512 SHA DES-CRYPT CRYPT SSHA MD5-CRYPT PLAIN-MD4 PLAIN-MD5 SCRAM-SHA-1 SHA512-CRYPT CLEAR CLEARTEXT ARGON2I ARGON2ID SSHA256 MD5 PBKDF2 SHA256 CRAM-MD5 PLAIN-TRUNC SHA256-CRYPT SMD5 DIGEST-MD5 LDAP-MD5 /var/log/dovecot.log Jan 22 16:20:32 auth: Fatal: Unknown authentication mechanism 'NTLM' Jan 22 16:20:32 master: Error: service(auth): command startup failed, throttling for 2.000 secs Jan 22 16:20:34 auth: Fatal: Unknown authentication mechanism 'NTLM' Jan 22 16:20:34 master: Error: service(auth): command startup failed, throttling for 4.000 secs Jan 22 16:20:38 auth: Fatal: Unknown authentication mechanism 'NTLM' Jan 22 16:20:38 master: Error: service(auth): command startup failed, throttling for 8.000 secs Jan 22 16:20:46 auth: Fatal: Unknown authentication mechanism 'NTLM' Jan 22 16:20:46 master: Error: service(auth): command startup failed, throttling for 16.000 secs # doveconf -n # 2.3.13 (89f716dc2): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.13 (cdd19fe3) # OS: Linux 5.10.0-11-amd64 x86_64 Debian 11.2 # Hostname: imail.khmfdbyekekelj1rmytwnfh1bc.dx.internal.cloudapp.net auth_mechanisms = plain login ntlm debug_log_path = /var/log/dovecot-debug.log info_log_path = /var/log/dovecot-info.log log_path = /var/log/dovecot.log maildir_stat_dirs = 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 compat { alias_for = hidden = yes inbox = no list = no location = prefix = INBOX. separator = . } namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = separator = . } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { mail_plugins = " quota trash sieve" sieve = file:~/sieve;active=~/.dovecot.sieve } protocols = " imap sieve" service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } unix_listener auth-client { mode = 0660 } } service stats { unix_listener stats-reader { group = vmail mode = 0660 user = vmail } unix_listener stats-writer { group = vmail mode = 0660 user = vmail } } ssl_cert = </etc/letsencrypt/live/imail1.sutinen.com/fullchain.pem ssl_client_ca_dir = /etc/ssl/certs ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } protocol lmtp { mail_plugins = " quota trash sieve" postmaster_address = admin-kosmosisland.com(a)kosmosisland.com } protocol lda { mail_plugins = " quota trash sieve" } Regards, David Koski

3 4

LMTP error on trying to find passwd-file for Postfix recipient validation
by Narcis Garcia 28 Jan '22

28 Jan '22

Hello everyone, I have following configurations (and more) at /etc/dovecot/local.conf in a "/VirtualUserFlatFilesPostfix/" setup : [partial file content begins] protocols = imap pop3 lmtp sieve mail_location = maildir:~/data:INBOX=~/data/.INBOX service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { user = vmail group = vmail mode = 0660 } } protocol lmtp { postmaster_address = postmaster(a)example.net mail_plugins = $mail_plugins sieve } userdb { driver = passwd-file args = username_format=%u /srv/vmail/domains.d/%d/users.d/%n/etc/passwd } passdb { driver = passwd-file args = username_format=%u /srv/vmail/domains.d/%d/users.d/%n/etc/shadow.%Ls } service auth { unix_listener /var/spool/postfix/private/auth { user = postfix group = postfix mode = 0660 } } [/partial file content ends] Everyting works (IMAP mail is stored, IMAP/POP3 mail is retrieved, incoming SMTP mail from Postfix is delivered, Outgoing SMTP senders are authenticated from Postfix~SASL) BUT: When incoming mail goes to a mailbox that does not exist, an error is logged by Dovecot, letter remains at Postfix queue, and no rejection message to sender (here host is /mail.example.net/): [partial]$ cat /var/log/mail.log 2022-01-28T08:52:00.851751+01:00 correo postfix/smtpd[1853]: CFDA63A174B: client=mail.example.com[1.2.3.4] 2022-01-28T08:52:00.872248+01:00 correo postfix/cleanup[1881]: CFDA63A174B: message-id=<83c79ee1-6e2e-4e15-307e-17cdc7e2b814(a)example.com> 2022-01-28T08:52:00.884100+01:00 correo postfix/qmgr[1529]: CFDA63A174B: from=<johndoe(a)example.com>, size=854, nrcpt=1 (queue active) 2022-01-28T08:52:00.884507+01:00 correo postfix/smtpd[1853]: disconnect from mail.example.com[1.2.3.4] ehlo=2 starttls=1 mail=1 rcpt=1 data=1 quit=1 commands=7 2022-01-28T08:52:00.969275+01:00 correo postfix/lmtp[1882]: CFDA63A174B: to=<wronguser(a)example.net>, relay=mail.example.net[private/dovecot-lmtp], delay=0.43, delays=0.35/0.02/0.02/0.05, dsn=4.3.0, status=deferred (host mail.example.net[private/dovecot-lmtp] said: 451 4.3.0 <wronguser(a)example.net> Temporary internal error (in reply to RCPT TO command)) [partial]$ cat /var/log/dovecot.log 2022-01-28 08:52:00 lmtp(1883): Info: Connect from local 2022-01-28 08:52:00 auth: Error: passwd-file(wronguser(a)example.net): stat(/srv/vmail/domains.d/example.net/users.d/wronguser/etc/passwd) failed: Address family not supported by protocol 2022-01-28 08:52:00 lmtp(wronguser(a)example.net)<1883><xbrsNqCg82FbBwAAzZSvjA>: Error: user wronguser(a)example.net: Auth USER lookup failed 2022-01-28 08:52:00 lmtp(1883): Error: Failed to lookup user wronguser(a)example.net: Internal error occurred. Refer to server log for more information. 2022-01-28 08:52:00 lmtp(1883): Info: Disconnect from local: Client has quit the connection (state=READY) Thank you for any help in debugging configuration or suggestion to enhance Postfix/Dovecot parameters. Postfix 3.4 Dovecot 2.3 -- Narcis Garcia __________ I'm using this dedicated address because personal addresses aren't masked enough at this mail public archive. Public archive administrator should fix this against automated addresses collectors.

2 2

Non-unique Message ID in mail messages
by Daniel Ryšlink 28 Jan '22

28 Jan '22

Hello! I apologize for bringing perhaps trivial/well-known matter, but I am interested in your opinion. RFC 5322 clearly states that mail messages SHOULD contain a Message ID identifier, but if the do contain it, it MUST be globally unique. Despite this requirement, I have encountered senders (namely Spamcop) that sends obviously different (albeit related) messages called "Alert" and "Summary" (they are always related to the same incident and have the same Message ID). This creates all sorts of problems when processing these mails, namely with users that have local forwards from one domain to another (our mailserver hosts multiple domains), because for example Dovecot refuses to forward the second message, flagging it as a duplicate. My question to you is - did you also encounter similar incorrect (according to RFC standards) problem, and if so, is there a way to persuade dovecot to perhaps determine the uniqueness of a message by other means than just checking the message ID (i.e. look at other identifiers, Subject, perhaps)? Because according to the log records, Spamcop does not seem to be the only offender. Thanks in advance for any reactions, and if I did something wrong by writing this message, I apologize again in advance. If required, I can provide samples of the Spamcop messages. -- --===============-- --== Best Regards! ==-- --===============-- Daniel Ryšlink Sysadmin @ Quantcom.cz Czech Republic

4 3

Re: dovecot Digest, Vol 225, Issue 71
by David Matthews 28 Jan '22

28 Jan '22

hi Christian >Did the password hash algorithm change between devuan 3 and 4? >You can check that in your /etc/shadow file. As I understand, devuan is pretty much debian without systemd? And that if you were prepared to do a fair bit of work you could start with debian installed, hack it about and end up with something like devuan? I doubt devuan has done anything to deviate from debian at this level and both machines were recently dist-upgraded. Dovecot needed no tinkering with at all on the debian machine. >The start of the password field should be the same something like $6$... > Yes it is on devuan 4. I no longer have anything with devuan 3 to check that, but it shouldn't have changed in a dist-upgrade? Interestingly, although it's the same user and password on both machines, I notice that the hashes in /etc/shadow are not identical after the commencing $6$. But then I don't know how these hashes are derived, so maybe that is not unexpected? -- David Matthews mail(a)dmatthews.org

2 1

Errors: Failed to map transaction log, Corrupted transaction log, imeout (180s) while waiting for lock for transaction log
by absolutely_free＠libero.it 28 Jan '22

28 Jan '22

Hi, no, it is a single mail server, no replication at all. Thank you > Hello > > We only saw such errors with replication between two machines, when new > emails where errornously deliverd to both of them or clients connected > to both simultaniously. > > Do you have such a setup? > Kind regards, > Christian Mack

1 0

doveadm backup : Warning: Deleting mailbox GUID= is missing locally
by Laura Smith 28 Jan '22

28 Jan '22

Hi, As per the docs (https://wiki.dovecot.org/Tools/Doveadm/Sync) I'm presently running doveadm backup multiple times with a view to eventual server migration. I am seeing messages such as this: Warning: Deleting mailbox 'Junk': UID=1826 GUID= is missing locally Is it anything to worry about ? If so, how should I be dealing with it. I also have a further question. It is not clear from the docs what the role of the "-R" flag is in relation to "doveadm backup" ? Surely by definition backup = remote -> local ? Thanks ! Laura

2 3

Question regarding delivery from Postfix via LMTP proxy
by Vlad Sedov 28 Jan '22

28 Jan '22

Hello, I'm using Postfix with Dovecot 2.3.13, and trying to get LMTP proxy to work for authentication and delivery in the following scenario: Incoming Mail -> Postfix (server A) -> LMTP to Dovecot (server A) -> LMTP to Dovecot (server B) I'm using MySQL for authentication. I've created a user on both server A and server B, test(a)domain.tld On server A, host parameter in password_query for test(a)domain.tld is set to server B's address, and proxy_maybe is enabled. Delivery and authentication to Server A works fine. Authentication and IMAP proxy to server B works fine as well. I can connect to IMAP on server A with credentials for test(a)domain.tld and access the maildir on server B. This works surprisingly well, and is about half the battle for me.. What I can't figure out, is how can I get Postfix to deliver mail using LMTP via server A to server B.. Currently, mail still gets delivered to the user's maildir on server A. Is this possible with Dovecot alone, or do I need to use another method to get messages to hop to server B via server A? Any help would be appreciated.. cheers, Vlad

1 0

Re: dovecot Digest, Vol 225, Issue 70
by David Matthews 27 Jan '22

27 Jan '22

hi Christian Same user and password on both machines, users with shell accounts; exactly the same; in fact I'm struggling to see anything different that might be relevant. On one machine dovecot just works on the other, it stopped working after a dist-upgrade. One machine (where it works) is a debian 11 VPS, the other is real PC hardware running devuan 4, but their dovecot is a debian package. I can't see why either of that should matter and dovecot also just worked on the PC with devuan 3. I've tried purging dovecot-core and dovecot-imapd and reinstalling to no effect. > > 1. Re: can't authenticate (Christian Mack) > > >---------------------------------------------------------------------- > >Message: 1 >Date: Thu, 27 Jan 2022 11:42:22 +0100 >From: Christian Mack >christian.mack(a)uni-konstanz.de> >To: dovecot(a)dovecot.org >Subject: Re: can't authenticate >Message-ID: >a2fbca25-75c7-4e19-a084-5e8d4d8cc645(a)uni-konstanz.de> >Content-Type: text/plain; charset="utf-8" > >Hello > >> passdb { >> driver = pam >> } > >Is user fred defined on your development machine? >Does the password match the one from the production machine? > > >Kind regards, >Christian Mack > >On 26.01.22 21:14, David Matthews wrote: >> My live mail exchanger and development machines have identical dovecot setups, yet I cannot login on the development machine:- >> >> dovecot --version >> 2.3.13 (89f716dc2) >> >>> telnet localhost 143 >> Trying 127.0.0.1... >> Connected to bulawayo. >> Escape character is '^]'. >> * OK [CAPABILITY IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE LITERAL+ STARTTLS AUTH=PLAIN] Dovecot (Debian) ready. >> a login fred xxxxxxxxxxx >> a NO [UNAVAILABLE] Temporary authentication failure. [bulawayo:2022-01-26 20:02:14] >> >> same if I try openssl s_client to 993 >> >>> tail /var/log/mail.log >> Jan 26 20:03:28 bulawayo dovecot: imap-login: Disconnected (auth service reported temporary failure): user=>fred>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured, session=>1MRorYHWwOp/AAAB> >> >> doveconf -n >> # 2.3.13 (89f716dc2): /etc/dovecot/dovecot.conf >> # Pigeonhole version 0.5.13 (cdd19fe3) >> # OS: Linux 5.10.0-10-amd64 x86_64 Debian 11.1 >> # Hostname: bulawayo >> mail_location = mbox:~/mail:INBOX=/var/mail/%u >> mail_privileged_group = mail >> namespace inbox { >> inbox = yes >> location = >> mailbox Drafts { >> special_use = \Drafts >> } >> mailbox Junk { >> special_use = \Junk >> } >> mailbox Sent { >> special_use = \Sent >> } >> mailbox "Sent Messages" { >> special_use = \Sent >> } >> mailbox Trash { >> special_use = \Trash >> } >> prefix = >> } >> passdb { >> driver = pam >> } >> protocols = " imap" >> service imap-login { >> inet_listener imap { >> port = 143 >> } >> inet_listener imaps { >> port = 993 >> ssl = yes >> } >> } >> ssl_cert = >/etc/dovecot/private/dovecot.pem >> ssl_client_ca_dir = /etc/ssl/certs >> ssl_dh = # hidden, use -P to show it >> ssl_key = # hidden, use -P to show it >> userdb { >> driver = passwd >> } >> >> -- >> David Matthews >> mail(a)dmatthews.org >> > > >-- >Christian Mack >Universit?t Konstanz >Kommunikations-, Informations-, Medienzentrum (KIM) >Abteilung IT-Dienste Forschung und Lehre >78457 Konstanz >+49 7531 88-4416 > >

2 1

can't authenticate
by David Matthews 27 Jan '22

27 Jan '22

My live mail exchanger and development machines have identical dovecot setups, yet I cannot login on the development machine:- dovecot --version 2.3.13 (89f716dc2) >telnet localhost 143 Trying 127.0.0.1... Connected to bulawayo. Escape character is '^]'. * OK [CAPABILITY IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE LITERAL+ STARTTLS AUTH=PLAIN] Dovecot (Debian) ready. a login fred xxxxxxxxxxx a NO [UNAVAILABLE] Temporary authentication failure. [bulawayo:2022-01-26 20:02:14] same if I try openssl s_client to 993 >tail /var/log/mail.log Jan 26 20:03:28 bulawayo dovecot: imap-login: Disconnected (auth service reported temporary failure): user=<fred>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured, session=<1MRorYHWwOp/AAAB> doveconf -n # 2.3.13 (89f716dc2): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.13 (cdd19fe3) # OS: Linux 5.10.0-10-amd64 x86_64 Debian 11.1 # Hostname: bulawayo mail_location = mbox:~/mail:INBOX=/var/mail/%u mail_privileged_group = mail namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { driver = pam } protocols = " imap" service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } } ssl_cert = </etc/dovecot/private/dovecot.pem ssl_client_ca_dir = /etc/ssl/certs ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it userdb { driver = passwd } -- David Matthews mail(a)dmatthews.org

2 1

Errors: Failed to map transaction log, Corrupted transaction log, imeout (180s) while waiting for lock for transaction log
by absolutely_free＠libero.it 27 Jan '22

27 Jan '22

Hi all, I am using dovecot-2.3.17_1 on FreeBSD system. This server offers webmail, pop3 and imap access for users. Today I am receiving several complaints from users about slowness and/or access issues. I checked on my /var/log/maillog and I see lots of: Error: Timeout (180s) while waiting for lock for transaction log file /var/domains/domain.it/username/Maildir/dovecot.list.index.log (WRITE lock held by pid 84939) Error: Corrupted transaction log file /var/domains/domain.it/otherusername/Maildir/dovecot.list.index.log seq 2: indexid changed: 1643184505 -> 1643205059 (sync_offset=0) Error: Transaction log file /var/domains/otherdomain.net/otheruser/Maildir/dovecot.list.index.log: marked corrupted Not all users seem affected. My mailbox, for example, is working fine. I checked on my disks (this is a ZFS volume) and I didn't find errors/warnings. Any suggestion? This is my dovecot configuration: # dovecot -n # 2.3.17 (e2aa53df5b): /usr/local/etc/dovecot/dovecot.conf # OS: FreeBSD 13.0-RELEASE-p6 amd64 zfs # Hostname: mailserver.domain.it auth_debug = yes auth_mechanisms = plain login auth_verbose = yes default_client_limit = 2000 default_process_limit = 500 default_vsz_limit = 512 M disable_plaintext_auth = no first_valid_gid = 125 first_valid_uid = 125 imap_id_log = * mail_gid = 1003 mail_location = maildir:/mail/domains mail_privileged_group = postfix mail_uid = 1003 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 = /usr/local/etc/dovecot/dovecot-sql-crypt.conf.ext driver = sql } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } unix_listener auth-userdb { group = postfix mode = 0600 user = postfix } } service imap { process_limit = 1536 } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } ssl_cert = </etc/ssl/wildcard.domain.net_bundle.crt ssl_key = # hidden, use -P to show it userdb { args = /usr/local/etc/dovecot/dovecot-sql-crypt.conf.ext driver = sql } protocol imap { mail_max_userip_connections = 100 } Thank you very much

2 1

sieve-filter ignores -u argument
by Андрей Куницын 27 Jan '22

27 Jan '22

Hello I try to test my sieve script, but found out that it is impossible to use a sieve-filter tool with virtual mail users. It always uses a real user name instead of passed via -u argument. # sieve-filter -v -u postmaster(a)domain.tld ~/sieve/managesieve.sieve INBOX sieve-filter(root): Fatal: Unknown user sudo -u vmail sieve-filter -u postmaster(a)domain.tld ~/sieve/managesieve.sieve INBOX sieve-filter(vmail): Fatal: Unknown user Also there is the same question on serverfault, but without an answer. https://serverfault.com/questions/1055407/how-to-make-sieve-filter-use-virt… My environment is Ubuntu 20.04 dovecot --version 2.3.7.2 (3c910f64b) -- Sincerely, Andrey Kunitsyn

4 5

Dovecot installation problem (libssl_iostream_openssl.so is not portable!)
by Dimitri 27 Jan '22

27 Jan '22

Hi there, i try to install dovecot from source with the following configuration: > ./configure --prefix=/test/core/dovecot --with-ssldir=/test/core/dovecot/tls the configuration runs fine with the following output at the end: > Install prefix . : /test/core/dovecot > File offsets ... : 64bit > I/O polling .... : epoll > I/O notifys .... : inotify > SSL ............ : yes (OpenSSL) > GSSAPI ......... : no > passdbs ........ : static passwd passwd-file shadow checkpassword > : -pam -bsdauth -ldap -sql > userdbs ........ : static prefetch passwd passwd-file checkpassword > : -ldap -sql > CFLAGS ......... : -std=gnu99 -g -O2 -fstack-protector-strong -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -mfunction-return=keep -mindirect-branch=keep -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -fno-builtin-strftime -Wstrict-aliasing=2 -I/test/dep/openssl/include > SYSTEMD ........ : notify - /lib/systemd/system/dovecot.service > SQL drivers .... : > : -pgsql -mysql -sqlite -cassandra > Full text search : squat > : -lucene -solr But when i start to build (make) after a while i get the following error: > *** Warning: Linking the executable test-iostream-ssl against the loadable module > *** libssl_iostream_openssl.so is not portable! > libtool: link: gcc -std=gnu99 -g -O2 -fstack-protector-strong -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -mfunction-return=keep -mindirect-branch=keep -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -fno-builtin-strftime -Wstrict-aliasing=2 -I/test/dep/openssl/include -o .libs/test-iostream-ssl test-iostream-ssl.o ./.libs/libssl_iostream_openssl.so ./.libs/libssl_iostream.a ../lib-test/.libs/libtest.a ../lib/.libs/liblib.a -L/test/dep/openssl/lib64 -lssl -lcrypto -ldl -Wl,-rpath -Wl,/test/core/dovecot/lib/dovecot > /usr/bin/ld: ./.libs/libssl_iostream_openssl.so: undefined reference to `ERR_free_strings' > /usr/bin/ld: ./.libs/libssl_iostream_openssl.so: undefined reference to `ENGINE_cleanup' > /usr/bin/ld: ./.libs/libssl_iostream_openssl.so: undefined reference to `SSL_library_init' > /usr/bin/ld: ./.libs/libssl_iostream_openssl.so: undefined reference to `OBJ_cleanup' > /usr/bin/ld: ./.libs/libssl_iostream_openssl.so: undefined reference to `CRYPTO_cleanup_all_ex_data' > /usr/bin/ld: ./.libs/libssl_iostream_openssl.so: undefined reference to `OpenSSL_add_all_algorithms' > /usr/bin/ld: ./.libs/libssl_iostream_openssl.so: undefined reference to `SSL_CTX_set_tmp_rsa_callback' > /usr/bin/ld: ./.libs/libssl_iostream_openssl.so: undefined reference to `EVP_cleanup' > /usr/bin/ld: ./.libs/libssl_iostream_openssl.so: undefined reference to `SSL_load_error_strings' > /usr/bin/ld: ./.libs/libssl_iostream_openssl.so: undefined reference to `SSL_CTX_need_tmp_RSA' > collect2: error: ld returned 1 exit status > make[3]: *** [Makefile:655: test-iostream-ssl] Error 1 > make[3]: Leaving directory '/test/tmp/dovecot-2.3.17.1/src/lib-ssl-iostream' > make[2]: *** [Makefile:573: all-recursive] Error 1 > make[2]: Leaving directory '/test/tmp/dovecot-2.3.17.1/src' > make[1]: *** [Makefile:702: all-recursive] Error 1 > make[1]: Leaving directory '/test/tmp/dovecot-2.3.17.1' > make: *** [Makefile:546: all] Error 2 I've searched for the error and find some posts about set explicitly CPPFLAGS and LDFLAGS and something about missing shared libraries of openssl. My openssl have shared libraries (libcrypto.so libssl.so ...) and the explicit use of CPPFLAGS and LDFLAGS to my openssl hasn't changed anything I use Openssl 3.0 but i've tested also 1.1.1m and 1.1.1g for example, same error! Dovecot is the latest 2.3.17.1 Can anyone help me with this please? Thanks!

1 0

doveadm stateful backup
by Christian 26 Jan '22

26 Jan '22

Hi all, first: I'm using version 2.3.4.1 I manage some rather large imap mailboxes which I want to backup on a regular basis. Some of them have relatively heavy traffic and one of them is greater than 30GB in size. I studied the docs for doveadm backup (https://wiki2.dovecot.org/Tools/Doveadm/Sync) and even did some code research to better understand the process. The docs state that using stateful synchronization is the most efficient way to synchronize mailboxes, therefore I chose this approach. Highlevel overview: - store a copy of the whole maildir in a separate directory (/var/vmail/backup) - backup to this directory once a minute (trying to make most use of transaction logs) using the last state stored within a file - create a backup once a day using tar (full, differential and incremental ones) blocking the backup process of the before mentioned step I quite often receive notifications that doveadm backup returned an exit code of 2, which should be quite normal. These notifications look like that: dsync(another_address(a)my.domain): Warning: Failed to do incremental sync for mailbox INBOX, retry with a full sync (Modseq 171631 no longer in transaction log (highest=177818, last_common_uid=177308, nextuid=177309)) dsync(another_address(a)my.domain): Warning: Mailbox changes caused a desync. You may want to run dsync again: Remote lost mailbox GUID e9149d0ae4e02d532505000026ca4352 (maybe it was just deleted?) Synced another_address(a)my.domain successfully but missing some changes. Took 3 seconds. Starting retry 1... The first message seems to point out that the transaction log got rolled and no more contains the messages from the backup dir, right? I thought about setting mail_index_log_rotate_min_age to 1hour to prevent rolling transaction logs too often, but abandoned this thought and increased the backup interval to once a minute. The warnings still appear so maybe my thoughts about transactions logs are wrong. The second message seems less alarming to me. How does doeveadm backup behave in such situations? Does it directly fall back to a less efficient way of syncing mails? Does the state store the information "retry with a full sync" and the next run uses this mode? To investigate on this I simply measured runtimes an saw that the second/retry run takes a bit longer (up to about 15 seconds) to sync the dir. I'm afraid of losing messages using my approach. Is it safe to always use doveadm backup -s $state? Simply counting one maildirs files within the live directory and the backup copy shows a 100 fewer files within the backup dir although the script runs only since a few days. For reference, see my backup script below. Regards Christian #!/bin/bash # * * * * * /root/bin/backup.sh --sync-only # 12 2 1-7 * * test $(date +\%u) -eq 6 && /root/bin/backup.sh --full # 12 2 8-31 * * test $(date +\%u) -eq 6 && /root/bin/backup.sh --differential # 12 2 * * * test $(date +\%u) -ne 6 && /root/bin/backup.sh synconly=0 differential=0 fullbackup=0 if [ $# -gt 0 ] ; then if [ "$1" == "--sync-only" ] ; then synconly=1 elif [ "$1" == "--differential" ] ; then differential=1 elif [ "$1" == "--full" ] ; then fullbackup=1 fi fi basedir="/var/vmail/backup" targetdir="/var/vmail/backup/done" mailaddresses="one_address(a)my.domain another_address(a)my.domain yet_another(a)my.domain" if [ ! -d "$basedir" ] ; then mkdir -p "$basedir" chown vmail:vmail "$basedir" fi if [ ! -d "$targetdir" ] ; then mkdir -p "$targetdir" chown vmail:vmail "$targetdir" fi for mailaddr in ${mailaddresses} ; do #echo "Creating backup for $mailaddr." domainpart=${mailaddr#*@} localpart=${mailaddr%%@*} lockfile="$basedir/$mailaddr.lock" statefile="$basedir/$mailaddr.state" backupdir="$domainpart/$localpart/Maildir" snapshotfile_full="$basedir/$mailaddr.full.snar" snapshotfile="$basedir/$mailaddr.snar" backup_basename="$basedir/${mailaddr}_$(date '+%Y%m%d_%H%M%S')" ( if [ $synconly -eq 1 ] ; then flock -xn 200 if [ $? -eq 1 ] ; then # failed to acquire lock. Skip mailbox silently. exit fi fi # try to acquire exclusive lock for one minute flock -xw 60 200 if [ $? -eq 1 ] ; then echo "Failed to acquire write lock within 60 seconds. Skipping $mailaddr." exit fi retries=0 retval=1 until [ $retval -eq 0 ] || [ $retries -ge 3 ] ; do let 'retries++' if [ -f "$statefile" ] ; then oldstate=$(head -1 "$statefile") else oldstate="" fi start_time=$(date +%s) ERROR=$((doveadm backup -u "$mailaddr" -s "$oldstate" "maildir:$basedir/$backupdir") 2>&1 > "$statefile") retval=$? end_time=$(date +%s) let 'duration=end_time-start_time' if [ $retval -eq 2 ] ; then #if [ $retries -gt 1 ] ; then echo "$ERROR" echo "Synced $mailaddr successfully but missing some changes. Took $duration seconds. Starting retry $retries..." #fi elif [ $retval -ne 0 ] ; then echo "$ERROR" echo "Syncing $mailaddr failed. Return code $retval. Took $duration seconds. Removing backup directory and starting retry $retries..." rm -rf "$basedir/$backupdir" rm -f "$statefile" "$snapshotfile" elif [ $retries -gt 1 ] ; then echo "Successful sync took $duration seconds." fi done # downgrade lock to shared lock flock -sn 200 [ $synconly -eq 1 ] && exit if [ $retval -ne 0 ] ; then echo "Too many retries. Aborting backup of $mailaddr." exit fi cd "$basedir" if [ $fullbackup -eq 1 ] || [ ! -f "$snapshotfile_full" ] ; then tar -cpzf "${backup_basename}_full.tar.gz" --level=0 -g "$snapshotfile_full" "$backupdir" cp -f "$snapshotfile_full" "$snapshotfile" else suffix="" if [ $differential -eq 1 ] ; then cp -f "$snapshotfile_full" "$snapshotfile" suffix="_diff" fi tar -cpzf "${backup_basename}${suffix}.tar.gz" -g "$snapshotfile" "$backupdir" fi cd - > /dev/null mv "${basedir}/"*.tar.gz "$targetdir" ) 200>"$lockfile" [ $synconly -eq 1 ] && continue # housekeeping newest_full=$(ls -1 "${targetdir}/${mailaddr}_"*_full.tar.gz 2>/dev/null | sort | tail -1) if [ -n "$newest_full" ] ; then #echo "Cleaning up files older than $newest_full..." find "$targetdir" -depth -maxdepth 1 -name "${mailaddr}_*" ! -newer "$newest_full" ! -samefile "$newest_full" -printf 'Deleting %p...\n' -delete fi done

1 1

pop3-login logging double Disconencted
by Noel Butler 26 Jan '22

26 Jan '22

Hi all, Wondering if anyone else is seeing this double Disconnected in the logs with current stable version, it only happens for pop3-login, and only with Too many commands... other pop3-login logging with Disconnected like Connection closed (no auth attempts... etc are fine Example of anomaly - pop3-login: Info: Disconnected: Disconnected: Too many bad commands (no auth attempts in ... If anyone running 2.3.17.1 sees this or does not see it on Too many bad... or at all, kindly mind letting me know, not sure if something has gone haywire here or its a bug that needs reporting since logs indicate this only occurred after updating to the point 1 release. -- Regards, Noel Butler This Email, including attachments, may contain legally privileged information, therefore at all times remains confidential and subject to copyright protected under international law. You may not disseminate this message without the authors express written authority to do so. If you are not the intended recipient, please notify the sender then delete all copies of this message including attachments immediately. Confidentiality, copyright, and legal privilege are not waived or lost by reason of the mistaken delivery of this message.

2 1

noob maildir question
by mikfum 25 Jan '22

25 Jan '22

I would like to ask if it is an acceptable practice to manage messages in the maildir as a file (move them from one folder to another) while dovecot is in stop state thinking that it will be rebuild to the next imap user login thanks for your patience:) mik

5 10

Re: noob maildir question
by mikfum 24 Jan '22

24 Jan '22

thanks ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ Il lunedì 24 gennaio 2022 5:15 AM, Ted Hatfield <ted(a)io-tx.com> ha scritto: > I do this all the time on my server. From one user mailbox to another or > > from one maildir folder to another. On my platform I need to make certain > > owner/group of the moved messages is correct for the user I've moved them > > to. Other than that dovecot appears to re-index on the fly. > > Be aware that this is observed information. Others more knowledgeable may > > have concerns that I'm not aware of or just can't see on my system. > > Ted > > On Mon, 24 Jan 2022, mikfum wrote: > > > I would like to ask if it is an acceptable practice to manage messages in the maildir as a file (move them from > > > > one folder to another) while dovecot is in stop state thinking that it will be rebuild to the next imap user login > > > > thanks for your patience:) > > > > mik

1 0

zlib.read errors after upgrade from 2.3.15 to 2.3.17.1
by Arno Schneider 24 Jan '22

24 Jan '22

After upgrading my mailserver from buster to bullseye and dovecot 2.3.15 to 2.3.17.1 I got the following errors: Jan 22 14:22:32 Warning: doveadm(user1)<2953060><49b0NRQF7GFkDy0ALVPUUA>: mdbox /local/mail/user1/storage: rebuilding indexes Jan 22 14:22:39 Error: doveadm(user2)<2953112><awsPGB8F7GGYDy0ALVPUUA>: dsync(2nd.dovecot.server): read(compress(/local/mail/user2/storage/m.4650)) failed: read(/local/mail/user2/storage/m.4650) failed: zlib.read(/local/mail/user2/storage/m.4650): unexpected EOF at 7038367 (last sent=mail, last recv=mail_request (EOL)) I have 2 dovecot servers in a multi-master configuration. The both servers are synced with dsync and the users are routed through a dovecot directors. Any hints where I can continue to investigate / solve this issue? best regards, arno

1 0

Why would dovecot not be answering
by Ruben Safir 23 Jan '22

23 Jan '22

I am really lost as to why dovecot is not authenticating I have smtpd_sasl_type = dovecot in main.cf and # Postfix smtp-auth unix_listener /var/spool/postfix/private/auth { mode = 0666 user = postfix group = postfix } in /etc/dovecot/conf.d/10-master.conf I want it to authenticate on submition only Everything I read says this should do it, but I am up against a wall. I have no debugging information or log at all to confirm what postfix is doing. -- So many immigrant groups have swept through our town that Brooklyn, like Atlantis, reaches mythological proportions in the mind of the world - RI Safir 1998 http://www.mrbrklyn.com DRM is THEFT - We are the STAKEHOLDERS - RI Safir 2002 http://www.nylxs.com - Leadership Development in Free Software http://www2.mrbrklyn.com/resources - Unpublished Archive http://www.coinhangout.com - coins! http://www.brooklyn-living.com Being so tracked is for FARM ANIMALS and extermination camps, but incompatible with living as a free human being. -RI Safir 2013

3 5

S3 integration w Dovecot
by Martin Olsen 21 Jan '22

21 Jan '22

Good morning, day, evening :P As stated on documentation S3-compatible Storages — Dovecot documentation <https://doc.dovecot.org/configuration_manual/mail_location/obox/s3/> only AWS S3 is officially supported. However, we know that Scality has been successfully integrated at some larger corporations. Particularly curious if anyone has integrated with Pure S3 object storage solution, or any other for that matter? Just looking at some different options. - Sincerely, Martin.

4 3

Stop used or not
by mauric＠gmx.ch 21 Jan '22

21 Jan '22

Sieve scripts running fine, but please what would mean the "Stop", if I have multiple Policy that will run true, I need one stop to finish this per section? if header :is ["from","bcc","to"] ["Email-Address-one", "Email-Address-Two", "and so on"] { fileinto ".\Magic-FolderName"; stop; } thanks

3 4

Upgrade only piegenhole to 0.5.17?
by mauric＠gmx.ch 20 Jan '22

20 Jan '22

Please it's possible to update only piegenhole to 0.5.17, on existing Dovecot installation? Downloading dovecot-2.3-pigeonhole-0.5.17.1 Here I found the update-version, its this the possible way? And why I don't found any Informations on any readme, please point me to the right place. installed version, I think this it's the right view? Please on witch place I can check the Sieve installed module? doveconf | head # 2.3.4.1 (f79e8e7e4): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5 () Also found in file pieg-config /* Define to the version of Pigeonhole for Dovecot. */ #define PIGEONHOLE_VERSION "0.5.4" On Debian 10 I have this installed. dovecot-managesieved 1:2.3.4.1-5+deb10u6 amd64 secure POP3/IMAP server - ManageSie dovecot-sieve 1:2.3.4.1-5+deb10u6 amd64 secure POP3/IMAP server - Sieve filters support also checking the folder /usr/include/dovecot/sieve with intention so found any possible version? Thanks for any update

2 2

sockets created for lmtp
by Mike 20 Jan '22

20 Jan '22

Was recently configuring lmtp to listen in the postfix spool for mail. I set the socket as suggested in the documentation, however, when I look at what sockets were created there was an additional one for dovecot. Since I made the change, my expectation would have been just the one that I set up. I doubt it impacts it negatively, but I wanted to understand if I configured things correctly or not. Thanks. Mike

4 6

FTS Tokenization filters normalizer-icu vs lowercase
by Alessio Cecchi 20 Jan '22

20 Jan '22

Hi, I'm trying to setup fts-flatcurve with tokenization. What are the differences/benefits with "fts_filters = normalizer-icu" vs "fts_filters = lowercase"? Reading the Doc I found about normalizer-icu "This is potentially very resource intensive." and about lowercase "Supports UTF8, when compiled with libicu". So, using lowercase is almost the same that normalizer-icu but faster? FYI for using fts-flatcurve with dovecot RPM packages from repo.dovecot.org you have to rebuild with --with-icu --with-stemmer --with-textcat and related library. Thanks -- Alessio Cecchi Postmaster @ http://www.qboxmail.it https://www.linkedin.com/in/alessice

2 1

Save of messages slow when replica unavailable
by Jörg Faudin Schulz 20 Jan '22

20 Jan '22

We have a setup with a dovecot server + replica. This works fine as long as the replica is available. When the replica is not available for some reason, the clients can work normally with one exception: the saving of sent messages to their inboxes takes ages. Thunderbird times out and complains (and duplicates the message), mail.app just waits until it's done. Is there any setting that helps here? For the time being, I deactivated replication; but this isn't a long time solution. Thank you for all your work&support, appreciating the doc as well.

1 0

dovecot-2.3.17: "Panic: file ioloop.c: line 865"
by Christian Küppers 20 Jan '22

20 Jan '22

Hello, we got the same backtrace in dovecot-ee version 2:2.3.17-8+ubuntu20.04 as Andreas Piper mentioned in November 2021 https://dovecot.org/pipermail/dovecot/2021-November/123468.html after installing dovecot package updates. Panic: file ioloop.c: line 865 (io_loop_destroy): assertion failed: (ioloop == current_ioloop) Error: Raw backtrace: #0 t_askpass[0x7fc609b0eba0] -> #1 backtrace_append[0x7fc609b0ee00] -> #2 backtrace_get[0x7fc609b0ef70] -> #3 i_syslog_error_handler[0x7fc609b1bfa0] -> #4 i_syslog_fatal_handler[0x7fc609b1c0d0] -> #5 i_panic[0x7fc609a6f1af] -> #6 i_error[0x7fc609a72906] -> #7 doveadm_http_server_deinit[0x55abd194af90] -> #8 doveadm_print_stream[0x55abd19447b0] -> #9 doveadm_print_istream[0x55abd1944810] -> #10 expunge_search_args_check[0x55abd1936a00] -> #11 expunge_search_args_check[0x55abd1935860] -> #12 doveadm_dsync_main[0x55abd1932900] -> #13 doveadm_cmd_ver2_to_mail_cmd_wrapper[0x55abd1933890] -> #14 doveadm_cmd_run_ver2[0x55abd1943fb0] -> #15 doveadm_server_deinit[0x55abd1948760] -> #16 io_loop_call_io[0x7fc609b32440] -> #17 io_loop_handler_run_internal[0x7fc609b33a00] -> #18 io_loop_handler_run[0x7fc609b32500] -> #19 io_loop_run[0x7fc609b32680] -> #20 master_service_run[0x7fc609aa4780] -> #21 main[0x55abd1923820] -> #22 __libc_start_main[0x7fc60970efc0] -> #23 _start[0x55abd1923980] Error: doveadm server disconnected before handshake: EOF Command fetch failed for <mailbox>: EOF We got it during doveadm fetch of a mail on multiple mailboxes. Is there any progress on this? Will it be fixed in next release? Kind regards, Christian Küppers Expert Administrator onOffice GmbH Charlottenburger Allee 5 | 52068 Aachen Tel. +49 (0)241 446 86-0 | Fax. +49 (0)241 446 86-250 E-Mail:c.kueppers@onoffice.de| Web:www.onOffice.com Registergericht: Amtsgericht Aachen, HRB 21420 Geschäftsführer: Dipl.-Kfm. Stefan Mantl Prokuristen: Janosch Reuschenbach, Kristina Andresen, Christian Mähringer

2 1

lmtp_save_to_detail_mailbox
by dovecot＠ptld.com 19 Jan '22

19 Jan '22

lmtp_save_to_detail_mailbox: " If the recipient address includes a detail element / role (as in user+detail format), save the message to the detail mailbox. " Im not understanding this, what is the "detail mailbox"? I tried testing this feature by setting "lmtp_save_to_detail_mailbox = yes" and sending an email to user+test(a)example.com. The email still ended up in the default inbox folder. So what does lmtp_save_to_detail_mailbox do or is there another setting that also needs to be set to use this feature?

3 5

Outlook vs. Dovecot experience
by Vladislav Kurz 18 Jan '22

18 Jan '22

Dear colleagues, what is your experience regarding using outlook (2016/365) as IMAP client and dovecot on server side? We have sync issues with outlook vs. cyrus IMAP server, and we consider moving to dovecot. But before that I'd like to hear from others if this combination works well. Especially if users have large and bushy mailboxes (>10 GB, >100 mailboxes), two mailboxes (accounts) on the same server. I don't want to do the migration just to find out that it is general issue of outlook vs. any IMAP server. -- Best regards Vladislav Kurz

7 10

JA3/JA3S as a Dovecot plugin?
by Sidsel Jensen 18 Jan '22

18 Jan '22

Hi We have been looking a bit into JA3 (https://engineering.salesforce.com/tls-fingerprinting-with-ja3-and-ja3s-247… <https://engineering.salesforce.com/tls-fingerprinting-with-ja3-and-ja3s-247…> and https://blog.squarelemon.com/tls-fingerprinting/ <https://blog.squarelemon.com/tls-fingerprinting/> ) for possible threat actor identifications. Roughly speaking you can think of JA3 as the TLS equivalent of the User-Agent string. Has anybody been looking into the possibility of building an open source dovecot JA3 plugin? I’d also like to hear the technical pros/cons of doing so…and perhaps the ethical deliberations also :-) Kind Regards, Sidsel

1 0

FTS flatcurve not index messages when SEARCH run on Virtual Mailboxes
by Alessio Cecchi 18 Jan '22

18 Jan '22

Hi, I'm testing FTS flatcurve plugin in order to understand if I can switch from FTS Solr to flatcurve. In my configuration I have enabled Virtual mailboxes and for search in all folders I just SEARCH on Virtual/All folder. I this (virtual) folder is not indexed with FTS Solr Dovecot start to index it (or all real folders). But with FTS flatcurve when I SEARCH on Virtual/All for the first time the indexer process does not start and the search return empty. Only if I run manually "doveadm index -q -u alessio(a)email.net '*'" flatcurve find messages. Can flatcurve have the same feature as Solr for Virtual mailboxes? Here a sample of my configuration: namespace Virtual { hidden = yes list = no location = virtual:/etc/dovecot/virtual:INDEX=~/Maildir/virtual prefix = Virtual/ separator = / subscriptions = no } namespace inbox { [...] mailbox virtual/All { comment = All my messages special_use = \All } } # cat /etc/dovecot/virtual/All/dovecot-virtual * all Thanks -- Alessio Cecchi Postmaster @ http://www.qboxmail.it https://www.linkedin.com/in/alessice

3 6

Extracting CLIENTID information from checkpassword or postlogin scripting
by Dan Conway 18 Jan '22

18 Jan '22

Hello, When extracting client_id information from the client connection (i.e. setting imap_id_log = *) the information is directly logged by Dovecot as such: ID sent: name=Thunderbird, version=91.5.0 My question is, Is it possible to export/set this information in a checkpassword script or a postlogin script? client_id If|imap_id_retain| <https://doc.dovecot.org/settings/core/#core_setting-imap_id_retain>is enabled this variable is populated with the client ID request as IMAP arglist. I've enabled both checkpassword and postlogin on a test server, as well as 'imap_id_retain' set to 'yes'. I wrote a simple Perl script that dumps everything in %ENV as well as @ARGV for checkpassword and postlogin, but I don't see any occurrences of ID information. I've also tried to see if I could supply that variable in dovecot.conf by setting 'client_id' as a parameter, but that didn't seem to do the trick either. passdb { ... # Doesn't work args = /usr/local/bin/checkpassword.pl client_id # Doesn't work args = /usr/local/bin/checkpassword.pl %{client_id} ... } What am I missing? Is it possible to get these variables into an external script that checkpassword or postlogin executes? Thanks.

3 2

Order of loading and checking userdb on Ubuntu
by Mike 16 Jan '22

16 Jan '22

When using the lmtp service for local delivery, I'd like to change the user lookup to only use the user portion of the email address. I think I do that in the 20-lmtp.conf file, but not exactly sure how. From what I've found on the web, I just need to change the auth_username_format=%n. I feel confident that I'm not doing it right. older posts implied that the order things are loaded is an issue, but not sure if that is the case anymore. My goal is to set username_format for only lmtp. Thanks for any help.

1 1

Wrong timestamp value in name of file
by Ervin Hegedüs 14 Jan '22

14 Jan '22

Hi there, Debian 10, Dovecot 2.3.4 (1:2.3.4.1-5+deb10u6), ext4 mailstore. A user on our server reorganized the sent items: he moved few items from the old sent folder into a new one. After that, he noticed me that he does not see every mail, but when he starts a search, then he finds it. I looked up the mail, and found this situation: # ls -la 1642152396.M997381P21341.mail2\,S\=473164\,W\=479469\:2\,S -rw-r--r-- 1 vmail vmail 473164 aug 24 10:21 '1642152396.M997381P21341.mail2,S=473164,W=479469:2,S' # grep Date '1642152396.M997381P21341.mail2,S=473164,W=479469:2,S' Date: Tue, 24 Aug 2021 10:21:39 +0200 # date -d @1642152396 Fri Jan 14 10:26:36 CET 2022 As you can see that mail had sent on 24 Aug, 2021, but after the reorganization it got a new timestamp with the date of today. I assume the client (iPhone) orders the mail by the name of files - am I right? Why did this happen? How can I fix that? I mean, is there any way to rename this files (a few hundred...) to the "real" timestamp? Thanks, a.

1 0

ssl=required per user?
by Arkadiusz Miśkiewicz 13 Jan '22

13 Jan '22

Can ssl=required be forced on per user setting? Right now I could modify password_query to check if %c (%{secured}) is empty and return appropriate error as "reason" like in https://doc.dovecot.org/configuration_manual/authentication/nologin/#authen… example. Unfortunately password_query is a bit too late. I would like to deny access as soon as possible, so just after user sends his login. (that won't help much in cases when client sends password early like "AUTH PLAIN b64loginpass" but will help in all other cases) user_query doesn't have this capability that password_query it seems. -- Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org )

1 0

Is Diffie-Hellman needed?
by dovecot＠ptld.com 13 Jan '22

13 Jan '22

Is Diffie-Hellman needed on a modern new dovecot setup? ssl_dh is empty by default. Both ssl_cert and ssl_key on my setup are pointing to let's encrypt certs. However i see Diffie-Hellman related warnings in logs: dovecot[1073]: imap-login: Error: Diffie-Hellman key exchange requested, but no DH parameters provided. Set ssl_dh=</path/to/dh.pem Am i causing issues for some users by not setting up ssl_dh or is this something being phased out?

4 6

source code doesn't compile
by Ruben Safir 12 Jan '22

12 Jan '22

I downloaded the dovecot source and it doesn't compile. The install script fails in auth because it makes a file and then tries to make a directory over it make[2]: Entering directory '/home/ruben/src/dovecot-2.3.17.1/src/auth' make[3]: Entering directory '/home/ruben/src/dovecot-2.3.17.1/src/auth' /usr/bin/mkdir -p '/usr/local/lib/dovecot' /bin/sh ../../libtool --mode=install /usr/bin/install -c auth checkpassword-reply '/usr/local/lib/dovecot' libtool: warning: 'libstats_auth.la' has not been installed in '/usr/local/lib/dovecot/old-stats' libtool: install: /usr/bin/install -c .libs/auth /usr/local/lib/dovecot/auth libtool: install: /usr/bin/install -c .libs/checkpassword-reply /usr/local/lib/dovecot/checkpassword-reply /usr/bin/mkdir -p '/usr/local/lib/dovecot/auth' I am running an older version of dovecott and would really like to upgrade it and there is no package for this linux version -- So many immigrant groups have swept through our town that Brooklyn, like Atlantis, reaches mythological proportions in the mind of the world - RI Safir 1998 http://www.mrbrklyn.com DRM is THEFT - We are the STAKEHOLDERS - RI Safir 2002 http://www.nylxs.com - Leadership Development in Free Software http://www2.mrbrklyn.com/resources - Unpublished Archive http://www.coinhangout.com - coins! http://www.brooklyn-living.com Being so tracked is for FARM ANIMALS and extermination camps, but incompatible with living as a free human being. -RI Safir 2013

7 14

Migrate mail_location
by hello＠reox.at 11 Jan '22

11 Jan '22

Hi! I have a dovecot installation, with the following configuration: mail_home = /var/vmail/%d/%n mail_location = maildir:~ I would like to migrate the mail_location to maildir:~/mail, to get around the issues described in the documentation. But I can not really find a good way to do that. I played around with doveadm sync/backup, but I can only copy everything into a new location (i.e. doveadm sync maildir:~/mail), but this does not really untangle the mail_home and location. My other idea was to migrate the maildir manually, i.e. move the maildir related folders and files (new, cur, tmp, all folders starting with a dot and containing itself {new,cur,tmp}, dovecot.* files, subscriptions file) into the ~/mail folder, but I'm not sure if this is a safe method. Is there any safe method to do this using dovecot tools? If the only way is a offline migration, I'm fine with that. Best, Sebastian

2 3

2.17.1 Fatal: master: service(doveadm): child 43879 killed with signal 6 (core dumped)
by Salatiel Filho 10 Jan '22

10 Jan '22

Hi, my dovecot 2.17.1 instance is crashing a lot. Quick question: The coredump should contain some private data, am I correct ? Assuming so, should it be posted on a public maillist? Panic: file dsync-ibc.c: line 166 (dsync_ibc_send_mail_request): assertion failed: (request->guid != NULL || request->uid != 0) ... Fatal: master: service(doveadm): child 43879 killed with signal 6 (core dumped) Using gdb/bt over the coredump I get: Using host libthread_db library "/lib64/libthread_db.so.1". Core was generated by `dovecot/doveadm-server'. Program terminated with signal SIGABRT, Aborted. #0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 50 return ret; (gdb) bt #0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 #1 0x00007f612d382db5 in __GI_abort () at abort.c:79 #2 0x00007f612db04485 in default_fatal_finish (status=0, type=LOG_TYPE_PANIC) at failures.c:459 #3 fatal_handler_real (ctx=<optimized out>, format=<optimized out>, args=<optimized out>) at failures.c:471 #4 0x00007f612dbb10f7 in i_internal_fatal_handler (ctx=<optimized out>, format=<optimized out>, args=<optimized out>) at failures.c:872 #5 0x00007f612db04126 in i_panic (format=format@entry=0x5641e4c16ba8 "file %s: line %d (%s): assertion failed: (%s)") at failures.c:524 #6 0x00005641e4bcfcb2 in dsync_ibc_send_mail_request (ibc=0x5641e50a5990, request=0x5641e51dcc70) at dsync-ibc.c:166 #7 0x00005641e4bfe0bc in dsync_brain_send_mail_request (brain=0x5641e50a8538) at dsync-brain-mails.c:215 #8 dsync_brain_sync_mails (brain=brain@entry=0x5641e50a8538) at dsync-brain-mails.c:418 #9 0x00005641e4bf9ad8 in dsync_brain_run_real (changed_r=0x7ffcd2397a47, brain=0x5641e50a8538) at dsync-brain.c:716 #10 dsync_brain_run (changed_r=0x7ffcd2397a47, brain=0x5641e50a8538) at dsync-brain.c:749 #11 dsync_brain_run (brain=0x5641e50a8538, changed_r=0x7ffcd2397a47) at dsync-brain.c:737 #12 0x00005641e4bfa13e in dsync_brain_run_io (context=0x5641e50a8538) at dsync-brain.c:110 #13 0x00005641e4c0b3c3 in dsync_ibc_stream_input (ibc=0x5641e50a5990) at dsync-ibc-stream.c:232 #14 0x00007f612dbc78ad in io_loop_call_io (io=0x5641e5040510) at ioloop.c:737 #15 0x00007f612dbc8f19 in io_loop_handler_run_internal (ioloop=ioloop@entry=0x5641e4f89ce0) at ioloop-epoll.c:222 #16 0x00007f612dbc7950 in io_loop_handler_run (ioloop=0x5641e4f89ce0) at ioloop.c:789 #17 0x00007f612dbc7ad0 in io_loop_run (ioloop=0x5641e4f89ce0) at ioloop.c:762 #18 0x00005641e4bddafa in cmd_dsync_run_remote (user=<optimized out>, user=<optimized out>) at doveadm-dsync.c:496 #19 cmd_dsync_run (_ctx=0x5641e4f89fe8, user=<optimized out>) at doveadm-dsync.c:703 #20 0x00005641e4bdfc26 in doveadm_mail_next_user (ctx=0x5641e4f89fe8, error_r=0x7ffcd2397de8) at doveadm-mail.c:462 #21 0x00005641e4be0d74 in doveadm_mail_cmd_exec (wildcard_user=0x0, ctx=0x5641e4f89fe8) at doveadm-mail.c:654 #22 doveadm_cmd_ver2_to_mail_cmd_wrapper (cctx=<optimized out>) at doveadm-mail.c:983 #23 0x00005641e4bf17c7 in doveadm_cmd_run_ver2 (argc=argc@entry=10, argv=argv@entry=0x5641e4fa3788, cctx=cctx@entry=0x7ffcd2397f40) at doveadm-cmd.c:465 #24 0x00005641e4bf5d1a in doveadm_cmd_server_run_ver2 (cctx=0x7ffcd2397f40, argv=0x5641e4fa3788, argc=10, conn=0x5641e4f81328) at client-connection-tcp.c:187 #25 doveadm_cmd_handle (cctx=0x7ffcd2397f40, argv=<optimized out>, argc=<optimized out>, cmd_name=<optimized out>, conn=0x5641e4f81328) at client-connection-tcp.c:214 #26 client_handle_command (args=<optimized out>, conn=0x5641e4f81328) at client-connection-tcp.c:284 #27 client_connection_tcp_input (conn=0x5641e4f81328) at client-connection-tcp.c:436 #28 0x00007f612dbc78ad in io_loop_call_io (io=0x5641e4f88ee0) at ioloop.c:737 #29 0x00007f612dbc8f19 in io_loop_handler_run_internal (ioloop=ioloop@entry=0x5641e4f3df40) at ioloop-epoll.c:222 #30 0x00007f612dbc7950 in io_loop_handler_run (ioloop=0x5641e4f3df40) at ioloop.c:789 #31 0x00007f612dbc7ad0 in io_loop_run (ioloop=0x5641e4f3df40) at ioloop.c:762 #32 0x00007f612db39287 in master_service_run (service=0x5641e4f3dda0, callback=<optimized out>) at master-service.c:863 #33 0x00005641e4bd09f2 in main (argc=<optimized out>, argv=<optimized out>) at main.c:124 # 2.3.17.1 (476cd46418): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.17.1 (a1a0b892) # OS: Linux 4.18.0-348.7.1.el8_5.x86_64 x86_64 AlmaLinux release 8.5 (Arctic Sphynx) xfs # Hostname: redacted auth_username_format = %Ln doveadm_password = # hidden, use -P to show it first_valid_uid = 1000 mail_home = /var/spool/imap/%n mail_location = maildir:/var/spool/imap/%n/mail:VOLATILEDIR=/var/spool/imap/%n 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 { list = children location = maildir:/var/spool/imap/redacted/mail/:INDEXPVT=/var/spool/imap/%n/pub-seen-idx/ mailbox * { autoexpunge = 60 days } prefix = redacted/ separator = / subscriptions = no 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 = separator = / } passdb { args = scheme=CRYPT username_format=%n /etc/dovecot/users driver = passwd-file } passdb { args = failure_show_msg=yes dovecot driver = pam } plugin { mail_replica = tcps:10.111.1.1:26 sieve = file:/var/spool/imap/%n/sieve;active=/var/spool/imap/%n/.dovecot.sieve sieve_before = /var/lib/dovecot/sieve.d/ sieve_global = /var/lib/dovecot/sieve.d/ } protocols = imap lmtp sieve replication_dsync_parameters = -d -N -l 60 -U service aggregator { fifo_listener replication-notify-fifo { mode = 0666 user = dovecot } unix_listener replication-notify { mode = 0666 user = dovecot } } service doveadm { inet_listener { port = 26 ssl = yes } } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { mode = 0666 user = dovecot } } ssl = required ssl_cert = </etc/ssl/certs/cluster-redacted.crt ssl_key = # hidden, use -P to show it userdb { args = username_format=%n /etc/dovecot/users default_fields = uid=vmail gid=mail home=/var/spool/imap driver = passwd-file } userdb { driver = passwd override_fields = uid=vmail gid=mail home=/var/spool/imap/%n } protocol lmtp { mail_plugins = " notify replication sieve" } protocol imap { ssl_cert = </etc/ssl/certs/redacted.crt ssl_key = # hidden, use -P to show it } Atenciosamente/Kind regards, Salatiel

1 0

Spamassassin fails
by Hans Brage 10 Jan '22

10 Jan '22

Hi! I've been running a server with Dovecot, Sieve, Spamassassin and getmail to handle my emails for several years now. Just before christmas I did one of these regular updates and since then I got problems with spamassassin. Quite a lot of spam is not been filtered out. I can see a lot of errors like these in the mail-log. spamd: failed to create readable default_prefs: /home/vmail/.spamassassin/user_prefs Vmail is the user that is running my scripts that retrieves email and executes spamc. Any ideas? Regards, Hans

2 3

Dovecot 2.3.17 on FreeBSD 12.2 panic
by Bert JW Regeer 10 Jan '22

10 Jan '22

Hello, I have dovecot 2.3.17 running on FreeBSD 12.2 and it keeps panicking: Jan 10 03:04:07 strida dovecot[55198]: imap(xistence(a)0x58.com)<56382><dx4KlzHVQecmAQKCQwA50VytdgLnsQSr>: Panic: file array.c: line 10 (array_idx_modifiable_i): assertion failed: (idx < array->buffer->used / array->element_size) Jan 10 03:04:07 strida dovecot[55198]: imap(xistence(a)0x58.com)<56382><dx4KlzHVQecmAQKCQwA50VytdgLnsQSr>: Fatal: master: service(imap): child 56382 killed with signal 6 (core not dumped - https://dovecot.org/bugreport.html#coredumps) Ignore the core not dumped, this is happening over and over, and I got one process to core dump: # lldb /usr/local/libexec/dovecot/imap -c imap.core (lldb) target create "/usr/local/libexec/dovecot/imap" --core "imap.core" Core file '/usr/local/vmail/domains/0x58.com/xistence/imap.core' (x86_64) was loaded. (lldb) bt * thread #1, name = 'imap', stop reason = signal SIGABRT * frame #0: 0x0000000011588c2a libc.so.7`__sys_thr_kill + 10 frame #1: 0x0000000011587084 libc.so.7`__raise + 52 frame #2: 0x00000000114fd279 libc.so.7`abort + 73 frame #3: 0x00000000113736f3 libdovecot.so.0`___lldb_unnamed_symbol873$$libdovecot.so.0 + 147 frame #4: 0x0000000011371eaf libdovecot.so.0`___lldb_unnamed_symbol862$$libdovecot.so.0 + 47 frame #5: 0x0000000011372c71 libdovecot.so.0`___lldb_unnamed_symbol864$$libdovecot.so.0 + 33 frame #6: 0x00000000113720bb libdovecot.so.0`i_panic + 187 frame #7: 0x0000000011363d3f libdovecot.so.0`array_idx_modifiable_i + 79 frame #8: 0x0000000011ef7c68 lib20_fts_plugin.so`fts_user_autoindex_exclude + 72 frame #9: 0x0000000011ef550f lib20_fts_plugin.so`fts_mailbox_allocated + 239 frame #10: 0x000000001113ed5a libdovecot-storage.so.0`hook_mailbox_allocated + 154 frame #11: 0x00000000111381e1 libdovecot-storage.so.0`mailbox_alloc + 449 frame #12: 0x0000000001043db4 imap`cmd_select_full + 356 frame #13: 0x000000000104c582 imap`command_exec + 178 frame #14: 0x000000000104ae8a imap`___lldb_unnamed_symbol58$$imap + 58 frame #15: 0x000000000104af91 imap`___lldb_unnamed_symbol58$$imap + 321 frame #16: 0x00000000010499e7 imap`client_handle_input + 471 frame #17: 0x0000000001048178 imap`client_input + 120 frame #18: 0x000000001138ca9f libdovecot.so.0`io_loop_call_io + 111 frame #19: 0x000000001138f45b libdovecot.so.0`io_loop_handler_run_internal + 347 frame #20: 0x000000001138cffa libdovecot.so.0`io_loop_handler_run + 346 frame #21: 0x000000001138ce58 libdovecot.so.0`io_loop_run + 88 frame #22: 0x00000000112f11c8 libdovecot.so.0`master_service_run + 24 frame #23: 0x000000000105a417 imap`main + 1383 frame #24: 0x000000000103bed2 imap`_start + 226 (lldb) ^D I was able to generate a core dump by issue a doveadm command too: (lldb) bt * thread #1, name = 'doveadm', stop reason = signal SIGABRT * frame #0: 0x00000008017b1c2a libc.so.7`__sys_thr_kill + 10 frame #1: 0x00000008017b0084 libc.so.7`__raise + 52 frame #2: 0x0000000801726279 libc.so.7`abort + 73 frame #3: 0x000000080159c6f3 libdovecot.so.0`___lldb_unnamed_symbol873$$libdovecot.so.0 + 147 frame #4: 0x000000080159aeaf libdovecot.so.0`___lldb_unnamed_symbol862$$libdovecot.so.0 + 47 frame #5: 0x000000080159ae71 libdovecot.so.0`default_fatal_handler + 33 frame #6: 0x000000080159b0bb libdovecot.so.0`i_panic + 187 frame #7: 0x000000080158cd3f libdovecot.so.0`array_idx_modifiable_i + 79 frame #8: 0x0000000802236c68 lib20_fts_plugin.so`fts_user_autoindex_exclude + 72 frame #9: 0x000000080223450f lib20_fts_plugin.so`fts_mailbox_allocated + 239 frame #10: 0x0000000801367d5a libdovecot-storage.so.0`hook_mailbox_allocated + 154 frame #11: 0x00000008013611e1 libdovecot-storage.so.0`mailbox_alloc + 449 frame #12: 0x000000080222d5fc lib20_fts_plugin.so`fts_backend_rescan + 60 frame #13: 0x000000080227c1a3 lib20_doveadm_fts_plugin.so`___lldb_unnamed_symbol15$$lib20_doveadm_fts_plugin.so + 99 frame #14: 0x000000000107172f doveadm`___lldb_unnamed_symbol134$$doveadm + 479 frame #15: 0x000000000107252c doveadm`doveadm_cmd_ver2_to_mail_cmd_wrapper + 2492 frame #16: 0x0000000001083c98 doveadm`doveadm_cmd_run_ver2 + 1416 frame #17: 0x00000000010836d7 doveadm`doveadm_cmd_try_run_ver2 + 71 frame #18: 0x0000000001086da3 doveadm`main + 835 frame #19: 0x000000000105fa92 doveadm`_start + 226 (lldb) # doveadm fts rescan -u xistence(a)0x58.com doveadm(xistence(a)0x58.com): Panic: file array.c: line 10 (array_idx_modifiable_i): assertion failed: (idx < array->buffer->used / array->element_size) Abort (core dumped) # dovecot-sysreport Gathering configurations ... grep: The -P option is not supported grep: The -P option is not supported grep: The -P option is not supported Gathering system informations ... Creating archive ... All done! Please report file dovecot-sysreport-strida.0x58.com-1641784164.tar.gz Removing temp files at /tmp/tmp.z5qJkwrW … While reading about fts/fts_squat I came across the page noting it was deprecated. I am running a mail server for myself, and have avoided installing Solr this entire time, but I guess its time to upgrade. In the mean time hopefully this core dump can help figure out what is going on. Bert JW Regeer

2 3

outlook 2019 not working
by postmaster 10 Jan '22

10 Jan '22

Just tried connecting a Windows 10 client with Outlook 2019 but it fail's on both POP3 or IMAP - i knew it was working when i tested it after the server setup about a year ago because i documented everything with screenshots. All other devices we use (Thunderbird, iPhone/iPad, Android devices, RoundCube) are working without any issue, just Outlook won't connect anymore. We don't have much Windows/Outlook experience - any help/hints appreciated. This what i have in the logs, but doesn't see anything that helps: 2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x10, ret=1: before SSL initialization 2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x2001, ret=1: before SSL initialization 2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x2002, ret=-1: before SSL initialization 2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x2001, ret=1: before SSL initialization 2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x2001, ret=1: SSLv3/TLS read client hello 2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x2001, ret=1: SSLv3/TLS write server hello 2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x2001, ret=1: SSLv3/TLS write certificate 2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x2001, ret=1: SSLv3/TLS write key exchange 2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x2001, ret=1: SSLv3/TLS write server done 2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x2002, ret=-1: SSLv3/TLS write server done 2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x2002, ret=-1: SSLv3/TLS write server done 2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x2002, ret=-1: SSLv3/TLS write server done 2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x2002, ret=-1: SSLv3/TLS write server done 2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x2001, ret=1: SSLv3/TLS write server done 2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x2001, ret=1: SSLv3/TLS read client key exchange 2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x2001, ret=1: SSLv3/TLS read change cipher spec 2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x2001, ret=1: SSLv3/TLS read finished 2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x2001, ret=1: SSLv3/TLS write session ticket 2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x2001, ret=1: SSLv3/TLS write change cipher spec 2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x2001, ret=1: SSLv3/TLS write finished 2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x20, ret=1: SSL negotiation finished successfully 2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x2002, ret=1: SSL negotiation finished successfully 2022.01.10 02:22:25 pop3-login: Info: Login: user=<user1(a)mail-server.cc>, method=PLAIN, rip=178.189.103.34, lip=195.88.238.13, mpid=1694, TLS, TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits) 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: Loading modules from directory: /usr/lib/dovecot/modules 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: Module loaded: /usr/lib/dovecot/modules/lib01_acl_plugin.so 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: Module loaded: /usr/lib/dovecot/modules/lib10_quota_plugin.so 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: Module loaded: /usr/lib/dovecot/modules/lib15_notify_plugin.so 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: Module loaded: /usr/lib/dovecot/modules/lib20_mail_log_plugin.so 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: Module loaded: /usr/lib/dovecot/modules/lib20_replication_plugin.so 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: Module loaded: /usr/lib/dovecot/modules/lib20_virtual_plugin.so 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: Module loaded: /usr/lib/dovecot/modules/lib20_zlib_plugin.so 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: Added userdb setting: plugin/quota_rule=*:bytes=10240000 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: Effective uid=5000, gid=5000, home=/srv/vmail/mail-server.cc/user1/ 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: dict(file): dict created (uri=file:/srv/vmail/shared-mailboxes.db, base_dir=/var/run/dovecot) 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: Quota root: name=User Quota backend=dict args=:proxy::sqluserquota 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: Quota rule: root=User Quota mailbox=* bytes=10240000 messages=0 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: Quota rule: root=User Quota mailbox=Trash bytes=+1024000 (10%) messages=0 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: Quota rule: root=User Quota mailbox=Sent bytes=+1024000 (10%) messages=0 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: Quota warning: bytes=10240000 (100%) messages=0 reverse=no command=quota-warning 100 user1(a)mail-server.cc 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: Quota warning: bytes=9728000 (95%) messages=0 reverse=no command=quota-warning 95 user1(a)mail-server.cc 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: Quota warning: bytes=9216000 (90%) messages=0 reverse=no command=quota-warning 90 user1(a)mail-server.cc 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: Quota warning: bytes=8192000 (80%) messages=0 reverse=no command=quota-warning 80 user1(a)mail-server.cc 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: Quota grace: root=User Quota bytes=1024000 (10%) 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: quota-dict: user=user1(a)mail-server.cc, uri=proxy::sqluserquota, noenforcing=0 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: dict(proxy): dict created (uri=proxy::sqluserquota, base_dir=/var/run/dovecot) 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: Namespace inbox: type=private, prefix=, sep=/, inbox=yes, hidden=no, list=yes, subscriptions=yes location=maildir:/srv/vmail/mail-server.cc/user1/maildir 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: maildir++: root=/srv/vmail/mail-server.cc/user1/maildir, index=, indexpvt=, control=, inbox=/srv/vmail/mail-server.cc/user1/maildir,alt= 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: acl: initializing backend with data: vfile 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: acl: acl username = user1(a)mail-server.cc 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: acl: owner = 1 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: acl vfile: Global ACLs disabled 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: Namespace : type=shared, prefix=shared/%u/, sep=/, inbox=no, hidden=no, list=children, subscriptions=yes location=maildir:/srv/vmail/%d/%n/maildir:INDEX=~/maildir/shared/%u:CONTROL=~/maildir/shared/%u 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: shared: root=/var/run/dovecot, index=, indexpvt=, control=, inbox=, alt= 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: acl: initializing backend with data: vfile 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: acl: acl username = user1(a)mail-server.cc 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: acl: owner = 0 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: acl vfile: Global ACLs disabled 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: quota: quota_over_flag check: quota_over_script unset - skipping 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: Mailbox INBOX: Mailbox opened because: POP3 INBOX 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: acl vfile: file /srv/vmail/mail-server.cc/user1/maildir/dovecot-acl not found 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Info: Disconnected: Logged out top=0/0, retr=0/0, del=0/0, size=0, bytes=12/43 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: dict(proxy): Waiting for dict to finish pending operations 2022.01.10 02:22:25 pop3-login: Debug: SSL alert: close notify 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: dict(file): dict destroyed 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: dict(proxy): Waiting for dict to finish pending operations 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: dict(proxy): dict destroyed 2022.01.10 02:23:00 imap-login: Debug: SSL: where=0x10, ret=1: before SSL initialization 2022.01.10 02:23:00 imap-login: Debug: SSL: where=0x2001, ret=1: before SSL initialization 2022.01.10 02:23:00 imap-login: Debug: SSL: where=0x2002, ret=-1: before SSL initialization 2022.01.10 02:23:00 imap-login: Debug: SSL: where=0x2001, ret=1: before SSL initialization 2022.01.10 02:23:00 imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3/TLS read client hello 2022.01.10 02:23:00 imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3/TLS write server hello 2022.01.10 02:23:00 imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3/TLS write certificate 2022.01.10 02:23:00 imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3/TLS write key exchange 2022.01.10 02:23:00 imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3/TLS write server done 2022.01.10 02:23:00 imap-login: Debug: SSL: where=0x2002, ret=-1: SSLv3/TLS write server done 2022.01.10 02:23:00 imap-login: Debug: SSL: where=0x2002, ret=-1: SSLv3/TLS write server done 2022.01.10 02:23:00 imap-login: Debug: SSL: where=0x2002, ret=-1: SSLv3/TLS write server done 2022.01.10 02:23:00 imap-login: Debug: SSL: where=0x2002, ret=-1: SSLv3/TLS write server done 2022.01.10 02:23:00 imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3/TLS write server done 2022.01.10 02:23:00 imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3/TLS read client key exchange 2022.01.10 02:23:00 imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3/TLS read change cipher spec 2022.01.10 02:23:00 imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3/TLS read finished 2022.01.10 02:23:00 imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3/TLS write session ticket 2022.01.10 02:23:00 imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3/TLS write change cipher spec 2022.01.10 02:23:00 imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3/TLS write finished 2022.01.10 02:23:00 imap-login: Debug: SSL: where=0x20, ret=1: SSL negotiation finished successfully 2022.01.10 02:23:00 imap-login: Debug: SSL: where=0x2002, ret=1: SSL negotiation finished successfully 2022.01.10 02:23:00 imap-login: Info: Login: user=<user1(a)mail-server.cc>, method=PLAIN, rip=178.189.103.34, lip=195.88.238.13, mpid=1696, TLS, TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits) 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: Loading modules from directory: /usr/lib/dovecot/modules 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: Module loaded: /usr/lib/dovecot/modules/lib01_acl_plugin.so 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: Module loaded: /usr/lib/dovecot/modules/lib02_imap_acl_plugin.so 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: Module loaded: /usr/lib/dovecot/modules/lib10_quota_plugin.so 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: Module loaded: /usr/lib/dovecot/modules/lib11_imap_quota_plugin.so 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: Module loaded: /usr/lib/dovecot/modules/lib15_notify_plugin.so 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: Module loaded: /usr/lib/dovecot/modules/lib20_mail_log_plugin.so 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: Module loaded: /usr/lib/dovecot/modules/lib20_replication_plugin.so 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: Module loaded: /usr/lib/dovecot/modules/lib20_virtual_plugin.so 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: Module loaded: /usr/lib/dovecot/modules/lib20_zlib_plugin.so 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: Module loaded: /usr/lib/dovecot/modules/lib95_imap_sieve_plugin.so 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: Added userdb setting: plugin/quota_rule=*:bytes=10240000 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: Effective uid=5000, gid=5000, home=/srv/vmail/mail-server.cc/user1/ 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: dict(file): dict created (uri=file:/srv/vmail/shared-mailboxes.db, base_dir=/var/run/dovecot) 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: Quota root: name=User Quota backend=dict args=:proxy::sqluserquota 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: Quota rule: root=User Quota mailbox=* bytes=10240000 messages=0 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: Quota rule: root=User Quota mailbox=Trash bytes=+1024000 (10%) messages=0 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: Quota rule: root=User Quota mailbox=Sent bytes=+1024000 (10%) messages=0 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: Quota warning: bytes=10240000 (100%) messages=0 reverse=no command=quota-warning 100 user1(a)mail-server.cc 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: Quota warning: bytes=9728000 (95%) messages=0 reverse=no command=quota-warning 95 user1(a)mail-server.cc 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: Quota warning: bytes=9216000 (90%) messages=0 reverse=no command=quota-warning 90 user1(a)mail-server.cc 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: Quota warning: bytes=8192000 (80%) messages=0 reverse=no command=quota-warning 80 user1(a)mail-server.cc 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: Quota grace: root=User Quota bytes=1024000 (10%) 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: quota-dict: user=user1(a)mail-server.cc, uri=proxy::sqluserquota, noenforcing=0 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: dict(proxy): dict created (uri=proxy::sqluserquota, base_dir=/var/run/dovecot) 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: Namespace inbox: type=private, prefix=, sep=/, inbox=yes, hidden=no, list=yes, subscriptions=yes location=maildir:/srv/vmail/mail-server.cc/user1/maildir 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: maildir++: root=/srv/vmail/mail-server.cc/user1/maildir, index=, indexpvt=, control=, inbox=/srv/vmail/mail-server.cc/user1/maildir,alt= 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: acl: initializing backend with data: vfile 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: acl: acl username = user1(a)mail-server.cc 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: acl: owner = 1 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: acl vfile: Global ACLs disabled 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: Namespace : type=shared, prefix=shared/%u/, sep=/, inbox=no, hidden=no, list=children, subscriptions=yes location=maildir:/srv/vmail/%d/%n/maildir:INDEX=~/maildir/shared/%u:CONTROL=~/maildir/shared/%u 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: shared: root=/var/run/dovecot, index=, indexpvt=, control=, inbox=, alt= 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: acl: initializing backend with data: vfile 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: acl: acl username = user1(a)mail-server.cc 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: acl: owner = 0 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: acl vfile: Global ACLs disabled 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: quota: quota_over_flag check: quota_over_script unset - skipping 2022.01.10 02:23:00 imap-login: Debug: SSL error: Connection closed 2022.01.10 02:23:00 imap-login: Debug: SSL alert: close notify 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: acl vfile: file /srv/vmail/mail-server.cc/user1/maildir/dovecot-acl not found 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Info: Disconnected: Connection closed (IDLE running for 0.001 + waiting input for 0.001 secs, 2 B in + 10 B out, state=wait-input) in=11 out=461 deleted=0 expunged=0 trashed=0 hdr_count=0 hdr_bytes=0 body_count=0 body_bytes=0 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: dict(file): dict destroyed 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: dict(proxy): Waiting for dict to finish pending operations 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: dict(proxy): dict destroyed thx, Alex

2 1

Patch: assertion failed in doveadm fts lookup
by John Fawcett 09 Jan '22

09 Jan '22

Hi I'm reposting this patch, which I have been applying locally since I originally posted it. Hopefully it can be considered for inclusion in the official release. It was tested on dovecot 2.3.16 but applies against the latest version 2.3.17.1. This is the "assertion failed" that it addresses doveadm fts lookup -u john(a)voipsupport.it body "text to look for" doveadm(john(a)voipsupport.it): Panic: file mail-storage.c: line 2108 (mailbox_get_open_status): assertion failed: (box->opened) doveadm(john(a)voipsupport.it): Error: Raw backtrace: /usr/local/lib/dovecot/libdovecot.so.0(backtrace_append+0x42) [0x7ff624fa7072] -> /usr/local/lib/dovecot/libdovecot.so.0(backtrace_get+0x1e) [0x7ff624fa718e] -> /usr/local/lib/dovecot/libdovecot.so.0(+0xffc3b) [0x7ff624fb3c3b] -> /usr/local/lib/dovecot/libdovecot.so.0(+0xffc71) [0x7ff624fb3c71] -> /usr/local/lib/dovecot/libdovecot.so.0(+0x5536f) [0x7ff624f0936f] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(+0x3fc31) [0x7ff6250bcc31] -> /usr/local/lib/dovecot/lib21_fts_solr_plugin.so(+0x540d) [0x7ff62244f40d] -> /usr/local/lib/dovecot/lib20_fts_plugin.so(fts_backend_lookup+0x4d) [0x7ff6246b624d] -> /usr/local/lib/dovecot/doveadm/lib20_doveadm_fts_plugin.so(+0x2e8c) [0x7ff62240ce8c] -> doveadm(+0x31ded) [0x55f0c7f3aded] -> doveadm(+0x32862) [0x55f0c7f3b862] -> doveadm(doveadm_cmd_ver2_to_mail_cmd_wrapper+0x22d) [0x55f0c7f3c6fd] -> doveadm(doveadm_cmd_run_ver2+0x4d8) [0x55f0c7f4d158] -> doveadm(doveadm_cmd_try_run_ver2+0x3a) [0x55f0c7f4d1aa] -> doveadm(main+0x1f6) [0x55f0c7f2b606] -> /lib64/libc.so.6(__libc_start_main+0xd5) [0x7ff624bc8b75] -> doveadm(_start+0x2e) [0x55f0c7f2ba0e] Aborted (core dumped) Here's the patch: diff -ur dovecot-2.3.17.1-orig/src/plugins/fts/doveadm-fts.c dovecot-2.3.17.1-new/src/plugins/fts/doveadm-fts.c --- dovecot-2.3.17.1-orig/src/plugins/fts/doveadm-fts.c 2021-12-03 12:48:47.000000000 +0100 +++ dovecot-2.3.17.1-new/src/plugins/fts/doveadm-fts.c 2022-01-09 01:33:23.396342025 +0100 @@ -47,6 +47,14 @@ i_array_init(&result.scores, 16); box = mailbox_alloc(info->ns->list, info->vname, 0); + mailbox_set_reason(box,"fts search"); + if (mailbox_open(box) < 0) { + i_error("Couldn't open mailbox: %s", + mailbox_get_last_internal_error(box, NULL)); + doveadm_mail_failed_error(ctx, MAIL_ERROR_TEMP); + return -1; + } + if (fts_backend_lookup(backend, box, ctx->search_args->args, FTS_LOOKUP_FLAG_AND_ARGS, &result) < 0) { i_error("fts lookup failed"); John

2 1

Non-user logins?
by Ken Wright 09 Jan '22

09 Jan '22

My Dovecot issues continue. Right now I see at least two issues: first, my logs consistently show non-users trying (and failing) to log in, and I'm still unable to log in from my email client (Evolution or Roundcube, either one). I'll post about the second issue later; right now I wonder why I'm getting so many non-users trying to log in. Am I the subject of concerted hacking attacks, or is there something else going on? Some of the attempted logins are more-or-less random names claiming to be @mydomain, but at least one is a username that's really on my server, to wit: Jan 7 22:52:01 grace dovecot: lmtp(776281): Error: lmtp-server: conn unix:pid=776262,uid=117 [3]: rcpt www-data(a)mydomain.com: Failed to lookup user www-data(a)mydomain.com: Internal error occurred. Refer to server log for more information. (Another quick question: which server log should I check?) So, if anyone can tell me what's going on with all these logins, I'd be much obliged! Ken

9 16

Patch: enhancements for solr/tika integration
by John Fawcett 09 Jan '22

09 Jan '22

Hi here's a patch with some enhancements that I am applying locally for solr/tika integration. Hopefully this can be considered for inclusion. I've tested up to 2.3.16 and this patch applies against latest version 2.3.17.1. The contents are: 1. Allow username and password in tika configuration (as is already supported for solr). For example: fts_tika = https://user:password@tika_host:tika_port/tika/tika This means that tika can be more easily located on a different server to dovecot. Locating Solr and Tika on separate servers can isolate the Dovecot server from issues that may happen on Solr or Tika (like out of memory). 2. Introduce an optional configurable limit on the size of emails whose message bodies will be indexed with solr via a new setting fts_max_size, to be put in the plugin section. For example plugin { ... fts_max_size = 2M ... } Message body indexing is skipped for messages that are larger than this setting. 3. Introduce an optional configurable limit on the size of emails whose attachments will be sent to tika for keyword extraction, via a new setting fts_max_size_tika, to be put in the plugin section. For example: plugin { ... fts_max_size_tika = 1M } I noticed that some very large attachments are being sent to tika and these often do not have any useful content to index. For simplicity the check is done on message size not individual or total attachment size. Here's the patch: diff -ur dovecot-2.3.17.1-orig/src/plugins/fts/fts-build-mail.c dovecot-2.3.17.1-new/src/plugins/fts/fts-build-mail.c --- dovecot-2.3.17.1-orig/src/plugins/fts/fts-build-mail.c 2021-12-03 12:48:47.000000000 +0100 +++ dovecot-2.3.17.1-new/src/plugins/fts/fts-build-mail.c 2022-01-09 01:33:23.398341998 +0100 @@ -17,6 +17,7 @@ #include "fts-filter.h" #include "fts-api-private.h" #include "fts-build-mail.h" +#include "settings-parser.h" /* there are other characters as well, but this doesn't have to be exact */ #define IS_WORD_WHITESPACE(c) \ @@ -25,6 +26,8 @@ wherever */ #define MAX_WORD_SIZE 1024 +static bool debug = FALSE; + struct fts_mail_build_context { struct mail *mail; struct fts_backend_update_context *update_ctx; @@ -34,6 +37,7 @@ buffer_t *word_buf, *pending_input; struct fts_user_language *cur_user_lang; + bool oversized_tika; }; static int fts_build_data(struct fts_mail_build_context *ctx, @@ -223,7 +227,7 @@ parser_context.user = mail_storage_get_user(storage); parser_context.content_disposition = ctx->content_disposition; - + parser_context.oversized_tika = ctx->oversized_tika; if (fts_parser_init(&parser_context, &ctx->body_parser)) { /* extract text using the the returned parser */ *binary_body_r = TRUE; @@ -496,7 +500,32 @@ bool binary_body; const char *error; int ret; - + uoff_t msg_size; + uoff_t fts_max_size = 0; + uoff_t fts_max_size_tika = 0; + const char * fts_max_size_setting; + const char * fts_max_size_tika_setting; + bool oversized_msg; + bool oversized_tika; + + fts_max_size_setting = mail_user_plugin_getenv(update_ctx->backend->ns->user, "fts_max_size"); + if (fts_max_size_setting != NULL) { + if (debug) i_debug("fts_max_size %s",fts_max_size_setting); + if (settings_get_size(fts_max_size_setting, &fts_max_size, &error) < 0) { + i_error("%s",error); + fts_max_size = 0; + } + if (debug) i_debug("fts_max_size (value) %"PRIuUOFF_T,fts_max_size); + } + fts_max_size_tika_setting = mail_user_plugin_getenv(update_ctx->backend->ns->user, "fts_max_size_tika"); + if (fts_max_size_tika_setting != NULL) { + if (debug) i_debug("fts_max_size_tika %s",fts_max_size_tika_setting); + if (settings_get_size(fts_max_size_tika_setting, &fts_max_size_tika, &error) < 0) { + i_error("%s",error); + fts_max_size_tika = 0; + } + if (debug) i_debug("fts_max_size_tika (value) %"PRIuUOFF_T,fts_max_size_tika); + } *may_need_retry_r = FALSE; if (mail_get_stream_because(mail, NULL, NULL, "fts indexing", &input) < 0) { if (mail->expunged) @@ -505,10 +534,21 @@ mailbox_get_last_internal_error(mail->box, NULL)); return -1; } - + oversized_msg = FALSE; + oversized_tika = FALSE; + i_stream_get_size(input,TRUE,&msg_size); + if (fts_max_size > 0 && msg_size > fts_max_size) { + i_info("Skipping message body indexing because size %"PRIuUOFF_T" exceeds setting fts_max_size %s",msg_size,fts_max_size_setting); + oversized_msg = TRUE; + } + if (fts_max_size_tika > 0 && msg_size > fts_max_size_tika) { + i_info("Skipping message attachment indexing because size %"PRIuUOFF_T" exceeds setting fts_max_size_tika %s",msg_size,fts_max_size_tika_setting); + oversized_tika = TRUE; + } i_zero(&ctx); ctx.update_ctx = update_ctx; ctx.mail = mail; + ctx.oversized_tika = oversized_tika; if ((update_ctx->backend->flags & FTS_BACKEND_FLAG_TOKENIZED_INPUT) != 0) ctx.pending_input = buffer_create_dynamic(default_pool, 128); @@ -563,7 +603,7 @@ message_decoder_set_return_binary(decoder, TRUE); body_part = TRUE; } else { - if (skip_body) + if (skip_body ||oversized_msg) continue; } @@ -597,7 +637,7 @@ else (void)fts_parser_deinit(&ctx.body_parser, NULL); } - if (ret == 0 && body_part && !skip_body && !body_added) { + if (ret == 0 && body_part && !skip_body && !oversized_msg && !body_added) { /* make sure body is added even when it doesn't exist */ block.data = NULL; block.size = 0; ret = fts_build_body_block(&ctx, &block, TRUE); diff -ur dovecot-2.3.17.1-orig/src/plugins/fts/fts-parser.h dovecot-2.3.17.1-new/src/plugins/fts/fts-parser.h --- dovecot-2.3.17.1-orig/src/plugins/fts/fts-parser.h 2021-12-03 12:48:47.000000000 +0100 +++ dovecot-2.3.17.1-new/src/plugins/fts/fts-parser.h 2022-01-09 01:33:23.399341985 +0100 @@ -10,6 +10,7 @@ /* Can't be NULL */ const char *content_type; const char *content_disposition; + bool oversized_tika; }; struct fts_parser_vfuncs { diff -ur dovecot-2.3.17.1-orig/src/plugins/fts/fts-parser-tika.c dovecot-2.3.17.1-new/src/plugins/fts/fts-parser-tika.c --- dovecot-2.3.17.1-orig/src/plugins/fts/fts-parser-tika.c 2021-12-03 12:48:47.000000000 +0100 +++ dovecot-2.3.17.1-new/src/plugins/fts/fts-parser-tika.c 2022-01-09 01:33:23.400341972 +0100 @@ -57,7 +57,7 @@ tuser = p_new(user->pool, struct fts_parser_tika_user, 1); MODULE_CONTEXT_SET(user, fts_parser_tika_user_module, tuser); - if (http_url_parse(url, NULL, 0, user->pool, + if (http_url_parse(url, NULL, HTTP_URL_ALLOW_USERINFO_PART, user->pool, &tuser->http_url, &error) < 0) { i_error("fts_tika: Failed to parse HTTP url %s: %s", url, error); return -1; @@ -148,6 +148,10 @@ if (tika_get_http_client_url(parser_context->user, &http_url) < 0) return NULL; + if (parser_context->oversized_tika) { + i_info("skipping tika parser due to oversized message"); + return NULL; + } if (http_url->path == NULL) http_url->path = "/"; @@ -159,6 +163,11 @@ http_url->host.name, t_strconcat(http_url->path, http_url->enc_query, NULL), fts_tika_parser_response, parser); + if (http_url->user != NULL) { + http_client_request_set_auth_simple( + http_req, http_url->user, http_url->password); + } + http_client_request_set_port(http_req, http_url->port); http_client_request_set_ssl(http_req, http_url->have_ssl); if (parser_context->content_type != NULL) John

1 0

Patch: safeguard against too large value for uid being sent to solr for single mailbox searches
by John Fawcett 09 Jan '22

09 Jan '22

Hi I'm reposting a patch for solr integration which I have been applying locally. It applies against 2.3.17.1. Dovecot already has a mechanism when doing solr fts searches on multiple mailboxes that prevents a too large value for maximum rows being sent to solr. #define SOLR_MAX_MULTI_ROWS 100000 (defined and used in plugins/fts-solr/fts-backend-solr.c) However on single mailbox searches Dovecot uses the last uid of the mailbox, which can be too large for solr. My suggested patch is to also limit maximum rows to return on single mailbox searches. Here is the patch: diff -ur dovecot-2.3.17.1-orig/src/plugins/fts-solr/fts-backend-solr.c dovecot-2.3.17.1-new/src/plugins/fts-solr/fts-backend-solr.c --- dovecot-2.3.17.1-orig/src/plugins/fts-solr/fts-backend-solr.c 2021-12-03 12:48:47.000000000 +0100 +++ dovecot-2.3.17.1-new/src/plugins/fts-solr/fts-backend-solr.c 2022-01-09 01:33:23.401341959 +0100 @@ -837,7 +837,7 @@ str = t_str_new(256); str_printfa(str, "wt=xml&fl=uid,score&rows=%u&sort=uid+asc&q=%%7b!lucene+q.op%%3dAND%%7d", - status.uidnext); + I_MIN(status.uidnext,SOLR_MAX_MULTI_ROWS)); prefix_len = str_len(str); if (solr_add_definite_query_args(str, args, and_args)) { John

1 0

Can't log in from Evolution or Roundcube
by Ken Wright 09 Jan '22

09 Jan '22

When I try to log in to my mail server (ubuntu 20.04, Postfix 3.4.13, Dovecot 2.3.7.2) I get a response saying "Source stream returned no data”. At least to me, that's not particularly informative. Is it any more informative to anyone else? Ken

3 10

Sv: banning
by Sebastian Nielsen 08 Jan '22

08 Jan '22

I would say, lock accounts to for example IP address, ASN or GeoIP. This can be accomplished simply by a custom login handler, which also checks IP against database. And first time users, and those who change country/ISP/IP have to simply logon to a web interface (where 2FA can be required and also Captcha) and add their IPs/ASNs/Geo's. For a larger user base, I would recommend GeoIP and no web interface, save country of first login to database, and subsequent logins must originate from same country. Users that want to reset have to contact support. If you are a web hotel who only sell service to a specific country at all, lock the ports in firewall to that GeoIP. For smaller user base, like 50-100 users, I would recommend locking to ASN and providing a web interface where multiple ASN can be added. So people syncing from mobile and home can succeed. For very small user base, like 10's of users, just plan lock to IP. By connecting IP to accounts, you greatly reduce the attack surface.

1 0

TLS connection closed unexpectedly
by Ken Wright 08 Jan '22

08 Jan '22

I reinstalled Dovecot this evening, because I haven't been able to receive emails recently. After configuring and adjusting for the use of PostfixAdmin, I get the following error message in Evolution:; Failed to open folder. The reported error was "Failed to authenticate: TLS connection closed unexpectedly". Does anyone recognize this error? Ken

6 8