Re: Creating HTML emails with mutt
Sorry, I'm coming into this late. Early on, Kevin McCarthy said: Native support for multipart/alternative composition isn't in my todo list. Too bad -- that would be conceptually clean, to generate multipart/alternative as part of composition. 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. That external program could be anything, could be user's choice. It could be a GUI HTML editor that generates HTML and plain text in parallel from what the user does. It could be a shell script, that runs a text editor where the user types Markdown, and then converts that to HTML and returns both. From there, I guess Mutt would treat that multipart/alternative the same as a simple body part of plain text: build a MIME tree around it, with attachments and GPG signature. Would that work?
Re: Creating HTML emails with mutt
> […] virtually all of the people who use mutt either as their only > email client or along with others, chose mutt because of its > simplicity. People who want a simple text mail client will use Alpine or similar. Mutt's possibly the most “complicated” text MUA. I don't use mutt because of its “simplicity”, I use it because of its power and flexibility. And I'm closely following this thread because I'm one of the “strange” people who'd _like_ mutt to be able to handle outgoing multipart messages; I was trying to achieve exactly that, three years ago: https://www.mail-archive.com/mutt-users@mutt.org/msg50518.html > It seems to be contrary to the direction and purpose of mutt to make > it do everything anybody wants. The current number of configuration options suggests otherwise, and mutt would lose most of its appeal for me if it trimmed down the number of options. > The harm of making the app more complicated and adding a lot of code > is real, and it directly affects the user of mutt whether he's new or > old. There are dozens of mutt options I turn off, yet I won't argue they need to be removed just because they're not part of _my_ use case. I can appreciate everyone's needs are different and what works best for me will likely not work best for everyone. -- · Patrice Levesque · http://ptaff.ca/ · mutt.wa...@ptaff.ca -- signature.asc Description: Digital signature
Re: Creating HTML emails with mutt
Regarding the following, written by "martin f krafft" on 2019-11-02 at 23:40 Uhr +1300: How does this message fare? I’ve hacked up my script so that it actually keeps the ‘>’ even in the HTML, but uses CSS to hide it. Yeah, so I am not convinced at all, because all the html2text converters won't ignore that extra '>', and it just gets really ugly. Assuming that Thunderbird users are the only ones that actually know how to quote (and we can safely ignore Outlook/Gmail, who all top-quote anyway), maybe this is a bug to be taken up with Thunderbird devs? -- @martinkrafft | https://riot.im/app/#/room/#madduck:madduck.net "es ist gut, eine sache doppelt auszudrücken und ihr einen rechten und linken fuß zu geben. auf einem bein kann die wahrheit zwar stehen; mit zweien aber wird sie gehen und herumkommen." -- friedrich nietzsche spamtraps: madduck.bo...@madduck.net digital_signature_gpg.asc Description: Digital GPG signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)
Re: Creating HTML emails with mutt
Regarding the following, written by "Martin Trautmann" on 2019-11-02 at 10:22 Uhr +0100: However, the usage of blockquote within HTML is something where there is not necessarily a proper way of handling this - Thunderbird does not do it properly, as you see above. How does handle html itself nested blockquote levels? Oh, interesting corner case you spotted there. HTML does nesting of blockquotes just fine. The problem here seems to be that Thunderbird doesn't recognise blockquote as a quote, and needs the leading '>'. How does this message fare? I've hacked up my script so that it actually keeps the '>' even in the HTML, but uses CSS to hide it. :grin: -- @martinkrafft | https://riot.im/app/#/room/#madduck:madduck.net in africa some of the native tribes have a custom of beating the ground with clubs and uttering spine chilling cries. anthropologists call this a form of primitive self-expression. in america they call it golf. spamtraps: madduck.bo...@madduck.net digital_signature_gpg.asc Description: Digital GPG signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)
Re: Creating HTML emails with mutt
On 19-11-01 11:37, martin f krafft wrote: > Regarding the following, written by “Stefan Hagen” on 2019-11-01 at > 08:53 Uhr +0100: > > While I was able to just write an email and send it, it is now a > process of carefully “coding” an email, previewing, correcting, > previewing, sending… > > There’s a lot of good things to be said about carefully crafting emails! > > Regardless, to most of us who’ve been writing text/plain emails all of > our lives, using ASCII characters for emphasis and hand-crafting > numbered and itemised lists, Markdown will hardly even have a learning > curve. Your setup for plain text is very reasonable, using format-flowed and > as quote character. However, the usage of blockquote within HTML is something where there is not necessarily a proper way of handling this - Thunderbird does not do it properly, as you see above. How does handle html itself nested blockquote levels? How does outlook handle it? I guess it's not an issue over there. Outlook users do use full quotes below without ever reading them!? Schönen Gruß Martin signature.asc Description: OpenPGP digital signature
