Creating HTML emails with mutt

[martin f krafft]

Regarding the following, written by "John Long" on 2019-10-30 at 11:31 Uhr +0000:
>From my point the issue is not only what I have to configure or 
>what can be configured, but also how much code is behind doing 
>that. Less code is easier to manage than more code. I can't see the 
>benefit of junking up mutt with HTML …

Fully agreed on all of the above.

The approach Kevin proposed is completely HTML-agnostic and leaves 
it up to the user to provide an external tool that provides the 
HTML. Mutt then just does the required MIME-handling, which is 
clearly within the domain of a MUA.

Also, mutt already does receiving/reading multipart/alternative, so 
it only makes sense to figure out how to properly add creation of 
such containers. After all, mutt can sign GPG signatures, not just 
verify them.

>Remember, some of us use mutt on a console with no GUI.

There is no GUI requirement in any of this.

-- 
@martinkrafft | https://riot.im/app/#/room/#madduck:madduck.net
 
"all i know is that i'm being sued for unfair business
 practices by micro$oft. hello pot? it's kettle on line two."
                                                -- michael robertson
 
spamtraps: madduck.bogus at madduck.net
-------------- next part --------------
A non-text attachment was scrubbed...
Name: digital_signature_gpg.asc
Type: application/pgp-signature
Size: 1118 bytes
Desc: Digital GPG signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)
URL: <http://lists.mutt.org/pipermail/mutt-users/attachments/20191031/5dae3e98/attachment.asc>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mutt.org/pipermail/mutt-users/attachments/20191031/5dae3e98/attachment.html>