Now I'm wondering which of these extensions and strategies are employed by mainstream mail clients like Thunderbird, Apple Mail and Outlook?
I'm currently doing remote work from a location with an instable connection. Naturally I expected mails to work well in an async fashion, but instead... everything is really janky and I'm always unsure whether actions like moving an mail to a different actually 'went through' without loosing any mails.
Now I'm wondering which of these extensions and strategies are employed by mainstream mail clients like Thunderbird, Apple Mail and Outlook?
I'm currently doing remote work from a location with an instable connection. Naturally I expected mails to work well in an async fashion, but instead... everything is really janky and I'm always unsure whether actions like moving an mail to a different actually 'went through' without loosing any mails.
Looks great! Curious what the author and others use for local maildir email reading.
I use isync and notmuch! With aerc as my reader.
mu4e, but I suspect that a local maildir is a poor choice anyway.
It's better to have a local cyrus running and connect to it by imap, with, say, gnus.
Well, it says its bidirectional, so perhaps you could run two instances pointed at the same local maildir, but at different IMAP servers?
You can do the same with a local cyrus.
[dead]
Seems like a clone of https://gitlab.com/Lockywolf/imap-idle-mail-checker/
The README for that project mentions IDLE, but not CONDSTORE.
So what happens if you lose your connection to the server? How do you get up to date with the current state?
mbsync does it.
It's separation of concerns, the monitor only checks that something has changed, while mbsync does the synchronisation.