On Thu, Mar 19, 2009 at 2:36 PM, Carl Houseman <[email protected]> wrote: > ... something changed in his local configuration, it would appear, > causing mail to go out as Base64 RTF for the text content.
We investigated this, Angus's mail appears to be going out with content-type text/html and with quoted-printable encoding, all in strict RFC compliance, as far as I could see. The headers seemed very vanilla. The one thing of note was a line continuation for the character-encoding for the content-type. That's perfectly legal, but perhaps Lyris is brain damaged about it. In any event, Lyris isn't setting the encoding type to BASE64, so even if Lyris thinks it *should* be re-encoding the message for some reason, it's not doing it right. Check the archives for more details. It was like a month ago. -- Ben ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
