> Jul 31, 2023 13:23:21 Matt Connell <[email protected]>: > > > On Mon, 2023-07-31 at 20:16 +0300, Alexe Stefan wrote: > >>> Normally I would be in the chorus of "why do I need a whole entire > >>> web engine for an email client" but I'm also in the group of people > >>> who knows full well what the answer is. > >> > >> What is the answer? > >> Mutt doesn't need a web engine. > > > > For the reason that you just demonstrated for the class: HTML emails. > > > > Now, your simple mail shows just fine in a plain text only mail > > client, but in my world, and I'd wager most people's world, handling > > HTML messages (which includes CSS for legibility) is a necessity to > > some varying degree. > > > > Don't get me wrong, I'm "team plaintext" all day every day but I'm not > > going to make my life more difficult on principles. There are hills > > worth dying on but this isn't mine. > Iirc, you can setup mutt to open html emails either in a web browser or with > something like w3m. There's no need for a web engine in a mail client when > you have a perfectly workable web engine in the browser. You can easily reply > to html mail in plain text either way, and most html mail are marketing or > newsletter emails from companies where replying isn't needed anyways. >
That is totally not true any more unfortunately. The vast majority of email clients and web interfaces used by the technopeasants send HTML mail by default. So unless you're one of the lucky few who exchange emails only with fellow hackers you can expect to have to deal with a lot of HTML mail. Still, you don't technically need to have the HTML engine *in* the client itself... But that does make opening the silly things a bit quicker. LMP
