First of all, I would like to thank you all for your quick answers.
> I looked at both notmuch and mu4e before deciding on mu4e. The key thing I
> found missing from notmuch was how to reliably synchronise tags across
> different machines. This was a year ago (roughly), has that been solved
> yet?
In fact, I guess we should tags into two classes:
1. tags that we can compute from the content of a mail like
mailing_list, sent, rss, work_mail ...
2. tags that we cannot compute from the content of the mail like
read, replied, spam...
When wanting to synchronize mails between several computers, I like the
idea of using an outside IMAP server and use offlineimap to synchronize
it with a local maildir. In fact, I don't really know other ways to do
that. I will then try to sum up how to synchronize tags with the
offlineimap + IMAP server and the problem each solution brings.
Abdó mentioned also a way using a folder synchronization tool such as
unison to synchronize mails. This assumes the user has access to both
computer at the same time or that he uses a usb stick to store the
mails. For that reason, this method does not quite fit with my
situation.
The first category of tags does not really need to be stored into the
mail content because in am able to re create the tags from a new copy of
maildir. Then notmuch and mu can both do that very well.
To synchronize tags from the second part, there are several approaches:
1. insert the tag into the mail headers like mu does. This, however,
needs offlineimap to be patched to work.
2. use the dedicated maildir tags like T, S, F, D... Those are really
limited and a patch in offlineimap should be needed to synchronize
other letters (for instance W for spams) as well. This is described
here
http://lists.gnu.org/archive/html/info-gnus-english/2011-10/msg00052.html
3. use a maildir directory and have offlineimap synchronize those with
imap labels. This causes the mails to be duplicated for each tag it
possesses.
4. Patch offlineimap to make it create hardlinks of mails instead of
copy them.
None of these solutions seems to be perfect. 3 and 4 work with notmuch
and mu but 3 is definitively not good because there are too many
duplications of mails and 4 seems like difficult to implement. 1 work
out of the box with mu but it needs a patch to be applied to
offlineimap. In the case of 2, a monkey patch must be applied in
offlineimap and both notmuch and mu must also be patched to make it
work.
As a conclusion, there does not seem to be any solution out of the box
using mu or notmuch to easily and efficiently synchronize mails. 1 is a
bit easier with mu.
Is there any one with a fifth solution?
> Also, perhaps another thing I prefer is that you can easily follow and
> contribute to mu4e development, as Dirk is so responsive. By contrast,
> notmuch is a bigger project, and it has many people contributing, but that
> seems to entail lots of discussion on each patch, which makes it less
> interesting for the outsider to follow on the mailing list.
I totally agree with this one. I really like the responsiveness and
kindness of Dirk on the mailing list.
--
Konubinix