Oswald, thanks for the detailed reply! Oswald Buddenhagen wrote:
> i think the overall best configuration is one with a "shadow" imap > server: an mbsync channel (partially) syncs the upstream with the > shadow, while the clients then sync only with the shadow. whether the > shadow runs on one of the clients or somewhere "in the cloud" is > irrelevant from a topological POV - an openwrt router with a usb stick > would be sufficient if it's all limited to one location. I think I can even do without a "shadow" server. The clients can simply continue to sync the active folders (those that still get new mail and are present on my mail provider's IMAP server) directly via that server. Once folders fell out of active use, I will delete them from the provider's server, and instead designate one of the clients (one that is always on) as the server for these folders. In this way modifications to old email (like moving or deleting messages) will propagate. There will be thus two separate sets of folders (active and old), with two different star topologies. This will require separate channels for active and old mail, but that's not a problem. > On Fri, Aug 11, 2017 at 04:42:01PM +0200, Christoph Groth wrote: > > Another question: what would happen if sometimes client1 (=slave) > > syncs with client2 (=master), and sometimes client2 (=slave) syncs > > with client1 (=master)? > > > that question makes "only limited sense", because it's way > under-specified. if you expose the clients to each other via NFS, it > will work just fine _if they use a shared sync state_. of course, you > need complementary configurations which are adjusted to the respective > "view". as before, each such channel may only ever connect the same > two stores. Thanks, it's clear. So it's definitely not a good idea to sync without a shared sync state. ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ isync-devel mailing list isync-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/isync-devel
