Actually, Exchange didn't get around to implementing this recently - it's been in Windows 2000 SMTP (which is what Exchange uses) since the release of Windows 2K. I'm dredging my memory here, but I believe that the code for this was locked down during the ID stage of RFC 2554, before the RFC was released. As I recall, it was interop-tested at the time, but there wasn't a lot to test against and I don't recall the results. I've passed this along to the Exchange folks, who say it's a known issue that wasn't fixed when discovered out of fear of breaking anything that might have relied on this behavior. If this behavior is breaking other apps, that would increase the impetus to fix it.
-- jeff Jeff Stephenson Software Developer Microsoft Outlook > -----Original Message----- > From: Ken Murchison <[EMAIL PROTECTED]> > Subject: Re: Exchange server has a broken SASL implementation ... > However, if there is/was any question about the specs, there > are mailing lists that can be contacted for clarification. > Interop testing could be done with non-MS products. The CMU > SASL library comes with test harnesses which can be used for > testing. There are at least 2 major MTAs (sendmail, postfix) > which use CMU SASL that could have been consulted for comparison.
