It looks like Microsoft finally implemented support for the GSSAPI SASL mechanism.
Unfortunately, they screwed it up. In their SMTP server, they respond to the command "AUTH GSSAPI" with "334 gssapi supported".
Yet more proof that the SASL specifications as currently constituted are too complex, and why IMAP should not add initial-response until the SASL specifications are fixed.
Or its more proof that M$ doesn't care about specs and choose to [re]define then as they see fit.
Can you show me where the SASL specs or SMTP SASL profile gives them license to put garbage in the challenge?
-- Kenneth Murchison Oceana Matrix Ltd. Software Engineer 21 Princeton Place 716-662-8973 x26 Orchard Park, NY 14127 --PGP Public Key-- http://www.oceana.com/~ken/ksm.pgp
