> On 4 Sep 2018, at 18.45, Rick Romero <rick at havokmon.com> wrote: > https://imapsync.lamiral.info/FAQ.d/FAQ.Duplicates.txt > > Seems to use UIDs so that 'data' isn't lost. > >No it does not. This is different thing. This is about managing duplicates on multiple syncs. Imapsync seems to keep track of UID -> MAIL mapping for server A and UID -> MAIL mapping for server B so that on multiple runs it does not sync the same messages again. However it does not use the same UID -> MAIL for server B as is originally on server A. And that is the problem. Sami -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://dovecot.org/pipermail/dovecot/attachments/20180904/6e6d331d/attachment-0001.html>
Quoting Sami Ketola <sami.ketola at dovecot.fi>:>> On 4 Sep 2018, at 18.45, Rick Romero <rick at havokmon.com> wrote: >> >> https://imapsync.lamiral.info/FAQ.d/FAQ.Duplicates.txt >> >> Seems to use UIDs so that 'data' isn't lost. >> ? > > No it does not. This is different thing. This is about managing > duplicates on multiple syncs. Imapsync seems to keep track of UID > -> MAIL mapping for server A and UID -> MAIL mapping for server B so > that on multiple runs it does not sync the same messages again. > However it does not use the same UID -> MAIL for server B as is > originally on server A. And that is the problem.That's not what you said, you said there was a client sync issue.? That's definitely an issue (especially if you run Mac Mail). Ignoring duplicates on multiples runs is a non-issue, even with the 2011 version.? Recording UIDs is not necessary for that. Rick -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://dovecot.org/pipermail/dovecot/attachments/20180904/6c346a75/attachment.html>
> On 4 Sep 2018, at 19.32, Rick Romero <rick at havokmon.com> wrote: >> No it does not. This is different thing. This is about managing duplicates on multiple syncs. >> Imapsync seems to keep track of UID -> MAIL mapping for server A and UID -> MAIL mapping for server B so that on multiple runs it does not sync the same messages again. However it does not use the same UID -> MAIL for server B as is originally on server A. And that is the problem. > That's not what you said, you said there was a client sync issue. That's definitely an issue (especially if you run Mac Mail). > > Ignoring duplicates on multiples runs is a non-issue, even with the 2011 version. Recording UIDs is not necessary for that. >Nope. I said that with imapsync there is no way to preserve the same UID for a mail on the destination. Data is lost. If the UID -> MAIL pairs are not kept then client caches need to be invalidated and redownloaded. Sami -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://dovecot.org/pipermail/dovecot/attachments/20180904/497e6bc2/attachment.html>