On Wed, Feb 07, 2001 at 12:14:53AM -0500, Ken Weingold wrote:
> What is it that mutt uses to tell that an email is in HTML? I set
> autoview to launch lynx to view HTML, and all of a sudden I am seeing
> a lot more emails as html. I commented out autoview in my muttrc and
> looked at one of them again and it was normal, in plain text. Here
> are the headers I think ar relative:
>
> ----------------------------------------------------------------
>
> Mime-Version: 1.0
> Content-Type: multipart/alternative;
> boundary="=====================_170611416==_.ALT"
> Status: RO
> Content-Length: 361
> Lines: 17
>
> Content-Type: text/plain; charset="us-ascii"
>
> ----------------------------------------------------------------
You'll note that the header says "multipart/alternative". That means
that the message contains multiple MIME parts, and that each part is an
alternative representation of the same content. If you pipe the message
to a pager such as 'less' or 'more', you will be able to see all the
parts. Somewhere in there is another part with Content-Type: text/html.
Most mailers, including mutt, will select just one of the multiple parts
to display based on the Content-Types in the message, the abilities of
the mailer, and the preferences of the user. If you give mutt the
ability to display HTML content in-line by setting "auto_view text/html"
and by putting an appropriate "text/html; ..." line in your mailcap, it
will apparently display the text/html part in preference to the
text/plain part. You can control this behavior with the
alternative_order list.
Gary
--
Gary Johnson | Agilent Technologies
[EMAIL PROTECTED] | RF Communications Product Generation Unit
| Spokane, Washington, USA
