Gnus development mailing list
 help / color / mirror / Atom feed
From: Karl Kleinpaste <karl@justresearch.com>
Subject: Re: Displaying mails with Content-Type: text/html
Date: 19 Jan 2000 11:03:39 -0500	[thread overview]
Message-ID: <vxkzou2t5es.fsf@beaver.jprc.com> (raw)
In-Reply-To: Raymond Scholz's message of "19 Jan 2000 16:53:37 +0100"

Raymond Scholz <rscholz@tzi.de> writes:
> I got two HTML mails (no multipart, SPAM of course). The first
> displays fine, the second doesn't and appears as HTML source. Looking
> at the MIME headers, I can't figure what causes this behaviour. 

The problem with the message you forwarded is that it contains no
MIME-Version header in the first place.  Gnus correctly declines to
display as MIME a message which does not claim to be MIME in the first
place.

"Content-Type: text/html" is necessary but not sufficient.
"MIME-Version: 1.0" is also needed.

> Subject: Earn 100K Plus a year! -aixnyg
> Reply-To: datsmyne008@yahoo.com
> From: wampun@necs.postmaster.co.uk
> Date: Mon, 17 Jan 2000 23:58:23 -0500
> X-Gnus-Mail-Source: file:/var/spool/mail/rscholz
> Message-Id: <vlmmixw.wjsmwc@jvxrjgu.jarh66@nexxmail.com>
> To: @informatik.uni-bremen.de@vhost2.systemv.com
> Content-Type: text/html;
> 	charset="iso-8859-1"
> Content-Transfer-Encoding: 7BIT
> X-UIDL: ca629e293b81b3df6b0f77400e797bb9
> Lines: 73
> Xref: mde1.home mail.spam:16
> X-Gnus-Article-Number: 16   Tue Jan 18 14:53:58 2000

As it happens, Netscrape's mail interface is deranged enough that it
will intuit MIMEness in the face of Content-Type alone.  But this is
true derangement, and jwz even admitted as much a couple years ago
when discussing such matters in news.software.readers.



  reply	other threads:[~2000-01-19 16:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-01-19 15:53 Raymond Scholz
2000-01-19 16:03 ` Karl Kleinpaste [this message]
2000-01-19 16:07 ` Kai Großjohann
2000-01-19 22:46   ` Brian May
2000-01-19 22:53     ` Alan Shutko
2000-01-20  4:43       ` Brian May
2000-01-20  5:48         ` Michael Welsh Duggan
2000-01-23 22:59           ` Brian May
2000-01-20 18:49     ` Jim Davidson
2000-01-23 22:58       ` Brian May

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=vxkzou2t5es.fsf@beaver.jprc.com \
    --to=karl@justresearch.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).