On 20/03/2020 16:07, Jaroslaw Rafa wrote: > Dnia 20.03.2020 o godz. 11:48:59 Gerard E. Seibert pisze: >> When I receive an email, I have two immediate choices to make; either >> read it or don't read it. > Let's say I decide to read it, so I press ENTER on the message header. > If it's plaintext, I continue straight on to reading it. > If it's HTML (without corresponding alternate plaintext part), I see only a > bunch of unreadable HTML tags. Sometimes even whem plaintext part is > present, it's formatted as everything-in-one-long-line, which is also hardly > readable. > Then I have to back out to message index, display attachment list for the > message, find the HTML part and press ENTER on it to launch web browser and > view the message in browser. > So it's much more effort needed to read HTML-only mail compared to > plaintext.
Your User-Agent header states that you're using Mutt. Did you know that
Mutt has some very good options when it comes to viewing HTML mail?
Firstly, there's the "alternative_order" directive. This takes a list of
MIME types and, when the body of an email has alternative types, Mutt
picks the first one on the list to display. So, in other words, if you
set this to "text/plain text/enriched text/html" then you get the
lightest-weight version by preference; if you set it to "text/html
text/enriched text/plain", then you get the most full-featured one by
preference.
Next up, there's the "auto_view" directive. This takes a list of MIME
types which, instead of being presented attachment-like are presented as
body. So you can list "text/html", "application/pdf" even whatever the
abomination is that Microsoft Word's documents are registered as :) But
how can Mutt display PDFs, DOCXs and so on? This is where your
~/.mailcap file comes in. This is a great file for registering viewers
for MIME types. So, for example, I have the following in my Mailcap:
text/html; uconv -f %{charset} < %s | elinks -dump 1 -dump-width 130
-dump-color-mode 0 -dump-charset utf-8 -default-mime-type text/html
-config-dir ~/.mutt/ ; nametemplate=%s.html ; copiousoutput
application/msword; antiword %s; copiousoutput
application/pdf; pdftotext %s -; copiousoutput
Here, I use elinks to dump the HTML to text, antiword to dump Word
documents to text and pdftotext to do "what it says on the tin". The
"copiousoutput" flag means that the command is likely to produce more
than a few lines of output. Mutt will invoke these filters on an
"auto_view" MIME part and use the output as body text.
My point being that if you're seeing HTML tags when reading email,
you've probably just not configured your MUA correctly.
>> I have
>> yet to understand this hatred of HTML email.
> Is it easier to understand now? :)
signature.asc
Description: OpenPGP digital signature
