You mean "handling of double quotes in Sender/Recipient headers"? A problem, definitely. And yes, non-compliant. But if you want to browbeat Outlook/Express for this level of non-compliance, I can quite easily tear into Thunderbird (check Bugzilla for RFC noncompliance), Eudora, Pine, etc., et al. Microsoft copied the BSD stack, as was their perfect right by licensing. But if you want to attack internet security in the bad old NT days I can point to the numerous patches that needed to be applied to everything from my Win 98 system, to the RHL and even *gasp* OpenBSD. I even had my RHL system rootkitted twice. So I'm not entirely sure what point you're making here, or indeed its relevance to your hypothesis "Microsoft won't support Silverlight on anything but IE/Win". Robert -----Original Message----- From: thelist-bounces at lists.evolt.org [mailto:thelist-bounces at lists.evolt.org] On Behalf Of Shawn K. Quinn Sent: Sunday, May 27, 2007 2:16 PM To: thelist at lists.evolt.org Subject: Re: [thelist] MS Silverlight > the way. Microsoft made Outlook (and Outlook Express) which was and > is in many ways either non-compliant with the RFCs in question > (2822, I think) or at least in violation of commonly accepted > principles of netiquette. Microsoft copied the BSD TCP/IP stack, > and said to heck with *many* good practices embodied therein, one > of which made it very easy to UDP port scan a Windows NT box back > in the day.