Subject: | |
From: | |
Reply To: | |
Date: | Tue, 24 Feb 2004 22:00:38 -0500 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
On Tue, 24 Feb 2004 17:55:22 EST, Catherine Buck Morgan <[log in to unmask]> said:
> In reviewing our archives, we've discovered that some subscribers'
> emails are not readable-- the email is nothing but an alphanumeric block
> of text. I thought maybe it was because people were sending in html (we
> have our lists set to "noHTML"), but on further investigation, found
> that the content type of their email is "Content-Type: text/plain;
> charset="utf-8"".
>
> It displays like this:
> SGVyZSBpcyBvdXIgYWdlbmRhIGZvciBGcmlkYXkNCiANCjEwOjAwICBIZWxlbiBGZWxsZXJzIC0g
You're missing a 'Content-Transfer-Encoding: base64' with that content-type, I
suspect. Properly written MIME-aware MUAs should be able to deal with base64,
(although they may choke if they don't have utf-8 support, or if they don't
have support for the specific Unicode pages that the mail requires).
Does mail to the list show up with the C-T-E: header, and it's just missing in the
archives? Or does mail from the user show up mangled on postings too? If the
latter, does direct mail from the user have issues as well?
|
|
|