Duplicate mails on pop3 expunge with dsync replication on 2.2.35 (2.2.33.2 works)

Gerald Galster list+dovecot at gcore.biz
Fri Sep 21 14:47:36 EEST 2018


Hi Jan,

unfortunately no news on this topic after 6 months.

I understand this bug might not be a top priority but perhaps someone from the dovecot team can clarify if they will investigate eventually or if we're on our own.

Thanks,
Gerald




> Am 18.09.2018 um 23:20 schrieb Jan Münnich <jan at dotplex.com>:
> 
> Hi,
> 
> Has anyone any idea how to solve or further debug this issue? It seems indeed that it was introduced in 2.2.34 and is still there in 2.3.2.1. I found a couple of posts for this on the mailing list and elsewhere, but no solution:
> 
> When a message is retrieved and immediately expunged, it gets replicated back from the other dsync node. This usually happens with POP3 but with IMAP as well, when the MUA fetches the mail and the user opens and reads it immediately within seconds. It does not seem to happen when the message is retrieved and only expunged a while after, which is mostly the case with IMAP.
> 
> The bug occurs and is reproducible when the message is delivered to node A and then fetched by the client from node B. If the message is delivered to and fetched from the same node, the message does not get duplicated.
> 
> I'm attaching the debug logs from both nodes for a full example transaction. The message is delivered via lmtp to node A with UID 175261, fetched and deleted on node B and then appears again with the new UID 175262.
> 
> Thanks,
> Jan
> 
> 
> [...]



More information about the dovecot mailing list