Many of us loathe html email, but obviously we have no control over what we receive and deal with it the best we can. In my experience, the text browsers are doing a pretty bad rendering job on average, so an alternative is to use mutt's view-mailcap function and launch your favourite browser from mailcap.
This is where the fun starts. Many emails are handled poorly even then. What I would like to see improved in particular is html email with embedded images. The MIME structure of such a message: 1 text/html 2 image/png 3 ... The images are referenced via img tags, src option, in the html part. When view-mailcap is invoked, the html part is saved into /tmp/mutt-hostname-uid-somenumber-somelongnumber, rendered by the browser and then removed, with gaps where the images should be. Could mutt, upon invoking view-mailcap, save all attachments to a temp directory and rewrite the html part so that the img src paths are correct? Html viewing is only one special case of invoking mailcap, so I don't think that mutt can or should provide a fully generalized solution. OTOH html email has become the de-facto norm in the corporate world, whether we like it or not. I'm also interested in hearing if anyone here has felt this is a problem and implemented a custom solution (macro/script based - I could probably whip one up easily, except I don't know how to get mutt to save all attachments in one command; doing it externally would duplicate the work mutt has already done).
