Hi,
I've been using mbsync with mu4e, and it's been sort of working for me, but I
wanted to share one thing that caused me headache : Inbox.
When reading the doc, it was never clear to me why and how one should use the
Inbox configuration parameter. Consider a mbsyncrc with this:
MaildirStore mymailstore-Local
Inbox ~/mbimaps/mymailstore/
Path ~/mbimaps/mymailstore/
SubFolders Verbatim
with, in this case, a IMAP/Gmail Master. Then, when synchronising, I see mails
from my inbox appear under mymailstore/{cur,new}
Now one error I made, and won't do again, was to think that I could "mbsync
mymailstore:Inbox" to sync only my inbox... That does not work ! Instead it
makes a new directory mymailstore/Inbox with its own {cur,new} subdirs... with
the same content as INBOX. I guess the IMAP server tries to be smart here ?
What I can do, however, is call "mbsync mymailstore:INBOX", which correctly
updates mymailstore/{cur,new}.
In particular, it seems to be a very bad idea to set Inbox to
~/mbimaps/mymailstore/Inbox (which is what I had done at first), because that
somehow associates both INBOX and Inbox to the same Maildir
(~/mbimaps/mymailstore/Inbox) and leads to a lot of pain.
I hope my experience will avoid someone else some pain in setting up their
config files and I welcome any comment on my current setup.
FWIW I'm about to try (once again) to download a few gigabytes of emails from
my main account, crossing my fingers that nothing gets messed up this time.
Nicolas.
------------------------------------------------------------------------------
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
