On Thu, Mar 19, 2009 at 4:37 PM, Carl Houseman <[email protected]> wrote: > And for some reason none of the rest of us have the problem, now or in the > past.
I've seen it happen to at least one other poster on a Sunbelt list, so it's not just Angus. I suspect most people on this list are using Outlook, so drawing conclusions from what happens to most people isn't really good strategy. Certainly, unless Angus is fabricating the whole thing and sending me different message traffic to fool me, the messages he's sending are *NOT* BASE64 encoded. It's something happening in Sunbelt's systems. And one can look at the headers of the messages see that the "Content-transfer-encoding" is *NOT* BASE64. Even if the messages Angus is sending are broken in some way, Lyris's response to them doesn't exactly make sense, either. (In fairness to Lyris: It's possible there is something else at Sunbelt, in front of or behind Lyris, that might be causing the problem.) > Has anyone actually tried to make it happen? I can run some experiments, but it will mean sending test messages (possibly a lot of them) to this list. > -----Original Message----- > From: Ben Scott [mailto:[email protected]] > Sent: Thursday, March 19, 2009 4:27 PM > To: NT System Admin Issues > Subject: Re: Windows 2008 as a fileserver > > 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. ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
