Hi,
Thanks for your answer.
On Tue, 19 Apr 2022 at 14:17, Oswald Buddenhagen
<oswald.buddenha...@gmx.de> wrote:
> the classic star config (each device syncs from the server and
> notmuch'es independently) works fine, but that would leave the archive
> inaccessible from the laptop, except if you configure a separate channel
> for that.
If all the tags applied by notmuch are fully automatic, I agree it
just works. However, if you manually apply some tags, then the issue
pops up. :-)
Because you want to share these manually set of tags and the options
to do so are few: rsync or unison but it is usually inefficient (from
my experience) or muchsync but then the next sync with mbsync with the
server will duplicate, IIUC.
What do you mean by "configure a separate channel"?
> you could use an additional always-on device with an IMAP server as a
> proxy to "chain-sync" from. that device would hold the entire box
> including archive, and mbsync itself to the real server. your pcs would
> sync only from that device (whose imap port you'd have to make
> accessible from the outside, be it via port forwarding or a vpn). a
> raspberry pi or the home router itself (with custom firmware and an
> external hdd) should do.
Yes, it is what I was doing with my desktop (always-on device) but
some rules had changed. Unfortunately, I do not have the resources to
setup an additional always-on device.
Somehow, it would be useful to have something like, from laptop:
mbsync --merge desktop
would read ~/.mbsyncrc from laptop, connect (via SSH, say) to desktop
and read ~/.mbsyncrc from desktop; then update all .mbsyncstate and
.uidvalidity accordingly.
Thanks again.
Cheers,
simon
_______________________________________________
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel
