- dovecot - dovecot.org

dsync fails for existing user: "Error: Failed to initialize user: Namespace '': Mailbox list driver imapc: missing imapc_password" ?
by PGNet Dev 27 Jul '20

27 Jul '20

i'm attempting to dsync from a remote/other IMAP store to my current/new dovecot instance testing remote's IMAP access from the local/dovecot box, i can successfully login openssl s_client \ -crlf \ -4 \ -showcerts \ -bind 10.0.1.10 \ -connect remote-imap.example.com:993 \ -cert /sec/vmail/client.EC.crt.pem \ -key /sec/vmail/client.EC.key.pem \ -CAfile /sec/vmail/CA.crt.pem a1 login "testuser(a)example.net" "my!secret" a1 OK [CAPABILITY IMAP4rev1 ACL BINARY CATENATE CHILDREN CONDSTORE ENABLE ESEARCH ESORT I18NLEVEL=1 ID IDLE LIST-EXTENDED LIST-STATUS LITERAL+ LOGIN-REFERRALS MULTIAPPEND NAMESPACE QRESYNC QUOTA RIGHTS=ektx SASL-IR SEARCHRES SORT THREAD=ORDEREDSUBJECT UIDPLUS UNSELECT WITHIN XLIST] LOGIN completed atm, my dovecot config includes the following, matching the ssl config above, ssl_client_ca_file = /sec/vmail/CA.crt.pem ssl_client_require_valid_cert = yes ssl_client_cert = < /sec/vmail/client.EC.crt.pem ssl_client_key = < /sec/vmail/client.EC.key.pem protocol doveadm { mail_plugins = virtual } imapc_host = remote-imap.example.com imapc_features = rfc822.size imapc_features = $imapc_features fetch-headers mail_prefetch_count = 20 imapc_port = 993 imapc_ssl = imaps imapc_ssl_verify = no dsync_features = empty-header-workaround dsync_commit_msgs_interval = 100 # default in v2.2.30+ dsync_hashed_headers = Date Message-ID and grep users.conf /etc/dovecot/conf.d/* /etc/dovecot/conf.d/10-auth.conf: args = scheme=ARGON2ID /etc/dovecot/sec/users.conf _USER="testuser(a)example.net" _PASS="my!secret" _PASS_ENC=$( doveadm pw -s ARGON2ID -p ${_PASS} ) echo "${_USER}:${_PASS_ENC}::::" >> /etc/dovecot/sec/users.conf grep testuser(a)example.net /etc/dovecot/sec/users.conf testuser@example.net:{ARGON2ID}$argon2id$v=19$m=65536,t=3,p=1$...qY:::: on exec doveadm -D -o mail_fsync=never backup -R -u "testuser(a)example.net" imapc: returns/fails, Debug: Loading modules from directory: /usr/lib64/dovecot Debug: Module loaded: /usr/lib64/dovecot/lib20_virtual_plugin.so Debug: Loading modules from directory: /usr/lib64/dovecot/doveadm Debug: Skipping module doveadm_acl_plugin, because dlopen() failed: /usr/lib64/dovecot/doveadm/lib10_doveadm_acl_plugin.so: undefined symbol: acl_user_module (this is usually intentional, so just ignore this message) Debug: Skipping module doveadm_expire_plugin, because dlopen() failed: /usr/lib64/dovecot/doveadm/lib10_doveadm_expire_plugin.so: undefined symbol: expire_set_deinit (this is usually intentional, so just ignore this message) Debug: Skipping module doveadm_quota_plugin, because dlopen() failed: /usr/lib64/dovecot/doveadm/lib10_doveadm_quota_plugin.so: undefined symbol: quota_user_module (this is usually intentional, so just ignore this message) Debug: Module loaded: /usr/lib64/dovecot/doveadm/lib10_doveadm_sieve_plugin.so Debug: Skipping module doveadm_fts_lucene_plugin, because dlopen() failed: /usr/lib64/dovecot/doveadm/lib20_doveadm_fts_lucene_plugin.so: undefined symbol: lucene_index_iter_deinit (this is usually intentional, so just ignore this message) Debug: Skipping module doveadm_fts_plugin, because dlopen() failed: /usr/lib64/dovecot/doveadm/lib20_doveadm_fts_plugin.so: undefined symbol: fts_user_get_language_list (this is usually intentional, so just ignore this message) Debug: Skipping module doveadm_mail_crypt_plugin, because dlopen() failed: /usr/lib64/dovecot/doveadm/libdoveadm_mail_crypt_plugin.so: undefined symbol: mail_crypt_box_get_pvt_digests (this is usually intentional, so just ignore this message) doveadm(testuser(a)example.net)<>: Debug: auth-master: userdb lookup(testuser(a)example.net): Started userdb lookup doveadm(testuser(a)example.net)<>: Debug: auth-master: conn unix:/run/dovecot/auth-userdb: Connecting doveadm(testuser(a)example.net)<>: Debug: auth-master: conn unix:/run/dovecot/auth-userdb (pid=10517,uid=0): Client connected (fd=10) doveadm(testuser(a)example.net)<>: Debug: auth-master: userdb lookup(testuser(a)example.net): auth USER input: testuser(a)example.net uid=5000 gid=5000 home=/data/vmail/example.net/testuser/Maildir doveadm(testuser(a)example.net)<>: Debug: auth-master: userdb lookup(testuser(a)example.net): Finished userdb lookup (username=testuser(a)example.net uid=5000 gid=5000 home=/data/vmail/example.net/testuser/Maildir) doveadm(testuser(a)example.net): Debug: Effective uid=5000, gid=5000, home=/data/vmail/example.net/testuser/Maildir doveadm(testuser(a)example.net): Debug: Namespace inbox: type=private, prefix=, sep=/, inbox=yes, hidden=no, list=yes, subscriptions=yes location=maildir:/data/vmail/example.net/testuser/Maildir:CONTROL=/data/vma… doveadm(testuser(a)example.net): Debug: fs: root=/data/vmail/example.net/testuser/Maildir, index=/var/vmail-index/example.net/testuser, indexpvt=, control=/data/vmail/example.net/testuser/_control, inbox=/data/vmail/example.net/testuser/Maildir, alt= doveadm(testuser(a)example.net): Debug: Namespace shared: type=shared, prefix=shared/%u/, sep=/, inbox=no, hidden=no, list=children, subscriptions=yes location=maildir:/data/vmail/example.net/testuser/Maildir:INDEXPVT=/var/vma… doveadm(testuser(a)example.net): Debug: shared: root=/run/dovecot/, index=, indexpvt=, control=, inbox=, alt= doveadm(testuser(a)example.net): Debug: Namespace virtual: type=private, prefix=virtual/, sep=/, inbox=no, hidden=no, list=yes, subscriptions=yes location=virtual:/data/vmail/virtual:INDEX=MEMORY doveadm(testuser(a)example.net): Debug: fs: root=/data/vmail/virtual, index=, indexpvt=, control=, inbox=, alt= doveadm(testuser(a)example.net): Debug: brain M: Namespace has location maildir:/data/vmail/example.net/testuser/Maildir:CONTROL=/data/vmail/exampl… doveadm(testuser(a)example.net): Debug: Namespace : Using permissions from /data/vmail/example.net/testuser/Maildir: mode=0700 gid=default dsync(testuser(a)example.net): Debug: Effective uid=5000, gid=5000, home=/data/vmail/example.net/testuser/Maildir dsync(testuser(a)example.net): Debug: Namespace inbox: type=private, prefix=, sep=/, inbox=yes, hidden=no, list=yes, subscriptions=yes location=imapc: dsync(testuser(a)example.net): Error: Failed to initialize user: Namespace '': Mailbox list driver imapc: missing imapc_password dsync(testuser(a)example.net): Debug: auth-master: conn unix:/run/dovecot/auth-userdb (pid=10517,uid=0): Disconnected: Connection closed (fd=10) what needs to change in this^ config so that 'dsync' successfully gets/uses the "missing imapc_password" from the existing users.conf file?

2 2

Crash during "doveadm import"
by Ralf Hildebrandt 27 Jul '20

27 Jul '20

Today I was looking for some spam and issued this command: ========================================================== doveadm import -u restore(a)backup.invalid mdbox:/home/copymail2/mdbox INBOX header Reply-To bixrs.com Then I immediately got a crash: doveadm(restore(a)backup.invalid): Panic: file mail-index-util.c: line 10 (mail_index_uint32_to_offset): assertion failed: (offset < 0x40000000) doveadm(restore(a)backup.invalid): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(backtrace_append+0x42) [0x7f757c0edf32] -> /usr/lib/dovecot/libdovecot.so.0(backtrace_get+0x1e) [0x7f757c0ee04e] -> /usr/lib/dovecot/libdovecot.so.0(+0xe692e) [0x7f757c0f892e] -> /usr/lib/dovecot/libdovecot.so.0(+0xe6971) [0x7f757c0f8971] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f757c05321b] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_index_uint32_to_offset+0x70)[0x7f757c4a43c0] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_cache_add+0x83b)[0x7f757c48cf4b] -> /usr/lib/dovecot/libdovecot-storage.so.0(index_mail_parse_header+0x449)[0x7f757c46f5f9] -> /usr/lib/dovecot/libdovecot.so.0(+0xbf2c3) [0x7f757c0d12c3] -> /usr/lib/dovecot/libdovecot.so.0(i_stream_read_memarea+0x74)[0x7f757c105c94] -> /usr/lib/dovecot/libdovecot.so.0(i_stream_read+0x29) [0x7f757c105fc9]-> /usr/lib/dovecot/libdovecot.so.0(i_stream_read_data+0x3d) [0x7f757c10693d] -> /usr/lib/dovecot/libdovecot.so.0(message_parse_header_next+0x68) [0x7f757c0d79c8] -> /usr/lib/dovecot/libdovecot.so.0(message_parse_header+0x4f) [0x7f757c0d839f] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xc9741) [0x7f757c479741] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xca9f4) [0x7f757c47a9f4] -> /usr/lib/dovecot/libdovecot-storage.so.0(index_storage_search_next_nonblock+0x10d)[0x7f757c47b1cd] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_search_next_nonblock+0x22)[0x7f757c3fd6e2] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_search_next+0x3d)[0x7f757c3fd74d] -> doveadm(+0x31a33) [0x559bc9c63a33] -> doveadm(+0x2c518) [0x559bc9c5e518] -> doveadm(+0x2d256) [0x559bc9c5f256] -> doveadm(doveadm_cmd_ver2_to_mail_cmd_wrapper+0x20e) [0x559bc9c600ce]-> doveadm(doveadm_cmd_run_ver2+0x548) [0x559bc9c70fa8] -> doveadm(doveadm_cmd_try_run_ver2+0x37) [0x559bc9c70ff7] -> doveadm(main+0x1d1) [0x559bc9c4e641] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7) [0x7f757b653b97] -> doveadm(_start+0x2a) [0x559bc9c4eb3a] Command terminated by signal 6 Running it in gdb gives me: # gdb doveadm (gdb) set args import -u restore(a)backup.invalid mdbox:/home/copymail2/mdbox mailbox INBOX header Reply-To bixrs.com (gdb) run Starting program: /usr/bin/doveadm import -u restore(a)backup.invalid mdbox:/home/copymail2/mdbox INBOX header Reply-To bixrs.com (gdb) bt #0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 #1 0x00007ffff68ec8b1 in __GI_abort () at abort.c:79 #2 0x00007ffff73728e1 in default_fatal_finish (status=0, type=LOG_TYPE_PANIC) at failures.c:459 #3 fatal_handler_real (ctx=<optimized out>, format=<optimized out>, args=<optimized out>) at failures.c:471 #4 0x00007ffff7372971 in default_fatal_handler (ctx=<optimized out>, format=<optimized out>, args=<optimized out>) at failures.c:479 #5 0x00007ffff72cd21b in i_panic (format=format@entry=0x7ffff772dd60 "file %s: line %d (%s): assertion failed: (%s)") at failures.c:523 #6 0x00007ffff771e3c0 in mail_index_uint32_to_offset (offset=<optimized out>) at mail-index-util.c:10 #7 0x00007ffff7706f4b in mail_cache_header_fields_write (ctx=0x55555585b690, buffer=<optimized out>, buffer=<optimized out>) at mail-cache-transaction.c:609 #8 mail_cache_header_add_field (field_idx=15, ctx=0x55555585b690) at mail-cache-transaction.c:690 #9 mail_cache_add (ctx=0x55555585b690, seq=1, field_idx=field_idx@entry=15, data=0x7ffff773b736, data_size=0) at mail-cache-transaction.c:739 #10 0x00007ffff76ebc34 in index_mail_cache_add_idx (mail=mail@entry=0x55555586e8d8, field_idx=field_idx@entry=15, data=data@entry=0x7ffff773b736, data_size=data_size@entry=0) at index-mail.c:631 #11 0x00007ffff76e95f9 in index_mail_parse_header_finish (mail=<optimized out>) at index-mail-headers.c:132 #12 index_mail_parse_header (part=<optimized out>, hdr=<optimized out>, mail=<optimized out>) at index-mail-headers.c:313 #13 0x00007ffff734b2c3 in read_header (mstream=0x555555879530) at istream-header-filter.c:356 #14 i_stream_header_filter_read (stream=0x555555879530) at istream-header-filter.c:446 #15 0x00007ffff737fc94 in i_stream_read_memarea (stream=stream@entry=0x5555558795b0) at istream.c:313 #16 0x00007ffff737ffc9 in i_stream_read (stream=stream@entry=0x5555558795b0) at istream.c:271 #17 0x00007ffff738093d in i_stream_read_data (stream=0x5555558795b0, data_r=data_r@entry=0x7fffffffdc18, size_r=size_r@entry=0x7fffffffdc20, threshold=threshold@entry=1) at istream.c:745 #18 0x00007ffff73519c8 in i_stream_read_bytes (wanted=2, size_r=0x7fffffffdc20, data_r=0x7fffffffdc18, stream=<optimized out>) at ../../src/lib/istream.h:217 #19 message_parse_header_next (ctx=0x55555582e580, hdr_r=hdr_r@entry=0x7fffffffdc80) at message-header-parser.c:85 #20 0x00007ffff735239f in message_parse_header (input=<optimized out>, hdr_size=hdr_size@entry=0x0, flags=flags@entry=MESSAGE_HEADER_PARSER_FLAG_CLEAN_ONELINE, callback=callback@entry=0x7ffff76f2cb0 <search_header>, context=context@entry=0x7fffffffdcf0) at message-header-parser.c:392 #21 0x00007ffff76f3741 in search_arg_match_text (ctx=0x55555585bad0, args=0x5555558216d0) at index-search.c:759 #22 search_match_once (ctx=0x55555585bad0) at index-search.c:1398 #23 0x00007ffff76f49f4 in search_match_next (ctx=0x55555585bad0) at index-search.c:1505 #24 search_more_with_mail (mail=<optimized out>, ctx=0x55555585bad0) at index-search.c:1621 #25 search_more_with_prefetching (mail_r=<optimized out>, ctx=<optimized out>) at index-search.c:1703 #26 search_more (ctx=ctx@entry=0x55555585bad0, mail_r=mail_r@entry=0x7fffffffde20) at index-search.c:1777 #27 0x00007ffff76f51cd in index_storage_search_next_nonblock (_ctx=0x55555585bad0, mail_r=0x7fffffffdef0, tryagain_r=0x7fffffffde87) at index-search.c:1805 #28 0x00007ffff76776e2 in mailbox_search_next_nonblock (ctx=0x55555585bad0, mail_r=0x7fffffffdef0, tryagain_r=<optimized out>) at mail-storage.c:2307 #29 0x00007ffff767774d in mailbox_search_next (ctx=0x55555585bad0, mail_r=mail_r@entry=0x7fffffffdef0) at mail-storage.c:2292 #30 0x0000555555586c02 in doveadm_mail_iter_next (iter=<optimized out>, mail_r=mail_r@entry=0x7fffffffdef0) at doveadm-mail-iter.c:161 #31 0x0000555555585a33 in cmd_import_box (search_args=<optimized out>, info=0x55555584f820, dest_user=<optimized out>, ctx=0x55555581fda8) at doveadm-mail-import.c:143 #32 cmd_import_run (_ctx=0x55555581fda8, user=0x5555558374a8) at doveadm-mail-import.c:203 #33 0x0000555555580518 in doveadm_mail_next_user (ctx=ctx@entry=0x55555581fda8, error_r=error_r@entry=0x7fffffffe0d0) at doveadm-mail.c:462 #34 0x000055555558116e in doveadm_mail_single_user (ctx=ctx@entry=0x55555581fda8, error_r=error_r@entry=0x7fffffffe0d0) at doveadm-mail.c:492 #35 0x0000555555581256 in doveadm_mail_cmd_exec (ctx=ctx@entry=0x55555581fda8, wildcard_user=wildcard_user@entry=0x0) at doveadm-mail.c:653 #36 0x00005555555820ce in doveadm_cmd_ver2_to_mail_cmd_wrapper (cctx=<optimized out>) at doveadm-mail.c:1149 #37 0x0000555555592fa8 in doveadm_cmd_run_ver2 (argc=8, argv=0x5555557f6bb8, cctx=cctx@entry=0x7fffffffe2c0) at doveadm-cmd.c:575 #38 0x0000555555592ff7 in doveadm_cmd_try_run_ver2 (cmd_name=<optimized out>, argc=<optimized out>, argv=<optimized out>, cctx=0x7fffffffe2c0) at doveadm-cmd.c:497 #39 0x0000555555570641 in main (argc=<optimized out>, argv=<optimized out>) at doveadm.c:395 -- 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

1 2

Problem with change file format in maildir
by turix13＠gmail.com 27 Jul '20

27 Jul '20

hi, i have a problem with a dovecot 2.2.36 (1f10bfa63) server, using maildir, some mails change the file format, the flag is modified and they appear again in the inbox as unread. ex. 1548753605.56008.server-mail,S=5935:2 (origin) 1548~RZ!.ESS:2 (modified) Could someone give me some light? thx. br. -- Sent from: http://dovecot.2317879.n4.nabble.com/

1 0

Multiple authentication instances (GSSAPI _or_ Client Certificate)
by Joakim Ekblad 27 Jul '20

27 Jul '20

Hi there, I am trying to make a paranoid IMAPS/Submission server. I'm running Ubuntu 20.04 with Dovecot 2.3.7.2 (3c910f64b). I mostly use my mail-server from the LAN/Realm where I have GSSAPI working well for both IMAPS and Submission and most other services But... I would like to be able to configure Dovecot to require mobile ("external") devices to authenticate using client certificates (with different SSL cert superset) instead of 'plain' fallback (if there is no valid Kerberos token/infrastructure). I have one SSL-certificate for the LAN-solution, but would like to have my self-signed PKI-stuff for the other solution where client certificates are used to authenticate. So. First of all. Is this a possible scenario? I'm struggling with the configuration and it seems Dovecot-configs are not accepting different authentication methods for different local listeners for different IPs etc. The only way i can think of getting this up and running is having two separate Dovecot instances (somehow) listening to different ports or even on different server hosts. What would be neat is if it would be possible to have like: auth_mechanisms = gssapi ssl :D But i know that's not how things work. I hope I'm not too unspecific. Is there any other clever ideas on how to get this use-case configured with the current version of Dovecot? I am thinking i _might_ be able to do something with stunnel to terminate the PKI authentication and still require normal plain user authentication with login/pass to get the extra security. But it does not feel clean enough. All good ideas are welcome! Stay safe! Kind regards, Joakim Ekblad

1 0

To field was not correct indexed by FTS
by TACHIBANA Masashi 27 Jul '20

27 Jul '20

Hi, This To field was not correct indexed by FTS. To: Yamada Taro <yamada(a)example.com>,=?UTF-8?B?dXNlcjJAZXhhbXBsZS5jb20=?= <user2(a)example.com>, =?UTF-8?B?dXNlcjNAZXhhbXBsZS5jb20=?= <user3(a)example.com>, user4 desu <user4(a)example.com> --> Yamada Taro <yamada(a)example.com> , user2(a)example.com And follow was correct indexed by FTS To: Yamada Taro <yamada(a)example.com>,"user2(a)example.com" <user2(a)example.com>, "user3(a)example.com" <user3(a)example.com>, user4 desu <user4(a)example.com> --> Yamada Taro <yamada(a)example.com> , user2(a)example.com <user2(a)example.com> , user3(a)example.com <user3(a)example.com> , user4 desu <user4(a)example.com> Any hint? -- TACHIBANA Masashi QUALITIA CO., LTD. mailto:tachibana@qualitia.co.jp 株式会社クオリティア https://www.qualitia.co.jp/

2 6

Dovecot serving incorrect certificate
by Antonio Leding 26 Jul '20

26 Jul '20

Hello all, I have a Dovecot (v2.3.10.1) + Postfix (v3.5.3) both cfg; d to use TLS however each using different certificates. In addition, I have cfg’d a DNS CNAME that points to the server A record. For example, mail.example.com (A) —> 1.2.3.4 alias.example.con (CNAME) —> mail.example.com When setting up a new account in Apple Mail, if I specify the server name as the “Host Name” (i.e. mil server), the cert that is cfg’d in Dovecot is received and everything works fine. However, if I instead use the alias CNAME as the “Host Name”, then the cert for Postfix is sent to the client. This causes issues because I do not have the CNAME in the SAN of the Postfix certificate. I doubt this is a bug because I have to think others have employed a similar configuration so I must be missing something here — any thoughts? Thanks in advance...

2 4

(re-) dsync: INBOX Can't be deleted
by PGNet Dev 24 Jul '20

24 Jul '20

with dovecot --version 2.3.10.1 (a3d0e1171) exec of doveadm -v -o mail_fsync=never backup -R -f -u testuser(a)example.com imapc: currently fails, here, with Error: Mailbox INBOX sync: mailbox_delete failed: INBOX can't be deleted checking lists, this has been seen before @ https://dovecot.org/pipermail/dovecot/2016-January/102988.html On 24 Jan 2016, at 18:47, Timo Sirainen <tss at iki.fi> wrote: > During Migration with dsync I get these Errors: > Error: Mailbox INBOX sync: mailbox_delete failed: INBOX can't be deleted > Is there a way to work around these Errors ? With "doveadm backup" you have gotten into such a state that the INBOX needs to be deleted and recreated to preserve it exactly as it's in source. But you're using Maildir format, which doesn't allow deleting INBOX. So possibilities: a) Don't use Maildir format b) Delete the entire Maildir manually with rm -rf and the next doveadm backup should work (if not then something strange is going on) per "b)", i explicitly 'rm' the Maildir rm -rf /data/vmail/example.com/testuser/Maildir tree /data/vmail/example.com/testuser/Maildir /data/vmail/example.com/testuser/Maildir [error opening dir] on re-exec, the backup still fails dsync(testuser(a)example.com): Info: imapc(mx.example.com:993): Connected to 10.1.0.20:993 (local 10.1.0.114:42926) dsync(testuser(a)example.com): Error: Mailbox INBOX sync: mailbox_delete failed: INBOX can't be deleted. where tree /data/vmail/example.com/testuser/Maildir /data/vmail/example.com/testuser/Maildir ├── cur ├── new ├── sieve │ └── tmp └── tmp and log detail, Debug: Loading modules from directory: /usr/lib64/dovecot Debug: Module loaded: /usr/lib64/dovecot/lib20_virtual_plugin.so Debug: Loading modules from directory: /usr/lib64/dovecot/doveadm doveadm(testuser(a)example.com)<>: Debug: auth-master: userdb lookup(testuser(a)example.com): Started userdb lookup doveadm(testuser(a)example.com)<>: Debug: auth-master: conn unix:/run/dovecot/auth-userdb: Connecting doveadm(testuser(a)example.com)<>: Debug: auth-master: conn unix:/run/dovecot/auth-userdb (pid=25419,uid=0): Client connected (fd=10) doveadm(testuser(a)example.com)<>: Debug: auth-master: userdb lookup(testuser(a)example.com): auth USER input: testuser(a)example.com uid=5000 gid=5000 home=/data/vmail/example.com/testuser/Maildir doveadm(testuser(a)example.com)<>: Debug: auth-master: userdb lookup(testuser(a)example.com): Finished userdb lookup (username=testuser(a)example.com uid=5000 gid=5000 home=/data/vmail/example.com/testuser/Maildir) doveadm(testuser(a)example.com): Debug: Effective uid=5000, gid=5000, home=/data/vmail/example.com/testuser/Maildir doveadm(testuser(a)example.com): Debug: Namespace inbox: type=private, prefix=, sep=/, inbox=yes, hidden=no, list=yes, subscriptions=yes location=maildir:/data/vmail/example.com/testuser/Maildir:CONTROL=/data/vma… doveadm(testuser(a)example.com): Debug: fs: root=/data/vmail/example.com/testuser/Maildir, index=/var/vmail-index/example.com/testuser, indexpvt=, control=/data/vmail/example.com/testuser/_control, inbox=/data/vmail/example.com/testuser/Maildir, alt= doveadm(testuser(a)example.com): Debug: Namespace shared: type=shared, prefix=shared/%u/, sep=/, inbox=no, hidden=no, list=children, subscriptions=yes location=maildir:/data/vmail/example.com/testuser/Maildir:INDEXPVT=/var/vma… doveadm(testuser(a)example.com): Debug: shared: root=/run/dovecot/, index=, indexpvt=, control=, inbox=, alt= doveadm(testuser(a)example.com): Debug: Namespace virtual: type=private, prefix=virtual/, sep=/, inbox=no, hidden=no, list=yes, subscriptions=yes location=virtual:/data/vmail/virtual:INDEX=MEMORY doveadm(testuser(a)example.com): Debug: fs: root=/data/vmail/virtual, index=, indexpvt=, control=, inbox=, alt= doveadm(testuser(a)example.com): Debug: brain M: Namespace has location maildir:/data/vmail/example.com/testuser/Maildir:CONTROL=/data/vmail/exampl… doveadm(testuser(a)example.com): Debug: Namespace : Using permissions from /data/vmail/example.com/testuser/Maildir: mode=0700 gid=default dsync(testuser(a)example.com): Debug: Effective uid=5000, gid=5000, home=/data/vmail/example.com/testuser/Maildir dsync(testuser(a)example.com): Debug: Namespace inbox: type=private, prefix=, sep=/, inbox=yes, hidden=no, list=yes, subscriptions=yes location=imapc: dsync(testuser(a)example.com): Debug: imapc(mx.example.com:993): Created new connection dsync(testuser(a)example.com): Debug: imapc(mx.example.com:993): Looking up IP address (reconnect_ok=true, last_connect=1595599741) dsync(testuser(a)example.com): Debug: imapc(mx.example.com:993): Connecting to 10.1.0.20:993 dsync(testuser(a)example.com): Info: imapc(mx.example.com:993): Connected to 10.1.0.20:993 (local 10.1.0.114:42924) dsync(testuser(a)example.com): Debug: imapc(mx.example.com:993): Starting SSL handshake dsync(testuser(a)example.com): Debug: imapc(mx.example.com:993): SSL handshake successful dsync(testuser(a)example.com): Debug: imapc(mx.example.com:993): Server capabilities: IMAP4rev1 AUTH=PLAIN ACL BINARY CATENATE CHILDREN CONDSTORE ENABLE ESEARCH ESORT I18NLEVEL=1 ID IDLE LIST-EXTENDED LIST-STATUS LITERAL+ LOGIN-REFERRALS MULTIAPPEND NAMESPACE QRESYNC QUOTA RIGHTS=ektx SASL-IR SEARCHRES SORT THREAD=ORDEREDSUBJECT UIDPLUS UNSELECT WITHIN XLIST dsync(testuser(a)example.com): Debug: imapc(mx.example.com:993): Authenticating as testuser(a)example.com dsync(testuser(a)example.com): Debug: imapc(mx.example.com:993): Server capabilities: IMAP4rev1 ACL BINARY CATENATE CHILDREN CONDSTORE ENABLE ESEARCH ESORT I18NLEVEL=1 ID IDLE LIST-EXTENDED LIST-STATUS LITERAL+ LOGIN-REFERRALS MULTIAPPEND NAMESPACE QRESYNC QUOTA RIGHTS=ektx SASL-IR SEARCHRES SORT THREAD=ORDEREDSUBJECT UIDPLUS UNSELECT WITHIN XLIST dsync(testuser(a)example.com): Debug: imapc(mx.example.com:993): Authenticated successfully dsync(testuser(a)example.com): Debug: imapc: root=, index=, indexpvt=, control=, inbox=, alt= dsync(testuser(a)example.com): Debug: Namespace shared: type=shared, prefix=shared/%u/, sep=/, inbox=no, hidden=no, list=children, subscriptions=yes location=maildir:/data/vmail/example.com/testuser/Maildir:INDEXPVT=/var/vma… dsync(testuser(a)example.com): Debug: shared: root=/run/dovecot/, index=, indexpvt=, control=, inbox=, alt= dsync(testuser(a)example.com): Debug: Namespace virtual: type=private, prefix=virtual/, sep=/, inbox=no, hidden=no, list=yes, subscriptions=yes location=virtual:/data/vmail/virtual:INDEX=MEMORY dsync(testuser(a)example.com): Debug: fs: root=/data/vmail/virtual, index=, indexpvt=, control=, inbox=, alt= dsync(testuser(a)example.com): Debug: brain S: Namespace has location imapc: dsync(testuser(a)example.com): Debug: brain M: Local mailbox tree: Sent guid=00000000000000000000000000000000 uid_validity=0 uid_next=0 subs=yes last_change=0 last_subs=1595535189 dsync(testuser(a)example.com): Debug: brain S: Local mailbox tree: Trash guid=7f5af7ba291b2df1a11d573bdb55d7e9 uid_validity=1 uid_next=89207 subs=yes last_change=0 last_subs=0 dsync(testuser(a)example.com): Debug: brain M: Local mailbox tree: Drafts guid=00000000000000000000000000000000 uid_validity=0 uid_next=0 subs=yes last_change=0 last_subs=1595535189 dsync(testuser(a)example.com): Debug: brain S: Local mailbox tree: Templates guid=d9f092123a43acb205a6869342cf9dd6 uid_validity=126054 uid_next=22295 subs=yes last_change=0 last_subs=0 dsync(testuser(a)example.com): Debug: brain M: Local mailbox tree: Trash guid=00000000000000000000000000000000 uid_validity=0 uid_next=0 subs=yes last_change=0 last_subs=1595534293 dsync(testuser(a)example.com): Debug: brain S: Local mailbox tree: Sent guid=bfb2e03fdce327671e82bf173b1ccb8b uid_validity=1 uid_next=89068 subs=yes last_change=0 last_subs=0 dsync(testuser(a)example.com): Debug: brain M: Local mailbox tree: INBOX guid=6f51443ad5eb195f9f4400005439fba4 uid_validity=1595534294 uid_next=1 subs=no last_change=0 last_subs=0 dsync(testuser(a)example.com): Debug: brain M: Local mailbox tree: Junk guid=6e51443ad5eb195f9f4400005439fba4 uid_validity=1595534293 uid_next=1 subs=yes last_change=0 last_subs=1595534293 dsync(testuser(a)example.com): Debug: brain S: Local mailbox tree: Junk guid=87680557f26fcb26843f739f7427e8c4 uid_validity=1 uid_next=88649 subs=yes last_change=0 last_subs=0 dsync(testuser(a)example.com): Debug: brain S: Local mailbox tree: INBOX guid=c92f64f79f0d1ed01e6d5b314f04886c uid_validity=1 uid_next=89209 subs=yes last_change=0 last_subs=0 dsync(testuser(a)example.com): Debug: brain M: Remote mailbox tree: Trash guid=7f5af7ba291b2df1a11d573bdb55d7e9 uid_validity=1 uid_next=89207 subs=yes last_change=0 last_subs=0 dsync(testuser(a)example.com): Debug: brain M: Remote mailbox tree: Templates guid=d9f092123a43acb205a6869342cf9dd6 uid_validity=126054 uid_next=22295 subs=yes last_change=0 last_subs=0 dsync(testuser(a)example.com): Debug: brain M: Remote mailbox tree: Sent guid=bfb2e03fdce327671e82bf173b1ccb8b uid_validity=1 uid_next=89068 subs=yes last_change=0 last_subs=0 dsync(testuser(a)example.com): Debug: brain M: Remote mailbox tree: Junk guid=87680557f26fcb26843f739f7427e8c4 uid_validity=1 uid_next=88649 subs=yes last_change=0 last_subs=0 dsync(testuser(a)example.com): Debug: brain M: Remote mailbox tree: INBOX guid=c92f64f79f0d1ed01e6d5b314f04886c uid_validity=1 uid_next=89209 subs=yes last_change=0 last_subs=0 dsync(testuser(a)example.com): Debug: brain S: Local mailbox tree: Drafts guid=e0187b65e763143666d22094cedfe6a4 uid_validity=1 uid_next=88914 subs=yes last_change=0 last_subs=0 dsync(testuser(a)example.com): Debug: brain M: Remote mailbox tree: Drafts guid=e0187b65e763143666d22094cedfe6a4 uid_validity=1 uid_next=88914 subs=yes last_change=0 last_subs=0 dsync(testuser(a)example.com): Debug: brain M: Mailbox Drafts: local=00000000000000000000000000000000/0/2, remote=e0187b65e763143666d22094cedfe6a4/0/1: mailbox not selectable yet dsync(testuser(a)example.com): Debug: brain M: Mailbox INBOX: local=6f51443ad5eb195f9f4400005439fba4/0/1, remote=c92f64f79f0d1ed01e6d5b314f04886c/0/1: GUIDs conflict - will be merged later dsync(testuser(a)example.com): Debug: brain M: Mailbox Junk: local=6e51443ad5eb195f9f4400005439fba4/0/1, remote=87680557f26fcb26843f739f7427e8c4/0/1: GUIDs conflict - will be merged later dsync(testuser(a)example.com): Debug: brain M: Mailbox Sent: local=00000000000000000000000000000000/0/0, remote=bfb2e03fdce327671e82bf173b1ccb8b/0/1: mailbox not selectable yet dsync(testuser(a)example.com): Debug: brain M: Mailbox Templates: local=00000000000000000000000000000000/0/0, remote=d9f092123a43acb205a6869342cf9dd6/0/1: mailbox not selectable yet dsync(testuser(a)example.com): Debug: brain M: Mailbox Trash: local=00000000000000000000000000000000/0/0, remote=7f5af7ba291b2df1a11d573bdb55d7e9/0/1: mailbox not selectable yet dsync(testuser(a)example.com): Debug: brain M: Deleting mailbox 'INBOX' (GUID 6f51443ad5eb195f9f4400005439fba4): UIDVALIDITY changed (1 -> 1595534294) dsync(testuser(a)example.com): Debug: brain M: Deleting mailbox 'Junk' (GUID 6e51443ad5eb195f9f4400005439fba4): UIDVALIDITY changed (1 -> 1595534293) dsync(testuser(a)example.com): Error: Mailbox INBOX sync: mailbox_delete failed: INBOX can't be deleted. dsync(testuser(a)example.com): Debug: brain S: Remote mailbox tree: Sent guid=00000000000000000000000000000000 uid_validity=0 uid_next=0 subs=yes last_change=0 last_subs=1595535189 dsync(testuser(a)example.com): Debug: brain S: Remote mailbox tree: Drafts guid=00000000000000000000000000000000 uid_validity=0 uid_next=0 subs=yes last_change=0 last_subs=1595535189 dsync(testuser(a)example.com): Debug: brain S: Remote mailbox tree: Trash guid=00000000000000000000000000000000 uid_validity=0 uid_next=0 subs=yes last_change=0 last_subs=1595534293 dsync(testuser(a)example.com): Debug: brain S: Remote mailbox tree: INBOX guid=6f51443ad5eb195f9f4400005439fba4 uid_validity=1595534294 uid_next=1 subs=no last_change=0 last_subs=0 dsync(testuser(a)example.com): Debug: brain S: Remote mailbox tree: Junk guid=6e51443ad5eb195f9f4400005439fba4 uid_validity=1595534293 uid_next=1 subs=yes last_change=0 last_subs=1595534293 dsync(testuser(a)example.com): Debug: imapc(mx.example.com:993): Disconnected dsync(testuser(a)example.com): Debug: auth-master: conn unix:/run/dovecot/auth-userdb (pid=25419,uid=0): Disconnected: Connection closed (fd=10) given the error again on "next doveadm backup", it indeed appears "something strange is going on" ... hints/suggestions as to what?

1 1

Mailbox sharing, user to user in same domain, OK! User to user sharing in separate domains, problem. ( ... and more oh boy!)
by Andreas T (DC) 22 Jul '20

22 Jul '20

Dovecot -n and version present at the bottom of the email for legibility. System is a Debian 10 + Virtualmin hosting setup for my domains ------------------------------------------------------------------- Hello everyone, my first post. Sorry for the long and confusing post, I'm pretty new to dovecot other than basic functionality. I recently in the last week went through the documentation for both shared (user to user) and public mailboxes and got them both working. Took me a bit but eventually I figured it out, but I am still encountering some stubborn scenarios. I am having some issues with 2 types of sharing. ( I believe problem A + B are related as the error is similarly permission based error) For inconsistencies in the user account names, user(a)domain.com vs user-domain.com please see issue C, which my workaround is functional. A.) Sharing user to user between in the same domain works fine. Sharing user to user in different domains gives me some permission errors. Permissions have been granted (to (using Linux ACL for more fine grained permissions) as far as I can tell. Trying to share the info "INBOX" (fullshare, same issue for single boxes as well) from the info(a)primarydomain.com to user(a)externaldomain.com from info(a)primarydomain.com Mailder cat dovecot-acl user=user-externaldomain.com akxeilprwts getfacl dovecot-acl # file: dovecot-acl # owner: info(a)primarydomain.com # group: primarydomain.com user::rw- user:user@externaldomain.com:rwx #effective:rw- user:info@primarydomain.com:rwx #effective:rw- group::--- mask::rw- other::--- doveadm acl debug -u user-externaldomain.com "@/info@primarydomain.com/INBOX" doveadm(user-externaldomain.com): Error: stat(/home/primarydomain.com/homes/info/Maildir/tmp) failed: Permission denied (euid=1121(user(a)externaldomain.com) egid=1091(holanow.com) missing +x perm: /home/primarydomain.com, we're not in group 1092(primarydomain.com), dir owned by 1126:1092 mode=0750) doveadm(user-externaldomain.com): Error: Can't open mailbox @/info@primarydomain.com/INBOX: stat(/home/primarydomain.com/homes/info/Maildir/tmp) failed: Permission denied (euid=1121(user(a)externaldomain.com) egid=1091(holanow.com) missing +x perm: /home/primarydomain.com, we're not in group 1092(primarydomain.com), dir owned by 1126:1092 mode=0750) getfacl /home/primarydomain.com/homes/info/Maildir/tmp # file: home/primarydomain.com/homes/info/Maildir/tmp # owner: info(a)primarydomain.com # group: primarydomain.com user::rwx user:user@externaldomain.com:rwx user:info@primarydomain.com:rwx group::--- mask::rwx other::--- default:user::rwx default:user:user@externaldomain.com:rwx default:user:info@primarydomain.com:rwx default:group::--- default:mask::rwx default:other::--- getfacl /home/primarydomain.com/homes/info/Maildir # file: home/primarydomain.com/homes/info/Maildir/ # owner: info(a)primarydomain.com # group: primarydomain.com user::rwx user:user@externaldomain.com:rwx user:info@primarydomain.com:rwx group::--- mask::rwx other::--- default:user::rwx default:user:user@externaldomain.com:rwx default:user:info@primarydomain.com:rwx default:group::--- default:mask::rwx default:other::--- B.) Public mailbox, mailboxes that are physically present on the public mail dir, work fine. Public boxes which are symlinks to mailboxes to other users, with correct permission and ACL, always give me permission errors and do not show up publicly. These type of mailboxes do show up if the person already has user to user share setup with those boxes, which due to problem A, means only within the same domain. Similar errors as to the A scenario, even if giving complete rwx access to all (user/group/other) I still get permission denied issues. It just feel like dovecot isn't even trying to access the files C. Tiny "other" problem I have worked around already. dovecot-acl when using users via their user(a)domain.com account doesn't lookup the user correctly. I already have set, auth_username_translation = @- which works for when users login but it doesn't seem to work with dovecot-acl files. I have helper account pointers replacing the @ with - and then the ACL file works fine. Would prefer acl files contain, user=user1(a)primarydomain.com akxeilprwts user=user2(a)primarydomain.com akxeilprwts But this works and is not a show stopper. user=user1-primarydomain.com akxeilprwts user=user2-primarydomain.com akxeilprwts -------------------------------------------- dovecot --version 2.3.4.1 (f79e8e7e4) # 2.3.4.1 (f79e8e7e4): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.4 () # OS: Linux 5.4.44-2-pve x86_64 Debian 10.4 # Hostname: vps1.abclution.com doveconf: Warning: please set ssl_dh=</etc/dovecot/dh.pem doveconf: Warning: You can generate it with: dd if=/var/lib/dovecot/ssl-parameters.dat bs=1 skip=88 | openssl dhparam -inform der > /etc/dovecot/dh.pem auth_mechanisms = plain login auth_username_translation = @- mail_debug = yes mail_location = maildir:~/Maildir mail_plugins = acl 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 = / } namespace public_ns1 { location = maildir:/home/.Public_Mailboxes:INDEX=~/Maildir/public_ns1:INDEXPVT=~/Maildir/public_ns1 prefix = Public/ separator = / subscriptions = no type = public } namespace shared_ns1 { list = yes location = maildir:%%h/Maildir:INDEX=~/Maildir/shared_ns1/%%u:INDEXPVT=~/Maildir/shared_ns1/%%u prefix = @/%%u/ separator = / subscriptions = no type = shared } passdb { driver = pam } plugin { acl = vfile acl_anyone = allow acl_defaults_from_inbox = yes acl_shared_dict = file:%h/Maildir/shared-mailboxes } protocols = " imap pop3" service auth { unix_listener auth-userdb { mode = 0777 } } ssl_cert = </etc/dovecot/dovecot.cert.pem ssl_cipher_list = ECDHE-RSA-AES256-SHA384:AES256-SHA256:AES256-SHA256:RC4:HIGH:MEDIUM:+TLSv1:+TLSv1.1:+TLSv1.2:!MD5:!ADH:!aNULL:!eNULL:!NULL:!DH:!ADH:!EDH:!AESGCM ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it ssl_prefer_server_ciphers = yes userdb { driver = passwd } protocol imap { mail_plugins = acl imap_acl }

1 1

IMAP ALERT on reason/nologin
by Pedro Ribeiro 22 Jul '20

22 Jul '20

Hello everyone, Some dovecot versions (years!) ago. I've made a rather complicated SQL query that verified some conditions during the SQL passdb checking and returned the usual parameters or "nologin" field signalling some account problem and a text on the "reason" field that were shown to the user telling him the reason of being rejected the login. Common "reasons" are blocked accounts, suspected brute-force to the user account, historic problems from his IP address, etc. In the current versions I've found that despite the attributes being set by the SQL query, dovecot no longer seems to signal that to the client application and it ends with some generic "wrong password" causing a lot of confusion and user complains. I can't find any reference to that (nologin/reason) logic in the current Dovecot documentation. Is this feature deprecated/removed? Were that logic changed and documented elsewhere? regards! stay safe! Note: running Dovecot 2.3.10.1 -- Best regards, =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Pedro Ribeiro Politécnico de Lisboa, Serviços da Presidência Departamento de Sistemas de Informação e Comunicações Phone: +351 210 464 700 (general) / VoIP: 80100 Helpdesk: helpdesk(a)net.ipl.pt / https://www.net.ipl.pt =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

1 0

ports with different crypto settings
by Leonardo Rodrigues 21 Jul '20

21 Jul '20

Hello Everyone, Is it possible, with latest dovecot, to have different crypto settings on different pop/imap ports? Basically i'm looking to have one port with TLSv1 enabled, which will be exposed to internal networks only, and other ports with TLSv1.2+ only, which will be exposed to the external networks. The internal one will likely be running on a different port and traffic will be redirected to it via iptables, so user doesn't need to care about it. Is that possible? I haven't found anything similar on the documentations, it seems to me that crypto settings are global ... -- Atenciosamente / Sincerily, Leonardo Rodrigues Solutti Tecnologia http://www.solutti.com.br Minha armadilha de SPAM, NÃO mandem email gertrudes(a)solutti.com.br My SPAMTRAP, do not email it

1 0

Sieve and OX push_notification_drive seem to not work together
by Ralf Becker 21 Jul '20

21 Jul '20

While it's documented that the OX push_notification_driver only supports MessageNew events, it does NOT generate any event if a Sieve script moves the message on arrival to an other folder, neither in INBOX were it original arrives by LMTP, nor in the folder Sieve moves the message. Is that a misconfiguration on my side, or a know / desired limitation or just a bug? I use LMTP to deliver mails from Postfix to Dovecot: protocol lmtp { mail_plugins = $mail_plugins notify push_notification } Does eg. the same need to be configured somehow for the Sieve plugin? 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 2

Questions about Dovecot push notifications
by Ralf Becker 21 Jul '20

21 Jul '20

I read the docu available under: https://doc.dovecot.org/configuration_manual/push_notification/ I'm using Dovecot 2.2.36.4 with directors and a replicating pair of backends using a custom dict with proxy protocol for user- and passdb plus a userdb using sqlite for backup. I understand 2.2 only allows to notify about new arriving mails, not eg. flag-changes which would require 2.3 with LUA. I want to use the ox notification driver with a http url (https seems to be 2.3 only). I read to enable push notifications on a mailbox I need: a) IMAP metadata enabled incl. a backend/driver to store the metadata b) enable push for the individual mailbox using a doveadm command (maybe also via IMAP, which would be easier in my case) My questions are: 1. can I set some static metadata via userdb to enable push for all mailboxes? 2. if no, does setting the metadata on one replicating backend replicates it to the other one too? 3. what purpose does the user=<something@else> argument in the doveadm command to enable push server: doveadm mailbox metadata set -u user(a)example.com -s "" /private/vendor/vendor.dovecot/http-notify user=11@3 Does it replace "user(a)example.com" in the push payload with <something@else>? 4. can I set the required metadata via IMAP command preferable with a (already configured) master user? Thanks in advance :) 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 1

History mails are stored in the tmp/ directory
by lty 21 Jul '20

21 Jul '20

We found that there are historically corrupted mails in the tmp/ directory, For example, Maildir/tmp/ or Maildir/.Drafts/tmp/ exists. We suspect that it may be caused by network transmission, or the user interrupted the network link. Can the dovecot team possibly fix this problem? dovecot --version 2.2.36

3 3

solr and dovecot-2.2.36.4
by Maciej Milaszewski 21 Jul '20

21 Jul '20

Hi Today i try run solr-8.6.0 + dovecot-2.2.36.4 and false I read https://doc.dovecot.org/configuration_manual/fts/solr/#fts-backend-solr Where I get schema.xml and solrconfig.xml for this version solr and dovecot ? I try schema.xml and solrconfig.xml from working solr-6.6.5 (dovecot) "dovecot: org.apache.solr.common.SolrException:org.apache.solr.common.SolrException: Error initializing QueryElevationComponent"

2 1

submission proxy -- where to config/present client cert?
by PGNet Dev 20 Jul '20

20 Jul '20

I've a dovecot instance setup with submission proxy, protocols = imap lmtp submission sieve hostname = internal.mx.example.com submission_relay_host = internal.mx.example.com submission_relay_port = 465 submission_relay_trusted = yes submission_relay_ssl = smtps submission_relay_ssl_verify = yes service submission-login { inet_listener submission { address = 10.2.2.10, 127.0.0.1 port = 50465 ssl = yes } } protocol submission { ssl_cert = < /sec/vmail/mx.example.com.server.EC.crt.pem ssl_key = < /sec/vmail/mx.example.com.server.EC.key.pem ssl_verify_client_cert = no } It submits to a postfix instance, atm on the same host, [internal.mx.example.com]:465 inet n - n - - smtpd -o smtpd_tls_req_ccert=no with that setup, all works as expected. If I turn ON required client cert verification @ postfix, - -o smtpd_tls_req_ccert=no + -o smtpd_tls_req_ccert=yes with that add'l req't, postfix log reports "no client certificate presented" Jul 18 14:52:38 mx postfix/submit-from-dovecot/smtpd[37133]: connect from internal.mx.example.com[10.2.2.10] Jul 18 14:52:39 mx postfix/submit-from-dovecot/smtpd[37133]: Anonymous TLS connection established from internal.mx.example.com[10.2.2.10]: TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-384) server-digest SHA384 Jul 18 14:52:39 mx postfix/submit-from-dovecot/smtpd[37133]: NOQUEUE: abort: TLS from internal.mx.example.com[10.2.2.10]: No client certificate presented Jul 18 14:53:09 mx postfix/submit-from-dovecot/smtpd[37133]: disconnect from internal.mx.example.com[10.2.2.10] commands=0/0 Clearly, I'm missing config. What in my dovecot submission config^^ do I need to change/add to get it to 'present' a client cert to the postfix relay for client cert verification?

2 2

Set mail to only display mail within 30 or 60 days
by lty 20 Jul '20

20 Jul '20

Set mail to only display mail within 30 or 60 days, Here are two examples. 1. normal E.g: A654 FETCH 2:4 (FLAGS BODY[HEADER.FIELDS (DATE FROM)]) * 2 FETCH (FLAGS (\Seen) BODY[HEADER.FIELDS (DATE FROM)] {73} Date: Tue, 07 May 2020 12:26:55 +0800 From: <test(a)www.chengmail.ml> ) * 3 FETCH (FLAGS (\Seen) BODY[HEADER.FIELDS (DATE FROM)] {62} Date: Tue, 07 May 2020 12:35:34 +0800 From: lty(a)cndns.com ) * 4 FETCH (FLAGS (\Seen) BODY[HEADER.FIELDS (DATE FROM)] {62} Date: Tue, 07 Jul 2020 17:41:53 +0800 From: lty(a)cndns.com ) A654 OK Fetch completed (0.002 + 0.000 + 0.001 secs). 2. Set to display mail within 30 days E.g: A654 FETCH 2:4 (FLAGS BODY[HEADER.FIELDS (DATE FROM)]) * 4 FETCH (FLAGS (\Seen) BODY[HEADER.FIELDS (DATE FROM)] {62} Date: Tue, 07 Jul 2020 17:41:53 +0800 From: lty(a)cndns.com ) A654 OK Fetch completed (0.002 + 0.000 + 0.001 secs). Is there any way to display the result of case 2? I found lua. https://doc.dovecot.org/admin_manual/lua/#mail-lua But I don't know how to edit the lua script, Are there more examples? I also watched the help, but it doesn't help much. https://doc.dovecot.org/configuration_manual/authentication/lua_based_authe… https://doc.dovecot.org/configuration_manual/push_notification/#lua-push-no… Can Lua fulfill my needs?

1 0

I need some help with my Dovecot and Postfix configs - I'm unable to log in on my mail server
by Nils 20 Jul '20

20 Jul '20

Hello, currently I'm working on my first mailserver but I can't log in to the account I made. For now my client (Mozlla Thunderbird) detects the server config (STARTTLS, Port, ...) but it is "Unable to log in at server. Probbly wrong configuration, username or passsword". I know that I added username and password correctly so there must something else be wrong. I run Debian 10 x64 on a fresh installation. Installed are: postfix, postfix-pcre, dovecot-core, dovecot-imapd and dovecot-pop3d. Dovecot is version 2.3.4.1, Postfix is 3.4.10. Here are my configurations: Postfix main.cf: https://pastebin.com/S17jWDQd Postfix master.cf: https://pastebin.com/W0nynZG6 dovecot.conf: https://pastebin.com/tMD90Znn This is what my server logs (mail.info, mail.warn) tell me: root@bgrsld-mail0:~# tail /var/log/mail.info Jul 17 18:22:08 bgrsld-mail0 postfix/submission/smtpd[8472]: improper command pipelining after EHLO from unknown[192.168.2.110]: QUIT\r\n Jul 17 18:22:08 bgrsld-mail0 postfix/submission/smtpd[8465]: disconnect from unknown[192.168.2.110] ehlo=1 quit=1 commands=2 Jul 17 18:22:08 bgrsld-mail0 postfix/submission/smtpd[8472]: disconnect from unknown[192.168.2.110] ehlo=1 quit=1 commands=2 Jul 17 18:24:59 bgrsld-mail0 postfix/submission/smtpd[8485]: warning: dict_nis_init: NIS domain name not set - NIS lookups disabled Jul 17 18:24:59 bgrsld-mail0 postfix/submission/smtpd[8485]: connect from unknown[192.168.2.110] Jul 17 18:24:59 bgrsld-mail0 postfix/submission/smtpd[8485]: improper command pipelining after EHLO from unknown[192.168.2.110]: QUIT\r\n Jul 17 18:24:59 bgrsld-mail0 postfix/submission/smtpd[8485]: disconnect from unknown[192.168.2.110] ehlo=1 quit=1 commands=2 Jul 17 18:28:19 bgrsld-mail0 postfix/anvil[8473]: statistics: max connection rate 2/60s for (submission:192.168.2.110) at Jul 17 18:22:08 Jul 17 18:28:19 bgrsld-mail0 postfix/anvil[8473]: statistics: max connection count 2 for (submission:192.168.2.110) at Jul 17 18:22:08 Jul 17 18:28:19 bgrsld-mail0 postfix/anvil[8473]: statistics: max cache size 1 at Jul 17 18:22:08 root@bgrsld-mail0:~# tail /var/log/mail.warn Jul 17 18:21:50 bgrsld-mail0 postfix/postfix-script[8290]: warning: symlink leaves directory: /etc/postfix/./makedefs.out Jul 17 18:22:08 bgrsld-mail0 postfix/submission/smtpd[8465]: warning: dict_nis_init: NIS domain name not set - NIS lookups disabled Jul 17 18:22:08 bgrsld-mail0 postfix/submission/smtpd[8472]: warning: dict_nis_init: NIS domain name not set - NIS lookups disabled Jul 17 18:24:59 bgrsld-mail0 postfix/submission/smtpd[8485]: warning: dict_nis_init: NIS domain name not set - NIS lookups disabled (I removed any information from older issues that are already solved, thats why mail.warn misses a few lines and there is no mail.err, mail.err hadn't any newer messages) Here is my only line from dovecot's userpass file (/maildata/userpass): nils@intern.xxx.xxx:{CRYPT}$2y$05$kkxElxFGsLSyTJwbEaPZzO/QA33vGY3oGyHcgEZa9rpklgBTKQw9O My postfix vhosts file (/maildir/vhosts) intern.xxx.xxx My postfix vmaps file (/maildir/vmaps) nils(a)intern.xxx.xxx intern.xxx.xxx/nils/ I've also created the hased database with 'postmap /maildata/vmaps' This is the script I've used to create my user database: https://pastebin.com/9uViNqjB I haven't worked with postfiy or dovecot yet so there are many things I don't know. Because of this a lot of my configurations is copied from an iRedMail installation. I know that taking these configs may cause some problems but I don't know where to change them or what else is wrong or missing. Thank you for any help!

6 11

Sieve and handling multiple addresses
by ＠lbutlr 19 Jul '20

19 Jul '20

I an trying to write a sieve action that will take mail that is addressed to a user only it is filed in a mailbox (e.g. "Direct") if it is to the email AND to any other email address, then file it in a mailbox named, e.g. "Cc". And if the mail is not addressed to the user at all, sieve does nothing with it. Message 1: to foo(a)example.com => Direct Message 2: to/cc foo(a)example.com & to/cc to anyone(a)anydomain.tlf => CC Optional: If it contains a specific header like "X-bypass: secret string" => no action Message 3: NOT to/cc foo(a)example.com => no action I've gotten exactly nowhere so far Something like if :allof (header :contains ["to"] ["foo#example.com"], header :contains ["cc"] ["foo#example.com"]) Takes care of the first part of the message 1 and 2 criteria. But then what? -- Was it everything you wanted to find? and did you miss me while you were looking for yourself out there?

5 8

problem with client using TLS
by ratatouille 18 Jul '20

18 Jul '20

Hello! On my testserver running CentOS8 I have installed dovecot v2.3.8. I can connect to the server using claws-mail on my PC but can't using K9-mail on android device. Jul 18 12:24:57 imap-login: Debug: SSL: where=0x10, ret=1: before SSL initialization Jul 18 12:24:57 imap-login: Debug: SSL: where=0x2001, ret=1: before SSL initialization Jul 18 12:24:57 imap-login: Debug: SSL: where=0x2002, ret=-1: before SSL initialization Jul 18 12:24:57 imap-login: Debug: SSL: where=0x2002, ret=-1: before SSL initialization Jul 18 12:24:57 imap-login: Debug: SSL: where=0x2001, ret=1: before SSL initialization Jul 18 12:24:57 imap-login: Debug: SSL alert: where=0x4008, ret=582: fatal protocol version Jul 18 12:24:57 imap-login: Debug: SSL: where=0x2002, ret=-1: error Jul 18 12:24:57 imap-login: Debug: SSL error: SSL_accept() failed: error:14209102:SSL routines:tls_early_post_process_client_hello:unsupported protocol Jul 18 12:24:57 imap-login: Info: Disconnected (no auth attempts in 0 secs): user=<>, rip=87.182.44.142, lip=185.84.81.115, TLS handshaking: SSL_accept() failed: error:14209102:SSL routines:tls_early_post_process_client_hello:unsupported protocol, session=<uppwr7SqrrpXtiyO> Jul 18 12:24:57 imap-login: Debug: SSL error: SSL_accept() syscall failed: Invalid argument Tried different settings without luck. grep -v '^#' 10-ssl.conf ssl = yes ssl_cert = </etc/letsencrypt/live/smtp.dualbit.de/fullchain.pem ssl_key = </etc/letsencrypt/live/smtp.dualbit.de/privkey.pem ssl_dh = </etc/dovecot/dh.pem ssl_min_protocol = TLSv1.2 ssl_cipher_list = PROFILE=SYSTEM ssl_prefer_server_ciphers = yes Can somebody help solving this? Kind regards Andreas

3 8

Non-standard socket locations w/ Dovecot + AWS Linux
by Antonio Leding 18 Jul '20

18 Jul '20

# === The post relates to Dovecot v2.2 running on AWS Linux v1 === # Hello all… The Dovecot sockets on this server are installed in two different locations one of which is different from what I have on my other Dovecot installations which run on Centos-7. Here are the sockets paths: — all sockets EXCEPT "auth-master” —> "/usr/local/var/run/dovecot” <<<<< this appears to be the default for this server — "auth-master” —> "/var/run/dovecot” <<<<< without this statement, Dovecot authentication always failed. The config stanza for this is shown below: service auth { unix_listener auth-userdb { path = /var/run/dovecot/auth-master mode = 0600 user = vmail } } ============ The above has been working great for several years but the time eventually came where I needed to upgrade. This of course meant I had to move lots of maildata between the servers. Unfortunately, the “auth-userdb" config mentioned above prevented “dsync" from working properly. This is the error I received when trying “dsync”: Error: userdb lookup: connect(/usr/local/var/run/dovecot/auth-userdb) failed: No such file or directory This error led me to the eventual fix which was adding the following to the “dovecot.conf” file: auth_socket_path = /var/run/dovecot/auth-master ============ So, to my questions: (1) Why would the socket path on this AWS installation be different from what I see on my Centos-based Dovecot servers and also what I’ve read in several Dovecot mailer discussions? (2) Can the default socket path be set at compile time? If so, then I'm thinking maybe the AWS folks — for whatever reason — decided to install all sockets (except ”auth-master”) in the “/usr/local/var/run/dovecot” directory. Are there any benefits or reason to do this? (3) Is there any requirement that the “auth-master” socket be located in the “/var/run/dovecot” directory? Also, there is nothing else in that directory — just the “auth-master” socket file — that’s it. (4) Why is “dsync" looking for "auth-userdb" in the “/usr/local/var/run/dovecot” directory despite the “auth" stanza stating it is located elsewhere in "/var/run/dovecot”? (5) And last, why do I need to add the “auth_socket_path” statement to get “dsync” working even though the socket path is stated in the “auth" stanza? Thanks in advance for your time on this. I know this is mostly to help educate me on what is going on so I really appreciate your feedback…

1 0

Namespace issues & duplicate maiboxes
by Antonio Leding 18 Jul '20

18 Jul '20

Hello, I am seeing duplicate mailboxes when I perform the “doveadm mailbox list” command…the output is as follows: ================= INBOX INBOX.Drafts INBOX.Trash INBOX.Sent INBOX.INBOX INBOX.INBOX.Sent Messages INBOX.INBOX.Drafts INBOX.INBOX.Trash INBOX.INBOX.Deleted Messages ================= Here is namespace config that seems to have caused the above duplicates. Please help me understand what I’m doing wrong here…and also, not sure if this is relevant but the client is Apple Mail… ================= namespace inbox { type = private separator = . inbox = yes prefix = INBOX. mailbox Trash { auto = subscribe special_use = \Trash } mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Sent { auto = subscribe special_use = \Sent } }

2 2

Stuck here - help please
by Kishore Potnuru 18 Jul '20

18 Jul '20

Hi All, I have 2 test servers with the below configuration. ========================== Linux OS - Red Hat Enterprise Linux Server release 7.7 (Maipo) Dovecot version - 2.2.36 (1f10bfa63) Postfix version - 2.10.1 ========================== Trying to create High Availability. I have added both of the above servers behind a F5 load balancer. I have got a Load Balancer FQDN "intl-dev-imaptest.testorg.com". I have enabled/opened the ports (25/110/143/993/995) on the above " intl-dev-imaptest.testorg.com". When I send 10 emails to "intl-dev-imaptest.testorg.com", then those 10 emails are getting distributed between the above 2 backend servers (5 emails to each server). I see those 5 emails each in both the servers. >From Outlook I have configured the email address using "POP and IMAP", when I gave the IMAP server as "intl-dev-imaptest.testorg.com" ,then it shows only 5 emails from server1 in outlook and after a few seconds/minutes, automatically it shows/refreshes the other 5 emails from server2. But I am not seeing all the 10 emails at the same time. why? So I tried the sync command. When I execute sync command like below from server1, it reflects the same emails in other server2 also. Then I see the same number of emails in both the servers. Is it not possible to access the both servers emails at one time with the "sync" command? Do we need to run this on all the email boxes on both servers? don't we miss/lose any emails during this sync process multiple times? "doveadm sync -f -u kishore(a)test.testorg.com remote:vmail@bal3200dev002.testorg.com" Is "replication" and "sync" are same? Why are we not able to see all the emails at one time without the "sync" command? What is the best and easiest way to create High Availability with just 2 servers, like emails should travel to both servers equally and if one server goes down also, another server should take care of the emails/functionality. This is my requirement. My current real time environment: I have around 10 email domains and each domain is having 10 imap emails. In total around 100 email boxes/addresses. We receive around 50K emails in a day to those email addresses. We are using the "Maildir" format in our environment. Want to move to the High Availability option with 2 servers. Please help me to fix the issue. Thanks & Regards, Kishore Potnuru

3 6

Outlook vs Thunderbird
by The Doctor 16 Jul '20

16 Jul '20

Got a client that usually uses Outlook I think 2010. This person tends to move their e-mails to certain folers. On Thunderbird, the move shows. Not on Outlook. Any explanation? -- Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca Yahweh, Queen & country!Never Satan President Republic!Beware AntiChrist rising! https://www.empire.kred/ROOTNK?t=94a1f39b A full cup must be carried steadily. -English proverb

12 22

Variable expansion in passwords
by lukn 16 Jul '20

16 Jul '20

Hello list A user reports failure to log in after password change. The client side error message indicates a lost or dropped connection by the server. A peek into the server logs reveales this: dovecot: imap(user(a)example.com)<53267><el0HoZGqHIdb0K2G>: Error: Failed to expand plugin setting plain_pass = 'asdf%?asdf': Unknown variable '%?' This looks a lot like a %-variable in the user provided password is tried to be expanded... Is this a bug or did I misconfigure something? output of dovecot -n is attached. regards lukn

1 0

NFS vs Replication
by Andrea Gabellini 16 Jul '20

16 Jul '20

Hello list, I built an email system using a proxy / director pair (IMAP, POP3, LMTP) and a backend pair. To have an HA system, I would like to understand if it is better to use an NFS export or replication to save emails and index files NFS is provided by a NAS (in HA), while for replication I would use the local backend disks Which of the two systems is more reliable? Are there any drawbacks for one or the other? Thanks, Andrea -- __________________________ Buy a Pentium 586/200 so you can reboot faster. __________________________ 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.

5 8

Error in namespace config; how to move messages
by Antonio Leding 16 Jul '20

16 Jul '20

Hello, I inadvertently made an error re: the namespace prefix when setting up a few accounts and several messages have been saved in the Sent\Deleted folders under the incorrect namespace. Can I simply copy these messages to the relevant folder in the proper namespace? Or do I need to export\import these? Some other procedure? Thanks in advance for any feedback…

2 1

Massive alias / bulk delivery problem
by gnd 16 Jul '20

16 Jul '20

Hello list, we are experimenting with using Dovecot as part of a simplified mail stack with SQL for a internal messaging / notification system for our customers. Sometimes we need to send a message to thousands of customers at once and we do it by having aliases resolve to 10k and 20k+ mail accounts. When we send such a message the server load (obviously) is very high for a few minutes (in case of an alias containing 10k addresses its around 6-7 minutes for a 2 core machine with load around 20-30). Are there any optimizations or ways how to design the system around this problem ? Eg. is there a way how to deliver messages more slowly, and spread the load over longer time ? The stack is very simple with Postfix receiving the messages and Dovecot acting as a LMTP and IMAP server. Mailboxes are in the Maildir format on disk. Customers get the messages on login, a PHP script connects to the mail account associated with their ID via IMAP and sends unseen messages in the form of a JSON. Best regards, gnd/

5 6

doveadm quota question
by hfh＠cndns.com 15 Jul '20

15 Jul '20

I found that when the mailbox name contains special characters such as \x7f, when the doveadm quota recalc -u xxx command is executed, the messages under the mailbox name with special characters will not be counted. doveadm mailbox list -u xxx Actual mailbox name: doveadm quota recalc -u xxx, Mail under 'INBOX.Metaltex' will not be counted. hfh(a)cndns.com

1 0

dovecot 2.2.13
by Santhosh 14 Jul '20

14 Jul '20

all, below command not reporting the actual usage report on dovecot 2.2.13. please share your suggestion to how to fix this issue doveadm -f flow mailbox status -A -t 'messages vsize' '*' is just showing rkreddy messages=0 vsize=0 jcplho messages=0 vsize=0 planning messages=0 vsize=0 accounts messages=0 vsize=0 spam.notify messages=0 vsize=0 jsraju messages=0 vsize=0 amarnath messages=0 vsize=0 kamesh messages=0 vsize=0 moulivarma messages=0 vsize=0 test messages=0 vsize=0 electrical messages=0 vsize=0 subbarao messages=0 vsize=0 contracts messages=0 vsize=0 rrsrinivas messages=0 vsize=0 sralluri messages=0 vsize=0 jvgkraju messages=0 vsize=0 harikrishna messages=0 vsize=0 kvvnrao messages=0 vsize=0 chandrasekhar messages=0 vsize=0 admin messages=0 vsize=0 gsnraju messages=0 vsize=0 Thanks Kumar -- Sent from: http://dovecot.2317879.n4.nabble.com/

2 1

IMAP SEARCH over ALL mailboxes
by Filip Hanes 14 Jul '20

14 Jul '20

Hi, is it possible to SEARCH in dovecot IMAP over all messages in all mailboxes without selecting each mailbox?

2 2

Static users and doveadm
by Antonio Leding 14 Jul '20

14 Jul '20

Hello Dovecot users… I wanted to ask is using a static userdb will cause issues with some of the account and user related doveadm commands? If so, any suggestions on how to use doveadm in such a configuration? I have pasted both the cmd + error and userdb config below — Thanks in advance… sudo doveadm mailbox list -A Error: auth-master: userdb list: User listing returned failure doveadm: Error: Failed to iterate through some users userdb { args = uid=vmail gid=vmail home=/var/vmail allow_all_users=yes userdb_warning_disable=yes driver = static }

2 1

Apple Mail and subfolders
by Filip Hajný 14 Jul '20

14 Jul '20

Hi all, does anybody here use MacOS (Catalina) Mail, who can confirm that subfolders (i.e. folders inside folders) work for them? It seems that I cannot create/access Maildir subfolders at all. Subfolders created in Mail show up as '.folder\2esubfolder' on disk, suggesting that Apple Mail is URL-coding the dot separator before it passes it onto Dovecot. No such translation takes place when interpreting the IMAP tree though, resulting in subfolders rendered as plain entries with the dot separator preserved. Subfolders can be created from elsewhere (SoGO, Roundube, Thunderbird) just fine and work here just fine, suggesting that all is well in terms of Dovecot configuration. Subfolders created here though show up as a proper hierarchy in Apple Mail, but their contents is not displayed, so the user thinks the subfolder is empty. This definitely used to work fine in the past. Running 2.3.10.1 as part of the Mailcow suite. -F

5 7

Syncing emails from external server like Gmail
by Vitalii 14 Jul '20

14 Jul '20

Greeting I've managed to backup my emails from external email server via dsync and imapc: protocol like this: doveadm -Dv -o imapc_user='user(a)gmail.com' -o imapc_password="pass" -o imapc_host=imap.gmail.com backup -R -u duke(a)ejoom.com imapc: taken from https://wiki.dovecot.org/Migration/Dsync I wish to do regular syncing of 5min interval to substitute 'getmail' program. When I repeat the command It doesn't download all the attachments(!good) but It seems that at retrieve all the the GUIDs and UIDs(!bad) again that take quite long considering 30K emails. The question is how to speed it up and retrieve only new emails? Does anyone have a solution for regular synchronization? What is the best way? Logs look like this: https://gist.githubusercontent.com/vnagara/87e0da1b21b51f68fd74270b3ec653b3… It wrights that "Mailboxes are equal" but still verifies all the UIDs again. Thanks.

4 11

Fwd: Dsync mail migration from v2.2 --> v2.3
by Antonio Leding 14 Jul '20

14 Jul '20

Two items I forgot to mention in my initial post: (A) I am running the sync command on the new v2.3 server. (B) To get sync to work, I had to add the following to the old v2.2 server: auth_socket_path = /var/run/dovecot/auth-master I think this relates to what I said in my initial post about AWS linux installing all of the sockets into a non-standard location. I say this because when I was trying get this working but before I had added the above setting, I noticed the following message: Error: userdb lookup: connect(/usr/local/var/run/dovecot/auth-userdb) failed: No such file or directory This seemed to indicate that the old server was looking for the auth socket in the incorrect location. So, I decided to correct this with the setting I noted above. Please let me know if I had this correct or perhaps there is something else going on here… Thanks... > Begin forwarded message: > > From: Antonio Leding <tech(a)leding.net> > Subject: Dsync mail migration from v2.2 --> v2.3 > Date: July 13, 2020 at 8:45:18 PM PDT > To: dovecot(a)dovecot.org > > Hello all, > > I’ve been battling how to migrate my imap mail following a new server install that has Dovecot and Postfix upgrades. > > The research seems pretty clear that the preferred method is to use dsync to get the mail from Server-A to B. After several hours and several different combos, I think I might finally have this working. However, before committing to my procedure and running it against all mailboxes, I wanted to bounce this off of the community and get any feedback that might catch possible issues and\or offer some advice. > > Environment > > Old server: Dovecot 2.2.2 running on AWS linux 1 (I believe that is based on RHEL 4 or 5). > New server: Dovecot 2.3.10.1 running on CentOS 7.6. > All authentication is done by Dovecot against a mySQL (and Maria) database — nothing is in files. > All mail data and mailboxes are owned by a dedicated user “vmail” and I’m using a static userdb. > SSH is via public key file only — no PW based SSH is allowed. > SSH is on a non-standard port > > Operations > > I’ve decided to migrate one mailbox per command. I only have about 30 accounts on the server so this shoudn't be a huge deal. > Here is the command that I believe is good to go: > > sudo doveadm -Dv sync -u [ MBOX_TO_MIGRATE ] remote:vmail@[ SERVER ] > > The SERVER references a host stanza in root's SSH connection file: /root/.ssh/config > I need to use the config file because I (a) use a non-standard SSH port; (b) need to login as “vmail” ; (c) need to use the “vmail" identity file. > > Comments & notes > > The Dovecot 2.2 package for AWS Linux was apparently setup to install all of the sockets in /usr/local/var/run/dovecot. This must have caused authentication issues because to get it working properly, I then had to add "path = /var/run/dovecot/auth-master” statement to the “auth" stanza in dovecot.conf file. > Also, the fact that I do not use a “standard” SSH config was an issue early on but once I committed to allowing vmail to SSH into the old server, that part became moot. For security purposes, I will probably disable vmail SSH after the data is migrated. > > Questions > > First and foremost — any obvious issues here? > Next, any advice and\or lessons learned with this type of migration? > Finally, presuming this is the proper way to do this, will this migrate all mail content including Sent, Deleted, Drafts, etc.? > > > Thanks in advance for taking the time and providing any feedback — very much appreciated... > >

1 0

Dsync mail migration from v2.2 --> v2.3
by Antonio Leding 14 Jul '20

14 Jul '20

Hello all, I’ve been battling how to migrate my imap mail following a new server install that has Dovecot and Postfix upgrades. The research seems pretty clear that the preferred method is to use dsync to get the mail from Server-A to B. After several hours and several different combos, I think I might finally have this working. However, before committing to my procedure and running it against all mailboxes, I wanted to bounce this off of the community and get any feedback that might catch possible issues and\or offer some advice. Environment Old server: Dovecot 2.2.2 running on AWS linux 1 (I believe that is based on RHEL 4 or 5). New server: Dovecot 2.3.10.1 running on CentOS 7.6. All authentication is done by Dovecot against a mySQL (and Maria) database — nothing is in files. All mail data and mailboxes are owned by a dedicated user “vmail” and I’m using a static userdb. SSH is via public key file only — no PW based SSH is allowed. SSH is on a non-standard port Operations I’ve decided to migrate one mailbox per command. I only have about 30 accounts on the server so this shoudn't be a huge deal. Here is the command that I believe is good to go: sudo doveadm -Dv sync -u [ MBOX_TO_MIGRATE ] remote:vmail@[ SERVER ] The SERVER references a host stanza in root's SSH connection file: /root/.ssh/config I need to use the config file because I (a) use a non-standard SSH port; (b) need to login as “vmail” ; (c) need to use the “vmail" identity file. Comments & notes The Dovecot 2.2 package for AWS Linux was apparently setup to install all of the sockets in /usr/local/var/run/dovecot. This must have caused authentication issues because to get it working properly, I then had to add "path = /var/run/dovecot/auth-master” statement to the “auth" stanza in dovecot.conf file. Also, the fact that I do not use a “standard” SSH config was an issue early on but once I committed to allowing vmail to SSH into the old server, that part became moot. For security purposes, I will probably disable vmail SSH after the data is migrated. Questions First and foremost — any obvious issues here? Next, any advice and\or lessons learned with this type of migration? Finally, presuming this is the proper way to do this, will this migrate all mail content including Sent, Deleted, Drafts, etc.? Thanks in advance for taking the time and providing any feedback — very much appreciated...

1 0

Re: Dovecot permission denied errors on NFS after upgrade to 2.2.17
by Claudio Corvino 13 Jul '20

13 Jul '20

Hi Jochen, the ID has not changed, in addition the "permission denied" error is random, most of the time Dovecot works well. How can I check the mappings NFS uses? After the Debian upgrade I was using these NFS mount options: rw,user,rsize=8192,wsize=8192,timeo=30,intr Now trying to fix the problem I set "defaults" mount option, but nothing has changed. Thanks On 13/07/20 13:08, Jochen Bern wrote: > On 07/13/2020 12:57 PM, Claudio Corvino wrote: >> we just upgraded our mail server from Debian 8 to Debian 9, so our >> dovecot packages just got upgraded from version 2.2.13 to 2.2.17. > [...] >> Every directory and sub-dir under >> /mnt/mail-storage >> is assigned to vmail:vmail with >> drwx------ >> permission set. > Just a quick shot into the dark, you verified the ownerships on the NFS > *client*, not the NFS *server*, yes? Because NFS speaks UIDs and GIDs, > not their names, so if your Debian 9 installation assigned different IDs > to "vmail" ... > > (You might also want to check what mappings the NFS mount uses, > including possible *default* behaviour.) > > Good luck,

1 0

Dovecot permission denied errors on NFS after upgrade to 2.2.17
by Claudio Corvino 13 Jul '20

13 Jul '20

Hi everyone, we just upgraded our mail server from Debian 8 to Debian 9, so our dovecot packages just got upgraded from version 2.2.13 to 2.2.17. Now we have a lot of errors in our dovecot.log about permission denied (our Mailboxes are on NFS remote server since years without problems) like these: Jul 13 12:39:23 Error: imap(XXXXXXXXX): open(/mnt/mail-storage/XXXXXXXXX/Maildir/cur/1594378191.M653755P26498.ganimede,S=12716,W=12984:2,S) failed: Permission denied (euid=501(vmail) egid=501(vmail) missing +r perm: /mnt/mail-storage/XXXXXXXXX/Maildir/cur/1594378191.M653755P26498.ganimede,S=12716,W=12984:2,S stat(/mnt/mail-storage/XXXXXXXXX/Maildir/cur/1594378191.M653755P26498.ganimede,S=12716,W=12984:2,S) failed: Permission denied) For some user this is not a problem, for some other user this blocks their mail client (Thunderbird). We use vmail user for running Dovecot and I can't find a permission problem on the path indicated by the mail error, user vmail can read and write and uid and gid seems to be correct. Permissions on /mnt/mail-storage was drwx------ 94 vmail vmail 4096 ago 29 2019 mail-storage I just changed to drwxr-xr-x 94 root root 4096 ago 29 2019 mail-storage but nothing has changed. Every directory and sub-dir under /mnt/mail-storage is assigned to vmail:vmail with drwx------ permission set. If try to stat on /mnt/mail-storage/XXXXXXXXX/Maildir/cur/1594378191.M653755P26498.ganimede,S=12716,W=12984:2,S I get permission denied. We use LMTP and Postfix to deliver mail to mailbox. mail_debug=yes already enabled; mail_fsync is set to never (should I change to always?). Please could you give us help on the matter as I don't know where to look further. Thanks Claudio

1 0

Re: Please Help me
by Kishore Potnuru 13 Jul '20

13 Jul '20

Hi Vitalii, I am using "Maildir". Thanks Kishore Potnuru On Mon, Jul 13, 2020 at 10:32 AM Vitalii <vnagara(a)yandex.com> wrote: > On Sun, 12 Jul 2020 21:17:48 +0100 > Kishore Potnuru <kishore.reachme(a)gmail.com> wrote: > > > Hi All, > > > > I need to migrate the complete data & setup/environment from an old > > dovecot environment to a new dovecot environment. > > Hi Kishore, > I was wondering what mail format do you use Maildir/mdbox/sdbox? >

1 0

Please Help me
by Kishore Potnuru 13 Jul '20

13 Jul '20

Hi All, I need to migrate the complete data & setup/environment from an old dovecot environment to a new dovecot environment. Old environment details: ======================== Linux OS - Red Hat Enterprise Linux Server release 6.5 (Santiago) Dovecot version - 2.0.9 Postfix version - 2.6.6 New Environment details: ( 2 systems) ======================== Linux OS - Red Hat Enterprise Linux Server release 7.7 (Maipo) Dovecot version - 2.2.36 (1f10bfa63) Postfix version - 2.10.1 In the new environment, I have 2 servers. I have got 2 of the above servers with above configuration and need to create HA/Resilience. I know there is advanced versions in Redhat and Dovecot. As per my organisation's existing support/policy, that is what maximum supported RHEL and official version of dovecot as per RHEL 7.7. Now my questions are: 1. I will stop the dovecot/postfix services on the server in old environment. Is it possible to move/copy the complete configuration along with data (directories/sub-directories/users/groups/existing email in new or cur folders/complete email domains along with complete structure) to the other 2 servers in new env? Could you please suggest me the commands or steps follow that? 2. Now, With the above 2 servers, I would like to create the HA/Resilience. I know there is a Replication options which are there. Could you please provide me the steps/video, how it needs to be done? I have got the systems and I need to move/copy the environment to a new environment and create the HA/Resilience. I am not sure, how to proceed and what needs to be done clearly? I am stuck here. Please help me in this step by step procedure. Thanks, Kishore Potnuru

3 2

INBOX folders disappeared after upgrading
by Dave 12 Jul '20

12 Jul '20

Hi, tried to Google/etc to see what to tweak.. not finding anything helpful. So.. I've been running my private mail through a Linux server since approx year 2000. The OS has been various flavors of Fedora or CentOS, since for work, I have to spend all day supporting some sort of Red Hat flavor. So I run SquirrelMail on top of Dovecot and Postfix on CentOS 7, things have been great for like forever. I recently ran updates and all my INBOX folders disappeared. I have made no configuration changes in at least 5 years. I can't seem to resolve/figure out what's going on. I have backups to see everything before the update. I've noticed that my subscriptions file is missing all the folders, which are all in this file in the backups. If I repopulate this file with the names, the next time I access mail, they are all removed. Most of my mail is in folders, therefore I have access to almost none of it (can see new stuff coming in, but can't sort it anywhere). k, for the details.. I was running dovecot-2.2.10 (2.2.10-8.el7.x86_64) and was updated to dovecot-2.2.36 (2.2.36-3.el7_7.1.x86_64) with yum updates. # dovecot --version 2.2.36 (1f10bfa63) # dovecot -n # 2.2.36 (1f10bfa63): /etc/dovecot/dovecot.conf # OS: Linux 3.10.0-1062.18.1.el7.x86_64 x86_64 CentOS Linux release 7.7.1908 (Core) # Hostname: vm1.tech...com auth_mechanisms = plain login login_greeting = IMAP ready. mail_location = maildir:~/Maildir 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 { driver = pam } service auth { unix_listener /var/spool/postfix/private/auth { mode = 0600 user = postfix } } service imap-login { inet_listener imap { address = 127.0.0.1,68.139.25.150 } inet_listener imaps { address = 127.0.0.1,68.139.25.150 } } service pop3-login { inet_listener pop3 { port = 0 } inet_listener pop3s { address = 127.0.0.1,68.139.25.150 } } ssl = required ssl_cert = </etc/pki/tls/certs/mail.tech...com.crt ssl_cipher_list = ALL:!aNULL:!eNULL:!LOW:!EXP:!RC4 ssl_key = # hidden, use -P to show it ssl_prefer_server_ciphers = yes userdb { driver = passwd } Regards, -Dave

2 4

2.3.10.1 on OpenBSD
by Rupert Gallagher 12 Jul '20

12 Jul '20

Apart from a few warnings (attached), and a bit of patience, the compiler terminates without error. On patience, OBSD has two processes who took almost half the CPU when compiling: reaper and zerothread. Will look into the warnings, and the testing errors (also attached). Let see how it works on this machine. OpenBSD 6.7 (GENERIC.MP) #2: Thu Jun 4 09:55:08 MDT 2020 real mem = 17125511168 (16332MB) avail mem = 16593879040 (15825MB) bios0: Supermicro A2SDi-4C-HLN4F OpenBSD clang version 8.0.1 (tags/RELEASE_801/final) (based on LLVM 8.0.1) Target: amd64-unknown-openbsd6.7 Thread model: posix

3 6

Per-user sieve_before settings?
by Gionatan Danti 11 Jul '20

11 Jul '20

Hi all, I wonder if using a per-user sieve_before setting (ie: a relative path to user home, as ~/filter.sieve) is expected to work corretly. Full disclaimer: I am migrating an old CentOS 6.10 box with dovecot 2.0.9 and an old pigenhole version. I now want to redirect emails from old account to new account (I have a csv with old->new address pairs). My first approach using a single, big filter file somewhat works, but it is not optimal. I am currently setting sieve_before = /var/vmail/autoreply.sieve, and it that file I have something as: ... if header :contains "to" "aaa(a)olddomain.com" { redirect "aaa(a)newdomain.com"; stop; } if header :contains "to" "bbb(a)olddomain.com" { redirect "bbb(a)newdomain.com"; stop; } ... Problem is that whan an email has multiple to or cc, the filter is evaluated multiple times (one per recipient) and I end with multiple email copies on the same destination address. For example, sending and email to aaa(a)olddomain.com, cc bbb(a)olddomain.com is evaluated *two* times: when delivering the email to aaa(a)olddomain.com, with a corresponding redirect to aaa(a)newdomain.com, and when delivering the email to bbb(a)olddomain.com, with *another* redirect to aaa(a)newdomain.com (ending with two email copies). Using a per-user filter file solves the problem, as the filter is evaluated in the context of the right user only (ie: an email sent to aaa(a)olddomain.com, cc bbb(a)olddomain.com is evaluated only in aaa(a)olddomain.com context, with a corresponding single email on aaa(a)newdomain.com) However, I would avoid manipulating the already present per-user file (roundcube.sieve), as I need to add my custom rules on top of that file. Moreover, users would be able to disable the redirect filter. Using a per-user before_sieve filter file seems the right solution, *if* it works using multiple files rather than a single global one. If not, do you have any other suggestion/approach to share? Thanks. -- Danti Gionatan Supporto Tecnico Assyoma S.r.l. - www.assyoma.it [1] email: g.danti(a)assyoma.it - info(a)assyoma.it GPG public key ID: FF5F32A8

1 1

antispam
by Matthew Broadhead 10 Jul '20

10 Jul '20

in dovecot/conf.d/90-plugin.conf i have plugin { # man antispam #setting_name = value antispam_debug_target = syslog antispam_verbose_debug = 1 antispam_backend = pipe antispam_signature = X-DSPAM-Signature # action to take on mails without signature # (used with any backend requiring a signature) # (we recommend only setting this to 'move' after verifying that the # whole setup is working) # antispam_signature_missing = move # move silently without training antispam_signature_missing = error antispam_trash = Trash antispam_spam = Junk antispam_pipe_program_spam_arg = --spam antispam_pipe_program_notspam_arg = --ham antispam_pipe_program = /usr/bin/sa-learn antispam_pipe_program_args = --username=%Lu } it seems to be going into the database ok but it doesn't seem to be applying anything it is learning. might there be some configuration option missing?

1 0

Ms Exchange vs dovecot
by Marc Roos 10 Jul '20

10 Jul '20

I have recently been working/testing with exchange 2016 and started thinking if I should even migrate to this platform. I assume more people here have experience with exchange and this idea. I was wondering if this is possible with a dovecot setup 1. public folder can be implemented with a public mailbox? 2. authorize users via groups access to mailboxes/folders of the public folder/mailbox. I think I saw ACL's with dovecot, does this compare to 'folder permissions' 3. is it possible with sieve to apply a rule on any mailbox/folder? Thus if I 'drag' a message to a folder, the sieve rule is activated?

18 25

Dovecot FTS with Solrcloud
by Patrik Peng 10 Jul '20

10 Jul '20

Greetings We are looking into a solution to set up full text search for our multiple Dovecot instances. According to the Dovecot Wiki, fts_solr is one of the recommended plugins to use. Since we have more than just a few hundred mailboxes, I guess one Solr instance will not suffice. So I took a look at SolrCloud and set up a small cluster with three nodes and shards. I have no preceding experience with Solr or SolrCloud and now it's not clear to me, how dovecot can interact with this cluster. Has anyone ever tried to setup dovecot FTS with a SolrCloud cluster and is willing to share his findings? Regards Patrik

1 0

BUG report: dbox movealt doesn't move reverse (to default location)
by Vitalii 09 Jul '20

09 Jul '20

Hi, Here is the problem that occured: #sudo doveadm -D altmove -u vv(a)vito.pp.ua all works properly and moves all storage to alt dir. However, to move it back to default storage I add '-r' by manual: #sudo doveadm -D altmove -u vv(a)vito.pp.ua -r all That seems behave like the original command ignoring '-r'. my dovecot conf: # 2.3.4.1 (f79e8e7e4): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.4 () # OS: Linux 4.19.0-9-amd64 x86_64 Debian 10.4 # Hostname: qemu7.internetguru.ca auth_mechanisms = plain login disable_plaintext_auth = no imapc_features = rfc822.size fetch-headers imapc_host = imap.gmail.com imapc_port = 993 imapc_ssl = imaps imapc_user = %u listen = *,[::] log_timestamp = "%Y-%m-%d %H:%M:%S " mail_attachment_dir = /wd640/mdbox-att/%d/%n mail_max_userip_connections = 100 mail_prefetch_count = 20 mail_privileged_group = vmail passdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } plugin { quota = dict:user::file:/var/vmail/%d/%n/.quotausage sieve = /var/vmail/%d/%n/.sieve sieve_max_redirects = 25 } protocols = imap pop3 service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-userdb { group = vmail mode = 0600 user = vmail } user = root } service imap-login { client_limit = 1000 process_limit = 512 } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } service stats { unix_listener stats-reader { group = vmail mode = 0660 user = vmail } unix_listener stats-writer { group = vmail mode = 0660 user = vmail } } ssl_cert = </etc/postfix/smtpd.cert ssl_client_ca_dir = /etc/ssl/certs ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it userdb { driver = prefetch } userdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } protocol imap { mail_plugins = quota imap_quota } protocol pop3 { mail_plugins = quota pop3_uidl_format = %08Xu%08Xv } protocol lda { mail_plugins = sieve quota postmaster_address = postmaster(a)some.ca } protocol lmtp { mail_plugins = quota sieve postmaster_address = postmaster(a)some.ca } I am using debian 10. P.S. I have not found much information about dbox attachments commands. Seems none needs them.

1 0

Urgent Help required
by Kishore Potnuru 09 Jul '20

09 Jul '20

Hi All, I request your help on this. I have 2 dovecot test servers (IMAP protocol) installed with the following configuration. ============= [root@devap01 ~]# cat /etc/redhat-* Red Hat Enterprise Linux Server release 6.10 (Santiago) [root@devap01 ~]# dovecot --version 2.0.9 [root@devap01 ~]# postconf | grep mail_version mail_version = 2.6.6 =============== I have another server also "devap02" with the same configuration. Couple of points/questions/queries here. 1. I know these servers are having old dovecot versions. I would like to upgrade to the latest versions. Could you please suggest the steps for upgrading to the latest version in redhat (step by step details are helpful please) . If I upgrade to the latest version, will there be any impact on the existing configuration/setup? 2. Now I have added these 2 servers behind the Load Balancer. Enabled 110/143 ports on the Load Balancer FQDN (test.pop3.testing.com) and opened the firewall ports. Here I configured IMAP settings from microsoft outlook to see the emails. I gave the Incoming Mail Server & Outgoing mail server as "test.pop3.testing.com". It is configured without errors in Outlook. But I see these 2 types issues (shared storage & individual storage) a) individual separate storage - When I send 10 emails to LB FQDN ( test.pop3.testing.com) the emails are going to 2 backend servers. But when i see the emails from Outlook inbox, it shows 5 emails from one server for some time. After sometime it shows other 5 emails in the inbox. But, I am not able to see all 10 emails at same time in my inbox. Please suggest how to fix this issue? In this scenario, I have separate individual storage in both the servers. b) common shared storage - I have tried a different scenario also. I also have one common NFS storage. So, I have configured that storage in both the servers. So when I sent 10 emails, I see all the 10 emails from both the servers as it is common shared storage. But, I am not getting those 10 emails delivered into my Outlook. I have made all the configuration correctly. Please suggest what is the mistake here. Dovecot.conf ========================================================= [root@devap01 ~]# cat /etc/dovecot/dovecot.conf disable_plaintext_auth = no listen = * log_path = /var/log/dovecot.log mail_location = maildir:/r3/mail/virtual/%d/%n/Maildir/ passdb { args = /etc/dovecot/passwd driver = passwd-file } pop3_uidl_format = %g protocols = imap pop3 ssl = yes ssl_cert = </etc/pki/dovecot/certs/dovecot.pem ssl_key = </etc/pki/dovecot/private/dovecot.pem userdb { args = uid=vmail gid=vmail home=/r3/mail/virtual/%d/%n driver = static } mail_debug = no verbose_ssl = no ========================================================= Please help me here. Thanks, Kishore Potnuru

9 15

Dovecot - Xoauth2 - keycloak
by la.jolie＠paquerette 09 Jul '20

09 Jul '20

Hello, Still trying to make roundcube / Dovecot works with Keycloak. Dovecot can't seem to validate the access_token that Roundcube gave. ----- Jul 08 20:48:05 auth: Debug: http-client[1]: request [Req1: GET https://my.keycloak.host/auth/realms/test_saml/protocol/openid-connect/toke…] Sent header Jul 08 20:48:05 auth: Debug: http-client[1]: peer 11.22.33.44:443: No more requests to service for this peer (1 connections exist, 0 pending) Jul 08 20:48:05 auth: Debug: http-client[1]: conn 11.22.33.44:443 [0]: Got 404 response for request [Req1: GET https://my.keycloak.host/auth/realms/test_saml/protocol/openid-connect/toke…] (took 11 ms + 19 ms in queue) Jul 08 20:48:05 auth: Debug: oauth2(my.mail@whatever,::1,<Z2mDOfSpJJ8AAAAAAAAAAAAAAAAAAAAB>): oauth2: callback(0, Invalid token) ---- The access_token used by Dovecot is the right one. Dovecot also has the right login (my.mail@whatever) The Nginx and Keycloak logs show this: ---- - - [08/Jul/2020:23:25:18 +0200] "POST /auth/realms/test_saml/protocol/openid-connect/token HTTP/1.1" 200 3171 "-" "Guzzle/5.3.1 curl/7.64.0 PHP/7.3.14-1~deb10u1" - - [08/Jul/2020:23:42:05 +0200] "GET /auth/realms/test_saml/protocol/openid-connect/tokeneyJhbGciOiJFUzI1NiIsInR5cCIgOiAiSldUIiwia2lkIiA6ICJEZzR2aWtndzN2MWVpQVgxMU10YkFIaXRaUnM2R2RlVzN3b3hGTTBpd1NnIn0.eyJleHAiOjE1OTQyNDE0NjUsImlhdCI6MTU5NDI0MTI4NSwiYXV0aF90aW1lIjoxNTk0MjM0ODI3LCJqdGkiOiI0NjRlZjc5NS0yZDYzLTQzYjktYjU4My1iYTY2MmFkMWRhYzUiLCJpc3MiOiJodHRwczovL3Nzby5udWJvLmNvb3AvYXV0aC9yZWFsbXMvdGVzdF9zYW1sIiwiYXVkIjoiYWNjb3VudCIsInN1YiI6IjhlZWNiODVjLTZlMDYtNGZhNC1iYTAwLTdlMGRlM2MyMWYxNCIsInR5cCI6IkJlYXJlciIsImF6cCI6InJvdW5kY3ViZSIsInNlc3Npb25fc3RhdGUiOiJmOTYyNWM3OS02OTM5LTRkZjEtOGM2Yi1hYWM5Y2EzYWJkY2YiLCJhY3IiOiIwIiwiYWxsb3dlZC1vcmlnaW5zIjpbImh0dHA6Ly9yYy5udWJvLmRvbWFpbmVwdWJsaWMubmV0Il0sInJlYWxtX2FjY2VzcyI6eyJyb2xlcyI6WyJvZmZsaW5lX2FjY2VzcyIsInVtYV9hdXRob3JpemF0aW9uIl19LCJyZXNvdXJjZV9hY2Nlc3MiOnsiYWNjb3VudCI6eyJyb2xlcyI6WyJtYW5hZ2UtYWNjb3VudCIsIm1hbmFnZS1hY2NvdW50LWxpbmtzIiwidmlldy1wcm9maWxlIl19fSwic2NvcGUiOiJvcGVuaWQgbWljcm9wcm9maWxlLWp3dCBwcm9maWxlIGVtYWlsIG9mZmxpbmVfYWNjZXNzIiwidWlkIjoicXVlbmVubmkiLCJ1cG4iOiJxdWVuZW5uaSIsImVtYWlsX3ZlcmlmaWVkIjpmYWxzZSwibmFtZSI6Iktlbm55IExvdXZlYXV4IExvdXZlYXV4IiwiZ3JvdXBzIjpbIm9mZmxpbmVfYWNjZXNzIiwidW1hX2F1dGhvcml6YXRpb24iXSwicHJlZmVycmVkX3VzZXJuYW1lIjoicXVlbmVubmkiLCJnaXZlbl9uYW1lIjoiS2VubnkgTG91dmVhdXgiLCJmYW1pbHlfbmFtZSI6IkxvdXZlYXV4IiwiZW1haWwiOiJrZW5ueUBudWJvLnNpdGUifQ.TsUBiZ5nSTuA9ojr6bao5NQUHeNRmcYQZsC95rrhYca9FsFG4xG8mT53X9eOSNEqzRMJiPHaDuAh-3Bq8Rjdlg HTTP/1.1" 404 1465 "-" "dovecot-oauth2-passdb/2.3.4.1" DEBUG [org.jboss.resteasy.resteasy_jaxrs.i18n] (default task-2) RESTEASY002315: PathInfo: /realms/test_saml/protocol/openid-connect/tokeneyJhbGciOiJFUzI1N iIsInR5cCIgOiAiSldUIiwia2lkIiA6ICJEZzR2aWtndzN2MWVpQVgxMU10YkFIaXRaUnM2R2RlVzN3b3hGTTBpd1NnIn0.eyJleHAiOjE1OTQyNDQ3MDQsImlhdCI6MTU5NDI0NDUyNCwiYXV0aF90aW1lIjoxNTk0MjQ0MzQ3LCJqdGk iOiIyYTg3MjQ3NS0zMGMxLTRmMDctODg5Ny04YmQ4OTJjMGI1MjEiLCJpc3MiOiJodHRwczovL3Nzby5udWJvLmNvb3AvYXV0aC9yZWFsbXMvdGVzdF9zYW1sIiwiYXVkIjoiYWNjb3VudCIsInN1YiI6IjhlZWNiODVjLTZlMDYtNGZhN C1iYTAwLTdlMGRlM2MyMWYxNCIsInR5cCI6IkJlYXJlciIsImF6cCI6InJvdW5kY3ViZSIsInNlc3Npb25fc3RhdGUiOiJmMjY0OTQyMy0xNmZkLTQzMTgtYTVkYy04NWJhNmU3YTQ4MWYiLCJhY3IiOiIwIiwiYWxsb3dlZC1vcmlnaW5 zIjpbImh0dHA6Ly9yYy5udWJvLmRvbWFpbmVwdWJsaWMubmV0Il0sInJlYWxtX2FjY2VzcyI6eyJyb2xlcyI6WyJvZmZsaW5lX2FjY2VzcyIsInVtYV9hdXRob3JpemF0aW9uIl19LCJyZXNvdXJjZV9hY2Nlc3MiOnsiYWNjb3VudCI6e yJyb2xlcyI6WyJtYW5hZ2UtYWNjb3VudCIsIm1hbmFnZS1hY2NvdW50LWxpbmtzIiwidmlldy1wcm9maWxlIl19fSwic2NvcGUiOiJvcGVuaWQgbWljcm9wcm9maWxlLWp3dCBwcm9maWxlIGVtYWlsIG9mZmxpbmVfYWNjZXNzIiwidWl kIjoicXVlbmVubmkiLCJ1cG4iOiJxdWVuZW5uaSIsImVtYWlsX3ZlcmlmaWVkIjpmYWxzZSwibmFtZSI6Iktlbm55IExvdXZlYXV4IExvdXZlYXV4IiwiZ3JvdXBzIjpbIm9mZmxpbmVfYWNjZXNzIiwidW1hX2F1dGhvcml6YXRpb24iX SwicHJlZmVycmVkX3VzZXJuYW1lIjoicXVlbmVubmkiLCJnaXZlbl9uYW1lIjoiS2VubnkgTG91dmVhdXgiLCJmYW1pbHlfbmFtZSI6IkxvdXZlYXV4IiwiZW1haWwiOiJrZW5ueUBudWJvLnNpdGUifQ.TsUBiZ5nSTuA9ojr6bao5NQUHe NRmcYQZsC95rrhYca9FsFG4xG8mT53X9eOSNEqzRMJiPHaDuAh-3Bq8Rjdlg --- Dovecot does a GET request where the access_token is directly attached to the 'tokeninfo_url' option. Is that the correct/normal way? Shouldn't it be a POST with data passed as params? Or is it Keycloak that should accept that request? Thanks Kenny

2 1

Re: Urgent Help required
by Kishore Potnuru 08 Jul '20

08 Jul '20

Hi, Our organisation has dependencies. There is a separate team/department who creates the servers for us. When they build a new RHEL system, the system will come up with various in-house softwares/tools. Those tools are not compatible as of now with RHEL8. So, our organisation is going with redhat 7.7 only as of today which is supported for all in-house tools also. This is my current situation: 1) I have 2 test servers which are loaded with the following configuration. ============= [root@devap01 ~]# cat /etc/redhat-* Red Hat Enterprise Linux Server release 6.10 (Santiago) [root@devap01 ~]# dovecot --version 2.0.9 [root@devap01 ~]# postconf | grep mail_version mail_version = 2.6.6 =============== So, I would like to install the max possible dovecot version on the above servers for the testing purpose. I would like to implement the HA/Resilience with those 2 servers. I have shared storage and individual storage in this environment. But I am seeing some issues with both of them ( I explained details in my first email thread). please see if you can help. 2) If it is successful, I will get two RHEL 7.7 servers to implement the same in LIVE environment for HA/Resilience. First I am going with compatibility issues to resolve in my environment. Once that is resolved, I will go with HA/Resilience implementation. Please let me know if you need any more details. Thanks & Regards, Kishore Potnuru On Wed, Jul 8, 2020 at 8:57 PM Marc Roos <M.Roos(a)f1-outsourcing.eu> wrote: > > > >>> with broken or vulnerable software is there really a benefit? > >> > >> LTS distributions back port necessary patches > > >Then the OP should be able to update to a dovecot that doesn't have the > issue, right? > > I have no idea what his issue is, and why he is stuck even in specific > releases. I have been running dovecot on el6 and el7 for years and years > without issues. > > > > > > > >

2 1

RE: Urgent Help required
by Marc Roos 08 Jul '20

08 Jul '20

>>The other side of the question is, Why is the software always so "vulnerable" and "broken" in the first >>place as to be unsuitable for Long Term Support? >> >>If the software code worked when it was released some number of years ago, then why doesn't it still work >>the same way today as it it did when it was released? Whenever I hear people complain about computers and/or software. I always suggest them to use something like the abacus of 2000 bc. You should be glad for what they do for you ;) And since humans operate them, you will find annoyances as with doctors amputating the wrong limb.

1 0

Re: Urgent Help required
by Kishore Potnuru 08 Jul '20

08 Jul '20

Thank you for your reply. 1. Am i able to upgrade directly from 2.0 to 2.3? or I should go periodically from 2.0 to 2.1, then 2.1 to 2.2, then 2.2 to 2.3....? 2. could you please suggest me steps to pick the correct package to upgrade in the above version (2.1, 2.2, 2.3)? 3. which location i need to download the packages? 4. I am using redhat servers. Am i able to directly download and upgrade the software from my redhat linux server? please advise step-by-step instructions for this? Thanks, Kishore Potnuru On Wed, Jul 8, 2020 at 11:00 AM Apostolis Hardalias <a.hardalias(a)skroutz.gr> wrote: > > On 7/8/20 12:53 PM, Kishore Potnuru wrote: > > Hi All, > > > > I request your help on this. > > > > I have 2 dovecot test servers (IMAP protocol) installed with the > > following configuration. > > ============= > > [root@devap01 ~]# cat /etc/redhat-* > > Red Hat Enterprise Linux Server release 6.10 (Santiago) > > > > [root@devap01 ~]# dovecot --version > > 2.0.9 > > > > [root@devap01 ~]# postconf | grep mail_version > > mail_version = 2.6.6 > > =============== > > > > I have another server also "devap02" with the same configuration. > > > > Couple of points/questions/queries here. > > > > 1. I know these servers are having old dovecot versions. I would like > > to upgrade to the latest versions. Could you please suggest the steps > > for upgrading to the latest version in redhat (step by step details > > are helpful please) . If I upgrade to the latest version, will there > > be any impact on the existing configuration/setup? > > Check the documents posted here: > > https://doc.dovecot.org/installation_guide/upgrading/from-2.0-to-2.1/ > > https://doc.dovecot.org/installation_guide/upgrading/from-2.1-to-2.2/ > > https://doc.dovecot.org/installation_guide/upgrading/from-2.2-to-2.3/ > > Depending on your setup, you may also need to check for changes to > additional software (e.g. amavis) > > > > > 2. Now I have added these 2 servers behind the Load Balancer. Enabled > > 110/143 ports on the Load Balancer FQDN (test.pop3.testing.com > > <http://test.pop3.testing.com>) and opened the firewall ports. Here I > > configured IMAP settings from microsoft outlook to see the emails. I > > gave the Incoming Mail Server & Outgoing mail server as > > "test.pop3.testing.com <http://test.pop3.testing.com>". It is > > configured without errors in Outlook. But I see these 2 types issues > > (shared storage & individual storage) > > > > a) individual separate storage - When I send 10 emails to LB FQDN > > (test.pop3.testing.com <http://test.pop3.testing.com>), the emails are > > going to 2 backend servers. But when i see the emails from Outlook > > inbox, it shows 5 emails from one server for some time. After sometime > > it shows other 5 emails in the inbox. But, I am not able to see all 10 > > emails at same time in my inbox. Please suggest how to fix this issue? > > In this scenario, I have separate individual storage in both the servers. > > I'm not sure if you've set it up already because it's unclear from the > configuration you posted but, you may wanna have a look at: > https://wiki.dovecot.org/Replication > > I suggest using replication after you've upgraded since earlier versions > of dovecot had a few issues. > > > > b) common shared storage - I have tried a different scenario also. > > I also have one common NFS storage. So, I have configured that storage > > in both the servers. So when I sent 10 emails, I see all the 10 emails > > from both the servers as it is common shared storage. But, I am not > > getting those 10 emails delivered into my Outlook. I have made all the > > configuration correctly. Please suggest what is the mistake here. > > > > Dovecot.conf > > ========================================================= > > > > [root@devap01 ~]# cat /etc/dovecot/dovecot.conf > > disable_plaintext_auth = no > > > > listen = * > > log_path = /var/log/dovecot.log > > mail_location = maildir:/r3/mail/virtual/%d/%n/Maildir/ > > passdb { > > args = /etc/dovecot/passwd > > driver = passwd-file > > } > > pop3_uidl_format = %g > > protocols = imap pop3 > > ssl = yes > > ssl_cert = </etc/pki/dovecot/certs/dovecot.pem > > ssl_key = </etc/pki/dovecot/private/dovecot.pem > > > > userdb { > > args = uid=vmail gid=vmail home=/r3/mail/virtual/%d/%n > > driver = static > > } > > mail_debug = no > > verbose_ssl = no > > ========================================================= > > > > Please help me here. > > > > Thanks, > > Kishore Potnuru >

1 1

Dovecot Maildirs multi language
by Luca Müller 07 Jul '20

07 Jul '20

Hello, I'm hosting a few customers on a dovecot Server. Most users speak german and have german as their main language. I configured the IMAP Foldernames in a Dovecot configuration file like this: ##### root@srv04:~# cat /etc/dovecot/conf.d/105-mailboxes.conf imap_capability = +XLIST namespace inbox { inbox = yes location = separator = / mailbox "Entwürfe" { auto = subscribe special_use = \Drafts auto=subscribe } mailbox Junk-E-Mail { special_use = \Junk auto=subscribe } mailbox "Gelöschte Elemente" { special_use = \Trash auto=subscribe } mailbox "Gesendete Elemente" { special_use = \Sent auto=subscribe } mailbox Archive { special_use = \Archive auto=subscribe } } ##### Dovecot Version: 2.3.10 (0da0eff44) ##### Is it possible to change this configuration for specific users or to provide multi language support somehow? Thanks in advance. Best regards, Luca

4 4

dovecot oauth
by la.jolie＠paquerette 06 Jul '20

06 Jul '20

Hello, I'm trying to configure roundcube / dovecot to work with keycloak. I activated xoauth2 oauthbearer in dovecot. But a problem occurs when dovecot tries to contact the keycloak server (logs are below). My problem looks like this one: https://dovecot.org/pipermail/dovecot/2019-December/117768.html The response to this problem was about a bug in oauth driver (https://dovecot.org/pipermail/dovecot/2019-December/117787.html) Mizuki was using Dovecot v2.2.36 (1f10bfa63) I have Dovecot Dovecot v2.3.4.1 (f79e8e7e4) I'm wondering if this bug is still present in my version or if I have another problem. Both my servers (dovecot and keycloak) are using let's encrypt certificates. I tried to configure Keycloak with nginx proxy and without it (access via port 8443) (in case the problem came from the ssl config on the keycloak server), but still the same error. If the bug is fixed, then could someone tell me what do I have to put in the option tls_ca_cert_file? I tried with /etc/letsencrypt/live/my.host/chain.pem and also certs I got from let's encrypt website (https://letsencrypt.org/certificates/ / tried ISRG Root X1 (self-signed) & Let’s Encrypt Authority X3 (IdenTrust cross-signed) & Let’s Encrypt Authority X3 (Signed by ISRG Root X1)) But I always have the same error. Thanks, Kenny My configs: - I'm on a Debian Buster with Dovecot / postfix / roundcube - dovecot -n : --- # 2.3.4.1 (f79e8e7e4): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.4 () # OS: Linux 4.19.0-5-cloud-amd64 x86_64 Debian 10.4 auth_debug = yes auth_mechanisms = xoauth2 oauthbearer login auth_verbose = yes debug_log_path = /var/log/dovecot-debug.log first_valid_gid = 10000 first_valid_uid = 10000 info_log_path = /var/log/dovecot.log last_valid_gid = 20000 last_valid_uid = 20000 lda_mailbox_autocreate = yes log_path = /var/log/dovecot.log mail_debug = yes mail_gid = mail mail_location = maildir:~/Maildir mail_privileged_group = mail namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } passdb { args = /etc/dovecot/dovecot-oauth2.conf.ext driver = oauth2 mechanisms = xoauth2 oauthbearer } plugin { sieve = file:~/sieve;active=~/.dovecot.sieve } protocols = " imap" service auth { unix_listener /var/spool/postfix/private/auth { mode = 0600 user = postfix } unix_listener auth-master { mode = 0600 user = mail } unix_listener auth-userdb { mode = 0600 user = mail } } service stats { unix_listener stats-reader { mode = 0600 user = mail } unix_listener stats-writer { mode = 0600 user = mail } } ssl_cert = </etc/letsencrypt/live/my.host/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 ssl_prefer_server_ciphers = yes ssl_require_crl = no userdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } userdb { args = gid=mail home=/var/mail/%u driver = static } verbose_ssl = yes protocol lda { info_log_path = /var/log/dovecot-deliver.log log_path = /var/log/dovecot-deliver-errors.log } ------ - dovecot-oauth2.conf.ext ----- tokeninfo_url = https://my.keycloak.host/auth/realms/test_saml/protocol/openid-connect/token introspection_mode = post introspection_url = https://my.keycloak.host/auth/realms/test_saml/protocol/openid-connect/toke… username_attribute = email tls_ca_cert_file = /etc/letsencrypt/live/my.host/chain.pem #tls_ca_cert_file = /etc/ssl/certs/letsencrypt.pem #active_attribute = enableMail #active_value = TRUE debug = yes rawlog_dir = /tmp/oauth2 ----- * Logs: ------- Jul 04 17:00:12 auth: Debug: oauth2(my.mail@whatever,::1,<fG8uk6CpBJ0AAAAAAAAAAAAAAAAAAAAB>): oauth2: Making token validation lookup to https://my.keycloak.host/auth/realms/test_saml/protocol/openid-connect/token Jul 04 17:00:12 auth: Debug: http-client: host my.keycloak.host: Host created Jul 04 17:00:12 auth: Debug: http-client: host my.keycloak.host: Host session created Jul 04 17:00:12 auth: Debug: http-client: host my.keycloak.host: IPs have expired; need to refresh DNS lookup Jul 04 17:00:12 auth: Debug: http-client: host my.keycloak.host: Performing asynchronous DNS lookup Jul 04 17:00:12 auth: Debug: http-client[1]: request [Req1: GET https://my.keycloak.host/auth/realms/test_saml/protocol/openid-connect/toke…... (long token)]: Submitted (requests left=1) Jul 04 17:00:12 auth: Debug: http-client: host my.keycloak.host: DNS lookup successful; got 1 IPs Jul 04 17:00:12 auth: Debug: http-client: peer 151.62.56.14 (shared): Peer created Jul 04 17:00:12 auth: Debug: http-client: peer 151.62.56.14: Peer pool created Jul 04 17:00:12 auth: Debug: http-client[1]: peer 151.62.56.14: Peer created Jul 04 17:00:12 auth: Debug: http-client[1]: queue https://my.keycloak.host: Setting up connection to 151.62.56.14 (SSL=my.keycloak.host) (1 requests pending) Jul 04 17:00:12 auth: Debug: http-client[1]: peer 151.62.56.14: Linked queue https://my.keycloak.host (1 queues linked) Jul 04 17:00:12 auth: Debug: http-client[1]: queue https://my.keycloak.host: Started new connection to 151.62.56.14 (SSL=my.keycloak.host) Jul 04 17:00:12 auth: Debug: http-client[1]: peer 151.62.56.14: Creating 1 new connections to handle requests (already 0 usable, connecting to 0, closing 0) Jul 04 17:00:12 auth: Debug: http-client[1]: peer 151.62.56.14: Making new connection 1 of 1 (0 connections exist, 0 pending) Jul 04 17:00:12 auth: Debug: http-client[1]: conn 151.62.56.14 [0]: (151.62.56.14): Connecting Jul 04 17:00:12 auth: Debug: http-client[1]: conn 151.62.56.14 [0]: (151.62.56.14): Waiting for connect (fd=22) to finish for max 0 msecs Jul 04 17:00:12 auth: Debug: http-client[1]: conn 151.62.56.14 [0]: HTTPS connection created (1 parallel connections exist) Jul 04 17:00:12 auth: Debug: http-client[1]: conn 151.62.56.14 [0]: (151.62.56.14): Client connected (fd=22) Jul 04 17:00:12 auth: Debug: http-client[1]: conn 151.62.56.14 [0]: Connected Jul 04 17:00:12 auth: Debug: http-client[1]: conn 151.62.56.14 [0]: Starting SSL handshake Jul 04 17:00:12 auth: Debug: my.keycloak.host: SSL: where=0x10, ret=1: before SSL initialization Jul 04 17:00:12 auth: Debug: my.keycloak.host: SSL: where=0x1001, ret=1: before SSL initialization Jul 04 17:00:12 auth: Debug: my.keycloak.host: SSL: where=0x1001, ret=1: SSLv3/TLS write client hello Jul 04 17:00:12 auth: Debug: my.keycloak.host: SSL: where=0x1002, ret=-1: SSLv3/TLS write client hello Jul 04 17:00:12 auth: Debug: my.keycloak.host: SSL: where=0x1002, ret=-1: SSLv3/TLS write client hello Jul 04 17:00:12 auth: Debug: my.keycloak.host: SSL: where=0x1001, ret=1: SSLv3/TLS write client hello Jul 04 17:00:12 auth: Debug: my.keycloak.host: SSL: where=0x1001, ret=1: SSLv3/TLS read server hello Jul 04 17:00:12 auth: Debug: my.keycloak.host: SSL error: Received invalid SSL certificate: unable to get issuer certificate: /C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3 Jul 04 17:00:12 auth: Debug: my.keycloak.host: SSL: where=0x1001, ret=1: SSLv3/TLS read server certificate Jul 04 17:00:12 auth: Debug: my.keycloak.host: SSL: where=0x1001, ret=1: SSLv3/TLS read server key exchange Jul 04 17:00:12 auth: Debug: my.keycloak.host: SSL: where=0x1001, ret=1: SSLv3/TLS read server done Jul 04 17:00:12 auth: Debug: my.keycloak.host: SSL: where=0x1001, ret=1: SSLv3/TLS write client key exchange Jul 04 17:00:12 auth: Debug: my.keycloak.host: SSL: where=0x1001, ret=1: SSLv3/TLS write change cipher spec Jul 04 17:00:12 auth: Debug: my.keycloak.host: SSL: where=0x1001, ret=1: SSLv3/TLS write finished Jul 04 17:00:12 auth: Debug: my.keycloak.host: SSL: where=0x1002, ret=-1: SSLv3/TLS write finished Jul 04 17:00:12 auth: Debug: my.keycloak.host: SSL: where=0x1002, ret=-1: SSLv3/TLS write finished ==> dovecot.log <== Jul 04 17:00:12 auth: Info: Received invalid SSL certificate: unable to get issuer certificate: /C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3 ==> dovecot-debug.log <== Jul 04 17:00:12 auth: Debug: my.keycloak.host: SSL: where=0x1002, ret=-1: SSLv3/TLS write finished Jul 04 17:00:12 auth: Debug: my.keycloak.host: SSL: where=0x1001, ret=1: SSLv3/TLS write finished Jul 04 17:00:12 auth: Debug: my.keycloak.host: SSL: where=0x1001, ret=1: SSLv3/TLS read change cipher spec Jul 04 17:00:12 auth: Debug: my.keycloak.host: SSL: where=0x1001, ret=1: SSLv3/TLS read finished Jul 04 17:00:12 auth: Debug: my.keycloak.host: SSL: where=0x20, ret=1: SSL negotiation finished successfully Jul 04 17:00:12 auth: Debug: my.keycloak.host: SSL: where=0x1002, ret=1: SSL negotiation finished successfully Jul 04 17:00:12 auth: Debug: my.keycloak.host: SSL error: Received invalid SSL certificate: unable to get issuer certificate: /C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3 Jul 04 17:00:12 auth: Debug: http-client[1]: peer 151.62.56.14: Connection failed (1 connections exist, 0 pending) Jul 04 17:00:12 auth: Debug: http-client: peer 151.62.56.14: Failed to make connection (1 connections exist, 0 pending) Jul 04 17:00:12 auth: Debug: http-client[1]: peer 151.62.56.14: Failed to establish any connection within our peer pool: SSL handshaking with 151.62.56.14 failed: read(SSL 151.62.56.14) failed: Received invalid SSL certificate: unable to get issuer certificate: /C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3 (1 connections exist, 0 pending) Jul 04 17:00:12 auth: Debug: http-client[1]: queue https://my.keycloak.host: Failed to set up connection to 151.62.56.14 (SSL=my.keycloak.host): SSL handshaking with 151.62.56.14 failed: read(SSL 151.62.56.14) failed: Received invalid SSL certificate: unable to get issuer certificate: /C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3 (1 peers pending, 1 requests pending) Jul 04 17:00:12 auth: Debug: http-client[1]: queue https://my.keycloak.host: Failed to set up any connection; failing all queued requests Jul 04 17:00:12 auth: Debug: http-client[1]: peer 151.62.56.14: Unlinked queue https://my.keycloak.host (0 queues linked) Jul 04 17:00:12 auth: Debug: http-client[1]: request [Req1: GET https://my.keycloak.host/auth/realms/test_saml/protocol/openid-connect/toke…... (long token)]: Error: 9003 SSL handshaking with 151.62.56.14 failed: read(SSL 151.62.56.14) failed: Received invalid SSL certificate: unable to get issuer certificate: /C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3 Jul 04 17:00:12 auth: Debug: http-client[1]: queue https://my.keycloak.host: Dropping request [Req1: GET https://my.keycloak.host/auth/realms/test_saml/protocol/openid-connect/toke…... (long token)] Jul 04 17:00:12 auth: Debug: oauth2(my.mail@whatever,::1,<fG8uk6CpBJ0AAAAAAAAAAAAAAAAAAAAB>): oauth2: callback(-1, SSL handshaking with 151.62.56.14 failed: read(SSL 151.62.56.14) failed: Received invalid SSL certificate: unable to get issuer certificate: /C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3) ==> dovecot.log <== Jul 04 17:00:12 auth: Error: oauth2(my.mail@whatever,::1,<fG8uk6CpBJ0AAAAAAAAAAAAAAAAAAAAB>): oauth2 failed: SSL handshaking with 151.62.56.14 failed: read(SSL 151.62.56.14) failed: Received invalid SSL certificate: unable to get issuer certificate: /C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3 ==> dovecot-debug.log <== Jul 04 17:00:12 auth: Debug: http-client[1]: request [Req1: GET https://my.keycloak.host/auth/realms/test_saml/protocol/openid-connect/toke…... (long token)]: Destroy (requests left=1) Jul 04 17:00:12 auth: Debug: http-client[1]: request [Req1: GET https://my.keycloak.host/auth/realms/test_saml/protocol/openid-connect/toke…... (long token)]: Free (requests left=0) Jul 04 17:00:12 auth: Debug: http-client[1]: conn 151.62.56.14 [0]: SSL handshaking with 151.62.56.14 failed: read(SSL 151.62.56.14) failed: Received invalid SSL certificate: unable to get issuer certificate: /C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3 Jul 04 17:00:12 auth: Debug: http-client[1]: conn 151.62.56.14 [0]: Connection close Jul 04 17:00:12 auth: Debug: http-client[1]: conn 151.62.56.14 [0]: Connection disconnect Jul 04 17:00:12 auth: Debug: http-client[1]: conn 151.62.56.14 [0]: (151.62.56.14): Disconnected: Connection closed: Received invalid SSL certificate: unable to get issuer certificate: /C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3 (fd=22) Jul 04 17:00:12 auth: Debug: my.keycloak.host: SSL error: Received invalid SSL certificate: unable to get issuer certificate: /C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3 Jul 04 17:00:12 auth: Debug: http-client[1]: conn 151.62.56.14 [0]: Detached peer Jul 04 17:00:12 auth: Debug: http-client[1]: conn 151.62.56.14 [0]: Connection destroy -------

2 4

export of information about mail into csv
by Marcel Blenkers 05 Jul '20

05 Jul '20

3 3

Quota: How/where to set/change
by Frank Elsner 03 Jul '20

03 Jul '20

Hi experts. in the output of imapsync I found: Host2: found quota, presented in raw IMAP Sending: 7 GETQUOTAROOT INBOX Sent 22 bytes Read: * QUOTAROOT INBOX "User quota" * QUOTA "User quota" (STORAGE 420325 1953125) 7 OK Getquotaroot completed (0.001 + 0.000 secs). Host2: Quota current storage is 430412800 bytes. Limit is 2000000000 bytes. So 21.52 % full Host2 is under my control and running dovecot-2.3.10.1. I need to increase the quota above 2 GB but don't know where it comes from and therefor don't know what to do. This is the doveconf -a: | # 2.3.10.1 (a3d0e1171): /usr/local/dovecot/etc/dovecot/dovecot.conf | # OS: Linux 5.7.6-201.fc32.x86_64 x86_64 Fedora release 32 (Thirty Two) ext3 | # Hostname: christo.fritz.box | # NOTE: Send doveconf -n output instead when asking for help. | auth_anonymous_username = anonymous | auth_cache_negative_ttl = 1 hours | auth_cache_size = 0 | auth_cache_ttl = 1 hours | auth_cache_verify_password_with_worker = no | auth_debug = no | auth_debug_passwords = no | auth_default_realm = | auth_failure_delay = 2 secs | auth_gssapi_hostname = | auth_krb5_keytab = | auth_master_user_separator = | auth_mechanisms = plain login | auth_policy_check_after_auth = yes | auth_policy_check_before_auth = yes | auth_policy_hash_mech = sha256 | auth_policy_hash_nonce = | auth_policy_hash_truncate = 12 | auth_policy_log_only = no | auth_policy_reject_on_fail = no | auth_policy_report_after_auth = yes | auth_policy_request_attributes = login=%{requested_username} pwhash=%{hashed_password} remote=%{rip} device_id=%{client_id} protocol=%s | auth_policy_server_api_header = | auth_policy_server_timeout_msecs = 2000 | auth_policy_server_url = | auth_proxy_self = | auth_realms = | auth_socket_path = auth-userdb | auth_ssl_require_client_cert = no | auth_ssl_username_from_cert = no | auth_stats = no | auth_use_winbind = no | auth_username_chars = abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@ | auth_username_format = %Lu | auth_username_translation = | auth_verbose = no | auth_verbose_passwords = no | auth_winbind_helper_path = /usr/bin/ntlm_auth | auth_worker_max_count = 30 | base_dir = /var/run/dovecot | config_cache_size = 1 M | debug_log_path = | default_client_limit = 1024 | default_idle_kill = 1 mins | default_internal_group = dovecot | default_internal_user = dovecot | default_login_user = dovenull | default_process_limit = 256 | default_vsz_limit = 512 M | deliver_log_format = msgid=%m: %$ | dict_db_config = | director_flush_socket = | director_mail_servers = | director_max_parallel_kicks = 100 | director_max_parallel_moves = 100 | director_output_buffer_size = 10 M | director_ping_idle_timeout = 30 secs | director_ping_max_timeout = 1 mins | director_servers = | director_user_expire = 15 mins | director_user_kick_delay = 2 secs | director_username_hash = %Lu | disable_plaintext_auth = yes | dotlock_use_excl = yes | doveadm_allowed_commands = | doveadm_api_key = | doveadm_http_rawlog_dir = | doveadm_password = | doveadm_port = 0 | doveadm_socket_path = doveadm-server | doveadm_ssl = no | doveadm_username = doveadm | doveadm_worker_count = 0 | dsync_alt_char = _ | dsync_commit_msgs_interval = 100 | dsync_features = | dsync_hashed_headers = Date Message-ID | dsync_remote_cmd = ssh -l%{login} %{host} doveadm dsync-server -u%u -U | first_valid_gid = 1 | first_valid_uid = 200 | haproxy_timeout = 3 secs | haproxy_trusted_networks = | hostname = | imap_capability = | imap_client_workarounds = | imap_fetch_failure = disconnect-immediately | imap_hibernate_timeout = 0 | imap_id_log = | imap_id_retain = no | imap_id_send = name * | imap_idle_notify_interval = 2 mins | imap_literal_minus = no | imap_logout_format = in=%i out=%o deleted=%{deleted} expunged=%{expunged} trashed=%{trashed} hdr_count=%{fetch_hdr_count} hdr_bytes=%{fetch_hdr_bytes} body_count=%{fetch_body_count} body_bytes=%{fetch_body_bytes} | imap_max_line_length = 64 k | imap_metadata = no | imap_urlauth_host = | imap_urlauth_logout_format = in=%i out=%o | imap_urlauth_port = 143 | imapc_cmd_timeout = 5 mins | imapc_connection_retry_count = 1 | imapc_connection_retry_interval = 1 secs | imapc_features = | imapc_host = | imapc_list_prefix = | imapc_master_user = | imapc_max_idle_time = 29 mins | imapc_max_line_length = 0 | imapc_password = | imapc_port = 143 | imapc_rawlog_dir = | imapc_sasl_mechanisms = | imapc_ssl = no | imapc_ssl_verify = yes | imapc_user = | import_environment = TZ CORE_OUTOFMEM CORE_ERROR | info_log_path = | instance_name = dovecot | last_valid_gid = 0 | last_valid_uid = 65534 | lda_mailbox_autocreate = no | lda_mailbox_autosubscribe = no | lda_original_recipient_header = | libexec_dir = /usr/local/dovecot/libexec/dovecot | listen = * | lmtp_add_received_header = yes | lmtp_client_workarounds = | lmtp_hdr_delivery_address = final | lmtp_proxy = no | lmtp_proxy_rawlog_dir = | lmtp_rawlog_dir = | lmtp_rcpt_check_quota = no | lmtp_save_to_detail_mailbox = yes | lmtp_user_concurrency_limit = 0 | lock_method = fcntl | log_core_filter = | log_debug = | log_path = syslog | log_timestamp = "%b %d %H:%M:%S " | login_access_sockets = | login_greeting = m28a.ddns.net - IMAPs Service (dovecot) ready. | login_log_format = %$: %s | login_log_format_elements = %u %r %c | login_plugin_dir = /usr/local/dovecot/lib/dovecot/login | login_plugins = | login_proxy_max_disconnect_delay = 0 | login_proxy_notify_path = proxy-notify | login_source_ips = | login_trusted_networks = | mail_access_groups = | mail_always_cache_fields = | mail_attachment_detection_options = | mail_attachment_dir = | mail_attachment_fs = sis posix | mail_attachment_hash = %{sha1} | mail_attachment_min_size = 128 k | mail_attribute_dict = | mail_cache_compress_continued_percentage = 200 | mail_cache_compress_delete_percentage = 20 | mail_cache_compress_header_continue_count = 4 | mail_cache_compress_min_size = 32 k | mail_cache_fields = flags | mail_cache_min_mail_count = 0 | mail_cache_record_max_size = 64 k | mail_cache_unaccessed_field_drop = 30 days | mail_chroot = | mail_debug = no | mail_fsync = optimized | mail_full_filesystem_access = no | mail_gid = | mail_home = | mail_index_log2_max_age = 2 days | mail_index_log_rotate_max_size = 1 M | mail_index_log_rotate_min_age = 5 mins | mail_index_log_rotate_min_size = 32 k | mail_index_rewrite_max_log_bytes = 128 k | mail_index_rewrite_min_log_bytes = 8 k | mail_location = maildir:/var/spool/mail/%u:LAYOUT=fs | mail_log_prefix = "%Us(%u,%r): " | mail_max_keyword_length = 50 | mail_max_lock_timeout = 0 | mail_max_userip_connections = 10 | mail_never_cache_fields = imap.envelope | mail_nfs_index = no | mail_nfs_storage = no | mail_plugin_dir = /usr/dovecot/lib/dovecot/ | mail_plugins = notify quota fts fts_squat acl | mail_prefetch_count = 0 | mail_privileged_group = | mail_save_crlf = no | mail_server_admin = | mail_server_comment = | mail_shared_explicit_inbox = no | mail_sort_max_read_count = 0 | mail_temp_dir = /tmp | mail_temp_scan_interval = 1 weeks | mail_uid = | mail_vsize_bg_after_count = 0 | mailbox_idle_check_interval = 30 secs | mailbox_list_index = yes | mailbox_list_index_include_inbox = no | mailbox_list_index_very_dirty_syncs = no | maildir_broken_filename_sizes = no | maildir_copy_with_hardlinks = yes | maildir_empty_new = no | maildir_stat_dirs = no | maildir_very_dirty_syncs = no | master_user_separator = | mbox_dirty_syncs = yes | mbox_dotlock_change_timeout = 2 mins | mbox_lazy_writes = yes | mbox_lock_timeout = 5 mins | mbox_md5 = apop3d | mbox_min_index_size = 0 | mbox_read_locks = fcntl | mbox_very_dirty_syncs = no | mbox_write_locks = dotlock fcntl | mdbox_preallocate_space = no | mdbox_rotate_interval = 0 | mdbox_rotate_size = 10 M | mmap_disable = no | namespace inbox { | disabled = no | hidden = no | ignore_on_failure = no | inbox = yes | list = yes | location = | mailbox Drafts { | auto = no | autoexpunge = 0 | autoexpunge_max_mails = 0 | comment = | driver = | special_use = \Drafts | } | mailbox Gesendet { | auto = no | autoexpunge = 0 | autoexpunge_max_mails = 0 | comment = | driver = | special_use = \Sent | } | mailbox SPAM { | auto = no | autoexpunge = 0 | autoexpunge_max_mails = 0 | comment = | driver = | special_use = \Junk | } | mailbox Sent { | auto = no | autoexpunge = 0 | autoexpunge_max_mails = 0 | comment = | driver = | special_use = \Sent | } | mailbox Trash { | auto = no | autoexpunge = 0 | autoexpunge_max_mails = 0 | comment = | driver = | special_use = \Trash | } | order = 0 | prefix = | separator = | subscriptions = yes | type = private | } | old_stats_carbon_interval = 30 secs | old_stats_carbon_name = | old_stats_carbon_server = | old_stats_command_min_time = 1 mins | old_stats_domain_min_time = 12 hours | old_stats_ip_min_time = 12 hours | old_stats_memory_limit = 16 M | old_stats_session_min_time = 15 mins | old_stats_user_min_time = 1 hours | passdb { | args = dovecot | auth_verbose = default | default_fields = | deny = no | driver = pam | master = no | mechanisms = | name = | override_fields = | pass = no | result_failure = continue | result_internalfail = continue | result_success = return-ok | skip = never | username_filter = | } | plugin { | fts = squat | fts_squat = partial=4 full=10 | mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename flag_change append | mail_log_fields = uid box from subject msgid size flags | mail_log_group_events = yes | quota = maildir:User quota | quota_rule = ?:storage=5G | quota_rule2 = Trash:storage=+100M | } | pop3_client_workarounds = | pop3_delete_type = default | pop3_deleted_flag = | pop3_enable_last = no | pop3_fast_size_lookups = no | pop3_lock_session = no | pop3_logout_format = top=%t/%p, retr=%r/%b, del=%d/%m, size=%s | pop3_no_flag_updates = no | pop3_reuse_xuidl = no | pop3_save_uidl = no | pop3_uidl_duplicates = allow | pop3_uidl_format = %08Xu%08Xv | pop3c_features = | pop3c_host = | pop3c_master_user = | pop3c_password = | pop3c_port = 110 | pop3c_quick_received_date = no | pop3c_rawlog_dir = | pop3c_ssl = no | pop3c_ssl_verify = yes | pop3c_user = %u | postmaster_address = mailonator(a)mailbox.org | protocols = imap | quota_full_tempfail = no | rawlog_dir = | recipient_delimiter = + | rejection_reason = Your message to <%t> was automatically rejected:%n%r | rejection_subject = Rejected: %s | replication_dsync_parameters = -d -N -l 30 -U | replication_full_sync_interval = 1 days | replication_max_conns = 10 | replicator_host = replicator | replicator_port = 0 | sendmail_path = /usr/sbin/sendmail | service aggregator { | chroot = . | client_limit = 0 | drop_priv_before_exec = no | executable = aggregator | extra_groups = | fifo_listener replication-notify-fifo { | group = | mode = 0600 | user = | } | group = | idle_kill = 0 | privileged_group = | process_limit = 0 | process_min_avail = 0 | protocol = | service_count = 0 | type = | unix_listener replication-notify { | group = | mode = 0600 | user = | } | user = $default_internal_user | vsz_limit = 18446744073709551615 B | } | service anvil { | chroot = empty | client_limit = 1024 | drop_priv_before_exec = no | executable = anvil | extra_groups = | group = | idle_kill = 4294967295 secs | privileged_group = | process_limit = 1 | process_min_avail = 1 | protocol = | service_count = 0 | type = anvil | unix_listener anvil-auth-penalty { | group = | mode = 0600 | user = | } | unix_listener anvil { | group = | mode = 0600 | user = | } | user = $default_internal_user | vsz_limit = 18446744073709551615 B | } | service auth-worker { | chroot = | client_limit = 1 | drop_priv_before_exec = no | executable = auth -w | extra_groups = | group = | idle_kill = 0 | privileged_group = | process_limit = 0 | process_min_avail = 0 | protocol = | service_count = 1 | type = | unix_listener auth-worker { | group = | mode = 0600 | user = $default_internal_user | } | user = | vsz_limit = 18446744073709551615 B | } | service auth { | chroot = | client_limit = 0 | drop_priv_before_exec = no | executable = auth | extra_groups = | group = | idle_kill = 0 | privileged_group = | process_limit = 1 | process_min_avail = 0 | protocol = | service_count = 0 | type = | unix_listener auth-client { | group = exim | mode = 0660 | user = exim | } | unix_listener auth-login { | group = | mode = 0600 | user = $default_internal_user | } | unix_listener auth-master { | group = | mode = 0600 | user = | } | unix_listener auth-userdb { | group = | mode = 0666 | user = $default_internal_user | } | unix_listener login/login { | group = | mode = 0666 | user = | } | unix_listener token-login/tokenlogin { | group = | mode = 0666 | user = | } | user = $default_internal_user | vsz_limit = 18446744073709551615 B | } | service config { | chroot = | client_limit = 0 | drop_priv_before_exec = no | executable = config | extra_groups = | group = | idle_kill = 4294967295 secs | privileged_group = | process_limit = 0 | process_min_avail = 0 | protocol = | service_count = 0 | type = config | unix_listener config { | group = | mode = 0600 | user = | } | user = | vsz_limit = 18446744073709551615 B | } | service dict-async { | chroot = | client_limit = 0 | drop_priv_before_exec = no | executable = dict | extra_groups = | group = | idle_kill = 0 | privileged_group = | process_limit = 0 | process_min_avail = 0 | protocol = | service_count = 0 | type = | unix_listener dict-async { | group = $default_internal_group | mode = 0660 | user = | } | user = $default_internal_user | vsz_limit = 18446744073709551615 B | } | service dict { | chroot = | client_limit = 1 | drop_priv_before_exec = no | executable = dict | extra_groups = | group = | idle_kill = 0 | privileged_group = | process_limit = 0 | process_min_avail = 0 | protocol = | service_count = 0 | type = | unix_listener dict { | group = $default_internal_group | mode = 0660 | user = | } | user = $default_internal_user | vsz_limit = 18446744073709551615 B | } | service director { | chroot = . | client_limit = 0 | drop_priv_before_exec = no | executable = director | extra_groups = | fifo_listener login/proxy-notify { | group = | mode = 00 | user = | } | group = | idle_kill = 4294967295 secs | privileged_group = | process_limit = 1 | process_min_avail = 0 | protocol = | service_count = 0 | type = | unix_listener director-admin { | group = | mode = 0600 | user = | } | unix_listener login/director { | group = | mode = 00 | user = | } | user = $default_internal_user | vsz_limit = 18446744073709551615 B | } | service dns_client { | chroot = | client_limit = 1 | drop_priv_before_exec = no | executable = dns-client | extra_groups = | group = | idle_kill = 0 | privileged_group = | process_limit = 0 | process_min_avail = 0 | protocol = | service_count = 0 | type = | unix_listener dns-client { | group = | mode = 0666 | user = | } | unix_listener login/dns-client { | group = | mode = 0666 | user = | } | user = $default_internal_user | vsz_limit = 18446744073709551615 B | } | service doveadm { | chroot = | client_limit = 1 | drop_priv_before_exec = no | executable = doveadm-server | extra_groups = $default_internal_group | group = | idle_kill = 0 | privileged_group = | process_limit = 0 | process_min_avail = 0 | protocol = | service_count = 1 | type = | unix_listener doveadm-server { | group = | mode = 0600 | user = | } | user = | vsz_limit = 18446744073709551615 B | } | service health-check { | chroot = | client_limit = 1 | drop_priv_before_exec = yes | executable = script -p health-check.sh | extra_groups = | group = | idle_kill = 0 | privileged_group = | process_limit = 0 | process_min_avail = 0 | protocol = | service_count = 0 | type = | user = $default_internal_user | vsz_limit = 18446744073709551615 B | } | service imap-hibernate { | chroot = | client_limit = 0 | drop_priv_before_exec = no | executable = imap-hibernate | extra_groups = | group = | idle_kill = 0 | privileged_group = | process_limit = 0 | process_min_avail = 0 | protocol = imap | service_count = 0 | type = | unix_listener imap-hibernate { | group = $default_internal_group | mode = 0660 | user = | } | user = $default_internal_user | vsz_limit = 18446744073709551615 B | } | service imap-login { | chroot = login | client_limit = 0 | drop_priv_before_exec = no | executable = imap-login | extra_groups = | group = | idle_kill = 0 | inet_listener imap { | address = | haproxy = no | port = 143 | reuse_port = no | ssl = no | } | inet_listener imaps { | address = | haproxy = no | port = 993 | reuse_port = no | ssl = yes | } | privileged_group = | process_limit = 512 | process_min_avail = 3 | protocol = imap | service_count = 1 | type = login | user = $default_login_user | vsz_limit = 18446744073709551615 B | } | service imap-postlogin { | chroot = | client_limit = 0 | drop_priv_before_exec = no | executable = script-login /usr/local/sbin/dovecot-imap-post-login | extra_groups = | group = | idle_kill = 0 | privileged_group = | process_limit = 0 | process_min_avail = 0 | protocol = | service_count = 0 | type = | user = | vsz_limit = 18446744073709551615 B | } | service imap-urlauth-login { | chroot = token-login | client_limit = 0 | drop_priv_before_exec = no | executable = imap-urlauth-login | extra_groups = | group = | idle_kill = 0 | privileged_group = | process_limit = 0 | process_min_avail = 0 | protocol = imap | service_count = 1 | type = login | unix_listener imap-urlauth { | group = | mode = 0666 | user = | } | user = $default_login_user | vsz_limit = 18446744073709551615 B | } | service imap-urlauth-worker { | chroot = | client_limit = 1 | drop_priv_before_exec = no | executable = imap-urlauth-worker | extra_groups = $default_internal_group | group = | idle_kill = 0 | privileged_group = | process_limit = 1024 | process_min_avail = 0 | protocol = imap | service_count = 1 | type = | unix_listener imap-urlauth-worker { | group = | mode = 0600 | user = $default_internal_user | } | user = | vsz_limit = 18446744073709551615 B | } | service imap-urlauth { | chroot = | client_limit = 1 | drop_priv_before_exec = no | executable = imap-urlauth | extra_groups = | group = | idle_kill = 0 | privileged_group = | process_limit = 1024 | process_min_avail = 0 | protocol = imap | service_count = 1 | type = | unix_listener token-login/imap-urlauth { | group = | mode = 0666 | user = | } | user = $default_internal_user | vsz_limit = 18446744073709551615 B | } | service imap { | chroot = | client_limit = 1 | drop_priv_before_exec = no | executable = imap | extra_groups = $default_internal_group | group = | idle_kill = 0 | privileged_group = | process_limit = 128 | process_min_avail = 0 | protocol = imap | service_count = 1 | type = | unix_listener imap-master { | group = | mode = 0600 | user = | } | unix_listener login/imap { | group = | mode = 0666 | user = | } | user = | vsz_limit = 18446744073709551615 B | } | service indexer-worker { | chroot = | client_limit = 1 | drop_priv_before_exec = no | executable = indexer-worker | extra_groups = $default_internal_group | group = | idle_kill = 0 | privileged_group = | process_limit = 10 | process_min_avail = 0 | protocol = | service_count = 0 | type = | unix_listener indexer-worker { | group = | mode = 0600 | user = $default_internal_user | } | user = | vsz_limit = 18446744073709551615 B | } | service indexer { | chroot = | client_limit = 0 | drop_priv_before_exec = no | executable = indexer | extra_groups = | group = | idle_kill = 0 | privileged_group = | process_limit = 1 | process_min_avail = 0 | protocol = | service_count = 0 | type = | unix_listener indexer { | group = | mode = 0666 | user = | } | user = $default_internal_user | vsz_limit = 18446744073709551615 B | } | service ipc { | chroot = empty | client_limit = 0 | drop_priv_before_exec = no | executable = ipc | extra_groups = | group = | idle_kill = 0 | privileged_group = | process_limit = 1 | process_min_avail = 0 | protocol = | service_count = 0 | type = | unix_listener ipc { | group = | mode = 0600 | user = $default_internal_user | } | unix_listener login/ipc-proxy { | group = | mode = 0600 | user = $default_login_user | } | user = $default_internal_user | vsz_limit = 18446744073709551615 B | } | service lmtp { | chroot = | client_limit = 1 | drop_priv_before_exec = no | executable = lmtp | extra_groups = $default_internal_group | group = | idle_kill = 0 | privileged_group = | process_limit = 0 | process_min_avail = 0 | protocol = lmtp | service_count = 0 | type = | unix_listener lmtp { | group = | mode = 0666 | user = | } | user = | vsz_limit = 18446744073709551615 B | } | service log { | chroot = | client_limit = 0 | drop_priv_before_exec = no | executable = log | extra_groups = | group = | idle_kill = 4294967295 secs | privileged_group = | process_limit = 1 | process_min_avail = 0 | protocol = | service_count = 0 | type = log | unix_listener log-errors { | group = | mode = 0600 | user = | } | user = | vsz_limit = 18446744073709551615 B | } | service old-stats { | chroot = empty | client_limit = 0 | drop_priv_before_exec = no | executable = old-stats | extra_groups = | fifo_listener old-stats-mail { | group = | mode = 0600 | user = | } | fifo_listener old-stats-user { | group = | mode = 0600 | user = | } | group = | idle_kill = 4294967295 secs | privileged_group = | process_limit = 1 | process_min_avail = 0 | protocol = | service_count = 0 | type = | unix_listener old-stats { | group = | mode = 0600 | user = | } | user = $default_internal_user | vsz_limit = 18446744073709551615 B | } | service pop3-login { | chroot = login | client_limit = 0 | drop_priv_before_exec = no | executable = pop3-login | extra_groups = | group = | idle_kill = 0 | inet_listener pop3 { | address = | haproxy = no | port = 110 | reuse_port = no | ssl = no | } | inet_listener pop3s { | address = | haproxy = no | port = 995 | reuse_port = no | ssl = yes | } | privileged_group = | process_limit = 0 | process_min_avail = 0 | protocol = pop3 | service_count = 1 | type = login | user = $default_login_user | vsz_limit = 18446744073709551615 B | } | service pop3 { | chroot = | client_limit = 1 | drop_priv_before_exec = no | executable = pop3 | extra_groups = $default_internal_group | group = | idle_kill = 0 | privileged_group = | process_limit = 128 | process_min_avail = 0 | protocol = pop3 | service_count = 1 | type = | unix_listener login/pop3 { | group = | mode = 0666 | user = | } | user = | vsz_limit = 18446744073709551615 B | } | service replicator { | chroot = | client_limit = 0 | drop_priv_before_exec = no | executable = replicator | extra_groups = | group = | idle_kill = 4294967295 secs | privileged_group = | process_limit = 1 | process_min_avail = 0 | protocol = | service_count = 0 | type = | unix_listener replicator-doveadm { | group = | mode = 00 | user = $default_internal_user | } | unix_listener replicator { | group = | mode = 0600 | user = $default_internal_user | } | user = | vsz_limit = 18446744073709551615 B | } | service stats { | chroot = | client_limit = 0 | drop_priv_before_exec = no | executable = stats | extra_groups = | group = | idle_kill = 4294967295 secs | privileged_group = | process_limit = 1 | process_min_avail = 0 | protocol = | service_count = 0 | type = | unix_listener stats-reader { | group = | mode = 0600 | user = | } | unix_listener stats-writer { | group = $default_internal_group | mode = 0660 | user = | } | user = $default_internal_user | vsz_limit = 18446744073709551615 B | } | service submission-login { | chroot = login | client_limit = 0 | drop_priv_before_exec = no | executable = submission-login | extra_groups = | group = | idle_kill = 0 | inet_listener submission { | address = | haproxy = no | port = 587 | reuse_port = no | ssl = no | } | privileged_group = | process_limit = 0 | process_min_avail = 0 | protocol = submission | service_count = 1 | type = login | user = $default_login_user | vsz_limit = 18446744073709551615 B | } | service submission { | chroot = | client_limit = 1 | drop_priv_before_exec = no | executable = submission | extra_groups = $default_internal_group | group = | idle_kill = 0 | privileged_group = | process_limit = 1024 | process_min_avail = 0 | protocol = submission | service_count = 1 | type = | unix_listener login/submission { | group = | mode = 0666 | user = | } | user = | vsz_limit = 18446744073709551615 B | } | shutdown_clients = yes | ssl = yes | ssl_alt_cert = | ssl_alt_key = | ssl_ca = | ssl_cert = </usr/local/etc/Certs/m28a.crt | ssl_cert_username_field = commonName | ssl_cipher_list = ALL:!kRSA:!SRP:!kDHd:!DSS:!aNULL:!eNULL:!EXPORT:!DES:!3DES:!MD5:!PSK:!RC4:!ADH:!LOW@STRENGTH | ssl_client_ca_dir = | ssl_client_ca_file = | ssl_client_cert = | ssl_client_key = | ssl_client_require_valid_cert = yes | ssl_crypto_device = | ssl_curve_list = | ssl_dh = # hidden, use -P to show it | ssl_key = # hidden, use -P to show it | ssl_key_password = | ssl_min_protocol = TLSv1 | ssl_options = | ssl_prefer_server_ciphers = no | ssl_require_crl = yes | ssl_verify_client_cert = no | state_dir = /var/lib/dovecot | stats_writer_socket_path = stats-writer | submission_client_workarounds = | submission_host = | submission_logout_format = in=%i out=%o | submission_max_mail_size = 0 | submission_max_recipients = 0 | submission_relay_command_timeout = 5 mins | submission_relay_connect_timeout = 30 secs | submission_relay_host = | submission_relay_master_user = | submission_relay_max_idle_time = 29 mins | submission_relay_password = | submission_relay_port = 25 | submission_relay_rawlog_dir = | submission_relay_ssl = no | submission_relay_ssl_verify = yes | submission_relay_trusted = no | submission_relay_user = | submission_ssl = no | submission_timeout = 30 secs | syslog_facility = mail | userdb { | args = | auth_verbose = default | default_fields = | driver = passwd | name = | override_fields = | result_failure = continue | result_internalfail = continue | result_success = return-ok | skip = never | } | valid_chroot_dirs = | verbose_proctitle = yes | verbose_ssl = no | version_ignore = no | protocol lmtp { | mail_plugins = notify quota fts fts_squat acl | } | protocol lda { | mail_plugins = notify quota fts fts_squat acl | } | protocol imap { | imap_client_workarounds = delay-newmail tb-extra-mailbox-sep tb-lsub-flags | imap_id_log = * | imap_logout_format = [%i/%o] | mail_max_userip_connections = 0 | mail_plugins = notify quota fts fts_squat acl quota imap_quota listescape fts fts_squat | } The config may be sub-optimal. Please concentrate on my quota problem. Stay healthy, Frank Elsner

1 0

Mail replication fails between v2.2.27 and v2.3.4.1
by Apostolis Hardalias 03 Jul '20

03 Jul '20

Hello, I have two installations of dovecot configured to replicate mailboxes between them. recently, i upgraded the operating system on one of them (mx2.example.com) and now i'm running one installation on version 2.2.27 (debian stretch) and another on version 2.3.4.1 (mx1.example.com debian buster). My setup includes 3 shared namespaces that point to the mailboxes of 3 accounts. these accounts are setup to use maildir format. After upgrading one of the hosts, i started having issues with failed replications on those mailboxes. I tried running the replication manually and repeatedly by issuing the following on mx1.example.com: doveadv -d sync -u exception_bucket(a)example.com -d -l 30 -n -u and the logs on mx2.example.com included the following lines consistently: Jul 02 14:21:58 dsync-server(exception_bucket(a)example.com): Debug: brain S: Change during sync: Mailbox GUID 2d32711ddfd27250390e0000a712b6e3 was lost Jul 02 14:21:58 dsync-server(exception_bucket(a)example.com): Debug: brain S: We don't have mailbox 2d32711ddfd27250390e0000a712b6e3 I double checked for the existance of the mailbox with that guid (that guid points to the inbox) and the mailbox existed on both servers but, the contents of the mailbox on the two servers where different (missing e-mails on both servers). I attempted running a force-resync command as follows but with no luck. doveadm -d force-resync -u exception_bucket(a)example.com inbox but the issue persisted. admittedly, i didn't run the command on both servers because i read it doesn't replicate after figuring a workaround. The next thing i tried was attempting replication without the -n flag, given that you mention that there are some issues replicating shared namespaces. That didn't fix the replication status either. After looking around, i came onto the solution on this thread: https://dovecot.org/pipermail/dovecot/2017-october/109620.html which proposed setting mailbox_list_index = no. This was the default setting on version 2.2.27, so i changed that setting on mx2.example.com which was running version 2.3.4.1. This allowed the replication to work but i don't think it is a setting i want in my configuration. Is there something i can do to re-enable dovecot to check index files instead of mailboxes? Could that be an issue when replicating between those two different versions? I'm attaching the configuration files for both the mailservers, a separate configuration file is included since mail_replica settings are set from there, and a link to the compressed log file i pulled during the operation. https://filebin.net/d9yygnq8jg74unwb/replication_debug.log.bz2?t=vv2o81ka Thank you in advance, Apostolis Hardalias

1 0

local stanza only generated for IPv6
by Jeremy Ardley 02 Jul '20

02 Jul '20

I have a mail server with multiple IP addresses and associated DNS names In the dovecot configuration I have a listen directive: listen = mail.example.com.com,mail.otherexample.com,localhost Multiple local stanzas are of the form: local mail.example.com { protocol imap { ssl_cert = </etc/letsencrypt/live/mail.example.com/fullchain.pem ssl_key = </etc/letsencrypt/live/mail.example.com/privkey.pem service imaps_login { inet_listener imaps { address=mail.example.com } inet_listener imap { address=mail.example.com } } } } mail.example.com has IPv4 and IPv6 addresses in DNS When I run doveconf -n the local configuration is only generated for the IPv6 address. I can test the operation on IPv6 using openSSL and see different server certificates on different IP addresses as expected. How do I force local generation for both IPv4 and IPv6 ?

3 4

dovecot: doveconf: Fatal: block_alloc(134217728): Out of memory
by Brent Clark 30 Jun '20

30 Jun '20

Good day Guys Currently on Debian Stretch (2.2.27). This morning we enabled SNI for our clients (file per domain). On going live with the new server configuration, we started getting the following on our shared hosting servers. Jun 30 07:25:04 REMOVED_HOSTNAME dovecot: doveconf: Fatal: block_alloc(134217728): Out of memory Jun 30 07:25:04 REMOVED_HOSTNAME dovecot: config: Fatal: block_alloc(134217728): Out of memory Jun 30 07:25:04 REMOVED_HOSTNAME dovecot: config: Fatal: master: service(config): child 64008 returned error 83 (Out of memory (service config { vsz_limit=512 MB }, you may need to increase it) - set CORE_OUTOFMEM=1 environment to get core dump) Jun 30 07:25:34 REMOVED_HOSTNAME dovecot: doveconf: Panic: data stack: Out of memory when allocating 2147483688 bytes Jun 30 07:25:37 REMOVED_HOSTNAME dovecot: config: Panic: data stack: Out of memory when allocating 2147483688 bytes This is a server with 2414 domains. On a few of our servers, to buy time, we had to set: default_vsz_limit =10096M A question I would like to ask is. Based on the following change notice, could the following be the problem. https://dovecot.org/pipermail/dovecot-news/2019-July/000412.html - config: Memory leak in config process when ssl_dh setting wasn't set and there was no ssl-parameters.dat file. This caused config process to die once in a while with "out of memory". If anyone could provide any assistance or share a tip on where we can look it would be appreciated. This one has my team and I stumped. Kind regards Brent Clark

1 0

POP3Deleted flag issues
by Justina Colmena ~biz 29 Jun '20

29 Jun '20

Hello, I have been running my own mail server with Dovecot, Postfix, and Cyrus-SASL for authentication. = dovecot22u.x86_64 1:2.2.36.4-1.el7.ius @ius I am basically trying to tune the system for better performance. The flat files "/var/mail/justina" etc exhibit locking issues and conflicts when fetching mail at the same time new mail is being delivered by Postfix. Other mail is stored in "Maildir" type folders accessible via IMAP. These exhibit better performance with finer grained locking. There's an "idea" that was posted to the list 7 years ago, shows up top rank on Google. https://dovecot.org/pipermail/dovecot/2013-May/090114.html I fear either an incomplete implementation of the feature or "here-be-dragons" code that may or may not be completely documented. I would like all the "$POP3Deleted" mail to be moved to an "Archive" Maildir folder accessible via IMAP. How do I accomplish this? -- Sent from my Android device with K-9 Mail. Please excuse my brevity.

1 0

layout:fs info
by Stefano Gatto - Fly2Net sas 29 Jun '20

29 Jun '20

Hi all, my dovecot version is 2.2.13, quite standard configuration. Can I add directive LAYOUT=fs in dovecot configuration without losing all my archived messages? This should modify the separator of email folders from dots to slashes, correct? BR Stefano

2 2

Plugin ABI compat between v2.3.8 and v2.3.9
by Alexander Strasser 24 Jun '20

24 Jun '20

Hi all! This is my first post on this list. Please pardon me if I overlooked or misunderstood some things. I had some imap crashes (sig11) starting at the end of 2019 after an upgrade of dovecot. I found out, that I didn't have any problems using version v2.3.8, but any version v2.3.9 and higher would trigger the crashes. After investigating more deeply and creating a core dump, I saw that the crash happened in an external plugin fetchmail_wakeup[1]. After recompiling that plugin with up to date dovecot headers, I didn't get crashes anymore. So I suspect there were ABI incompatible changes and it was forgotten to bump the minimum Plugin-ABI version supported. I could try to follow up some more details, but it would be quite a burden because of rebuilding the plugin with debug symbols against version 2.3.8 of dovecot and triggering the crash etc. Despite that I think it should be possible to detect changes that are ABI incompatible, as otherwise plugin users would always have to find out first hand with unknown consequences. That said there could be a possibility of the plugin using the API/ABI in an invalid way. If that was the cause, then the plugin should be changed. Hope this report turns out to help improve the situation. I don't have problems currently and will in future be sensitive to this specific possible cause of problems, but not having such crashes in the first place, would be worth it and maybe could still help others. Best regards, Alexander 1: slightly reduced version of: https://github.com/marschap/fetchmail_wakeup

2 4

Converting dot-namespaced Maildir to /-namespaced
by Guido Goluke, MajorLabel 24 Jun '20

24 Jun '20

I have a couple of domains on my server, all of them namespaced with a dot. It's 10-15 mailboxes at the most. Is there good way to convert them to / (slash) namespaced folders? Maybe some bash script lying around somewhere?

1 0

dovecot fts configuration without solr
by Danilo Tomasoni 24 Jun '20

24 Jun '20

Hello All, I always used dovecot and I'm pretty happy with it, but recently I changed OS (to ubuntu 18) and to get dovecot LTS with lucene (the default I was using on my previous arch installation) I needed to build from source the version 2.3.10 (the one that came with the repos was older and clucene was not actually supported) The problem is that the Clucene is not behaving well, It indexes only some mails but definitely not all according to my tests (there are also strange assertion errors in the logs) I also tried xapian fts index but is very slow indexing and definitely doesn't seem to work. The problem with solr fts is that solr doesn't even start on my tiny system (odroid C2 with 2GB RAM) and anyway I don't want to bloat all the system for the indexing if possible.. Anyone can suggest me a proper minimal and working configuration? Thank you Danilo

2 2

JMAP support
by Martynas Bendorius 23 Jun '20

23 Jun '20

Hello, Is there any ETA set for JMAP support? Thank you! >> On 11/27/2016 5:28 AM, Aki Tuomi <aki.tuomi at dovecot.fi> wrote: >> Hi! >> We are working on including JMAP support to Dovecot. At this moment I cannot give any promise for exact version, but hopefully it will be part of v2.3 >> >> Aki Tuomi >> Dovecot Oy -- Best regards, Martynas Bendorius

3 2

Apple mail works but thunderbird unable to connect
by Dshah 23 Jun '20

23 Jun '20

Dear all, I am stuck on this issue for days, I am able to connect on my IMAP server using Apple mail client but thunderbird shows me this error: "improper command pipelining after EHLO" I have tried all the ports in manual config but it just is not working while Apple Mail is able to connect perfectly, here are my configuration details of "postconf -n" , "doveconf -n" and " master.cf" https://pastebin.com/M3XG9DXA Thanks in advance.

6 12

problem with warnings
by Maciej Milaszewski 23 Jun '20

23 Jun '20

Hi I have a problem with warrnings in log Yesterday "big gays" change datastore and After this time i get warrnings in dovecot like: Warning: Created dotlock file's timestamp is different than current time (1592878268 vs 1592871191): /vmail/us/username/Maildir/dovecot-uidlist Before that there was no problem with warnnings I have dovecot director with 5 dovecot-nodes and storage always was mounted via nfs /vmail on /vmail type nfs (rw,noexec,noatime,vers=3,rsize=65536,wsize=65536,namlen=255,acregmin=120,acregmax=120,acdirmin=120,acdirmax=120,hard,nocto,nordirplus,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=10.0.100.41,mountvers=3,mountport=635,mountproto=tcp,local_lock=none,addr=xxx.xxx.xxx.xxx) # 2.2.36.4 (baf9232c1): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.24.rc1 (debaa297) # OS: Linux 3.16.0-10-amd64 x86_64 Debian 8.11

1 0

from field encoding
by Jan Jurko 23 Jun '20

23 Jun '20

Good day. I have a dovecot 2.3.4.1 on debian 10 as an imap server. I found there are emails where the header field From has no encoding even if there is a name with special characters like Žlutý Kůň. The header looks like: From: "Žlutý Kůň" <zluty.kun(a)domain.tld> In this case the email client - roundcube, outlook etc. will show the From with wrong characters. This behaviour is typical only for dovecot, not for courier-imap - it was installed before dovecot with no problems. If there is corretly encoded From filed, the client shows the From correctly. Is there a way to set up the dovecot to show the field correctly even without encoding stuff? Some default/fallback settings? Thank you very much for your help Jan Jurko

2 3

nodelay passdb extra field does not work?
by Joe Wong 23 Jun '20

23 Jun '20

Hello, I have added 'y' as nodelay in my passdb query and I see the following in log: dovecot: imap-login: Debug: Ignoring unknown passdb extra field: nodelay does it mean this option is no longer supported in 2.3.10 ? - Joe

2 4

AW: replicator: Panic: data stack: Out of memory
by Thomas Tsiakalakis 23 Jun '20

23 Jun '20

I managed to convince the System that I really want a core dump Thomas Tsiakalakis Team Applikationsbetrieb GDV Dienstleistungs-GmbH Tel: +49(40)33449-4318 Fax: E-Mail: Thomas.Tsiakalakis(a)gdv-dl.de<mailto:Thomas.Tsiakalakis@gdv-dl.de> GDV Dienstleistungs-GmbH Glockengießerwall 1 D-20095 Hamburg www.gdv-dl.de<http://www.gdv-dl.de> Niederlassungen: Wilhelmstraße 43 / 43 G 10117 Berlin Frankenstraße 18 20097 Hamburg Sitz und Registergericht: Hamburg HRB 145291 USt.-IdNr : DE 205183123 Geschäftsführer: Dr. Jens Bartenwerfer Fred di Giuseppe Chiachiarella Aufsichtsratsvorsitzender: Werner Schmidt ------------------------------------------------------------------ Diese E-Mail und alle Anhänge enthalten vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese E-Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe der E-Mail ist nicht gestattet. This e-mail and any attached files may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorised copying, disclosure or distribution of the material in this e-mail is strictly forbidden. Von: Thomas Tsiakalakis Gesendet: Donnerstag, 18. Juni 2020 16:26 An: 'dovecot(a)dovecot.org' <dovecot(a)dovecot.org> Betreff: replicator: Panic: data stack: Out of memory Hi, I have set up 2 SLES 15 Hosts with dovecot and replication. Everything seems to work fine but every time a message is delivered, I get an out of memory error in the logs. The Replication itself seems to work fine though. I increased default_vsz_limit to 512M but the only thing that changed was that dovecot was trying to allocate 1073741864 bytes instead of 268435496 As I said, I’m running SLES 15 SP1 and Dovecot 2.3.10 (0da0eff44) (both Hosts have the same version) Each Host currently has 8GB of Memory. # free -h total used free shared buff/cache available Mem: 7.8Gi 278Mi 7.3Gi 47Mi 183Mi 7.2Gi Swap: 4.0Gi 0B 4.0Gi # journalctl -f Jun 18 15:55:48 mail1 postfix/pickup[3457]: 18533C009C8: uid=0 from=<root> Jun 18 15:55:48 mail1 postfix/cleanup[3669]: 18533C009C8: message-id=<20200618135548.18533C009C8@mail1> Jun 18 15:55:48 mail1 postfix/qmgr[3458]: 18533C009C8: from=<root@mail1>, size=431, nrcpt=1 (queue active) Jun 18 15:55:48 mail1 dovecot[1833]: lmtp(3673): Connect from local Jun 18 15:55:48 mail1 dovecot[1833]: replicator: Panic: data stack: Out of memory when allocating 268435496 bytes Jun 18 15:55:48 mail1 dovecot[1833]: replicator: Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(backtrace_append+0x42) [0x7f8346d6d262] -> /usr/lib64/dovecot/libdovecot.so.0(backtrace_get+0x1e) [0x7f8346d6d37e] -> /usr/lib64/dovecot/libdovecot.so.0(+0xebcee) [0x7f8346d77cee] -> /usr/lib64/dovecot/libdovecot.so.0(+0xebd91) [0x7f8346d77d91] -> /usr/lib64/dovecot/libdovecot.so.0(i_fatal+0) [0x7f8346cd1f8b] -> /usr/lib64/dovecot/libdovecot.so.0(t_pop_last_unsafe+0) [0x7f8346d73660] -> /usr/lib64/dovecot/libdovecot.so.0(+0xe7a50) [0x7f8346d73a50] -> /usr/lib64/dovecot/libdovecot.so.0(+0x10eb58) [0x7f8346d9ab58] -> /usr/lib64/dovecot/libdovecot.so.0(+0xe3ac5) [0x7f8346d6fac5] -> /usr/lib64/dovecot/libdovecot.so.0(buffer_write+0xf2) [0x7f8346d6fdb2] -> dovecot/replicator(replicator_queue_push+0xde) [0x5648989a5cde] -> dovecot/replicator(+0x5464) [0x5648989a5464] -> dovecot/replicator(+0x4a0b) [0x5648989a4a0b] -> dovecot/replicator(+0x4c02) [0x5648989a4c02] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_call_io+0x69) [0x7f8346d90c99] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x134) [0x7f8346d92574] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run+0x4c) [0x7f8346d90d9c] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7f8346d90fc8] -> /usr/lib64/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f8346d01873] -> dovecot/replicator(main+0x1a0) [0x5648989a3cb0] -> /lib64/libc.so.6(__libc_start_main+0xea) [0x7f83468f534a] -> dovecot/replicator(_start+0x2a) [0x5648989a3d5a] Jun 18 15:55:48 mail1 dovecot[1833]: lmtp(test(a)example.com)<3673><q5sLCGRy615ZDgAATn/NZw>: Warning: replication(test(a)example.com): Sync failure: Jun 18 15:55:48 mail1 dovecot[1833]: lmtp(test(a)example.com)<3673><q5sLCGRy615ZDgAATn/NZw>: Warning: replication(test(a)example.com): Remote sent invalid input: - Jun 18 15:55:48 mail1 dovecot[1833]: lmtp(test(a)example.com)<3673><q5sLCGRy615ZDgAATn/NZw>: msgid=<20200618135548.18533C009C8@mail1>: saved mail to INBOX Jun 18 15:55:48 mail1 dovecot[1833]: lmtp(3673): Disconnect from local: Client has quit the connection (state=READY) Jun 18 15:55:48 mail1 postfix/lmtp[3672]: 18533C009C8: to=<test(a)example.com>, orig_to=<test(a)domain.com>, relay=mail1[private/dovecot-lmtp], delay=0.17, delays=0.02/0.01/0.02/0.13, dsn=2.0.0, status=sent (250 2.0.0 <test(a)example.com> q5sLCGRy615ZDgAATn/NZw Saved) Jun 18 15:55:48 mail1 postfix/qmgr[3458]: 18533C009C8: removed Jun 18 15:55:48 mail1 dovecot[1833]: replicator: Fatal: master: service(replicator): child 2948 killed with signal 6 (core not dumped - https://dovecot.org/bugreport.html#coredumps - set /proc/sys/fs/suid_dumpable to 2)

1 0

Updating wiki content
by Dan 22 Jun '20

22 Jun '20

Greetings, I'd like to contribute to the Dovecot wiki in regards to clients that lack the ability to support SNI. However the captcha doesn't make sense, I get a question "What do you do to prevent spam?". This is a loaded question which I'm uncertain what the answer should be. Thanks.

2 1

Bug[?]report: duplicate response
by Johannes Schilling 21 Jun '20

21 Jun '20

hi, i'm not sure if i've discovered a bug or if i'm not following the IMAP specs correctly. observations: { echo -en "a1 login foo bar\r\na2 notify set (subscribed (FlagChange SubscriptionChange MessageNew MessageExpunge))\r\n"; cat - } | openssl s_client -connect [my_dovecot_server]:993 produces the following output (aside from the openssl s_client cert-inspection stuff): 2020-06-21 12:26:02 * OK [CAPABILITY IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE LITERAL+ AUTH=PLAIN AUTH=LOGIN] Dovecot (Debian) ready. 2020-06-21 12:26:02 a1 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 LITERAL+ NOTIFY SPECIAL-USE] Logged in 2020-06-21 12:26:02 a2 OK NOTIFY completed (0.005 + 0.000 + 0.004 secs). 2020-06-21 12:26:02 a2 OK NOTIFY completed (0.002 + 0.000 + 0.001 secs). the first line is the pre-login welcome prompt, the second one the result of the "a1 login .." command and the third and fourth seem to be the answer to the "a2 notify set .." command, twice. from the different timings given, it seems the a2 command is actually executed twice. is this a case of "you're not allowed to pipeline commands like this" or a bug in dovecot (or both)? i attached the output of `dovecot -n`. best, dario

1 0

Mailfiles gets duplicated
by Jacques Schreiber 19 Jun '20

19 Jun '20

Hello, With my configuration Dovecot creates multiple duplicates (sometimes 2, sometimes 3, sometimes a plenty) of mailfiles when moving them into the Sent or the Trash folders. This does not affect the Inbox folder. I observed this while using Thunderbird on Ubuntu as a client as well as K9-Mail on Android, therefore I expect this comes from the Dovecot server and not from the client itself. It also appears that the duplicates does not have the size S= and vsize W= flags. Here is a short example of the last emails from my folder /.Sent/cur: -rw------- 1 pi pi 1,6M mars 24 22:18 1585084691.M834293P16489.raspberry-pi,S=1658182,W=1679758:2,S -rwx------ 1 pi pi 34M mars 24 22:20 1585084841.M415421P17104Q0Rc311b18de2edf536.raspberry-pi:2, -rwx------ 1 pi pi 34M mars 24 22:22 1585084954.M254398P17175Q0R6c5a66e22ac3a3d2.raspberry-pi:2, -rwx------ 1 pi pi 34M mars 24 22:46 1585086411.M317404P18117Q0R61ba34fb281e8eb5.raspberry-pi:2, -rwx------ 1 pi pi 34M mars 24 22:51 1585086659.M435086P18251Q0R7e118d3bd7784c6d.raspberry-pi:2, -rwx------ 1 pi pi 34M mars 24 22:53 1585086799.M821376P18319Q0R6b838db7f14a2302.raspberry-pi:2, -rwx------ 1 pi pi 34M mars 24 22:54 1585086861.M788796P18398Q0Raaa98233db1f9b6a.raspberry-pi:2, -rwx------ 1 pi pi 34M mars 24 23:00 1585087244.M616219P18629Q0R4d5856ac0d1b1337.raspberry-pi:2, -rwx------ 1 pi pi 34M mars 24 23:01 1585087278.M581756P18651Q0R6a75f871d9e8f0aa.raspberry-pi:2, -rwx------ 1 pi pi 34M mars 24 23:01 1585087296.M954701P18666Q0R0cce469807cb0aa8.raspberry-pi:2, -rwx------ 1 pi pi 34M mars 24 23:05 1585087552.M557221P18793Q0R541dece72da12039.raspberry-pi:2, -rwx------ 1 pi pi 34M mars 24 23:09 1585087759.M768686P18927Q0Rbc1c813e1b124702.raspberry-pi:2, -rwx------ 1 pi pi 34M mars 24 23:10 1585087823.M232119P19026Q0R4086d52491835470.raspberry-pi:2, -rwx------ 1 pi pi 34M mars 24 23:10 1585087855.M951407P19035Q0R4edd76369b804f54.raspberry-pi:2, -rwx------ 1 pi pi 34M mars 24 23:22 1585088561.M364587P19476Q0Rdc0ac3a664f1a80f.raspberry-pi:2, -rwx------ 1 pi pi 34M mars 24 23:24 1585088639.M90555P19512Q0R6214b0e915c88908.raspberry-pi:2, -rwx------ 1 pi pi 34M mars 24 23:27 1585088859.M192671P19663Q0Re4562fb440f7a4be.raspberry-pi:2, -rwx------ 1 pi pi 34M mars 24 23:28 1585088927.M926251P19699Q0Rbe7523140efc06e2.raspberry-pi:2, -rwx------ 1 pi pi 34M mars 24 23:29 1585088962.M120826P19721Q0Rd66b5d585c41123b.raspberry-pi:2, -rwx------ 1 pi pi 34M mars 24 23:31 1585089111.M427988P19799Q0R5b8e8a032adc33c8.raspberry-pi:2, -rwx------ 1 pi pi 1,6M mars 24 23:32 1585089138.M910049P19827Q1R1b4d834fadfb0fd6.raspberry-pi:2, -rwx------ 1 pi pi 34M mars 24 23:33 1585089180.M811880P19839Q0R8c415b8fbf638018.raspberry-pi:2, -rwx------ 1 pi pi 34M mars 24 23:34 1585089252.M333476P19878Q0R3b809c0f458a90e0.raspberry-pi:2, -rwx------ 1 pi pi 34M mars 24 23:34 1585089293.M103544P19918Q0Rd9acc8d53f5c8b32.raspberry-pi:2, -rwx------ 1 pi pi 34M mars 24 23:35 1585089314.M270143P19948Q0R1202a6fe81862880.raspberry-pi:2, -rw------- 1 pi pi 2,0M mars 29 13:01 1585479708.M437415P11486.raspberry-pi,S=2076767,W=2105374:2,S -rwx------ 1 pi pi 2,0M mars 29 13:02 1585479733.M94224P13150Q0R974361f29d7d9cdb.raspberry-pi:2, -rw------- 1 pi pi 2,5K mars 31 09:10 1585638623.M921769P12803.raspberry-pi,S=2511,W=2585:2,S -rwx------ 1 pi pi 3,0K mars 31 09:11 1585638671.M552885P12861Q0R878fb6aa8485b5c0.raspberry-pi:2, -rw------- 1 pi pi 19M avril 3 09:38 1585899475.M669440P24679.raspberry-pi,S=19757959,W=20028662:2,S -rwx------ 1 pi pi 19M avril 3 09:38 1585899531.M744009P25082Q0R0b61c7e8e7b723b4.raspberry-pi:2, -rw------- 1 pi pi 421 avril 3 14:52 1585918350.M591326P1027.raspberry-pi,S=421,W=434:2,S -rw------- 1 pi pi 421 avril 3 14:52 1585918360.M206900P1027.raspberry-pi,S=421,W=434:2,S -rw------- 1 pi pi 421 avril 3 14:52 1585918372.M255849P1032.raspberry-pi,S=421,W=434:2,S -rwx------ 1 pi pi 1,1K avril 3 14:53 1585918394.M224204P1071Q0R7e9bc28b2d8e7fc4.raspberry-pi:2, -rwx------ 1 pi pi 1,1K avril 3 14:53 1585918395.M884727P1073Q1Ra4a111c1e0f5a399.raspberry-pi:2, -rwx------ 1 pi pi 1,1K avril 3 14:53 1585918398.M36019P1077Q2R10960cdc588b3ede.raspberry-pi:2, Below are details about my configuration pi@raspberry-pi:~$ sudo uname --all Linux raspberry-pi 4.4.38+ #938 Thu Dec 15 15:17:54 GMT 2016 armv6l GNU/Linux pi@raspberry-pi:~$ mount [...] /dev/sda1 on /home/pi type ext4 (rw,noatime,nodiratime,data=ordered) [...] pi@raspberry-pi:/var/log$ sudo dovecot --version 2.2.13 pi@raspberry-pi:/var/log$ sudo dovecot -n # 2.2.13: /etc/dovecot/dovecot.conf # OS: Linux 4.4.38+ armv6l Debian 8.0 ext4 disable_plaintext_auth = no mail_location = maildir:/home/pi/Mails/%u namespace { inbox = yes location = mailbox { auto = subscribe special_use = \Drafts name = Drafts } mailbox { special_use = \Junk name = Junk } mailbox { auto = subscribe special_use = \Sent name = Sent } mailbox { special_use = \Sent name = Sent Messages } mailbox { auto = subscribe special_use = \Trash name = Trash } prefix = separator = / type = private name = inbox } passdb { driver = pam } passdb { args = /home/pi/Mails/dovecot_passwords driver = passwd-file } protocols = " imap" service replication-notify-fifo { name = aggregator } service anvil-auth-penalty { name = anvil } service auth-worker { name = auth-worker } service auth-client { name = auth } service config { name = config } service dict { name = dict } service login/proxy-notify { name = director } service dns-client { name = dns_client } service doveadm-server { name = doveadm } service { inet_listener { address = * port = 4143 name = imap } name = imap-login } service imap-urlauth { name = imap-urlauth-login } service imap-urlauth-worker { name = imap-urlauth-worker } service token-login/imap-urlauth { name = imap-urlauth } service login/imap { name = imap } service indexer-worker { name = indexer-worker } service indexer { name = indexer } service ipc { name = ipc } service lmtp { name = lmtp } service log-errors { name = log } service pop3 { name = pop3-login } service login/pop3 { name = pop3 } service replicator-doveadm { name = replicator } service login/ssl-params { name = ssl-params } service stats-mail { name = stats } ssl_cert = </home/pi/Mails/imap_ssl_certificate.crt ssl_key = </home/pi/Mails/imap_ssl_private.key userdb { driver = passwd } userdb { args = uid=1000 gid=1000 home=/var/mail/%u driver = static } protocol lmtp { service replication-notify-fifo { name = aggregator } service anvil-auth-penalty { name = anvil } service auth-worker { name = auth-worker } service auth-client { name = auth } service config { name = config } service dict { name = dict } service login/proxy-notify { name = director } service dns-client { name = dns_client } service doveadm-server { name = doveadm } service imap { name = imap-login } service imap-urlauth { name = imap-urlauth-login } service imap-urlauth-worker { name = imap-urlauth-worker } service token-login/imap-urlauth { name = imap-urlauth } service login/imap { name = imap } service indexer-worker { name = indexer-worker } service indexer { name = indexer } service ipc { name = ipc } service lmtp { name = lmtp } service log-errors { name = log } service pop3 { name = pop3-login } service login/pop3 { name = pop3 } service replicator-doveadm { name = replicator } service login/ssl-params { name = ssl-params } service stats-mail { name = stats } } protocol lda { service replication-notify-fifo { name = aggregator } service anvil-auth-penalty { name = anvil } service auth-worker { name = auth-worker } service auth-client { name = auth } service config { name = config } service dict { name = dict } service login/proxy-notify { name = director } service dns-client { name = dns_client } service doveadm-server { name = doveadm } service imap { name = imap-login } service imap-urlauth { name = imap-urlauth-login } service imap-urlauth-worker { name = imap-urlauth-worker } service token-login/imap-urlauth { name = imap-urlauth } service login/imap { name = imap } service indexer-worker { name = indexer-worker } service indexer { name = indexer } service ipc { name = ipc } service lmtp { name = lmtp } service log-errors { name = log } service pop3 { name = pop3-login } service login/pop3 { name = pop3 } service replicator-doveadm { name = replicator } service login/ssl-params { name = ssl-params } service stats-mail { name = stats } } protocol imap { service replication-notify-fifo { name = aggregator } service anvil-auth-penalty { name = anvil } service auth-worker { name = auth-worker } service auth-client { name = auth } service config { name = config } service dict { name = dict } service login/proxy-notify { name = director } service dns-client { name = dns_client } service doveadm-server { name = doveadm } service imap { name = imap-login } service imap-urlauth { name = imap-urlauth-login } service imap-urlauth-worker { name = imap-urlauth-worker } service token-login/imap-urlauth { name = imap-urlauth } service login/imap { name = imap } service indexer-worker { name = indexer-worker } service indexer { name = indexer } service ipc { name = ipc } service lmtp { name = lmtp } service log-errors { name = log } service pop3 { name = pop3-login } service login/pop3 { name = pop3 } service replicator-doveadm { name = replicator } service login/ssl-params { name = ssl-params } service stats-mail { name = stats } }

1 1

replicator: Panic: data stack: Out of memory
by Thomas Tsiakalakis 18 Jun '20

18 Jun '20

Hi, I have set up 2 SLES 15 Hosts with dovecot and replication. Everything seems to work fine but every time a message is delivered, I get an out of memory error in the logs. The Replication itself seems to work fine though. I increased default_vsz_limit to 512M but the only thing that changed was that dovecot was trying to allocate 1073741864 bytes instead of 268435496 As I said, I’m running SLES 15 SP1 and Dovecot 2.3.10 (0da0eff44) (both Hosts have the same version) Each Host currently has 8GB of Memory. # free -h total used free shared buff/cache available Mem: 7.8Gi 278Mi 7.3Gi 47Mi 183Mi 7.2Gi Swap: 4.0Gi 0B 4.0Gi # journalctl -f Jun 18 15:55:48 mail1 postfix/pickup[3457]: 18533C009C8: uid=0 from=<root> Jun 18 15:55:48 mail1 postfix/cleanup[3669]: 18533C009C8: message-id=<20200618135548.18533C009C8@mail1> Jun 18 15:55:48 mail1 postfix/qmgr[3458]: 18533C009C8: from=<root@mail1>, size=431, nrcpt=1 (queue active) Jun 18 15:55:48 mail1 dovecot[1833]: lmtp(3673): Connect from local Jun 18 15:55:48 mail1 dovecot[1833]: replicator: Panic: data stack: Out of memory when allocating 268435496 bytes Jun 18 15:55:48 mail1 dovecot[1833]: replicator: Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(backtrace_append+0x42) [0x7f8346d6d262] -> /usr/lib64/dovecot/libdovecot.so.0(backtrace_get+0x1e) [0x7f8346d6d37e] -> /usr/lib64/dovecot/libdovecot.so.0(+0xebcee) [0x7f8346d77cee] -> /usr/lib64/dovecot/libdovecot.so.0(+0xebd91) [0x7f8346d77d91] -> /usr/lib64/dovecot/libdovecot.so.0(i_fatal+0) [0x7f8346cd1f8b] -> /usr/lib64/dovecot/libdovecot.so.0(t_pop_last_unsafe+0) [0x7f8346d73660] -> /usr/lib64/dovecot/libdovecot.so.0(+0xe7a50) [0x7f8346d73a50] -> /usr/lib64/dovecot/libdovecot.so.0(+0x10eb58) [0x7f8346d9ab58] -> /usr/lib64/dovecot/libdovecot.so.0(+0xe3ac5) [0x7f8346d6fac5] -> /usr/lib64/dovecot/libdovecot.so.0(buffer_write+0xf2) [0x7f8346d6fdb2] -> dovecot/replicator(replicator_queue_push+0xde) [0x5648989a5cde] -> dovecot/replicator(+0x5464) [0x5648989a5464] -> dovecot/replicator(+0x4a0b) [0x5648989a4a0b] -> dovecot/replicator(+0x4c02) [0x5648989a4c02] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_call_io+0x69) [0x7f8346d90c99] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x134) [0x7f8346d92574] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run+0x4c) [0x7f8346d90d9c] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7f8346d90fc8] -> /usr/lib64/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f8346d01873] -> dovecot/replicator(main+0x1a0) [0x5648989a3cb0] -> /lib64/libc.so.6(__libc_start_main+0xea) [0x7f83468f534a] -> dovecot/replicator(_start+0x2a) [0x5648989a3d5a] Jun 18 15:55:48 mail1 dovecot[1833]: lmtp(test(a)example.com)<3673><q5sLCGRy615ZDgAATn/NZw>: Warning: replication(test(a)example.com): Sync failure: Jun 18 15:55:48 mail1 dovecot[1833]: lmtp(test(a)example.com)<3673><q5sLCGRy615ZDgAATn/NZw>: Warning: replication(test(a)example.com): Remote sent invalid input: - Jun 18 15:55:48 mail1 dovecot[1833]: lmtp(test(a)example.com)<3673><q5sLCGRy615ZDgAATn/NZw>: msgid=<20200618135548.18533C009C8@mail1>: saved mail to INBOX Jun 18 15:55:48 mail1 dovecot[1833]: lmtp(3673): Disconnect from local: Client has quit the connection (state=READY) Jun 18 15:55:48 mail1 postfix/lmtp[3672]: 18533C009C8: to=<test(a)example.com>, orig_to=<test(a)domain.com>, relay=mail1[private/dovecot-lmtp], delay=0.17, delays=0.02/0.01/0.02/0.13, dsn=2.0.0, status=sent (250 2.0.0 <test(a)example.com> q5sLCGRy615ZDgAATn/NZw Saved) Jun 18 15:55:48 mail1 postfix/qmgr[3458]: 18533C009C8: removed Jun 18 15:55:48 mail1 dovecot[1833]: replicator: Fatal: master: service(replicator): child 2948 killed with signal 6 (core not dumped - https://dovecot.org/bugreport.html#coredumps - set /proc/sys/fs/suid_dumpable to 2) Thomas Tsiakalakis Team Applikationsbetrieb GDV Dienstleistungs-GmbH Tel: +49(40)33449-4318 Fax: E-Mail: Thomas.Tsiakalakis(a)gdv-dl.de<mailto:Thomas.Tsiakalakis@gdv-dl.de> GDV Dienstleistungs-GmbH Glockengießerwall 1 D-20095 Hamburg www.gdv-dl.de<http://www.gdv-dl.de> Niederlassungen: Wilhelmstraße 43 / 43 G 10117 Berlin Frankenstraße 18 20097 Hamburg Sitz und Registergericht: Hamburg HRB 145291 USt.-IdNr : DE 205183123 Geschäftsführer: Dr. Jens Bartenwerfer Fred di Giuseppe Chiachiarella Aufsichtsratsvorsitzender: Werner Schmidt ------------------------------------------------------------------ Diese E-Mail und alle Anhänge enthalten vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese E-Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe der E-Mail ist nicht gestattet. This e-mail and any attached files may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorised copying, disclosure or distribution of the material in this e-mail is strictly forbidden.

1 0

Sieve-scripts won't replicate
by Niels Kobschätzki 18 Jun '20

18 Jun '20

Hi, I am trying to use dovecot replication for a two-way sync. And whatever I do, sieve-scripts won’t replicate. Mails replicate near instantaneous. When I disable the sieve-script in roundcube, the other server will create in the home of the user on the other side a folder sieve/tmp but enabling won’t create the roundcube.sieve and the symlink .dovecot.sieve -> sieve/roundcube.sieve The home of a virtual mail user on server1 looks like this: drwx------ 4 vexim vexim 4096 Jun 18 08:02 . drwx------ 8 vexim vexim 4096 Jun 18 07:59 .. lrwxrwxrwx 1 vexim vexim 21 Jun 18 07:59 .dovecot.sieve -> sieve/roundcube.sieve drwx------ 5 vexim vexim 4096 Jun 18 08:14 Maildir drwx------ 3 vexim vexim 4096 Jun 18 08:02 sieve A ps auxwww|grep dove looks like this (maybe some user is wrong?): ps auxwww |grep dove root 847 0.0 0.0 4200 3044 ? Ss 07:54 0:00 /usr/sbin/dovecot -F root 849 0.0 0.0 4060 2544 ? S 07:54 0:00 dovecot-team1/replicator dovecot 850 0.0 0.0 3912 1092 ? S 07:54 0:00 dovecot-team1/anvil root 851 0.0 0.0 4048 2464 ? S 07:54 0:00 dovecot-team1/log dovecot 852 0.0 0.0 4048 2692 ? S 07:54 0:00 dovecot-team1/stats root 853 0.0 0.0 6072 4368 ? S 07:54 0:00 dovecot-team1/config dovecot 855 0.0 0.0 17412 6620 ? S 07:54 0:00 dovecot-team1/auth dovenull 856 0.0 0.0 8200 6344 ? S 07:54 0:00 dovecot-team1/imap-login vexim 858 0.0 0.0 7092 5300 ? S 07:54 0:00 dovecot-team1/imap dovecot 902 0.0 0.0 3912 1096 ? S 07:55 0:00 dovecot-team1/aggregator dovenull 1929 0.0 0.0 8200 6256 ? S 08:15 0:00 dovecot-team1/imap-login vexim 1930 0.0 0.0 6984 5284 ? S 08:15 0:00 dovecot-team1/imap dovenull 1931 0.0 0.0 8200 6248 ? S 08:15 0:00 dovecot-team1/imap-login vexim 1932 0.0 0.0 6964 5140 ? S 08:15 0:00 dovecot-team1/imap root 2210 0.0 0.0 6048 892 pts/0 S+ 08:21 0:00 grep dove I do not see any errors in the log. Here is the doveconf -n output. The partner looks identical except the replication target. # 2.3.4.1 (f79e8e7e4): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.4 () # OS: Linux 4.19.0-9-amd64 x86_64 Debian 10.4 # Hostname: team.snafu.de auth_mechanisms = plain login auth_verbose = yes doveadm_password = # hidden, use -P to show it doveadm_port = 12345 instance_name = team1 mail_location = maildir:~/mail:INBOX=/var/vmail/%d/%u mail_plugins = " notify replication" 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 spamtest spamtestplus virustest editheader servermetadata imapflags notify 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 = separator = / } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { imapsieve_mailbox1_before = file:/usr/lib/dovecot/sieve/report-spam.sieve imapsieve_mailbox1_causes = COPY imapsieve_mailbox1_name = Junk imapsieve_mailbox2_before = file:/usr/lib/dovecot/sieve/report-ham.sieve imapsieve_mailbox2_causes = COPY imapsieve_mailbox2_from = Junk imapsieve_mailbox2_name = * mail_replica = tcps:server2.domain.de:12345 sieve = file:~/sieve;active=~/.dovecot.sieve sieve_dir = ~/sieve sieve_extensions = +notify +imapflags +editheader +regex +spamtest +spamtestplus +virustest +servermetadata sieve_global_extensions = +vnd.dovecot.pipe +vnd.dovecot.environment sieve_pipe_bin_dir = /usr/lib/dovecot/sieve-pipe sieve_plugins = sieve_imapsieve sieve_extprograms } protocols = " imap lmtp sieve sieve" replication_dsync_parameters = -D -d -N -l 30 -U service aggregator { fifo_listener replication-notify-fifo { mode = 0666 user = vexim } unix_listener replication-notify { mode = 0666 user = vexim } } service auth { unix_listener auth-client { group = vexim mode = 0660 user = Debian-exim } unix_listener auth-userdb { group = vexim mode = 0666 user = vexim } } service config { unix_listener config { user = vexim } } service doveadm { inet_listener { port = 12345 ssl = yes } user = vexim } service managesieve-login { inet_listener sieve { port = 4190 } process_min_avail = 0 service_count = 1 vsz_limit = 64 M } service managesieve { process_limit = 1024 } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { mode = 0666 } } ssl = required ssl_cert = </etc/ssl/certs/wildcard.domain.de.pem ssl_cipher_list = HIGH:!aNULL ssl_client_ca_dir = /etc/ssl/certs 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 { driver = prefetch } userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } protocol lda { mail_plugins = " notify replication sieve" } protocol imap { mail_plugins = " notify replication imap_sieve" } protocol lmtp { info_log_path = /var/log/dovecot-lmtp.log mail_plugins = " notify replication sieve" } protocol sieve { mail_max_userip_connections = 10 managesieve_max_line_length = 65536 } Any help appreciated. Niels

1 1

Password mismatch after upgrade to Ubuntu Focal
by Jeffrey van Doesburg 16 Jun '20

16 Jun '20

Hi! Today I upgraded one of our Dovecot servers from Ubuntu 18.04 to Ubuntu 20.04. After the upgrade I have login issues because the password didn't match. I also installed Dovecot on a clean Ubuntu 20.04 server with the same configuration files. And here I also got the password match issue. We're using LDAP for managing the login credentials and I'm 100% sure the password is correct. With the debug options on, you will see something like this: CRYPT(<PLAIN_TEXT_PASSWORD>) != '$6$<SECRET_PASSWORD_HASH>' Does somebody know if there are know issues with Dovecot 2.3.7.2- 1ubuntu3.1 on Ubuntu 20.04 and with the LDAP driver? dovecot -n ------------------------- # 2.3.7.2 (3c910f64b): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.7.2 () # OS: Linux 5.4.0-33-generic x86_64 Ubuntu 20.04 LTS ceph # Hostname: server.example.tld auth_verbose = yes disable_plaintext_auth = no listen = *, [::] log_timestamp = "%Y-%m-%d %H:%M:%S " login_greeting = POP/IMAP Service ready. mail_fsync = always mail_location = maildir:/mail/%u mail_privileged_group = mail passdb { args = /etc/dovecot/dovecot-ldap.conf driver = ldap } plugin { acl = vfile:/etc/dovecot/acls/:cache_secs=30 autosubscribe = Trash autosubscribe2 = Sent autosubscribe3 = Drafts } protocols = imap pop3 service auth { user = root } service imap-create-folder { executable = script-login /usr/local/sbin/dovecot-create-dirs.sh } service imap-login { process_min_avail = 15 service_count = 0 } service imap { executable = imap imap-create-folder } service pop3-login { process_min_avail = 15 service_count = 0 } service pop3 { drop_priv_before_exec = yes } ssl = no userdb { driver = prefetch } protocol imap { mail_max_userip_connections = 25 mail_plugins = acl } protocol pop3 { pop3_uidl_format = %f } ------------------------------ /etc/dovecot/dovecot-ldap.conf ------------------------------ hosts = ldap.server.example.tld dn = <XXXXX> dnpass = <XXXXX> auth_bind = no ldap_version = 3 base = <XXXXX> pass_attrs = <XXXXX> pass_filter = <XXXXX> ----------------- Thanks! Jeffrey

2 5

Send SPF SoftFails to Junk
by Scott A. Wozny 14 Jun '20

14 Jun '20

Hello Dovecot gurus, I've set up SPF checking on my postfix gateway and have confirmed that messages from domains set with hard fails that don't come from a good sender are rejected outright. Messages from domains set with a softfail that come from bad sources are tagged in the message header with "Softfail (domain owner discourages use of this host)", but end up in the user's Inbox, anyway. I suppose I kind of figured DoceCot would see the SPF softfail in the message header and automagically route that message to Junk, but it didn't. I've looked around Google and the Dovecot documentation to see if there are any instructions on how to do this, but I can't find anything. Is there an easy way to do this or do I need something more advanced in the way of a spam filtering system? OR is doing this my mail client's responsibility and I need to look around my Thunderbird settings? I suppose it's also possible that Postfix needed to do something beyond adding the Received-SPF line in the message header, but I didn't see anything about that in the Policy-SPF config. This is my first foray into SPF so I'm open to any suggestions. Thanks, Scott

2 2

Login auth strip domain from username
by David Pottage 14 Jun '20

14 Jun '20

Hi, I have just discovered that the IMAP account setup wizard in outlook 2019 assumes that the email address for a user is the same as their username, and there is no easy way to separately enter different user. (It can be done via hidden dialog boxes, command line switches and registry hacking, but it is far from easy [1]) Like many small setups, the dovecot accounts on my mail server map directly to unix accounts on the machine, and the IMAP password for each account is the same as the unix login password. I have now got outlook sorted and talking to my IMAP server, but seeing as this issue will almost certainly arise again, with out over-simplified MUA software, is there a setting in dovecot that if it is given an email address as a login username it strips off the domain part, and tests the user part against the password supplied? If you know how to do that for postfix for sending email, then even better! [1] https://superuser.com/questions/1391960/how-to-enter-username-of-imap-accou… -- David Pottage

4 3

handling spam from gmail.
by Marc Roos 12 Jun '20

12 Jun '20

I am sick of this gmail spam. Does anyone know a solution where I can do something like this: 1. received email from adcpni444(a)gmail.com 2. system recognizes this email address has been 'whitelisted', continue with 7. 3. system recognizes as this email never been seen before 4. auto reply with something like (maybe with a wait time of x hours): Your message did not receive the final recipient. You are sending from a known spam provider network that is why we blocked your message. Please confirm that: - you are not a spammer and - you have permission to use the mail adress you send your message to - you and your provider agree to uphold GDPR legislation - you and your provider are liable for damages when breaching any of the above. Click link to confirm and you agree with the above https://www.domainwithoutletsencryptcertificate.com/asdfasdfadsfaf 5. sender clicks confirm url 6. email address is added to some white list. 7. email is delivered to recipient.

16 27

Read-flag of mails don't update
by Marius Rasch 12 Jun '20

12 Jun '20

Hi, since one or two month I have a problem with Dovecot not updating the read-flag on mails using IMAP. I receive new mails, but when reading, they still unread on other devices (but shown as read on the first device). When I remember correct, this problem doesn't come with an update of dovecot, but just occured at some time. But I've updated dovecot since then a few times. Whenever a client connects to dovecot I get an panic in the log. I therefore added a log file and my dovecot configuration (is this fine or does it need to be in the mail body?). There are system information in the output of dovecot -n; the filesystem dovecot is running on is ext4. I hope I provided all information needed and seeing forward to get a hint what the problem might be. Marius

3 7

executing script on mail arrival from sieve
by Voytek Eymont 12 Jun '20

12 Jun '20

I currently have a basic script to process some mails, it runs from cron every 10 minutes, basically, sieve copies some mails to subfolder on mail arrival, script fetches mails if any from this subfolder then processes these mail, get maybe 1 or 2 or often none but cron runs the script every 10 minutes, most times not needed as nothing is retrieved it's pretty crude - but works getmail fetches mails to local folder, deletes in subfolder munpack mailfile to unMIME links dumps HTML to txt looking at wiki2, 'Pigeonhole Sieve Extprograms Plugin', is this what would allow to execute my script on new mail arrival? I can't quite figure out how to.. if anyone has any sample, I might try to adapt to my need.. thanks (probably I should just leave like it is till I understand the docs...) thanks, V

2 2

Doveadm Backup (other) issues
by Gingko 11 Jun '20

11 Jun '20

Hello, I also have issues using Dovecot Backup. I am trying to Backup (or possibly Sync - one way) a single user IMAP account from a remote server, unknown type, to my own server. For that purpose, I defined the following parameters : imapc_host = <host name> imapc_user = <user name> imapc_password = <password> imapc_features = rfc822.size (<user name> has format: name(a)example.com, and <host name> is the name of the imap remote server that I use for getting mails) … and then I issued the following command: doveadm backup -R -u <user name, format name(a)example.com> imapc: ... but doing this, I get the following answer: dsync(<user name>): Info: imapc(<host name>:143): Connected to <host IP address>:143 (local 192.168.1.2:52940) dsync(<user name>): Error: Failed to initialize user: namespace configuration error: Namespace mail/ can't have alias_for= to a different storage (different root dirs) How can I solve this? If there is something not matching between servers, I may eventually change configuration on my side, but I think I would first have to know which feature(s) I have to know from the remote server in order to create the matching one on my server. Is there a way to list all relevant data coming from the remote server? Also: Doing this, is it necessary that the source user name be the same as the destination user name? Is it possible to backup an IMAP account to a user account having a completely different name? Regards, Gingko

5 7

Dovecot /VMWare Boxer
by Djule Djukic 11 Jun '20

11 Jun '20

Hello all, My name is Djule Djukic and I am working for Hipotekarna Banka from Montenegro. We are using IMAP email server Dovecot version 2.1.17. As a email clients on our corporate workstations we are using Thunderbird or WebMail and everything is working fine. We decided to introduce MDM solution in our environment and we installed VMWare WorkspaceOne (former Airwatch) which use Boxer as a mail client in App per VPN scenario. When we syncronise email with Boxer we have found that the time and date displayed for some messages have been changed to the time at which the file was synchronized. This is not hapening with all messages. It is happening only with messages in subfolders, never with Inbox. It seems when messages is moved by some rule from WebMail or Thunderbird from Inbox to some subfolder, Boxer is not able to read dates correctly, By seraching on Internet we found couple of explanation what might be possibel cause of this behaviour. https://imapsync.lamiral.info/FAQ.d/FAQ.Dates.txt https://serverfault.com/questions/588618/maintain-email-timestamp-when-tran… https://dovecot.org/pipermail/dovecot/2008-July/032165.html Problem with some email clients is that they not look always for "Date:" from email message header. The "Date:" header is usually the date the message was written or sent the first time, at the writer side. This "Date:" header line is never changed by any transfer or copy. If an email client uses the "Date:" header for displaying the date of a message then no problem in synchronization with wrong date should arise. Obviously this is not a case with a Boxer email application. We tried GMail and everything is working fine. We are wondering if someone can explain what APPEND command could have done in our case? Is it relevant at all for our case? Is it used somehow by thunderbird or webmail clients? Also we would like to hear from someone if there are some improvemnents in further release of dovecot or some configuration that we can implement in order to fix this? Thank you in advanced for your suggestions and contribution, Đule Đukić Specijalista za informacionu bezbjednost / ISO ĐuleĐukić Specijalistaza informacionu bezbjednost / ISO http://www.hipotekarnabanka.com/hb-content/uploads/2014/06/slika1.jpg

3 3

RE: handling spam from gmail.
by Marc Roos 11 Jun '20

11 Jun '20

Yes tell that to the people that create rhel6, rhel7 and rhel8 and give lts support. Unless google pays you to train your software to mark their messages as spam, you might want to consider yourself not to smart as well ;) My solution would solve the problem others create (see the other mail). Your solution wastes your time and will always be carrying water to the sea. I think if 50% of providers in the world would do this, it would quickly be end of story for the spam originating from the networks like google and amazon. If there is a McDonalds build next to your home, and their clients throw waste into your garden. You hold McDonalds liable for cleaning this up not? Or are you also going to cleanup their mess indefinitely. -----Original Message----- From: Reindl Harald [mailto:h.reindl@thelounge.net] Sent: donderdag 11 juni 2020 11:09 To: Marc Roos; dominic; dovecot; lists; users Subject: Re: handling spam from gmail. Am 11.06.20 um 11:04 schrieb Marc Roos: > I have got lots of shit coming from *.google.com like these: > > X-Spam-Status: No, score=2.1 required=3.0 tests=BAYES_00 because you are too dumb to train your bayes give me one such message and i am pretty sure it will fire BAYES_80 or BAYES_99 which will burn it with fire and lead to a milter reject here SpamAssassin 3.3.1 is also not very smart in 2020 so instead ask for dumb solutions which making you part of a bigger problem better do your homework

2 1

Pigeonhole-sieve auto-reply
by ＠lbutlr 11 Jun '20

11 Jun '20

Is it possible to have a sieve script reply with a press message to certain emails (and only certain emails) based on sieve matches? I see a lot on vacation replies, but I want something more specific. Something along the lines of procmails formail command? Everything I’ve searched for is about vacation r filing replies into the same folder as the original message.

2 2

Special use folders in mailbox hierarchy
by Scott A. Wozny 11 Jun '20

11 Jun '20

Dear Dovecot Gurus, Setting up my first IMAP server and looking at the folder structure, I had a mailbox I built on a Dovecot server and a mailbox configured by a hosting provider next to each other in Thunderbird and I noticed that the special use folders (Drafts, Trash and Sent) in my default-ish (I did set them to auto = subscribe) Dovecot install make these folders appear parallel to my Inbox folder where my hosting provider’s default configuration has them under the Inbox hierarchically, along with all the folders I built for mail storage over the use of the account. I did some googling, but I cannot find any guidance on which of these is preferred, why, or how they could be controlled in Dovecot. The default Dovecot config is ambiguous (IMHO) in that the mailbox config elements are children to the inbox namespace (implying they go under Inbox in the hierarchy) but their special_use parameter names are \Name which (if you use a UNIX filesystem paradigm) implies they should be at the root of the hierarchy and, therefore, parallel with Inbox, which is how Thunderbird shows them, but I’m not sure if that’s a mail client decision and not anything to do with the server configuration. Since I can’t access the config of my hosting provider, I can’t make any comparisons, so I thought I’d ask on the list if there is any standard guidance on server side configuration of special use folders in Dovecot or if there’s no guidance available because I’m overthinking this. :) Thanks, Scott

3 3

RE: handling spam from gmail.
by Marc Roos 11 Jun '20

11 Jun '20

>> Yes tell that to the people that create rhel6, rhel7 and rhel8 and give >> lts support. > >as said that has nothing to do with your wrong training and RHEL has >always the same problem: you can't package the latest and greatest shit >over 10 years because it requrires newer versions of dependencies > >so what you get with your lazyness by using a LTS distribution is a >"never change a running system, just fix the worst bugs and don't touch >anything else" > >upstream developers don't hold development for 10 years > >written from a Fedora workstation with kernel 5.6.18-200.fc31.x86_64 >from last night realyed over a datacenter firewall and a mailserver >using the same kernel > >> Unless google pays you to train your software to mark their messages as >> spam, you might want to consider yourself not to smart as well ;) > >unless i make good money from customers paying for a nearly 100% >hitrate of spam combine with a zero-false-positive policy i am likely >smarter than you I would argue it is quite difficult to identify intelligence. I am pretty sure I would not start with your reasoning. I have a favourite German saying I like to quote in matters like these "gegen Dummheit kämpfen Götter selbst vergebens" >> My solution would solve the problem others create (see the other mail). >> Your solution wastes your time and will always be carrying water to the >> sea. I think if 50% of providers in the world would do this, it would >> quickly be end of story for the spam originating from the networks like >> google and amazon. > >they won't give a shit and when i get such idiotic mails as you propose >i take the phone, call the sender and suggest to fire his mailadmin >better sooner than later > >> If there is a McDonalds build next to your home, and their clients throw >> waste into your garden. You hold McDonalds liable for cleaning this up >> not? Or are you also going to cleanup their mess indefinitely. > >what a nonsense

1 0

RE: handling spam from gmail.
by Marc Roos 11 Jun '20

11 Jun '20

Your logics sucks. There is a difference between how email works and how spamassassin works. You are assuming that everyone in the world is using spamassassin by including it in 'how email works'. Maybe you like to post a link to your bayes files???? Am 11.06.20 um 11:13 schrieb Marc Roos: > You do not understand how mail works. Google mail is only getting > through when spf checks and the likes are being passed. unless you don't manage to get rid of BAYES_00 in case of clear spam messages don't tell me you understand how email works

1 0

RE: handling spam from gmail.
by Marc Roos 11 Jun '20

11 Jun '20

You do not understand how mail works. Google mail is only getting through when spf checks and the likes are being passed. I am not creating any problems with this, I am just bouncing them back. Google has enough billions to handle these issues. If everyone would apply this procedures, people with legitimate email accounts would move from a spam network to some other provider. People joining these providers are the problem, because it allows these networks to mix spam with legitimate email. When clients start moving out, spam networks are becoming easier to hard block and these providers start thinking about their infrastructure and their bussines model. If everyone would be doing this, it is solving the spam problem. My below procedure should be applicable for any network generating a lot of spam. -----Original Message----- From: Reindl Harald [mailto:h.reindl@thelounge.net] Sent: donderdag 11 juni 2020 10:25 To: Marc Roos; dovecot; users Subject: Re: handling spam from gmail. Am 11.06.20 um 10:19 schrieb Marc Roos: > I am sick of this gmail spam. Does anyone know a solution where I can > do something like this: > > 1. received email from adcpni444(a)gmail.com 2. system recognizes this > email address has been 'whitelisted', continue with 7. > 3. system recognizes as this email never been seen before 4. auto > reply with something like (maybe with a wait time of x hours): > Your message did not receive the final recipient. You are sending > from a known spam provider > network that is why we blocked your message. Please confirm that: > - you are not a spammer and > - you have permission to use the mail adress you send your message to > - you and your provider agree to uphold GDPR legislation > - you and your provider are liable for damages when breaching any > of the above. > > > Click link to confirm and you agree with the above > https://www.domainwithoutletsencryptcertificate.com/asdfasdfadsfaf > > 5. sender clicks confirm url > 6. email address is added to some white list. > 7. email is delivered to recipient. and i am sick of people not understanding how email works! you don't send unasked mail to a in the most cases forged sender unless you want to be part of the problem backscatters and brainless autoreplies have to be burnt with fire

1 0

Dovecot fs quota reports quota as byte
by Kazim Koybasi 11 Jun '20

11 Jun '20

Hello, My dovecot configuration is like below. My filesystem quota is reported as kb and dovecot quota reported as bytes so dovecot quota becomes wrongly greater than filesystem quota. How can I solve this issue? Any help apretiated. Quota name Type Value Limit % user STORAGE 10428416 3242880 321 # 2.2.36 (1f10bfa63): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.24 (124e06aa) # OS: Linux 4.18.0-147.8.1.el8_1.x86_64 x86_64 CentOS Linux release 8.1.1911 (Core) # Hostname: suretired auth_mechanisms = plain login auth_username_format = %Ln debug_log_path = /var/log/dovecot.log first_valid_uid = 1000 lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes listen = * mail_debug = yes mail_location = maildir:~/Maildir:INDEX=/var/no-quotas/index/%u:CONTROL=/var/no-quotas/control/%u mail_plugins = quota 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 mbox_write_locks = fcntl namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { auto = subscribe special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { driver = pam } plugin { quota = fs:user sieve = file:~/sieve;active=~/.dovecot.sieve sieve_before = /etc/dovecot/sieve/default.sieve sieve_extensions = +spamtest +spamtestplus sieve_spamtest_max_value = 15 sieve_spamtest_status_header = X-Spam-Score: (-?[[:digit:]]+\.[[:digit:]]).* sieve_spamtest_status_type = score } protocols = imap pop3 lmtp sieve service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0600 user = postfix } unix_listener auth-userdb { group = postfix mode = 0600 user = dovecot } } service lmtp { executable = lmtp -L inet_listener lmtp { address = 127.0.0.1 port = 2424 } unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } service managesieve-login { inet_listener sieve { port = 4190 } } service managesieve { process_limit = 1024 } service quota-warning { executable = script /usr/bin/quota-warning.sh unix_listener quota-warning { group = dovecot mode = 0600 user = dovecot } user = dovecot } ssl_cert = </etc/pki/dovecot/certs/letsencrypt/fullchain1.pem ssl_cipher_list = ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-SHA384:ECDHE-ECDSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA:ECDHE-ECDSA-AES256-SHA ssl_key = # hidden, use -P to show it ssl_prefer_server_ciphers = yes ssl_protocols = !SSLv3 !TLSv1 userdb { driver = passwd } protocol lmtp { info_log_path = /var/log/dovecot-lmtp.log log_path = /var/log/dovecot-lmtp-errors.log mail_plugins = quota sieve quota } protocol lda { mail_plugins = quota sieve quota } protocol imap { mail_plugins = quota quota imap_quota } protocol sieve { info_log_path = /var/log/dovecot-sieve.log log_path = /var/log/dovecot-sieve-errors.log managesieve_max_line_length = 65536 } protocol pop3 { mail_plugins = quota pop3_quota quota pop3_client_workarounds = outlook-no-nuls oe-ns-eoh pop3_uidl_format = %08Xu%08Xv }

1 0

How to unset namespace configuration from dovecot.conf in conf.d/99-cutom.conf?
by Py Retta 09 Jun '20

09 Jun '20

Dear all, my /etc/dovecot/dovecot.conf [0] that is shipped with the Linux distro (Ubuntu 18.04, dovecot 2.3.10) has a namespace section: namespace inbox { ... mailbox Sent { ... } ... } I need to remove this whole section from the configuration, but I need to do this in a file such as /etc/dovecot/conf.d/99-custom.conf because I want this modification to be stable against automatic updates of dovecot.conf shipped by the distro. This raises the question, how do I "unset" an earlier namespace configuration at a later point in the stack of config files? Speaking in terms of `doveconf -n`, snippet [1] below lists the original configuration (including namespace setup) and [2] lists the desired configuration that results from deleting the namespace passage from dovecot.conf. However, I would like to achieve it without deleting it from dovecot.conf but by adding sth to conf.d/99-custom.conf. Thanks a lot, Py [0] original dovecot.conf (only relevant namespace section): # Default private namespace setup compatible with Courier-IMAP. namespace inbox { separator = . prefix = INBOX. inbox = yes mailbox Sent { auto = subscribe # autocreate and autosubscribe the Sent mailbox special_use = \Sent } mailbox Spam { auto = create # autocreate Spam, but don't autosubscribe special_use = \Junk } mailbox Drafts { auto = create special_use = \Drafts } mailbox Trash { auto = create special_use = \Trash } } [1] `doveconf -n` for the original configuration: # 2.3.10 (0da0eff44): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.9 (db4e9a2f) doveconf: Warning: service auth { client_limit=1000 } is lower than required under max. load (2248) doveconf: Warning: service anvil { client_limit=1000 } is lower than required under max. load (2251) # OS: Linux 4.15.0 x86_64 Ubuntu 18.04.4 LTS ext4 # Hostname: ############ auth_mechanisms = ####################### auth_username_chars = ################ disable_plaintext_auth = #### first_valid_uid = #### imap_client_workarounds = delay-newmail imap_logout_format = rcvd=%i, sent=%o mail_home = ################## mail_location = ##################### mail_log_prefix = "service=%s, user=%u, ip=[%r]. " mail_plugins = " quota" managesieve_logout_format = rcvd=%i, sent=%o managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date index ihave duplicate mime foreverypart extracttext imapflags notify namespace inbox { inbox = yes location = mailbox Drafts { auto = create special_use = \Drafts } mailbox Sent { auto = subscribe special_use = \Sent } mailbox Spam { auto = create special_use = \Junk } mailbox Trash { auto = create special_use = \Trash } prefix = INBOX. separator = . } passdb { driver = plesk } plugin { quota = maildir:User quota quota_grace = 0 quota_warning = storage=95%% quota-warning %u sieve = ~/.dovecot.sieve sieve_dir = ~/sieve sieve_extensions = +notify +imapflags } pop3_client_workarounds = outlook-no-nuls oe-ns-eoh pop3_logout_format = rcvd=%i, sent=%o, top=%t/%p, retr=%r/%b, del=%d/%m, size=%s protocols = imap pop3 sieve service auth-worker { group = user = } service auth { group = unix_listener auth-userdb { group = popuser mode = 0600 user = popuser } user = } service imap-login { process_limit = 1024 service_count = 1 } service imap { process_limit = 1024 service_count = 1 } service pop3-login { process_limit = 1024 service_count = 1 } service pop3 { process_limit = 1024 service_count = 1 } service quota-warning { executable = ################ unix_listener quota-warning { user = popuser } user = popuser } service stats { unix_listener stats-writer { user = popuser } } ssl_cert = ################ ssl_cipher_list = ############# ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it ssl_prefer_server_ciphers = yes userdb { args = uid=popuser gid=popuser driver = static } protocol imap { mail_plugins = " quota imap_quota" } protocol pop3 { pop3_uidl_format = UID%u-%v } protocol lda { mail_plugins = " quota sieve" } [2] `doveconf -n` for the desired configuration (with the namespace section in dovecot.conf removed): # 2.3.10 (0da0eff44): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.9 (db4e9a2f) doveconf: Warning: service auth { client_limit=1000 } is lower than required under max. load (2248) doveconf: Warning: service anvil { client_limit=1000 } is lower than required under max. load (2251) # OS: Linux 4.15.0 x86_64 Ubuntu 18.04.4 LTS ext4 # Hostname: ############ auth_mechanisms = ####################### auth_username_chars = ################ disable_plaintext_auth = #### first_valid_uid = #### imap_client_workarounds = delay-newmail imap_logout_format = rcvd=%i, sent=%o mail_home = ################## mail_location = ##################### mail_log_prefix = "service=%s, user=%u, ip=[%r]. " mail_plugins = " quota" managesieve_logout_format = rcvd=%i, sent=%o managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date index ihave duplicate mime foreverypart extracttext imapflags notify passdb { driver = plesk } plugin { quota = maildir:User quota quota_grace = 0 quota_warning = storage=95%% quota-warning %u sieve = ~/.dovecot.sieve sieve_dir = ~/sieve sieve_extensions = +notify +imapflags } pop3_client_workarounds = outlook-no-nuls oe-ns-eoh pop3_logout_format = rcvd=%i, sent=%o, top=%t/%p, retr=%r/%b, del=%d/%m, size=%s protocols = imap pop3 sieve service auth-worker { group = user = } service auth { group = unix_listener auth-userdb { group = popuser mode = 0600 user = popuser } user = } service imap-login { process_limit = 1024 service_count = 1 } service imap { process_limit = 1024 service_count = 1 } service pop3-login { process_limit = 1024 service_count = 1 } service pop3 { process_limit = 1024 service_count = 1 } service quota-warning { executable = ################ unix_listener quota-warning { user = popuser } user = popuser } service stats { unix_listener stats-writer { user = popuser } } ssl_cert = ################ ssl_cipher_list = ############# ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it ssl_prefer_server_ciphers = yes userdb { args = uid=popuser gid=popuser driver = static } protocol imap { mail_plugins = " quota imap_quota" } protocol pop3 { pop3_uidl_format = UID%u-%v } protocol lda { mail_plugins = " quota sieve" }

1 0

doveadm protocol bug
by Felipe Gasper 08 Jun '20

08 Jun '20

Hi everyone, On 26th May I emailed this list a few times about an apparent protocol bug in Dovecot’s server-side doveadm implementation. Later that day I sent in a pull request to fix the issue. Thread reference: https://dovecot.org/pipermail/dovecot/2020-May/119066.html Pull request: https://github.com/dovecot/core/pull/129 Thus far neither the mailing list emails nor the PR have garnered any responses. Can someone please weigh in on these? It’s totally understandable if Dovecot’s behavior here is going to say as-is; I’d just like some confirmation so we can note it in our client implementation. (Switching our client to the HTTP API would be out-of-scope for our current project.) Thank you again! cheers, -Felipe Gasper

1 0

Can't share a mailbox
by Maxime DERCHE 08 Jun '20

08 Jun '20

Hello, I have a "notifs@" generic mail account, intended to receive technical monitoring messages. I need to share it with the people of the analyst team. I created a shared namespace, and enabled the modules. doveadm acl creates the dovecot-acl file but not the acl_shared_dict file. I guess something prevents it from doing it, but I fail to see what. It is a LDAP setup, and there is only one vmail (uid/gid 500) UNIX account to read and write the files on the file system. $ > doveadm acl add -u notifs(a)test.example.tld "shared/notifs(a)test.example.tld/INBOX" user=maxime.derche(a)test.example.tld :lrw $ > doveadm acl debug -u maxime.derche(a)test.example.tld "shared/notifs(a)test.example.tld/INBOX" doveadm(maxime.derche(a)test.example.tld): Info: Mailbox 'INBOX' is in namespace 'shared/notifs(a)test.example.tld/' doveadm(maxime.derche(a)test.example.tld): Info: Mailbox path: /var/vmail/test.example.tld/notifs/mail doveadm(maxime.derche(a)test.example.tld): Info: Per-user private flags in mailbox: \Seen doveadm(maxime.derche(a)test.example.tld): Info: User maxime.derche(a)test.example.tld has rights: lrw doveadm(maxime.derche(a)test.example.tld): Error: User maxime.derche(a)test.example.tld is missing 'lookup' right doveadm(maxime.derche(a)test.example.tld): Info: Mailbox shared/notifs(a)test.example.tld/INBOX is NOT visible in LIST /var/vmail/test.example.tld/notifs/mail/dovecot-acl: ---------------------------------------- user=maxime.derche(a)test.example.tld :lrw ---------------------------------------- dovecot -n ---------------------------------------- # 2.3.4.1 (f79e8e7e4): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.4 () # OS: Linux 4.19.0-9-amd64 x86_64 Debian 10.4 # Hostname: server.example.tld auth_debug = yes auth_mechanisms = plain login auth_verbose = yes lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes lmtp_save_to_detail_mailbox = yes mail_access_groups = vmail mail_debug = yes mail_gid = 5000 mail_location = maildir:~/Maildir mail_plugins = quota acl mail_privileged_group = mail mail_server_admin = mailto:postmaster@test.example.tld mail_shared_explicit_inbox = yes mail_uid = 5000 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 { list = children location = maildir:%%h/mail:INDEXPVT=~/mail/shared/%%u prefix = shared/%%u/ separator = / subscriptions = no type = shared } namespace inbox { inbox = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk { auto = subscribe autoexpunge = 30 days special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox Trash { auto = subscribe autoexpunge = 30 days special_use = \Trash } prefix = separator = / } passdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } plugin { acl = vfile acl_shared_dict = file:/var/vmail/shared-mailboxes imapsieve_mailbox1_before = file:/etc/dovecot/sieve/learn-spam.sieve imapsieve_mailbox1_causes = COPY imapsieve_mailbox1_name = Junk imapsieve_mailbox2_before = file:/etc/dovecot/sieve/learn-ham.sieve imapsieve_mailbox2_causes = COPY imapsieve_mailbox2_from = Junk imapsieve_mailbox2_name = * recipient_delimiter = + sieve = file:~/sieve;active=~/.dovecot.sieve sieve_after = /etc/dovecot/sieve-after sieve_before = /etc/dovecot/sieve-before sieve_global_extensions = +vnd.dovecot.pipe sieve_pipe_bin_dir = /etc/dovecot/sieve sieve_plugins = sieve_imapsieve sieve_extprograms } protocols = " imap lmtp sieve" service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } ssl = required ssl_cert = </etc/ssl/certs/cert.pem ssl_cipher_list = HIGH:!ADH:!AECDH:!PSK:!KRB5:!RC4:!DES:!3DES:!MD5 ssl_client_ca_dir = /etc/ssl/certs 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 = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap override_fields = home=/var/vmail/%d/%n } protocol lmtp { mail_plugins = quota acl sieve userdb { args = allow_all_users=yes uid=vmail gid=vmail home=/var/vmail/%d/%n mail=maildir:~/mail driver = static name = } } protocol imap { mail_plugins = quota acl imap_sieve imap_acl } ---------------------------------------- Does anyone see what I'm doing wrong here? Kind regards, -- Maxime DERCHE Information System Consulting France | NVMQVAM SOLVS https://www.mdisc.fr/ OpenPGP Key ID: 0x814E02A25697FD13 OpenPGP Key Fingerprint: 8B7B 60C9 1095 A198 C883 5205 814E 02A2 5697 FD13

1 0

Doveadm Backup issues
by Francis Augusto Medeiros-Logeay 07 Jun '20

07 Jun '20

Hi, I'm trying to use doveadm backup but I'm having a few issues. When trying locally: `doveadm backup -D -A maildir:/usr/local/backup` It results that no mailbox is separated by user - all seems to sync on the same folder, messing up with the folder structure of the original maildir. When trying remotely: `doveadm backup -D -A -N ssh -i mykey root@myremotebackup.com:/backup doveadmin dsync-server -A` I get this error line for each user: dsync-local(theuser(a)thedomain.com)<5DNrEXdG1l5tAgAAqsACHw>: Error: read(remote) failed: EOF (version not received) doveadm(theuser(a)thedomain.com): Fatal: execvp(ssh) failed: No such file or directory I'd be very thankful if someone could help me with this. Best, Francis -- Francis Augusto Medeiros-Logeay Oslo, Norway

3 5

Deliver administrative message ignoring user quota
by Peter Folta 07 Jun '20

07 Jun '20

Hi everyone, I have a separate internal system running on a different host that needs to put an administrative email into a user’s inbox. I’ve been playing around with the “doveadm mailbox save” command via Doveadm’s HTTP API (https://doc.dovecot.org/admin_manual/doveadm_http_api/#doveadm-mailbox-save <https://doc.dovecot.org/admin_manual/doveadm_http_api/#doveadm-mailbox-save>). This works quite well provided the user is within quota limit, however, I would like to be able to deliver these messages even if the email account is over quota. I noticed that it’s possible to override the quota configuration using dovecot-lda by overriding plugin/quota with the “noenforcing” directive as explained in https://wiki.dovecot.org/Quota/Configuration <https://wiki.dovecot.org/Quota/Configuration>. I don’t currently use LDA, SMTP servers based on Postfix deliver mail via LMTP and I need to be able to deliver this message from a different host in the network. The HTTP API doesn’t seem to support overriding the quota config. What would be the best way to go about this? Thanks Peter

2 2

(no subject)
by Stephen Blackwell 07 Jun '20

07 Jun '20

I want to disable the time penalty for dovecot imap authentication. When receiving a valid user-password combo the server responds in .04 seconds. When I send in an invalid comination it will either respond in 1.544 or 2.044 seconds += .002 I am using dovecot to test a program that sends a login request to a server and processes the response. I want to be able to send a series of valid and invalid login attempts. The issue is that with the 2 seconds delay for a bad login attempt, the tests are too slow to run in production I can see that the delay is defined in auth-penalty.h Is there a way, in the config file, to set AUTH_PENALTY_INIT_SECS = 0, or any other way to remove the time delay for an invalid login. I am running dovecot version 2.2.33.2 I am running without root permissions I do not want to make changes outside of the dovecot config file, password file, or run folder. -- Stephen

3 2

Cannot log in to IMAP server and logs are unclear as to why
by Scott A. Wozny 07 Jun '20

07 Jun '20

I’m trying a super basic config based upon https://wiki.dovecot.org/HowTo/PostfixDovecotLMTP but before I work on shipping mail through Postfix to DoveCot, I wanted to make sure IMAP is working first, but I can’t even get a basic login to so I thought I’d see if the gurus on the list might be able to point out I’m doing wrong. The documentation is pretty good, but there were some gaps I had to guess at and I’m presuming that’s where I went wrong. I’ve turned SELinux to permissive mode, for now. Here’s the doveconf -n: # 2.2.36 (1f10bfa63): /etc/dovecot/dovecot.conf # OS: Linux 3.10.0-1062.12.1.el7.x86_64 x86_64 CentOS Linux release 7.7.1908 (Core) # Hostname: imap first_valid_uid = 1000 listen = 192.168.1.207 mail_gid = vmail mail_home = /var/vmail/%d/%n mail_location = sdbox:~/mail mail_uid = vmail 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 = / } passdb { args = scheme=PLAIN username_format=%u /etc/dovecot/users driver = passwd-file } protocols = imap lmtp service lmtp { group = vmail unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } user = vmail } ssl = no ssl_cert = </etc/pki/dovecot/certs/dovecot.pem ssl_key = # hidden, use -P to show it userdb { args = username_format=%u /etc/dovecot/users driver = passwd-file } I wasn’t sure how to set rights on the users file: [sawozny@imap var]$ cat /etc/dovecot/users test@test.com:{plain}test [sawozny@imap var]$ ls -la /etc/dovecot/users -rw-r--r--. 1 root root 26 Jun 3 23:31 /etc/dovecot/users Also, didn’t know what rights to set on the /var/vmail directoy so I did this: drwxrwx---. 3 vmail vmail 4096 Jun 3 20:52 vmail This directory is also empty except for the lost+fond directory that comes with a disk mount point. My understanding is that the mail home and maildir will manifest automagically on first login, but if I need to prime the pump, please let me know what I need to do. For my test, I did: [sawozny@imap var]$ telnet 192.168.1.207 143 Trying 192.168.1.207... Connected to 192.168.1.207. Escape character is '^]'. * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE AUTH=PLAIN] Dovecot ready. 01 LOGIN test(a)test.com test 01 NO [UNAVAILABLE] Internal error occurred. Refer to server log for more information. Connection closed by foreign host. And the results in the /var/log/maillog file are: Jun 3 23:35:34 imap dovecot: auth: Error: passwd-file /etc/dovecot/users: User test(a)test.com is missing userdb info Jun 3 23:35:44 imap dovecot: auth: Error: passwd-file(test(a)test.com,192.168.1.207,<DBqafDan7ODAqAHP>): user not found from userdb Jun 3 23:35:44 imap dovecot: imap: Error: Authenticated user not found from userdb, auth lookup id=843055105 (auth connected 0 msecs ago, handshake 0 msecs ago, request took 0 msecs, client-pid=12047 client-id=1) Jun 3 23:35:44 imap dovecot: imap-login: Internal login failure (pid=12047 id=1) (internal failure, 1 successful auths): user=<test(a)test.com>, method=PLAIN, rip=192.168.1.207, lip=192.168.1.207, mpid=12049, secured, session=<DBqafDan7ODAqAHP> I’m not sure where I’ve gone wrong. From my understanding of the documentation, all I need in the userdb is name and password. UID, GID and HOME are also indicated as required, but I set them at the system level, so why is the system telling me the user was not found? This definitely isn’t my first rodeo with Linux, but I know almost nothing about messaging so in that regard I’m a totally n00b and would really appreciate some guidance. Thanks, Scott

3 5

Only show mails within 30 days or 60 days?
by hfh＠cndns.com 05 Jun '20

05 Jun '20

How to display emails within 30 days or 60 days in inbox, sent box, etc. For example, in the mail client tool, the user clicks the inbox button and only sees the mail within 30 days. The virtual mailbox plugin will only generate a new mailbox. Thank you！！！

4 3

manual mdbox lock
by rudolf＠padaru.de 05 Jun '20

05 Jun '20

Good Morning, i have a question about the mdbox dotlock technique. We create a new backup strategy for our mailservers because we want to switch the mailformat from mbox to mdbox. Our recent backup plan works mainly with rsync and the inbuild tar function. We want to hande the backups with mdbox similar. Is there a way, how i can write-lock a mail user via the doveadm command or with dotlock files? I have searched the doveadm-sync code but i cant make out the point where the command lock the mailbox for write access. We work with Ubuntu 18, dovecot 2.33.2 Mit freundlichen Grüßen Yours sincerely <https://padaru.de/> Pascal Rudolf | Geschäftsführer PADARU-IT | Bielebohstraße 10 | 02736 Beiersdorf @: rudolf(a)padaru.de | www: <http://padaru.de/> padaru.de mobil: +49 (0) 17 772 595 32

1 0

Mailbox & Server Down
by Andrea Miconi 04 Jun '20

04 Jun '20

My mailboxes are on a Dovecot (IMAP) server.On DNS there is an MX record pointing to the server.To read the mail I use Roundcube.If the server is down, I lose the new mail. I would like to do two things, alternatively. First option.1) I keeep the mail on the provider's server, restoring the original MX record.2) Dovecot does not receive the mail, but should go to download it.3) I can access the server with Roundcube to read the downloaded mail, but if the server is down I can always go to read the mail on the provider's server with its webmail Second optionI install a second mail server and the two have to replicate the mail.But I don't know how to do it, so I need a guide with instructions.Furthermore Roundcube would always access only one server and if this is down, how can I connect to the second one?This is a typical situation for webmail like Yahoo, Outlook or GMail, but I'm not Yahoo, Microsoft and Google ;) Thanks in advance for any advice.

5 7

Error deleting INBOX when doing an imap sync
by Des Magner 04 Jun '20

04 Jun '20

Hi I am trying to set up a new mail server with dovecot. I got it all installed and set up successfully but am running into problems trying to migrate from my current email server. I tried the following command: doveadm -Dv -o imapc_host=[current-imap-host] -o imapc_user=[current-user] -o imapc_password=[password] -o imapc_features=rfc822.size -o mail_fsync=never backup -R -u [user] imapc: It connects fine but eventually fails with the following errors: dsync([user]): Error: Mailbox INBOX sync: mailbox_delete failed: INBOX can't be deleted. dsync([user]): Debug: brain S: Remote mailbox tree: INBOX guid=[xxx] uid_validity=1591096439 uid_next=1 subs=no last_change=0 last_subs=0 dsync([user] Debug: imapc([current-imap-host]:143): Disconnected I am guessing the new INBOX is not compatible with the Inbox on my current mail server so it is trying to delete it. If so is there a way I can change my configuration to allow it to be deleted?

3 2