- dovecot - dovecot.org

Many Duplicated messages after migrate from 2.0.19 to 2.2.15
by Listas＠Adminlinux 15 May '15

15 May '15

Hi, In my company, we have several failover clusters (~50k accounts per cluster) with Ubuntu12.04 and Dovecot-2.0.19 (without dsync, replication at block level with DRBD). We are migrating to active/active clusters with Ubuntu14.04 and Dovecot-2.2.15 with replication via dovecot-dsync. Each new cluster consists of two machines and each machine runs two instances of Dovecot (one for backend and the other for proxy Dovecot-director). We did the migration of message files, indexes and sieve scripts using rsync to one of the backends. After we turn on the second backend and let the dsync work in replication for him. Now, many accounts are with duplicated messages and some new emails delivered are also being duplicated. Doveadm deduplicate doesn't work for me. I ran: doveadm deduplicate -u <user> -m ALL Does do the migration of files with rsync was a mistake ? We are using mdbox on both clusters. My confs with doveconf -n for both clusters: http://www.adminlinux.com.br/newcluster_doveconf.txt http://www.adminlinux.com.br/oldcluster_doveconf.txt Thanks and regards, Thiago Henrique

1 0

v2.2.18 released
by Timo Sirainen 15 May '15

15 May '15

http://dovecot.org/releases/2.2/dovecot-2.2.18.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.18.tar.gz.sig Oops, director was somewhat broken in 2.2.17. I thought I tested the last changes in it well enough, but looks like not. To avoid all existing Dovecot director installations from breaking I decided to make 2.2.18 release quickly afterwards.. BTW. We're planning on making some changes soon to how version control is used in Dovecot development, which should help avoid these kind of problems. The main problem now is that everything gets directly committed to the master branch (although we have a separate more stable dovecot-ee repo also). The new plan is to do something like this: http://nvie.com/posts/a-successful-git-branching-model/ Besides some minor compiling issues and other small changes, the important ones are: - director: Login UNIX sockets were normally detected as doveadm or director ring sockets, causing it to break in existing installations. - sdbox: When copying a mail in alt storage, place the destination to alt storage as well.

3 2

Best practice for getting sieve scripts replicated?
by Michael Grimm 15 May '15

15 May '15

Hi — I do have replication between two servers running, and mail is replicated without any issues. I do have sieve running at both servers without any issues. But replication of sieve scripts doesn't work as "expected": Whenever I do modify my default script und upload it via "doveadm sieve put -u abc -a default < default" it becomes uploaded to the home directory of user abc as expected, but it will not be replicated to the partner server. Whenever I do deactivate the default script by "doveadm sieve deactivate -u abc", followed by a deletion "doveadm sieve delete -u abc default" plus subsequent upload of the script "doveadm sieve put -u abc -a default < default", replication takes place instantly. Questions: Is a modification of a sieve script supposed to be triggered the latter way? Or am I doing it the wrong way? Thanks and regards, Michael

2 5

Alternate Storage altmove not working bug
by Daniel van Ham Colchete 15 May '15

15 May '15

Hello everyone! I would like to report a bug here. We are using dovecot's sdbox with alternate storage here. From time to time my SSD partition gets full and I always find users with lots of e-mails stuck there, and altmove just won't move them. It moves most of the e-mails correctly, but a few was getting stuck everyday. So, I think I have found the problem! When a user moves the message from one mailbox to another, the move will keep all the flags! Including MAIL_INDEX_MAIL_FLAG_BACKEND 0x40. So, altmove think this message was already moved and doesn't do anything. I did a doveadm dump on the destination mailbox's index and what I see is a lot of this: RECORD: seq=104, uid=104, flags=0x48 (Seen) - ext 0 keywords : (0000) - ext 1 modseq : 12 (0c00000000000000) - ext 3 cache : 14004 (b4360000) - cache offset=14004 size=76, prev_offset = 0 - mime.parts: (48000000b404000000000000cc04000000000000e542000000000000fd4300000000000018010000) (pos=0 hdr.p=1204 hdr.v=1228 body.p=17125 body.v=17405 flags=48) - size.physical: 18329 (9947000000000000) - date.received: 1418235366 (e68d8854) Although the 0x40 flag is set, the file still lives on the main/ssd storage area. My config: http://pastebin.com/8Wk4bfRK Dovecot version: 2.2.5-0~auto+22 Host is Xeon E3 64bit, running Debian 7. Filesystem is plain local ext4 on both storage areas I know my version is outdated but I didn't find anything related to this there. Just one last question: how can I remove that flag from the message? I have taken a look at doveadm-flags(1) but it doesn't seem to allow anything on that flag. Thank you very much! Best, Daniel Colchete

2 2

Return code 139 when enabling auth debugging
by Stefan Midjich 15 May '15

15 May '15

Hi I'm running dovecot 2.2.10 installed from base repos on CentOS 7. I'm trying to use sqlite as an auth backend but it's not working so I enabled some auth debugging settings in conf.d/10-logging.conf and then dovecot refused to start. sudo dovecot -F produced 139. Here is doveconf -n: http://dpaste.com/2BNB2F7 Unfortunately when I have these settings enabled doveconf does not work and only produces the first comment line. So here is the output of sudo grep -v '^#' /etc/dovecot/conf.d/10-logging.conf | grep -v '^$': http://dpaste.com/0G0VVK8 And when these settings are uncommented dovecot -F produces return code 139 and no output. So I'm having a hard time troubleshooting my authentication when I can't even troubleshoot my debug options not working. ;) -- Hälsningar / Greetings http://Stefan.Midjich.name

1 0

Re: [Dovecot] IMAP and POP3 operations log per user
by Steffen Kaiser 14 May '15

14 May '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thu, 14 May 2015, Jorge Bastos wrote: > I'd like to have a log per user, and protocol (imap+pop3), where this log > would tell me/save the message sender+subject+operation (deleted, marked to > expunge/other/was read/other). > Is there something similar to this that already exists? Check out the mail_log plugin. You'll have to break the logfiles by users via script. - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEVAwUBVVWSGHz1H7kL/d9rAQLIzAf/ZtNOLa1n12LnxwhMaS1B+6LEHDOCZWtw ldTarGE0uovu/OH84PEq4MkE5Y1Oww+VWmA+b2csBx1C0bZmcQeF2g7O65fESYsI Qu/xSuJLhOyUm4sppE62Zqyxba+rG2tyj9XpKMrHI6nU3ZTCOhVu/RJ2TB2WkhkB 21pgYEpkBYvRZK2PPqRwl+Lwc3oGQvWoYHcyniXL0v2P5tNNQj1gTuGVm53dPliM cFm9p4EjAOKEZyFgQokBljDpp03OMpEu16GT8XjCg8Fxg2BkF2XHBx/Wvv8DxQCC vyLA1SFMLNNRoizwF+xVlUJu4AW8fWBLhCgvOAFw4mFXkbMoi+lUwQ== =vRwJ -----END PGP SIGNATURE-----

1 0

Trying to get mail working
by Steve Matzura 14 May '15

14 May '15

I have charge of a very mixed system--current OS (Fedora 20--OK 21's out but I just haven't upgraded yet), current (or nearly so) Mailman (2.1.18-1), Postfix 2.10 with a configuration file sfrom something a lot older which I've run through the upgrade-configuration procedure, and old Dovecot (1.0.15). Is there anything I can do to test each of these components individually, then add a second component and test the three pairs, then all three together? I am nobody's definitioin of an expert in any of these three components, so am having a lot of trouble making them work together, so I thought maybe there might be some test procedure that might straighten me out. Thanks in advance.

2 1

[Dovecot] IMAP and POP3 operations log per user
by Jorge Bastos 14 May '15

14 May '15

Hi, I'd like to have a log per user, and protocol (imap+pop3), where this log would tell me/save the message sender+subject+operation (deleted, marked to expunge/other/was read/other). Is there something similar to this that already exists? If not is there something like this on the TODO/whishlist? Thanks in advanced, Jorge Bastos

1 0

v2.2.17 Segfault
by Adam Lackorzynski 14 May '15

14 May '15

Hi, I'm using libexec/dovecot/imap via a ssh tunnel. 2.2.17 segfaults while accessing a NULL pointer. The following change fixes it for me: --- dovecot-2.2.17/src/lib-imap/imap-keepalive.c 2015-05-03 11:12:11.000000000 +0200 +++ dovecot-2.2.17/src/lib-imap/imap-keepalive.c 2015-05-14 20:06:29.490617405 +0200 @@ -11,6 +11,8 @@ { unsigned int addr; + if (!ip) + return FALSE; if (ip->family == 0) return FALSE; if (ip->family == AF_INET) { Thanks, Adam -- Adam adam(a)os.inf.tu-dresden.de Lackorzynski http://os.inf.tu-dresden.de/~adam/

2 1

Pigeonhole v0.4.8.rc3 compilation error (bad mail-deliver.h)
by Jacques Distler 14 May '15

14 May '15

Got a /usr/local/include/dovecot/mail-deliver.h:30:17: error: field has incomplete type 'struct timeval' struct timeval delivery_time_started; ^ error. This is because mail-deliver.h in dovecot-2.2.17 is missing an #include <sys/time.h> Adding that line to mail-deliver.h fixes the problem. Oddly, I had no problem compiling dovecot itself.

2 1