Forcing replication - difference is a 0x0D 0x0D 0xA sequence?

[Arnold Hendriks]

I've found a few mailboxes on my system that were being replicated where
the mailboxes are not in sync.

On server 1 I see:

dovecot1:/# doveadm fetch -u s0000000 "size.physical size.virtual"
mailbox-guid c92f64f79f0d1ed01e6d5b314f04886c uid 115
size.physical: 1815
size.virtual: 1843

On server 2 I see:

dovecot2:/# doveadm fetch -u s0000000 "size.physical size.virtual"
mailbox-guid c92f64f79f0d1ed01e6d5b314f04886c uid 115
size.physical: 1805
size.virtual: 1833

Running ' doveadm replicator replicate -f s0000000 "*" ' does not fix the
issue.

I've compared the mails and the difference appears to be that the primary
server (where the mail comes in) has a few occurences of "0D 0D 0A" (hex)
which on the replicated server looks like "0D 0A". (ie, \r\r\n was
replicated as \r\n ?)

Is there a way to force these two messages to be in sync again ?

Is the \r\r\n being replicated as \r\n a known issue ?

(I'm not sure if I could replicate this, this message dates back to 2007 so
probably wasn't even received originally on this server. Replication was
configured much later than 2007)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://dovecot.org/pipermail/dovecot/attachments/20210715/5a7b93e8/attachment-0001.html>