I tried several Base64 decoders (the top 5-6 hits on google), and only one came through with anything, and several of the characters appear to be substituted for others. So, I'd say that something is wrong. I'm not saying that this is the exact same issue as we've faced before. It's just that we've had issues before where the whole process of sending encoded messages to the list has resulted in problems with people receiving them (e.g. where Lyris has added un-encoded footers to the bottom of encoded messages).
Here's part of Angus' message: On 19 Mar 2009 at 8:09, David Lum wrote: > I doÿ´t have an answer for you - I have only two 2008 Server deployed - but > the speed between the Vistaÿß à 2008 Server should be significantly faster > than XP - 2008. FWIW, I'm not saying any messages are blank. I said that Outlook 2003 would display a blank message went it couldn't properly decode certain encoded messages. Cheers Ken -----Original Message----- From: Carl Houseman [mailto:[email protected]] Sent: Friday, 20 March 2009 2:07 PM To: NT System Admin Issues Subject: RE: Windows 2008 as a fileserver This particular issue is a block of Base64 encoded text substituted for the actual text of a message. I wouldn't call it "garbled" (randomly mixed up or corrupted) and it's definitely not blank. Clearly the issue has its origins with the sender - either settings or an interim mail-handling device changing the message in a way that Lyris can't cope with. Carl -----Original Message----- From: Ken Schaefer [mailto:[email protected]] Sent: Thursday, March 19, 2009 10:53 PM To: NT System Admin Issues Subject: RE: Windows 2008 as a fileserver Not sure which "none" you're referring to. We've had heaps of problems with "blank" emails and garbled ones over the past 12-24 months (I only have 12 months worth of mail for this list). Cheers Ken -----Original Message----- From: Carl Houseman [mailto:[email protected]] Sent: Friday, 20 March 2009 7:38 AM To: NT System Admin Issues Subject: RE: Windows 2008 as a fileserver And for some reason none of the rest of us have the problem, now or in the past. Has anyone actually tried to make it happen? Carl -----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. -- Ben ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
