- dovecot - dovecot.org

recipient bcc and dovecot
by ＠lbutlr 13 Mar '19

13 Mar '19

I have a recipient_bcc_maps which contains a bcc map that is updated everyday: rbcc.pcre: if !/backup.*@/ /^([^+_]*).*(a)([^.]*)/ backup+071.${1}-${2}(a)adomain.tld endif the 071 portion is changed each day to the current day of the year. Everything works, but I get an error from dovecot on every message: lda(backup(a)adomain.tld): Error: User initialization failed: Namespace '': Ambiguous mail location setting, don't know what to do with it: /usr/local/virtual/backup(a)adomain.tld (try prefixing it with mbox: or maildir:) The mail is delivered two the right directory anyway, but after a temporary failure. I'd like to eliminate the error. the backup user is not a 'real' user (it is not in the lookup map) so should I bypass dovecot entirely in delivering these messages? (and if so, how) If not, where/how would I add the prefix maildir: Is there something I can add to dovecot to specifically deal with messages coming in to backup(a)adomain.tld and add the maildir: specification there? (Still on dovecot 2.2.35) -- And sometimes there's a short cut. A door or a gate. Some standing stones. A tree cleft by lightning, a filing cabinet. Maybe just a spot on some moorland somewhere... A place where THERE is very nearly HERE... If some people knew where such a spot was, if they had experience of what happens when here and there become entangled, then they might - if they knew how - mark such a spot with certain stones. In the hope that enough daft buggers would take it as a warning and keep away. (Lords and Ladies)

2 3

sieve vacation to an alias group
by Monis Monther 13 Mar '19

13 Mar '19

Hi, We have an alias group named xyz(a)example.com, this alias group has 3 actual users a(a)example.com, b(a)example.com and c(a)example.com We set vacation rule on the generic sieve rule, the problem is that 3 responses are sent to the original sender. (obviously because the rule is being executed with each user in the alias group) Is it possible to set auto response only once, we tried the ( :days 1) option but still all 3 respond back. How can such a setup be achieved. (Single auto response to an alias group) CentOS 7.5 dovecot-pigeonhole-2.3.4.1-1.x86_64 dovecot-2.3.4.1-1.x86_64 postfix 2.10-1 -- Best Regards Monis

4 14

Delayed flags changes over IDLE
by Kostya Vasilyev 13 Mar '19

13 Mar '19

Hello, I'm experiencing slow flags changes over IMAP IDLE: - If I start an IDLE session / command - Change the flags of some messages via another email app - Dovecot can take a minute or more to notify the IDLE connection about flags changes If I use another email app to add or remove a message, Dovecot sends that (EXISTS / EXPUNGE) instantly and also flushes the (so far delayed) flags changes. So it does "know" already. The system is Debian Testing, 64 bit, file system is ext4. Dovecot is 2.3.4.1 (f79e8e7e4) - I believe from Debian repos (I had Dovecot's own repo added at some point, disabled now). My mail is stored under ~/mail/.imap (not sure what this format is called), I mean not "single file mbox". I have not changed any IDLE related config settings: doveconf | grep -i idle default_idle_kill = 1 mins director_ping_idle_timeout = 30 secs imap_idle_notify_interval = 2 mins imapc_max_idle_time = 29 mins mailbox_idle_check_interval = 30 secs What can I do to make Dovecot notify IDLE clients about flags changes - more quickly? Preferably near-instant? -- Kostya Vasilyev kman(a)fastmail.com

3 9

“doveadm mailbox” command fails with UTF-8 mailboxes
by Felipe Gasper 13 Mar '19

13 Mar '19

Hello, I’ve got a strange misconfiguration where the following command: doveadm -f pager mailbox status -u spamutf8 'messages vsize guid' INBOX 'INBOX.*' … fails with error code 68, saying that it can’t find one of the mailboxes. (It lists the user’s other mailboxes.) The name of the mailbox in question is saved to disk in UTF-8 rather than mUTF-7, but strace shows that doveadm is stat()ing the mUTF-7 path; the failure of that stat() is, assumedly, what causes doveadm to report the error status. I’ve tried to paw through the source code to see what might be causing this but haven’t made much headway. Can someone here point out where the misconfiguration might be that is causing doveadm to stat() the mUTF-7 path rather than UTF-8? Or perhaps offer any tips as to how I might diagnose what’s going on? What causes doveadm to stat() one path or the other? Thank you! -Felipe Gasper Mississauga, ON

5 9

Inbox quota usage doubled when mailbox_list_index enabled, under some circumstances
by Chris Dillon 13 Mar '19

13 Mar '19

Hello, I searched through the list archives for anything that appeared to be similar to this but I didn't find any good matches. I apologize if this has been brought up before. Beginning with Dovecot 2.2.34, reported quota usage of a user's inbox can be doubled when the following criteria are met: 1) quota plugin is enabled 2) mailbox_list_index=yes 3) A sub-folder of the inbox exists whose name also matches the prefix (for example, "INBOX.Test"), even if that folder has no contents. (Apparently, some mail clients such as K-9 Mail on Android can create these folders automatically) Downgrading to 2.2.33.2 allows this configuration to work normally. I looked through the changes in git between 2.2.33.2 and 2.2.34 and they appeared extensive, so unfortunately I wasn't able to pinpoint a specific change that caused this. Reproduced on a CentOS 7 server with Dovecot 2.2.34 built from git sources according to https://wiki2.dovecot.org/CompilingSource#Compiling_Dovecot_From_Git using the following minimal configuration: ========== root@centos7 [~]# dovecot -n # 2.2.34 (874deae): /usr/local/etc/dovecot/dovecot.conf # OS: Linux 3.10.0-862.9.1.el7.x86_64 x86_64 CentOS Linux release 7.5.1804 (Core) # Hostname: centos7.local mail_location = maildir:~/Maildir mail_plugins = quota mailbox_list_index = yes namespace inbox { inbox = yes location = prefix = INBOX. separator = . } passdb { driver = pam } plugin { quota = maildir:Mailbox } userdb { driver = passwd } ========== With the system user "myuser" and a minimal Maildir setup containing 1 email in the inbox, and one sub-folder named "INBOX.Test": ========== root@centos7 [~]# ls -lAR /home/myuser/Maildir /home/myuser/Maildir: total 4 drwxr-xr-x. 2 myuser myuser 77 Jul 25 09:36 cur drwxr-xr-x. 5 myuser myuser 56 Jul 25 15:19 .INBOX.Test -rw-r--r--. 1 myuser myuser 14 Jul 25 15:19 maildirsize drwxr-xr-x. 2 myuser myuser 6 Jul 25 09:36 new drwxr-xr-x. 2 myuser myuser 6 Jul 25 09:36 tmp /home/myuser/Maildir/cur: total 12416 -rw-r--r--. 1 myuser myuser 12712627 Jul 25 09:07 1532529376.M543965P58007.centos7.local,S=12712627,W=12877782:2,S /home/myuser/Maildir/.INBOX.Test: total 0 drwxr-xr-x. 2 myuser myuser 6 Jul 25 09:36 cur -rw-r--r--. 1 myuser myuser 0 Jul 25 09:36 maildirfolder drwxr-xr-x. 2 myuser myuser 6 Jul 25 09:36 new drwxr-xr-x. 2 myuser myuser 6 Jul 25 09:36 tmp /home/myuser/Maildir/.INBOX.Test/cur: total 0 /home/myuser/Maildir/.INBOX.Test/new: total 0 /home/myuser/Maildir/.INBOX.Test/tmp: total 0 /home/myuser/Maildir/new: total 0 /home/myuser/Maildir/tmp: total 0 ========== Given this configuration, when "mailbox_list_index" is enabled, after quota recalculation, quota reports that there are 2 messages and that double the amount of storage is used: ========== root@centos7 [~]# doveadm quota recalc -u myuser; doveadm quota get -u myuser Quota name Type Value Limit % Mailbox STORAGE 24830 - 0 Mailbox MESSAGE 2 - 0 ========== When "mailbox_list_index" is disabled and quota is recalculated, it will report the message and storage counts correctly: ========== root@centos7 [~]# doveadm -o 'mailbox_list_index=no' quota recalc -u myuser; doveadm quota get -u myuser Quota name Type Value Limit % Mailbox STORAGE 12415 - 0 Mailbox MESSAGE 1 - 0 ========== I am hoping that someone with much more familiarity with the code path involved here could take a look at this issue and possibly submit a fix for it -- that would be greatly appreciated. Please let me know if you need any more details regarding the replication steps, though I hope that I didn't miss anything. Thank you! -- Chris Dillon Technical Analyst III Migrations Specialist cPanel, Inc.

2 3

Dovecot 2.3.4 crash
by azurit＠pobox.sk 13 Mar '19

13 Mar '19

Hi, is this a know problem? Newest Dovecot 2.3.4 package from repo.dovecot.org , Debian Stretch (fully upgraded). Nov 29 14:25:11 server00 dovecot: lmtp(16854): Panic: file ostream-dot.c: line 208 (o_stream_dot_sendv): assertion failed: ((size_t)ret == sent + added) Nov 29 14:25:11 server00 dovecot: lmtp(16854): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0xd25e1) [0x7fa5f7b655e1] -> /usr/lib/dovecot/libdovecot.so.0(+0xd2681) [0x7 fa5f7b65681] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7fa5f7acd093] -> /usr/lib/dovecot/libdovecot.so.0(+0xbb97b) [0x7fa5f7b4e97b] -> /usr/lib/dovecot/libdovecot.so.0(+0x fa4ae) [0x7fa5f7b8d4ae] -> /usr/lib/dovecot/libdovecot.so.0(o_stream_sendv+0x2e) [0x7fa5f7b8da3e] -> /usr/lib/dovecot/libdovecot.so.0(io_stream_copy+0x52) [0x7fa5f7b8e512] -> /usr /lib/dovecot/libdovecot.so.0(o_stream_send_istream+0x58) [0x7fa5f7b8e008] -> /usr/lib/dovecot/libdovecot.so.0(smtp_client_command_send_more+0x1b1) [0x7fa5f7ad7351] -> /usr/lib/dov ecot/libdovecot.so.0(+0x4a096) [0x7fa5f7add096] -> /usr/lib/dovecot/libdovecot.so.0(+0xfd0c3) [0x7fa5f7b900c3] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x75) [0x7fa5f7b 7e5d5] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x109) [0x7fa5f7b7ffd9] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x56) [0x7fa5f7b7e6e6] -> / usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7fa5f7b7e8f8] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7fa5f7af2d43] -> dovecot/lmtp [local DATA](main+ 0x240) [0x565287c30f70] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1) [0x7fa5f77142e1] -> dovecot/lmtp [local DATA](_start+0x2a) [0x565287c310ca] Nov 29 14:25:11 server00 dovecot: lmtp(16854): Fatal: master: service(lmtp): child 16854 killed with signal 6 (core dumps disabled - https://dovecot.org/bugreport.html#coredumps) azur

3 5

Crash in director for secure lmtp proxy connections
by Marcus Fenner 13 Mar '19

13 Mar '19

Hi, After updating some of our director servers from 2.2.36 to 2.3.3 (dcead646b) we experience crashes in about 1/5000 mails in lmtp delivery: Nov 13 12:23:36 Fatal: lmtp(113620): master: service(lmtp): child 113620 killed with signal 6 (core dumped) Nov 13 12:23:36 Panic: lmtp(113623): file ostream-dot.c: line 208 (o_stream_dot_sendv): assertion failed: ((size_t)ret == sent + added) Nov 13 12:23:36 Error: lmtp(113623): Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(+0xe34fb) [0x7f31d89134fb] -> /usr/lib64/dovecot/libdovecot.so.0(+0xe3597) [0x7f31d8913597] -> /usr/lib64/dovecot/libdovecot.so.0(+0x51207) [0x7f31d8881207] -> /usr/lib64/dovecot/libdovecot.so.0(+0x4eeef) [0x7f31d887eeef] -> /usr/lib64/dovecot/libdovecot.so.0(+0x107cf8) [0x7f31d8937cf8] -> /usr/lib64/dovecot/libdovecot.so.0(o_stream_sendv+0x32) [0x7f31d89382c2] -> /usr/lib64/dovecot/libdovecot.so.0(io_stream_copy+0x5a) [0x7f31d8938b6a] -> /usr/lib64/dovecot/libdovecot.so.0(o_stream_send_istream+0x53) [0x7f31d8938873] -> /usr/lib64/dovecot/libdovecot.so.0(smtp_client_command_send_more+0x145) [0x7f31d8890805] -> /usr/lib64/dovecot/libdovecot.so.0(+0x660dd) [0x7f31d88960dd] -> /usr/lib64/dovecot/libssl_iostream_openssl.so(+0xa7e1) [0x7f31d864a7e1] -> /usr/lib64/dovecot/libdovecot.so.0(+0x10a558) [0x7f31d893a558] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_call_io+0x73) [0x7f31d892a203] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x136) [0x7f31d892b8b6] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run+0x50) [0x7f31d892a2b0] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_run+0x48) [0x7f31d892a418] -> /usr/lib64/dovecot/libdovecot.so.0(master_service_run+0x17) [0x7f31d88a95a7] -> dovecot/lmtp(main+0x245) [0x555b8b59cea5] -> /lib64/libc.so.6(__libc_start_main+0xf3) [0x7f31d867c413] -> dovecot/lmtp(_start+0x2e) [0x555b8b59cfbe] Nov 13 12:23:36 Fatal: lmtp(113623): master: service(lmtp): child 113623 killed with signal 6 (core dumped) On the backend servers the only message is lmtp(9571): Disconnect from 192.168.1.56: Connection closed (in DATA) This happens for every server with this version every time postfix tries to resend the mail. After removing "starttls=y" from the static passdb entry, the mail is sent successfully. Starting with version 2.3.2 the lmtp proxy uses starttls as well, therefore the error seems to be there. I've not been able to figure out, if this has to do with the content of the mails, because they are from many different sources. Thanks! Marcus

3 2

lmtp 2.3.2.1 segfault with backtrace
by Tom Sommer 13 Mar '19

13 Mar '19

lmtp on Director crash with 2.3.2.1 # gdb /usr/libexec/dovecot/lmtp /var/core/60174 GNU gdb (GDB) Red Hat Enterprise Linux (7.2-92.el6) Copyright (C) 2010 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-redhat-linux-gnu". For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>... Reading symbols from /usr/libexec/dovecot/lmtp...Reading symbols from /usr/lib/debug/usr/libexec/dovecot/lmtp.debug...done. done. [New Thread 60174] Reading symbols from /usr/lib64/dovecot/libdovecot-lda.so.0...Reading symbols from /usr/lib/debug/usr/lib64/dovecot/libdovecot-lda.so.0.0.0.debug...done. done. Loaded symbols for /usr/lib64/dovecot/libdovecot-lda.so.0 Reading symbols from /usr/lib64/dovecot/libdovecot-storage.so.0...Reading symbols from /usr/lib/debug/usr/lib64/dovecot/libdovecot-storage.so.0.0.0.debug...done. done. Loaded symbols for /usr/lib64/dovecot/libdovecot-storage.so.0 Reading symbols from /usr/lib64/dovecot/libdovecot.so.0...Reading symbols from /usr/lib/debug/usr/lib64/dovecot/libdovecot.so.0.0.0.debug...done. done. Loaded symbols for /usr/lib64/dovecot/libdovecot.so.0 Reading symbols from /lib64/libc.so.6...(no debugging symbols found)...done. Loaded symbols for /lib64/libc.so.6 Reading symbols from /lib64/librt.so.1...(no debugging symbols found)...done. Loaded symbols for /lib64/librt.so.1 Reading symbols from /lib64/libdl.so.2...(no debugging symbols found)...done. Loaded symbols for /lib64/libdl.so.2 Reading symbols from /lib64/ld-linux-x86-64.so.2...(no debugging symbols found)...done. Loaded symbols for /lib64/ld-linux-x86-64.so.2 Reading symbols from /lib64/libpthread.so.0...(no debugging symbols found)...done. [Thread debugging using libthread_db enabled] Loaded symbols for /lib64/libpthread.so.0 Reading symbols from /usr/lib64/dovecot/libssl_iostream_openssl.so...Reading symbols from /usr/lib/debug/usr/lib64/dovecot/libssl_iostream_openssl.so.debug...done. done. Loaded symbols for /usr/lib64/dovecot/libssl_iostream_openssl.so Reading symbols from /usr/lib64/libssl.so.10...(no debugging symbols found)...done. Loaded symbols for /usr/lib64/libssl.so.10 Reading symbols from /usr/lib64/libcrypto.so.10...(no debugging symbols found)...done. Loaded symbols for /usr/lib64/libcrypto.so.10 Reading symbols from /lib64/libgssapi_krb5.so.2...(no debugging symbols found)...done. Loaded symbols for /lib64/libgssapi_krb5.so.2 Reading symbols from /lib64/libkrb5.so.3...(no debugging symbols found)...done. Loaded symbols for /lib64/libkrb5.so.3 Reading symbols from /lib64/libcom_err.so.2...(no debugging symbols found)...done. Loaded symbols for /lib64/libcom_err.so.2 Reading symbols from /lib64/libk5crypto.so.3...(no debugging symbols found)...done. Loaded symbols for /lib64/libk5crypto.so.3 Reading symbols from /lib64/libz.so.1...(no debugging symbols found)...done. Loaded symbols for /lib64/libz.so.1 Reading symbols from /lib64/libkrb5support.so.0...(no debugging symbols found)...done. Loaded symbols for /lib64/libkrb5support.so.0 Reading symbols from /lib64/libkeyutils.so.1...(no debugging symbols found)...done. Loaded symbols for /lib64/libkeyutils.so.1 Reading symbols from /lib64/libresolv.so.2...(no debugging symbols found)...done. Loaded symbols for /lib64/libresolv.so.2 Reading symbols from /lib64/libselinux.so.1...(no debugging symbols found)...done. Loaded symbols for /lib64/libselinux.so.1 Core was generated by `dovecot/lmtp'. Program terminated with signal 11, Segmentation fault. #0 smtp_client_command_set_replies (cmd=0x0, replies=1) at smtp-client-command.c:401 401 i_assert(cmd->replies_expected == 1 || Missing separate debuginfos, use: debuginfo-install glibc-2.12-1.212.el6.x86_64 keyutils-libs-1.4-5.el6.x86_64 krb5-libs-1.10.3-65.el6.x86_64 libcom_err-1.41.12-24.el6.x86_64 libselinux-2.0.94-7.el6.x86_64 openssl-1.0.1e-57.el6.x86_64 zlib-1.2.3-29.el6.x86_64 (gdb) bt full #0 smtp_client_command_set_replies (cmd=0x0, replies=1) at smtp-client-command.c:401 __func__ = "smtp_client_command_set_replies" #1 0x00007f5d14f40f3f in smtp_client_transaction_data_cb (reply=0x7ffe5cd19650, trans=0x7f5d176ae2b8) at smtp-client-transaction.c:658 conn = 0x7f5d176ade80 rcpt = 0x7f5d176ae560 i = <value optimized out> count = 1 #2 0x00007f5d14f3e941 in smtp_client_command_fail_reply (_cmd=<value optimized out>, reply=0x7ffe5cd19650) at smtp-client-command.c:299 cmd = 0x7f5d17600d18 tmp_cmd = <value optimized out> conn = 0x7f5d176ade80 state = <value optimized out> callback = 0x7f5d14f40e80 <smtp_client_transaction_data_cb> #3 0x00007f5d14f4113f in smtp_client_transaction_fail_reply (trans=0x7f5d176ae2b8, reply=0x7ffe5cd19650) at smtp-client-transaction.c:365 conn = 0x7f5d176ade80 rcpts = <value optimized out> i = <value optimized out> count = <value optimized out> __func__ = "smtp_client_transaction_fail_reply" #4 0x00007f5d14f41442 in smtp_client_transaction_timeout (trans=0x7f5d176ae2b8) at smtp-client-transaction.c:419 reply = {status = 451, enhanced_code = {x = 4, y = 4, z = 0}, text_lines = 0x7f5d1759c090} #5 0x00007f5d14fdbe7b in io_loop_handle_timeouts_real (ioloop=0x7f5d175a4c80) at ioloop.c:641 timeout = 0x7f5d176299d0 tv = {tv_sec = 0, tv_usec = 0} tv_call = {tv_sec = 1534202969, tv_usec = 770866} t_id = 3 item = 0x7f5d176299d0 #6 io_loop_handle_timeouts (ioloop=0x7f5d175a4c80) at ioloop.c:655 _data_stack_cur_id = 2 #7 0x00007f5d14fdd667 in io_loop_handler_run_internal (ioloop=0x7f5d175a4c80) at ioloop-epoll.c:195 ctx = 0x7f5d175af300 events = <value optimized out> event = <value optimized out> list = <value optimized out> io = <value optimized out> tv = {tv_sec = 34, tv_usec = 105308} events_count = <value optimized out> msecs = <value optimized out> ret = 0 i = <value optimized out> call = <value optimized out> __func__ = "io_loop_handler_run_internal" #8 0x00007f5d14fdb7c5 in io_loop_handler_run (ioloop=0x7f5d175a4c80) at ioloop.c:726 __func__ = "io_loop_handler_run" #9 0x00007f5d14fdb9e8 in io_loop_run (ioloop=0x7f5d175a4c80) at ioloop.c:699 __func__ = "io_loop_run" #10 0x00007f5d14f58963 in master_service_run (service=0x7f5d175a4b10, callback=<value optimized out>) at master-service.c:767 No locals. #11 0x00007f5d159eb584 in main (argc=1, argv=0x7f5d175a48a0) at main.c:158 set_roots = {0x7f5d15262e20, 0x7f5d157c2040, 0x7f5d15bf1540, 0x0} service_flags = <value optimized out> storage_service_flags = <value optimized out> tmp_base_dir = 0x7f5d1759c040 "erver not answering (transaction timed out while waiting for reply to DATA)" c = <value optimized out> error = <value optimized out> -- Tom

3 3

2.3.3: Panic: file ostream-zlib.c: line 37 (o_stream_zlib_close): assertion failed
by Tom Sommer 13 Mar '19

13 Mar '19

I see this in my logs after 2.3.3: using zlib plugin, ofc. Oct 02 10:01:39 imap(user(a)example.com)<50643></2k4Sjp3vMqC496W>: Panic: file ostream-zlib.c: line 37 (o_stream_zlib_close): assertion failed: (zstream->ostream.finished || zstream->ostream.ostream.stream_errno != 0 || zstream->ostream.error_handling_disabled) Oct 02 10:01:39 imap(user(a)example.com)<50643></2k4Sjp3vMqC496W>: Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(+0xce56a) [0x7f442487556a] -> /usr/lib64/dovecot/libdovecot.so.0(+0xce5b1) [0x7f44248755b1] -> /usr/lib64/dovecot/libdovecot.so.0(+0x3d941) [0x7f44247e4941] -> /usr/lib64/dovecot/lib20_zlib_plugin.so(+0x5cdf) [0x7f44233c4cdf] -> /usr/lib64/dovecot/libdovecot.so.0(+0xf4b46) [0x7f442489bb46] -> /usr/lib64/dovecot/libdovecot.so.0(o_stream_destroy+0x13) [0x7f442489be83] -> /usr/lib64/dovecot/libdovecot-storage.so.0(maildir_save_finish+0x173) [0x7f4424b93973] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mailbox_save_cancel+0x36) [0x7f4424b68696] -> dovecot/imap [user(a)example.com X.X.X.X APPEND](+0xede9) [0x55a9d7e86de9] -> dovecot/imap [user(a)example.com X.X.X.X APPEND](command_exec+0x65) [0x55a9d7e956e5] -> dovecot/imap [user(a)example.com X.X.X.X APPEND](+0xf9e6) [0x55a9d7e879e6] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_call_io+0x55) [0x7f442488c275] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0xbf) [0x7f442488e13f] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run+0x55) [0x7f442488c365] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7f442488c588] -> /usr/lib64/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f4424808053] -> dovecot/imap [user(a)example.com X.X.X.X APPEND](main+0x32d) [0x55a9d7ea20dd] -> /lib64/libc.so.6(__libc_start_main+0x100) [0x7f4424431d20] -> dovecot/imap [user(a)example.com X.X.X.X APPEND](+0xe419) [0x55a9d7e86419] No clue how to reproduce -- Tom

3 2

submission-login: Fatal: master: service(submission-login):
by Marcelo Coelho 13 Mar '19

13 Mar '19

Hi everyone! I’m using dovecot 2.3.5. submission-login is crashing many times in a day: Here is a sample error message: dovecot: submission-login: Fatal: master: service(submission-login): child 34247 killed with signal 11 (core not dumped - https://dovecot.org/bugreport.html#coredumps - set service submission-login { drop_priv_before_exec=yes }) After I added drop_priv_before_exec, I got these error messages: submission-login: Error: master-service: cannot get filters: net_connect_unix(/var/run/dovecot/config) failed: Permission denied dovecot: master: Error: service(submission-login): command startup failed, throttling for 2 secs How to get submission core dumps properly? Thank you. — Marcelo Coelho

3 2

imap-hibernate not working
by Marcelo Coelho 13 Mar '19

13 Mar '19

Hi, I follow different setup instructions and I can't make imap-hibernate work. I've tried vmail and dovecot as users, tried to set mode to 0666, without success. I'm using FreeBSD 11.2. Is imap-hibernate compatible with FreeBSD 11.2? My operational system: # uname -v FreeBSD 11.2-RELEASE-p9 #0: Tue Feb 5 15:30:36 UTC 2019 root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC Here are my logs: Mar 8 15:30:57 servername dovecot: imap(user@domain.com:52.125.128.90): Error: kevent(-1) for notify remove failed: Bad file descriptor Mar 8 15:30:57 servername dovecot: imap(user@domain.com:52.125.128.90): Error: close(-1) for notify remove failed: Bad file descriptor Mar 8 15:30:57 servername dovecot: imap-hibernate: Error: Failed to parse client input: Invalid peer_dev_minor value: 18446744073709486335 Mar 8 15:30:57 servername dovecot: imap(user@domain.com:52.125.128.90): Error: /opt/dovecot/2.3.5/var/run/dovecot/imap-hibernate returned failure: Failed to parse client input: Invalid peer_dev_minor value: 18446744073709486335 Mar 8 15:30:57 servername dovecot: imap: Error: Here are my processes: # ps aux | grep imap dovenull 68264 0.0 0.0 12012 8292 - S 10:15 0:00.06 imap-login: (imap-login) dovenull 68274 0.0 0.0 12012 8272 - S 10:15 0:00.06 imap-login: (imap-login) dovenull 68275 0.0 0.0 12012 8356 - S 10:15 0:00.11 imap-login: (imap-login) dovenull 68276 0.0 0.0 12012 8468 - S 10:15 0:00.16 imap-login: (imap-login) dovenull 68277 0.0 0.0 12012 8328 - S 10:15 0:00.09 imap-login: (imap-login) dovenull 68278 0.0 0.0 12012 8368 - S 10:15 0:00.11 imap-login: (imap-login) dovenull 68279 0.0 0.0 12012 8272 - S 10:15 0:00.05 imap-login: (imap-login) dovenull 68280 0.0 0.0 12012 8288 - S 10:15 0:00.06 imap-login: (imap-login) dovenull 68281 0.0 0.0 12012 8316 - S 10:15 0:00.08 imap-login: (imap-login) dovenull 68282 0.0 0.0 12012 8312 - S 10:15 0:00.10 imap-login: (imap-login) dovenull 68283 0.0 0.0 12012 8356 - S 10:15 0:00.14 imap-login: (imap-login) dovenull 68286 0.0 0.0 12012 8312 - S 10:15 0:00.08 imap-login: (imap-login) dovenull 68287 0.0 0.0 14060 9024 - S 10:15 0:01.31 imap-login: [0 pre-login + 2 TLS proxies] (imap-login) dovenull 68288 0.0 0.0 12012 8392 - S 10:15 0:00.24 imap-login: [11.11.11.11 TLS proxy] (imap-login) dovenull 68289 0.0 0.0 14060 9116 - S 10:15 0:01.75 imap-login: [11.11.11.11 TLS proxy] (imap-login) dovenull 68290 0.0 0.0 14060 9208 - S 10:15 0:01.84 imap-login: [0 pre-login + 4 TLS proxies] (imap-login) nobody 68475 0.0 0.0 14404 6020 - I 10:19 0:00.08 /usr/local/sbin/in.imapproxyd -f /usr/local/etc/imapproxyd.conf vmail 76108 0.0 0.0 21612 17700 - S 14:30 0:00.12 imap: [user(a)domain.com 11.11.11.11 IDLE] (imap) vmail 76332 0.0 0.0 21536 17612 - I 14:41 0:00.16 imap: [user(a)domain.com 11.11.11.11 IDLE] (imap) vmail 77127 0.0 0.0 21516 17396 - S 15:17 0:00.07 imap: [user(a)domain.com 11.11.11.11] (imap) vmail 77170 0.0 0.0 21516 17380 - I 15:19 0:00.06 imap: [user(a)domain.com 11.11.11.11] (imap) vmail 77438 0.0 0.0 21516 17396 - S 15:31 0:00.05 imap: [user(a)domain.com 11.11.11.11] (imap) vmail 77536 0.0 0.0 21548 17400 - S 15:35 0:00.05 imap: [user(a)domain.com 11.11.11.11 IDLE] (imap) vmail 77539 0.0 0.0 21516 17256 - I 15:35 0:00.03 imap: [user(a)domain.com 11.11.11.11] (imap) vmail 77594 0.0 0.0 8892 4760 - S 15:38 0:00.01 imap-hibernate: [0 connections] (imap-hibernate) vmail 77620 0.0 0.0 21516 17256 - I 15:39 0:00.03 imap: [user(a)domain.com 11.11.11.11] (imap) My build options: Install prefix . : /opt/dovecot/2.3.5 File offsets ... : 64bit I/O polling .... : kqueue I/O notifys .... : kqueue SSL ............ : yes (OpenSSL) GSSAPI ......... : no passdbs ........ : static passwd passwd-file pam checkpassword sql CFLAGS ......... : -std=gnu99 -O2 -pipe -fno-strict-aliasing -fstack-protector-strong -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -Wno-duplicate-decl-specifier -Wstrict-aliasing=2 : -shadow -bsdauth -sia -ldap -vpopmail userdbs ........ : static prefetch passwd passwd-file checkpassword sql : -ldap -vpopmail SQL drivers .... : mysql : -pgsql -sqlite -cassandra Full text search : squat lucene : -solr Configure command: ./configure '--prefix=/opt/dovecot/2.3.5' --without-docs '--without-shadow' '--without-docs' '--without-gssapi' '--without-vpopmail' '--without-ldap' --without-shadow --with-ssl=openssl --with-mysql --with-zlib --with-libwrap --with-lucene --with-stemmer --with-textcat --with-icu --without-cdb --without-lua --disable-silent-rules --build=amd64-portbld-freebsd11.2 'CC=cc' 'CFLAGS=-O2 -pipe -fno-strict-aliasing' 'LDFLAGS= -L/usr/local/lib' 'CPPFLAGS=-I/usr/local/include' 'CPP=cpp' 'CXX=c++' 'CXXFLAGS=-O2 -pipe -fno-strict-aliasing' My dovecot version: # dovecot --version 2.3.5 (513208660) My config: service imap-hibernate { chroot = client_limit = 0 drop_priv_before_exec = no executable = imap-hibernate extra_groups = $default_internal_group 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 = vmail } user = vmail vsz_limit = 18446744073709551615 B }

4 4

question about %u and %h used in mail_location
by Joe Wong 12 Mar '19

12 Mar '19

Hello, I have defined the following: mail_location = maildir:~:INBOX=~/Maildir:LAYOUT=fs:INDEX=%u %u is retrieve via database in that my username contain ":", in which it create some confusion to dovecot: doveadm index -u user1:site@domain iNBOX doveadm(user1:site@domain): Error: remote(192.168.10.22:24245): Namespace '': Unknown setting: site@domain I cannot change the value in DB so is there a workaround to this problem? TIA. - Joe

2 1

Suggestions for dovecot-submission (XCLIENT NAME attribute)
by Marcelo Coelho 12 Mar '19

12 Mar '19

Hi, Currently, Dovecot Submission doesn't forward NAME attribute when XCLIENT is enable: Received: from server.example.org (localhost [1.2.3.4]) (Authenticated sender: test(a)example.org) by localhost (Postfix) with ESMTPA id AAAAAAAAAA for <user(a)domain.com>; Fri, 8 Mar 2019 12:28:02 Postfix adds a header with the sender IP address (1.2.3.4), but with localhost as hostname. It would be great if Dovecot Submission send NAME attribute, with the resolved hostname of the sender IP (ADDR attribute). Thank you! -- Marcelo Coelho

2 1

Sieve scripts not triggered on IMAP inbound messages using IMAPC
by Fred 12 Mar '19

12 Mar '19

Good morning. I am using Dovecot as an IMAP proxy -- using IMAPC -- and the system is working great. Thank you for contributing such great software to the community! I'm using Dovcot 2.3.5 and Pigeonhole 0.5.5. My server is located behind a content-filtering firewall that will mark incoming messages by adding "[SPAM]" to the subject line. I'm trying to use Sieve to identify those messages and move them into the Spam folder. I have a basic Sieve script that looks like this: require ["fileinto"]; if anyof (header :contains "Subject" "[SPAM]", header :contains "X-Spam-Flag" "Yes") { fileinto "Spam"; stop; } I can see in the logs that Sieve is loaded, and also the imapsieve_plugin Debug: sieve: Pigeonhole version 0.5.5 (2483b085) initializing Debug: sieve: Sieve imapsieve plugin for Pigeonhole version 0.5.5 (2483b085) loaded Sieve detects outbound messages (from the log: Debug: imapsieve: mailbox INBOX.Sent: APPEND event) but nothing registers for inbound, and my spam_rule is never triggered. Any suggestions? Here is the output from "Dovecot -n": # 2.3.5 (513208660): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.5 (2483b085) # OS: Linux 3.10.0-957.5.1.el7.x86_64 x86_64 CentOS Linux release 7.6.1810 (Core) xfs # Hostname: <redacted> auth_master_user_separator = * auth_mechanisms = PLAIN LOGIN auth_verbose_passwords = plain deliver_log_format = from=%{from}, envelope_sender=%{from_envelope}, subject=%{subject}, msgid=%m, size=%{size}, %$ dict { acl = pgsql:/etc/dovecot/dovecot-share-folder.conf quotadict = pgsql:/etc/dovecot/dovecot-used-quota.conf } first_valid_uid = 2000 imapc_features = fetch-bodystructure fetch-headers imapc_host = <redacted> imapc_port = 993 imapc_ssl = imaps imapc_ssl_verify = no last_valid_uid = 2000 listen = * [::] mail_debug = yes mail_gid = 2000 mail_home = /var/mail/imapc/home/%d/%n mail_location = imapc:/var/mail/imapc/%d/%n mail_plugins = mailbox_alias mail_log notify mail_uid = 2000 managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date index ihave duplicate mime foreverypart extracttext imapsieve vnd.dovecot.imapsieve namespace inbox { inbox = yes list = yes location = prefix = separator = . type = private } passdb { args = host=<redacted> default_fields = userdb_imapc_user=%u userdb_imapc_password=#hidden_use-P_to_show# driver = imap } passdb { args = /etc/dovecot/dovecot-master-users driver = passwd-file master = yes } plugin { imapsieve_default = /var/vmail/sieve/global/spam_rule.sieve mail_log_events = delete undelete expunge mailbox_delete mailbox_rename mail_log_fields = uid box msgid size from subject mailbox_alias_new = Sent Messages mailbox_alias_new2 = Sent Items mailbox_alias_old = Sent mailbox_alias_old2 = Sent sieve_global_dir = /var/vmail/sieve/global/ sieve_max_redirects = 30 sieve_plugins = sieve_imapsieve sieve_trace_debug = yes sieve_trace_dir = /var/log/dovecot sieve_trace_level = matching } protocols = imap sieve service auth { unix_listener /var/spool/postfix/private/dovecot-auth { group = postfix mode = 0666 user = postfix } unix_listener auth-master { group = vmail mode = 0666 user = vmail } unix_listener auth-userdb { group = vmail mode = 0660 user = vmail } } service dict { unix_listener dict { group = vmail mode = 0660 user = vmail } } service imap-login { process_limit = 500 service_count = 1 } service lmtp { executable = lmtp -L inet_listener lmtp { address = 127.0.0.1 port = 24 } process_min_avail = 5 unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } user = vmail } service managesieve-login { inet_listener sieve { address = 127.0.0.1 port = 4190 } } ssl = required ssl_cert = </etc/letsencrypt/live/mgrids.dynu.com/fullchain.pem ssl_cipher_list = ECDH+AESGCM:DH+AESGCM:ECDH+AES256:DH+AES256:ECDH+AES128:DH+AES:ECDH+3DES:DH+ 3DES:RSA+AESGCM:RSA+AES:RSA+3DES:!aNULL:!MD5 ssl_client_ca_file = /etc/pki/ca-trust/extracted/pem/tls-ca-bundle.pem ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it ssl_prefer_server_ciphers = yes syslog_facility = local5 userdb { driver = prefetch } protocol imap { imap_client_workarounds = tb-extra-mailbox-sep mail_max_userip_connections = 30 mail_plugins = mailbox_alias mail_log notify imap_sieve } protocol sieve { info_log_path = /var/log/dovecot/sieve-info.log log_path = /var/log/dovecot/sieve-err.log managesieve_implementation_string = Dovecot Pigeonhole managesieve_max_line_length = 65536 }

2 2

dovecot Connection closed IDLE running
by Adrian Minta 11 Mar '19

11 Mar '19

Hello, sometimes I get lines like this on mail log. Mar 11 07:57:14 mail2 dovecot: imap(john.one(a)domain.ro): Connection closed (IDLE running for 0.006 + waiting input for 1765.640 secs, 0.001 in locks, 2 B in + 10+0 B out, state=wait-input) in=323201 out=3177999 Mar 11 07:58:56 mail3 dovecot: imap(john.two(a)domain.ro): Connection closed (IDLE running for 0.005 + waiting input for 3535.348 secs, 0.001 in locks, 2 B in + 10+0 B out, state=wait-input) in=1627 out=14872 Mar 11 08:38:50 mail2 dovecot: imap(sam(a)domain.ro): Connection closed (IDLE running for 2.225 + waiting input for 267.413 secs, 0.005 in locks, 2 B in + 10+0 B out, state=wait-input) in=7212 out=2503 Mar 11 09:01:23 mail2 dovecot: imap(john.one(a)domain.ro): Connection closed (FETCH running for 8.784 + waiting input for 0.001 secs, 0.008 in locks, 24 B in + 6291+6291 B out, state=wait-input) in=196 out=43968 Mar 11 09:02:57 mail1 dovecot: imap(bush(a)domain.ro): Connection closed (IDLE running for 0.006 + waiting input for 1031.530 secs, 0.001 in locks, 2 B in + 10+0 B out, state=wait-input) in=9157 out=381003 Mar 11 09:33:31 mail2 dovecot: imap(john.one(a)domain.ro): Connection closed (IDLE running for 0.008 + waiting input for 1737.458 secs, 0.001 in locks, 2 B in + 41+0 B out, state=wait-input) in=7871 out=322122 Our dovecot version is 2.2.27 and the mail storage is maildir. What is the cause ? Could this negatively affects the users ? -- Best regards, Adrian Minta

1 0

Assistance with doveadm backup...
by SH Development 11 Mar '19

11 Mar '19

I am having trouble locating examples of how to use doveadm backup. All the examples I see are for sync. I simply want to create a backup to a network volume of the email server's vmail folders. The goal here is to have a reasonably current backup should the main drive on the email server go south. We currently authenticate our users from a mysql database. User’s mailboxes are stored as domainname/username/Maildir I assume what I will wind up on the network volume is a duplicate directory structure as the vmail folder on the email server? Can someone help get me started here? Jeff

7 13

readonly archive folders using squashfs
by Natu 11 Mar '19

11 Mar '19

I have a dovecot server running under CentOS using maildir format. Due to the issue with minimum blocksize for files I would like to offer some kind of readonly archive using something like the compressed squashfs where I would move messages to be archived to a maildir folder and then convert "cur" directory into a squashfs and mount it in place of the original directory so my biggest users could have readonly access to older messages without it using so much disk space. Has anyone tried anything like this before and is dovecot likely to complain about the readonly cur directory? If the complaints are minimal and didn't cause other problems it might be ok. Any better ideas to implement something like this? Thank You, Natu

2 2

Re: Auto MX Email Client configuration, the right way?
by Davide Marchi 10 Mar '19

10 Mar '19

> Now I've seen the new RFC 6186 specification > (https://tools.ietf.org/html/rfc6186) that describe a "DNS way" to > achieve the same goal. > > [..] > again: > [..] > When a user identifier is required, MUAs MUST first > use the full email address provided by the user, and if that > results > in an authentication failure, SHOULD fall back to using the "local- > part" extracted from the email address. This is in line with the > guidance outlined in Section 5. If both these user identifiers > result in authentication failure, the MUA SHOULD prompt the user > for > a valid identifier. > [..] > > here I have the biggest doubt, in fact Thunderbird often uses only the > username and not the whole email address, both for incoming and > outgoing > server... > Is any of you using this second way? And possibly, do you kniw if it > works with different clients (desktop and mobile)? I've made some tests and this solution seems very serviceable, for the only exception for the user name on Thunderbird. Unlike what is stated in this RFC, Thunderbird "takes" only the name and not the entire email address as the username. Anyone knows if is it possible to communicate the username type via RFC? Many thanks again! Davide

2 1

GSSAPI and usernames, not Kerberos ticket names
by Dmitry Donskih 09 Mar '19

09 Mar '19

Hi all, I've got a Dovecot v2.3.3 IMAP with GSSAPI auth set up. This server is in main domain, 'contoso.com'. I also have several subdomains. My problem is usernames with GSSAPI authentication: When I try to login as 'user' or as 'user(a)CONTOSO.COM' - everything works. But, 'user(a)contoso.com' auth fails. But when I try to login as subdomain user, 'user2' - it fails to login. 'user2(a)sub.contoso.com' fails also. However, 'user2(a)SUB.CONTOSO.COM' works ok. It looks like PAM uses domain part of login as Kerberos realm name, regardless of Kerberos domain-realm mapping. Also, if domain part is not specified, PAM (Kerberos?) fails to determine non-default realm. What am I missing? Is there a way to use traditional 'user@domain' login names with PAM/GSSAPI, instead of Kerberos ticket names? Or maybe to tell PAM module to convert domain part of username to uppercase before using? Thanks on any help or advice. ===== dovecot.conf: ===== auth_mechanisms = gssapi plain login external auth_gssapi_hostname = "$ALL" auth_krb5_keytab = /etc/krb5.keytab auth_default_realm = passdb { driver = pam args = cache_key=%d%r%n failure_show_msg=yes dovecot } userdb { driver = static args = uid=502 gid=502 home=/var/vmail/%L{auth_domain}/%L{auth_username} mail=maildir:/var/vmail/%L{auth_domain}/%L{auth_username}/Maildir allow_all_users=yes } ===== ===== pam.d/dovecot: ===== auth sufficient pam_krb5.so use_first_pass account [default=bad success=ok user_unknown=ignore] pam_krb5.so password sufficient pam_krb5.so use_authtok session optional pam_krb5.so ===== ===== krb5.conf: ===== [libdefaults] default_realm = CONTOSO.COM dns_lookup_realm = true dns_lookup_kdc = true [realms] CONTOSO.COM = { kdc = dc.contoso.com:88 admin_server = dc.contoso.com:749 } [domain_realm] contoso.com = CONTOSO.COM .contoso.com = CONTOSO.COM sub.contoso.com = CONTOSO.COM .sub.contoso.com = CONTOSO.COM SUB.CONTOSO.COM = CONTOSO.COM .SUB.CONTOSO.COM = CONTOSO.COM [appdefaults] pam = { ticket_lifetime = 36000 renew_lifetime = 36000 forwardable = true krb4_convert = false } ===== klist server ==== Default principal: imap/mail2.contoso.com(a)CONTOSO.COM ===== klist client ==== Default principal: user2(a)SUB.CONTOSO.COM ===== Logging in with user2(a)SUB.CONTOSO.COM - OK: ===== auth: Debug: client in: AUTH 1 GSSAPI service=imap secured=tls session=.... auth: Debug: gssapi(?,192.168.....,<MR1yvq6DftfAqAoP>): Using all keytab entries auth: Debug: client passdb out: CONT 1 auth: Debug: client in: CONT<hidden> auth: Debug: gssapi(user2(a)sub.contoso.com,192.168....,<MR1yvq6DftfAqAoP>): security context state completed. auth: Debug: client passdb out: CONT 1 YIGVB.... auth: Debug: client in: CONT<hidden> auth: Debug: gssapi(user2(a)sub.contoso.com,192.168.....,<MR1yvq6DftfAqAoP>): Negotiated security layer auth: Debug: client passdb out: CONT 1 BQQF/..... auth: Debug: client in: CONT<hidden> auth: Debug: pam(user2(a)sub.contoso.com,192.168.....,<MR1yvq6DftfAqAoP>): passdb doesn't support credential lookups auth: Debug: gssapi(user2(a)sub.contoso.com,192.168.....,<MR1yvq6DftfAqAoP>): skipping passdb: mechanism filtered auth: Debug: client passdb out: OK 1 user=user2(a)sub.contoso.com original_user=user2(a)SUB.CONTOSO.COM ===== Logging in with user2(a)sub.contoso.com - FAIL: ===== auth: Debug: client in: AUTH 1 GSSAPI service=imap secured=tls session=... auth: Debug: gssapi(?,192.168....,<Hgh4zq6DhNfAqAoP>): Using all keytab entries auth: Debug: client passdb out: CONT 1 auth: Debug: client in: CONT<hidden> auth: Debug: gssapi(user2(a)sub.contoso.com,192.168....,<Hgh4zq6DhNfAqAoP>): security context state completed. auth: Debug: client passdb out: CONT 1 YIGVB..... auth: Debug: client in: CONT<hidden> auth: Debug: gssapi(user2(a)sub.contoso.com,192.168....,<Hgh4zq6DhNfAqAoP>): Negotiated security layer auth: Debug: client passdb out: CONT 1 BQQF/..... auth: Debug: client in: CONT<hidden> auth: Debug: pam(user2(a)sub.contoso.com,192.168.....,<Hgh4zq6DhNfAqAoP>): passdb doesn't support credential lookups auth: Debug: gssapi(user2(a)sub.contoso.com,192.168.....,<Hgh4zq6DhNfAqAoP>): skipping passdb: mechanism filtered auth: Debug: client passdb out: FAIL 1 user=user2(a)sub.contoso.com original_user=user2(a)SUB.CONTOSO.COM

1 0

Auto MX Email Client configuration, the right way?
by Davide Marchi 09 Mar '19

09 Mar '19

Hi Friends! An opinion. I would like to facilitate the configuration of one's mail client (desktop or mobile) to my users server. Some time ago I asked the same question and you suggested me to use "Automx". So I started of good will and I looked for the Automx documentation. And here the problems started as I found several inconsistencies, even parameters (in official documentation) that produce Apache errors.. to complicate things, different path between deb packages and official version :-) Now I've seen the new RFC 6186 specification (https://tools.ietf.org/html/rfc6186) that describe a "DNS way" to achieve the same goal. [..] 4. Guidance for MUAs By using SRV records as above, MUAs need initially only to prompt the user for their email address [RFC5322]. The "local-part" and "domain" portions are then extracted from the email address by the MUA. The MUA uses the "domain" portion as the service domain to perform SRV lookups for the services it wants to configure. If the SRV lookup is successful, the target FQDN and port for the service can be determined and used to complete MUA configuration. If an SRV record is not found, the MUA will need to prompt the user to enter the FQDN and port information directly, or use some other heuristic. In the case of multiple SRV records returned for a particular service, the MUA MUST use the priority and weight fields in the record to determine which one to use (as per [RFC2782]). [..] again: [..] When a user identifier is required, MUAs MUST first use the full email address provided by the user, and if that results in an authentication failure, SHOULD fall back to using the "local- part" extracted from the email address. This is in line with the guidance outlined in Section 5. If both these user identifiers result in authentication failure, the MUA SHOULD prompt the user for a valid identifier. [..] here I have the biggest doubt, in fact Thunderbird often uses only the username and not the whole email address, both for incoming and outgoing server... Is any of you using this second way? And possibly, do you kniw if it works with different clients (desktop and mobile)? Many many thanks! Davide

3 2

Dovecot v2.3.5 released
by Aki Tuomi 08 Mar '19

08 Mar '19

Hi! We are happy to release dovecot v2.3.5. Please find sources at https://dovecot.org/releases/2.3/dovecot-2.3.5.tar.gz https://dovecot.org/releases/2.3/dovecot-2.3.5.tar.gz.sig You can find precompiled binaries at https://repo.dovecot.org/ NEWS: + Lua push notification driver: mail keywords and flags are provided in MessageNew and MessageAppend events. + submission: Implement support for plugins. + auth: When auth_policy_log_only=yes, only log what the policy server response would do without actually doing it. + auth: Always log policy server decisions with auth_verbose=yes - v2.3.[34]: doveadm log errors: Output was missing user/session - lda: Debug log lines could have shown slightly corrupted - login proxy: Login processes may have crashed in various ways when login_proxy_max_disconnect_delay was set. - imap: Fix crash with Maildir+zlib if client disconnects during APPEND - lmtp proxy: Fix potential assert-crash - lmtp/submission: Fix crash when SMTP client transaction times out - submission: Split large XCLIENT commands to 512 bytes per command, so Postfix accepts them. - submission: Fix crash when client sends invalid BURL command - submission: relay backend: VRFY command: Avoid forwarding 500 and 502 replies back to client. - lib-http: Fix potential assert-crash when DNS lookup fails - lib-fts: Fix search query generation when one language ignores a token (e.g. via stopwords). --- Aki Tuomi Open-Xchange Oy

3 5

Re: Removing a mailbox from a dovecot cluster
by Francis 08 Mar '19

08 Mar '19

Le mar. 26 févr. 2019 à 22:58, David Myers <david.myers.24j74(a)gmail.com> a écrit : > Hello Francis, > > I wonder if this is due to how a cluster is configured to function > internally. > > Tell us more about the cluster, is it one of those ‘fancy pants’ high > availability, auto backup heart beat things, or is it more a traditional > multi server (master slave style) setup. > > Either way you may need to disconnect the servers from one another and > delete the offending files / directories either via dove or or via the os > (although reading your original email it sounds like you are already > attempting this). > > If you have a fancy cluster this may actually be more difficult than it > sounds and have interesting (unwanted) side effects, also the underlying > database (if you are storing emails that way) may have a method to remove > data > > I assume you are keeping back up copies of all those emails somewhere, > just in case you need them in the future. > > See this wiki article to better understand what I mean by the ‘fancy > pants’ clusters : > https://en.m.wikipedia.org/wiki/High-availability_cluster > They sound very cool, but I suspect are overkill for a mail server, unless > your database is already inside one then it would make sense I guess. > > Hello, I just use the cluster/replication functionality integrated into dovecot, nothing more. There is no database involved. I use LDAP for the authentication. The mails are stored locally on each server and replicated with the replication feature of dovecot. I followed this wiki article: https://wiki.dovecot.org/Replication Thanks! -- Francis

2 8

imap segfault in libc.so with CLucene FTS backend enabled
by Alexander Miroshnichenko 08 Mar '19

08 Mar '19

Steps to reproduce: - Enable CLucene FTS in Dovecot; - Open mailbox with MUA; - Search for message with any text; - IMAP session crash. OS: Gentoo Base System release 2.6 Version: FTS: dev-cpp/clucene-2.3.3.4-r6 IMAP: net-mail/dovecot-2.3.2.1 LIBC: sys-libs/musl-1.1.21 Dovecot FTS config: plugin { fts = lucene fts_lucene = whitespace_chars=@. normalize no_snowball fts_autoindex=yes fts_autoindex_max_recent_msgs=80 fts_index_timeout=90 } dmesg: [260150.192294] imap[18221]: segfault at 6578772cca98 ip 000063e7f1b10397 sp 00007945d5822970 error 6 in libc.so[63e7f1ae8000+a4000] [260150.192316] Code: 0f 84 44 02 00 00 48 39 ca 0f 84 62 02 00 00 48 8b 43 08 48 89 4a 10 48 89 51 18 48 89 c2 48 83 e0 fe 48 83 ca 01 48 89 53 08 <48> 83 0c 03 01 41 8b 07 48 8d 6b 10 85 c0 0f 84 68 ff ff ff 31 c0 bt full: Core was generated by `dovecot/imap'. Program terminated with signal SIGSEGV, Segmentation fault. #0 unbin (i=0, c=0x1908553de10) at src/malloc/malloc.c:195 195 src/malloc/malloc.c: No such file or directory. (gdb) bt full #0 unbin (i=0, c=0x1908553de10) at src/malloc/malloc.c:195 No locals. #1 malloc (n=<optimized out>, n@entry=4) at src/malloc/malloc.c:320 mask = <optimized out> c = 0x1908553de10 i = 0 j = 0 #2 0x000063e7f1b4984f in wcsdup (s=0x63e7ed7d0c58 L"") at src/string/wcsdup.c:7 l = 0 d = <optimized out> #3 0x000063e7eda98308 in lucene::index::Term::Term (this=0x1908553df80) at /var/tmp/portage/dev-cpp/clucene-2.3.3.4-r6/work/clucene-core-2.3.3.4/src/core/CLucene/index/Term.cpp:26 No locals. #4 0x000063e7edad5f25 in lucene::index::SegmentTermEnum::readTerm(lucene::index::Term*) () at /var/tmp/portage/dev-cpp/clucene-2.3.3.4-r6/work/clucene-core-2.3.3.4/src/core/CLucene/index/SegmentTermEnum.cpp:351 start = 1 length = 4 totalLength = 5 field = <optimized out> fieldname = 0x1908553d180 L"\142\157\144\171" #5 0x000063e7edad5f7c in lucene::index::SegmentTermEnum::next (this=0x19085524460) at /var/tmp/portage/dev-cpp/clucene-2.3.3.4-r6/work/clucene-core-2.3.3.4/src/core/CLucene/index/SegmentTermEnum.cpp:180 tmp = <optimized out> this = 0x19085524460 tmp = <optimized out> tmp = <optimized out> #6 0x000063e7edad5be9 in lucene::index::SegmentTermEnum::scanTo (this=this@entry=0x19085524460, term=term@entry=0x7945d5822dc0) at /var/tmp/portage/dev-cpp/clucene-2.3.3.4-r6/work/clucene-core-2.3.3.4/src/core/CLucene/index/SegmentTermEnum.cpp:218 No locals. #7 0x000063e7edad959c in lucene::index::TermInfosReader::scanEnum (this=<optimized out>, term=term@entry=0x7945d5822dc0) at /var/tmp/portage/dev-cpp/clucene-2.3.3.4-r6/work/clucene-core-2.3.3.4/src/core/CLucene/index/TermInfosReader.cpp:422 enumerator = 0x19085524460 #8 0x000063e7edad96a4 in lucene::index::TermInfosReader::get (this=<optimized out>, term=term@entry=0x7945d5822dc0) at /var/tmp/portage/dev-cpp/clucene-2.3.3.4-r6/work/clucene-core-2.3.3.4/src/core/CLucene/index/TermInfosReader.cpp:246 enumerator = <optimized out> #9 0x000063e7edab9071 in lucene::index::SegmentReader::docFreq (this=0x19085500ae0, t=0x7945d5822dc0) at /var/tmp/portage/dev-cpp/clucene-2.3.3.4-r6/work/clucene-core-2.3.3.4/src/core/CLucene/index/SegmentReader.cpp:518 ti = <optimized out> #10 0x000063e7edae2620 in lucene::search::Similarity::idf (this=0x19085526e60, term=0x7945d5822dc0, searcher=0x190855007a0) at /var/tmp/portage/dev-cpp/clucene-2.3.3.4-r6/work/clucene-core-2.3.3.4/src/core/CLucene/search/Similarity.cpp:184 No locals. #11 0x000063e7edaeda51 in lucene::search::TermWeight::TermWeight(lucene::search::Searcher*, lucene::search::TermQuery*, lucene::index::Term*) () at /var/tmp/portage/dev-cpp/clucene-2.3.3.4-r6/work/clucene-core-2.3.3.4/src/core/CLucene/search/TermQuery.cpp:117 No locals. #12 0x000063e7edaeda99 in lucene::search::TermQuery::_createWeight(lucene::search::Searcher*) () at /var/tmp/portage/dev-cpp/clucene-2.3.3.4-r6/work/clucene-core-2.3.3.4/src/core/CLucene/search/TermQuery.cpp:240 No locals. #13 0x000063e7edafa2dc in lucene::search::BooleanWeight::BooleanWeight(lucene::search::Searcher*, lucene::util::CLVector<lucene::search::BooleanClause*, lucene::util::Deletor::Object<lucene::search::BooleanClause> >*, lucene::search::BooleanQuery*) () at /usr/lib/gcc/x86_64-gentoo-linux-musl/8.2.0/include/g++-v8/bits/stl_vector.h:930 i = 1 i = <optimized out> #14 0x000063e7edafa351 in lucene::search::BooleanQuery::_createWeight(lucene::search::Searcher*) () at /var/tmp/portage/dev-cpp/clucene-2.3.3.4-r6/work/clucene-core-2.3.3.4/src/core/CLucene/search/BooleanQuery.cpp:66 No locals. #15 0x000063e7edaef926 in lucene::search::Query::weight (this=this@entry=0x7945d5822da0, searcher=searcher@entry=0x190855007a0) at /var/tmp/portage/dev-cpp/clucene-2.3.3.4-r6/work/clucene-core-2.3.3.4/src/core/CLucene/search/SearchHeader.cpp:121 query = <optimized out> weight = <optimized out> sum = <optimized out> norm = <optimized out> #16 0x000063e7edaf0cd7 in lucene::search::IndexSearcher::_search(lucene::search::Query*, lucene::search::Filter*, int) () at /var/tmp/portage/dev-cpp/clucene-2.3.3.4-r6/work/clucene-core-2.3.3.4/src/core/CLucene/search/IndexSearcher.cpp:222 weight = <optimized out> scorer = <optimized out> bits = <optimized out> hq = <optimized out> totalHits = <optimized out> hitCol = {<lucene::search::HitCollector> = {<lucene::debug::LuceneVoidBase> = {_vptr.LuceneVoidBase = 0x2}, <No data fields>}, minScore = -1.75304399e+30, bits = 0x30, hq = 0xffffffffffffffff, nDocs = 40, totalHits = 0x63e7eda6f2cc <lucene::util::Compare::WChar::operator()(wchar_t const*, wchar_t const*) const+20>} scoreDocsLength = <optimized out> scoreDocs = <optimized out> totalHitsInt = <optimized out> wq = <optimized out> #17 0x000063e7edaf4344 in lucene::search::Hits::getMoreDocs(unsigned long) () at /var/tmp/portage/dev-cpp/clucene-2.3.3.4-r6/work/clucene-core-2.3.3.4/src/core/CLucene/search/Hits.cpp:120 _min = <optimized out> n = <optimized out> topDocs = 0x0 scoreDocs = <optimized out> scoreDocsLength = <optimized out> scoreNorm = <optimized out> ---Type <return> to continue, or q <return> to quit--- #18 0x000063e7edaf443e in lucene::search::Hits::Hits (this=0x1908553a1a0, s=0x190855007a0, q=<optimized out>, f=<optimized out>, _sort=<optimized out>) at /var/tmp/portage/dev-cpp/clucene-2.3.3.4-r6/work/clucene-core-2.3.3.4/src/core/CLucene/search/Hits.cpp:60 No locals. #19 0x000063e7edaef7fc in lucene::search::Searcher::search(lucene::search::Query*, lucene::search::Filter*) () at /var/tmp/portage/dev-cpp/clucene-2.3.3.4-r6/work/clucene-core-2.3.3.4/src/core/CLucene/search/SearchHeader.cpp:188 No locals. #20 0x000063e7edd7edf0 in lucene_index_search(lucene_index*, array__lucene_query&, fts_result*, array__seq_range*) () at lucene-wrapper.cc:1361 hits = <optimized out> last_uid = <optimized out> score = <optimized out> ret = 0 query = {<lucene::search::Query> = {<lucene::util::NamedObject> = {_vptr.NamedObject = 0x63e7edd6e970 <vtable for lucene::search::BooleanQuery+16>}, boost = 1}, clauses = 0x190855007e0, static maxClauseCount = 1024, static allowDocsOutOfOrder = false, disableCoord = false, minNrShouldMatch = 0} mailbox_term = {<lucene::debug::LuceneBase> = {_vptr.LuceneBase = 0x63e7edd68e80 <vtable for lucene::index::Term+16>, __cl_refcount = 2}, cachedHashCode = 0, _field = 0x190854bd7c0 L"\142\157\170", _text = 0x1908553a0a0 L"\142\146\064\141\067\066\061\060\146\062\070\143\063\142\065\143\066\145\060\062\060\060\060\060\065\143\146\143\061\141\061\064", textLenBuf = 32, textLen = 32, internF = true} mailbox_query = {<lucene::search::Query> = {<lucene::util::NamedObject> = {_vptr.NamedObject = 0x63e7edd6d918 <vtable for lucene::search::TermQuery+16>}, boost = 1}, term = 0x7945d5822dc0} #21 0x000063e7edd7ff54 in lucene_index_lookup (index=0x190854ee8e0, args=args@entry=0x1908553b468, flags=flags@entry=(unknown: 0), result=result@entry=0x7945d5823000) at lucene-wrapper.cc:1421 uids_arr = <optimized out> arg = 0x0 def_queries = {arr = {buffer = 0x190854b2438, element_size = 16}, v = 0x190854b2438, v_modifiable = 0x190854b2438} have_definites = true maybe_queries = {arr = {buffer = 0xc, element_size = 18446744073709551612}, v = 0xc, v_modifiable = 0xc} have_maybies = <optimized out> #22 0x000063e7edd7c0d4 in fts_backend_lucene_lookup () at fts-backend-lucene.c:489 _data_stack_cur_id = 5 backend = 0x190854ee780 ret = <optimized out> #23 0x000063e7f09a85dd in fts_backend_lookup (backend=0x190854ee780, box=0x190854fc148, args=args@entry=0x1908553b468, flags=flags@entry=(unknown: 0), result=result@entry=0x7945d5823000) at fts-api.c:353 No locals. #24 0x000063e7f09acd92 in fts_search_lookup_level_single (and_args=<optimized out>, args=0x1908553b468, fctx=0x190854f5520) at fts-search.c:50 flags = (unknown: 0) level = <optimized out> result = {box = 0x0, definite_uids = {arr = {buffer = 0x19085528378, element_size = 8}, v = 0x19085528378, v_modifiable = 0x19085528378}, maybe_uids = {arr = {buffer = 0x190855284b8, element_size = 8}, v = 0x190855284b8, v_modifiable = 0x190855284b8}, scores = {arr = {buffer = 0x190855285f8, element_size = 8}, v = 0x190855285f8, v_modifiable = 0x190855285f8}, scores_sorted = false} flags = <optimized out> level = <optimized out> result = <optimized out> #25 fts_search_lookup_level () at fts-search.c:210 _data_stack_cur_id = 4 ret = <optimized out> #26 0x000063e7f09ad32c in fts_search_lookup_level () at fts-search.c:220 ret = 0 #27 0x000063e7f09ad48e in fts_search_lookup () at fts-search.c:360 last_uid = 622 seq1 = 544 seq2 = 807 __func__ = "fts_search_lookup" #28 0x000063e7f09af460 in fts_mailbox_search_init () at fts-storage.c:250 ft = 0x19085511e60 fbox = <optimized out> flist = <optimized out> ctx = 0x190854f5240 fctx = 0x190854f5520 #29 0x000001905d983992 in imap_search_start () at imap-search.c:586 cmd = 0x190854e9628 __func__ = "imap_search_start" #30 0x000001905d9753e5 in cmd_search (cmd=<optimized out>) at cmd-search.c:48 ctx = 0x190854e9830 sargs = 0x1908553b308 args = 0x19085527620 charset = 0x190854f3860 "utf-8" ret = 1 #31 0x000001905d97cad4 in command_exec () at imap-commands.c:201 hook = 0x1905db9cda0 finished = <optimized out> __func__ = "command_exec" #32 0x000001905d97b262 in client_command_input () at imap-client.c:1152 client = 0x190854e89c8 command = <optimized out> __func__ = "client_command_input" #33 0x000001905d97b305 in client_command_input () at imap-client.c:1215 client = 0x190854e89c8 command = <optimized out> __func__ = "client_command_input" ---Type <return> to continue, or q <return> to quit--- #34 0x000001905d97b6cd in client_handle_next_command (remove_io_r=<synthetic pointer>, client=0x190854e89c8) at imap-client.c:1257 No locals. #35 client_handle_input () at imap-client.c:1271 _data_stack_cur_id = 3 ret = <optimized out> remove_io = false handled_commands = false ret = <optimized out> remove_io = <optimized out> __func__ = "client_handle_input" client = 0x190854e89c8 handled_commands = <optimized out> _data_stack_cur_id = <optimized out> ret = <optimized out> remove_io = <optimized out> __func__ = "client_handle_input" _data_stack_cur_id = <optimized out> #36 0x000001905d97bb9e in client_input () at imap-client.c:1317 cmd = 0x190854cfba0 output = 0x190854e9440 bytes = 80 __func__ = "client_input" #37 0x000063e7f14f8c58 in io_loop_call_io () at ioloop.c:674 ioloop = 0x63e7f1ae7f20 t_id = 2 __func__ = "io_loop_call_io" #38 0x000063e7f14fa116 in io_loop_handler_run_internal () at ioloop-epoll.c:222 ctx = 0x1905db9cfc0 events = <optimized out> event = 0x190854bc360 list = 0x190854bd1a0 io = <optimized out> tv = {tv_sec = 1799, tv_usec = 999332} events_count = <optimized out> msecs = <optimized out> ret = <optimized out> i = 0 j = <optimized out> call = <optimized out> __func__ = "io_loop_handler_run_internal" #39 0x000063e7f14f8cfa in io_loop_handler_run () at ioloop.c:726 __func__ = "io_loop_handler_run" #40 0x000063e7f14f8e68 in io_loop_run () at ioloop.c:699 __func__ = "io_loop_run" #41 0x000063e7f1480dbb in master_service_run (service=0x63e7f1ae7de0, callback=callback@entry=0x1905d987e60 <client_connected>) at master-service.c:767 No locals. #42 0x000001905d96dfc4 in main () at main.c:521 set_roots = {0x1905db9aa20 <smtp_submit_setting_parser_info>, 0x1905db9a740 <imap_setting_parser_info>, 0x0} login_set = {auth_socket_path = 0x190854b2060 "\003", postlogin_socket_path = 0x0, postlogin_timeout_secs = 60, callback = 0x1905d9886b0 <login_client_connected>, failure_callback = 0x1905d987f28 <login_client_failed>, request_auth_token = true} service_flags = <optimized out> storage_service_flags = MAIL_STORAGE_SERVICE_FLAG_NO_NAMESPACES username = 0x0 auth_socket_path = <optimized out> c = <optimized out> error = 0x4cd0 <error: Cannot access memory at address 0x4cd0> #43 0x000063e7f1b0506b in libc_start_main_stage2 (main=0x1905d96dc80 <main>, argc=1, argv=0x7945d5823688) at src/env/__libc_start_main.c:94 envp = 0x7945d5823698 #44 0x000001905d96e168 in _start_c () at imap-client.c:1433 No symbol table info available. #45 0x0000000000000000 in ?? () No symbol table info available. (gdb) -- Alexander Miroshnichenko

1 0

Re: rsync /old/server new/server ?
by Aki Tuomi 08 Mar '19

08 Mar '19

On 8.3.2019 14.07, Voytek Eymont wrote: > On Fri, March 8, 2019 10:45 pm, Aki Tuomi via dovecot wrote: >> On 8.3.2019 13.44, Voytek Eymont via dovecot wrote: >> >>> I have Centos 7 with dovecot/postfix/mysql Maildir >>> >>> >>> I want to bring in a new server, new server will have same hostname as >>> current, but, different IP >>> >>> I was intending to >>> rsync -avzhe ssh vmail@oldserver:/var/vmail/vmail1 /var/vmail/vmail1 >>> >>> and, then, re run as necessary when/if mail still arrives on old server >>> >>> >>> is that "a good plan" ...? >>> >>> TIA, V >>> >>> >> Yeah, it's ok as long as you haven't switched to new server. > Aki, thanks > > I'm not certain I understand your comment properly > > I currently have server 'geko' > > intention was to change A record to assign geko to new IP/server, assign > new hostname to oldserver A record > > I guess I;ll still get some emails delivered to oldserver with new > hostname/old ip for 24 hours or so after aA record change ? > > so, I was going to re run rsync 2 or 3 times over the first 24 hours or so ? > > are you saying NOT to rsync once A record changed ? > > sorry for being slow > > You could configure old server's MTA to deliver mail to new server's MTA instead? After there has been activity on the new server, running rsync from old server can cause problems. Aki

2 1

Re: rsync /old/server new/server ?
by Voytek Eymont 08 Mar '19

08 Mar '19

On Fri, March 8, 2019 10:45 pm, Aki Tuomi via dovecot wrote: > > On 8.3.2019 13.44, Voytek Eymont via dovecot wrote: > >> I have Centos 7 with dovecot/postfix/mysql Maildir >> >> >> I want to bring in a new server, new server will have same hostname as >> current, but, different IP >> >> I was intending to >> rsync -avzhe ssh vmail@oldserver:/var/vmail/vmail1 /var/vmail/vmail1 >> >> and, then, re run as necessary when/if mail still arrives on old server >> >> >> is that "a good plan" ...? >> >> TIA, V >> >> > Yeah, it's ok as long as you haven't switched to new server. Aki, thanks I'm not certain I understand your comment properly I currently have server 'geko' intention was to change A record to assign geko to new IP/server, assign new hostname to oldserver A record I guess I;ll still get some emails delivered to oldserver with new hostname/old ip for 24 hours or so after aA record change ? so, I was going to re run rsync 2 or 3 times over the first 24 hours or so ? are you saying NOT to rsync once A record changed ? sorry for being slow (sorry for sending not to list...)

1 0