On Wed, Dec 1, 2021 at 5:00 PM Oswald Buddenhagen <oswald.buddenha...@gmx.de> wrote:
> On Wed, Dec 01, 2021 at 12:54:33PM -0500, Peng Bai via isync-devel wrote: > >I'm a bit confused how this will work. Please see the description of my > >workflow above. My setup may be a bit weird as I'm working with mails on > >the far side and the near side is a backup that only mbsync touches. > >Information only propagates from far -> near. > > > right, sorry, i misread. > > what you want is currently not supported. i could make it work for > maildir and servers that support the UIDPLUS extension (which, by now, > includes even ms exchange). it's a somewhat different mode of operation, > so i wonder how to make it fit best with what is already there. "Expunge > NearMirror" for your use case comes to mind. proposals for better > keywords or completely different options are welcome. > > That would be fantastic! If I understand the semantics of the new keyword correctly, it will sync the `\Deleted` flag for messages that have this flag on the far side and delete and expunge messages that have disappeared from the far side, essentially mirroring from far -> near. Is this correct? I think the keyword makes perfect sense for this behavior. On the other hand, a filter mechanism for flags to avoid syncing certain flags seems to be another flexible, general purpose solution (e.g., something like what I was proposing earlier: `SkipFlags Deleted`). Separately, is it possible to re-sync messages from far -> near (under new UIDs on the near side) for messages that have been deleted and expunged on the near side, say as part of a ReNew operation? This is regarding the last step of my workflow, since damages have already been done and it would be nice not to have to re-sync the whole mailbox (~10^5 messages...) 1) messages were pulled from far -> near; 2) some of these messages were marked `\Deleted` on the far side; **3) the `\Deleted` flags were pulled from far -> near and the corresponding messages expunged on the near side (because of `Sync Pull` and `Expunge Near`); **4) the `\Deleted` flags were removed from the far side (warnings appeared at this point); 5) the state file were hacked to change to `MaxPulledUid 0` in the hope that mbsync will re-sync the now expunged messages, but this didn't happen -- is there a way to achieve this at present? > > _______________________________________________ > isync-devel mailing list > isync-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/isync-devel >
_______________________________________________ isync-devel mailing list isync-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/isync-devel
