Regarding the following, written by “Dave Woodfall” on 2019-10-30 at 11:25 Uhr +0000:
I’d guess we all agree on that point. We’re currently discussing the creation of multipart/alternative containers, which place the HTML part as an alternative to the plain-text part, so you can freely choose which one to read. Nobody is suggesting mutt no longer sends text/plain by default. --
@martinkrafft | https://riot.im/app/#/room/#madduck:madduck.net the only difference between a car salesman and a computer salesman is that the car salesman knows he's lying. spamtraps: madduck.bo...@madduck.net |
- Re: Creating HTML emails with mutt martin f krafft
- Re: Creating HTML emails with mutt John Long
- Re: Creating HTML emails with mutt 雨宫恋叶
- Re: Creating HTML emails with mutt Derek Martin
- Rendering HTML as Markdown in mutt... martin f krafft
- Re: Rendering HTML as Markdown in ... Akkana Peck
- Formatting HTML content for colour... martin f krafft
- Re: Formatting HTML content for co... Kevin J. McCarthy
- Re: Formatting HTML content for co... martin f krafft
- Re: Creating HTML emails with mutt Dave Woodfall
- Re: Creating HTML emails with mutt martin f krafft
- Re: Creating HTML emails with mutt Dave Woodfall
- Re: Creating HTML emails with mutt Mark H. Wood
- Re: Creating HTML emails with mutt martin f krafft
- Re: Creating HTML emails with mutt Derek Martin
- Re: Creating HTML emails with mutt Dave Woodfall
- Re: Creating HTML emails with mutt martin f krafft
- Re: Creating HTML emails with mutt Kevin J. McCarthy
- Re: Creating HTML emails with mutt martin f krafft
- Re: Creating HTML emails with mutt Kevin J. McCarthy
- Re: Creating HTML emails with mutt Kevin J. McCarthy