[Dovecot] Expunged message reappeared, giving a new UID

Timo Sirainen tss at iki.fi
Sun Sep 22 00:02:05 EEST 2013

On 8.8.2013, at 11.21, Simon Fraser <srf at sanger.ac.uk> wrote:

> I ran two tests: one using 'doveadm expunge' and one deleting the
> message using mutt. Since the hosts mentioned so far have a copy of my
> full mailbox on, I re-ran the tests (with the same results) on a test
> server with a fresh mailbox on, so there was no extra folder
> synchronisation in there to fill up the rawlog. 
> Those log entries are too big for the mailing list (70k+), so are here:
> 'doveadm expunge' dsync-rawlog node A
> http://pastebin.com/LtUnENPv
> 'doveadm expunge' dsync-rawlog node B
> http://pastebin.com/QaWLyZq2
> imap expunge dsync-rawlog node A
> http://pastebin.com/SuFdWn0w
> imap expunge dsync-rawlog node B
> http://pastebin.com/Ex66s7hq

I finally looked into this:

The A and B node logs are exactly the same. I think you sent the same ones for both? Anyway, one of the sides is enough. The interesting parts are:

1375808883.299424 O: NINBOX     y       0314c806e3fa0052d26a0000736ac1b0        1375795939      24
1375808883.350378 I: NINBOX     y       0314c806e3fa0052d26a0000736ac1b0        1375795939      23
1375808883.360216 I: Ce 22      6e2b7029b52c015258220000736ac1b0
1375808883.360972 O: Cs 23      ae42e400732d0152d3310000736ac1b0               59             1375808883                    20

One side has uidnext=23 and the other side has uidnext=24. You're deleting the last message with uid=22, so the uidnext=23 is correct. The other side however thinks that the same mail's uid is 23. There must be something wrong with the mail delivery, because both sides should have uid=22 and uidnext=23 here. So replication rawlogs of a new mail delivery would be helpful..

More information about the dovecot mailing list