On Wed, Jan 07, 2026 at 06:17:08PM +0100, Sébastien Hinderer wrote: > Alejandro Colomar via Mutt-dev (2026/01/05 14:17 +0100): > > For a starter, I'd love to remove IMAP support, as that belongs in a > > separate tool (mbsync(1)). That would have removed most of the bugs > > I see reported in neomutt(1). A mail client should only talk SMTP, and > > mbox & maildir, IMHO. > > I'd really miss IMAP support.
Yeah, ditto, I use Mutt with local mbox / maildir for my personal stuff, but have used mutt with IMAP at a bunch of jobs. I haven't used neomutt (which is probably out of scope here anyway), but in general, Mutt's IMAP support works pretty well (esp. with header caching, which IIRC is all mainline now). POP3, maybe could make some better arguments in favor of removing, but _not_ having IMAP support in a mail client in 2026 seems less than ideal to me. Also, mutt already provides compile options to not include IMAP or POP support conditionally, so users or distributers can choose not to include that functionality if they prefer. /w
