From: "Rich" 

This is a multi-part message in MIME format.

------=_NextPart_000_0405_01C5D708.6453A240
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

   non sequitur.

Rich

  "Geo"  wrote in message
news:4359b7d1{at}w3.nls.net...
  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_0405_01C5D708.6453A240
Content-Type: text/html;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable








   non
sequitur.
 
Rich
 

  "Geo" <georger{at}nls.net>">mailto:georger{at}nls.net">georger{at}nls.net>
wrote=20
  in message news:4359b7d1{at}w3.nls.net...
  Yes but there is dos/win =
permissive and=20
  there is NT permissive. NT cleaned up a lot of the nonsense that =
dos/win=20
  allowed and while it wasn't entirely painless it resulted in a better, =
more=20
  stable, more 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=20
    permissive about this because they have to work in the real =
world. =20
    That isn't the case with your example though which is well defined =
by a 12=20
    year old standard.
     
    Rich

------=_NextPart_000_0405_01C5D708.6453A240--

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