 
Tue, 18 Jun 2002 16:23:38 +1000
|
hmmmm...I've got our most active list coded with Language= NOHTML. The way
I read the Site Manager's manual, this should strip out all HTML parts that
are MIME encoded and send on the plain-text part. However, I just received
a message on said list with all sorts of gaudy fonts and colors.
Here's a sampling on the header:
<begin header>
This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
------=_NextPartTM-000-c90b21fa-826b-11d6-9af7-009027de5928
Content-Type: multipart/alternative;
boundary="----_=_NextPart_001_01C2168D.7A549AC0"
------_=_NextPart_001_01C2168D.7A549AC0
Content-Type: text/plain;
charset="iso-8859-1"
Hi,
I am interested in finding out how different organisations have set up...
<snip>
------_=_NextPart_001_01C2168D.7A549AC0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<XETA HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<XETA NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2653.12">
<TITLE>Journal Record Plan</TITLE>
</HEAD>
<BODY>
<P><FONT COLOR=3D"#000000" FACE=3D"Trebuchet MS">Hi,</FONT>
</P>
<P><FONT COLOR=3D"#000000" FACE=3D"Trebuchet MS">I am interested in =
<snip>
</end header>
Now, am I reading it wrong or is this correctly formatted HTML email? If
so, does anyone have an idea why it didn't get stripped? We're currently
running 1.8d but I just received the LAK for 1.8e this morning. Is 1.8e
better at blocking the unwanted HTML?
--
Chazzozz!!
Michael Shannon
Webmaster
[log in to unmask]
"Before you can grow old and wise you must first survive being young and
stupid." - Ancient Proverb
Note: Opinions expressed on this list are my own and do not reflect the
views, opinions or position of my employer. If swallowed, seek medical
advice.
|
|
|
