Hmmm, as far as I can tell the reason that only one machine should sync is that 
the file names for the mail files are not preserved by muchsync. This causes 
issues with mbsync as it uses the filename to store the UID.

So it seems that simply preserving the file names (either directly through 
muchsync or in a post-processing pass after running muchsync) should fix this? 
Or am I missing something?

Cheers,

Lars


On Tue, 18 Feb 2025 08:58:08 +0100, Alan Schmitt <alan.schmitt@polytechnique.org> wrote:
> Hello Lars,
> 
> On 2025-02-17 08:58, Lars Kotthoff <lists@larsko.org> writes:
> 
> > I use muchsync (https://www.muchsync.org/), which also copies the mail files. 
> > Works great.
> 
> Thank you for the suggestion. I did considered muchsync, but I ruled
> against it for two reasons. First, it is an extra program that is not
> packaged on my system (macos) so I need to compile it (I agree it is a
> small reason and I could attempt it, but my previous experience with
> compiling things on the mac was not great). Second, and more
> importantly, it seems that muchsync has to copy the mail files, so only
> one machine should fetch mail. This is a showstopper for me, and looking
> at previous discussion about it
> (https://yhetil.org/notmuch/87mup3bqmh.fsf@ra.horus-it.com/t/) did not
> help.
> 
> I guess I should just bite the bullet, make copious backups and play
> with notmuch-git. I’m wondering if others are currently using it.
> 
> Best,
> 
> Alan
> 
_______________________________________________
notmuch mailing list -- notmuch@notmuchmail.org
To unsubscribe send an email to notmuch-leave@notmuchmail.org