From: Raymond Scholz <rscholz@tzi.de>
Subject: Displaying mails with Content-Type: text/html
Date: 19 Jan 2000 16:53:37 +0100 [thread overview]
Message-ID: <m3901m3vni.fsf@rscholz.dyndns.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 596 bytes --]
Hello!
A few days ago, somebody reported in a German newsgroup that he
couldn't automatically display a mail with a correctly declared
Content-Type: text/html. I told him that I've never had any problems
with this. Well, I now ran into the same problem.
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.
When saving the HTML content in an extra file, W3 mode displays both
mails as expected.
Here is the second (incorrectley displayed) mail:
[-- Attachment #2: Type: message/rfc822, Size: 4997 bytes --]
[-- Attachment #2.1: Type: text/html, Size: 3440 bytes --]
From: wampun@necs.postmaster.co.uk
To: @informatik.uni-bremen.de@vhost2.systemv.com
Subject: Earn 100K Plus a year! -aixnyg
Date: Mon, 17 Jan 2000 23:58:23 -0500
Message-ID: <vlmmixw.wjsmwc@jvxrjgu.jarh66@nexxmail.com>
[-- Attachment #3: Type: text/plain, Size: 345 bytes --]
I did not include the mail which is rendered correctly because it's
rather big.
I put them here:
http://rscholz.dusnet.de/spam_ok.mail
http://rscholz.dusnet.de/spam_not_ok.mail
Cheers,
Ray
--
Raymond Scholz -*- rscholz@tzi.de -*- http://www.tzi.de/~rscholz/
FB 3 Informatik, Universität Bremen -*- PGP key available via WWW
next reply other threads:[~2000-01-19 15:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-19 15:53 Raymond Scholz [this message]
2000-01-19 16:03 ` Karl Kleinpaste
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=m3901m3vni.fsf@rscholz.dyndns.org \
--to=rscholz@tzi.de \
/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).