Read: Western European (ISO). Use default... is not selected.
Send: Same
There is no significant difference whether I choose UTF-8 or ISO-8859 to
view.
--
Noel
"Ron Sommer" <rsommer@xxxxxx> wrote in message
news:OG7l8EPXIHA.5208@xxxxxx
Quote:
> What is the default encoding Tools, Options, Read, International Settings?
> and Tools, Options, Send, International Settings?
> --
> Ronald Sommer
>
> "Ildhund" <jnllb@xxxxxx> wrote in message
> news:eeOWvHOXIHA.1168@xxxxxx Quote:
>> Is there a MIME expert out there who can help me understand why some
>> e-mail
>> newsletters I receive are not displaying properly in WLMail?
>>
>> The newsletter's designers are clearly struggling to get it right, but I
>> have a feeling that the problem is at their end and not with WLMail. The
>> message is single-part HTML, and displays perfectly in Yahoo's web
>> interface. However, all I get in WLMail is garbage as shown in the
>> screenshot.
>>
>> The relevant headers are:
>> ...
>> mime-version: 1.0
>> from: *****
>> to: *****
>> date: 22 Jan 2008 00:55:07 -0500
>> subject: *****
>> content-type: text/html; charset=utf-8
>> content-transfer-encoding: base64
>> Message-ID: *****
>> X-OriginalArrivalTime: 22 Jan 2008 05:55:08.0542 (UTC)
>> FILETIME=[5804F9E0:01C85CBB]
>> Content-Length: 17958
>>
>> <HTML>
>> <HEAD>
>> ...
>>
>> It looks like WLMail is trying to decode the characters following the
>> Content-Length header from base64, but because they are not encoded to
>> start
>> with, the result is garbage. They also tried using QP a few weeks ago,
>> with
>> bizarre results. Is there any need to encode at all, when the body is
>> pure
>> HTML? Or
>> --
>> Noel
>>
>>