Creating HTML emails with mutt

[martin f krafft]

Regarding the following, written by "Kurt Hackenberg" on 2019-11-03 at 00:11 Uhr -0400:
>Mutt runs an external text editor to 
>compose plain text; it could do the same 
>for this -- run some external composition 
>program that would return both HTML and 
>plain text.

There is nothing stopping you from setting `$editor` to a HTML 
editor, and defining `$content_type` to be `text/html`, and then 
using Kevin's `multipart/alternative` functionality to generate a 
`text/plain` part.

The only issue with this approach would be that you'd now have the 
`text/plain` part after the `text/html`, which means that dumb 
clients such as Gmail and Outlook and Thunderbird too would actually 
prefer the plain-text message over the HTML one.

Getting mutt to sort those into order might get really messy though, 
and while I think it it wouldn't be too hard to ensure that 
`text/html` always comes after `text/plain`, anything beyond that 
would require a new command, but `alternative_order` is already 
taken for something else, and cannot be reused, I don't think.

-- 
@martinkrafft | https://riot.im/app/#/room/#madduck:madduck.net
  
"no work of art ever puts forward views.
  views belong to people
  who are not artists."
                                                       -- oscar wilde
  
spamtraps: madduck.bogus at madduck.net
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mutt.org/pipermail/mutt-users/attachments/20191103/dd7bdba7/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: digital_signature_gpg.asc
Type: application/pgp-signature
Size: 1187 bytes
Desc: Digital GPG signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)
URL: <http://lists.mutt.org/pipermail/mutt-users/attachments/20191103/dd7bdba7/attachment.asc>