From: "Geo" 

This is a multi-part message in MIME format.

------=_NextPart_000_0037_01C5D69A.90A02850
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Yes but there is dos/win permissive and there is NT permissive. NT =
cleaned up a lot of the nonsense that dos/win allowed and while it = wasn't
entirely painless it resulted in a better, more stable, more = secure
environment.

We need a change like that for email (or maybe I should say email = clients).

Geo.
  "Rich"  wrote in message news:43590d6c{at}w3.nls.net...
     End user applications are permissive about this because they have =
to work in the real world.  That isn't the case with your example though =
which is well defined by a 12 year old standard.

  Rich
------=_NextPart_000_0037_01C5D69A.90A02850
Content-Type: text/html;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable








Yes but there is dos/win =
permissive and there=20
is NT permissive. NT cleaned up a lot of the nonsense that dos/win = allowed and=20
while it wasn't entirely painless it resulted in a better, more stable, = more=20
secure environment.
 
We need a change like that for email =
(or maybe I=20
should say email clients).
 
Geo.

  "Rich" <{at}> wrote in message news:43590d6c{at}w3.nls.net...
     End
user applications =
are permissive=20
  about this because they have to work in the real world.  That =
isn't the=20
  case with your example though which is well defined by a 12 year old=20
  standard.
   
  Rich

------=_NextPart_000_0037_01C5D69A.90A02850--

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