[Vision2020] Test Post

Sat, 15 May 2004 18:09:27 EDT

--part1_12d.413a0f1f.2dd7ef17_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

Nick:

When I opened you previous post to V2020 with your reply to Don Nelson via my 
AOL e-mail as the post came in normally to my account, there was no code in 
the body of your message.  It was easily readable, etc.

When you go into the V2020 archives, "code," as you put it, is often 
displayed, but this is a characteristic, I think, of how V2020 archived messages are 
shown when you access the archive.  This does not mean this is how they 
appeared originally when the messages went out to the V2020 list serve.

Just two cents worth from a computer neophyte,

Ted

--part1_12d.413a0f1f.2dd7ef17_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

<HTML><FONT FACE=3Darial,helvetica><HTML><FONT  SIZE=3D2 PTSIZE=3D10 FAMILY=
=3D"SANSSERIF" FACE=3D"Arial" LANG=3D"0"><BR>
Nick:<BR>
<BR>
When I opened you previous post to V2020 with your reply to Don Nelson via m=
y AOL e-mail as the post came in normally to my account, there was no code i=
n the body of your message.&nbsp; It was easily readable, etc.<BR>
<BR>
When you go into the V2020 archives, "code," as you put it, is often display=
ed, but this is a characteristic, I think, of how V2020 archived messages ar=
e shown when you access the archive.&nbsp; This does not mean this is how th=
ey appeared originally when the messages went out to the V2020 list serve.<B=
R>
<BR>
Just two cents worth from a computer neophyte,<BR>
<BR>
Ted</FONT></HTML>

--part1_12d.413a0f1f.2dd7ef17_boundary--