From: Jeff Templon <templon@nikhef.nl>
To: "David Mazieres expires 2019-04-09 PDT"
<mazieres-228pybtsy8xg9tbtwegs2zvxea@temporary-address.scs.stanford.edu>,
"Dan Čermák" <dan.cermak@posteo.net>,
notmuch@notmuchmail.org
Subject: Re: How do you synchronize your notmuch tags across multiple machines?
Date: Wed, 09 Jan 2019 14:40:31 +0100 [thread overview]
Message-ID: <m21s5m7xv4.fsf@nikhef.nl> (raw)
In-Reply-To: <87tvii6xpt.fsf@ta.scs.stanford.edu>
Hi,
I too, am using muchsync to synchronize between two machine, I too have
profited from David's quick responses, and I too deal with the problem
of only being able to "fetch mail" on one machine.
I followed the discussion with interest.
Looking at the isync (mbsync) docs (I can't speak for offlineimap) it
might be easier: the state of the sync seems to be kept in little files
per Maildir subdirectory, called .mbsyncstate and .uivalidity. If
muchsync were to sync these files as well, then I think it would work.
See the explanation of the .mbsyncstate file in this thread:
https://sourceforge.net/p/isync/mailman/message/34682807/
quote: "mbsync maintains a mapping of remote (col 1) to local (col 2) uids.
when you migrate, you can just duplicate the columns."
He's talking about migrating a mail store from offlineimap to mbsync, I
guess the issues would be the same.
HTH,
JT
next prev parent reply other threads:[~2019-01-09 13:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-17 22:57 How do you synchronize your notmuch tags across multiple machines? Dan Čermák
2018-12-18 0:55 ` Ralph Seichter
2018-12-18 8:18 ` Tom Hirschowitz
2019-01-03 22:27 ` Dan Čermák
2019-01-03 22:48 ` Brian Sniffen
2019-01-04 13:43 ` Dan Čermák
2019-01-06 4:20 ` David Mazieres
2019-01-08 23:54 ` Dan Čermák
2019-01-09 8:29 ` David Mazieres
2019-01-09 13:40 ` Jeff Templon [this message]
2019-01-09 16:50 ` David Mazieres
2019-03-09 9:21 ` Dan Čermák
2019-01-12 22:45 ` jpellegrini
2019-01-14 23:00 ` Dan Čermák
2019-01-19 4:02 ` jpellegrini
2019-01-19 4:08 ` Jeronimo Pellegrini
2019-01-13 18:12 ` Ioan-Adrian Ratiu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m21s5m7xv4.fsf@nikhef.nl \
--to=templon@nikhef.nl \
--cc=dan.cermak@posteo.net \
--cc=mazieres-228pybtsy8xg9tbtwegs2zvxea@temporary-address.scs.stanford.edu \
--cc=notmuch@notmuchmail.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).