"Ildhund" <jnllb@xxxxxx> wrote in message
news:OnbCwGTXIHA.3956@xxxxxx
Quote:
> Thanks, Robert. When I opened it as quoted-printable, I got the same bizarre
> rendering as when the sender was doing the same. I.e. every time a "="
> appears in the HTML, WLMail takes the following two characters and converts
> them as if they were QP code.
Oops. Perhaps you need to convert every instance of a real = into =3D
Do any of the lines end with =20 ? That instance of an = would not be
a "real" = ; )
Quote:
> So, a link like "href='http://" shows as
> "ttp://" in the status bar, presumably because the " 'h " have been replaced
> by whitespace because it does not decode to anything recognizable. I can
> copy the HTML to a text file and open it in IE, where it looks just like
> it's supposed to.
Another example of GIGO due to brittle design and blind unimaginative
adherence to "standards". ; ]
Quote:
>
> I've been corresponding with their techies via customer service and I see
> that the mailbot they're using has a new version dated last week, so they
> are trying. Shouldn't I suggest that they just try
> content-transfer-encoding: 7-bit? Could that break anything?
Originally it was UTF-8 so what would GIGO do if there was an 8-bit character
in the datastream? ; }
Did you try my second suggestion instead?
....
Quote:
Quote:
>> Another thing you could do is capture all the (HTML) content
>> and use it in your own Forward of it which does use BASE64
>> to see what it should look like when using that encoding method.
Actually I just realized that without a Source pane WLMail makes
this suggestion harder than it would be in OE. How do you insert
custom HTML or edit it in WLMail? Perhaps you have to use
Custom Stationery as a workaround? ; }
Good luck
Robert
---