powermail-discuss Digest #2959 - Wednesday, December 7, 2011
CTM support AWOL again: Re(3): HTML/RTF messages have odd characters - ho
by "Winston Weinmann" <[email protected]>
Re: Re(2): HTML/RTF messages have odd characters - how to avoid?
by "Ben Kennedy" <[email protected]>
----------------------------------------------------------------------
Subject: CTM support AWOL again: Re(3): HTML/RTF messages have odd characters -
how to avoid?
From: "Winston Weinmann" <[email protected]>
Date: Tue, 6 Dec 2011 23:54:06 -0500
No support from CTM. This is incredibly frustrating.
In some cases it is extremely embarrassing to send out poorly formatted mail.
Because I don't know what will show up when someone receives a message,
effectively I can't use HTML mail. Why did CTM even bother to add the feature?
- Winston
Winston wrote:
>>If you view the full headers for one of the "garbled" examples sent back
>>to you by your correspondent, what mail client ("X-Mailer: XXXX") and
>>text encoding ("Content-type: text/*; charset=XXXX") are used in his message?
>
>Here's what the response had:
>
>X-Mailer: Microsoft Office Outlook 11
>
>Content-Type: multipart/alternative;
> boundary="----=_NextPart_000_003D_01CC8B3C.19364F30"
>
>
>- Winston
>
>
>Ben Kennedy wrote:
>
>>On 29 Nov 2011, at 12:51 pm, Winston Weinmann wrote:
>>
>>> When I use PowerMail's "Rich Text" HTML format for messages some
>>people receive the message with odd characters inserted like this:
>>
>>Winston sent me an example directly (both as he sent out, and as
>>forwarded back to him by a recipient claiming it was mis-formatted).
>>The original looked correct to me in both Apple Mail and PowerMail.
>>
>>The appearance of the garbled result (as provided by your correspondent)
>>is consistent with how the text would appear if originally encoded in
>>UTF-8 but incorrectly decoded as "Windows 1252" (which is similar to ISO-
>>Latin-1 but a bit different. <http://en.wikipedia.org/wiki/Windows-1252>
>>
>>My inference: the recipient is using a broken (probably Windows-based)
>>mail client that does not properly understand UTF-8 text encoding.
>>
>>If you view the full headers for one of the "garbled" examples sent back
>>to you by your correspondent, what mail client ("X-Mailer: XXXX") and
>>text encoding ("Content-type: text/*; charset=XXXX") are used in his message?
>>
>>-b
>>
>>--
>>Ben Kennedy, chief magician
>>Zygoat Creative Technical Services
>>http://www.zygoat.ca
>>
>>
>
>
>
----------------------------------------------------------------------
Subject: Re: Re(2): HTML/RTF messages have odd characters - how to avoid?
From: "Ben Kennedy" <[email protected]>
Date: Tue, 6 Dec 2011 23:14:07 -0800
On 30 Nov 2011, at 2:24 pm, Winston Weinmann wrote:
>> If you view the full headers for one of the "garbled" examples sent back
>> to you by your correspondent, what mail client ("X-Mailer: XXXX") and
>> text encoding ("Content-type: text/*; charset=XXXX") are used in his message?
>
> Here's what the response had:
>
> X-Mailer: Microsoft Office Outlook 11
>
> Content-Type: multipart/alternative;
> boundary="----=_NextPart_000_003D_01CC8B3C.19364F30"
Hmm. That doesn't answer my question, because the "Content-type: text" header
will be in one of the encapsulated MIME parts later in the message.
Unfortunately, PowerMail decomposes multipart MIME messages for internal
storage, so there's no way to reliably examine the raw message source any more.
(If you receive another such message in the future, you could examine it e.g.
using Mail.app.)
(Pardon my delay following up here. In any case, my original suspicion is that
the recipient's client -- Outlook 11, I guess -- is mis-handling the message on
receipt. But I might be wrong.)
-b
--
Ben Kennedy, chief magician
Zygoat Creative Technical Services
http://www.zygoat.ca
----------------------------------------------------------------------
End of powermail-discuss Digest
