mutt-wizard VS mutt

For other people interested in giving it a go, this script is quite good: https://github.com/LukeSmithxyz/mutt-wizard

Worth looking at LukeSmithxyz/mutt-wizard: A system for automatically configuring mutt and isync with a simple interface and safe passwords

i would just use luke smith's mutt wizard for neomutt.

mutt-wizard (https://github.com/LukeSmithxyz/mutt-wizard) helped me with the configuration a lot

If you use mutt-wizzard[1] to set up neomutt, you'll be up and running in no time.

Edit: typo

[1]: https://github.com/lukesmithxyz/mutt-wizard

I suggest you check out https://github.com/LukeSmithxyz/mutt-wizard and use that to set up your Gmail account.

While I think Thunderbird is bloated , I think is by far the best graphical email manager, specially if you use other than gmail accounts. I think besides Mailspring (which I did not try just because I found something for me needs) every other tool has some issue later (Geary , Claws Mail , Evolution ) specially if your email box has a big size (not even that big) . I just use this , which is basically neomutt on steroids and is basically the best email client I ever use.

Here is the link

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: