From: "Rich" 

This is a multi-part message in MIME format.

------=_NextPart_000_0384_01C5D59A.C6FCBFE0
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

   Email content is any encoding you want.  The example you give is =
valid even if silly.  It's not a security issue in any case.

   BTW, email is not 7-bit though it is encouraged to be encoded as such =
because that provides better compatibility.  There is a standard for =
checking for 8-bit compatiblity.  See =
http://www.ietf.org/rfc/rfc1652.txt.  It's not necessary since anything =
can be encoded as 7-bit.  It can be more efficient.

Rich

  "Geo."  wrote in message =
news:4357ff5e$1{at}w3.nls.net...
  Ok I don't understand so maybe someone can give me a rational =
explanation of
  this.

  Why would an email program accept

  Subject: =3D?ascii?B?W1NQQU1dICBPbmxpbmUgUGF5bWVu?=3D
  =3D?ascii?B?dHMgYW5kIG91ciBzZWN1cmUgc2l0?=3D =3D?ascii?B?ZSE=3D?=3D

  and decode it to

   [SPAM]  Online Payments and our secure site!

  This just boggles the mind, I mean if you were trying to create secure
  application wouldn't you restrict to a least common instead of allow
  everything? Email is 7bit ascii not unicode correct? Is this somehow =
needed
  to allow unicode subject line where the RFC's don't allow it?

  Geo. 


------=_NextPart_000_0384_01C5D59A.C6FCBFE0
Content-Type: text/html;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable








   Email
content is any =
encoding you=20
want.  The example you give is valid even if silly.  It's
not = a=20
security issue in any case.
 
   BTW,
email is not 7-bit =
though it is=20
encouraged to be encoded as such because that provides better=20
compatibility.  There is a standard for checking for 8-bit=20
compatiblity.  See http://www.ietf.org/rfc/rfc1" target="new">http://www.ietf.org/rfc/rfc1=">http://www.ietf.org/rfc/rfc1652.txt">http://www.ietf.org/rfc/rfc1=
652.txt. =20
It's not necessary since anything can be encoded as 7-bit.  It can
= be more=20
efficient.
 
Rich
 

  "Geo." <fake{at}barkdom.com>=20">mailto:fake{at}barkdom.com">fake{at}barkdom.com>=20
  wrote in message news:4357ff5e$1{at}w3.nls.net...Ok I=20
  don't understand so maybe someone can give me a rational explanation=20
  ofthis.Why would an email program
acceptSubject:=20
  =
=3D?ascii?B?W1NQQU1dICBPbmxpbmUgUGF5bWVu?=3D=3D?ascii?B?dHMgYW5kIG91c=
iBzZWN1cmUgc2l0?=3D=20
  =3D?ascii?B?ZSE=3D?=3Dand decode it =
to [SPAM]  Online=20
  Payments and our secure site!This just boggles the mind, I =
mean if you=20
  were trying to create secureapplication wouldn't you restrict to a =
least=20
  common instead of alloweverything? Email is 7bit ascii not unicode =

  correct? Is this somehow neededto allow unicode subject line where =
the=20
  RFC's don't allow it?Geo. <confused and trying
not to read=20
  conspiricy into
it>

------=_NextPart_000_0384_01C5D59A.C6FCBFE0--

--- BBBS/NT v4.01 Flag-5