Mutt's downfall is it's designed around a single account. Most people have at least a personal and work email account, if not more. People also access their email through IMAP these days. Mutt has many config hacks to try and make it load multiple IMAP accounts, but a single failure to auth or connect will leave mutt completely frozen.
I have to use mutt to read and pull kernel patches, but I hate it. I would love a modern tui email client to rise from the ashes, but I doubt that will ever happen.
Mutt is not single account, mutt is account-agnostic. Dump your email to one mailbox or a thousand, and it'll process those according to your configuration setting(s).
It's possible to configure mutt to handle multiple accounts by:
- Dumping accounts to independent mailboxes and accessing through through specific mutt configurations.
- Dumping accounts to independent folders and Using folder-hook to set account-specific configurations.
- Performing other configurations based on reciepient and/or sender.
Not only that. It's still built around that ancient concept that users connect via TTYs to a single machine, and mail is actually moving mail locally to their /var/spool/mail/%u, no network involved.
In fact, this is also what all self-hosted email guides expect in Anno Fucking Domini 2022! I don't want to have to create system users just so they can have their mailboxes! Somebody tell those guys that such defaults are not sensible in this age.
when i switched to sup, it was a paradigm change in terms of interfaces compared to mutt. i can't say how well it works with imap though because i don't use that feature.
I have to use mutt to read and pull kernel patches, but I hate it. I would love a modern tui email client to rise from the ashes, but I doubt that will ever happen.