On 2017-04-26, Grant Edwards <grant.b.edwa...@gmail.com> wrote: > On 2017-04-26, Will Yardley <mutt-us...@veggiechinese.net> wrote: [...]
> If there was a simple way to get mutt to auto-magically do that to > create a multipart/alternative text and HTML message body, that > wouldn't be that bad an option. Though I'd probably use <xmp> rather > than <pre>, since <xmp> is less fragile.
[...]
> > I also wouldn't be too averse to setting up some sort of scheme for > running a message body thought asciidoc or rst to produce HTML and > plaintext multipart alternative. The solution I settled (and have been using for a couple weeks now) is to use mutt's 'sendmail' configuration setting to pipe outgoing mail to the 'muttdown' utility
I didn't know about muttdown, but I actually developed a similar system: https://github.com/amitramon/plainMail2HTML I developed it specifically for Mutt, the README explains my motivation. What it does, in short, is replacing Mutt's sendmail command with a tool that reads the message generated by Mutt, parse the text/plain part with a rst parser (that can easily be replaced by a different parser), create and add to the message a text/html part, then send it as usual. I hope you find it useful. Cheers, Amit
