I don't understand what you envision such a rendering to do.
To achieve a level of rendering emails (and web) similar to gitlab or github. That includes bold, italics, code blocks, and possibly more. In both Hyperkitty and email clients.
It has nothing at all to do with messages delivered to list members.
that's why I mentioned "would affect more than just Hyperkitty. (i.e. mailman-core)."
Archived messages which contain text/html parts currently render those parts as attachments that can be downloaded. Are you suggesting that "HTML" rendering would render those inline or something else?
Yes "inline", as part of the main message display, and not as an attachment. No attachment would appear.
HyperKitty's rendering mode has nothing to do with that.
Hyperkitty is one of the two main components. It's the web UI part. The other being the outgoing emails.
If you're suggesting a text/html part outside of a multipart/alternative part
I was probably imagining just "multipart/alternative", containing alternatives. Is the "outside" method also a possibility? I did not intend that.
For example if in Yahoo mail one composes in "rich text" and drags and drops or copy/pastes or in some ways even types a link, the generated text/plain alternative doesn't contain the url in any form.
Our lists are set to "Convert html to plaintext". I just tested from Yahoo email, with rich text, and hyperlinks. Everything was fine. The problem didn't exhibit itself. I also "copied" a link from a website, and pasted it into the email, but it was ok. Perhaps other clients "aol.com, att.net, netscape.net, pacbell.net, prodigy.net, rocketmail.com, sbcglobal.net and ymail.com" have a problem? But today in mail.yahoo.com , no...
If most mail clients include Yahoo and Gmail send both HTML and plain-text versions in a multipart message, there would theoretically be two choices for mm3 with "Convert html to plaintext".
- Mail out the included plain-text copy from the multipart email. Or,
- Parse the HTML part of the message and "convert html to plaintext".
which of those is occurring?
To summarize again, the goal is to show in Hyperkitty and in email clients a format (based on HTML) that includes bold, italics, bullet items, and code blocks. The same way github or gitlab messages appear, with more formatting options. Since HTML is a standard format, and many mail clients have built-in support for both generating and displaying it, HTML is nature choice for a protocol to use, it's already included everywhere.