On Mon, Dec 13, 2021 at 12:34:38PM -0500, H wrote:
Perhaps I should have a second script that syncs my upstream mailbox
to local storage, ie also deletes anything locally that is no longer
found upstream?
in simpler terms, one regular working clone, and one full backup.
The drawback is that I would end up with a lot of duplicated stuff.
with both clones on one partition (which is reasonable if you keep a
proper backup of if), using a modern CoW file system like btrfs or zfs,
you'd have transparent data de-duplication. or you can simulate that by
hard-linking the duplicated messages (i suppose there are tools to
automate that).
a completely different approach would be never propagating deletions,
only "moves out of view". basically, you'd move messages to a trash
folder, which mbsync would sync, with the option of not actually having
a local copy of that trash folder. if, otoh, it saw a real deletion, it
would raise an alarm.
there are just two problems with that idea:
- mbsync currently can't do that
- it wouldn't be bullet-proof, as you could still accidentally move
messages to the trash. this would be a problem regardless of what
"tagging" system you use - you'd need an AI to detect that something
is out of the ordinary and raise an alert.
_______________________________________________
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel
