February 2019 - dovecot

imapsieve: script not triggered
by Andreas Krischer 24 Mar '19

24 Mar '19

Hi, folks! My problem: I set up dovecot with imapsieve to execute a script whenever a user copies a mail to his Spam folder (spam autolearning). Unfortunately this script is never executed regardless what I’m configuring for imapsieve. It looks like dovecot doesn’t really load the plugin… The "dovecot -n" output is attached. I already tried setting imapsieve_mailbox1_name to *, but even this does not execute the script… Also I tried a mailbox without mail_crypt enabled, no success as well. In the attached mail.log (mail_debug=yes) you can see, that imap_sieve_plugin is loaded, but it isn’t really executed. The normal (LMTP) sieve is working - if a mail is incoming the sieve module shows it work in mail.log: May 7 17:54:04 dovecot dovecot: lmtp(postmaster(a)myhost.name): Debug: YEm9ILyS8FqSaAAAujt/SA: sieve: file storage: Storage path `/var/vmail/myhost.name/postmaster/sieve' not found May 7 17:54:04 dovecot dovecot: lmtp(postmaster(a)myhost.name): Debug: YEm9ILyS8FqSaAAAujt/SA: sieve: file storage: Storage path `/var/vmail/myhost.name/postmaster/.dovecot.sieve' not found May 7 17:54:04 dovecot dovecot: lmtp(postmaster(a)myhost.name): Debug: YEm9ILyS8FqSaAAAujt/SA: sieve: storage: No default script location configured May 7 17:54:04 dovecot dovecot: lmtp(postmaster(a)myhost.name): Debug: YEm9ILyS8FqSaAAAujt/SA: sieve: User has no personal script May 7 17:54:04 dovecot dovecot: lmtp(postmaster(a)myhost.name): Debug: YEm9ILyS8FqSaAAAujt/SA: sieve: file storage: Using script storage path: /etc/dovecot/sieve/after/ May 7 17:54:04 dovecot dovecot: lmtp(postmaster(a)myhost.name): Debug: YEm9ILyS8FqSaAAAujt/SA: sieve: file script: Opened script `spam' from `/etc/dovecot/sieve/after/spam.sieve' May 7 17:54:04 dovecot dovecot: lmtp(postmaster(a)myhost.name): Debug: YEm9ILyS8FqSaAAAujt/SA: sieve: executed after user's Sieve script(1): /etc/dovecot/sieve/after/spam.sieve May 7 17:54:04 dovecot dovecot: lmtp(postmaster(a)myhost.name): Debug: Mailbox <lmtp DATA>: Opened mail UID=1 because: header Message-ID (Cache file is unusable) May 7 17:54:04 dovecot dovecot: lmtp(postmaster(a)myhost.name): Debug: YEm9ILyS8FqSaAAAujt/SA: sieve: Opening script 1 of 1 from `/etc/dovecot/sieve/after/spam.sieve' May 7 17:54:04 dovecot dovecot: lmtp(postmaster(a)myhost.name): Debug: YEm9ILyS8FqSaAAAujt/SA: sieve: Loading script /etc/dovecot/sieve/after/spam.sieve May 7 17:54:04 dovecot dovecot: lmtp(postmaster(a)myhost.name): Debug: YEm9ILyS8FqSaAAAujt/SA: sieve: Script binary /etc/dovecot/sieve/after/spam.svbin successfully loaded May 7 17:54:04 dovecot dovecot: lmtp(postmaster(a)myhost.name): Debug: YEm9ILyS8FqSaAAAujt/SA: sieve: binary save: not saving binary /etc/dovecot/sieve/after/spam.svbin, because it is already stored May 7 17:54:04 dovecot dovecot: lmtp(postmaster(a)myhost.name): Debug: YEm9ILyS8FqSaAAAujt/SA: sieve: Executing script from `/etc/dovecot/sieve/after/spam.svbin' I already spent hours on this problem so please let me know if you have any idea what the problem could be… :( Thanks in advance! Andreas

3 4

dovecot/config processes one more time - which are safe to kill?
by Arkadiusz Miśkiewicz 14 Mar '19

14 Mar '19

Hello. The problem with dovecot/config processes never ending and spawning new one on each reload (https://www.dovecot.org/list/dovecot/2016-November/106058.html) is becoming a problem here: # ps aux|grep dovecot/config|wc -l 206 That's a lot of wasted memory - dovecot/config processes ate over 30GB of ram on 64GB box. Before killing dovecot/config processes: # free -m total used free shared buff/cache available Mem: 64437 61656 483 0 2297 after: # free -m total used free shared buff/cache available Mem: 64437 23676 37822 0 2939 Currently on dovecot 2.3.3. I guess it's very low priority to handle that, so: how can I figure out which dovecot/config processes are safe to be killed by external script? Does "all beside 2 newest ones" rule look sane? Thanks, -- Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org )

3 5

replication dropped imap flags
by Patrick Cernko 14 Mar '19

14 Mar '19

Hi list, I think, I found a bug in the replication setup, that drops (custom) flags like Thunderbird labels. I have set up a simple 2 node setup to reproduce and explain it: Host adove.mpi-klsb.mpg.de and bdove.mpi-klsb.mpg.de (doveconf -n attached) have dovecot-imapd (from repo.dovecot.org) installed on an ext4 filesystem. They only have one account "test" via /etc/dovecot/userdb ("test:testpassword:::Test User::/bin/bash:"). It's mailbox contains one message, that is flagged with "$label1": doveadm -f flow fetch -u test 'guid flags' ALL guid=d1516a2b5c08fc5b541d00005a350039 flags=\Recent $label1 Now I simulate a node reinstall on adove by uninstalling dovecot, removing all remnants, reinstalling and configuring it again: apt purge dovecot-core dovecot-imapd rm -rf /var/vmail /var/lib/dovecot /etc/dovecot apt install dovecot-imapd # disable system auth : > /etc/dovecot/conf.d/auth-system.conf.ext # create /var/vmail install -d -o nobody -g nogroup -m 700 /var/vmail # create userdb echo 'test:testpassword:::Test User::/bin/bash:' > /etc/dovecot/userdb # create /etc/dovecot/local.conf # not described here, the resulting doveconf -n is attached! service dovecot restart When I check the flags of the mail of user test now, the "$label1" is disapeared on both machines, even after "doveadm replicator replicate -f test": doveadm -f flow fetch -u test 'guid flags' ALL guid=d1516a2b5c08fc5b541d00005a350039 flags=\Recent Any hints what I am doing wrong here or is this really a bug? Best, -- Patrick Cernko <pcernko(a)mpi-klsb.mpg.de> +49 681 9325 5815 Joint Administration: Information Services and Technology Max-Planck-Institute fuer Informatik & Softwaresysteme

1 2

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

12 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 12 Mar '19

12 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 12 Mar '19

12 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 12 Mar '19

12 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 12 Mar '19

12 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

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

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