mu VS mutt

I like mu4e (https://github.com/djcb/mu) for reading emails. You'll need to run mu init [email protected] (append as many --my-address entries as email addresses you receive mail at) in your Maildir and mu4e should start reading it.

For all details, see https://github.com/djcb/mu/blob/release/1.10/NEWS.org (and I'd recommend

And djcb already fixed it: https://github.com/djcb/mu/issues/2420 !

I've tried to follow the release notes here, but find it hard to follow... for instance, the releases jump from 1.4.15 to 1.6.0? (So where is 1.5.5?) Is there a compilation of all these changes from e.g. ~ to -- and other general refactoring?

> Surely there is a space for minimalist office suites and email clients,

FWIW, my email life improved massively when I left the likes of Thunderbird and KMail behind for the simplicity of mu/mu4e [1]. I hear similarly stellar things about Notmuch [2]. I'm never going back to an email client that even thinks about itself in relation to "office suites".

[1] https://www.djcbsoftware.nl/code/mu/

[2] https://notmuchmail.org/

and maildir-utils to index for search, https://www.djcbsoftware.nl/code/mu/

Mutt supports OAuth now as well, which lets you eliminate the need for the app-specific passwords. https://gitlab.com/muttmua/mutt/-/blob/master/contrib/mutt_oauth2.py.README

mutt: https://gitlab.com/muttmua/mutt

Another option is https://gitlab.com/muttmua/mutt/-/blob/master/contrib/mutt_oauth2.py , which has support for GPG-based storage of the secrets, and can do the token re-negotiation on demand, as well.

Thunderbird is an example of a client that implements Oauth2 for these protocols. Claws Mail and Mutt (command line) do as well.

For those of us with Unix-y mail setups the move to OAuth2 can be a bit tricky, but there are now several different programs to help (spurred, I suspect in no small part, by Microsoft/Exchange's stance). The ones I know about are:

Email OAuth 2.0 Proxy <https://github.com/simonrob/email-oauth2-proxy>; mailctl <https://github.com/pdobsan/mailctl>; mutt_oauth2.py <https://gitlab.com/muttmua/mutt/-/blob/master/contrib/mutt_o...> (some suggestion that it might not always work these days?); pizauth <https://github.com/ltratt/pizauth>; oauth-helper-office-365 <https://github.com/ahrex/oauth-helper-office-365>. Disclaimer: I wrote pizauth and it's just about to move into the alpha stage.

You could fix that by contributing since it's open-source and GPL-licenced.

https://gitlab.com/muttmua/mutt

I feel like I had this working in Evolution once?

In reality I found that 99% of the time I only use aliases like yours for receiving email. On the one day a month I need to send from [email protected], I just sack up and add it as an account alias. Le sigh.

Of course, mutt does this right:

https://gitlab.com/muttmua/mutt/-/wikis/MuttFaq/Header#how-t...

But building mutt from source is straightforward, although it has an abundance of options. Below I configure for IMAP, SSL, and a local executable (if left blank, the default is /usr/local; you could also choose /opt, but in these cases the make install must be done as sudo. Also, IIRC mutt looks for elinks, as well as xsltproc and/or lynx to install its documentation (see this discussion for details), although the program itself will still work.

The trick seems to be caching mail headers, https://gitlab.com/muttmua/mutt/-/wikis/MuttGuide/Caching

Also if you change folders frequently you can put: