- dovecot - dovecot.org

Error suggestions please
by Remo Mattei 27 May '19

27 May '19

May 25 15:01:27 imap(xxxxx(a)italy1.com)<10256><LsrOdL2J3uisCqP7>: Error: Mailbox INBOX: UID=208: read(/home/vpopmail/domains/italy1.com/xxxxx/Maildir/cur/1154731221.9257.az… failed: Cached message size smaller than expected (26421 < 26511, box=INBOX, UID=208) (read reason=mail stream) May 25 15:01:27 imap(xxxxxx(a)italy1.com)<10256><LsrOdL2J3uisCqP7>: Error: Corrupted record in index cache file /home/vpopmail/domains/italy1.com/xxxxx/Maildir/dovecot.index.cache: UID 208: Broken physical size in mailbox INBOX: read(/home/vpopmail/domains/italy1.com/xxxxx/Maildir/cur/1154731221.9257.az… failed: Cached message size smaller than expected (26421 < 26511, box=INBOX, UID=208) May 25 15:01:27 imap(xxxxxx(a)italy1.com)<10256><LsrOdL2J3uisCqP7>: Panic: file istream.c: line 315 (i_stream_read_memarea): assertion failed: (old_size <= _stream->pos - _stream->skip) Can someone tell help on how to fix this issue. Thanks

3 3

Unknown error message
by Jerry 26 May '19

26 May '19

dovecot 2.3.6 (7eab80676) FreeBSD 12.0-RELEASE-p5 amd64 I have recently been finding error messages similar to the following in my Dovecot log file: May 26 06:58:32 imap(gerard(a)seibercom.net)<87791><WvXT+LyJHBCubeH6>: Error: stat(/var/mail/vmail/seibercom.net/gerard/.dovecot.sieve/tmp) failed: Not a directory The message is correct as there is no such directory. The question is why has it suddenly started appearing? I checked my maillog file, and there are no messages being transmitted to Dovecot when that error message is created. Neither is there any mail with that ID number either. Could this be someone attempting to hack into my system? Thanks! -- Jerry

2 1

Automatically subscribe to the INBOX folder
by glts 26 May '19

26 May '19

Hello, I am using the ‘auto = subscribe’ feature in the mailbox configuration section in the usual fashion (as shown in conf.d/15-mailboxes.conf): namespace inbox { inbox = yes mailbox Drafts { special_use = \Drafts auto = subscribe } ... } When I connect to an account with the Thunderbird mail client, those mailboxes/folders get autocreated and autosubscribed. Good! INBOX, however, does not get subscribed to automatically. When I look at the account’s subscriptions in Thunderbird, all folders are subscribed, except INBOX. How can I enable autosubscribe for the INBOX folder (like the other folders)? Is there an option for this? This is in Dovecot 2.2.22. Cheers, David

2 1

Workaround for infinite loop in XCLIENT command bug
by mabi 26 May '19

26 May '19

Hello, I am running Dovecot 2.3.5 package on OpenBSD 6.5 and it looks like this bug which has been fixed in 2.3.6 is hitting me: lib-smtp: client: Fix infinite loop in XCLIENT command interaction with server https://github.com/dovecot/core/commit/5d03f39b345127b80d145ee90772739baa7a… so I was wondering if there is any workarounds? Maybe like disabling the XCLIENT command from the config file or something similar? My original post regarding this issue is here: https://www.mail-archive.com/misc@opensmtpd.org/msg04362.html I first thought this was an OpenSMTPD issue but it seems to be that Dovecot bug. Cheers, Mabi

3 6

Dovecot multiple passdb and fail2ban
by Joaquin F 26 May '19

26 May '19

Objective: different password for remote and local imap login Version: 2.2.36 (1f10bfa63) on CentOS 7 Users are from Active Directory, mapped to local users via sssd After much experimentation, I have configured this way: doveconf -n passdb userdb passdb { args = username_format=%Ln /etc/dovecot/remote driver = passwd-file skip = authenticated username_filter = user01 user02 } passdb { driver = pam override_fields = allow_nets=127.0.0.0/8,192.168.1.0/24 skip = authenticated } userdb { driver = passwd } If I put the passdb's in the reverse order, I would get failure messages (when logging in remotely) in /var/log/secure, such as: auth: pam_sss(dovecot:auth): authentication failure; logname= uid=0 euid=0 tty=dovecot ruser=user02 rhost=xx.xx.xx.xx user=user02 Which caused fail2ban to ban that ip /etc/fail2ban/jail.local [dovecot] enabled = true port = imap,imaps If I set "auth_verbose = yes", then I can see messages in (when logging in locally) in /var/log/maillog dovecot: auth: passwd-file(user02,192.168.1.20,<Na/7f8WJC8HAqAEU>): Password mismatch which is probably not a big deal... but seems inefficient? Question: is there a more elegant way to use different passdb depending on ip? Thanks in advance.

1 0

Imap reverse / proxy in front of our clients machines.
by Brent Clark 25 May '19

25 May '19

Good day Guys I have a user story have an imap reverse / proxy in front of our clients servers. Im currently using the following sources for information. https://wiki.failover.de/Email/Dovecot/IMAP/Proxy/ https://gist.github.com/rplessl/dd56d05c84f988706418 https://wiki2.dovecot.org/PasswordDatabase/ExtraFields/Proxy In my vagrant instance, dovecot can connect to the the remote server You can see my debugging and conf: https://pastebin.com/raw/H2AL53Fz https://pastebin.com/raw/hZHSHvcu If anyone can assist it would be greatly appreciated. Many thanks Regards Brent

1 0

Race condition in IMAP NOTIFY for events received NOTIFY_DELAY_MSECS apart
by Guilhem Moulin 25 May '19

25 May '19

Hi there, There seem to be a race condition in IMAP NOTIFY: when two events for the SELECTED mailbox are received soon after one another, sometimes only the first one is being reported to clients that enabled IMAP NOTIFY. On closer look it seems like this is most often reproducible when the delay between the two events is NOTIFY_DELAY_MSECS (500ms). This is with 2.3.4.1 from Debian sid. $ sed -r 's/^\s*//; s/\s+/ /g' >/tmp/dovecot.conf <<-EOF log_path = /tmp/dovecot.log mailbox_list_index = yes mail_home = /dev/shm/dovecot-test/%u mail_location = dbox:~/mail ssl = no EOF (`doveconf -c /tmp/dovecot.conf -n` output enclosed.) $ rm -rf /dev/shm/dovecot-test && mkdir -m0700 /dev/shm/dovecot-test $ env -i USER=user HOME=/dev/shm/dovecot-test/user PATH=/usr/bin:/bin \ doveadm -c /tmp/dovecot.conf exec imap S: * PREAUTH [CAPABILITY IMAP4rev1 … NOTIFY] Logged in as user C: a NOTIFY SET STATUS (SELECTED (MessageNew MessageExpunge FlagChange)) (MAILBOXES (INBOX test) (MessageNew MessageExpunge FlagChange)) S: * STATUS INBOX (MESSAGES 0 UIDNEXT 1 UIDVALIDITY 1558785754 UNSEEN 0 HIGHESTMODSEQ 1) S: a OK NOTIFY completed (0.004 + 0.000 + 0.003 secs). S: * STATUS INBOX (MESSAGES 0 UIDNEXT 1 UIDVALIDITY 1558785754 UNSEEN 0 HIGHESTMODSEQ 1) C: b SELECT INBOX […] S: b OK [READ-WRITE] Select completed (0.001 + 0.000 secs). Now deliver two messages to INBOX with ~500ms in between: $ env -i USER=user HOME=/dev/shm/dovecot-test/user PATH=/usr/bin:/bin sh -c \ 'echo -n . | doveadm -c /tmp/dovecot.conf exec dovecot-lda -e -m INBOX; \ sleep 0.500; \ echo -n . | doveadm -c /tmp/dovecot.conf exec dovecot-lda -e -m INBOX' Only the the first message is reported in the above IMAP session: S: * 1 EXISTS S: * 1 RECENT An UNSELECT doesn't trigger the notification, but (of course) a NOOP does: C: c NOOP S: * 2 EXISTS S: * 2 RECENT S: c OK NOOP completed (0.001 + 0.000 secs). Similarly, for two flag changes within 0.5s only the first is recorded: $ env -i USER=user HOME=/dev/shm/dovecot-test/user PATH=/usr/bin:/bin sh -c \ 'doveadm -c /tmp/dovecot.conf flags add "\\Seen" mailbox INBOX 1; \ sleep 0.500; \ doveadm -c /tmp/dovecot.conf flags add "\\Answered" mailbox INBOX 2' yields a single unsolicited FETCH response: S: * 1 FETCH (MODSEQ (4) FLAGS (\Seen \Recent)) AFAICT this is only reproducible in the ‘SELECTED’ mailbox specifier: after creating a mailbox "test", $ env -i USER=user HOME=/dev/shm/dovecot-test/user PATH=/usr/bin:/bin sh -c \ 'echo -n . | doveadm -c /tmp/dovecot.conf exec dovecot-lda -e -m test; \ sleep 0.500; \ echo -n . | doveadm -c /tmp/dovecot.conf exec dovecot-lda -e -m test' yields two unsolicited STATUS responses as expected: * STATUS test (MESSAGES 1 UIDNEXT 2 UIDVALIDITY 1558787038 UNSEEN 1 HIGHESTMODSEQ 2) * STATUS test (MESSAGES 2 UIDNEXT 3 UIDVALIDITY 1558787038 UNSEEN 2 HIGHESTMODSEQ 3) (And same thing for two flag updates in the "test" mailbox.) This is not specific to INBOX as once "test" is selected the same problem arises. AFAICT the race is in ‘src/lib-storage/list/mailbox-list-index-notify.c’ which for some reason doesn't acknowledge ST_CHANGED() after inotify_rm_watch(), but I couldn't get my head around that file. Cheers, -- Guilhem.

1 0

SIGABRT on fetching mail
by Peter Nabbefeld 24 May '19

24 May '19

Hello, I'm running dovecot with getmail for several months already, but today it's always crashing: "getmailrc: operation error (child pid 2995 killed by signal 6)". The deliver process aborts due to an unknown reason. > tail /var/log/dovecot-info.log May 24 12:10:28 imap-login: Info: Login: user=<peter.nabbefeld(a)gmx.de>, method=PLAIN, rip=::1, lip=::1, mpid=2970, secured, session=<n/dfaJ+JuIMAAAAAAAAAAAAAAAAAAAAB> May 24 12:10:49 lda(peter.nabbefeld(a)gmx.de)<2994><kCP3FifD51yyCwAA7IIYzw>: Info: sieve: msgid=<318D121B-37FC-4E8C-B4B8-93C87E0692B8(a)gmx.de>: stored mail into mailbox 'Gesendet' May 24 15:14:30 imap-login: Info: Login: user=<peter.nabbefeld(a)gmx.de>, method=PLAIN, rip=::1, lip=::1, mpid=6304, secured, session=<+Rae+qGJ4IUAAAAAAAAAAAAAAAAAAAAB> May 24 15:14:31 imap(peter.nabbefeld(a)gmx.de)<6304><+Rae+qGJ4IUAAAAAAAAAAAAAAAAAAAAB>: Info: Connection closed (append finished 0.562 secs ago) in=157758 out=520 deleted=0 expunged=0 trashed=0 hdr_count=0 hdr_bytes=0 body_count=0 body_bytes=0 May 24 15:14:37 imap-login: Info: Login: user=<peter.nabbefeld(a)gmx.de>, method=PLAIN, rip=::1, lip=::1, mpid=6307, secured, session=<MjwD+6GJ4oUAAAAAAAAAAAAAAAAAAAAB> May 24 15:55:28 imap-login: Info: Login: user=<peter.nabbefeld(a)gmx.de>, method=PLAIN, rip=::1, lip=::1, mpid=7205, secured, session=<T9ofjaKJgIYAAAAAAAAAAAAAAAAAAAAB> May 24 15:57:00 imap-login: Info: Login: user=<peter.nabbefeld(a)gmx.de>, method=PLAIN, rip=::1, lip=::1, mpid=7254, secured, session=<nT6XkqKJhIYAAAAAAAAAAAAAAAAAAAAB> May 24 16:08:22 imap-login: Info: Login: user=<peter.nabbefeld(a)gmx.de>, method=PLAIN, rip=::1, lip=::1, mpid=7507, secured, session=<LI40u6KJJIcAAAAAAAAAAAAAAAAAAAAB> May 24 16:16:40 imap(peter.nabbefeld(a)gmx.de)<6307><MjwD+6GJ4oUAAAAAAAAAAAAAAAAAAAAB>: Info: Connection closed (IDLE running for 0.001 + waiting input for 0.001 secs, 2 B in + 10 B out, state=wait-input) in=4251 out=137885 deleted=0 expunged=0 trashed=0 hdr_count=1 hdr_bytes=661 body_count=0 body_bytes=0 May 24 16:16:54 imap-login: Info: Login: user=<peter.nabbefeld(a)gmx.de>, method=PLAIN, rip=::1, lip=::1, mpid=7662, secured, session=<zV++2aKJOIcAAAAAAAAAAAAAAAAAAAAB> > tail /var/log/dovecot.log May 24 11:25:33 master: Warning: Killed with signal 15 (by pid=12275 uid=0 code=kill) May 24 11:25:35 log(660): Warning: Killed with signal 15 (by pid=1 uid=0 code=kill) May 24 12:10:47 lda(peter.nabbefeld(a)gmx.de)<2994><kCP3FifD51yyCwAA7IIYzw>: Warning: Failed to parse return-path header May 24 12:10:50 lda(peter.nabbefeld(a)gmx.de)<2995><hco1BirD51yzCwAA7IIYzw>: Panic: file istream-crlf.c: line 24 (i_stream_crlf_read_common): assertion failed: (ret != -2) May 24 12:10:50 lda(peter.nabbefeld(a)gmx.de)<2995><hco1BirD51yzCwAA7IIYzw>: Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0xeee14) [0x7fd668defe14] -> /usr/lib/dovecot/libdovecot.so.0(+0xeee51) [0x7fd668defe51] -> /usr/lib/dovecot/libdovecot.so.0(+0x46268) [0x7fd668d47268] -> /usr/lib/dovecot/libdovecot.so.0(+0x4892e) [0x7fd668d4992e] -> /usr/lib/dovecot/libdovecot.so.0(+0x1004e6) [0x7fd668e014e6] -> /usr/lib/dovecot/libdovecot.so.0(i_stream_read_memarea+0x81) [0x7fd668dfd681] -> /usr/lib/dovecot/libdovecot.so.0(i_stream_read+0x36) [0x7fd668dfd8a6] -> /usr/lib/dovecot/libdovecot.so.0(+0x1058f8) [0x7fd668e068f8] -> /usr/lib/dovecot/libdovecot.so.0(i_stream_read_memarea+0x81) [0x7fd668dfd681] -> /usr/lib/dovecot/libdovecot.so.0(i_stream_read+0x36) [0x7fd668dfd8a6] -> /usr/lib/dovecot/libdovecot.so.0(i_stream_read_data+0x4c) [0x7fd668dfe33c] -> /usr/lib/dovecot/libdovecot.so.0(io_stream_copy+0x8a) [0x7fd668e18aba] -> /usr/lib/dovecot/libdovecot.so.0(+0x119ac2) [0x7fd668e1aac2] -> /usr/lib/dovecot/libdovecot.so.0(o_stream_send_istream+0x4f) [0x7fd668e1874f] -> /usr/lib/dovecot/libdovecot-storage.so.0(index_storage_save_continue+0x2e) [0x7fd668f981ee] -> /usr/lib/dovecot/libdovecot-storage.so.0(maildir_save_continue+0x27) [0x7fd668f36887] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_save_continue+0x44) [0x7fd668f083f4] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_storage_copy+0xf8) [0x7fd668ef9828] -> /usr/lib/dovecot/libdovecot-storage.so.0(maildir_copy+0x59) [0x7fd668f32639] -> /usr/lib/dovecot/libdovecot-lda.so.0(+0x3d5c) [0x7fd66902ad5c] -> /usr/lib/dovecot/modules/lib20_fts_plugin.so(+0x10eec) [0x7fd668a90eec] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0x58981) [0x7fd668f08981] -> /usr/lib/dovecot/libdovecot-sieve.so.0(+0x4e6df) [0x7fd66676e6df] -> /usr/lib/dovecot/libdovecot-sieve.so.0(sieve_result_execute+0x4e5) [0x7fd666764065] -> /usr/lib/dovecot/libdovecot-sieve.so.0(+0x57259) [0x7fd666777259] -> /usr/lib/dovecot/libdovecot-sieve.so.0(sieve_multiscript_run+0xa2) [0x7fd6667783f2] -> /usr/lib/dovecot/modules/lib90_sieve_plugin.so(+0x3d45) [0x7fd668cecd45] -> /usr/lib/dovecot/libdovecot-lda.so.0(mail_deliver+0xf9) [0x7fd66902c229] How can I find out which message is causing the crash? It would be very helpful, if the message's subject and receipt time could be logged in case of an abort or anything else that could help identify the corrupt message. This would also enable me to send You the message for further investigation (if appropriate). Kind regards Peter

1 0

Panic: file mail-index-util.c: line 10 (mail_index_uint32_to_offset): assertion failed: (offset < 0x40000000)
by Ralf Hildebrandt 24 May '19

24 May '19

I'm encountering a crash which this command: % doveadm import -u restore(a)backup.invalid mdbox:/home/copymail2/mdbox '' mailbox INBOX header X-Spam Yes SAVEDBEFORE 2019-05-23 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(+0xd9f9e) [0x7fbc52ba7f9e] -> /usr/lib/dovecot/libdovecot.so.0(+0xd9fe1) [0x7fbc52ba7fe1] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7fbc52b0cc54] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_index_uint32_to_offset+0x78)[0x7fbc52f525e8] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_cache_add+0x83b)[0x7fbc52f3ac2b] -> /usr/lib/dovecot/libdovecot-storage.so.0(index_mail_parse_header+0x449)[0x7fbc52f1c969] -> /usr/lib/dovecot/libdovecot.so.0(+0xb6af9) [0x7fbc52b84af9] -> /usr/lib/dovecot/libdovecot.so.0(i_stream_read_memarea+0x7a) [0x7fbc52bb531a] -> /usr/lib/dovecot/libdovecot.so.0(i_stream_read+0x2f) [0x7fbc52bb565f] -> /usr/lib/dovecot/libdovecot.so.0(i_stream_read_data+0x3d)[0x7fbc52bb604d] -> /usr/lib/dovecot/libdovecot.so.0(message_parse_header_next+0x68)[0x7fbc52b8b3f8] -> /usr/lib/dovecot/libdovecot.so.0(message_parse_header+0x52)[0x7fbc52b8bdd2] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xcadae) [0x7fbc52f26dae] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xcc0ac) [0x7fbc52f280ac] -> /usr/lib/dovecot/libdovecot-storage.so.0(index_storage_search_next_nonblock+0x11d)[0x7fbc52f288bd] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_search_next_nonblock+0x28)[0x7fbc52ea92e8] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_search_next+0x3d)[0x7fbc52ea934d] -> doveadm(+0x31443) [0x5635b4760443] -> doveadm(+0x2bdb1) [0x5635b475adb1] -> doveadm(+0x2caf9) [0x5635b475baf9] -> doveadm(doveadm_cmd_ver2_to_mail_cmd_wrapper+0x20e) [0x5635b475c9ce] -> doveadm(doveadm_cmd_run_ver2+0x55e) [0x5635b476db7e] -> doveadm(doveadm_cmd_try_run_ver2+0x37) [0x5635b476dbd7] -> doveadm(main+0x1d1) [0x5635b474aec1] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7) [0x7fbc5210fb97] -> doveadm(_start+0x2a) [0x5635b474b39a] Version info: ii dovecot-core 2:2.3.6-2~bionic amd64 secure POP3/IMAP server - core files ii dovecot-dbg 2:2.3.6-2~bionic amd64 secure POP3/IMAP server - debug symbols ii dovecot-imapd 2:2.3.6-2~bionic amd64 secure POP3/IMAP server - IMAP daemon ii dovecot-lmtpd 2:2.3.6-2~bionic amd64 secure POP3/IMAP server - LMTP server Backtrace: Program received signal SIGABRT, Aborted. __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 51../sysdeps/unix/sysv/linux/raise.c: No such file or directory. (gdb) bt #0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 #1 0x00007ffff68fa801 in __GI_abort () at abort.c:79 #2 0x00007ffff7373f51 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 0x00007ffff7373fe1 in default_fatal_handler (ctx=<optimized out>, format=<optimized out>, args=<optimized out>) at failures.c:479 #5 0x00007ffff72d8c54 in i_panic (format=format@entry=0x7ffff772e440 "file %s: line %d (%s): assertion failed: (%s)") at failures.c:523 #6 0x00007ffff771e5e8 in mail_index_uint32_to_offset (offset=<optimized out>) at mail-index-util.c:10 #7 0x00007ffff7706c2b in mail_cache_header_fields_write (ctx=0x55555583d960, buffer=<optimized out>, buffer=<optimized out>) at mail-cache-transaction.c:609 #8 mail_cache_header_add_field (field_idx=15, ctx=0x55555583d960) at mail-cache-transaction.c:690 #9 mail_cache_add (ctx=0x55555583d960, seq=1, field_idx=field_idx@entry=15, data=0x7ffff773ba56, data_size=0) at mail-cache-transaction.c:739 #10 0x00007ffff76eafdc in index_mail_cache_add_idx (mail=mail@entry=0x55555583e2f8, field_idx=field_idx@entry=15, data=data@entry=0x7ffff773ba56, data_size=data_size@entry=0) at index-mail.c:621 #11 0x00007ffff76e8969 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:312 #13 0x00007ffff7350af9 in read_header (mstream=0x55555584b7f0) at istream-header-filter.c:357 #14 i_stream_header_filter_read (stream=0x55555584b7f0) at istream-header-filter.c:447 #15 0x00007ffff738131a in i_stream_read_memarea (stream=stream@entry=0x55555584b870) at istream.c:313 #16 0x00007ffff738165f in i_stream_read (stream=stream@entry=0x55555584b870) at istream.c:271 #17 0x00007ffff738204d in i_stream_read_data (stream=0x55555584b870, data_r=data_r@entry=0x7fffffffdbe8, size_r=size_r@entry=0x7fffffffdbf0, threshold=threshold@entry=1) at istream.c:745 #18 0x00007ffff73573f8 in i_stream_read_bytes (wanted=2, size_r=0x7fffffffdbf0, data_r=0x7fffffffdbe8, stream=<optimized out>) at ../../src/lib/istream.h:217 #19 message_parse_header_next (ctx=0x55555584ca70, hdr_r=hdr_r@entry=0x7fffffffdc50) at message-header-parser.c:85 #20 0x00007ffff7357dd2 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=0x7ffff76f2310 <search_header>, context=context@entry=0x7fffffffdcc0) at message-header-parser.c:392 #21 0x00007ffff76f2dae in search_arg_match_text (ctx=0x55555583dd20, args=0x555555809690) at index-search.c:760 #22 search_match_once (ctx=0x55555583dd20) at index-search.c:1400 #23 0x00007ffff76f40ac in search_match_next (ctx=0x55555583dd20) at index-search.c:1507 #24 search_more_with_mail (mail=<optimized out>, ctx=0x55555583dd20) at index-search.c:1624 #25 search_more_with_prefetching (mail_r=<optimized out>, ctx=<optimized out>) at index-search.c:1706 #26 search_more (ctx=ctx@entry=0x55555583dd20, mail_r=mail_r@entry=0x7fffffffddf0) at index-search.c:1780 #27 0x00007ffff76f48bd in index_storage_search_next_nonblock(_ctx=0x55555583dd20, mail_r=0x7fffffffdec0, tryagain_r=0x7fffffffde57) at index-search.c:1808 #28 0x00007ffff76752e8 in mailbox_search_next_nonblock (ctx=0x55555583dd20, mail_r=0x7fffffffdec0, tryagain_r=<optimized out>) at mail-storage.c:2141 #29 0x00007ffff767534d in mailbox_search_next (ctx=0x55555583dd20, mail_r=mail_r@entry=0x7fffffffdec0) at mail-storage.c:2126 #30 0x0000555555586682 in doveadm_mail_iter_next (iter=<optimized out>, mail_r=mail_r@entry=0x7fffffffdec0) at doveadm-mail-iter.c:160 #31 0x0000555555585443 in cmd_import_box (search_args=<optimized out>, info=0x555555832118, dest_user=<optimized out>, ctx=0x555555807d78) at doveadm-mail-import.c:142 #32 cmd_import_run (_ctx=0x555555807d78, user=0x55555581c688) at doveadm-mail-import.c:202 #33 0x000055555557fdb1 in doveadm_mail_next_user (ctx=ctx@entry=0x555555807d78, error_r=error_r@entry=0x7fffffffe0a0) at doveadm-mail.c:462 #34 0x0000555555580a0b in doveadm_mail_single_user (ctx=ctx@entry=0x555555807d78, error_r=error_r@entry=0x7fffffffe0a0) at doveadm-mail.c:492 #35 0x0000555555580af9 in doveadm_mail_cmd_exec (ctx=ctx@entry=0x555555807d78, wildcard_user=wildcard_user@entry=0x0) at doveadm-mail.c:653 #36 0x00005555555819ce in doveadm_cmd_ver2_to_mail_cmd_wrapper (cctx=<optimized out>) at doveadm-mail.c:1144 #37 0x0000555555592b7e in doveadm_cmd_run_ver2 (argc=12, argv=0x5555557f5ae8, cctx=cctx@entry=0x7fffffffe290) at doveadm-cmd.c:574 #38 0x0000555555592bd7 in doveadm_cmd_try_run_ver2 (cmd_name=<optimized out>, argc=<optimized out>, argv=<optimized out>, cctx=0x7fffffffe290) at doveadm-cmd.c:496 #39 0x000055555556fec1 in main (argc=<optimized out>, argv=<optimized out>) at doveadm.c:391 -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebrandt(a)charite.de | https://www.charite.de

2 2

MailCrypt plugin questions
by MRob 24 May '19

24 May '19

I read the mailcrypt plugin document on the wiki and had couple questions. 1. If I want per-user encryption am I correct I should configure global keys with all related settings override in the userdb lookup? 2. If I do not want to encrypt some user accounts, is it enough to omit the mail_crypt_global_private_key from the userdb lookup? In other word, mail_plugins still active with mail_crypt, will that cause user account to be encrypted unexpectedly if no private key is given? 3. Example command to create EC key does not ask for password, openssl ecparam command does not seem to have password arg. If I want password-protection should I use RSA key which the doc tell to be discouraged?

1 1