These following posts, taken from the Digests of the PipeChat list, show how NON Plain Text postings appear to those receiving the Digest. I have tried to limit these examples to those pertaining to the HTML / RTF formatting problems on the list and by no means am I trying to "pick" on any list member by posting these examples.

Subject: Re: HTML Workaround for AOL
From: <RonSeverin@aol.com>
Date: Fri, 27 Dec 2002 11:26:46 EST


--part1_8.31e770b6.2b3dd946_boundary
Content-Type: text/plain; charset=3D"US-ASCII"
Content-Transfer-Encoding: 7bit

Dear Peter et al:

Even after following the proceedure to strip HTML it seems
MIME 1.0 takes over. How do I deal with that? I'm not a computer
genius. If I use MS Express I take the chance of passing on
and receiving Viruses, which I don't want to do. I've noticed that
AOL is not the only culprit. Several of the other major providers
also send rich text which if stripped off will not send the
pipechat footers either. They also go to MIME. I've installed
ZoneAlarm as a firewall, and AdWare 5.83 to find and eliminate
Zombie intrusions into my hard drive. Zombie masters use our
computers to send and bounce anonymous business and porno
activity. These may be delivered in pop ups and deposit programs
to further their nefarious activities without your knowledge. Yahoo
is one of the worst. I have not had a crash since installing AdWare.
These are dumped to your hard drive as cookies and run in the
background undetected. As soon as I get a pop up, I run AdWare
and sure enough there are cookies and other files left behind to use
your computer for their own network purposes.

Ron Severin

--part1_8.31e770b6.2b3dd946_boundary
Content-Type: text/html; charset=3D"US-ASCII"
Content-Transfer-Encoding: 7bit

<HTML><FONT FACE=3Darial,helvetica><FONT SIZE=3D2 FAMILY=3D"SANSSERIF" =
FACE=3D"Arial" LANG=3D"0">Dear Peter et al:<BR>
<BR>
Even after following the proceedure to strip HTML it seems<BR>
MIME 1.0 takes over. How do I deal with that? I'm not a computer<BR>
genius. If I use MS Express I take the chance of passing on<BR>
and receiving Viruses, which I don't want to do. I've noticed that<BR>
AOL is not the only culprit. Several of the other major providers<BR>
also send rich text which if stripped off will not send the<BR>
pipechat footers either. They also go to MIME. I've installed<BR>
ZoneAlarm as a firewall, and AdWare 5.83 to find and eliminate<BR>
Zombie intrusions into my hard drive. Zombie masters use our<BR>
computers to send and bounce anonymous business and porno<BR>
activity. These may be delivered in pop ups and deposit programs<BR>
to further their nefarious activities without your knowledge. Yahoo<BR>
is one of the worst. I have not had a crash since installing AdWare.<BR>
These are dumped to your hard drive as cookies and run in the <BR>
background undetected. As soon as I get a pop up, I run AdWare<BR>
and sure enough there are cookies and other files left behind to use<BR>
your computer for their own network purposes.<BR>
<BR>
Ron Severin</FONT></HTML>

--part1_8.31e770b6.2b3dd946_boundary--

Subject: HTML
From: <Wuxuzusu@aol.com>
Date: Fri, 27 Dec 2002 10:32:25 EST


--part1_22.3403bae1.2b3dcc89_boundary
Content-Type: text/plain; charset=3D"US-ASCII"
Content-Transfer-Encoding: 7bit

Greetings Stan Yoder,

Do you receive the digest version of the chaline?

I wonder if perhaps only the AOL subscribers get the double plus gobblety
gook on the chatline digest?

Stan Krider

PS Back to real pipe organ stuff now.

In a message dated 12/27/2002 5:03:51 AM Eastern Standard Time,
pipechat@pipechat.org vze2myh5@verizon.net writes:

> Subject: Re: HTML Workaround for AOL
> From: "Stan Yoder" <vze2myh5@verizon.net>
> Date: Thu, 26 Dec 2002 22:17:41 -0500
>
> David Scribner wrote:
> >
> >Except Ron this is what your email shows - it is NOT in Plain Text so
> >that doesn't work.
> >
>
> Well, Ron's message appeared on my screen as plain text (only.)
>
> Stan Yoder
> Pittsburgh


--part1_22.3403bae1.2b3dcc89_boundary
Content-Type: text/html; charset=3D"US-ASCII"
Content-Transfer-Encoding: 7bit

<HTML><FONT FACE=3Darial,helvetica><FONT SIZE=3D2 FAMILY=3D"SANSSERIF" =
FACE=3D"Arial" LANG=3D"0">Greetings Stan Yoder,<BR>
<BR>
Do you receive the digest version of the chaline?<BR>
<BR>
I wonder if perhaps only the AOL subscribers get the double plus gobblety =
gook on the chatline digest?<BR>
<BR>
Stan Krider<BR>
<BR>
PS&nbsp; Back to real pipe organ stuff now.<BR>
<BR>
In a message dated 12/27/2002 5:03:51 AM Eastern Standard Time, =
pipechat@pipechat.org vze2myh5@verizon.net writes:<BR>
<BR>
<BLOCKQUOTE TYPE=3DCITE style=3D"BORDER-LEFT: #0000ff 2px solid; =
MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">Subject: Re: HTML =
Workaround for AOL<BR>
From: "Stan Yoder" &lt;vze2myh5@verizon.net&gt;<BR>
Date: Thu, 26 Dec 2002 22:17:41 -0500<BR>
<BR>
David Scribner wrote:<BR>
&gt;<BR>
&gt;Except Ron this is what your email shows - it is NOT in Plain Text =
so<BR>
&gt;that doesn't work.<BR>
&gt;<BR>
<BR>
Well, Ron's message appeared on my screen as plain text (only.)<BR>
<BR>
Stan Yoder<BR>
Pittsburgh</BLOCKQUOTE><BR>
<BR>
</FONT></HTML>
--part1_22.3403bae1.2b3dcc89_boundary--

Subject: HTML
From: <Wuxuzusu@aol.com>
Date: Thu, 26 Dec 2002 20:56:52 EST


--part1_ab.271b8727.2b3d0d64_boundary
Content-Type: text/plain; charset=3D"US-ASCII"
Content-Transfer-Encoding: 7bit

Greetings,

I'd hate to give up on this pipechat line, however, if you folks only knew =

how inept I am with this new fangled computer gadget, you would understand =
my
reluctance to leave AOL.

Stan Krider

In a message dated 12/26/2002 7:09:51 PM Eastern Standard Time, Peter
Harrison writes:

Another email list I use recently solved this problem for their digest
subscribers by changing the list server settings to bounce all incoming =
post
that contained HTML format tags. It meant users of AOL V5 and later were =
no
longer able to post without using webmail or posting from the mail list
website.

The majority of posters were not affected but it provided a reminder for =
the
minority who used AOL (which at that time included me) that perhaps it was
time to move on from an ISP that provides super simple, friendly, but
limited facility software to something more flexible.

--part1_ab.271b8727.2b3d0d64_boundary
Content-Type: text/html; charset=3D"US-ASCII"
Content-Transfer-Encoding: 7bit

<HTML><FONT FACE=3Darial,helvetica><FONT SIZE=3D2 FAMILY=3D"SANSSERIF" =
FACE=3D"Arial" LANG=3D"0">Greetings,<BR>
<BR>
I'd hate to give up on this pipechat line, however, if you folks only knew =
how inept I am with this new fangled computer gadget, you would understand =
my reluctance to leave AOL.<BR>
<BR>
Stan Krider<BR>
<BR>
In a message dated 12/26/2002 7:09:51 PM Eastern Standard Time, Peter =
Harrison writes:<BR>
<BR>
Another email list I use recently solved this problem for their digest<BR>
subscribers by changing the list server settings to bounce all incoming =
post<BR>
that contained HTML format tags. It meant users of AOL V5 and later were =
no<BR>
longer able to post without using webmail or posting from the mail =
list<BR>
website.<BR>
<BR>
The majority of posters were not affected but it provided a reminder for =
the<BR>
minority who used AOL (which at that time included me) that perhaps it =
was<BR>
time to move on from an ISP that provides super simple, friendly, but<BR>
limited facility software to something more flexible.<BR>
</FONT></HTML>
--part1_ab.271b8727.2b3d0d64_boundary--

Subject: HTML messages
From: <Wuxuzusu@aol.com>
Date: Tue, 24 Dec 2002 14:36:52 EST


--part1_153.19649b87.2b3a1154_boundary
Content-Type: text/plain; charset=3D"US-ASCII"
Content-Transfer-Encoding: 7bit

Greetings Michael and all,

As you might note, I am as guilty of this as anyone else.

Sadly, AOL does not give me any choice. I type what I perceive to be a =
plain
text email message, yet the digests receive two messages from me, one the
plain text, and the other (whatever Michael talked about). I've complained =
to
AOL several times to no avail.

I'm sorry; I apologize, I'm guilty; but AOL won't let me send it any other =

way.

Sorry,

Stan Krider

PS Did I say, I'm sorry?

In a message dated 12/24/2002 1:57:28 PM Eastern Standard Time, Michael =
David
writes:
>
> Those of us who get this list in digest mode have to put up with things
> like
> the following. This represents most of an entire HTML formatted message
> after it has been "translated" by the list server.
>
> Would any of you who cannot or will not post to the list in plain text
> format care to explain the advantages of this format. I'm really =
curious
> as
> I am unable to extract any useful information from these posts.
>

--part1_153.19649b87.2b3a1154_boundary
Content-Type: text/html; charset=3D"US-ASCII"
Content-Transfer-Encoding: 7bit

<HTML><FONT FACE=3Darial,helvetica><FONT SIZE=3D2 FAMILY=3D"SANSSERIF" =
FACE=3D"Arial" LANG=3D"0">Greetings Michael and all,<BR>
<BR>
As you might note, I am as guilty of this as anyone else. <BR>
<BR>
Sadly, AOL does not give me any choice. I type what I perceive to be a =
plain text email message, yet the digests receive two messages from me, =
one the plain text, and the other (whatever Michael talked about). I've =
complained to AOL several times to no avail.<BR>
<BR>
I'm sorry; I apologize, I'm guilty; but AOL won't let me send it any other =
way.<BR>
<BR>
Sorry,<BR>
<BR>
Stan Krider<BR>
<BR>
PS Did I say, I'm sorry?<BR>
<BR>
In a message dated 12/24/2002 1:57:28 PM Eastern Standard Time, Michael =
David writes:<BR>
<BLOCKQUOTE TYPE=3DCITE style=3D"BORDER-LEFT: #0000ff 2px solid; =
MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px"><BR>
Those of us who get this list in digest mode have to put up with things =
like<BR>
the following.&nbsp; This represents most of an entire HTML formatted =
message<BR>
after it has been "translated" by the list server.<BR>
<BR>
Would any of you who cannot or will not post to the list in plain text<BR>
format care to explain the advantages of this format.&nbsp; I'm really =
curious as<BR>
I am unable to extract any useful information from these posts.<BR>
</BLOCKQUOTE><BR>
</FONT></HTML>
--part1_153.19649b87.2b3a1154_boundary--

Subject: Sending No HTML from AOL
From: <Myosotis51@aol.com>
Date: Tue, 24 Dec 2002 18:51:16 EST


--part1_f2.26d65f70.2b3a4cf4_boundary
Content-Type: text/plain; charset=3D"US-ASCII"
Content-Transfer-Encoding: 7bit

Here's how to wipe the HTML coding from AOL mail:

1. Write your mail as usual, making sure you don't copy anything you =
don't
need to respond to. Make sure you are using the "Arial" font, in black.

2. Highlight the entire text area.

3. Right-click with your mouse, and choose "Select All."

4. Right-click again, and choose "Text" --> "Normal."

5. Send, without adding anything else - if you do, repeat 2 - 4.

This should ease the Digestion problems!

Victoria

--part1_f2.26d65f70.2b3a4cf4_boundary
Content-Type: text/html; charset=3D"US-ASCII"
Content-Transfer-Encoding: 7bit

<HTML><FONT FACE=3Darial,helvetica><FONT SIZE=3D2 FAMILY=3D"SANSSERIF" =
FACE=3D"Arial" LANG=3D"0">Here's how to wipe the HTML coding from AOL =
mail:<BR>
<BR>
1.&nbsp; Write your mail as usual, making sure you don't copy anything you =
don't need to respond to.&nbsp; Make sure you are using the "Arial" font, =
in black.<BR>
<BR>
2.&nbsp; Highlight the entire text area.<BR>
<BR>
3.&nbsp; Right-click with your mouse, and choose "Select All."<BR>
<BR>
4.&nbsp; Right-click again, and choose "Text"&nbsp; --&gt;&nbsp; =
"Normal."<BR>
<BR>
5.&nbsp; Send, without adding anything else - if you do, repeat 2 - 4.<BR>
<BR>
This should ease the Digestion problems!<BR>
<BR>
Victoria</FONT></HTML>

--part1_f2.26d65f70.2b3a4cf4_boundary--