April 2020 - dovecot - dovecot.org

doveadm replicator command
by Ivo 09 Apr '20

09 Apr '20

Can someone please explain to me what do commands "doveadm replicator add" and "doveadm replicator remove" really do. According to https://wiki.dovecot.org/Tools/Doveadm/Replicator they "Add the specified user(s) to the replicator." and "Remove the specified user from replicator.". Do they really do that? Since the default list of users for replication comes from doveadm user '*' (https://wiki.dovecot.org/Replication) I tried removing one user (e.g. xyz) from replication by using "doveadm replicator remove xyz" and it didn't work. Namely, after entering that command the only thing that I noticed is that "doveadm replicator status xyz" does not return any information. BUT, as soon as one mail arrives for that user "doveadm replicator status xyz" displays valid information and mail is replicated. Thanks in advance for any reply. # dovecot --version 2.2.33.2 (d6601f4ec)

1 0

doveadm backup into IMAP folder
by Gionatan Danti 09 Apr '20

09 Apr '20

Hi all, I am migrating a number of account from an old domain to a new one. I would like to store all imported email from the old domain under a specific IMAP folder. For example, if having test(a)domain.old, I would like to import all old email to test(a)domain.new/fromold. While I succeeded using doveadm backup / dsync to successfully replicate the old mailbox to the new one, I am unable to store all imported mail under a specific folder. So, I have some questions: - can the above be done? - if yes, can you confirm that email outside the specific destination folder will not be touched/deleted/whatever by doveadm backup? - does a "dry-run" option exists for doveadm backup / dsync? Thank you all. -- Danti Gionatan Supporto Tecnico Assyoma S.r.l. - www.assyoma.it [1] email: g.danti(a)assyoma.it - info(a)assyoma.it GPG public key ID: FF5F32A8

2 1

alternatives for imapproxy
by Maciej Milaszewski 08 Apr '20

08 Apr '20

Hi System debian 8.11 and dovecot-2.2.36.4 My webmail is roundcube with imapproxy. I have one problem. My dovecot servers is are in a cluster with keepalived like: dovecot1----VIP-IP--------dovecot2 All works fine I have a problem with imapproxy when a server dovecot1 had a problem (kernel panic sic!) Keepalived works perfecty and moved VIP to dovecot2 - all works fine for normal users but imapproxy gave a timeout and webmail clinet cannot connect what do you recommend alternative to imapproxy ? I use imapproxy because is fast ...

2 2

Warning: Failed to do incremental sync
by Laura Smith 08 Apr '20

08 Apr '20

Setup dovecot sync along the lines of (https://wiki2.dovecot.org/Replication) I am doing one way replication. The initial full replication happened without issue, but now I'm seeing these errors on the slave server: doveadm: Warning: /data/mail/foo/bar/Maildir/dovecot-uidlist: Duplicate file entry at line 26397: 1562173159.M215923P17350.mxp,S=2290,W=2339 (uid 143128 -> 143142) Warning: Failed to do incremental sync for mailbox Sent Messages, retry with a full sync (Modseq 1766 no longer in transaction log (highest=17617, last_common_uid=17559, nextuid=17560)) Warning: Failed to do incremental sync for mailbox INBOX, retry with a full sync (Modseq 2540 no longer in transaction log (highest=13870, last_common_uid=19912, nextuid=19913)) I guess dovecot automatically tries a full replication because eventually the messages get pushed and "sync failed" status changes from 'y' to '-'

2 1

Dovecot "User-Agent" equivalent
by Plutocrat 08 Apr '20

08 Apr '20

Hi, I was trying to debug an IMAP connection problem. The client accesses an account via webmail, mobile phone, and desktop. I was wondering if there was a way of determining which of these they were using at a given time. My googling turned up the following settings in the imap{} section: protocol imap { imap_id_log = * imap_id_send = "name" * "version" * } ... but setting these didn't seem to log any more information that I could use. Have I misunderstood the usage of these settings? Shouldn't they log a "user agent" type information in /var/log/dovecot.log ? Or are there any other ways I can get information on the client? P.

1 0

\Noselect missing after deleting mailbox
by Onno Molenkamp 07 Apr '20

07 Apr '20

Hi, With mailbox_list_index enabled (which is the default), Dovecot won't return \Noselect when LISTing a mailbox that was deleted but still has subordinate mailboxes. Before creating such a mailbox in the first place, it does return \Noselect. 1 LIST "" Test 1 OK List completed (0.002 + 0.000 + 0.001 secs). 2 CREATE Test/Test 2 OK Create completed (0.014 + 0.000 + 0.014 secs). 3 LIST "" Test * LIST (\Noselect \HasChildren) "/" Test 3 OK List completed (0.001 + 0.000 secs). 4 CREATE Test 4 OK Create completed (0.006 + 0.000 + 0.005 secs). 5 LIST "" Test * LIST (\HasChildren) "/" Test 5 OK List completed (0.001 + 0.000 secs). 6 DELETE Test 6 OK Delete completed (0.011 + 0.000 + 0.011 secs). 7 LIST "" Test * LIST (\HasChildren) "/" Test 7 OK List completed (0.001 + 0.000 secs). Like response 3, response 7 should contain \Noselect. (and it does, when mailbox_list_index is disabled) It looks like Dovecot isn't updating dovecot.list.index properly when deleting such a mailbox. Forcing Dovecot to rebuild the index by deleting dovecot.list.index* will cause \Noselect to re-appear in responses. Onno

1 0

Query change mdbox_rotate_size & mdbox_rotate_interval after sometime
by Durga Prasad Malyala 06 Apr '20

06 Apr '20

Hello All, If I change the mdbox_rotate_size to 100 MB & mdbox_rotate_interval to say 3 days after a year of usage what would be the impact on existing mails and new mails? Thanks/DP

1 1

replication and spam removal ("doveadm expunge")
by Olaf Hopp 06 Apr '20

06 Apr '20

Hello everybody, since now I did no replication and spam is delivered into users folder "spambox" Every night there is a cronjob which deletes spam older than 30 days via something like "find .... -ctime +30 -delete" Now I'm going to set up replication (two way) and I thought that doing "rm" is not a good idea. So I modified the job to something like /usr/bin/doveadm expunge -u test1 mailbox INBOX.spambox BEFORE 30d which works like intended, but I see that on the replication partner the spam isn't deleted. Even if I do a doveadm force-resync -u test1 '*' or log in via imap to the replication partner I still see the old spam. So my question is: is this the intended behaviour and I have to run the "doveadm expunge" on both replication partners or should the deletion via "expunge" being replicated to the partner and I have a misconfiguration or maybe I hit a bug ? Regards, Olaf /etc/dovecot/conf.d/12-replication.conf: mail_plugins = $mail_plugins notify replication service aggregator { fifo_listener replication-notify-fifo { mode = 0666 } unix_listener replication-notify { mode = 0666 } } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { mode = 0666 } } service doveadm { inet_listener { port = 1109 } } doveadm_password = XXXXX plugin { mail_replica = tcp:X.Y.Z.X:1109 } -- Karlsruher Institut für Technologie (KIT) ATIS - Abt. Technische Infrastruktur, Fakultät für Informatik Dipl.-Geophys. Olaf Hopp - Leitung IT-Dienste - Am Fasanengarten 5, Gebäude 50.34, Raum 009 76131 Karlsruhe Telefon: +49 721 608-43973 Fax: +49 721 608-46699 E-Mail: Olaf.Hopp(a)kit.edu www.atis.informatik.kit.edu www.kit.edu KIT - Die Forschungsuniversität in der Helmholtz-Gemeinschaft Das KIT ist seit 2010 als familiengerechte Hochschule zertifiziert.

2 4

net_connect_unix(imap) failed
by Philipp Ewald 06 Apr '20

06 Apr '20

Hello everyone, we have a huge problem with dovecot and IMAP connections. we got the following errors: 39665 today dovecot: imap-login: Error: master(imap): net_connect_unix(imap) failed: Resource temporarily unavailable - http://wiki2.dovecot.org/SocketUnavailable (client-pid=29066, client-id=1755, rip=IP, created 562 msecs ago, received 0/4 bytes) we thinks this may be a problem with authorization take too long? Authorization is not local and with SQL. i found the following in source code of Dovecot: #define SOCKET_CONNECT_RETRY_MSECS 500 #define SOCKET_CONNECT_RETRY_WARNING_INTERVAL_SECS 2 [...] i_error("master(%s): %s (client-pid=%u, client-id=%u, rip=%s, created %u msecs ago, received %u/%zu bytes)", This is no process limit problem: ps auxf | grep -c "[d]ovecot/imap$" 688 ps auxf | grep -c "[d]ovecot/imap-login$" 100 cat /proc/`pidof dovecot`/limits Limit Soft Limit Hard Limit Units Max cpu time unlimited unlimited seconds Max file size unlimited unlimited bytes Max data size unlimited unlimited bytes Max stack size 8388608 unlimited bytes Max core file size 0 unlimited bytes Max resident set unlimited unlimited bytes Max processes 64053 64053 processes Max open files 65535 65535 files Max locked memory 65536 65536 bytes Max address space unlimited unlimited bytes Max file locks unlimited unlimited locks Max pending signals 64053 64053 signals Max msgqueue size 819200 819200 bytes Max nice priority 0 0 Max realtime priority 0 0 Max realtime timeout unlimited unlimited us ulimit -n 1024 dovecot --version 2.3.4.1 (f79e8e7e4) protocols = imap pop3 service imap-login { process_min_avail = 4 service_count = 0 } service imap { process_limit = 4096 } service pop3-login { process_min_avail = 4 service_count = 0 } service pop3 { process_limit = 4096 } Can someone explain why we got this error and how to fix? If you need another information please tell me. -- Philipp Ewald Administrator DigiOnline GmbH, Probsteigasse 15 - 19, 50670 Köln E-Mail: philipp.ewald(a)digionline.de Web: www.digionline.de, www.webweaver.de AG Köln HRB 27711, St.-Nr. 5215 5811 0640 Geschäftsführer: Werner Grafenhain Informationen zum Datenschutz: www.digionline.de/ds

2 2

Panic due to assertion failure
by Bert JW Regeer 06 Apr '20

06 Apr '20

Hey all, I continue to receive the following messages every so often: dovecot[93817]: imap(xistence(a)0x58.com)<39982><>: Panic: file mail-storage.c: line 2122 (mailbox_get_open_status): assertion failed: (box->opened) dovecot[93817]: imap(xistence(a)0x58.com)<39982><>: Fatal: master: service(imap): child 39982 killed with signal 6 (core not dumped - https://dovecot.org/bugreport.html#coredumps) Even with core dumps enabled I haven't been able to get good information. I'm using FreeBSD and have installed dovecot from the pkg repositories dovecot-2.3.9.3 Is the package I have installed. (I just noticed there is an update available, so I'll upgrade, but this has been happening for a long time now, across multiple versions). What I was wondering, is there a way to rebuild all files that dovecot uses, indexes/caches/everything. Is there a doveadm command I can use for this? Bert JW Regeer

2 2