- dovecot - dovecot.org

Disconnected: Inactivity (auth failed, 2 attempts in 180 secs)
by basti 11 Dec '20

11 Dec '20

Hello, I have a problem with "apple mail". Once it work as expected, then it does not answer. Dez 10 00:16:04 vsrv10563 dovecot[17121]: imap-login: Login: user=<info(a)example.com>, method=PLAIN, rip=77.xx.xxx.xxx, lip=31.xx.xxx.xxx, mpid=4490, TLS, session=<Oit4OxC2CTZNFv7P> Dez 10 00:17:38 vsrv10563 dovecot[17121]: imap-login: Login: user=<info(a)example.com>, method=PLAIN, rip=77.xx.xxx.xxx, lip=31.xx.xxx.xxx, mpid=5174, TLS, session=<IhlpQhC2XjZNFv7P> Dez 10 00:18:14 vsrv10563 dovecot[17121]: imap-login: Disconnected: Inactivity (auth failed, 2 attempts in 180 secs): user=<user(a)example.com>, method=CRAM-MD5, rip=77.xx.xxx.xxx, lip=31.xx.xxx.xxx, TLS, session=<tkVXOxC2DDZNFv7P> Dez 10 00:18:14 vsrv10563 dovecot[17121]: imap-login: Disconnected: Inactivity during authentication (auth failed, 2 attempts in 179 secs): user=<info(a)example.com>, method=CRAM-MD5, rip=77.xx.xxx.xxx, lip=31.xx.xxx.xxx, TLS, session=<pHVeOxC2HzZNFv7P> Dez 10 00:18:14 vsrv10563 dovecot[17121]: imap-login: Disconnected: Inactivity (auth failed, 2 attempts in 180 secs): user=<test(a)example.com>, method=CRAM-MD5, rip=77.xx.xxx.xxx, lip=31.xx.xxx.xxx, TLS, session=<J6ZXOxC2OTZNFv7P> Dez 10 00:18:14 vsrv10563 dovecot[17121]: imap-login: Disconnected: Inactivity (auth failed, 2 attempts in 180 secs): user=<user(a)example.com>, method=CRAM-MD5, rip=77.xx.xxx.xxx, lip=31.xx.xxx.xxx, TLS, session=<oUFXOxC2ATZNFv7P> Dez 10 04:00:22 vsrv10563 dovecot[17121]: imap-login: Login: user=<test(a)example.com>, method=PLAIN, rip=77.xx.xxx.xxx, lip=31.xx.xxx.xxx, mpid=24532, TLS, session=<QYSEXxO2DzZNFv7P> Dez 10 04:03:06 vsrv10563 dovecot[17121]: imap-login: Disconnected: Inactivity during authentication (auth failed, 2 attempts in 180 secs): user=<info(a)example.com>, method=CRAM-MD5, rip=77.xx.xxx.xxx, lip=31.xx.xxx.xxx, TLS, session=<fo2FXxO2BDZNFv7P> Dez 10 04:03:07 vsrv10563 dovecot[17121]: imap-login: Disconnected: Inactivity during authentication (auth failed, 2 attempts in 180 secs): user=<user(a)example.com>, method=CRAM-MD5, rip=77.xx.xxx.xxx, lip=31.xx.xxx.xxx, TLS, session=<ekWNXxO2VTZNFv7P> Dez 10 04:03:09 vsrv10563 dovecot[17121]: imap-login: Disconnected: Inactivity during authentication (auth failed, 2 attempts in 180 secs): user=<user(a)example.com>, method=CRAM-MD5, rip=77.xx.xxx.xxx, lip=31.xx.xxx.xxx, TLS, session=<YE6sXxO2HTZNFv7P> Then fail2ban block the IP. Has anybody similar problems? This there a way to fix this? Thunderbird does not have this problem. Best Regards,

1 0

Standalone Directors
by William Edwards 11 Dec '20

11 Dec '20

Situation: We will be switching to Dovecot proxy + Director with three email clusters - each cluster will host different email domains and users - with CephFS storage. Problem: A Director instance has one 'director_mail_servers' setting, meaning I could only use one set of email servers, while the set of email servers in the cluster depends on the client's domain. (The reason I use Dovecot proxy is so people can use the same IMAP/POP/SMTP hostnames; regardless of which email server / email cluster they're hosted on.) Question: Is it possible to set 'director_mail_servers' based on the client's email domain? Met vriendelijke groeten, William Edwards

2 2

problems after upgrade from 2.2.27 to 2.3.4.1
by Lampa 09 Dec '20

09 Dec '20

Hello, after debian version from 9 to, also dovecot was upgraded. There was problems with right imap and imap-login connection settings. I adjusted process_limit, service count increased /proc/sys/net/core/somaxconn from 128 to 1024 for imap It's a system with 1000+ imap and 200+ pop3 connections. When imap connections are over 1000 problems begins. Problem one: 2020-12-07T12:46:39.575586+01:00 vhermes dovecot: master: Error: service(pop3): Initial status notification not received in 30 seconds, killing the process 2020-12-07T12:46:39.576448+01:00 vhermes dovecot: pop3: Fatal: master: service(pop3): child 13975 killed with signal 9 2020-12-07T12:46:42.015726+01:00 vhermes dovecot: master: Error: service(lmtp): Initial status notification not received in 30 seconds, killing the process 2020-12-07T12:46:42.016680+01:00 vhermes dovecot: lmtp: Fatal: master: service(lmtp): child 13985 killed with signal 9 2020-12-07T12:46:42.061963+01:00 vhermes dovecot: master: Error: service(lmtp): Initial status notification not received in 30 seconds, killing the process 2020-12-07T12:46:42.062973+01:00 vhermes dovecot: lmtp: Fatal: master: service(lmtp): child 13987 killed with signal 9 problem two: 2020-12-07T13:55:43.106017+01:00 vhermes dovecot: pop3: Error: net_connect_unix(/var/run/dovecot/stats-writer) failed: Resource temporarily unavailable 2020-12-07T13:56:22.300893+01:00 vhermes dovecot: lmtp: Error: net_connect_unix(/var/run/dovecot/stats-writer) failed: Resource temporarily unavailable 2020-12-07T13:58:11.721892+01:00 vhermes dovecot: imap: Error: net_connect_unix(/var/run/dovecot/stats-writer) failed: Resource temporarily unavailable problem three - lot of 2020-12-07T10:16:24.773347+01:00 vhermes dovecot: imap-login: Error: master(imap): net_connect_unix(imap) failed: Resource temporarily unavailable - http://wiki2.dovecot.org/SocketUnavailable problem four - crashing 020-12-09T07:53:26.914331+01:00 vhermes dovecot: imap(user@domain)<5426><cv8ehAK2npZX7MQb>: Panic: file message-parser.c: line 174 (message_part_finish): assertion failed: (ctx->nested_parts_count > 0) 2020-12-09T07:53:26.916771+01:00 vhermes dovecot: imap(user@domain)<5426><cv8ehAK2npZX7MQb>: Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0xdb62b) [0x7f31bb0d462b] -> /usr/lib/dovecot/libdovecot.so.0(+0xdb6c1) [0x7f31bb0d46c1] -> /usr/lib/dovecot/libdovecot.so.0(+0x4a149) [0x7f31bb043149] -> /usr/lib/dovecot/libdovecot.so.0(+0x474ac) [0x7f31bb0404ac] -> /usr/lib/dovecot/libdovecot.so.0(message_parser_parse_next_block+0x104) [0x7f31bb0bc844] -> /usr/lib/dovecot/libdovecot.so.0(message_search_msg+0xa8) [0x7f31bb0bedf8] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xcf89e) [0x7f31bb25789e] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_search_args_foreach+0x45) [0x7f31bb1d9445] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xd0774) [0x7f31bb258774] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xd1a68) [0x7f31bb259a68] -> /usr/lib/dovecot/libdovecot-storage.so.0(index_storage_search_next_nonblock+0x61) [0x7f31bb25a0e1] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_search_next_nonblock+0x28) [0x7f31bb1e2e58] -> dovecot/imap [user@domain 1.2.3.4 UID SORT](+0x2691f) [0x559347dc891f] -> dovecot/imap [user@domain 1.2.3.4 UID SORT](command_exec+0x70) [0x559347dc1d80] -> dovecot/imap [user@domain 1.2.3.4 UID SORT](+0x25ed2) [0x559347dc7ed2] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handle_timeouts+0x111) [0x7f31bb0ea8f1] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0xd0) [0x7f31bb0ec070] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x4c) [0x7f31bb0eab7c] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x40) [0x7f31bb0eace0] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f31bb06b0d3] -> dovecot/imap [user@domain 1.2.3.4 UID SORT](main+0x325) [0x559347db2bf5] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xeb) [0x7f31bae5609b] -> dovecot/imap [user@domain 1.2.3.4 UID SORT](_start+0x2a) [0x559347db2d8a] 2020-12-09T07:53:26.917634+01:00 vhermes dovecot: imap(user@domain)<5426><cv8ehAK2npZX7MQb>: Fatal: master: service(imap): child 5426 killed with signal 6 (core dumps disabled - https://dovecot.org/bugreport.html#coredumps) Seems that last problem is solved (if same) https://github.com/dovecot/core/commit/a668d767a710ca18ab6e7177d8e8be22a6b0… Thank you for any help -- Lampa

2 2

Question about login_log_format_elements in a proxy environment
by Adi Pircalabu 08 Dec '20

08 Dec '20

Hi, I have a Dovecot proxy setup with several proxy machines (currently running 2.3.11.3) in front of the real Dovecot servers (2.3.10.1) storing the mailboxes. "doveconf -a | egrep lip" returns: login_log_format_elements = user=<%u> method=%m rip=%r lip=%l mpid=%e %c session=<%{session}> In the real server maillog I'm expecting to have "lip" replaced with the IP address of the proxy. It works as expected for imap-login processes, however for pop3-login processes I still see the real server IP instead of the proxy IP. Ideas? Regards, -- Adi Pircalabu

2 8

Fts solr add fields message-id, date, in-reply-to
by michael1970 08 Dec '20

08 Dec '20

Hi, how can I add fields message-id, date, in-reply-to to fts solr index like hdr,body,subject or to? Thanks, Michael -- Sent from: http://dovecot.2317879.n4.nabble.com/

3 6

dovecot/imap killed with signal 6 after SEARCH in specific mailbox
by Jiri 07 Dec '20

07 Dec '20

Hi All, on my older production server (Deb9 dovecot version 2.2.27-3+deb9u6) a client reported that searching text in one mailbox failed while other mailboxes do search ok. He is using Rouddcube webmail and is searching the whole messages including the body. Errorlog shows panic and assertion failed logs. So I'v moved the 'problematic' mailbox to my latest production server (Deb10 2.3.4.1-5+deb10u4 = 2.3.4.1 (f79e8e7e4)) where I have more RAM to eliminate that and the same error appeared. There is nothing special about the mailbox, roughly 600MiB and 2200 messges. Other much larger mailboxes on the same server do search fine. After turning on imap logging in Roundcube mail, the critical command was: A0004 UID SEARCH RETURN (ALL) TEXT whatever I increased default_process_limit and default_client_limit, I run: doveadm index -u ttt(a)mail2.swpraha.cz -q INBOX but didn't help. I used the gdb method to reproduce it and to get the whole info including backtrace: vmail@s6mail:~$ gdb --args /usr/lib/dovecot/imap -u ttt(a)mail2.swpraha.cz (gdb) r Starting program: /usr/lib/dovecot/imap -u ttt(a)mail2.swpraha.cz process 4458 is executing new program: /usr/bin/doveconf process 4458 is executing new program: /usr/lib/dovecot/imap * PREAUTH [CAPABILITY IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS THREAD=ORDEREDSUBJECT MULTIAPPEND URL-PARTIAL CATENATE UNSELECT CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS BINARY MOVE SNIPPET=FUZZY LITERAL+ NOTIFY SPECIAL-USE QUOTA] Logged in as ttt(a)mail2.swpraha.cz a select INBOX * FLAGS (\Answered \Flagged \Deleted \Seen \Draft $MDNSent Junk $Forwarded NonJunk) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft $MDNSent Junk $Forwarded NonJunk \*)] Flags permitted. * 682 EXISTS * 0 RECENT * OK [UNSEEN 639] First unseen. * OK [UIDVALIDITY 1147771637] UIDs valid * OK [UIDNEXT 104487] Predicted next UID * OK [HIGHESTMODSEQ 53108] Highest a OK [READ-WRITE] Select completed (0.002 + 0.000 + 0.001 secs). A0004 UID SEARCH RETURN (ALL) TEXT whatewer imap(ttt(a)mail2.swpraha.cz)<4458><Auy4NnMnzl9qEQAAevFY8w>: Panic: file message-parser.c: line 174 (message_part_finish): assertion failed: (ctx->nested_parts_count > 0) imap(ttt(a)mail2.swpraha.cz)<4458><Auy4NnMnzl9qEQAAevFY8w>: Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0xdb62b) [0x7ffff7dbb62b] -> /usr/lib/dovecot/libdovecot.so.0(+0xdb661) [0x7ffff7dbb661] -> /usr/lib/dovecot/libdovecot.so.0(+0x4a149) [0x7ffff7d2a149] -> /usr/lib/dovecot/libdovecot.so.0(+0x474ac) [0x7ffff7d274ac] -> /usr/lib/dovecot/libdovecot.so.0(message_parser_parse_next_block+0x104) [0x7ffff7da3844] -> /usr/lib/dovecot/libdovecot.so.0(message_search_msg+0xa8) [0x7ffff7da5df8] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xcf89e) [0x7ffff7f3e89e] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_search_args_foreach+0x45) [0x7ffff7ec0445] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xd0774) [0x7ffff7f3f774] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xd1a68) [0x7ffff7f40a68] -> /usr/lib/dovecot/libdovecot-storage.so.0(index_storage_search_next_nonblock+0x10d) [0x7ffff7f4118d] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_search_next_nonblock+0x28) [0x7ffff7ec9e58] -> /usr/lib/dovecot/imap [ttt(a)mail2.swpraha.cz UID SEARCH](+0x2691f) [0x55555557a91f] -> /usr/lib/dovecot/imap [ttt(a)mail2.swpraha.cz UID SEARCH](command_exec+0x70) [0x555555573d80] -> /usr/lib/dovecot/imap [ttt(a)mail2.swpraha.cz UID SEARCH](+0x25ed2) [0x555555579ed2] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handle_timeouts+0x111) [0x7ffff7dd18f1] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0xd0) [0x7ffff7dd3070] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x4c) [0x7ffff7dd1b7c] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x40) [0x7ffff7dd1ce0] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7ffff7d520d3] -> /usr/lib/dovecot/imap [ttt(a)mail2.swpraha.cz UID SEARCH](main+0x325) [0x555555564bf5] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xeb) [0x7ffff7b3c09b] -> /usr/lib/dovecot/imap [ttt(a)mail2.swpraha.cz UID SEARCH](_start+0x2a) [0x555555564d8a] Program received signal SIGABRT, Aborted. __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 50 ../sysdeps/unix/sysv/linux/raise.c: No such file or directory. (gdb) bt full #0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 set = {__val = {0, 9355454118400172544, 1928, 1862, 1863, 93824992506008, 65, 140737352109185, 140737351192526, 140737351951989, 257, 145, 206158430224, 140737488344944, 140737488344736, 140737351756174}} pid = <optimized out> tid = <optimized out> ret = <optimized out> #1 0x00007ffff7b3a535 in __GI_abort () at abort.c:79 save_stage = 1 act = {__sigaction_handler = {sa_handler = 0x9ef, sa_sigaction = 0x9ef}, sa_mask = {__val = {30216, 93824992300426, 0, 513, 513, 140737351192526, 140737351744763, 140737351192526, 9355454118400172544, 140737351192526, 140737351951234, 140737488344944, 93824992503880, 140737351192526, 140737351951609, 140737351192526}}, sa_flags = -136625910, sa_restorer = 0x5} sigs = {__val = {32, 0 <repeats 15 times>}} #2 0x00007ffff7d2a481 in ?? () from /usr/lib/dovecot/libdovecot.so.0 No symbol table info available. #3 0x00007ffff7dbb661 in default_fatal_handler () from /usr/lib/dovecot/libdovecot.so.0 No symbol table info available. #4 0x00007ffff7d2a149 in i_panic () from /usr/lib/dovecot/libdovecot.so.0 No symbol table info available. #5 0x00007ffff7d274ac in ?? () from /usr/lib/dovecot/libdovecot.so.0 No symbol table info available. #6 0x00007ffff7da3844 in message_parser_parse_next_block () from /usr/lib/dovecot/libdovecot.so.0 No symbol table info available. #7 0x00007ffff7da5df8 in message_search_msg () from /usr/lib/dovecot/libdovecot.so.0 No symbol table info available. #8 0x00007ffff7f3e89e in ?? () from /usr/lib/dovecot/libdovecot-storage.so.0 No symbol table info available. #9 0x00007ffff7ec0445 in mail_search_args_foreach () from /usr/lib/dovecot/libdovecot-storage.so.0 No symbol table info available. #10 0x00007ffff7f3f774 in ?? () from /usr/lib/dovecot/libdovecot-storage.so.0 No symbol table info available. #11 0x00007ffff7f40a68 in ?? () from /usr/lib/dovecot/libdovecot-storage.so.0 No symbol table info available. #12 0x00007ffff7f4118d in index_storage_search_next_nonblock () from /usr/lib/dovecot/libdovecot-storage.so.0 No symbol table info available. #13 0x00007ffff7ec9e58 in mailbox_search_next_nonblock () from /usr/lib/dovecot/libdovecot-storage.so.0 No symbol table info available. #14 0x000055555557a91f in ?? () No symbol table info available. #15 0x0000555555573d80 in command_exec () No symbol table info available. #16 0x0000555555579ed2 in ?? () No symbol table info available. #17 0x00007ffff7dd18f1 in io_loop_handle_timeouts () from /usr/lib/dovecot/libdovecot.so.0 No symbol table info available. #18 0x00007ffff7dd3070 in io_loop_handler_run_internal () from /usr/lib/dovecot/libdovecot.so.0 No symbol table info available. #19 0x00007ffff7dd1b7c in io_loop_handler_run () from /usr/lib/dovecot/libdovecot.so.0 No symbol table info available. #20 0x00007ffff7dd1ce0 in io_loop_run () from /usr/lib/dovecot/libdovecot.so.0 No symbol table info available. #21 0x00007ffff7d520d3 in master_service_run () from /usr/lib/dovecot/libdovecot.so.0 No symbol table info available. #22 0x0000555555564bf5 in main () No symbol table info available. (gdb) ========================== dovecot -n: # 2.3.4.1 (f79e8e7e4): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.4 () # OS: Linux 5.4.65-1-pve x86_64 Debian 10.6 # Hostname: s6mail.ehosting.cz default_client_limit = 10000 default_process_limit = 1000 deliver_log_format = msgid=%m, from=%f, Subj=%s: %$ dict { expire = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext quota = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext } disable_plaintext_auth = no first_valid_gid = 150 first_valid_uid = 150 last_valid_gid = 150 last_valid_uid = 150 log_timestamp = "%Y-%m-%d %H:%M:%S " mail_plugins = quota trash expire mail_privileged_group = vmail managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date index ihave duplicate mime foreverypart extracttext spamtest spamtestplus namespace inbox { inbox = yes location = mailbox Archive { auto = subscribe special_use = \Archive } mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk { auto = subscribe 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 = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { antispam_backend = pipe antispam_crm_binary = /bin/false antispam_dspam_args = --deliver=;--user;%u;--source=error;--signature=%%s antispam_dspam_binary = /usr/bin/dspam antispam_dspam_notspam = --class=innocent antispam_dspam_result_header = X-DSPAM-Result antispam_dspam_spam = --class=spam antispam_pipe_program = /usr/local/bin/postfix/reclasify-from-dovecot antispam_pipe_program_args = %u;%d antispam_pipe_program_notspam_arg = --ham antispam_pipe_program_spam_arg = --spam antispam_pipe_tmpdir = /tmp antispam_signature = X-CRM114-CacheID antispam_signature_missing = error antispam_spam = Junk;Spam antispam_spool2dir_notspam = /tmp/spamspool/%%020lu-%u-%%05luh antispam_spool2dir_spam = /tmp/spamspool/%%020lu-%u-%%05lus antispam_trash = trash;Trash;Deleted Items;Deleted Messages antispam_verbose_debug = 0 expire = Trash expire2 = Trash/* expire3 = Spam expire_dict = proxy::expire quota = dict:User quota::proxy::quota quota_exceeded_message = Uzivatel %u ma zaplnenou schranku. quota_rule = *:storage=1G quota_rule2 = Trash:storage=+100M sieve = file:~/sieve;active=~/.dovecot.sieve sieve_after = /etc/dovecot/sieve_after sieve_before = /etc/dovecot/sieve_before sieve_extensions = +spamtest +spamtestplus sieve_spamtest_max_value = 15 sieve_spamtest_status_header = X-Spam-Level sieve_spamtest_status_type = strlen trash = /etc/dovecot/dovecot-trash.conf.ext } pop3_client_workarounds = outlook-no-nuls oe-ns-eoh pop3_uidl_format = UID%u-%v postmaster_address = sysadmin(a)ehosting.cz protocols = " imap lmtp sieve pop3" service auth-worker { user = $default_internal_user } service dict { unix_listener dict { user = vmail } } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0660 user = postfix } user = vmail } service stats { unix_listener stats-writer { user = vmail } } 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 syslog_facility = local0 userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } verbose_proctitle = yes protocol lmtp { mail_plugins = quota trash expire sieve quota trash expire } protocol lda { mail_plugins = quota trash expire sieve } protocol imap { mail_plugins = quota trash expire antispam imap_quota } ========================== The dovecot.err shows the two mentioned error lines (Panic:, Error:) plus: Dec 7 13:12:21 s6mail dovecot: imap(ttt(a)mail2.swpraha.cz)<13466><wezwvN61RK0AAAAAAAAAAAAAAAAAAAAB>: Fatal: master: service(imap): child 13466 killed with signal 6 (core dumps disabled - https://dovecot.org/bugreport.html#coredumps) Please let me know if you need any other details. Thanks for any suggestion --Jiri Kacena

2 2

logging in to postfixadmin failed probably because of a dovecot error
by peacecop kalmer: 07 Dec '20

07 Dec '20

I can’t log in to postfixadmin anymore. It says that the username or password is incorrect. It can’t be incorrect as I’ve stored them in Google and “Chrome”. I have two admin accounts and none of them can’t be used for logging in. So I changed the main password with “setup.php” and copied that hash into the configuration file. Then, I deleted one of the admin accounts directly in the database from the table “admin”. Finally, I tried to recreate that deleted admin account using “setup.php”. I get the following error message: “can’t encrypt password with dovecotpw, see error log for details”. I had a look into the error log file of postfixadmin and found these complaints: [Wed Dec 02 02:33:37.551048 2020] [authz_core:debug] [pid 30540] mod_authz_core.c(809): [client 192.168.1.65:54948] AH01626: authorization result of Require all granted: granted, referer:https://postfixadmin.tennis24.ee/setup.php [Wed Dec 02 02:33:37.551070 2020] [authz_core:debug] [pid 30540] mod_authz_core.c(809): [client 192.168.1.65:54948] AH01626: authorization result of : granted, referer:https://postfixadmin.tennis24.ee/setup.php [Wed Dec 02 02:33:37.551280 2020] [php7:warn] [pid 30540] [client 192.168.1.65:54948] PHP Warning: Cannot assign an empty string to a string offset in /usr/share/postfixadmin/variables.inc.php on line 31, referer:https://postfixadmin.tennis24.ee/setup.php [Wed Dec 02 02:33:37.568128 2020] [php7:notice] [pid 30540] [client 192.168.1.65:54948] dovecotpw password encryption failed., referer:https://postfixadmin.tennis24.ee/setup.php [Wed Dec 02 02:33:37.568155 2020] [php7:notice] [pid 30540] [client 192.168.1.65:54948] STDERR output: doveconf: Fatal: Error in configuration file /etc/dovecot/conf.d/10-ssl.conf line 13: ssl_cert: Can't open file /etc/letsencrypt/live/test.tennis24.ee/fullchain.pem: Permission denied\n, referer:https://postfixadmin.tennis24.ee/setup.php [Wed Dec 02 02:33:37.568897 2020] [deflate:debug] [pid 30540] mod_deflate.c(854): [client 192.168.1.65:54948] AH01384: Zlib: Compressed 1320 to 732 : URL /setup.php, referer:https://postfixadmin.tennis24.ee/setup.php Is the issue connected to the permission problem? If so why is the permission denied? I can't even receive any mails to the address kalmer(a)test.tennis24.ee anymore. If I send out it works fine but no mail arrives. -- *peacecop kalmer:* *Instituudi tee 3-27 * *76902 * *Harku * *Harku* *Harjumaa* Estonia *+372 652 4228 * *+372 5620 4556 * *__________________________________________________________________ *

2 1

http pipelining on auth_policy_server
by Adrian M 07 Dec '20

07 Dec '20

Hi, I'm curious to know if dovecot can be configured to do pipelining for auth_policy in order to use less connection to the server and keep them for longer. I'm working on making a small policy server and the lack of persistent connections is a cause of overhead. Thank you !

2 2

[patch] enhancement for adding limits to solr and tika parsing
by John Fawcett 07 Dec '20

07 Dec '20

Hi As mentioned in a previous thread, the solr + tika combination has caused me some issues due to attachment size. While tika seems to be able to parse large attachments, the resulting volume of text can overwhelm the solr server. One solution would be to throw resources at the problem, but in my case such large attachments don't contain anything worthwile indexing. Additionally I don't want people to be able to randomly crash my solr server by sending large compressed attachments that expand into huge volumes for solr. It's also a safety feature to have sane limits on what can be indexed. Attached is a first attempt to address the problem. I did not find a way to easily get actual attachment sizes, so I used an already available information - the overall message size. It may not be ideal but at least introduces limits where none existed. I have introduced two new parameters for the plugin section, for example: plugin { fts_max_size = 2M fts_max_size_tika = 1M } They can be used separately or together. Both sizes refer to the overall message size. The meaning is: fts_max_size - do not parse message bodies if the message size exceeds this value. A value of 0 indicates no limit. If the message body is not parsed, attachments are also not parsed. fts_max_size_tika - do not parse message attachments with tika if the message size exceeds this value. A value of 0 indicates no limit. If using both settings it makes sense to have fts_max_size > fts_max_size_tika, since with a smaller fts_max_size bodies are not indexed including attachments and the fts_max_size_tika will have no effect. The difference (ft_max_size - fts_max_size_tika) places an upper bound on the size of the non attachment body text that will be indexed. However, any attachments over the fts_size will automatically consume this limit and no body text will be indexed for those messages. I've only updated the tika parser not the script parser though the script parser potentially could benefit from this approach. The attached patch also includes the rolled up patch for using basic auth with the tika server and the previous posted patch (not mine) which solves an assert when using solr and tika together. John

1 0

Re: Re: Re: Dovecot+Solr+Tika segmentation fault
by Manuel Josupeit-Walter 07 Dec '20

07 Dec '20

>>> A fix was posted on this list which seems to avoid segfaults when >>> using solr+tika. I reposted it not long ago in response to another >>> question. Before exploring the other segfaults it would be worthwhile >>> getting that fix. If other segfaults continue then I suggest posting >>> the logging from Dovecot >> >> https://github.com/dovecot/core/commit/043d111cea78533cf22d3bfe0872c8376d84… >> (DOV-4090) >> >> Scheduled for 2.3.13. > > I applied the fix and will observe it for the next couple of days. Unfortunately, the issue still persists even with this patch. The log message is slightly different, though, regarding disconnection: Dec 03 17:10:49 server.name tika[988]: INFO tika/ (application/pdf) Dec 03 17:10:49 server.name tika[988]: INFO tika/ (image/png) Dec 03 17:10:49 server.name kernel: indexer-worker[15805]: segfault at 0 ip 00007f140483db64 sp 00007ffc04fa7960 error 4 in libdovecot.so.0.0.0[7f14047f3000+db000] Dec 03 17:10:49 server.name kernel: Code: 89 f5 48 8d b8 f0 01 00 00 48 8b 52 08 4c 8b 62 48 e8 90 89 fb ff 48 8b 44 24 08 be 00 20 00 00 4c 89 ef 48 8b 80 10 01 00 00 <4c> 8b 38 e8 64 b2 fb ff 48 8b 44 24 0 Dec 03 17:10:49 server.name dovecot[988]: Dec 03 16:10:49 indexer: Error: Indexer worker disconnected, discarding 1 requests for username_stripped Dec 03 17:10:49 server.name dovecot[988]: Dec 03 16:10:49 indexer-worker(username_stripped)<1952><Ed3ek5G1BMQgARa4EL8DAKGMINRlZjjS:c+gACAkOyV+gBwAAhFs1yA>: Fatal: master: service(indexer-worker): child 1952 killed It seems that there is something else going wrong in this version. Best, Manuel

3 3

quota-status for outgoing mail (Dovecot/Postfix)
by Peter Folta 06 Dec '20

06 Dec '20

[Dovecot version 2.3.11.3 (502c39af9)] Hi all, I’m using Dovecot’s quota-status service to let Postfix check the recipient’s quota before accepting emails following the guide here: https://blog.sys4.de/postfix-dovecot-mailbox-quota-en.html <https://blog.sys4.de/postfix-dovecot-mailbox-quota-en.html>. This works well for inbound emails. I would like to set up something similar for outbound email, i.e. if a user is over quota, they should not be allowed to send new emails. At the moment, the setup is in a bit of an inconsistent state: Users that have exceeded their quota are still able to send outbound emails but saving them in their Sent folder will fail leaving them without a copy. I have tried using Dovecot’s quota-status in Postfix’s smtpd_send_restrictions but didn’t get this to work. A quick look at the Dovecot source code seems to suggest that the quota-status plugin is only checking the recipient address: https://github.com/dovecot/core/blob/master/src/plugins/quota/quota-status.… <https://github.com/dovecot/core/blob/master/src/plugins/quota/quota-status.…> and https://github.com/dovecot/core/blob/master/src/plugins/quota/quota-status.… <https://github.com/dovecot/core/blob/master/src/plugins/quota/quota-status.…>. I suspect it’s not possible to use the quota-status service to control outbound email but thought I’d ask to confirm. I’m wondering if there’s a different way to achieve this? Thanks Peter

3 2

Files in tmp directory
by David Morsberger 05 Dec '20

05 Dec '20

I had to restore many thousands of dovecot emails from a crashed Mac Server to a new Ubuntu server. After completing I am noticing a few things that may be okay or may need to be fixed. 1) a couple of mailboxes have a lot (one has 102462) emails in the tmp directory. The files do not have the standard Mairdir++ filename format. An example: 1581262582.M397740P72267.mini.mmpcrofton.com <http://1581262582.m397740p72267.mini.mmpcrofton.com/> (missing the stuff at the end, ,S=,W=:2,S) 2) I see files in the cur directory that do not have the Maildir++ format. An example: 1601287326.V810Ie80087M240104.mmp-mail.mmpcrofton.com:2,S. (do not have the ,S=,W= values and the second value, V810Ie80087M240104, is longer that the other file names) How do I get the emails in (1) out of tmp? Do I need to convert the emails in (2)? David

2 3

Combine director and HAProxy for loadbalancig and failover
by Steven Varco 05 Dec '20

05 Dec '20

Hi All I’m trying to achive an active/active cluster with dovecot-director and HAProxy, as the director does not do health checks (loadblancing only) and I want both, loadblancing AND failover, where the latter is far more important to me (loadblancing I would just use as an addon and for curiosity, it is not really need in my setup). However, I’m not sure if this combination can be used that way, as I found almost no documentation on this. What I found is using either directory OR haproxy with dovecot, but not both. So I guess, that the description here is intended to use without the director: https://wiki2.dovecot.org/HAProxy This older list post is basically exaclty, what I’m trying to achive: https://dovecot.org/pipermail/dovecot/2015-July/101487.html Clients --> Load Balancer(HAProxy) --> Dovecot Proxy(DP) --> Dovecot Director(DD) --> MS1 / MS2 As far as I understood, this would require to (statically) set a host= entry for each client which would give another single point of failure? However reading the documentation: https://doc.dovecot.org/configuration_manual/haproxy/ assumes that this setup IS actually possible. Unfortunately it does not describe how dovecot must be setup at this point. So I assume since HAProxy is listening on port 1143 (for IMAP) and dovecot (with directror enabled) is listening on port 143, which is the main entry point for clients. So in this setup dovecot-director should first pass the mail traffic to HAProxy on port 1143 and then HAProxy passes it to the actual imap servers? So how would the dovecot setup on the director servers look like and how on the dovecot imap mail servers? My setup consist of each two machines: loadblancer (with HAProxy and dovecot-director) and dovecot imap servers. Last but not least, I found documentation for „dovemon“, which, if I got that correctly, should replace the external tool „poolmon“: https://doc.dovecot.org/configuration_manual/dovemon/ - However, I could not find out where the configuration YAML file (/etc/dovecot/dovemon.config.yml) should get included in the main dovecot configuration. By default this file would not be included at all and therefore would have no effect… thanks. Steven My setup: LOADBALANCERS: Currently one only running on: 10.0.2.26 haproxy: Exactly as: https://doc.dovecot.org/configuration_manual/haproxy/ where the backend servers line have been replaced with the mail servers. dovecot -n # 2.2.36 (1f10bfa63): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.24 (124e06aa) # OS: Linux 3.10.0-1127.19.1.el7.x86_64 x86_64 CentOS Linux release 7.8.2003 (Core) # Hostname: lb01.example.com auth_verbose = yes director_mail_servers = 10.0.2.30 10.0.2.29 director_servers = 10.0.2.26 disable_plaintext_auth = no first_valid_uid = 1000 haproxy_trusted_networks = 10.0.2.0/24 mail_location = maildir:~/Maildir managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date index ihave duplicate mime foreverypart extracttext mbox_write_locks = fcntl namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { args = proxy=y ssl=any-cert nopassword=y driver = static } plugin { sieve = file:~/sieve;active=~/.dovecot.sieve } protocols = imap pop3 lmtp sieve service director { fifo_listener login/proxy-notify { mode = 0666 } inet_listener { port = 9090 } unix_listener director-userdb { mode = 0600 } unix_listener login/director { mode = 0666 } } service imap-login { executable = imap-login director inet_listener imap { port = 143 } inet_listener imap_haproxy { haproxy = yes port = 10143 } } service managesieve-login { inet_listener sieve { port = 4190 } } service pop3-login { executable = pop3-login director } ssl_cert = </etc/letsencrypt/live/mail-lb.tech-island.xyz/fullchain.pem ssl_key = # hidden, use -P to show it verbose_proctitle = yes protocol lmtp { auth_socket_path = director-userdb mail_plugins = " sieve" } protocol lda { mail_plugins = " sieve" } MAIL SERVERS: mx01: 10.0.2.30 mx02: 10.0.2.29 dovecot -n # 2.2.36 (1f10bfa63): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.24 (124e06aa) # OS: Linux 3.10.0-1127.19.1.el7.x86_64 x86_64 CentOS Linux release 7.8.2003 (Core) # Hostname: mx01.example.com auth_mechanisms = plain login auth_verbose = yes dict { sqlquota = mysql:/etc/dovecot/dict-sqlquota.conf.ext } doveadm_password = # hidden, use -P to show it doveadm_port = 14310 first_valid_uid = 1000 login_trusted_networks = 10.0.2.0/24 mail_location = maildir:~/Maildir mail_plugins = quota notify replication managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date index ihave duplicate mime foreverypart extracttext mbox_write_locks = fcntl namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = separator = / type = private } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { mail_replica = tcp:10.0.2.29 quota = maildir:User quota quota_exceeded_message = Quota exceeded, please go to http://www.tech-island.xyz/over_quota_help for instructions on how to fix this. quota_rule2 = INBOX.Trash:storage=+100M quota_status_nouser = DUNNO quota_status_overquota = 552 5.2.2 Mailbox is full / Mailbox ist voll quota_status_success = DUNNO quota_warning = storage=90%% quota-warning 90 %u quota_warning2 = -storage=90%% quota-warning below %u sieve = file:~/sieve;active=~/.dovecot.sieve } postmaster_address = postmaster(a)tech-island.xyz protocols = imap pop3 lmtp sieve replication_dsync_parameters = -d -l 30 -U service aggregator { fifo_listener replication-notify-fifo { user = vmail } unix_listener replication-notify { user = vmail } } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-userdb { user = vmail } } service dict { unix_listener dict { user = vmail } } service doveadm { inet_listener { port = 14310 } } service managesieve-login { inet_listener sieve { port = 4190 } } service quota-status { client_limit = 1 executable = quota-status -p postfix inet_listener { port = 14340 } } service quota-warning { executable = script /usr/local/libexec/dovecot/quota-warning.sh unix_listener quota-warning { user = vmail } user = vmail } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { mode = 0600 user = vmail } } ssl = required ssl_cert = </etc/ssl/acme/certs/mail.tech-island.xyz.chain.crt ssl_key = # hidden, use -P to show it userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } verbose_proctitle = yes protocol lmtp { mail_plugins = quota notify replication sieve } protocol lda { mail_plugins = quota notify replication sieve } protocol imap { mail_max_userip_connections = 20 mail_plugins = quota notify replication imap_quota } -- https://steven.varco.ch/

1 0

Server-side threading
by ohw.giles＠gmail.com 05 Dec '20

05 Dec '20

Hi list, Considering a message A in INBOX, where a reply B is sent and copied to the recipient's SENT folder, and to which a reply-to-reply C is received, again in INBOX, how should the list of threads in INBOX be (ideally) retrieved? Using THREADS=REFS when listing threads in INBOX to avoid matching unrelated threads unfortunately seems to miss the above example because B is only in SENT, not INBOX. REFERENCES allows A to be linked to C, but the sent message is missing from the returned thread. Of course this is by design. When listing messages in a selected mailbox, many modern clients provide the experience of listing the messages grouped by thread, showing all threads where *at least one message in the thread is in the selected mailbox*. IIUC, clients usually build their own indexes to achieve this, which seems wasteful. Does dovecot provide a server-side way to list or search messages and return threaded results in this manner?

1 0

doveadm sync return "failed: EOF (version not received)"
by Olivier Mars 04 Dec '20

04 Dec '20

Hi, I have 2 dovecot servers, server1.domain.tld and server2.domain.tld and I'm not able to do a simple doveadm backup command between them. Dovecot version 2.3.11.3, on debian buster, (installed from apt) I try to execute this cmd between to of my dovecot servers : doveadm sync -u postmaster(a)domain.tld remote:root@server2.domain.tld and it returns : doveadm(postmaster(a)domain.tld): Debug: remote(/var/run/dovecot/doveadm-server): auth-master: userdb lookup(postmaster(a)domain.tld): Started userdb lookup doveadm(postmaster(a)domain.tld): Debug: remote(/var/run/dovecot/doveadm-server): auth-master: conn unix:/var/run/dovecot/auth-userdb: Connecting doveadm(postmaster(a)domain.tld): Debug: remote(/var/run/dovecot/doveadm-server): auth-master: conn unix:/var/run/dovecot/auth-userdb (pid=118292,uid=0): Client connected (fd=15) doveadm(postmaster(a)domain.tld): Debug: remote(/var/run/dovecot/doveadm-server): auth-master: userdb lookup(postmaster(a)domain.tld): auth USER input: postmaster(a)domain.tld mail=maildir:/mails/2/domain.tld/postmaster/Maildir:INDEX=/var/lib/dovecot/indexes/domain.tld/postmaster@domain.tld home=/mails/2/domain.tld/postmaster quota_rule=*:storage=3145728000b:messages=500k doveadm(postmaster(a)domain.tld): Debug: remote(/var/run/dovecot/doveadm-server): auth-master: userdb lookup(postmaster(a)domain.tld): Finished userdb lookup (username=postmaster(a)domain.tld mail=maildir:/mails/2/domain.tld/postmaster/Maildir:INDEX=/var/lib/dovecot/indexes/domain.tld/postmaster@domain.tld home=/mails/2/domain.tld/postmaster quota_rule=*:storage=3145728000b:messages=500k) doveadm(postmaster(a)domain.tld): Debug: remote(/var/run/dovecot/doveadm-server): Added userdb setting: mail=maildir:/mails/2/domain.tld/postmaster/Maildir:INDEX=/var/lib/dovecot/indexes/domain.tld/postmaster@domain.tld doveadm(postmaster(a)domain.tld): Debug: remote(/var/run/dovecot/doveadm-server): Added userdb setting: plugin/quota_rule=*:storage=3145728000b:messages=500k doveadm(postmaster(a)domain.tld): Debug: remote(/var/run/dovecot/doveadm-server): Effective uid=65534, gid=65534, home=/mails/2/domain.tld/postmaster doveadm(postmaster(a)domain.tld): Debug: remote(/var/run/dovecot/doveadm-server): Quota root: name=Mailbox backend=count args= doveadm(postmaster(a)domain.tld): Debug: remote(/var/run/dovecot/doveadm-server): Quota rule: root=Mailbox mailbox=* bytes=3145728000 messages=512000 doveadm(postmaster(a)domain.tld): Debug: remote(/var/run/dovecot/doveadm-server): Quota grace: root=Mailbox bytes=314572800 (10%) doveadm(postmaster(a)domain.tld): Debug: remote(/var/run/dovecot/doveadm-server): Namespace inbox: type=private, prefix=INBOX., sep=., inbox=yes, hidden=no, list=yes, subscriptions=yes location=maildir:/mails/2/domain.tld/postmaster/Maildir:INDEX=/var/lib/dovecot/indexes/domain.tld/postmaster@domain.tld doveadm(postmaster(a)domain.tld): Debug: remote(/var/run/dovecot/doveadm-server): maildir++: root=/mails/2/domain.tld/postmaster/Maildir, index=/var/lib/dovecot/indexes/domain.tld/postmaster(a)domain.tld, indexpvt=, control=, inbox=/mails/2/domain.tld/postmaster/Maildir, alt= doveadm(postmaster(a)domain.tld): Debug: remote(/var/run/dovecot/doveadm-server): Namespace : type=private, prefix=, sep=, inbox=no, hidden=yes, list=no, subscriptions=no location=fail::LAYOUT=none doveadm(postmaster(a)domain.tld): Debug: remote(/var/run/dovecot/doveadm-server): none: root=, index=, indexpvt=, control=, inbox=, alt= doveadm(postmaster(a)domain.tld): Debug: remote(/var/run/dovecot/doveadm-server): quota: quota_over_flag check: quota_over_script unset - skipping doveadm(postmaster(a)domain.tld): Debug: remote(/var/run/dovecot/doveadm-server): brain M: Namespace INBOX. has location maildir:/mails/2/domain.tld/postmaster/Maildir:INDEX=/var/lib/dovecot/indexes/domain.tld/postmaster@domain.tld doveadm(postmaster(a)domain.tld): Debug: remote(/var/run/dovecot/doveadm-server): Namespace INBOX.: Using permissions from /mails/2/domain.tld/postmaster/Maildir: mode=0700 gid=default doveadm(postmaster(a)domain.tld): Error: remote(/var/run/dovecot/doveadm-server): read(root(a)server2.domain.tld) failed: EOF (version not received) doveadm(postmaster(a)domain.tld): Debug: remote(/var/run/dovecot/doveadm-server): auth-master: conn unix:/var/run/dovecot/auth-userdb (pid=118292,uid=0): Disconnected: Connection closed (fd=15) On the destination server, I can see that the destination server is well retrieving the user's info in userdb, before saying : server2 dovecot: doveadm: Error: read(<local>) failed: EOF (version not received) I tried to activate verbosity everywhere, but It does not show anything, like : ssh -v -lroot server2.domain.tld doveadm dsync-server -upostmaster(a)domain.tld -U debug1: Authentication succeeded (publickey). Authenticated to server2;domain.tld ([w.x.y.z]:22). debug1: channel 0: new [client-session] debug1: Requesting no-more-sessions(a)openssh.com debug1: Entering interactive session. debug1: pledge: network debug1: client_input_global_request: rtype hostkeys-00(a)openssh.com want_reply 0 debug1: Remote: /root/.ssh/authorized_keys:4: key options: agent-forwarding port-forwarding pty user-rc x11-forwarding debug1: Remote: /root/.ssh/authorized_keys:4: key options: agent-forwarding port-forwarding pty user-rc x11-forwarding debug1: Sending environment. debug1: Sending env LANG = fr_FR.UTF-8 debug1: Sending command: doveadm dsync-server -upostmaster(a)domain.tld -U debug1: client_input_channel_req: channel 0 rtype exit-status reply 0 debug1: client_input_channel_req: channel 0 rtype eow(a)openssh.com reply 0 debug1: channel 0: free: client-session, nchannels 1 Transferred: sent 2800, received 2820 bytes, in 0.1 seconds Bytes per second: sent 25466.2, received 25648.1 debug1: Exit status 0 If somebody can tell me some hints to go further, it'll be very apreciate. Thanks ! Here is the doveconf -n output (the two servers have the same) # 2.3.11.3 (502c39af9): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.11 (6c69c917) # OS: Linux 4.19.0-12-amd64 x86_64 Debian 10.6 # Hostname: server1 auth_cache_negative_ttl = 0 auth_cache_size = 100 M auth_cache_ttl = 5 mins auth_master_user_separator = * default_client_limit = 2000 disable_plaintext_auth = no doveadm_api_key = # hidden, use -P to show it doveadm_worker_count = 50 listen = w.x.y.z mail_fsync = always mail_gid = nogroup mail_location = maildir:~/Maildir:INDEX=/var/lib/dovecot/indexes/%d/%n mail_max_userip_connections = 300 mail_plugins = quota mail_uid = nobody maildir_very_dirty_syncs = yes namespace inbox { inbox = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk { auto = subscribe autoexpunge = 90 days special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox "Sent Messages" { auto = no special_use = \Sent } mailbox Trash { auto = subscribe autoexpunge = 90 days special_use = \Trash } prefix = INBOX. separator = . } passdb { args = /etc/dovecot/master-users driver = passwd-file master = yes result_success = continue } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { imapsieve_mailbox1_before = file:/var/lib/dovecot/sieve/report-spam.sieve imapsieve_mailbox1_causes = COPY imapsieve_mailbox1_name = INBOX.Junk imapsieve_mailbox2_before = file:/var/lib/dovecot/sieve/report-ham.sieve imapsieve_mailbox2_causes = COPY imapsieve_mailbox2_from = INBOX.Junk imapsieve_mailbox2_name = * quota = count:Mailbox quota_rule = *:storage=1G:messages=500k quota_vsizes = yes sieve = file:~/sieve;active=~/.dovecot.sieve sieve_before = /var/lib/dovecot/sieve/antispam.sieve sieve_global_extensions = +vnd.dovecot.pipe +vnd.dovecot.environment +spamtest +spamtestplus sieve_pipe_bin_dir = /var/lib/dovecot/sieve sieve_plugins = sieve_imapsieve sieve_extprograms sieve_spamtest_max_header = X-Spam-Status: [[:alnum:]]+, score=-?[[:digit:]]+\.[[:digit:]] required=([[:digit:]]+\.[[:digit:]]).* sieve_spamtest_status_header = X-Spam-Status: [[:alnum:]]+, score=(-?[[:digit:]]+\.[[:digit:]]) sieve_spamtest_status_type = score } pop3_fast_size_lookups = yes pop3_reuse_xuidl = yes pop3_save_uidl = yes pop3_uidl_format = %f protocols = imap pop3 lmtp service anvil { client_limit = 5000 unix_listener anvil-auth-penalty { mode = 00 } } service auth { client_limit = 0 } service doveadm { inet_listener http { port = 8080 } vsz_limit = 2 G } service imap-login { process_limit = 2000 service_count = 1 } service imap { client_limit = 1 process_limit = 5000 vsz_limit = 1 G } service indexer-worker { process_limit = 20 } service lmtp { client_limit = 1 inet_listener lmtp { port = 24 } process_limit = 200 process_min_avail = 20 vsz_limit = 1 G } service pop3-login { process_limit = 2000 service_count = 1 } ssl = no submission_host = smtp.domain.tld:25 userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } protocol lmtp { mail_plugins = quota sieve } protocol imap { mail_plugins = quota imap_sieve imap_quota }

1 0

Any RPMs for aarch64 available?
by Peter Cooper Jr. 04 Dec '20

04 Dec '20

Hey, I really appreciate Dovecot being available with standard repos in repo.dovecot.org. I'm currently using the "CentOS 7" one on Amazon Linux 2 and it works great for x86_64. I'm wondering if there are any plans for also providing arm builds (aarch64) at some point? Or if they're available somewhere else already? I may play around with compiling things myself, but just downloading an official package is generally the easier way to go so I thought it couldn't hurt to ask. Thanks, Peter

3 4

follow up to my mail issues I posted about
by Christy S 03 Dec '20

03 Dec '20

Okay. A few days late, but I've gone through the replies I received from several of you and consolidated responses into one mail. Of course life gets crazy when I need to sit down and work on things. "It seems to me Thunderbird is struggling to write to the Sent mailbox, so disk space, and file permissions are the obvious ones to check. And yes, on the server rather than your local machine, as you're using IMAP" It's definitely not disc space. I wouldn't think an upgrade would change permissions, but it's a place to check. I'm showing my newbieness here but, I'm not even sure what account should have access to those files. I know, it's a miracle I got all this working in the first place. I should have taken notes, but I did so much fiddling with this and that to make it behave that I didn't know what to write down. "Anything interesting in the dovecot logs at the time when you check?" So I looked up dovecot logs on google, and what I'm seeing is that dovecot generally writes to mail logs under /var/log. The stuff I sent in my first email came from mail.err in that folder. The only other file I could find was mail.log. Using tail on that file, I see entries like these. Dec 2 20:53:07 kylesmith-music postfix/smtpd[396853]: warning: unknown[212.70.149.37]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Dec 2 20:53:07 kylesmith-music postfix/smtpd[396853]: disconnect from unknown[212.70.149.37] ehlo=1 auth=0/1 rset=1 quit=1 commands=3/4 There are similar entries from a different ip address, but interestingly neither match the ip address of our fiber modem so I have no idea what's going on there. "First, do you have a backup prior to upgrading the server? You may want to refer to that to get a clean idea of how the configuration was set up initially. Sometimes the upgrade process can reset configuration files and its usually easier to work from a known working configuration. " I really wish I did, but I'm not sure how to effectively back up a VPS. "Second, can you describe how you set the mail stack you are using up?" I can tell you it's postfix and dovecot. That's what a lot of articles recommended, so I went with that. We use different devices so I chose to use imap as it interfaces directly with the stored mail on the server. Usually this is good, except now when it breaks. "Its possible the issue is SSL related but its difficult to say. There have been a number of breaks with SSL encryption in recent years which is why the cipher list has been adjusted," SSL is definitely my weakest point of knowledge. I know I had it working smoothly but it was basically following how to stuff. The reason we're using it even for mail has to do with someone in my husband's life who would get in and mess things up if he had the chance, so I'm trying to make sure he doesn't have that chance by locking things down tight. "google can also be out of date I'd recommend using a date filter when using it for checking configurations and limit it only to the last 1-2 years as you will get more relevant information typically." Oh my gosh, that alone would be extremely helpful. The number of seriously outdated articles I had to filter through when I set this up in the first place is just unreal. Mind telling me how to do a date filter? Otherwise, I'll google how to use google, hahaha. "The configuration parameter for the cipher list uses HIGH as a default profile and if I recall correctly that disables lower TLS versions that are susceptible to certain types of attacks. (SSL3,TLS1,TLS1.1,1.2 I think) The dovecot documentation explains what the defaults are for HIGH. The ! prevents using specifica protocols and configuration is usually a chain (processed from left to right until a match is found). DH is the diffie-helman exchange. Usually this file is recalculated on a per server basis to prevent pre-calculation attacks on SSL and usually it must meet a certain key length. DH Groups 1 and 2 are known to be insecure." Okay, that went way over my head, but it sounds like good information to have and study up more on, hopefully after I get the immediate issue solved. If I'm following you correctly at all though I could see that potentially being my issue, hmm. I will for sure see if I can get my hands on that book. "Some quick thoughts here — if the changes you mentioned did not solve the issue, I would definitely comment those back out so you are only troubleshooting one thing at a time." Fair point. I commented out the one about dh high, then hopefully reloaded the configuration, dovecot reload? That done, I tried sending an email from the domain to my gmail using thunderbird. I got the same message, but it did actually send this time. However, when I replied to the test message with my gmail account, it wasn't received by thunderbird. I do see it using the mail app on the server, though. "Next, are you able to send email using any other client?" I can send mail locally on the server from one account to another for sure. I managed it once, at least. Those mail clients seem clunky though so I may not be doing things correctly to test. "Third, try disabling all SSL and see if you are able to send via Thunderbird or really, any client at all…" Is there an easy way to disable ssl for now and then reenable it? That would definitely help narrow this down. "Your DH parameters are too weak. You should generate at least 2048 byte parameters." To be honest, I don't even recall setting up DH parameters. I would guess that probably happened when I was setting up ssl? Again, thank you to each of you for helping with this. I really try not to send stuff like this to mailing lists that are technical in nature, but this is important business mail he's potentially missing and I'm a bit out of my league. First project once this gets fixed will be learning how to back up the server. Christy

3 2

New Version
by Jorge Bastos 02 Dec '20

02 Dec '20

Howdy, Sorry the question, I havent seen any update on github since July, is everything ok with Dovecot? Thanks,

2 3

Re: Re: Dovecot+Solr+Tika segmentation fault
by Manuel Josupeit-Walter 02 Dec '20

02 Dec '20

>> A fix was posted on this list which seems to avoid segfaults when >> using solr+tika. I reposted it not long ago in response to another >> question. Before exploring the other segfaults it would be worthwhile >> getting that fix. If other segfaults continue then I suggest posting >> the logging from Dovecot >> > > https://github.com/dovecot/core/commit/043d111cea78533cf22d3bfe0872c8376d84… > (DOV-4090) > > Scheduled for 2.3.13. Meanwhile, I also found the fix from October. I can confirm that the issue occurred on 2.3.11.3 only. I switched to the previous version (which is pretty easy thanks to Docker) and the issue disappeared. All messages were indexed properly afterwards. I applied the fix and will observe it for the next couple of days. The assertions have been misplaced anyway from my viewpoint because the asserted fields (or properties or whatever, I don't know how they're called in C) are not accessed in every case. I am happy that this is scheduled for 2.3.13. Although, I hope that the payload_input or payload_output won't be NULL when payload_finished is true. :) Thanks a lot to you guys for all the effort. I would not be able to resolve this on my own without your help. Best, Manuel

1 0

Error: Mailbox INBOX: Sync failed
by Jos Chrispijn 02 Dec '20

02 Dec '20

Just saw in my logfile this line appeared: imap(xxxxxx)<56614><CMMJw9i0aoBSsH9H>: Error: Mailbox INBOX: Sync failed for mbox: Expunged message reappeared to mailbox (UID 174550 < 174552, seq=11, idx_msgs=9) Looks like messages' UIDs are mixed up? I thought that if Dovecot sees broken X-UID headers for "new" messages, they're silently fixed? Can you tell how I can correct this error/warning? Thanks! BR, Jos

1 1

Dovecot+Solr+Tika segmentation fault
by Manuel Josupeit-Walter 02 Dec '20

02 Dec '20

3 2

Bug report: invalid \HasNoChildren in response when asterisk is used in the name
by Merijn Schering 01 Dec '20

01 Dec '20

Hi, I'm using dovecot 2.3.4.1 (f79e8e7e4). I have created a folder called "Test with *". Now when I do a command: A3 LIST "" "%" RETURN (CHILDREN STATUS (MESSAGES UNSEEN)) It responds: * STATUS Test with * ( MESSAGES 0 UNSEEN 0 ) * LIST ( \HasNoChildren \UnMarked ) / Spam But it actually has children! This only happens when I use a * character in the name. I hope you can fix this some day. Thanks! Best regards, Merijn Schering Intermesh https://www.group-office.com https://twitter.com/GroupOffice

2 1

doveadm crash on import
by Ralf Hildebrandt 01 Dec '20

01 Dec '20

% doveadm import -u restore(a)backup.invalid mdbox:/home/copymail2/mdbox '' mailbox INBOX header Reply-To gmail.com results in: doveadm(restore(a)backup.invalid): Panic: fcntl(/home/copymail2/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.log, write-lock, F_SETLKW) locking failed: Resource deadlock avoided (WRITE lock held by pid 37462) doveadm(restore(a)backup.invalid): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(backtrace_append+0x42) [0x7fb131662d22] -> /usr/lib/dovecot/libdovecot.so.0(backtrace_get+0x1e) [0x7fb131662e3e] -> /usr/lib/dovecot/libdovecot.so.0(+0xed75e) [0x7fb13166d75e] -> /usr/lib/dovecot/libdovecot.so.0(+0xed7a1) [0x7fb13166d7a1] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7fb1315c2beb] -> /usr/lib/dovecot/libdovecot.so.0(+0xf2932) [0x7fb131672932] -> /usr/lib/dovecot/libdovecot.so.0(file_wait_lock_error+0x26) [0x7fb131672966] -> /usr/lib/dovecot/libdovecot.so.0(file_wait_lock+0x20) [0x7fb131672a00] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_transaction_log_file_lock+0x90)[0x7fb131a28050] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_transaction_log_lock_head+0x3d)[0x7fb131a2d4dd] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_transaction_log_append_begin+0x3e)[0x7fb131a26a8e] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xf52f2) [0x7fb131a202f2] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_index_transaction_commit_full+0x76)[0x7fb131a20826] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_index_transaction_commit+0x1c)[0x7fb131a208bc] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xdd619) [0x7fb131a08619] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_cache_add+0x214) [0x7fb131a08f24] -> /usr/lib/dovecot/libdovecot-storage.so.0(index_mail_parse_header+0x5a5) [0x7fb1319eaef5] -> /usr/lib/dovecot/libdovecot.so.0(+0xc5b13) [0x7fb131645b13] -> /usr/lib/dovecot/libdovecot.so.0(i_stream_read_memarea+0x74) [0x7fb13167ab14] -> /usr/lib/dovecot/libdovecot.so.0(i_stream_read+0x29) [0x7fb13167ae49] -> /usr/lib/dovecot/libdovecot.so.0(i_stream_read_data+0x3d) [0x7fb13167b7bd] -> /usr/lib/dovecot/libdovecot.so.0(message_parse_header_next+0x68) [0x7fb13164c288] -> /usr/lib/dovecot/libdovecot.so.0(message_parse_header+0x4f) [0x7fb13164cc5f] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xc9f61) [0x7fb1319f4f61] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xcb214) [0x7fb1319f6214] -> /usr/lib/dovecot/libdovecot-storage.so.0(index_storage_search_next_nonblock+0x10d)[0x7fb1319f69ed] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_search_next_nonblock+0x22)[0x7fb131978df2] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_search_next+0x3d)[0x7fb131978e5d] -> doveadm(+0x31c14) [0x557ac63f1c14] -> doveadm(+0x2c518) [0x557ac63ec518] -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebrandt(a)charite.de | https://www.charite.de

2 2

director_username_hash = %d and doveadm director map
by Ralf Becker 30 Nov '20

30 Nov '20

Our directors hash by domain (director_username_hash = %d), as some of our users share folders with other users of the same domain. We now started using director tags to map domains to their backends. Unfortunately doveadm director map seems no to work with director_username_hash = %d user hash mail server ip expire time <unknown> 432784257 10.44.88.1 2020-11-23 13:10:55 <unknown> 4244233328 10.44.88.1 2020-11-23 13:13:55 <unknown> 1913982503 10.44.88.1 2020-11-23 13:15:40 How can I check to which backend / IP a domain is maped, aka how is that hash calculated? doveadm director move seems also not to do anything meaningful for %d, or at least I have not found out how to use it to move a domain to a different backend. Hoping for some insight :) Ralf -- Ralf Becker EGroupware GmbH [www.egroupware.org] Handelsregister HRB Kaiserslautern 3587 Geschäftsführer Birgit und Ralf Becker Leibnizstr. 17, 67663 Kaiserslautern, Germany Telefon +49 631 31657-0

3 5

Dovecot cannot access mailcrypt decryption key
by Daniel Niewerth 30 Nov '20

30 Nov '20

2 1

A probably dumb question, but I'm stumped
by Christy S 30 Nov '20

30 Nov '20

Hi folks, I'm stumped on an error we're getting in dovecot after upgrading ubuntu. I will say up front that I'm far from a linux expert. I'm helping my husband by managing a virtual private server to handle his domain, including its email. We set this up two years ago and once I finally got the mail working, it's been humming along just fine since, until two days ago when I performed the ubuntu upgrade. Now, when we try to send mail through his domain thunderbird gives this error: Your message was sent but a copy was not placed in your sent folder (Sent) due to network or file access errors. Note that it says this, but the mail isn't actually sent at all. We are using SSL and have been since the beginning which might be part of our problem, but I'm not positive. A google search suggested adding two lines to the 10-ssl.conf file. ssl_dh = </usr/share/dovecot/dh.pem ssl_cipher_list = HIGH:!DH:!aNULL I did both of these things and restarted the server completely, but no luck. looking in /var/log/mail.err I see this. Nov 29 14:08:56 kylesmith-music dovecot: imap-login: Error: Failed to initialize SSL server context: Can't load SSL cert ificate: error:140AB18F:SSL routines:SSL_CTX_use_certificate:ee key too small: user=<>, rip=xxx.xxx.xxx.xxx, lip=xxx.xxx.xxx.xxx, session=<t4qrdkS1kPNLFhL4> What's interesting is that last line only showed up after I added the two lines to the config file. My guess is I need to do something with SSL, update it maybe? But I don't want to go fiddling around purely on a guess and potentially break things even more. So, any of you much more linux familiar types want to point me in the right direction? Thanks! Christy

4 3

Repo for ubuntu focal 20.04 LTS
by Sébastien Riccio 27 Nov '20

27 Nov '20

Hello Dovecot, As the new ubuntu LTS 20.04 seems to be out, I would like to ask if there are any plans to add a repo like it already exists for 18.04 LTS. We planned to upgrade our 18.04 LTS boxes to 20.04. It has it’s own dovecot packages (2.3.7 at the time of writing this), but I would prefer we use your repositories like we do with 18.04. Kind regards, Sébastien

4 4

Panic: file message-parser.c
by Urban Loesch 27 Nov '20

27 Nov '20

Hi, I'm running Dovecot 2.3.11 from Dovet Repository on Debian 9.13. I get the following error when some of our users are doing searches in mailboxes. My error log: ... Nov 25 17:32:13 dcot-mydomain-1 dovecot: imap-login: ID sent: x-session-id=Dh04+PC0+O9t+MsP, x-originating-ip=109.248.203.15, x-originating-port=61432, x-connected-ip=10.10.10.10206, x-connected-port=993, x-proxy-ttl=4: user=<>, rip=109.248.203.15, lip=10.10.10.10206, secured, session=<Dh04+PC0+O9t+MsP> Nov 25 17:32:13 dcot-mydomain-1 dovecot: imap-login: Login: user=<user(a)domain.com>, method=PLAIN, rip=109.248.203.15, lip=10.10.10.10206, mpid=110860, secured, session=<Dh04+PC0+O9t+MsP> Nov 25 17:32:18 dcot-mydomain-1 dovecot: imap(user(a)domain.com pid:110860 session:<Dh04+PC0+O9t+MsP>): Panic: file message-parser.c: line 174 (message_part_finish): assertion failed: (ctx->nested_parts_count > 0) Nov 25 17:32:18 dcot-mydomain-1 dovecot: imap(user(a)domain.com pid:110860 session:<Dh04+PC0+O9t+MsP>): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(backtrace_append+0x42) [0x7fd61a26c0e2] -> /usr/lib/dovecot/libdovecot.so.0(backtrace_get+0x1e) [0x7fd61a26c1ee] -> /usr/lib/dovecot/libdovecot.so.0(+0xe9c81) [0x7fd61a276c81] -> /usr/lib/dovecot/libdovecot.so.0(+0xe9d21) [0x7fd61a276d21] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7fd61a1cbfa4] -> /usr/lib/dovecot/libdovecot.so.0(+0xc990e) [0x7fd61a25690e] -> /usr/lib/dovecot/libdovecot.so.0(message_parser_parse_next_block+0xdc) [0x7fd61a257f8c] -> /usr/lib/dovecot/libdovecot.so.0(message_search_msg+0xa0) [0x7fd61a25a810] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xc4c5f) [0x7fd61a5fbc5f] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_search_args_foreach+0x45) [0x7fd61a577575] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xc5a5e) [0x7fd61a5fca5e] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xc6f63) [0x7fd61a5fdf63] -> /usr/lib/dovecot/libdovecot-storage.so.0(index_storage_search_next_nonblock+0x10c) [0x7fd61a5fe68c] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_search_next_nonblock+0x22) [0x7fd61a580fb2] -> dovecot/imap(+0x257f0) [0x55be0929f7f0] -> dovecot/imap(command_exec+0x64) [0x55be09297ff4] -> dovecot/imap(+0x24a32) [0x55be0929ea32] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handle_timeouts+0x137) [0x7fd61a28f707] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0xc1) [0x7fd61a291211] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x59) [0x7fd61a28fa69] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7fd61a28fc98] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7fd61a1fd2f3] -> dovecot/imap(main+0x338) [0x55be09287f68] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1) [0x7fd619e0e2e1] -> dovecot/imap(_start+0x2a) [0x55be0928816a] Nov 25 17:32:18 dcot-mydomain-1 dovecot: imap(user(a)domain.com pid:110860 session:<Dh04+PC0+O9t+MsP>): Fatal: master: service(imap): child 110860 killed with signal 6 (core dumps disabled - https://dovecot.org/bugreport.html#coredumps) ... I searched the archives and found this patch which seems to fix it: https://github.com/dovecot/core/commit/a668d767a710ca18ab6e7177d8e8be22a6b0… Have you planned to release new Debian 9 packages in dovecot repository where this patch will be applied? My current Dovecot version is: ii dovecot-core 2:2.3.11.3-3+debian9 amd64 secure POP3/IMAP server - core files ii dovecot-dbg 2:2.3.11.3-3+debian9 amd64 secure POP3/IMAP server - debug symbols ii dovecot-imapd 2:2.3.11.3-3+debian9 amd64 secure POP3/IMAP server - IMAP daemon ii dovecot-lmtpd 2:2.3.11.3-3+debian9 amd64 secure POP3/IMAP server - LMTP server ii dovecot-managesieved 2:2.3.11.3-3+debian9 amd64 secure POP3/IMAP server - ManageSieve server ii dovecot-mysql 2:2.3.11.3-3+debian9 amd64 secure POP3/IMAP server - MySQL support ii dovecot-pop3d 2:2.3.11.3-3+debian9 amd64 secure POP3/IMAP server - POP3 daemon ii dovecot-sieve 2:2.3.11.3-3+debian9 amd64 secure POP3/IMAP server - Sieve filters support ... Many thanks Urban

2 1

Dovecot alternatives with good i18n support?
by David Bürgin 26 Nov '20

26 Nov '20

Hello! I’m interested in exploring alternative IMAP servers that have good support for internationalised email, such as support for SMTPUTF8, IDN mail domains, Unicode local-part, etc. etc. If you used to use Dovecot, and found an alternative that does such things well, I would very much like to hear it. Thank you, -- David

2 2

Dovecot+Samba AD - authentication failure
by Odhiambo Washington 26 Nov '20

26 Nov '20

Hi, I have setup samba4 as AD and hoping to have dovecot authenticate users against it. I am facing challenges though and I am unable to figure it out. I could do with a third eye to help me spot what is wrong. root@adc0:/etc# doveadm auth test -x service=imap odhiambo(a)newideatest.local Password: passdb: odhiambo(a)newideatest.local auth failed extra fields: temp Warning: auth-client: conn unix:/var/run/dovecot/auth-client: Auth connection closed with 1 pending requests (max 0 secs, pid=10537, EOF) Fatal: Couldn't connect to auth socket A test against IMAP gives the following debug information: Nov 22 14:31:01 auth: Debug: Loading modules from directory: /usr/lib/dovecot/modules/auth Nov 22 14:31:01 auth: Debug: Module loaded: /usr/lib/dovecot/modules/auth/lib20_auth_var_expand_crypt.so Nov 22 14:31:01 auth: Debug: Module loaded: /usr/lib/dovecot/modules/auth/libdriver_mysql.so Nov 22 14:31:01 auth: Debug: Loading modules from directory: /usr/lib/dovecot/modules/auth Nov 22 14:31:01 auth: Debug: Module loaded: /usr/lib/dovecot/modules/auth/libauthdb_ldap.so Nov 22 14:31:01 auth: Debug: Read auth token secret from /var/run/dovecot/auth-token-secret.dat Nov 22 14:31:01 auth: Debug: auth client connected (pid=10979) Nov 22 14:31:08 auth: Debug: client in: AUTH 1 PLAIN service=imap secured session=uPLvabC0RIh/AAAB lip=127.0.0.1 rip=127.0.0.1 lport=143 rport=34884 resp=<hidden> Nov 22 14:31:08 auth: Debug: ldap(odhiambo(a)newideatest.local,127.0.0.1,<uPLvabC0RIh/AAAB>): Performing passdb lookup Nov 22 14:31:08 auth: Debug: ldap(odhiambo(a)newideatest.local,127.0.0.1,<uPLvabC0RIh/AAAB>): bind search: base=cn=Users,dc=NEWIDEATEST,dc=LOCAL filter=(&(objectClass=user)(!(userAccountControl:1.2.840.113556.1.4.803:=2))(sAMAccountName=odhiambo@newideatest.local )) Nov 22 14:31:08 auth: Debug: ldap(odhiambo(a)newideatest.local,127.0.0.1,<uPLvabC0RIh/AAAB>): no fields returned by the server *< ====================* Nov 22 14:31:08 auth: Debug: ldap(odhiambo(a)newideatest.local,127.0.0.1,<uPLvabC0RIh/AAAB>): Finished passdb lookup Nov 22 14:31:08 auth: Debug: auth(odhiambo(a)newideatest.local,127.0.0.1,<uPLvabC0RIh/AAAB>): Auth request finished Nov 22 14:31:10 auth: Debug: client passdb out: FAIL 1 user=odhiambo(a)newideatest.local info.log: Nov 22 14:31:08 auth: Info: ldap(odhiambo(a)newideatest.local ,127.0.0.1,<uPLvabC0RIh/AAAB>):* unknown user* (given password: XXXXXXX) Nov 22 14:31:15 imap-login: Info: Aborted login (auth failed, 1 attempts in 7 secs): user=<odhiambo(a)newideatest.local>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured, session=<uPLvabC0RIh/AAAB> Here is my doveconf -n: https://paste.ubuntu.com/p/SPmrxZxHPx/ My dovecot-ldap.cont.ext: uris = ldap://localhost/ dn = "dovecot(a)newideatest.local" dnpass = "XXXXXXXX" sasl_bind = no tls = no ldap_version = 3 deref = never scope = subtree base = cn=Users,dc=NEWIDEATEST,dc=LOCAL auth_bind = yes user_filter = (&(objectClass=user)(!(userAccountControl:1.2.840.113556.1.4.803:=2))(|(mail=%u)(sAMAccountName=%u)(otherMailbox=%u))) user_attrs = sAMAccountName=user,userPassword=password,=mail=maildir:/home/%n/Maildir/ pass_filter = (&(objectClass=user)(!(userAccountControl:1.2.840.113556.1.4.803:=2))(sAMAccountName=%u)) pass_attrs = sAMAccountName=user,userPassword=password The use exists in the database: *root@adc0:/var/log/dovecot# samba-tool user show odhiambo* ldb_wrap open of secrets.ldb dn: CN=Odhiambo Washington,CN=Users,DC=newideatest,DC=local objectClass: top objectClass: person objectClass: organizationalPerson objectClass: user cn: Odhiambo Washington sn: Washington givenName: Odhiambo instanceType: 4 whenCreated: 20201120101420.0Z displayName: Odhiambo Washington uSNCreated: 4086 name: Odhiambo Washington objectGUID: e6969596-8b28-41af-b5d8-cea63cc97f98 badPwdCount: 0 codePage: 0 countryCode: 0 badPasswordTime: 0 lastLogoff: 0 lastLogon: 0 primaryGroupID: 513 objectSid: S-1-5-21-701866827-3355127779-3787685610-1106 accountExpires: 9223372036854775807 logonCount: 0 sAMAccountName: odhiambo sAMAccountType: 805306368 userPrincipalName: odhiambo(a)newideatest.local objectCategory: CN=Person,CN=Schema,CN=Configuration,DC=newideatest,DC=local mail: odhiambo(a)newideatest.local loginShell: /bin/bash userAccountControl: 512 pwdLastSet: 132505181852397220 whenChanged: 20201122112945.0Z uSNChanged: 4104 distinguishedName: CN=Odhiambo Washington,CN=Users,DC=newideatest,DC=local -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)

2 3

Panic: file istream-seekable.c: line 226
by Eric Mauger 26 Nov '20

26 Nov '20

Hi, I have a lot of Panic in my logs. They happen almost every day and never on the same user. When it happens, the mail is not distributed (it's always lda). I discovered it because my Sympa server had a lot of users in error. The last error (below) was a local user sending a mail to 10 users : 3 of them never get the email. I've looked into my logs and discovered it started after the upgrade from 2.2.27 to 2.3.4 in february. I'm on Debian. This week, I installed the dovecot repo and upgraded to the very last and same thing. The error below happened after the latest upgrade. An example : Nov 25 11:33:07 mx.igf.cnrs.fr dovecot: lda(username_hidden)<4653><A3S4MuIyvl8tEgAAmSH/vg>: Panic: file istream-seekable.c: line 230 (read_from_buffer): assertion failed: (*ret_r > 0) Nov 25 11:33:07 mx.igf.cnrs.fr dovecot: lda(sebastien.granier)<4653><A3S4MuIyvl8tEgAAmSH/vg>: Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(backtrace_append+0x3d) [0x7f49a56d4eed] -> /usr/lib/dovecot/libdovecot.so.0(backtrace_get+0x1e) [0x7f49a56d500e] -> /usr/lib/dovecot/libdovecot.so.0(+0xf465b) [0x7f49a56de65b] -> /usr/lib/dovecot/libdovecot.so.0(+0xf46c1) [0x7f49a56de6c1] -> /usr/lib/dovecot/libdovecot.so.0(+0x514a6) [0x7f49a563b4a6] -> /usr/lib/dovecot/libdovecot.so.0(+0x53cfb) [0x7f49a563dcfb] -> /usr/lib/dovecot/libdovecot.so.0(+0x1074a1) [0x7f49a56f14a1] -> /usr/lib/dovecot/libdovecot.so.0(+0x1078f6) [0x7f49a56f18f6] -> /usr/lib/dovecot/libdovecot.so.0(i_stream_stat+0x34) [0x7f49a56eaab4] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xb1396) [0x7f49a5852396] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xb1472) [0x7f49a5852472] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_get_physical_size+0x38) [0x7f49a57ef0c8] -> /usr/lib/dovecot/libdovecot-lda.so.0(+0x4005) [0x7f49a5907005] -> /usr/lib/dovecot/libdovecot-lda.so.0(mail_deliver_init+0x141) [0x7f49a5908101] -> /usr/lib/dovecot/deliver(main+0x879) [0x562d1c0e6f99] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xeb) [0x7f49a543e09b] -> /usr/lib/dovecot/deliver(_start+0x2a) [0x562d1c0e76ea] My configuration : dovecot -n # 2.3.11.3 (502c39af9): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.11 (6c69c917) # OS: Linux 4.19.0-9-amd64 x86_64 Debian 10.6 # Hostname: mx.igf.cnrs.fr auth_username_format = disable_plaintext_auth = no lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes mail_location = maildir:~/maildir mail_plugins = fts mail_privileged_group = mail managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date index ihave duplicate mime foreverypart extracttext namespace inbox { inbox = yes location = mailbox Ads { auto = subscribe } 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 } passdb { driver = pam } plugin { sieve = file:~/sieve;active=~/.dovecot.sieve sieve_after = /etc/dovecot/sieve.d } protocols = " imap sieve pop3 sieve" service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } } service imap-login { process_min_avail = 16 service_count = 0 } service managesieve-login { inet_listener sieve { port = 4190 } } service stats { unix_listener stats-reader { group = dovecot mode = 0666 user = root } unix_listener stats-writer { group = dovecot mode = 0666 user = root } } ssl_cert = </etc/dovecot/ssl/certs/mx_igf_cnrs_fr_with_CA.crt ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it syslog_facility = local2 userdb { driver = passwd } verbose_proctitle = yes protocol lda { mail_plugins = fts sieve syslog_facility = local2 } Thanks, -- Eric Mauger | Administrateur système et réseau IGF UMR5203 | https://www.igf.cnrs.fr

1 0

Dovecot+Solr+Tika segmentation fault
by Manuel Josupeit-Walter 25 Nov '20

25 Nov '20

Hi all, I am running a mail server for family and friends based on Dovecot and Docker. Today I made a weird observation which I must have overlooked for a long time so far because they logs were written to the journal. However, I am usually only investigating the Docker logs. It seems that some e-mail indexing leads to segfaults and it seems to be related only with Solr and Tika. I have auto-indexing turned on so sometimes the indexer-worker crashes when moving mails from one folder to the other or searching for mails otherwise. Also, if I try to manually reindex using doveadm index, the doveadm process quits with a segfault. I am always running the most recent Dovecot version, in this case 2.3.11.3, but I am not neccessarily up-to-date with Solr or Tika. I am on Solr Version 7.4 and Tika 1.24.1. On the console I am receiving Tika errors and on the Solr Webinterface I see a couple of Ealry EOFs as well. I am not a Linux expert from a dev perspective, but it seems to me that the client (Dovecot) closes the connection prematurely. Does anyone have a hint? I am happy to provide more information if required. I need to know how to collect them, though. Best, Manuel The following can be found in the journald logs during the attempt to reindex my Sent mailbox with doveadm index: Nov 24 16:59:49 server.name tika[988]: INFO tika/ (application/pdf) Nov 24 16:59:49 server.name tika[988]: INFO tika/ (application/pdf) Nov 24 16:59:50 server.name tika[988]: INFO tika/ (application/pdf) Nov 24 16:59:50 server.name tika[988]: INFO tika/ (application/pdf) Nov 24 16:59:50 server.name tika[988]: INFO tika/ (application/pdf) Nov 24 16:59:50 server.name tika[988]: INFO tika/ (application/pdf) Nov 24 16:59:50 server.name tika[988]: INFO tika/ (application/pdf) Nov 24 16:59:50 server.name tika[988]: INFO tika/ (application/pdf) Nov 24 16:59:50 server.name tika[988]: INFO tika/ (application/pdf) Nov 24 16:59:50 server.name tika[988]: INFO tika/ (application/pdf) Nov 24 16:59:50 server.name tika[988]: WARN Using fallback font LiberationSans for Helvetica Nov 24 16:59:50 server.name tika[988]: WARN Using fallback font LiberationSans for Helvetica Nov 24 16:59:50 server.name tika[988]: WARN Using fallback font LiberationSans for Helvetica Nov 24 16:59:50 server.name tika[988]: WARN Using fallback font LiberationSans for Helvetica Nov 24 16:59:50 server.name tika[988]: WARN Using fallback font LiberationSans for Helvetica Nov 24 16:59:50 server.name tika[988]: WARN Using fallback font LiberationSans for Helvetica Nov 24 16:59:50 server.name tika[988]: WARN Using fallback font LiberationSans for Helvetica Nov 24 16:59:50 server.name tika[988]: WARN Using fallback font LiberationSans for Helvetica Nov 24 16:59:50 server.name tika[988]: WARN Using fallback font LiberationSans for Helvetica Nov 24 16:59:50 server.name tika[988]: WARN Using fallback font LiberationSans for Helvetica Nov 24 16:59:50 server.name tika[988]: WARN Using fallback font LiberationSans for Helvetica Nov 24 16:59:50 server.name tika[988]: WARN Using fallback font LiberationSans for Helvetica Nov 24 16:59:50 server.name tika[988]: WARN Using fallback font LiberationSans for Helvetica Nov 24 16:59:50 server.name tika[988]: WARN Using fallback font LiberationSans for Helvetica Nov 24 16:59:50 server.name tika[988]: WARN Using fallback font LiberationSans for Helvetica Nov 24 16:59:50 server.name tika[988]: WARN Using fallback font LiberationSans for Helvetica Nov 24 16:59:50 server.name tika[988]: WARN Using fallback font LiberationSans for Helvetica Nov 24 16:59:50 server.name tika[988]: WARN Using fallback font LiberationSans for Helvetica Nov 24 16:59:50 server.name tika[988]: WARN Using fallback font LiberationSans for Helvetica Nov 24 16:59:50 server.name tika[988]: WARN Using fallback font LiberationSans for Helvetica Nov 24 16:59:50 server.name tika[988]: WARN Using fallback font LiberationSans for Helvetica Nov 24 16:59:50 server.name tika[988]: WARN Using fallback font LiberationSans for Helvetica Nov 24 16:59:50 server.name tika[988]: WARN Using fallback font LiberationSans for Helvetica Nov 24 16:59:50 server.name tika[988]: WARN Using fallback font LiberationSans for Helvetica Nov 24 16:59:50 server.name kernel: doveadm[400]: segfault at 0 ip 00007fb9f4fa2b64 sp 00007ffc927694f0 error 4 in libdovecot.so.0.0.0[7fb9f4f58000+db000] Nov 24 16:59:50 server.name kernel: Code: 89 f5 48 8d b8 f0 01 00 00 48 8b 52 08 4c 8b 62 48 e8 90 89 fb ff 48 8b 44 24 08 be 00 20 00 00 4c 89 ef 48 8b 80 10 01 00 00 <4c> 8b 38 e8 64 b2 fb ff 48 8b 44 24 08 4c 89 ef 48 8b b0 10 01 00 Nov 24 16:59:50 server.name tika[988]: INFO tika/ (application/pdf) Nov 24 16:59:50 server.name tika[988]: WARN tika/: Text extraction failed (null) Nov 24 16:59:50 server.name tika[988]: org.apache.tika.exception.TikaException: TIKA-198: Illegal IOException from org.apache.tika.parser.DefaultParser@4dcc5b82 Nov 24 16:59:50 server.name tika[988]: at org.apache.tika.parser.CompositeParser.parse(CompositeParser.java:286) Nov 24 16:59:50 server.name tika[988]: at org.apache.tika.parser.AutoDetectParser.parse(AutoDetectParser.java:143) Nov 24 16:59:50 server.name tika[988]: at org.apache.tika.server.resource.TikaResource.parse(TikaResource.java:409) Nov 24 16:59:50 server.name tika[988]: at org.apache.tika.server.resource.TikaResource$4.write(TikaResource.java:521) Nov 24 16:59:50 server.name tika[988]: at org.apache.cxf.jaxrs.provider.BinaryDataProvider.writeTo(BinaryDataProvider.java:177) Nov 24 16:59:50 server.name tika[988]: at org.apache.cxf.jaxrs.utils.JAXRSUtils.writeMessageBody(JAXRSUtils.java:1472) Nov 24 16:59:50 server.name tika[988]: at org.apache.cxf.jaxrs.interceptor.JAXRSOutInterceptor.serializeMessage(JAXRSOutInterceptor.java:249) Nov 24 16:59:50 server.name tika[988]: at org.apache.cxf.jaxrs.interceptor.JAXRSOutInterceptor.processResponse(JAXRSOutInterceptor.java:122) Nov 24 16:59:50 server.name tika[988]: at org.apache.cxf.jaxrs.interceptor.JAXRSOutInterceptor.handleMessage(JAXRSOutInterceptor.java:84) Nov 24 16:59:50 server.name tika[988]: at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308) Nov 24 16:59:50 server.name tika[988]: at org.apache.cxf.interceptor.OutgoingChainInterceptor.handleMessage(OutgoingChainInterceptor.java:90) Nov 24 16:59:50 server.name tika[988]: at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308) Nov 24 16:59:50 server.name tika[988]: at org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121) Nov 24 16:59:50 server.name tika[988]: at org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:267) Nov 24 16:59:50 server.name tika[988]: at org.apache.cxf.transport.http_jetty.JettyHTTPDestination.doService(JettyHTTPDestination.java:247) Nov 24 16:59:50 server.name tika[988]: at org.apache.cxf.transport.http_jetty.JettyHTTPHandler.handle(JettyHTTPHandler.java:79) Nov 24 16:59:50 server.name tika[988]: at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:127) Nov 24 16:59:50 server.name tika[988]: at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:235) Nov 24 16:59:50 server.name tika[988]: at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1300) Nov 24 16:59:50 server.name tika[988]: at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:190) Nov 24 16:59:50 server.name tika[988]: at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1215) Nov 24 16:59:50 server.name tika[988]: at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141) Nov 24 16:59:50 server.name tika[988]: at org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:221) Nov 24 16:59:50 server.name tika[988]: at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:127) Nov 24 16:59:50 server.name tika[988]: at org.eclipse.jetty.server.Server.handle(Server.java:500) Nov 24 16:59:50 server.name tika[988]: at org.eclipse.jetty.server.HttpChannel.lambda$handle$1(HttpChannel.java:383) Nov 24 16:59:50 server.name tika[988]: at org.eclipse.jetty.server.HttpChannel.dispatch(HttpChannel.java:547) Nov 24 16:59:50 server.name tika[988]: at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:375) Nov 24 16:59:50 server.name tika[988]: at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:273) Nov 24 16:59:50 server.name tika[988]: at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:311) Nov 24 16:59:50 server.name tika[988]: at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:103) Nov 24 16:59:50 server.name tika[988]: at org.eclipse.jetty.io.ChannelEndPoint$2.run(ChannelEndPoint.java:117) Nov 24 16:59:50 server.name tika[988]: at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.runTask(EatWhatYouKill.java:336) Nov 24 16:59:50 server.name tika[988]: at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.doProduce(EatWhatYouKill.java:313) Nov 24 16:59:50 server.name tika[988]: at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.tryProduce(EatWhatYouKill.java:171) Nov 24 16:59:50 server.name tika[988]: at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.run(EatWhatYouKill.java:129) Nov 24 16:59:50 server.name tika[988]: at org.eclipse.jetty.util.thread.ReservedThreadExecutor$ReservedThread.run(ReservedThreadExecutor.java:375) Nov 24 16:59:50 server.name tika[988]: at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:806) Nov 24 16:59:50 server.name tika[988]: at org.eclipse.jetty.util.thread.QueuedThreadPool$Runner.run(QueuedThreadPool.java:938) Nov 24 16:59:50 server.name tika[988]: at java.lang.Thread.run(Thread.java:748) Nov 24 16:59:50 server.name tika[988]: Caused by: org.eclipse.jetty.io.EofException: Early EOF Nov 24 16:59:50 server.name tika[988]: at org.eclipse.jetty.server.HttpInput$3.getError(HttpInput.java:1141) Nov 24 16:59:50 server.name tika[988]: at org.eclipse.jetty.server.HttpInput$3.noContent(HttpInput.java:1129) Nov 24 16:59:50 server.name tika[988]: at org.eclipse.jetty.server.HttpInput.read(HttpInput.java:321) Nov 24 16:59:50 server.name tika[988]: at java.io.FilterInputStream.read(FilterInputStream.java:133) Nov 24 16:59:50 server.name tika[988]: at java.io.BufferedInputStream.fill(BufferedInputStream.java:246) Nov 24 16:59:50 server.name tika[988]: at java.io.BufferedInputStream.read1(BufferedInputStream.java:286) Nov 24 16:59:50 server.name tika[988]: at java.io.BufferedInputStream.read(BufferedInputStream.java:345) Nov 24 16:59:50 server.name tika[988]: at java.io.FilterInputStream.read(FilterInputStream.java:107) Nov 24 16:59:50 server.name tika[988]: at org.apache.tika.io.ProxyInputStream.read(ProxyInputStream.java:78) Nov 24 16:59:50 server.name tika[988]: at org.apache.commons.io.input.ProxyInputStream.read(ProxyInputStream.java:78) Nov 24 16:59:50 server.name tika[988]: at org.apache.pdfbox.io.ScratchFile.createBuffer(ScratchFile.java:443) Nov 24 16:59:50 server.name tika[988]: at org.apache.pdfbox.pdmodel.PDDocument.load(PDDocument.java:1220) Nov 24 16:59:50 server.name tika[988]: at org.apache.pdfbox.pdmodel.PDDocument.load(PDDocument.java:1196) Nov 24 16:59:50 server.name tika[988]: at org.apache.tika.parser.pdf.PDFParser.getPDDocument(PDFParser.java:190) Nov 24 16:59:50 server.name tika[988]: at org.apache.tika.parser.pdf.PDFParser.parse(PDFParser.java:149) Nov 24 16:59:50 server.name tika[988]: at org.apache.tika.parser.CompositeParser.parse(CompositeParser.java:280) Nov 24 16:59:50 server.name tika[988]: at org.apache.tika.parser.CompositeParser.parse(CompositeParser.java:280) Nov 24 16:59:50 server.name tika[988]: ... 39 more Nov 24 16:59:50 server.name tika[988]: ERROR Problem with writing the data, class org.apache.tika.server.resource.TikaResource$4, ContentType: text/plain

1 0

Dovecot authentication hangs when ldap_start_tls_s() fails for invalid certificate
by sebastiano degan 19 Nov '20

19 Nov '20

On a Debian10 I've installed postfix 3.4.14 and dovecot 2.3.4.1. I've configured multiple passdb sources and I expect that if one fails the other ones are tested. This is usually the case, except when the failure is due to an invalid certificate from the ldap server. In that case all authentication attempts from that moment on will fail. I've trimmed down the configuration as much as possible (see below), and this is the syslog output of my tests: TEST 1 - Everything is configured correctly: No output on syslog TEST 2 - Wrong hostname as a ldap server: Auth attempt 1: Nov 19 11:25:29 debian dovecot: auth: Error: LDAP /etc/dovecot/dovecot-ldap-passdb.conf.ext: ldap_start_tls_s() failed: Can't contact LDAP server Nov 19 11:25:29 debian dovecot: auth: Error: LDAP /etc/dovecot/dovecot-ldap-userdb.conf.ext: ldap_start_tls_s() failed: Can't contact LDAP server Nov 19 11:25:29 debian dovecot: auth: Error: LDAP /etc/dovecot/dovecot-ldap-passdb.conf.ext: ldap_start_tls_s() failed: Can't contact LDAP server Nov 19 11:25:35 debian dovecot: auth: Error: LDAP /etc/dovecot/dovecot-ldap-passdb.conf.ext: ldap_start_tls_s() failed: Can't contact LDAP server Auth attempt 2: Nov 19 11:25:57 debian dovecot: auth: Error: LDAP /etc/dovecot/dovecot-ldap-passdb.conf.ext: ldap_start_tls_s() failed: Can't contact LDAP server Nov 19 11:25:59 debian dovecot: auth: Error: LDAP /etc/dovecot/dovecot-ldap-passdb.conf.ext: ldap_start_tls_s() failed: Can't contact LDAP server Auth attempt 3: Nov 19 11:26:28 debian dovecot: auth: Error: LDAP /etc/dovecot/dovecot-ldap-passdb.conf.ext: ldap_start_tls_s() failed: Can't contact LDAP server Nov 19 11:26:30 debian dovecot: auth: Error: LDAP /etc/dovecot/dovecot-ldap-passdb.conf.ext: ldap_start_tls_s() failed: Can't contact LDAP server TEST 3 - Invalid certificate: Attempt 1: Nov 19 11:21:20 debian dovecot: auth: Error: LDAP /etc/dovecot/dovecot-ldap-passdb.conf.ext: ldap_start_tls_s() failed: Connect error Nov 19 11:21:20 debian dovecot: auth: Error: LDAP /etc/dovecot/dovecot-ldap-userdb.conf.ext: ldap_start_tls_s() failed: Connect error No output on other attempts... CONFIGURATION FILES: ______________________________________________________ auth.conf: auth_mechanisms = plain login passdb { driver = ldap args = /etc/dovecot/dovecot-ldap-passdb.conf.ext } userdb { driver = ldap args = /etc/dovecot/dovecot-ldap-userdb.conf.ext default_fields = uid=vmail gid=vmail home=/var/mail/vmail/%d/%n } ______________________________________________________ ______________________________________________________ dovecot-ldap-passdb.conf.ext: tls = yes hosts = DC1.fv.lan base = ou=Frigoveneta,dc=fv,dc=lan auth_bind = yes auth_bind_userdn = %u ______________________________________________________ ______________________________________________________ dovecot-ldap-userdb.conf.ext: tls = yes hosts = DC1.fv.lan base = ou=Frigoveneta,dc=fv,dc=lan dn = ##removed## dnpass = ##removed## user_filter = (&(userPrincipalName=%u)) ______________________________________________________

1 0

RE: about imap-login: Error and imap: Error after Version-UP
by 'Aki Tuomi' 18 Nov '20

18 Nov '20

Hi.. there is supposed to be only at most one (1) stats process. Having multiple stats processes breaks stats. Aki > On 18/11/2020 01:48 森川　孝司 <morikawa-k6(a)itec.hankyu-hanshin.co.jp> wrote: > > > Aki-san > > Last night We adjusted the "process_limit" in the stats service to get rid of the error. > > "client_limit" is in the blank (default) state. > > Thank you very much. > > morikawa > -----Original Message----- > From: 'Aki Tuomi' [mailto:aki.tuomi@open-xchange.com] > Sent: Tuesday, November 17, 2020 2:35 PM > To: 森川　孝司 <morikawa-k6(a)itec.hankyu-hanshin.co.jp>; dovecot(a)dovecot.org > Subject: RE: about imap-login: Error and imap: Error after Version-UP > > You need to configure stats service client limit and imap service client limit. Those are different services than imap-login service. > > Aki > > > On 17/11/2020 01:28 森川　孝司 <morikawa-k6(a)itec.hankyu-hanshin.co.jp> wrote: > > > > > > Aki-san > > > > I have already seen that page. > > Is the setting method wrong? > > > > Is there any other tuning point? > > > > morikawa > > -----Original Message----- > > From: Aki Tuomi [mailto:aki.tuomi@open-xchange.com] > > Sent: Monday, November 16, 2020 8:52 PM > > To: 森川　孝司 <morikawa-k6(a)itec.hankyu-hanshin.co.jp>; dovecot(a)dovecot.org > > Subject: Re: about imap-login: Error and imap: Error after Version-UP > > > > > > > On 16/11/2020 13:44 森川　孝司 <morikawa-k6(a)itec.hankyu-hanshin.co.jp> wrote: > > > > > > > > > We have upgraded dovecot from 2.0.9 (centos6) to 2.2.36 (centos8). > > > > > > If more than 1000 users log in, the following error will occur. > > > ------------------------- > > > Nov 16 11:33:00 xxxxxxxx dovecot[1361]: imap-login: Error: master(imap): > > > net_connect_unix(imap) failed: Resource temporarily unavailable - > > > http://wiki2.dovecot.org/SocketUnavailable (client-pid=1362, > > > client-id=129834, rip=10.10.10.10, created 551 msecs ago, received > > > 0/4 > > > bytes) > > > Nov 16 11:30:26 xxxxxxxx dovecot[1361]: imap: Error: > > > net_connect_unix(/var/run/dovecot/stats-writer) failed: Resource > > > temporarily unavailable > > > ------------------------- > > > > > > I set the following because I thought it was a problem with the > > > number of connections, but I get an error. > > > > > > service imap-login { > > > service_count=0 > > > client_limit = $default_client_limit > > > process_min_avail = 4 > > > process_limit = $default_process_limit > > > vsz_limit = 1G > > > } > > > > > > limits.conf > > > ------------------------- > > > * soft nofile 4096 > > > * hard nofile 4096 > > > ------------------------- > > > > > > cat /proc/sys/net/core/somaxconn > > > ------------------------- > > > 4096 > > > ------------------------- > > > > > > Is there any other tuning point? > > > Where should I look? > > > > https://wiki.dovecot.org/SocketUnavailable > > > > Aki

1 0

RE: about imap-login: Error and imap: Error after Version-UP
by 'Aki Tuomi' 18 Nov '20

18 Nov '20

You need to configure stats service client limit and imap service client limit. Those are different services than imap-login service. Aki > On 17/11/2020 01:28 森川　孝司 <morikawa-k6(a)itec.hankyu-hanshin.co.jp> wrote: > > > Aki-san > > I have already seen that page. > Is the setting method wrong? > > Is there any other tuning point? > > morikawa > -----Original Message----- > From: Aki Tuomi [mailto:aki.tuomi@open-xchange.com] > Sent: Monday, November 16, 2020 8:52 PM > To: 森川　孝司 <morikawa-k6(a)itec.hankyu-hanshin.co.jp>; dovecot(a)dovecot.org > Subject: Re: about imap-login: Error and imap: Error after Version-UP > > > > On 16/11/2020 13:44 森川　孝司 <morikawa-k6(a)itec.hankyu-hanshin.co.jp> wrote: > > > > > > We have upgraded dovecot from 2.0.9 (centos6) to 2.2.36 (centos8). > > > > If more than 1000 users log in, the following error will occur. > > ------------------------- > > Nov 16 11:33:00 xxxxxxxx dovecot[1361]: imap-login: Error: master(imap): > > net_connect_unix(imap) failed: Resource temporarily unavailable - > > http://wiki2.dovecot.org/SocketUnavailable (client-pid=1362, > > client-id=129834, rip=10.10.10.10, created 551 msecs ago, received 0/4 > > bytes) > > Nov 16 11:30:26 xxxxxxxx dovecot[1361]: imap: Error: > > net_connect_unix(/var/run/dovecot/stats-writer) failed: Resource > > temporarily unavailable > > ------------------------- > > > > I set the following because I thought it was a problem with the number > > of connections, but I get an error. > > > > service imap-login { > > service_count=0 > > client_limit = $default_client_limit > > process_min_avail = 4 > > process_limit = $default_process_limit > > vsz_limit = 1G > > } > > > > limits.conf > > ------------------------- > > * soft nofile 4096 > > * hard nofile 4096 > > ------------------------- > > > > cat /proc/sys/net/core/somaxconn > > ------------------------- > > 4096 > > ------------------------- > > > > Is there any other tuning point? > > Where should I look? > > https://wiki.dovecot.org/SocketUnavailable > > Aki

2 1

Re: about imap-login: Error and imap: Error after Version-UP
by Aki Tuomi 17 Nov '20

17 Nov '20

> On 16/11/2020 13:44 森川　孝司 <morikawa-k6(a)itec.hankyu-hanshin.co.jp> wrote: > > > We have upgraded dovecot from 2.0.9 (centos6) to 2.2.36 (centos8). > > If more than 1000 users log in, the following error will occur. > ------------------------- > Nov 16 11:33:00 xxxxxxxx dovecot[1361]: imap-login: Error: master(imap): > net_connect_unix(imap) failed: Resource temporarily unavailable - > http://wiki2.dovecot.org/SocketUnavailable (client-pid=1362, > client-id=129834, rip=10.10.10.10, created 551 msecs ago, received 0/4 > bytes) > Nov 16 11:30:26 xxxxxxxx dovecot[1361]: imap: Error: > net_connect_unix(/var/run/dovecot/stats-writer) failed: Resource temporarily > unavailable > ------------------------- > > I set the following because I thought it was a problem with the number of > connections, but I get an error. > > service imap-login { > service_count=0 > client_limit = $default_client_limit > process_min_avail = 4 > process_limit = $default_process_limit > vsz_limit = 1G > } > > limits.conf > ------------------------- > * soft nofile 4096 > * hard nofile 4096 > ------------------------- > > cat /proc/sys/net/core/somaxconn > ------------------------- > 4096 > ------------------------- > > Is there any other tuning point? > Where should I look? https://wiki.dovecot.org/SocketUnavailable Aki

2 1

about imap-login: Error and imap: Error after Version-UP
by 森川　孝司 16 Nov '20

16 Nov '20

We have upgraded dovecot from 2.0.9 (centos6) to 2.2.36 (centos8). If more than 1000 users log in, the following error will occur. ------------------------- Nov 16 11:33:00 xxxxxxxx dovecot[1361]: imap-login: Error: master(imap): net_connect_unix(imap) failed: Resource temporarily unavailable - http://wiki2.dovecot.org/SocketUnavailable (client-pid=1362, client-id=129834, rip=10.10.10.10, created 551 msecs ago, received 0/4 bytes) Nov 16 11:30:26 xxxxxxxx dovecot[1361]: imap: Error: net_connect_unix(/var/run/dovecot/stats-writer) failed: Resource temporarily unavailable ------------------------- I set the following because I thought it was a problem with the number of connections, but I get an error. service imap-login { service_count=0 client_limit = $default_client_limit process_min_avail = 4 process_limit = $default_process_limit vsz_limit = 1G } limits.conf ------------------------- * soft nofile 4096 * hard nofile 4096 ------------------------- cat /proc/sys/net/core/somaxconn ------------------------- 4096 ------------------------- Is there any other tuning point? Where should I look?

1 0

last-login Plugin
by Andrea Gabellini 16 Nov '20

16 Nov '20

Hello, i'm using last_login plugin and store data into a MySql DB. I'm using version 2.3.10.1 and the config is at the end of the email. I would like to store also the remote IP and the session name. The config is working but other informations are written only the first time. Any update is ignored but last_login time. Debugging MySQL, I notice that dovecot is using this query: INSERT INTO last_login (last_login,userid,rip,protocol,session) VALUES (1605350938,'xxxx',x.x.x.x','imap','jLFs5A609cdSN4Wh') ON DUPLICATE KEY UPDATE last_login=1605350938 How can I modify the configuration? conf.d/95-last_login.conf: dict { lastlogin = mysql:/etc/dovecot/dovecot-last-login.conf.ext } plugin { last_login_dict = proxy::lastlogin last_login_key = last-login/%u/%r/%s/%{session} } protocol imap { mail_plugins = $mail_plugins last_login } protocol pop3 { mail_plugins = $mail_plugins last_login } dovecot-last-login.conf.ext: connect = host=/var/lib/mysql/mysql.sock dbname=dovecot user=xxx password=xxx map { pattern = shared/last-login/$userid/$rip/$service/$session table = last_login value_field = last_login value_type = uint fields { userid = $userid rip = $rip protocol = $service session = $session } } -- __________________________ UNIX is user friendly. It's just selective about who its friends are. __________________________ TIM San Marino S.p.A. Andrea Gabellini Engineering R&D TIM San Marino S.p.A. - https://www.telecomitalia.sm Via Ventotto Luglio, 212 - Piano -2 47893 - Borgo Maggiore - Republic of San Marino Tel: (+378) 0549 886237 Fax: (+378) 0549 886188 -- Informativa Privacy Questa email ha per destinatari dei contatti presenti negli archivi di TIM San Marino S.p.A.. Tutte le informazioni vengono trattate e tutelate nel rispetto della normativa vigente sulla protezione dei dati personali (Reg. EU 2016/679). Per richiedere informazioni e/o variazioni e/o la cancellazione dei vostri dati presenti nei nostri archivi potete inviare una email a privacy(a)telecomitalia.sm. Avviso di Riservatezza Il contenuto di questa e-mail e degli eventuali allegati e' strettamente confidenziale e destinato alla/e persona/e a cui e' indirizzato. Se avete ricevuto per errore questa e-mail, vi preghiamo di segnalarcelo immediatamente e di cancellarla dal vostro computer. E' fatto divieto di copiare e divulgare il contenuto di questa e-mail. Ogni utilizzo abusivo delle informazioni qui contenute da parte di persone terze o comunque non indicate nella presente e-mail potra' essere perseguito ai sensi di legge.

2 1

[patch] enhancement for tika server protected by user/password basic auth
by John Fawcett 16 Nov '20

16 Nov '20

Hi The existing code is designed for a tika server on local host, or on a remote host that is either accessable to all or for example taht is protected by ip restrictions via a proxy in front of it. I've configured a tika server behind an apache proxy which enforces basic auth, but sending basic auth credentials for a tika server is not currently supported by Dovecot. The following patch allows to have user and password specified in the fts_tika url in much the same way you can for fts_solr. fts_tika = https://user:password@tika_host/tika John --- dovecot-2.3.11.3-orig/src/plugins/fts/fts-parser-tika.c 2020-08-12 14:20:41.000000000 +0200 +++ dovecot-2.3.11.3/src/plugins/fts/fts-parser-tika.c 2020-11-15 15:18:24.351281064 +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; @@ -152,6 +152,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)

2 9

Re: no shared cipher openssl
by Aki Tuomi 16 Nov '20

16 Nov '20

> On 16/11/2020 09:54 lists(a)lazygranch.com <lists(a)lazygranch.com> wrote: > > > On Sun, 15 Nov 2020 17:31:07 -0500 > Mike Schroeder <mikeschroe(a)gmail.com> wrote: > > > CentOS 7 > > Dovecot 2.2.36 > > > > Nov 14 07:13:08 mail dovecot: pop3-login: Disconnected (no auth > > attempts in 0 secs): > > user=<>, rip=73.0.0.0, lip=192.64.118.242, TLS handshaking: > > SSL_accept() failed: > > error:1408A0C1:SSL routines:ssl3_get_client_hello:no shared cipher, > > session=<> > > > > Was working fine for over a year, until the cert expired and I > > replaced it. I've tried the good cert I have for https and I used the > > Dovecot.org script to generate a self-signed certificate. > > > > 10-ssl.conf > > ## SSL settings > > #ssl = required > > ssl = yes > > #ssl = no > > ssl_cert = </etc/pki/dovecot/certs/mydomain.com.crt > > ssl_key = </etc/pki/dovecot/private/mydomain.com.key > > #ssl_ca = > > #ssl_require_crl = yes > > #ssl_client_ca_dir = > > #ssl_client_ca_file = > > #ssl_verify_client_cert = no > > #ssl_cert_username_field = commonName > > #ssl_dh_parameters_length = 1024 > > #ssl_protocols = !SSLv3 > > > > # SSL ciphers to use > > # ols values ssl_cipher_list = ALL:!LOW:!SSLv2:!EXP:!aNULL > > ssl_cipher_list = > > ALL:!kRSA:!SRP:!kDHd:!DSS:!aNULL:!eNULL:!EXPORT:!DES:!3DES:!MD5:!PSK: > > !RC4:!ADH:!LOW@STRENGTH > > > > # Prefer the server's order of ciphers over client's. > > #ssl_prefer_server_ciphers = no > > > > # Prefer the server's order of ciphers over client's. > > #ssl_prefer_server_ciphers = no > > # SSL crypto device to use, for valid values run "openssl engine" > > #ssl_crypto_device = > > > > # SSL extra options. Currently supported options are: > > # no_compression - Disable compression. > > # no_ticket - Disable SSL session tickets. > > #ssl_options = > > > > =========================== > > # openssl x509 -dates -in mydomain.com.crt > > notBefore=Nov 11 16:31:35 2020 GMT > > notAfter=Nov 11 16:31:35 2022 GMT > > -----BEGIN CERTIFICATE----- > > : > > =========================== > > # openssl pkey -in mydomain.com.key > > -----BEGIN PRIVATE KEY----- > > : > > > > Thanks for taking a look. Any ideas on what I should do next to > > debug? > > > > Mike > > I remembered this problem was posted and still had the reply post from > Viktor. This may or may not be relevant. A search on this text will > probably drag up the whole thread. > --------------- > Specifically, an ECDSA P-256 certificate, but some systems don't (yet?) > support ECDSA. You'd need an additional RSA certificate to interoperate > with their sending MTA's limited STARTTLS cipher/protocol repertoire. > -------------- > > When this thread went around I looked at my logs and found some no > auth complaints on my dovecot log. I believe they were trying to use > the sslv3 to hack my server. Or at least see if it is hackable. Since > my email server is a personal one and the attack was from a hosting > company, I blocked server IP space. > > The weird thing I get your error now myself but not consistently. Here > is an example. > ------------------------------- > Nov 16 04:18:37 imap-login: Info: Disconnected (no auth attempts in 0 secs): user=<>, rip=myvpn, lip=myserverip, TLS handshaking: SSL_accept() failed: error:14094416:SSL routines:ssl3_read_bytes:sslv3 alert certificate unknown: SSL alert number 46, session=<rXchrDG06qvGx2p9> > Nov 16 04:18:37 imap-login: Info: Login: user=<me(a)mydomain.com>, method=PLAIN, rip=myvpn, lip=myserverip, mpid=11710, TLS, session=<DSIjrDG05KvGx2p9> > > However the problem isn't present at the moment. Dovecot supports alternative certificate if you have problems with ECDSA and need to use RSA for them. See https://doc.dovecot.org/settings/core/#ssl-alt-cert Aki

1 0

no shared cipher openssl
by Mike Schroeder 16 Nov '20

16 Nov '20

CentOS 7 Dovecot 2.2.36 Nov 14 07:13:08 mail dovecot: pop3-login: Disconnected (no auth attempts in 0 secs): user=<>, rip=73.0.0.0, lip=192.64.118.242, TLS handshaking: SSL_accept() failed: error:1408A0C1:SSL routines:ssl3_get_client_hello:no shared cipher, session=<> Was working fine for over a year, until the cert expired and I replaced it. I've tried the good cert I have for https and I used the Dovecot.org script to generate a self-signed certificate. 10-ssl.conf ## SSL settings #ssl = required ssl = yes #ssl = no ssl_cert = </etc/pki/dovecot/certs/mydomain.com.crt ssl_key = </etc/pki/dovecot/private/mydomain.com.key #ssl_ca = #ssl_require_crl = yes #ssl_client_ca_dir = #ssl_client_ca_file = #ssl_verify_client_cert = no #ssl_cert_username_field = commonName #ssl_dh_parameters_length = 1024 #ssl_protocols = !SSLv3 # SSL ciphers to use # ols values ssl_cipher_list = ALL:!LOW:!SSLv2:!EXP:!aNULL ssl_cipher_list = ALL:!kRSA:!SRP:!kDHd:!DSS:!aNULL:!eNULL:!EXPORT:!DES:!3DES:!MD5:!PSK: !RC4:!ADH:!LOW@STRENGTH # Prefer the server's order of ciphers over client's. #ssl_prefer_server_ciphers = no # Prefer the server's order of ciphers over client's. #ssl_prefer_server_ciphers = no # SSL crypto device to use, for valid values run "openssl engine" #ssl_crypto_device = # SSL extra options. Currently supported options are: # no_compression - Disable compression. # no_ticket - Disable SSL session tickets. #ssl_options = =========================== # openssl x509 -dates -in mydomain.com.crt notBefore=Nov 11 16:31:35 2020 GMT notAfter=Nov 11 16:31:35 2022 GMT -----BEGIN CERTIFICATE----- : =========================== # openssl pkey -in mydomain.com.key -----BEGIN PRIVATE KEY----- : Thanks for taking a look. Any ideas on what I should do next to debug? Mike

2 1

imap dumping core in libdovecot-storage with assert "(block_count == 0 || block_idx+1 == block_count)"
by Renaud Métrich 15 Nov '20

15 Nov '20

Hi, I would like to report an issue which is 100% reproducible with a specific mail available in the reproducer attached to Red Hat's bugzilla <https://bugzilla.redhat.com/show_bug.cgi?id=1894418> (https://bugzilla.redhat.com/attachment.cgi?id=1726535) -------- 8< ---------------- 8< ---------------- 8< ---------------- 8< -------- Return-Path: <XXXXXXXXX(a)XXXXXXX.XXX.XX> X-Original-To: XXXXXXXXX(a)XXXXXXX.XXX.XX Delivered-To: XXXXXXXXXXXXXXXX(a)XXXXXX.XX.XXX.XX Received: from XXXXXXXXXXXXXXXXX.XXXXX.XX.XX (unknown [XX.XX.XXX.XXX]) by XXXXXX.XX.XXX.XX (Postfix) with ESMTP id XXXXXXXXXXX for <XXXXXXXXX(a)XXXXXXX.XXX.XX>; Thu, 15 Oct 2020 23:11:45 +0200 (CEST) Date: Thu, 15 Oct 2020 23:11:42 +0200 Subject: zoom Message-ID: <XXXXXXXXXXXXXXXXXXXXXXXX.XXXXXXXXXXXXX(a)XXXXX.XXXXXXX.XXX> From: "XXXXXXXXX(a)XXXXXXX.XXX.XX" <XXXXXXXXX(a)XXXXXXX.XXX.XX> To: XXXXXXXXX(a)XXXXXXX.XXX.XX MIME-Version: 1.0 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: base64 -------- 8< ---------------- 8< ---------------- 8< ---------------- 8< -------- The email seems completely valid to me, but I'm no email expert. When performing a "FETCH <ID> (BINARY.SIZE[1] BINARY.PEEK[1])" operation, imap crashes with following backtrace: -------- 8< ---------------- 8< ---------------- 8< ---------------- 8< -------- (gdb) bt [...] #5 0x00007ffff7707a25 in i_panic ( format=format@entry=0x7ffff7b7b460 "file %s: line %d (%s): assertion failed: (%s)") at failures.c:523 #6 0x00007ffff7ab5de7 in blocks_count_lines (full_input=0x5555557f1230, ctx=0x7fffffffdb80) at index-mail-binary.c:357 #7 index_mail_read_binary_to_cache (_mail=0x5555557e3b48, part=0x5555557e4678, include_hdr=<optimized out>, reason=<optimized out>, binary_r=0x7fffffffdc16, converted_r=0x7fffffffdc17) at index-mail-binary.c:395 #8 0x00007ffff7b39c8b in index_mail_get_binary_size (lines_r=0x7fffffffdcc4, size_r=0x7fffffffdd20, include_hdr=false, part=0x5555557e4678, _mail=0x5555557e3b48) at index-mail-binary.c:497 #9 index_mail_get_binary_stream (_mail=0x5555557e3b48, part=0x5555557e4678, include_hdr=<optimized out>, size_r=0x7fffffffdd20, lines_r=0x7fffffffdcc4, binary_r=<optimized out>, stream_r=0x0) at index-mail-binary.c:557 #10 0x00007ffff7abd204 in mail_get_binary_size (mail=mail@entry=0x5555557e3b48, part=0x5555557e4678, include_hdr=<optimized out>, size_r=size_r@entry=0x7fffffffdd20, lines_r=lines_r@entry=0x7fffffffdcc4) at mail.c:342 #11 0x00007ffff7b7add8 in imap_msgpart_size (mail=0x5555557e3b48, msgpart=0x5555557e0748, size_r=size_r@entry=0x7fffffffdd20) at imap-msgpart.c:755 #12 0x000055555557917c in fetch_binary_size (ctx=0x5555557c97b0, mail=<optimized out>, body=0x5555557dfa20) at imap-fetch-body.c:212 #13 0x00005555555777e2 in imap_fetch_more_int (ctx=0x5555557c97b0, cancel=false) at imap-fetch.c:562 #14 0x00005555555788ed in imap_fetch_more (ctx=0x5555557c97b0, cmd=cmd@entry=0x5555557c95d8) at imap-fetch.c:617 #15 0x00005555555694b1 in cmd_fetch (cmd=0x5555557c95d8) at cmd-fetch.c:337 [...] #28 0x0000555555566405 in main (argc=<optimized out>, argv=<optimized out>) at main.c:523 -------- 8< ---------------- 8< ---------------- 8< ---------------- 8< -------- This happens on latest dovecot. Best regards, Renaud METRICH

2 3

dovecot fts-solr + solr 8.7.0 upgrade: "Indexing failed: 401 Unauthorized" + "Transaction commit failed: FTS transaction commit failed: backend deinit" ?
by PGNet Dev 14 Nov '20

14 Nov '20

I've built a new dovecot + fts-solr instance; I've now picked up & am running the recently released solr 8.7.0. In a test account, I've one message -- in the 'Drafts' folder. On exec of fts 'index' doveadm index -u testuser(a)example.com -q '*' I get a 401 unauthorized indexing failure, only for the one dir+message in 'Drafts', 2020-11-13 05:43:21 indexer-worker(testuser(a)example.com)<8MKVNHmNrl/DJgEA+IOfAw>: Info: Indexed 0 messages in Queue 2020-11-13 05:43:21 indexer-worker(testuser(a)example.com)<OHfzNHmNrl/DJgEA+IOfAw>: Info: Indexed 0 messages in testing 2020-11-13 05:43:21 indexer-worker(testuser(a)example.com)<yMxJNXmNrl/DJgEA+IOfAw>: Info: Indexed 0 messages in Junk 2020-11-13 05:43:21 indexer-worker(testuser(a)example.com)<uDCbNXmNrl/DJgEA+IOfAw>: Info: Indexed 0 messages in Trash 2020-11-13 05:43:21 indexer-worker(testuser(a)example.com)<kA/uNXmNrl/DJgEA+IOfAw>: Info: Indexed 0 messages in Sent 2020-11-13 05:43:22 indexer-worker(testuser(a)example.com)<cEw/NnmNrl/DJgEA+IOfAw>: Error: fts_solr: Indexing failed: 401 Unauthorized 2020-11-13 05:43:22 indexer-worker(testuser(a)example.com)<cEw/NnmNrl/DJgEA+IOfAw>: Error: fts_solr: Indexing failed: 401 Unauthorized 2020-11-13 05:43:22 indexer-worker(testuser(a)example.com)<cEw/NnmNrl/DJgEA+IOfAw>: Error: Mailbox Drafts: Transaction commit failed: FTS transaction commit failed: backend deinit (attempted to index 1 messages (UIDs 3..3)) 2020-11-13 05:43:22 indexer-worker(testuser(a)example.com)<2OUMCHqNrl/DJgEA+IOfAw>: Info: Indexed 0 messages in INBOX I get NO output atm in my solr logs @ this 'index'; just, atm, in the dovecot logs, above I've checked all my usual perms. Indexing _was_ working with a prior solr v8.6.3 ... Either I've misconfigured some perm, and am missing it, or new-solr-version v8.7.0 is causing me some grief. (1) Can anyone yet verify Doveoct/fts-solr working with solr 8.7.x? (2) What logging config in Dovecot gets me more/detailed output for the fts_solr fail? (3) Any obvious clues as to what, specifically, is the source of this prob?

2 9

Submission service capabilities listing
by Dan 13 Nov '20

13 Nov '20

Hello all, I'm attempting to implement a submission server with questions in regards to how Dovecot handles the backend hosts capabilities. To my understanding, Dovecot will connect to the host specified in either submission_host or submission_relay_host, and gather a list of capabilities. Once gathered, after the client sends the EHLO greeting Dovecot will respond back with capabilities that the backend host is capable of. My question is, When does this occur? Running a tcpdump with the filter set to the relay host IP, I don't see any traffic until after I send the EHLO command. Dovecot states that CHUNKING is available, but the backend host does not have that capability. Is there a way to disable CHUNKING explicitly? Thanks. submission_relay_host = x.x.x.x submission_host = x.x.x.x submission_relay_ssl = no submission_relay_ssl_verify = no protocol submission { passdb { driver = static args = host=x.x.x.x proxy=y nopassword=y port=587 } }

2 1

How do Cerbot files map to Dovecot?
by Raymond Herrera 12 Nov '20

12 Nov '20

I am postponing the Apache plugin issue (CentOS is not Certbot friendly) and requesting a standalone, generic certificate. After the command "1: Spin up a temporary webserver" I have the following 2 files in the folder /etc/letsencrypt: -rw-r--r-- 1 root root 924 Nov 12 11:14 csr/0000_csr-certbot.pem -rw------- 1 root root 1708 Nov 12 11:14 keys/0000_key-certbot.pem The "key" is probably a direct replacement for the file in the distribution. What about the "csr" file? It seems to be a request, not the certificate itself. TIA

3 2

Fwd: Trying to install certbot on CentOS
by Raymond Herrera 12 Nov '20

12 Nov '20

On 11/12/2020 10:44 AM, Raymond Herrera wrote: > Following the advice obtained here, I am trying to get a LetsEncrypt > certificate. > > These are the instructions: > > Step 1: > https://snapcraft.io/docs/installing-snapd > > Step 2: > https://certbot.eff.org/lets-encrypt/centosrhel7-apache > > My problem is this error message: > > # snap install --classic certbot > > error: system does not fully support snapd: cannot mount squashfs > image using "squashfs": mount: > /tmp/sanity-squashfs-881328484: failed to setup loop device: No > such file or directory > > Apparently, RedHat/CentOS are not supporters of snap. > > TIA > > OS: CentOS 7 > Thanks to Leonardo and Michael, I have made some progress. The snaps application is not supported by RedHat/CentOS. The solution is simple, just use: # yum install certbot The new error message is this: # certbot certonly --apache Saving debug log to /var/log/letsencrypt/letsencrypt.log Could not choose appropriate plugin: The requested apache plugin does not appear to be installed The requested apache plugin does not appear to be installed I am trying to find which is the "requested apache plugin". The log mentions "authenticator". I am hoping that an Apache Certificate will be useful for Dovecot.

2 1

Guide on Renewing SSL Certificate for Apache, Postfix and Dovecot on CentOS 6.8 Linux
by Turritopsis Dohrnii Teo En Ming 12 Nov '20

12 Nov '20

Good day from Singapore, Please check out the following link for my guide. https://marc.info/?l=postfix-users&m=160517863730596&w=2 Thank you very much. -----BEGIN EMAIL SIGNATURE----- The Gospel for all Targeted Individuals (TIs): [The New York Times] Microwave Weapons Are Prime Suspect in Ills of U.S. Embassy Workers Link: https://www.nytimes.com/2018/09/01/science/sonic-attack-cuba-microwave.html ******************************************************************************************** Singaporean Targeted Individual Mr. Turritopsis Dohrnii Teo En Ming's Academic Qualifications as at 14 Feb 2019 and refugee seeking attempts at the United Nations Refugee Agency Bangkok (21 Mar 2017), in Taiwan (5 Aug 2019) and Australia (25 Dec 2019 to 9 Jan 2020): [1] https://tdtemcerts.wordpress.com/ [2] https://tdtemcerts.blogspot.sg/ [3] https://www.scribd.com/user/270125049/Teo-En-Ming -----END EMAIL SIGNATURE-----

2 1

Trying to install certbot on CentOS
by Raymond Herrera 12 Nov '20

12 Nov '20

Following the advice obtained here, I am trying to get a LetsEncrypt certificate. These are the instructions: Step 1: https://snapcraft.io/docs/installing-snapd Step 2: https://certbot.eff.org/lets-encrypt/centosrhel7-apache My problem is this error message: # snap install --classic certbot error: system does not fully support snapd: cannot mount squashfs image using "squashfs": mount: /tmp/sanity-squashfs-881328484: failed to setup loop device: No such file or directory Apparently, RedHat/CentOS are not supporters of snap. TIA OS: CentOS 7

3 2

Testing
by Turritopsis Dohrnii Teo En Ming 12 Nov '20

12 Nov '20

Testing -----BEGIN EMAIL SIGNATURE----- The Gospel for all Targeted Individuals (TIs): [The New York Times] Microwave Weapons Are Prime Suspect in Ills of U.S. Embassy Workers Link: https://www.nytimes.com/2018/09/01/science/sonic-attack-cuba-microwave.html ******************************************************************************************** Singaporean Targeted Individual Mr. Turritopsis Dohrnii Teo En Ming's Academic Qualifications as at 14 Feb 2019 and refugee seeking attempts at the United Nations Refugee Agency Bangkok (21 Mar 2017), in Taiwan (5 Aug 2019) and Australia (25 Dec 2019 to 9 Jan 2020): [1] https://tdtemcerts.wordpress.com/ [2] https://tdtemcerts.blogspot.sg/ [3] https://www.scribd.com/user/270125049/Teo-En-Ming -----END EMAIL SIGNATURE-----

1 0

Support TLS for pure remote doveadm commands
by Vincent Brillault 11 Nov '20

11 Nov '20

Dear all, A lot of doveadm commands (e.g. backup/sync, deduplicate, mailbox) support a `-S` (a.k.a `socket-path`) argument that allows to run the command remotely. Unfortunately, I think that there is a bug in the handling of the TLS configuration for this feature. After a bit of debugging, I think it's simply due to doveadm_mail_server_user_get_host (https://github.com/dovecot/core/blob/master/src/doveadm/doveadm-mail-server…) bailing out too quickly: It's used by doveadm_mail_server_user (https://github.com/dovecot/core/blob/master/src/doveadm/doveadm-mail-server…) to set its `user`, `host`, `hostip`, `port` and `ssl_flags`. When doveadm_port is not (or set to 0): - `user` is set to `input->username`: OK - `host` is set to `ctx->set->doveadm_socket_path` (the content of the `-S` option): OK - `hostip` is not set: OK (Later on, the `host` is used in that case) - `port` is set to 0: This is OK, as when the `hostip` (or rather the `server->ip` later in the code) is not set, this is only the default, the port is extracted from the `host` (or rather `server->name`) - `ssl_flags` is not modified: this is not OK as there is nothing else modifying it! Bailing out just a few line later (as in https://patch-diff.githubusercontent.com/raw/dovecot/core/pull/145.patch) fixes the issue for me. To reproduce the issue, with dovecot-2.3.11.3-4, you will need two systems, A & B: A needs to have dovecot configured and port 9091 open in its firewall for B. B just need dovecot to be installed. - Testing without TLS: - Add the following to A's dovecot configuration (and reload it): ``` service doveadm { inet_listener { port = 9091 } } doveadm_password=VeryRandomString ``` - On B, create a file X containing (only): ``` doveadm_password=VeryRandomString ``` - On B, running `doveadm -c X mailbox list -u ${existing_user} -S ${A}:9091` should return the mailbox list - Switching to TLS: - Replace what was added to A's dovecot configuration (and reload it) with: ``` service doveadm { inet_listener { port = 9091 ssl = yes } } doveadm_password=VeryRandomString doveadm_ssl = ssl # Not strictly required ``` - On B, create a file Y containing (only): ``` doveadm_password=VeryRandomString doveadm_ssl=yes ``` - On B, running `doveadm -c Y mailbox list -u ${existing_user} -S ${A}:9091` will not work. - On A, you should see in the logs: `dovecot[16435]: doveadm(${B}): Error: SSL handshake failed: SSL_accept() failed: error:140760FC:SSL routines:SSL23_GET_CLIENT_HELLO:unknown protocol` Applying the patch mentioned above makes the 2nd case work. What do you think? Cheers, Vincent

1 0

Re: how to set smtp-client -> submission_relay_host for IPv4 only?
by PGNet Dev 11 Nov '20

11 Nov '20

ref https://dovecot.org/pipermail/dovecot/2020-October/120226.html > On 10/15/20 10:13 PM, Aki Tuomi wrote: >> I'm asking how/where to 'tell', via config, Dovecot's smtp-CLIENT, that's making >> to connection to the submission_relay_host, to use _only_ IPv4. > > > There is currently no (other) way to do this than using /etc/hosts or specifying > IPv4 address for the relay host. Is there a bug request opened for this, then ? Is it planned for implementation ?

1 0

Re: Recovering expunged but not purged e-mails from mdbox with zlib compression
by Aki Tuomi 11 Nov '20

11 Nov '20

> On 10/11/2020 20:07 Daniel Schütze <dms(a)cwa.uk.com> wrote: > > > Dear Aki > Thank you. Unfortunately I'm struggling to get the right syntax for this as it looks like someone else was here too > https://dovecot.org/pipermail/dovecot/2018-July/112441.html > The location in my dovecot.conf is > > mdbox:%%h/mdbox:INDEX=/indexdisk/indexes/%%n:INDEXPVT=~/mdbox/shared/%%n This syntax is for accessing shared folders. You probably should try doveadm -Dv -o mail_location=mdbox_deleted:/path/to/mdbox fetch -u victim text ALL > I'm trying to fetch a message (for testing purposes now) based on it's guid as that is available from doveadm dump. > So my syntax is (based on the previous person who didn't get it to work). > > doveadm -o "mail_location=mdbox_deleted:%%h/mdbox:INDEX=/indexdisk/indexes/%%n:INDEXPVT=~/mdbox/shared/%%n" fetch "body" guid (msg.guid from doveadm dump) > Doveadm does not support var expand, so this will not work. See above for syntax. > But that's getting no response. I've tried putting in the hard path in case there is any trouble with the %%h etc but that doesn't help either. > I've also tried the fetch with the subject of a known deleted message and also adding mailbox Drafts (as I know that's where it is or rather was) but to no avail. > Given doveadm dump gives msg.uid and no subject I'd prefer to use that in any case. > There are no error messages, I do with doveadm was a little more verbose to help over these bumps! > > Any chance of a helping hand? > > > > Aki > > > > Daniel Schütze > Director > > ------------------ > > CWA International Ltd > 5th Floor, 42 Trinity Square > London > EC3N 4DJ > > (t) + 44 (0)20 7242 8444 > (e) dms(a)cwa.uk.com > (w) http://www.cwa.international/ > On 10/11/20 10:53, Aki Tuomi wrote: > > > You can use mdbox_deleted driver to access mails with refcount 0. See > > https://wiki2.dovecot.org/MailboxFormat/dbox > > > > Aki > > > > On 10.11.2020 12.42, Daniel Schütze wrote: > > > > > Yesterday I had to recover an e-mail which a user had deleted. If I > > > understand this correctly the message was expunged but not purged > > > (doveadm purge had not been run). > > > > > > This e-mail was clearly still in the mdbox stored with zlib > > > compression as I could tell using the doveadm dump command (doveadm > > > dump -t dbox filename). > > > > > > I could however not reveal the e-mail with the normal doveadm fetch -u > > > username "body" guid (guid from dump output) > > > > > > In the end I was able to recover the e-mail by cutting it out from the > > > mdbox and running gunzip over it, but this method was very fiddly and > > > would not have worked for a bulk job. I appreciate I could have just > > > deleted the index files and gotten all the deleted messages back by > > > having the index rebuilt but that would have been the proverbial > > > "hammer to crack a nut". > > > > > > Fortunately this e-mail had no attachment for me to worry about, as > > > those are also detached for sis by dovecot. > > > > > > Can anyone tell me of a quick and easy way to recover one or multiple > > > e-mails marked as expunged but not purged which are stored in a mdbox > > > with zlib compression? I'm sure I'll have to do this again the future > > > and my method wouldn't work with a folder! > > > > > > Clearly if I was not using zlib compression I could just have read the > > > contents of the mdbox without any complication. > > > > > > > > > -- > > > Daniel Schütze > > > Director > > > > > > ------------------ > > > > > > CWA International Ltd > > > 5th Floor, 42 Trinity Square > > > London > > > EC3N 4DJ > > > > > > (t) + 44 (0)20 7242 8444 > > > (e) dms(a)cwa.uk.com > > > (w) http://www.cwa.international/ > > >

3 2

Recommended Protocols?
by Raymond Herrera 11 Nov '20

11 Nov '20

Hello all: For several years I have been running the following in a Linux server. Dovecot Version: 2.0.9 *IMAP:* Connection Security: SSL/TLS Port: 993 Authentication Method: Normal Password *SMTP:* Connection Security: STARTTLS Port: 587 Authentication Method: Normal Password The E-mail client is Thunderbird on Windows. I am preparing a new server, with Dovecot 2.2.36 and would like to know the currently recommended protocols. Should I stick to what I have? I would prefer to start with the easiest configuration possible, which I will revise later. This is the command that I have been using to verify the server's functionality: % openssl s_client -connect localhost:imaps TIA

8 13

SSL alert number 42
by Raymond Herrera 11 Nov '20

11 Nov '20

This is a followup to my thread "Recommended Protocols?". The error message is as follows: dovecot: imap-login: Disconnected: TLS: SSL_read() failed: SSL routines:ssl3_read_bytes:sslv3 alert bad certificate: SSL alert number 42 I have selected both SSL/TLS and STARTTLS on the Thunderbird side, with identical results. The first question that I have is this. Is there any way to know whether that error messages comes from an attempt to read: (a) The server SSL certificate? (b) The client SSL certificate? Please find attached 2 log files. I am essentially using the distribution files as they come from the box. TIA

3 6

Recovering expunged but not purged e-mails from mdbox with zlib compression
by Daniel Schütze 10 Nov '20

10 Nov '20

Yesterday I had to recover an e-mail which a user had deleted. If I understand this correctly the message was expunged but not purged (doveadm purge had not been run). This e-mail was clearly still in the mdbox stored with zlib compression as I could tell using the doveadm dump command (doveadm dump -t dbox filename). I could however not reveal the e-mail with the normal doveadm fetch -u username "body" guid (guid from dump output) In the end I was able to recover the e-mail by cutting it out from the mdbox and running gunzip over it, but this method was very fiddly and would not have worked for a bulk job. I appreciate I could have just deleted the index files and gotten all the deleted messages back by having the index rebuilt but that would have been the proverbial "hammer to crack a nut". Fortunately this e-mail had no attachment for me to worry about, as those are also detached for sis by dovecot. Can anyone tell me of a quick and easy way to recover one or multiple e-mails marked as expunged but not purged which are stored in a mdbox with zlib compression? I'm sure I'll have to do this again the future and my method wouldn't work with a folder! Clearly if I was not using zlib compression I could just have read the contents of the mdbox without any complication. -- Daniel Schütze Director ------------------ CWA International Ltd 5th Floor, 42 Trinity Square London EC3N 4DJ (t) + 44 (0)20 7242 8444 (e) dms(a)cwa.uk.com (w) http://www.cwa.international/

2 2

Sieve body test
by ＠lbutlr 10 Nov '20

10 Nov '20

I have an email where I need to edit the body. I know this is generally a bad idea, but in this case I need to do it. The email comes in automatically every week or two, and so I thought that SIEVE would be the way to go. if header :contains "from" "theaddress@tehdomain" { if body :raw :contains "A string" { # Magic happens here } } It looks like what I need to do is enable and use vnd.dovecot.filter to pipe the message to a script. (Er. | not vnd.dovecot.pipe) So, if I wanted to transform the message so that the string "foobar13" was changed to "foo-bar-13" I would add filter :try "myfoobarfix.sh" After "magic happens here"> OK so far? Now, what are the requirements on the executable script? Would it literally be as simple as an executable file that simply said sed -e '|foobar13|foo-bar-13|g' Or does it need to be a shebang script and take input on $1 and … ? And lastly, where do the executable scripts need to be? https://raw.githubusercontent.com/dovecot/pigeonhole/master/doc/rfc/spec-bo… says "the external programs cannot be chosen arbitrarily; the available programs are restricted through administrator configuration", but no details on exactly how that is configured. -- "Are you pondering what I'm pondering?" Pinky: I think so, Brain. But if I put on two tutu's, would I really be wearing a four-by-four? Brain: Why do I even bother asking? Pinky: I dunno, Brain. Maybe it's all part of some huge, cosmic plot formula!

2 7

DOP-1414 sieve vacation address matching is case sensitive
by Mathieu Gosset 09 Nov '20

09 Nov '20

Hello, One year ago a bug was reported regarding pigeonhole vacation plugin https://www.mail-archive.com/dovecot@dovecot.org/msg78588.html a mail sent to User(a)domain.com instead of user(a)domain.com will generate a " vacation action: discarding vacation response for implicitly delivered message; no known (envelope) recipient address found in message headers (recipient=<user(a)domain.com>, and no additional `:addresses' are specified)" and no auto-response will be sent the problem seems to be located in /src/lib-sieve/plugins/vacation/cmd-vacation.c and the _contains_my_address_() function the comparison is done using dovecot's lib-smtp (src/lib-smtp/smtp-address.h) smtp_address_equals() function, which returns smtp_address_cmp(.) == 0; smtp_address_cmp() does a case insensitive comparison of the domain parts (using null_strcasecmp()) and a case sensitive comparison of the local parts (using null_strcmp()) There is probably a good reason why the local parts comparison is case sensitive within smtp_address_cmp(), but having vacation rely on that function causes the problem described above. Is there any plan to fix that ? Regards

2 1

HIGHESTMODSEQ replication issue
by Gustavo Ajeitos [Office365] 09 Nov '20

09 Nov '20

Hello, I'm using dovecot 2.3.10 in OpenSUSE and I have configured a master/master replication between two backends, it works well but I have found an issue with the replication of the HIGHESTMODSEQ. When I move a set of message from a mailbox to other, e.g. move 3 messages from INBOX to Junk, the HIGHESTMODSEQ get different on each server, with no errors in the log: [Borrador] 34:34 [Sent] 63:63 [Drafts] 12:12 [Trash] 146:146 [Junk] 219:218 [INBOX] 1133:1130 It can be fixed executing a full sync: $ sudo doveadm -D -v sync -u user(a)test.priv -d -l 30 -U But it is not a solution because it happens all the time that a user move messages. I'm using ActiveSync and the ActiveSync server use the HIGHESTMODSEQ as part of the synchronization key (sync_key), so in that situation the server detect changes on the mailbox if it connects to the backend with a different HIGHESTMODSEQ that it previously cached, causing a loop beetween the ActiveSync server and the the email client, where the server constantly inform email client about nonexistent changes. Could it be a bug in Dovecot replication? How can I solve it? Best regards, Gustavo Ajeitos

4 7

Re: vsz_limit
by Aki Tuomi 06 Nov '20

06 Nov '20

Duh... src/lib/restrict-process-size.h Should be in the installed include files as well, /usr/include/dovecot/restrict-process-size.h Aki > On 06/11/2020 15:56 Joan Moreau <jom(a)grosjo.net> wrote: > > > Hello > I can't find "src/lib/restrict.h" . Is it in dovecot source ? > > > On 2020-11-06 13:20, Aki Tuomi wrote: > > Seems I had forgotten that you can use src/lib/restrict.h, in particular, restrict_get_process_size() to figure out the limit. You can combine this with getrusage to find out current usage. > > > > Aki > > > > > > > On 06/11/2020 13:26 Joan Moreau <jom(a)grosjo.net> wrote: > > > > > > > > > yes, will do so. > > > It would be nice however to be able to access the actual dovecot config from the plugin side > > > > > > > > > > > > On 2020-11-04 06:46, Aki Tuomi wrote: > > > > You could also add it as setting for the fts_xapian plugin parameters? > > > > > > > > Aki > > > > > > > > > > > > > > > > > On 04/11/2020 08:42 Joan Moreau <jom(a)grosjo.net> wrote: > > > > > > > > > > > > > > > For machines with low memory, I would like to detect how much ram remains available before starting indexing a mail, so I can commit everything on disk before the ram is exhausted (and break the process) > > > > > I tried to put a "fake" allocation to test if it fails, (so it can fail separately, and I can "if ram remaining is above X") but the is really not clean > > > > > > > > > > > > > > > > > > > > On 2020-11-04 06:28, Aki Tuomi wrote: > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On 04/11/2020 05:19 Joan Moreau <jom(a)grosjo.net> wrote: > > > > > > > > > > > > > > > > > > > > > Hello > > > > > > > I am looking for help around memory management > > > > > > > 1 - How to get the current value of "vsz_limit" from inside a plugin (namely https://github.com/grosjo/fts-xapian/ ) , especially for indexer-worker > > > > > > > 2 - Is there a macro or function in dovecot to get the remaining free memory from this vsz value ? > > > > > > > Thank you > > > > > > > > > > > > > > > > > > > > > > > > > > Hi Joan, > > > > > > > > > > > > I don't think there is a feasible way to access this setting as of now. Is there a reason you need this? We usually recommend setting vsz_limit=0 for indexer-worker. > > > > > > > > > > > > Aki > > > > > >

2 2

Re: vsz_limit
by Aki Tuomi 06 Nov '20

06 Nov '20

You could also add it as setting for the fts_xapian plugin parameters? Aki > On 04/11/2020 08:42 Joan Moreau <jom(a)grosjo.net> wrote: > > > For machines with low memory, I would like to detect how much ram remains available before starting indexing a mail, so I can commit everything on disk before the ram is exhausted (and break the process) > I tried to put a "fake" allocation to test if it fails, (so it can fail separately, and I can "if ram remaining is above X") but the is really not clean > > > > On 2020-11-04 06:28, Aki Tuomi wrote: > > > > > > > On 04/11/2020 05:19 Joan Moreau <jom(a)grosjo.net> wrote: > > > > > > > > > Hello > > > I am looking for help around memory management > > > 1 - How to get the current value of "vsz_limit" from inside a plugin (namely https://github.com/grosjo/fts-xapian/ ) , especially for indexer-worker > > > 2 - Is there a macro or function in dovecot to get the remaining free memory from this vsz value ? > > > Thank you > > > > > > > > > > Hi Joan, > > > > I don't think there is a feasible way to access this setting as of now. Is there a reason you need this? We usually recommend setting vsz_limit=0 for indexer-worker. > > > > Aki > >

2 3

doveadm sync usage ; root INBOX unsynced
by François Poulain 06 Nov '20

06 Nov '20

Hi, I am trying to import a mail IMAP account using doveadm. Following https://serverfault.com/questions/605342/migrating-from-any-imap-pop3-serve… I did it with: doveadm -D -v \ -o imapc_host=mail.oldserver.tld \ -o imapc_user=contact(a)domain.org \ -o imapc_password=xxxxxxx \ -o imapc_features=rfc822.size \ -o imapc_ssl=starttls \ -o ssl_client_ca_file=/etc/ssl/certs/ca-certificates.crt \ -o mail_fsync=never \ sync -1 -R -u contact(a)domain.org imapc: Btw I am facing with exactly the same error than: https://serverfault.com/questions/960264/doveadm-backup-doesnt-transfer-mai… I.e. it works fine for all subfolders, but the root INBOX stay empty on the new server. Those debug messages tell me something seems wrong with INBOX root but I am unable to understand them: dsync(contact(a)domain.tld): Debug: brain M: Local mailbox tree: INBOX guid=deadbeefdeabbeefdeadbeefdeabbeef uid_validity=1604137198 uid_next=1 subs=no last_change=0 last_subs=0 dsync(contact(a)domain.tld): Debug: brain S: Remote mailbox tree: INBOX guid=deadbeefdeabbeefdeadbeefdeabbeef uid_validity=1604137198 uid_next=1 subs=no last_change=0 last_subs=0 dsync(contact(a)domain.tld): Debug: brain M: Mailbox INBOX: local=deadbeefdeabbeefdeadbeefdeabbeef/0/1, remote=00000000000000000000000000000000/0/0: mailbox not selectable yet dsync(contact(a)domain.tld): Debug: brain S: Mailbox INBOX: local=00000000000000000000000000000000/0/0, remote=deadbeefdeabbeefdeadbeefdeabbeef/0/1: mailbox not selectable yet dsync(contact(a)domain.tld): Debug: brain S: Ignore nonexistent mailbox GUID deadbeefdeabbeefdeadbeefdeabbeef with -1 sync dsync(contact(a)domain.tld): Debug: brain S: We don't have mailbox deadbeefdeabbeefdeadbeefdeabbeef dsync(contact(a)domain.tld): Debug: brain M: Change during sync: Remote lost mailbox GUID deadbeefdeabbeefdeadbeefdeabbeef (maybe it was just deleted?) dsync(contact(a)domain.tld): Warning: Mailbox changes caused a desync. You may want to run dsync again: Remote lost mailbox GUID deadbeefdeabbeefdeadbeefdeabbeef (maybe it was just deleted?) Does someone have on hint? Best regards. François -- François Poulain <fpoulain(a)metrodore.fr>

3 4

Re: Fatal: write(indexer) failed: Resource temporarily unavailable
by Aki Tuomi 06 Nov '20

06 Nov '20

> On 06/11/2020 13:37 Joan Moreau <jom(a)grosjo.net> wrote: > > > Hello > I have this issue for Xapian plugin: > https://github.com/grosjo/fts-xapian/issues/62 > > But I am not sure where can it comes from. > Is dovecot calling some specific function in the plugin after the init, that would create such error ? > In doveadm dealing differently with plugins that dovecot core does ? > Has there been some recent changes in the plugin framework that would lead to such error ? > Thank you https://wiki.dovecot.org/SocketUnavailable Aki

1 0

Fatal: write(indexer) failed: Resource temporarily unavailable
by Joan Moreau 06 Nov '20

06 Nov '20

Hello I have this issue for Xapian plugin: https://github.com/grosjo/fts-xapian/issues/62 But I am not sure where can it comes from. Is dovecot calling some specific function in the plugin after the init, that would create such error ? In doveadm dealing differently with plugins that dovecot core does ? Has there been some recent changes in the plugin framework that would lead to such error ? Thank you

1 0

Indexer error after upgrade to 2.3.11.3
by Alessio Cecchi 06 Nov '20

06 Nov '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

9 25

Understanding the limitations of Dovecot Submission Service
by R. Diez 04 Nov '20

04 Nov '20

Hi all: The Dovecot Submission Service is very enticing for laz... I mean for busy people like me. A couple of lines in dovecot.conf , and you have a local SMTP server that does authentication. No SASL loops to jump through! Very cool people like me also appreciate cool new features like BURL. But now I want to understand its limitations. Say I just bought e-mail domain xxx(a)example.org . Say employee A has e-mail address a(a)example.org . It this employee turns evil, will he/she be able to send e-mails impersonating b(a)example.org ? Or does the Dovecot Submission Service check that he only has permission to send as a(a)example.org ? My requirements are pretty modest. Basically e-mail should just be sent all right. But are there any other reasons why I should avoid the Dovecot Submission Server anyway? The documentation does not really say much. Thanks in advance, rdiez

1 0

Re: API support for placing a message for a specific user
by Aki Tuomi 04 Nov '20

04 Nov '20

> On 03/11/2020 02:24 Oren Yehezkely <orenyny(a)gmail.com> wrote: > > > Hello, > > I am trying to find out if Dovecot API allows placing a message directly in a customer's mailbox, without needing to send the email via SMTP. > > Thanks for your help, > > Oren `doveadm save` is available from HTTP API, but seems to be missing from documentation. Example: curl --user doveadm:password http://localhost:1122/doveadm/v1 -d '[["save",{"user":"testuser","file":"Hello, world"},"c0d0"]]' note that despite being called 'file', is it actually the mail contents. Aki API for the SAVE command: { "command": "save", "parameters": [ { "name": "allUsers", "type": "boolean" }, { "name": "socketPath", "type": "string" }, { "name": "user", "type": "string" }, { "name": "transFlags", "type": "integer" }, { "name": "userFile", "type": "string" }, { "name": "mailbox", "type": "string" }, { "name": "file", "type": "string" } ] }

2 1

Re: Panic-Error (ctx->nested_parts_count > 0)
by Aki Tuomi 04 Nov '20

04 Nov '20

You should be able to workaround this by enabling fts. Aki > On 04/11/2020 09:22 Andreas Piper <piper(a)hrz.uni-marburg.de> wrote: > > > Hello, > > on my dovecot-replicator-backend I see lots of panic-messages "assertion > failed: (ctx->nested_parts_count > 0)", produced from a single user. I > assume that this is correlated with > https://github.com/dovecot/core/commit/a668d767a710ca18ab6e7177d8e8be22a6b0… > > How can I identify the incorrect formatted message in the user's > mailbox? I want to remove it, as the error-processes drive up the > backend's load incredibly. > > Will a fixed dovecot-package be out soon? > > Any help is appreciated. > > Best regards, > Andreas > > My system-data: > # 2.3.11.3 (502c39af9): /etc/dovecot/dovecot.conf > # Pigeonhole version 0.5.11 (6c69c917) > # OS: Linux 4.15.0-122-generic x86_64 Ubuntu 18.04.5 LTS > > An example error-message: > > Nov 04 08:04:25 vhrz311 dovecot[6163]: > imap(xxx(a)staff.uni-marburg.de)<63176><ad/jlkKzSs2sGQEp>: Panic: file > message-parser.c: line 174 (message_part_finish): assertion failed: > (ctx->nested_parts_count > 0) > Nov 04 08:04:25 vhrz311 dovecot[6163]: > imap(xxx(a)staff.uni-marburg.de)<63173><ORvjlkKzRs2sGQEp>: Fatal: master: > service(imap): child 63173 killed with signal 6 (core dumps disabled - > https://dovecot.org/bugreport.html#coredumps) > Nov 04 08:04:25 vhrz311 dovecot[6163]: > imap(xxx(a)staff.uni-marburg.de)<63176><ad/jlkKzSs2sGQEp>: Error: Raw > backtrace: /usr/lib/dovecot/libdovecot.so.0(backtrace_append+0x42) > [0x7f1dd28d6d22] -> /usr/lib/dovecot/libdovecot.so.0(backtrace_get+0x1e) > [0x7f1dd28d6e3e] -> /usr/lib/dovecot/libdovecot.so.0(+0xed75e) > [0x7f1dd28e175e] -> /usr/lib/dovecot/libdovecot.so.0(+0xed801) > [0x7f1dd28e1801] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) > [0x7f1dd2836beb] -> /usr/lib/dovecot/libdovecot.so.0(+0xcd40e) > [0x7f1dd28c140e] -> > /usr/lib/dovecot/libdovecot.so.0(message_parser_parse_next_block+0x15c) > [0x7f1dd28c2b2c] -> > /usr/lib/dovecot/libdovecot.so.0(message_search_msg+0xa0) > [0x7f1dd28c52a0] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xc8f9e) > [0x7f1dd2c67f9e] -> > /usr/lib/dovecot/libdovecot-storage.so.0(mail_search_args_foreach+0x45) > [0x7f1dd2be31e5] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xca111) > [0x7f1dd2c69111] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xcb214) > [0x7f1dd2c6a214] -> > /usr/lib/dovecot/libdovecot-storage.so.0(index_storage_search_next_nonblock+0x10d) > [0x7f1dd2c6a9ed] -> > /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_search_next_nonblock+0x22) > [0x7f1dd2becdf2] -> dovecot/imap(+0x25eb1) [0x561689529eb1] -> > dovecot/imap(command_exec+0x64) [0x561689522bc4] -> > dovecot/imap(+0x25592) [0x561689529592] -> > /usr/lib/dovecot/libdovecot.so.0(io_loop_handle_timeouts+0x12f) > [0x7f1dd28fa3ff] -> > /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0xbe) > [0x7f1dd28fbebe] -> > /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x4c) > [0x7f1dd28fa75c] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x38) > [0x7f1dd28fa988] -> > /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13) > [0x7f1dd2867c23] -> dovecot/imap(main+0x339) [0x561689512d19] -> > /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7) [0x7f1dd2424bf7] > -> dovecot/imap(_start+0x2a) [0x561689512f2a]

1 0

Panic-Error (ctx->nested_parts_count > 0)
by Andreas Piper 04 Nov '20

04 Nov '20

Hello, on my dovecot-replicator-backend I see lots of panic-messages "assertion failed: (ctx->nested_parts_count > 0)", produced from a single user. I assume that this is correlated with https://github.com/dovecot/core/commit/a668d767a710ca18ab6e7177d8e8be22a6b0… How can I identify the incorrect formatted message in the user's mailbox? I want to remove it, as the error-processes drive up the backend's load incredibly. Will a fixed dovecot-package be out soon? Any help is appreciated. Best regards, Andreas My system-data: # 2.3.11.3 (502c39af9): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.11 (6c69c917) # OS: Linux 4.15.0-122-generic x86_64 Ubuntu 18.04.5 LTS An example error-message: Nov 04 08:04:25 vhrz311 dovecot[6163]: imap(xxx(a)staff.uni-marburg.de)<63176><ad/jlkKzSs2sGQEp>: Panic: file message-parser.c: line 174 (message_part_finish): assertion failed: (ctx->nested_parts_count > 0) Nov 04 08:04:25 vhrz311 dovecot[6163]: imap(xxx(a)staff.uni-marburg.de)<63173><ORvjlkKzRs2sGQEp>: Fatal: master: service(imap): child 63173 killed with signal 6 (core dumps disabled - https://dovecot.org/bugreport.html#coredumps) Nov 04 08:04:25 vhrz311 dovecot[6163]: imap(xxx(a)staff.uni-marburg.de)<63176><ad/jlkKzSs2sGQEp>: Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(backtrace_append+0x42) [0x7f1dd28d6d22] -> /usr/lib/dovecot/libdovecot.so.0(backtrace_get+0x1e) [0x7f1dd28d6e3e] -> /usr/lib/dovecot/libdovecot.so.0(+0xed75e) [0x7f1dd28e175e] -> /usr/lib/dovecot/libdovecot.so.0(+0xed801) [0x7f1dd28e1801] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f1dd2836beb] -> /usr/lib/dovecot/libdovecot.so.0(+0xcd40e) [0x7f1dd28c140e] -> /usr/lib/dovecot/libdovecot.so.0(message_parser_parse_next_block+0x15c) [0x7f1dd28c2b2c] -> /usr/lib/dovecot/libdovecot.so.0(message_search_msg+0xa0) [0x7f1dd28c52a0] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xc8f9e) [0x7f1dd2c67f9e] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_search_args_foreach+0x45) [0x7f1dd2be31e5] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xca111) [0x7f1dd2c69111] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xcb214) [0x7f1dd2c6a214] -> /usr/lib/dovecot/libdovecot-storage.so.0(index_storage_search_next_nonblock+0x10d) [0x7f1dd2c6a9ed] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_search_next_nonblock+0x22) [0x7f1dd2becdf2] -> dovecot/imap(+0x25eb1) [0x561689529eb1] -> dovecot/imap(command_exec+0x64) [0x561689522bc4] -> dovecot/imap(+0x25592) [0x561689529592] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handle_timeouts+0x12f) [0x7f1dd28fa3ff] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0xbe) [0x7f1dd28fbebe] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x4c) [0x7f1dd28fa75c] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7f1dd28fa988] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f1dd2867c23] -> dovecot/imap(main+0x339) [0x561689512d19] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7) [0x7f1dd2424bf7] -> dovecot/imap(_start+0x2a) [0x561689512f2a]

1 0

Re: vsz_limit
by Aki Tuomi 04 Nov '20

04 Nov '20

> On 04/11/2020 05:19 Joan Moreau <jom(a)grosjo.net> wrote: > > > Hello > I am looking for help around memory management > 1 - How to get the current value of "vsz_limit" from inside a plugin (namely https://github.com/grosjo/fts-xapian/ ) , especially for indexer-worker > 2 - Is there a macro or function in dovecot to get the remaining free memory from this vsz value ? > Thank you > > Hi Joan, I don't think there is a feasible way to access this setting as of now. Is there a reason you need this? We usually recommend setting vsz_limit=0 for indexer-worker. Aki

2 1

Re: vsz_limit
by Aki Tuomi 04 Nov '20

04 Nov '20

> On 04/11/2020 05:19 Joan Moreau <jom(a)grosjo.net> wrote: > > > Hello > I am looking for help around memory management > 1 - How to get the current value of "vsz_limit" from inside a plugin (namely https://github.com/grosjo/fts-xapian/ ) , especially for indexer-worker > 2 - Is there a macro or function in dovecot to get the remaining free memory from this vsz value ? > Thank you > >

1 0

vsz_limit
by Joan Moreau 04 Nov '20

04 Nov '20

Hello I am looking for help around memory management 1 - How to get the current value of "vsz_limit" from inside a plugin (namely https://github.com/grosjo/fts-xapian/ ) , especially for indexer-worker 2 - Is there a macro or function in dovecot to get the remaining free memory from this vsz value ? Thank you

1 0

Feature Request: Redis support for username and TLS
by Mark Moseley 04 Nov '20

04 Nov '20

I was wondering if there was any imminent support in 2.3.12+ for using a username to log into Redis, as well as support for using TLS to connect to Redis. And if not, I'd like to put in a feature request for those two things (AUTH with username/password, and TLS connections to Redis). Specifically, I was looking at using a username/password combo to log into Redis for the quota_clone plugin. I found the 'password' param in the source (not documented at https://wiki.dovecot.org/Dictionary) There's no 'username' param (the 'username' in the source seems to refer to the mailbox, for the purpose of building the key name). Redis 6 supports authenticating with a username and password, as well as the ability to listen on a TLS-enabled port. Both of these significantly improve security, combined with the new ACL system. Obviously, these Redis 6 features are brand new, so I'd be shocked if they were already supported. But it'd be awesome if those were added to Dovecot :) Currently, I've got a localhost Envoy proxy doing TCP proxying from localhost+non-TLS to my Redis TLS port, which is a kludge at best. There's a neat Envoy Redis proxy that *almost* does the trick but the Envoy Redis proxy unfortunately doesn't support MULTI/EXEC, which Dovecot quota_clone uses, or I'd be using that instead of a plain TCP proxy (since the Envoy Redis proxy can use a username/password+tls to connect to the upstream Redis).

1 0

Delivering locally through the Submission Server
by R. Diez 03 Nov '20

03 Nov '20

Hi all: I am learning Dovecot step by step. I have enabled the Submission Server, in the hope that I would not need to learn other MTAs like Postfix. The Submission Server is very comfortable: it picks up the existing Dovecot configuration, so that you do not need to configure any user authentication separately. It is working fine on my test setup. My first thought was that, if the recipient is a local mailbox, the Submission Server would not need to relay the message to any external SMTP server, as it could just deliver it locally. After all, it is running on the same Dovecot. But it cannot do that, can it? Is there a work-around? I am still hoping that the mail server still works locally if the Internet connection fails. But I would need to learn some Postfix magic for that, would I? Thanks in advance, rdiez

5 7

Re: Delivering locally through the Submission Server
by Aki Tuomi 03 Nov '20

03 Nov '20

> On 03/11/2020 12:31 Piotr Auksztulewicz <dcml(a)hasiok.net> wrote: > > > On Mon, Nov 02, 2020 at 09:33:08PM +0100, R. Diez wrote: > > OK, so I gather that the Submission Server cannot do that (yet). > > And probably would never do. It isn't its job description. > > Actually, it is just a convenience/workaround feature, which comes handy > only if your own MTA cannot handle dovecot's SASL authentication (must be > something real strange) or there are some integration/security/policy > issue perceived (but I cannot think of any, actually). In this case you > can set up dovecot's submission server, which uses dovecot's authentication > settings, so you have single source of authentication, and whitelist > dovecot IP address in your MTA so it accepts anything that dovecot's > submission server lets through. But I don't think it is a good idea > personally, it is more open to exploitation this way, unless the > address is 127.0.0.1, in which case you can simply set up SASL over > Unix sockets, which is as secure as your host server is. > Submission service is not only a proxy, it - provides authentication natively from Dovecot - provides features like BURL, and maybe in future outbound Sieve but it does require real MTA behind. -- Aki

2 1

API support for placing a message for a specific user
by Oren Yehezkely 03 Nov '20

03 Nov '20

Hello, I am trying to find out if Dovecot API allows placing a message directly in a customer's mailbox, without needing to send the email via SMTP. Thanks for your help, Oren

1 0

Re: strange file .temp.1592374672.P11164Q21M692534.hostname - doveadm altmove
by Aki Tuomi 02 Nov '20

02 Nov '20

> On 01/11/2020 21:13 John Stoffel <john(a)stoffel.org> wrote: > > > >>>>> "Gionatan" == Gionatan Danti <g.danti(a)assyoma.it> writes: > > Gionatan> Il 2020-11-01 13:23 John Stoffel ha scritto: > >> How is your "mail_location" defined in your configuration? And what > >> is your search term? > > Gionatan> Hi, I just discovered having such strange .temp files on an > Gionatan> old server of mine. > > I honestly haven't a clue... I don't have these on my server at all. > > Gionatan> In some folders I have hundred of such files, but they > Gionatan> really are hardlinks to the same .temp file (for each > Gionatan> folder), so they do not consume much space. These files > Gionatan> seems much more common in the Trash folder, but they appear > Gionatan> even in other folder. > > I would probably just nuke these files, but maybe after confirming > what their contents really is. > > Gionatan> An example of a folder with 6 .temp files: > Gionatan> [root@mail dbox-Mails]# ls -al > Gionatan> /var/vmail/domain/user/dbox/mailboxes/INBOX/Trash/dbox-Mails > Gionatan> drwxr-x---. 2 vmail vmail 4096 Oct 31 12:42 . > Gionatan> drwxr-x---. 3 vmail vmail 4096 Mar 17 2020 .. > Gionatan> -rw-r-----. 1 vmail vmail 512 Oct 29 09:45 dovecot.index > Gionatan> -rw-r-----. 1 vmail vmail 392 Oct 28 13:59 dovecot.index.backup > Gionatan> -rw-r-----. 1 vmail vmail 55296 Oct 31 12:42 dovecot.index.cache > Gionatan> -rw-r-----. 1 vmail vmail 23536 Oct 31 12:42 dovecot.index.log > Gionatan> -rw-r-----. 6 vmail vmail 22215889 Oct 12 10:42 > Gionatan> .temp.1602492703.P47358Q0M194142.hostname > Gionatan> -rw-r-----. 6 vmail vmail 22215889 Oct 12 10:42 > Gionatan> .temp.1602494002.P50402Q0M898232.hostname > Gionatan> -rw-r-----. 6 vmail vmail 22215889 Oct 12 10:42 > Gionatan> .temp.1602494013.P50446Q0M771524.hostname > Gionatan> -rw-r-----. 6 vmail vmail 22215889 Oct 12 10:42 > Gionatan> .temp.1602494621.P51761Q0M119496.hostname > Gionatan> -rw-r-----. 6 vmail vmail 22215889 Oct 12 10:42 > Gionatan> .temp.1602494745.P51954Q0M387071.hostname > Gionatan> -rw-r-----. 6 vmail vmail 22215889 Oct 12 10:42 > Gionatan> .temp.1602495419.P53185Q0M671512.hostname > Gionatan> -rw-r-----. 1 vmail vmail 848909 Oct 29 21:12 u.1623 > > Gionatan> 6x 22M files = 128M... > Gionatan> [root@mail dbox-Mails]# du -hscl .temp.160249* > Gionatan> 22M .temp.1602492703.P47358Q0M194142.hostname > Gionatan> 22M .temp.1602494002.P50402Q0M898232.hostname > Gionatan> 22M .temp.1602494013.P50446Q0M771524.hostname > Gionatan> 22M .temp.1602494621.P51761Q0M119496.hostname > Gionatan> 22M .temp.1602494745.P51954Q0M387071.hostname > Gionatan> 22M .temp.1602495419.P53185Q0M671512.hostname > Gionatan> 128M total > > Gionatan> ...but only 22M really consumed (1 file, 6 hardlinks) > Gionatan> [root@mail dbox-Mails]# du -hsc .temp.160249* > Gionatan> 22M .temp.1602492703.P47358Q0M194142.hostname > Gionatan> 22M total > > Gionatan> I never run doveadm altmove; moreover, these .tempo files > Gionatan> are both old (>1 year) and new (~3 weeks ago). Below you can > Gionatan> find the output from dovecot -n. Any ideas? > > I really don't know, sorry! I'd have to got poke at the source to see > how they're created and where. I don't use dbox, I use Maildir for my > setup. > > So I suspect (but I'm not sure!) that these are just leftovers from > mailbox accesses which got left behind. Try googling for 'dovecot > dbox temp files' and maybe that will help. Sorry! > > John Those files are most likely leftovers due to failed operations, for reasons like crashes. Aki

2 1

v2.3.11.3 solr plugin search via MUA fails to match accented ascii characters; cmd line exec of `doveadm fts lookup` PANICs (assertion failed)
by PGNet Dev 02 Nov '20

02 Nov '20

I'm running, dovecot --version 2.3.11.3 (502c39af9) solr -version 8.6.3 uname -rm 5.8.13-200.fc32.x86_64 x86_64 grep _NAME /etc/os-release PRETTY_NAME="Fedora 32 (Server Edition)" CPE_NAME="cpe:/o:fedoraproject:fedora:32" Solr FTS plugin is enabled/configured, mail_plugins = virtual acl fts fts_solr plugin { fts = solr fts_autoindex = yes fts_solr = url=https://solr.example.com:8984/solr/dovecot/ fts_enforced = body fts_filters = normalizer-icu stopwords snowball fts_language_config = /usr/share/libexttextcat/fpdb.conf fts_languages = en es de fr it pt soft_commit = yes } IMAP capability returns, a OK [CAPABILITY IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS THREAD=ORDEREDSUBJECT MULTIAPPEND URL-PARTIAL CATENATE UNSELECT CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS BINARY MOVE SNIPPET=FUZZY PREVIEW=FUZZY STATUS=SIZE SAVEDATE SPECIAL-USE LITERAL+ NOTIFY SPECIAL-USE QUOTA ACL RIGHTS=texk] Logged in I've got two messages in my IMAP store, cd /data/vmail/example.com/myuser/Maildir/cur/ ls -altr | grep S= | /bin/tail -n2 -rw------- 1 vmail vmail 1.3K Oct 11 14:05 1602450306.M393628P65260.mx.example.com,S=1278,W=1304:2,S -rw------- 1 vmail vmail 1.3K Oct 11 14:05 1602450353.M756184P65260.mx.example.com,S=1277,W=1303:2,S that differ in BODY CONTENT -- -- one message has ascii txt with NO character accents -- the other has the same text, but with ON character accent cat "1602450306.M393628P65260.mx.example.com,S=1278,W=1304:2,S" ... From: M User <myuser(a)example.com> Subject: test Reply-To: myuser(a)example.com To: "User, My" <myuser(a)example.com> Message-ID: <6fc7ac30-b460-7dd4-f85d-ca4403ad7188(a)example.com> Date: Sun, 11 Oct 2020 14:05:06 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.3.2 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit !!!! también cat 1602450353.M756184P65260.mx.example.com,S=1277,W=1303:2,S ... From: M User <myuser(a)example.com> Subject: test Reply-To: myuser(a)example.com To: "User, My" <myuser(a)example.com> Message-ID: <015b3fb4-46f9-87cc-d541-060db0a13086(a)example.com> Date: Sun, 11 Oct 2020 14:05:53 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.3.2 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit !!!! tambien i manually re-scan & index doveadm fts rescan -u myuser(a)example.com doveadm index -u myuser(a)example.com -q '*' ... ==> /var/log/dovecot/dovecot-info.log <== 2020-10-11 15:06:34 indexer-worker(myuser(a)example.com)<OyUmLeqBg18fDAEA+IOfAw>: Info: Indexed 21 messages in accts (UIDs 14399..130699) 2020-10-11 15:06:34 indexer-worker(myuser(a)example.com)<6NnOMuqBg18fDAEA+IOfAw>: Info: Indexed 16 messages in accts/v007132 (UIDs 13414..14778) ... with no errors. then search in mail client, here TBird 78, with [X] Run Search on Server for _un_accented "tambien", match is correctly -- and quickly -- returned. in logs, ==> /var/log/dovecot/dovecot-info.log <== 2020-10-11 14:57:05 imap-login: Info: Login: user=<myuser(a)example.com>, method=PLAIN, rip=10.0.1.7, lip=10.0.1.50, mpid=67743, TLS 2020-10-11 14:57:16 indexer-worker(myuser(a)example.com)<3ZUzQ2yx2JKsHgsH:9gu0MbF/g1+hCAEA+IOfAw>: Info: Indexed 4788 messages in INBOX (UIDs 135476..140263) BUT, repeating search for ACCENTED "también" returns *no* match/result. No errors in log, simply no match. Attempting to test/debug from from cmd line, doveadm fts lookup -u myuser(a)example.com body "tambien" causes a PANIC doveadm(myuser(a)example.com): Panic: file mail-storage.c: line 2112 (mailbox_get_open_status): assertion failed: (box->opened) doveadm(myuser(a)example.com): Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(backtrace_append+0x46) [0x7f3ee94accc6] -> /usr/lib64/dovecot/libdovecot.so.0(backtrace_get+0x22) [0x7f3ee94acde2] -> /usr/lib64/dovecot/libdovecot.so.0(+0x10025b) [0x7f3ee94b625b] -> /usr/lib64/dovecot/libdovecot.so.0(+0x100297) [0x7f3ee94b6297] -> /usr/lib64/dovecot/libdovecot.so.0(+0x59bc6) [0x7f3ee940fbc6] -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0x4779e) [0x7f3ee95c379e] -> /usr/lib64/dovecot/lib21_fts_solr_plugin.so(+0x5849) [0x7f3ee9015849] -> /usr/lib64/dovecot/lib20_fts_plugin.so(fts_backend_lookup+0x51) [0x7f3ee8c37491] -> /usr/lib64/dovecot/doveadm/lib20_doveadm_fts_plugin.so(+0x3280) [0x7f3ee8ba9280] -> doveadm(+0x343cd) [0x5637e99443cd] -> doveadm(+0x34fe0) [0x5637e9944fe0] -> doveadm(doveadm_cmd_ver2_to_mail_cmd_wrapper+0x22d) [0x5637e9945e2d] -> doveadm(doveadm_cmd_run_ver2+0x4e8) [0x5637e99568d8] -> doveadm(doveadm_cmd_try_run_ver2+0x3e) [0x5637e995692e] -> doveadm(main+0x1d4) [0x5637e9934cf4] -> /lib64/libc.so.6(__libc_start_main+0xf2) [0x7f3ee9071042] -> doveadm(_start+0x2e) [0x5637e99351ce] Aborted (1) What config -- dovecot &/or solr -- is needed to match on accented characters? (2) What add'l detail, if any, is needed for troubleshooting the panic?

5 37

removing 'use_libfts' from dovecot fts_solr config; docs/examples of solr-backend-only tokenizer config for dovecot?
by PGNet Dev 02 Nov '20

02 Nov '20

given existing problems with fts_solr = ... use_libfts ... i've rm'd it from dovecot config, and am moving all tokenization to solr config. iiuc, in dovecot + solr context, that's correctly config'd in solr/data/dovecot/conf/schema.xml dovecot release ships with 'starter configs', cp -af /usr/share/doc/dovecot/solr-config-7.7.0.xml /path/to/solr/data/dovecot/conf/solrconfig.xml cp -af /usr/share/doc/dovecot/solr-schema-7.7.0.xml /path/to/solr/data/dovecot/conf/schema.xml that^ schema.xml contains a limited solr.StandardTokenizerFactory config. it can of course be extended; lots of generic solr config info available. is there _documentation_, preferably a good example, of a dovecot-'friendly' solr config for non-"use_libfts" use case? specifically, moving any/all of the libfts front-end tokenizers @ https://doc.dovecot.org/configuration_manual/fts/tokenization/#fts-tokeniza… https://doc.dovecot.org/settings/plugin/fts-plugin/#plugin-fts-setting-fts-… fully to a backend solr instance? i suspect that solr config is fairly well insulated from dovecot's; what i'm not sure of is if dovecot's fts has specific requirements to get the backend-only tokenization working.

1 0

Re: v2.3.11.3 solr plugin search via MUA fails to match accented ascii characters; cmd line exec of `doveadm fts lookup` PANICs (assertion failed) [proposed patch]
by Aki Tuomi 02 Nov '20

02 Nov '20

> On 02/11/2020 15:11 PGNet Dev <pgnet.dev(a)gmail.com> wrote: > > > On 11/2/20 12:44 AM, Aki Tuomi wrote: > > you should try removing use_libfts from your config line and let solr do that part. > > sry, i'm a bit confused. > > you'd suggested I _add_ it, > > https://dovecot.org/pipermail/dovecot/2020-October/120258.html > > > I can reproduce your problem with the `fts lookup` command. Luckily it's equivalent to running `doveadm search`. I'll open a bug about this. > > Dovecot FTS tokenization is not done, unless you have `use_libfts` in fts_solr setting, in your case > > fts_solr = url=https://solr.example.com:8984/solr/dovecot/ use_libfts > > Without this, everything is sent to to solr as-is, which is then expected to do all the work. > > So what's the recommendation? use use_libfts, or not? It's a choice. You can let solr perform the tokenization etc. or you can let dovecot do it. There is no recommendation when using solr. It seems that use_libfts is broken with solr due to reasons, so I guess the only option for now is not to use it. Aki

2 1

Re: v2.3.11.3 solr plugin search via MUA fails to match accented ascii characters; cmd line exec of `doveadm fts lookup` PANICs (assertion failed) [proposed patch]
by Aki Tuomi 02 Nov '20

02 Nov '20

> On 01/11/2020 20:35 John Fawcett <john(a)voipsupport.it> wrote: > > > On 01/11/2020 15:20, PGNet Dev wrote: > > On 11/1/20 1:56 AM, John Fawcett wrote: > >> At the moment I don't see other corrections needed in dovecot apart from > >> command line doveadm fts which is not a show stopper. Via doveadm search > >> I confirm - on my simple config - that search for accented or non > >> accented characters works correctly as it does via imap connection. > > > > thx. hopefully it'll get considered for a next release soon. > > > >> Only thing I cannot vouch for is bringing dovecot fts library and config > >> into the equation because my setup delegates almost everything to solr. > > > > do i understand correctly that you're solr-indexing your dovecot mail > > store withOUT using dovecot fts plugin, and that -- with your > > aforementioned patch -- doveadm successfully uses the resulting indexes? > > > > i hadn't yet seriously considered _circumventing_ fts plugin; if this^ > > does get resolved soonish, then it's not a big deal. if not, an > > fts-plugin-less setup would be interesting to know more abt! > > > >> Can you get evidence of things not working? For example tests run with > >> soft_commit configured - that's important since without it the updates > >> don't show up immediately in searches, that do show that the update is > >> happening in solr via solr log, but then search is not working on > >> accented characters, despite it working on other text in the same > >> message? The solr logs also show whether the text was found or not via > >> the "hits=" value in the logged searches, for example: > >> > >> 2020-11-01 08:32:42.231 INFO (qtp24119573-21) [ x:dovecot] > >> o.a.s.c.S.Request [dovecot] webapp=/solr path=/select > >> params={q={!lucene+q.op%3DAND}body:también&fl=uid,score&sort=uid+asc&fq=%2Bbox:b1626f0fe8d9145e54100000c54a863a+%2Buser:john@voipsupport.it&rows=3202&wt=xml} > >> > >> hits=3 status=0 QTime=3 > >> > >> But if no hits are found, then dovecot cannot be expected to display > >> results. It still may be an indexing problem though. > > > > my current config has soft_commit enabled, > > > > fts_solr = url=https://solr.example.com:8984/solr/dovecot/ > > use_libfts soft_commit=yes batch_size=250 > > > > i'll see abt getting some clearer test results ... > > Yes, getting more data about any potential problem would be useful. > > Just to clarify: I have a fully working search setup for some time now > over various dovecot releases, so no patches needed to get it working. > > My setup does use fts plugin and fts-solr plugin, but it does not use > lib-fts functionality (that has many features for example it was > stopping you indexing excluded words like tambien). On my setup without > lib-fts everything goes to solr which does the work of indexing without > all the features of lib-fts. > > My setup is like this not because of issues in lib-fts, but because I > never had the need for it. There is no evidence at the moment however > that even with lib-fts enabled there are issues with dovecot indexing or > searching. > > What is currently nor working is "doveadm fts" command line utility. But > this is mitigated by being able to use a similar command line utility > "doveadm search". The issue on "dovecot fts" command line utility has > (so far as the available evidence suggests) no effect on indexing or > imap searches. > > fyi my working configuration includes fts and fts_solr plugins > > mail_plugins = quota notify replication fts fts_solr > > (and those are also recalled in the various specific plugin settings for > imap, lmtp ecc), The specific config I am using for fts and fts_solr is: > > fts = solr > fts_enforced = yes > fts_solr = url=https://user@server.example.com:443/solr/dovecot/ > batch_size=500 soft_commit=no > > BTW I use soft_commit=no because I have periodic soft commits setup on > solr and I accept that newly indexed text won't become searchable for up > to that interval, but for your testing purposes much more useful as you > have it. > > John PGNet, you should try removing use_libfts from your config line and let solr do that part. Aki

2 1

strange file .temp.1592374672.P11164Q21M692534.hostname - doveadm altmove
by Maciek Jackowski 01 Nov '20

01 Nov '20

dovecot 2.2.33.2 Ubuntu 18.04 I got strange file .temp.1592374672.P11164Q21M692534.hostname after doveadm altmove command in INBOX on alternate storage server What can I do with this file? Remove? I am using dbox regards

3 3

doveadm altmove not working for some folders
by Maciek Jackowski 01 Nov '20

01 Nov '20

dovecot 2.2.33.2 on Ubuntu 18.04 I am using dbox with altmove to save storage space on mail server I got strange behaviour with one email box where folder content Archives/2018 is not moving but other folders Archives/2017 and Archives/2019 are moved to the alternate storage server Well I dont know howto start to resolve this regards

1 0

sieve-extdata plugin breaks on pigeonhole 0.5 ish
by Ed W 01 Nov '20

01 Nov '20

Hi, I wonder if someone could give me a little help bringing the sieve-extdata plugin up to date to be usable with latest Dovecot/pigeonhole Trying to use both together at present I get an error: managesieve: Fatal: Couldn't load required plugin /usr/lib/dovecot/sieve/lib90_sieve_extdata_plugin.so: dlopen() failed: /usr/lib/dovecot/sieve/lib90_sieve_extdata_plugin.so: undefined symbol: sieve_sys_error This appears to be due to the change in error handling in pigeonhole 0.5 which appears to have removes the "sieve_sys_error()" and "sieve_sys_warning()" functions I'm unclear how this code should be change (I've commented it out for now - eek). I find this extension useful to pass in user specific parameters to my sieve scripts that are stored elsewhere in an sql database, eg spam score, size threshold for attachments, perhaps there is some other way to achieve this? Any hints on how to fixing this would be appreciated Thanks Ed W

3 2

Dovecot, sa-learn and sieve - where to save the Bayes DB
by Francis Augusto Medeiros-Logeay 31 Oct '20

31 Oct '20

Hi! I have dovecot, Spamassassin and postfix running. I started to use sa-learn to get better and more precise spam identification and filtering. I have not set the Bayes_path preference on my local.cf file, thus when I call sa-learn -u myuser(a)mydomain.org --spam, the Bayes DB gets updated at /root/.spamassassin. I decided then to create a sieve filter on dovecot, as described on Dovecot's wiki page. Basically, Dovecot's sieve plugin execute sa-learn with a -u argument, apparently the same way I do when I use it manually. BUT, the thing is that when Dovecot executes sa-learn, the bayes database is created on the virtual user's folder, ie., /var/mail/vmail/mydomain.org/user/.spamassassin. When I call it manually, the db used is /root/.spamassassin` I am now confused as I don't know if, when evaluating spam, spamd will use the Bayes DB on the user's Maildir, or if it will use the one under /root/.spamassassin. I would really like to have my spam evaluation done per user, not site wide, so I wonder: - How can I configure bayes_path for each user, individually, on a virtual users setup? - Does calling spamd with --virtual-config-dir have anything to do with this? I tried it, setting it up with my virtual users path, but it didn't seem to make any difference when it comes to what I describe in this post. With or without it set up, the results above are the same. -- Francis Augusto Medeiros-Logeay Oslo, Norway

1 0

Odd replication behaviour
by James Pattinson 31 Oct '20

31 Oct '20

Hi, I have just built a new pair of similar machines both running CentOS 8.2 (selinux disabled) and Dovecot 2.3.8 (9df20d2db). One machine is a VPS (host A) and one is on my home network (host B). The idea is that they are set up in a master/master config with Dovecot replication. I seem to have this 95% working but there is one strange issue I can’t work out. Currently B is a perfect replica of A. I have pointed an instance of Thunderbird at it, and I can see all my mails. If I delete any mails or change any flags, I see the same changes almost instantly on the A side. PROBLEM: if host A receives a new mail, I don’t see it on B until I do ‘something’ to change metadata, for example deleting any random email, or marking an email as read on EITHER side causes the new email to appear almost instantly on the B side. I would have expected emails on B to appear immediately. Am I doing something wrong? Extra info - my mailboxes are in Maildir format with single OS user (vmail). I have about 4000 emails in the Inbox and about 30k in other folders. There are only 5 users and I’m using passdb as the very simple backend. Replication is via doveadm on a specified port (not SSH). Some output from dovecot -n is below. Cheers James HOST A # 2.3.8 (9df20d2db): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.8 (b7b03ba2) # OS: Linux 4.18.0-193.28.1.el8_2.x86_64 x86_64 CentOS Linux release 8.2.2004 (Core) xfs # Hostname: hosta.domain auth_mechanisms = plain login doveadm_password = # hidden, use -P to show it doveadm_port = 4040 first_valid_uid = 1000 mail_debug = yes mail_home = /srv/vmail/%u mail_location = maildir:/srv/vmail/%u mail_plugins = notify replication managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date index ihave duplicate mime foreverypart extracttext mbox_write_locks = fcntl namespace inbox { inbox = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk { auto = subscribe special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { auto = subscribe special_use = \Trash } prefix = } passdb { args = scheme=BLF-CRYPT username_format=%u /etc/dovecot/users driver = passwd-file } plugin { mail_replica = tcp:b.b.b.b:4040 sieve = file:~/sieve;active=~/.dovecot.sieve sieve_before = /var/mail/SpamToJunk.sieve } protocols = imap lmtp service aggregator { fifo_listener replication-notify-fifo { group = root mode = 0660 user = vmail } unix_listener replication-notify { group = root mode = 0660 user = vmail } } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0600 user = postfix } } service doveadm { inet_listener { port = 4040 } } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { mode = 0600 user = vmail } } ssl = required ssl_cert = </etc/letsencrypt/live/mail2.pattinson.org/fullchain.pem ssl_cipher_list = PROFILE=SYSTEM ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it ssl_min_protocol = TLSv1.2 ssl_prefer_server_ciphers = yes userdb { args = username_format=%u /etc/dovecot/users default_fields = uid=vmail gid=mail home=/srv/vmail/%u driver = passwd-file } protocol lmtp { mail_plugins = sieve } protocol lda { mail_plugins = notify replication sieve } HOST B # 2.3.8 (9df20d2db): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.8 (b7b03ba2) # OS: Linux 4.18.0-193.28.1.el8_2.x86_64 x86_64 CentOS Linux release 8.2.2004 (Core) ext4 # Hostname: hostb auth_mechanisms = plain login doveadm_password = # hidden, use -P to show it doveadm_port = 4040 first_valid_uid = 1000 mail_debug = yes mail_home = /srv/vmail/%u mail_location = maildir:/srv/vmail/%u mail_plugins = notify replication managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date index ihave duplicate mime foreverypart extracttext mbox_write_locks = fcntl namespace inbox { inbox = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk { auto = subscribe special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { auto = subscribe special_use = \Trash } prefix = } passdb { args = scheme=BLF-CRYPT username_format=%u /etc/dovecot/users driver = passwd-file } plugin { mail_replica = tcp:a.a.a.a:4040 sieve = file:~/sieve;active=~/.dovecot.sieve sieve_before = /var/mail/SpamToJunk.sieve } protocols = imap lmtp service aggregator { fifo_listener replication-notify-fifo { group = root mode = 0660 user = vmail } unix_listener replication-notify { group = root mode = 0660 user = vmail } } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0600 user = postfix } } service doveadm { inet_listener { port = 4040 } } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { mode = 0600 user = vmail } } ssl = required ssl_cert = </etc/letsencrypt/live/mail2.pattinson.org/fullchain.pem ssl_cipher_list = PROFILE=SYSTEM ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it ssl_min_protocol = TLSv1.2 ssl_prefer_server_ciphers = yes userdb { args = username_format=%u /etc/dovecot/users default_fields = uid=vmail gid=mail home=/srv/vmail/%u driver = passwd-file } protocol lmtp { mail_plugins = sieve } protocol lda { mail_plugins = notify replication sieve }

1 1

Sieve filter script EXECUTION FAILED
by ＠lbutlr 31 Oct '20

31 Oct '20

So, I have the sieve working up to the point that it calls the script, and the script is called (I get different errors if the script is not there, for example). filter action execute program `darkmode.sh' [[EXECUTION ABORTED]] There's no other error logged (for example, when I had sieve_filter_bin_dir miss-set, I would get: sieve: action filter: failed to execute program `darkmode.sh': vnd.dovecot.filter extension is unconfigured In /var/log/messages, but I fixed that. I assume there is something wrong with what I am doing in the script, bit that is something I am not finding any examples on that are proving useful. The script file is simply: Darkmode.sh: #!/bin/sh echo $1 | sed -e '|</head>|<style>* {color:white !important; background-color: black !important; } </style></head>|' Which is somehwat similar to a working script for reporting spam: sa-learn-spam.sh: #!/bin/sh exec /usr/local/bin/sa-learn -u ${1} --spam -- "Are you pondering what I'm pondering?" "I think so, Brain, but won't it go straight to my hips?!"

5 8

Re: Sieve filter script EXECUTION FAILED
by Aki Tuomi 30 Oct '20

30 Oct '20

> On 30/10/2020 19:25 Bernd Petrovitsch <bernd(a)petrovitsch.priv.at> wrote: > > > On 30/10/2020 17:11, @lbutlr wrote: > [...] > > echo $1 | sed -e '|</head>|<style>* {color:white !important; background-color: black !important; } </style></head>|' > > What should the sed stuff do? > TTBOMK '|' is not known by sed ... > > MfG, > Bernd sed accepts | as alternative for / as boundary. But I think the sed here is missing 's' from start, so this does not actually do anything... Aki

5 5

Re: Sieve filter script EXECUTION FAILED
by Aki Tuomi 30 Oct '20

30 Oct '20

> On 30/10/2020 20:34 @lbutlr <kremels(a)kreme.com> wrote: > > > On 30 Oct 2020, at 11:57, Aki Tuomi <aki.tuomi(a)open-xchange.com> wrote: > > But I think the sed here is missing 's' from start, so this does not actually do anything... > > Copy/paste/edit error. The s is there in the file. > > darkmode.sh: > #!/bin/sh > echo $1 | sed -e 's|</head>|<style>* {color:white !important; background-color: black !important; } </style></head>|' > > I am not sure about the $1. I think filter just pipes the message (or part of the message. > > I will see what happens without the echo I suppose. > > Nope, still the same. > > 32: starting `:contains' match with `i;ascii-casemap' comparator: > 32: matching value `<!DOCTYPE html><html lang="en"><head><title>29-Oct-2020 ""</title> <style>?? ...' > 32: with key `</head>' => 1 > 32: finishing match with result: matched > 32: jump if result is false > 32: not jumping > 34: filter action > 34: execute program `darkmode.sh' > 34: [[EXECUTION ABORTED]] > > -- > They looked at the drinks. > They drank the drinks. I am pretty sure that you are holding filter wrong, it expects you to process the entire mail, not just $1. Aki

1 0

how to enable automatic sharing of folders added/created in an already shared folder hiearchy?
by PGNet Dev 30 Oct '20

30 Oct '20

I'm running dovecot --version 2.3.11.3 (502c39af9) folder sharing is enabled & working. as long as I manually enable enable sharing for each folder/subfolder. e.g., if I enable sharing for each of: sharedtopfolder subfolder1 subfolder2 then all's good -- shared-to users can access according to set permissions. BUT, if I drag any folder under that shared-hierarchy e.g., sharedtopfolder subfolder1 subfolder2 + subfolder3 + subfolder4 the just-added subfolder3 subfolder4 are NOT shared. They CAN be -- manually. And, as soon as they are, they're, again, usable by target users. I'd like to have any/all newly-created, or dragged-in, folders under the already-shared "sharedtopfolder" to be **automatically** enabled for sharing. how is that explicitly setup? is it 'just' Dovecot config? &/or does it require some Sieve?

1 0

Sieve matching the raw body
by ＠lbutlr 30 Oct '20

30 Oct '20

I have tried the following to match the string '</head>' in the body of an email: if body :raw :contains "</head>" { if body :content "text/html" :contains "</head>" { if body :contains "</head>" { All three result in matching value `' with key `</head>' => 0 finishing match with result: not matched RFC 5173 says: 5.1. Body Transform ":raw" The ":raw" transform matches against the entire undecoded body of a message as a single item. Which seems like exactly what I want. :content does not seem like what I want since it appears to only match the non HTML code content of the mime part. Eventually what I want to do is to alert some of the code in the HTML portion the email. Failing that, to remove the HTML mime part entirely, but that is less desirable. NB: I am not getting sieve.log errors the code seems to parse fine, it's just not matching how I expect. -- I'm the High King of Fillory. I took a blood test.

1 1

Filtering mails with sieve filters
by Odhiambo Washington 30 Oct '20

30 Oct '20

Hello good people, I have dovecot- 2.3.7.2 (Ubuntu Ubuntu 20.04.1 LTS) running fine. However, I have a hitch with mail filtering. Using SOGo as the webmail UI, I created a filter rule which resulted into the rule below: require ["fileinto"]; if allof (address :contains "from" "odhiambo") { fileinto "INBOX/Odhiambo"; } However, the test mail I sent did not end up the folder expected. lda.log contains this info: Oct 30 07:39:07 lda(wash@mydomain)<2415266><tSKSHhvDm1+i2iQA9H6eMA>: Info: sieve: msgid=<CAAdA2WNqXpG1qmOmKp_pJPS6iQrEPeS6=vM_= o8UnvR152x54Q(a)mail.gmail.com>: stored mail into mailbox 'INBOX' Oct 30 07:39:07 lda(wash@mydomain)<2415266><tSKSHhvDm1+i2iQA9H6eMA>: Info: sieve: Execution of script /var/spool/virtual/mydomain/wash/.dovecot.sieve failed, but implicit keep was successful (user logfile /var/spool/virtual/mydomain/wash/.dovecot.sieve.log may reveal additional details) And the .dovecot.sieve.log contains: sieve: info: started log at Oct 30 07:39:07. error: msgid=<CAAdA2WNqXpG1qmOmKp_pJPS6iQrEPeS6=vM_= o8UnvR152x54Q(a)mail.gmail.com>: failed to store into mailbox 'INBOX/Odhiambo': *Invalid mailbox name: Name must not have '/' characters.* What might be the problem here?? dovecot -n output is below: # 2.3.7.2 (3c910f64b): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.7.2 () # OS: Linux 5.4.0-29-generic x86_64 Ubuntu 20.04.1 LTS ext4 # Hostname: jp.mydomain auth_mechanisms = plain login auth_socket_path = /var/run/dovecot/auth-userdb debug_log_path = /var/log/dovecot/debug.log default_login_user = dovecot default_vsz_limit = 2 G disable_plaintext_auth = no first_valid_uid = 110 hostname = gw.mydomain info_log_path = /var/log/dovecot/info.log log_path = /var/log/dovecot/error.log mail_gid = Debian-exim mail_location = maildir:/var/spool/virtual/%d/%n/Maildir:INDEX=/var/spool/virtual/indexes/%d/%1n/%n mail_plugins = fts mail_privileged_group = mail mail_server_admin = postmaster@mydomain mail_uid = Debian-exim managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date index ihave duplicate mime foreverypart extracttext imapsieve vnd.dovecot.imapsieve namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { fts_autoindex = yes fts_autoindex_exclude = \Junk fts_autoindex_exclude2 = \Trash fts_autoindex_exclude3 = \Drafts fts_autoindex_exclude4 = \Spam fts_enforced = yes imapsieve_mailbox1_before = file:/usr/lib/dovecot/sieve/report-spam.sieve imapsieve_mailbox1_causes = COPY imapsieve_mailbox1_name = Spam imapsieve_mailbox2_before = file:/usr/lib/dovecot/sieve/report-ham.sieve imapsieve_mailbox2_causes = COPY imapsieve_mailbox2_from = Spam imapsieve_mailbox2_name = * plugin = fts managesieve sieve sieve = file:~/sieve;active=~/.dovecot.sieve sieve_execute_bin_dir = /usr/lib/dovecot/sieve-execute sieve_filter_bin_dir = /usr/lib/dovecot/sieve-filter sieve_global_extensions = +vnd.dovecot.pipe +vnd.dovecot.environment sieve_pipe_bin_dir = /usr/lib/dovecot/sieve sieve_plugins = sieve_imapsieve sieve_extprograms } postmaster_address = postmaster@mydomain protocols = imap lmtp sieve service auth { unix_listener auth-client { mode = 0600 user = Debian-exim } unix_listener auth-userdb { group = Debian-exim user = Debian-exim } } service stats { unix_listener stats-reader { user = Debian-exim } unix_listener stats-writer { user = Debian-exim } } service submission-login { inet_listener submission { port = 2587 } } ssl_cert = </etc/letsencrypt/live/mydomain/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 { info_log_path = /var/log/dovecot/lmtp.log log_path = /var/log/dovecot/lmtp-errors.log mail_plugins = fts sieve postmaster_address = postmaster@mydomain } protocol lda { info_log_path = /var/log/dovecot/lda.log log_path = /var/log/dovecot/lda-errors.log mail_plugins = fts sieve } -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)

2 3

doveadm replicator, what decides the timing on a full resync?
by Norman King 30 Oct '20

30 Oct '20

Hello. If running dovadm replicator status, i get something like the following. root@mail2:~# doveadm replicator status Queued 'sync' requests 0 Queued 'high' requests 0 Queued 'low' requests 0 Queued 'failed' requests 0 Queued 'full resync' requests 4 Waiting 'failed' requests 0 Total number of known users 1000 When would these full resyncs happen? Is it on a schedule? and if so where is said schedule configured? doveadm replicator dsync-status shows plenty of available sessions. Thanks. -- regards Norman King Compass Foundation sysadmin/tech support Phone, 856-974-5335 ext 221 support(a)compassfoundation.io <mailto:support@compassfoundation.io> Website <https://compassfoundation.io>

1 0

When is the Dovecot 2.3.12 release due?
by Sidsel Jensen 30 Oct '20

30 Oct '20

Hi We are very eager to test the zstd compression in the upcoming Dovecot 2.3.12 release - any pointer as to when that is expected to be released? Kind Regards, Sidsel

1 0

dovecot replicator not replicating automatically?
by Norman King 29 Oct '20

29 Oct '20

Hello all. I'm trying to set up the dovecot replicator plugin to automatically replicate mail between 2 servers. The servers are both using iredmail with dovecot as the imap server. I have everything working if i run dovecot replicator replicate \* all accounts update. But if an account receives a message it isn't automatically sent to the other system. The system config. OS, ubuntu 20.04 db, postgresql 12 dovecot info. root@mail:~# dovecot -n # 2.3.7.2 (3c910f64b): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.7.2 () # OS: Linux 5.3.18-2-pve x86_64 Ubuntu 20.04.1 LTS # Hostname: mail.daystar.io auth_master_user_separator = * auth_mechanisms = PLAIN LOGIN deliver_log_format = from=%{from}, envelope_sender=%{from_envelope}, subject=%{subject}, msgid=%m, size=%{size}, delivery_time=%{delivery_time}ms, %$ dict { acl = pgsql:/etc/dovecot/dovecot-share-folder.conf lastlogin = pgsql:/etc/dovecot/dovecot-last-login.conf quotadict = pgsql:/etc/dovecot/dovecot-used-quota.conf } doveadm_password = # hidden, use -P to show it doveadm_port = 10993 first_valid_uid = 2000 last_valid_uid = 2000 listen = * [::] login_log_format_elements = user=<%u> method=%m rip=%r lip=%l mpid=%e %c %k session=<%{session}> mail_gid = 2000 mail_location = maildir:%Lh/Maildir/:INDEX=%Lh/Maildir/ mail_plugins = quota mailbox_alias acl mail_log notify mail_uid = 2000 managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date index ihave duplicate mime foreverypart extracttext metric imap_command_finished { event_name = imap_command_finished } namespace { inbox = yes location = mailbox Archive { auto = no special_use = \Archive } mailbox Archives { auto = no special_use = \Archive } mailbox "Deleted Messages" { auto = no special_use = \Trash } mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk { auto = subscribe special_use = \Junk } mailbox "Junk E-mail" { auto = no special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox "Sent Items" { auto = no special_use = \Sent } mailbox "Sent Messages" { auto = no special_use = \Sent } mailbox Spam { auto = no special_use = \Junk } mailbox Trash { auto = subscribe special_use = \Trash } prefix = separator = / type = private } namespace { list = children location = maildir:%%Lh/Maildir/:INDEX=%%Lh/Maildir/Shared/%%Ld/%%Ln prefix = Shared/%%u/ separator = / subscriptions = yes type = shared } passdb { args = /etc/dovecot/dovecot-pgsql.conf driver = sql } passdb { args = /etc/dovecot/dovecot-master-users driver = passwd-file master = yes } plugin { acl = vfile acl_shared_dict = proxy::acl mail_log_events = delete undelete expunge copy mailbox_create mailbox_delete mailbox_rename mail_log_fields = uid box msgid size from subject flags mail_replica = tcp:10.2.2.113:10993 mailbox_alias_new = Sent Messages mailbox_alias_new2 = Sent Items mailbox_alias_old = Sent mailbox_alias_old2 = Sent quota = dict:user::proxy::quotadict quota_grace = 10%% quota_status_nouser = DUNNO quota_status_overquota = 552 5.2.2 Mailbox is full quota_status_success = DUNNO quota_warning = storage=100%% quota-warning 100 %u quota_warning2 = storage=95%% quota-warning 95 %u quota_warning3 = storage=90%% quota-warning 90 %u quota_warning4 = storage=85%% quota-warning 85 %u sieve = ~/sieve/dovecot.sieve sieve_before = /var/vmail/sieve/dovecot.sieve sieve_dir = ~/sieve sieve_global_dir = /var/vmail/sieve sieve_max_redirects = 30 sieve_vacation_send_from_recipient = yes } protocols = pop3 imap sieve lmtp service anvil { client_limit = 7000 } service auth { client_limit = 7000 unix_listener /var/spool/postfix/private/dovecot-auth { group = postfix mode = 0666 user = postfix } unix_listener auth-master { group = vmail mode = 0666 user = vmail } unix_listener auth-userdb { group = vmail mode = 0660 user = vmail } } service dict { unix_listener dict { group = vmail mode = 0660 user = vmail } } service doveadm { inet_listener { port = 10993 } } service imap-login { process_limit = 6144 service_count = 1 } service imap { process_limit = 6144 } service lmtp { executable = lmtp -L inet_listener lmtp { address = 127.0.0.1 port = 24 } process_min_avail = 5 unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } user = vmail } service managesieve-login { inet_listener sieve { address = 127.0.0.1 port = 4190 } } service pop3-login { service_count = 1 } service quota-status { client_limit = 1 executable = quota-status -p postfix inet_listener { address = 127.0.0.1 port = 12340 } } service quota-warning { executable = script /usr/local/bin/dovecot-quota-warning.sh unix_listener quota-warning { group = vmail mode = 0660 user = vmail } } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { mode = 0666 } } service stats { client_limit = 5000 fifo_listener stats-mail { mode = 0644 user = vmail } inet_listener { address = 127.0.0.1 port = 24242 } unix_listener stats-writer { group = vmail mode = 0660 user = vmail } } ssl = required ssl_ca = </etc/ssl/certs/star.daystar.io.crt ssl_cert = </etc/ssl/certs/star.daystar.io-chained.crt ssl_cipher_list = ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:AES:CAMELLIA:DES-CBC3-SHA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!MD5:!PSK:!aECDH:!EDH-DSS-DES-CBC3-SHA:!EDH-RSA-DES-CBC3-SHA:!KRB5-DES-CBC3-SHA ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it syslog_facility = local5 userdb { args = /etc/dovecot/dovecot-pgsql.conf driver = sql } protocol lda { lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes mail_plugins = quota mailbox_alias acl mail_log notify sieve } protocol lmtp { lmtp_save_to_detail_mailbox = yes mail_plugins = quota mailbox_alias acl mail_log notify sieve recipient_delimiter = + } protocol imap { imap_client_workarounds = tb-extra-mailbox-sep mail_max_userip_connections = 100 mail_plugins = quota mailbox_alias acl mail_log notify imap_quota imap_acl } protocol pop3 { mail_max_userip_connections = 50 mail_plugins = quota mailbox_alias acl mail_log notify pop3_client_workarounds = outlook-no-nuls oe-ns-eoh pop3_uidl_format = %08Xu%08Xv } What's wrong with this picture? Thanks. -- regards Norman King Compass Foundation sysadmin/tech support Phone, 856-974-5335 ext 221 support(a)compassfoundation.io <mailto:support@compassfoundation.io> Website <https://compassfoundation.io>

2 3

Re: dovecot replicator not replicating automatically?
by Aki Tuomi 29 Oct '20

29 Oct '20

Hi! In order for replication to trigger, you need - load the replication plugin - use dovecot-lda / lmtp to deliver mail If you have done these both, please provide doveconf -n and output of mail_debug=yes logs. Aki > On 29/10/2020 19:10 Norman King <norman(a)compassfoundation.io> wrote: > > > Thanks for that tip. > I loaded the replication plugin but still have the same issue. Anything else i can check? > > > > > regards > Norman King > Compass Foundation sysadmin/tech support > Phone, 856-974-5335 ext 221 > support(a)compassfoundation.io > Website (https://compassfoundation.io) > On 10/29/2020 12:17 PM, Sami Ketola wrote: > > > > > > > > > > > > On 29. Oct 2020, at 17.24, Norman King <norman(a)compassfoundation.io> wrote: > > > > > > > > > Hello all. > > > I'm trying to set up the dovecot replicator plugin to automatically replicate mail between 2 servers. > > > The servers are both using iredmail with dovecot as the imap server. > > > > > > I have everything working if i run dovecot replicator replicate \* all accounts update. But if an account receives a message it isn't automatically sent to the other system. > > > > > > > > > The system config. > > > > > > > > > mail_plugins = quota mailbox_alias acl mail_log notify > > > > > > > > > > > > > your mail_plugins does not even load replication plugin. > > > > > > Sami > > > >

1 0

Re: Support of INDEXPVT in Dovecot 2.3 with replication
by Aki Tuomi 29 Oct '20

29 Oct '20

At the moment the correct way to use shared folders in a replication pair is to access them with imapc from the other pair. Aki > On 29/10/2020 14:43 Ralf Becker <rb(a)egroupware.org> wrote: > > > In reference to an earlier mail from me, I'd like to ask: > > Have there been any changes in regard to INDEXPVT and replication or are > there any plans in that direction? > > Thanks :) > > Ralf > > > On 03.08.20 at 11:20 Ralf Becker wrote: > > So far the only thing we noticed: private seen flags on shared user > > folders (which were never supported for replication!) seem to be not > > functioning any more in 2.3. Not functioning means, if they are > > configured you can not set a mail to seen in a shared user folder. After > > removing this configuration: > > > > location = mdbox:%%h/mdbox:INDEXPVT=~/shared/%%u --> mdbox:%%h/mdbox > > > > seen flags behave as expected / are identical now if you access the > > mailbox direct or via the shared user folder, and the are identical on > > both backends. > > > > Ralf > > -- > Ralf Becker > EGroupware GmbH [www.egroupware.org] > Handelsregister HRB Kaiserslautern 3587 > Geschäftsführer Birgit und Ralf Becker > Leibnizstr. 17, 67663 Kaiserslautern, Germany > Telefon +49 631 31657-0

2 1

Support of INDEXPVT in Dovecot 2.3 with replication
by Ralf Becker 29 Oct '20

29 Oct '20

In reference to an earlier mail from me, I'd like to ask: Have there been any changes in regard to INDEXPVT and replication or are there any plans in that direction? Thanks :) Ralf On 03.08.20 at 11:20 Ralf Becker wrote: > So far the only thing we noticed: private seen flags on shared user > folders (which were never supported for replication!) seem to be not > functioning any more in 2.3. Not functioning means, if they are > configured you can not set a mail to seen in a shared user folder. After > removing this configuration: > > location = mdbox:%%h/mdbox:INDEXPVT=~/shared/%%u --> mdbox:%%h/mdbox > > seen flags behave as expected / are identical now if you access the > mailbox direct or via the shared user folder, and the are identical on > both backends. > > Ralf -- Ralf Becker EGroupware GmbH [www.egroupware.org] Handelsregister HRB Kaiserslautern 3587 Geschäftsführer Birgit und Ralf Becker Leibnizstr. 17, 67663 Kaiserslautern, Germany Telefon +49 631 31657-0

1 0

dovecot quota-warning detection mail
by 森川　孝司 29 Oct '20

29 Oct '20

Hi, all. we use quota-warning emails to notify you of quotas. In rare cases, the email address has changed to the logged-in user. (Because the address of %u is passed as the logged-in user.) So I couldn’t send the email with “Recipient address rejected: User unknown in local recipient table”. Why does my email address change to a logged-in user? %u of "quota_warning = storage = 95 %% quota-warning 95% u" The output is the logged-in user. By Morikawa

3 16

Directors and LMTP: mailAlternateAddress of same user
by Paterakis E. Ioannis 28 Oct '20

28 Oct '20

Good evening everyone, I'd like to paste a problem i experience the last days with a mail cluster system based on three dovecot servers and two directors in front of them. The Directors are proxying the auth requests to the dovecot servers below (LDAP). The protocols i use are imap/managesieve/lmtp. The setup works as intented, exept one detail. There are a lot of users that happen to have mailAlternateAddress attriutes with different e-mail addresses. The problem is that when a mail arrives to the lmtp of the directors, and the recipient is one of the mailalternateAddresses the same user has, director/lmtp doesn't recognise the real user of that e-mail address, and routes the e-mail to a different dovecot server than the real user is logged in, resulting in a corrupted .index.cache file. I've searched around for a solution to this, and figured out that a special userdb {} section in the protocol lmtp {} section, with driver = ldap etc etc so that i 'd be able to "show" the correct user to the lmtp might work, but strangely that userdb {} setting looks like being ignored by lmtp. Has any of you guys have an idea how will i be able to solve that issue because i get thousands of corrupted .index.cache files every day.... Thank you very much in advance, Ioannis

2 2

Looking for a guide to collect all e-mail from the ISP mail server
by R. Diez 28 Oct '20

28 Oct '20

Hi all: I am evaluating mail server solutions for a small business. The trouble is, I am only a part-time admin and a newbie to mail servers. Most guides I have seen are rather unrealistic: they encourage you to expose your e-mail server to the Internet, and hope that you have the resources to keep it patched up. I would rather have an internal mail server that collects e-mails from a standard ISP mail server. It is like the old "POP3 Connector" that came with Microsoft Exchange. Sometimes, there is a mailbox per user on the ISP, and a corresponding one on the local server. Other times, there is a single "catch all" or "multidrop" mailbox on the ISP. Users can still access their internal mailboxes from outside through an OpenVPN connection. The goal is that only VPN, and perhaps SSH, are accessible from the outside. We do not need to arrange any special SMTP configuration with the ISP either. This kind of mail server setup is rather different to the standard configuration. You do not normally need you own antivirus and spam filter, and you do not need to configure SSL certificates, MX or SPF DNS records. Most ISP handle that correctly and economically. Internal e-mail does not leave your LAN, and your internal SMTP server is just a relay for the external ISP SMTP server. Furthermore, most guides do not explain how to setup an autoresponder ("I am on holiday until xxx") so that users can enable theirs with the mouse. Editing configuration files over SSH is not really an option for normal users. This detail is important because it could be the only thing I need above standard e-mail. Further groupware features can be seen as nice but ultimately unnecessary luxury, and a basic shared calendar can be accomplished with a separate server like https://radicale.org/ and a calendar client like one built into Thunderbird. Hopefully, that is all I would need for a small business. Can anyone point me to the kind of guide I need? Failing that, I would need information or examples about using fetchmail, getmail or similar software with Dovecot. Good or bad experiences from you guys would also help. Each of those tools has a detailed man page, but there are many options and ways with different advantages and disadvantages. I would need a simpler guide to get started. I am aware that there are pre-packaged mail server solutions that would perhaps bring an easy-to-use autoresponder, but I haven't seen one yet that where you could tick a box like "this server is only internal and collects mail from the ISP server" during installation. Nor have I seen instructions about reconfiguring the mail server for my ISP mail scenario. I am prepared to learn more and write my own Perl scripts and/or installation guide, but it would be stupid to waste time if something easy already exists. After all, the setup I am describing (external ISP mail server + internal mail server) is not so weird. Thanks in advance, rdiez

21 82