On Mon, Dec 13, 2021 at 06:21:51PM +0000, Sabahattin Gucukoglu wrote:
One-way (possibly stateless) sync, [...]
i'm not sure which of the named behaviors you consider requirements, and
which just happen to be things imapsync does, so here are three ways to
do it *somehow* with isync:
the most direct way is just a single channel that connects two imap
stores. there is no local copy in that case, but that seems unnecessary
anyway - you can just inspect the result on the target server with any
interactive imap client.
the second way introduces a local maildir store. the first channel pulls
from the first server to the local store, the second pushes from the
local store to the second server. obviously, at least one of the
channels *must not* use 'SyncState *', or hell breaks loose.
both of these solutions don't "clean up" the source - synchronization
(rather than fetching) is the very nature of isync.
if you want (optional) source deletion, then you get a classical use
case for fetchmail: fetch into a local store, and then use isync to push
that up to the second server. this is a two-step process, but it's free
from races. it may not be beautiful, but it does the job, and it doesn't
require turning isync into something it's not, by design.
_______________________________________________
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel
