[sigil]

> I often receive emails with attached images or HTML code.

Here's my ~/.mailcap file:

    text/html; w3m -T text/html
    image/gif; gm display -
    image/jpg; gm display -
    image/eps; gm display -
    application/postscript; gm display -
    application/pdf; evince /dev/stdin

In mutt's pager view (reading a message), hit "v" to see all the mime parts, j and k to select one, and enter to view it with the associated mailcap command. In my mailcap I'm popping up images in GraphicsMagick, and viewing rendered html pages in w3m. Pretty rare for me when that doesn't cut it -- most mail has a readable plaintext part or a w3m-readable html part.

> Maybe some Mutt user can share with me some of the reasons why they like it so much?

It lets me fully reside in "the world of text:"

- I can compose emails in my text editor (vim, like you) instead of a crappy textarea.

- Mutt feels much faster than gmail and other gui mail clients. The keyboard shortcuts are amazing.

- I can use tmux's activity monitor feature as a text-based growl notification for new mail.

- All my mail (300k+ messages over 10+ years) is available locally, offline, in Maildirs. It's searchable and pliable by the unix toolset, enabling all kinds of fun things like [1]. I use and recommend offlineimap.

- Control. Mutt has changed conservatively over the years. You can configure it to your liking, and be reasonably certain it will continue working to your liking. No "New Compose" crap here. Tools like mutt are a great long haul investment.

One thing I find seriously lacking with mutt: the folder-centric message index (instead of tag-centric or search-centric index). You can get by okay with mutt's searching and limiting, but if you're jumping between folders often, it kinda sucks. Reminds me, I need to revisit mutt-kz.

[1] https://twitter.com/alangrow/status/448965593564078080

[cm3]

> I need to revisit mutt-kz

I haven't used it myself, but there's also https://www.neomutt.org/.

[sigil]

Interesting, thanks.

[krrrh]

I like the idea of having a large mail archive available locally for searching, but what do you do for mobile access? The utility of being able to search 10+ years of quickly while AFK is very high. I'd love to have a synced local archive that resided entirely on the mobile device.

[necessity]

The w3m bit doesn't work for me, mutt itself opens it and fails to format it. I have to type | to pipe it to w3m (or save the file).

[dredmorbius]

There's a commandline option to pass the document type to w3m: '-T text/html', I believe, confirm on the manpage.

It'll force any given file, or stdin, to be interpreted as HTML. It helps to remember that w3m was originally created as a generic file / directory browser. It's Web capabilities were somewhat incidental, though that's what it's largely used for now.

[sigil]

Sounds a problem with your mailcap.