Allyson,

I received a response on this directly from Karen Reznek that identified the
cause of the problem.  Her response was as follows...

"If the charset="utf-8" and/or the sender is using Microsoft Exchange,
then it likely UUENCODED. I am having that problem with one of my
subscribers. The character set cannot be changed under Exchange, and the
subscriber is stuck with it through the near future. Our temporary
solution is for her to send it to me (Mozilla automatically decodes it),
I change the setting to plain text - Western, and forward it on to the list.

Those with updated readers can read it, but it stores in the archives as
garbage. When I did a GET on the messages they came back as garbage. I
suspect that folks on DIGEST will not be able to read it, and know that
those on INDEX won't."

I confirmed that the message did have the charset="utf-8".  Problem is I've
tried numerous ways to remove this code and every time I have tried
resending the e-mail to my test list it comes back encoded again with the
utf-8 charset.  The only way I have been able to get around it is to send
the e-mail in plain text or rich text format but this isn't acceptable for
an announcement list that managers want to "look pretty".  We need to be
able to broadcast e-mails out in html format.  I've tried saving the content
with a different character set and although it appears to work, once again,
when I paste it into an e-mail with html format, the utf-8 charset
mysteriously returns.

Does anyone have any insight on this issue?  How can I get rid of the utf-8
charset and still maintain an html format for the e-mail?


...Wes Anderson


> -----Original Message-----
> From: Allyson McGibbon [mailto:[log in to unmask]]
> Sent: March 27, 2003 8:43 AM
> To: [log in to unmask]
> Subject: Re: Garbled text in archives
>
> Wes,
>
> We have experienced this problem with Outlook 2002 and when approving
> moderated messages via Exchange 5.5. Although we don't have a  fix we
> luckily have pop/Outlook 98 and use that for all our moderated messages.
> Only the IT team has 2002 right now but we are becoming worried as we will
> soon need to upgrade all our users and wonder if we'll see an increase in
> this issue.
>
> Allyson
>
> -----Original Message-----
> From: LISTSERV list owners' forum
> [mailto:[log in to unmask]]On Behalf Of Wes Anderson
> Sent: Monday, March 24, 2003 1:47 PM
> To: [log in to unmask]
> Subject: Garbled text in archives
>
>
> An owner of 6 announce-only lists recently sent out a broadcast to each of
> the 6 lists.  When I checked the archives through the web interface for
> these lists the information was all garbled.  All the messages were sent
> out
> using Outlook 2002 and were generally the same with the exception of some
> list specific information.  We have a couple of other lists that are
> configured exactly the same, with owners using the same Outlook and have
> not
> had any such problem; i.e. the archives appear okay.
>
> Example from one list:
> 1.      BM_1=?utf-8?B?UmVwb3J0IHRvIENQaEEgTWVtYmVycw==?=
> *
> <http://listserv-
> cpha.inf.ca/admin/wa.exe?A2=ind0303&L=ontario_onvote&T=0&F=
> &S=&X=3F175243755238D4C8&[log in to unmask]&P=65>
> =?utf-8?B?UmVwb3J0IHRvIENQaEEgTWVtYmVycw==?= (889 lines)
> From: =?utf-8?B?Q2FuYWRpYW4gUGhhcm1hY2lzdHMgQXNzb2NpYXRpb24vQXNzb2NpYXRp?=
> =?utf-8?B?b24gZGVzIHBoYXJtYWNpZW5zIGR1IENhbmFkYQ==?=
> <[log in to unmask]>
> Date: Thu, 20 Mar 2003 14:04:58 -0500
> When I go into the content of the message, it appears okay.  It's just the
> information in the archive header that seems garbled.  I wasn't too
> concerned since the owner has been receiving replies and all indications
> are
> the message went through okay (i.e. the replies include the original and
> it
> is all intact).  However, we just got notice from one subscriber saying
> the
> message was all garbled.  I have concerns now as to whether some
> subscribers
> got the e-mail okay, while others got "junk" and simply deleted it.
>
> I took one of the original e-mails and sent it to a test list that I have
> been working with.  I got the same result so it would seem that there is
> something in the content of the message that Listserv doesn't like.
> However, it's pretty plain other than a couple of bold-face headings and a
> couple of embedded web links.
>
> Has anyone ever experienced this problem?  Any clues as to what would
> cause
> this?
>
> Thanks in advance for any assistance.
>
> ...Wes
>
> =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=
> Wes Anderson, Wescath Solutions
> per Canadian Pharmacists Association
> Tel: 613-523-7877 ext. 228
> CPhA: [log in to unmask] <mailto:[log in to unmask]>
> =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=