- dovecot - dovecot.org

solr and dovecot 2.2.36
by Maciej Milaszewski 18 Aug '20

18 Aug '20

Hi I have dovecot-2.2.36.4 (director) + 5 nodes dovecot (dovecot-2.2.36.4) What version of Solr do you recommend ? -- Maciej Miłaszewski Starszy Administrator Systemowy IQ PL Sp. z o.o. Biuro Obsługi Klienta: e-mail: bok(a)iq.pl tel.: +48 58 326 09 90 - 94 fax: +48 58 326 09 99 Dział pomocy: https://www.iq.pl/pomoc Informacja dotycząca przetwarzania danych osobowych: https://www.iq.pl/kontakt IQ PL Sp. z o.o. z siedzibą w Gdańsku (80-298), ul. Geodetów 16, KRS 0000007725, Sąd rejestrowy: Sąd Rejonowy w Gdańsku VII Wydział KRS, kapitał zakładowy: 140.000 PLN, NIP 5832736211, REGON 192478853

3 3

Indexer error after upgrade to 2.3.11.3
by Alessio Cecchi 18 Aug '20

18 Aug '20

Hi, after the upgrade to Dovecot 2.3.11.3, from 2.3.10.1, I see frequently these errors from different users: Aug 18 11:02:35 Panic: indexer-worker(info(a)domain.com) session=<g71KISOttvS5LNVj:O3ahCyuZO18cYAAAEPCW+w>: file http-client-request.c: line 1232 (http_client_request_send_more): assertion failed: (req->payload_input != NULL) Aug 18 11:02:35 Error: indexer-worker(info(a)domain.com) session=<g71KISOttvS5LNVj:O3ahCyuZO18cYAAAEPCW+w>: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(backtrace_append+0x2f) [0x7f0ee3c828bf] -> /usr/lib64/dovecot/libdovecot.so.0(backtrace_get+0x26) [0x7f0ee3c829d6] -> /usr/lib64/dovecot/libdovecot.so.0(+0xeb7ba) [0x7f0ee3c8d7ba] -> /usr/lib64/dovecot/libdovecot.so.0(+0xeb801) [0x7f0ee3c8d801] -> /usr/lib64/dovecot/libdovecot.so.0(+0x42ff1) [0x7f0ee3be4ff1] -> /usr/lib64/dovecot/libdovecot.so.0(http_client_request_send_more+0x415) [0x7f0ee3c2ba25] -> /usr/lib64/dovecot/libdovecot.so.0(http_client_connection_output+0x114) [0x7f0ee3c30994] -> /usr/lib64/dovecot/libdovecot.so.0(+0x115470) [0x7f0ee3cb7470] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_call_io+0x55) [0x7f0ee3ca4eb5] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0xdc) [0x7f0ee3ca6ebc] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run+0x5c) [0x7f0ee3ca4fac] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7f0ee3ca51f8] -> /usr/lib64/dovecot/libdovecot.so.0(+0x8a955) [0x7f0ee3c2c955] -> /usr/lib64/dovecot/libdovecot.so.0(http_client_request_finish_payload+0x21) [0x7f0ee3c2cbd1] -> /usr/lib64/dovecot/lib21_fts_solr_plugin.so(solr_connection_post_end+0x45) [0x7f0ee1c85d15] -> /usr/lib64/dovecot/lib21_fts_solr_plugin.so(+0x3fa0) [0x7f0ee1c81fa0] -> /usr/lib64/dovecot/lib20_fts_plugin.so(+0x86cc) [0x7f0ee297f6cc] -> /usr/lib64/dovecot/lib20_fts_plugin.so(fts_backend_update_deinit+0x2c) [0x7f0ee297f74c] -> /usr/lib64/dovecot/lib20_fts_plugin.so(+0xfd04) [0x7f0ee2986d04] -> /usr/lib64/dovecot/lib20_fts_plugin.so(+0xff3f) [0x7f0ee2986f3f] -> /usr/lib64/dovecot/lib10_quota_plugin.so(+0xf64b) [0x7f0ee2dc764b] -> /usr/lib64/dovecot/lib01_acl_plugin.so(+0xde43) [0x7f0ee2fdce43] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mailbox_transaction_commit_get_changes+0x54) [0x7f0ee3f91db4] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mailbox_transaction_commit+0x16) [0x7f0ee3f91e76] -> dovecot/indexer-worker [info(a)domain.com INBOX](+0x291c) [0x557584acb91c] -> dovecot/indexer-worker [info(a)domain.com INBOX](+0x2e54) [0x557584acbe54] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_call_io+0x55) [0x7f0ee3ca4eb5] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0xdc) [0x7f0ee3ca6ebc] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run+0x5c) [0x7f0ee3ca4fac] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7f0ee3ca51f8] Aug 18 11:02:35 Error: indexer: Indexer worker disconnected, discarding 1 requests for info(a)domain.com Aug 18 11:02:35 Error: imap(info(a)domain.com) session=<g71KISOttvS5LNVj>: indexer failed to index mailbox INBOX Aug 18 11:02:35 Fatal: indexer-worker(info(a)domain.com) session=<g71KISOttvS5LNVj:O3ahCyuZO18cYAAAEPCW+w>: master: service(indexer-worker): child 24604 killed with signal 6 (core dumps disabled - https://dovecot.org/bugreport.html#coredumps) I'm using FTS with Solr 6.6.5. What is it? Thanks -- Alessio Cecchi Postmaster @ http://www.qboxmail.it https://www.linkedin.com/in/alessice

1 0

Tests failing on CentOS 6
by Peter 18 Aug '20

18 Aug '20

Getting this when attempting to build 2.3.11.3 on CentOS 6: test-mail-cache.c:176: Assert failed: strcmp(str_c(str),"123\nfoo\n456\nbar\n") "" != "123 foo 456 bar " test-mail-cache.c:176: Assert failed: strcmp(str_c(str),"123\nfoo\n456\nbar\n") "" != "123 foo 456 bar " mail cache uncommitted lookups ....................................... : FAILED Full make check output is at https://paste.centos.org/view/b48d38a9 I can provide full build logs if you want, but that's a 4M file so I'll provide it upon request. For now I'm going ot have to bypass the make check stage of the build for CentOS 6, but I worry that the failed check could be indicative of something critical. Peter

2 2

Apple Mail Since upgrade to dovecot 2.3.x unable to connect
by Johannes Rohr 18 Aug '20

18 Aug '20

|Dear all,| |a couple of days ago I upgraded our server from Ubuntu 18.04 to 20.04, thereby upgrading dovecot from 2.2.x to 2.3.x. | |Since then, some older versions of apple's mail.app (bundled with el Capitano, released in 2016) no longer connect. When I turn on SSL debugging, I see:| |Debug: SSL error: SSL_accept() failed: error:14209102:SSL routines:tls_early_post_process_client_hello:unsupported protocol imap-login: Debug: SSL error: SSL_accept() syscall failed: Invalid argument| || |Unfortunately, it doesn't reveal the name of the unsupported protocol. Also, what about the failed syscall? Does dovecot try and fail to open some file?| |Here are the contents of /etc/dovecot/conf.d/10-ssl.conf:| | ssl = yes ssl_cert = </etc/ssl/letsencrypt/idaweb-mail.rooot.de/fullchain.pem ssl_key = </etc/ssl/letsencrypt/idaweb-mail.rooot.de/key.pem ssl_ca = </etc/ssl/letsencrypt/idaweb-mail.rooot.de/ca.pem ssl_client_ca_dir = /etc/ssl/certs ssl_dh = </etc/dovecot/dh.pem | |I would greatly appreciate any hints! | |Cheers,| |Johannes | | | ||

6 6

MDBOX DSYNC error: Broken physical size in mailbox
by paul-dovecotlist＠trainor.nz 18 Aug '20

18 Aug '20

Hi All, I currently have a small Dovecot server (Server A) and I've installed a second dovecot mailbox server (server B) and am trying to sync mailboxes from Server A to Server B. Both servers sit behind two dovecot directors on separate hosts and have identical config files (doveconf -n output below). Mailboxes on Server A are on an NFS mount. Server A has been working fine with no issues for a couple of years. I'm running this command on Server A: doveadm sync -u #user# tcp:#newservername#:24245 Small mailboxes with few items are syncing OK.. but most mailboxes fail (sycn stops) with the following type of error: (Mailbox name, storage file, UID and sizes vary). dsync-local(#username#)<b2vTDKerOV/fAQAAZMK/0g>: Error: Mailbox INBOX: Cache /#usershomedirectory#/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache: Deleting corrupted cache record uid=9: UID 9: Broken physical size in mailbox INBOX: read(/#usershomedirectory#/mdbox/storage/m.1) failed: Cached message size larger than expected (60616 > 8688, box=INBOX, UID=9) If I run it again, I'll get the same error, but with a new UID. If I do a local migration instead of server to server, I still get the errors. e.g. doveadm sync -u #user# maildir:~/Maildir-test/ I tried running a force resync (doveadm force-resync -u #user# -f "*) but it didn't help. There's no issues from an imap client accessing any emails. Using imapsync to sync affected mailboxes works fine for example. But... if I then run a dsync on Server B (doveadm sync -u #user# maildir:~/Maildir-test/) on an account that was successfully migrated with imapsync, I get the issue again. How worried should I be about these corrupted cache records, and any ideas how to resolve? Thanks in advance for your help! Paul. --- output of doveconf -n --- # 2.3.11.3 (502c39af9): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.11 (6c69c917) # OS: Linux 5.3.0-1032-aws x86_64 Ubuntu 18.04.5 LTS hostname = ### lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes login_trusted_networks = ### mail_fsync = always mail_location = mdbox:~/mdbox mail_plugins = " acl 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 mmap_disable = yes namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = separator = / type = private } namespace shared { list = children location = mdbox:/mailhomes/%%d/%%n/mdbox:INDEXPVT=/mailhomes/%d/%n/shared prefix = shared/%%u/ separator = / subscriptions = no type = shared } passdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } plugin { acl = vfile:/tmp/global-acls:cache_secs=5 mail_plugins = " acl notify replication" sieve = file:~/sieve;active=~/.dovecot.sieve sieve_before = /mailhomes/sieve/global/SpamToJunk.sieve sieve_max_actions = 32 sieve_max_redirects = 4 sieve_max_script_size = 1M sieve_quota_max_scripts = 20 sieve_quota_max_storage = 10M sieve_redirect_envelope_from = sender zlib_save = bz2 zlib_save_level = 6 } protocols = " imap lmtp sieve submission sieve" recipient_delimiter = - service doveadm { inet_listener { port = 24245 } } service imap-login { process_min_avail = 2 } service imap { process_limit = 4096 } service lmtp { inet_listener lmtp { port = 24 } } service managesieve-login { inet_listener sieve { port = 4190 } process_min_avail = 2 service_count = 1 } service managesieve { process_limit = 1024 } service submission-login { inet_listener submission { port = 587 } } ssl = required ssl_cert = </etc/dovecot/dovecot-backend.pem ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it submission_client_workarounds = whitespace-before-path submission_host = ### submission_relay_host = ### submission_relay_ssl = starttls submission_relay_trusted = yes userdb { driver = prefetch } userdb { args = /etc/dovecot/dovecot-ldap-userdb.conf.ext driver = ldap } protocol lda { mail_plugins = " acl notify replication zlib" } protocol imap { mail_max_userip_connections = 100 mail_plugins = " acl notify replication zlib imap_acl" } protocol lmtp { mail_plugins = " acl notify replication zlib sieve" } protocol sieve { mail_max_userip_connections = 10 managesieve_implementation_string = Dovecot Pigeonhole managesieve_logout_format = bytes=%i/%o managesieve_max_compile_errors = 5 managesieve_max_line_length = 64 k } protocol submission { mail_plugins = " acl notify replication" } local ### { doveadm_password = # hidden, use -P to show it } local ### { doveadm_password = # hidden, use -P to show it }

2 1

Apple Mail Since upgrade to dovecot 2.3.x unable to connect
by Johannes Rohr 17 Aug '20

17 Aug '20

|Dear all,| |a couple of days ago I upgraded our server from Ubuntu 18.04 to 20.04, thereby upgrading dovecot from 2.2.x to 2.3.x. | |Since then, some older versions of apple's mail.app (bundled with el Capitano, released in 2016) no longer connect. When I turn on SSL debugging, I see:| |Debug: SSL error: SSL_accept() failed: error:14209102:SSL routines:tls_early_post_process_client_hello:unsupported protocol imap-login: Debug: SSL error: SSL_accept() syscall failed: Invalid argument| || |Unfortunately, it doesn't reveal the name of the unsupported protocol. Also, what about the failed syscall? Does dovecot try and fail to open some file?| |Here are the contents of /etc/dovecot/conf.d/10-ssl.conf:| | ssl = yes ssl_cert = </etc/ssl/letsencrypt/idaweb-mail.rooot.de/fullchain.pem ssl_key = </etc/ssl/letsencrypt/idaweb-mail.rooot.de/key.pem ssl_ca = </etc/ssl/letsencrypt/idaweb-mail.rooot.de/ca.pem ssl_client_ca_dir = /etc/ssl/certs ssl_dh = </etc/dovecot/dh.pem | |I would greatly appreciate any hints! | |Cheers,| |Johannes | | | ||

2 1

generating secure ARGON2ID passwords
by Felix Zielcke 16 Aug '20

16 Aug '20

Hello, I'm using dovecot 2.3.4.1 on a Debian buster system. with Argon2ID password scheme, it's only possible to configure the parameters used for it via the generic -r option to "doveadm pw". A higher -r will increase time and memory comsumption. But on my dual core VM it always uses p=1. So it seems the needed threads can only be changed on compile time? Will there be in future a way to explicitly specify memory, time and threads needed for Argon2ID?

2 2

Bug: GSSAPI: Unexpected NUL in auth data
by Paul Banks 16 Aug '20

16 Aug '20

Hi, After upgrading server to v2.3.11.3 (Arch linux). I can no longer connect from Evolution client to the server via GSSAPI (Kerberos). I get the following message in the log: auth: Debug: gssapi(?,x.x.x.x,<XXX>): Unexpected NUL in auth data The bug appears to have been introduced by this patch: https://github.com/dovecot/core/commit/d196f4c83c7383c17440d39eb994b4cd9ff5… Should mech_gssapi also have the MECH_SEC_ALLOW_NULS flag set? Kind regards, Paul

2 2

2.3.11.3: dsync failure
by Alexander Tsoy 16 Aug '20

16 Aug '20

Hello! dovecot 2.3.11.3 fails to backup/sync my mailbox. The mailbox is currently in mdbox format and is (mostly) lz4-compressed. See the trace below (I've added newlines to the output): # doveadm -v backup -u username mdbox:/var/vmail/username_new/mdbox dsync(username): Panic: file istream.c: line 332 (i_stream_read_memarea): assertion failed: (!stream->blocking) dsync(username): Error: Raw backtrace: #0 default_fatal_finish[0x7f1179173b29] -> #1 fatal_handler_real[0x7f1179173be0] -> #2 default_fatal_handler[0x7f1179173c3d] -> #3 i_panic[0x7f1179173e27] -> #4 i_stream_read_memarea[0x7f1179187b29] -> #5 read_more[0x7f117919519b] -> #6 read_from_buffer[0x7f117919535a] -> #7 i_stream_seekable_read[0x7f117919582e] -> #8 i_stream_seekable_stat[0x7f1179195cdf] -> #9 i_stream_stat[0x7f1179188764] -> #10 i_stream_limit_stat[0x7f1179192380] -> #11 i_stream_stat[0x7f1179188764] -> #12 i_stream_default_stat[0x7f117918a0a3] -> #13 i_stream_default_get_size[0x7f117918a282] -> #14 i_stream_get_size[0x7f1179188811] -> #15 mdbox_save_begin[0x7f11792edb85] -> #16 zlib_mail_save_compress_begin[0x7f117891b2ad] -> #17 mailbox_save_begin[0x7f11792c8f22] -> #18 mail_storage_try_copy[0x7f11792b2443] -> #19 mail_storage_copy[0x7f11792b2604] -> #20 mdbox_copy[0x7f11792ee96f] -> #21 mailbox_copy_int[0x7f11792c9611] -> #22 mailbox_copy[0x7f11792c98c2] -> #23 dsync_mailbox_save_body[0x5629fd7936a5] -> #24 dsync_mailbox_save_newmails[0x5629fd793dc3] -> #25 dsync_mailbox_import_mail[0x5629fd793eb0] -> #26 dsync_brain_recv_mail[0x5629fd78b982] -> #27 dsync_brain_sync_mails[0x5629fd78bd79] -> #28 dsync_brain_run_real[0x5629fd78576c] -> #29 dsync_brain_run[0x5629fd7859a5] -> #30 cmd_dsync_run_local[0x5629fd75e8d3] -> #31 cmd_dsync_run[0x5629fd75f3a8] -> #32 doveadm_mail_next_user[0x5629fd762f81] -> #33 doveadm_mail_single_user[0x5629fd763311] -> #34 doveadm_mail_cmd_exec[0x5629fd763963] -> #35 doveadm_mail_cmd[0x5629fd763c22] -> #36 doveadm_mail_try_run[0x5629fd7641e1] -> #37 main[0x5629fd78051d] -> #38 __libc_start_main[0x7f1178d56c00] -> #39 _start[0x5629fd74cb20] Aborted Tried different output compression types: gz, xz, zstd. dovecot 2.3.10.1 doesn't seem to have such problem. But since I already have some messages compressed with zstd, I would like to do migration using 2.3.11.x. Please let me know if I can provide any further information. I'm not on the list, so please CC me on reply. $ sudo dovecot -n # 2.3.11.3 (502c39af9): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.11 (d71e0372) # OS: Linux 5.4.58-gentoo x86_64 Gentoo Base System release 2.6 # Hostname: xxxxxxxx.xx auth_mechanisms = plain login default_client_limit = 50 default_process_limit = 10 imap_idle_notify_interval = 29 mins mail_fsync = always mail_location = mdbox:~/mdbox mail_plugins = " zlib" 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 mdbox_preallocate_space = yes namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = separator = / subscriptions = yes } passdb { args = scheme=CRYPT username_format=%n /etc/dovecot/users driver = passwd-file } plugin { sieve = file:~/sieve;active=~/.dovecot.sieve zlib_save = xz zlib_save_level = 9 } protocols = imap lmtp service auth-worker { user = $default_internal_user } service auth { unix_listener auth-client { mode = 0660 user = mail } user = $default_internal_user } service imap-login { inet_listener imaps { port = 0 } } ssl = required ssl_cert = </etc/ssl/dovecot/server.crt ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it ssl_prefer_server_ciphers = yes userdb { args = username_format=%n /etc/dovecot/users driver = passwd-file } protocol lmtp { mail_plugins = " zlib sieve" } protocol lda { mail_plugins = " zlib sieve" } local_name imap.xxxx.xx { ssl_cert = </etc/ssl/dovecot/imap.xxxx.xx.crt ssl_key = # hidden, use -P to show it } local_name imap.xxxxxxxx.xx { ssl_cert = </etc/ssl/dovecot/imap.xxxxxxxx.xx.crt ssl_key = # hidden, use -P to show it }

1 0

Doveadm error since 2.3.11.3 when run as unprivileged user
by Arjen de Korte 15 Aug '20

15 Aug '20

I allow users to run 'doveadm' for mailbox maintenance (to expunge mail for instance). Since the upgrade to 2.3.11.3, this no longer works and results in the following error message: doveconf: Fatal: Error in configuration file /etc/dovecot/conf.d/10-ssl.conf line 13: ssl_key: Can't open file /etc/ssl/private/de-korte.org.key: Permission denied This is no surprise, as non-privileged users are not allowed to read the private keys of the server. Question is, why is doveadm trying to read this key in the first place (it is not needed for mailbox maintenance) and why is it failing now? Regards, Arjen

4 6