886261 - IMAP GSSAPI auth fails with "BAD Command Error. 10" on MS Exchange

Status: RESOLVED INCOMPLETE

(MailNews Core :: Networking: IMAP, defect)

Description

[Martin Wilck]

Attachment: tb-130624-1.log

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:20.0) Gecko/20100101 Firefox/20.0 (Beta/Release)
Build ID: 20130401133302

Steps to reproduce:

I am using Thunderbird (17.0.x for Linux Fedora 18) as IMAP client on an Exchange 2007 server.  Recently the IMAP/GSSAPI authentification that I've used successfully for years stopped working.



Actual results:

Status bar shows "sending login information ..." then nothing happens any more (under Linux; under Windows I get a popup "the Kerberos/GSSAPI ticket was rejected"). The missing popup under Linux is probably a GNOME3 issue, don't worry about it.

In the log (NSPR_LOG_MODULES='imap:5,negotiateauth:5,gssapi:5,timestamp', see attachment),  I see:

2ed0e800:pdbrd21e.pdb.fsc.net:NA:SendData: 2 authenticate GSSAPI
ReadNextLine [stream=303afc10 nb=3 needmore=0]
2f79e800:pdbrd21e.pdb.fsc.net:NA:CreateNewLineFromSocket: +
2ed0e800:pdbrd21e.pdb.fsc.net:NA:SendData: YIIeCgYJKoZIhvcSAQICAQ ...
[...]
2f79e800:pdbrd21e.pdb.fsc.net:NA:CreateNewLineFromSocket: * BAD Command Error. 10
ReadNextLine [stream=303afc10 nb=4294967295 needmore=0]
2f79e800:pdbrd21e.pdb.fsc.net:NA:CreateNewLineFromSocket: clearing IMAP_CONNECTION_IS_OPEN - rv = 80470002
2f79e800:pdbrd21e.pdb.fsc.net:NA:TellThreadToDie: close socket connection
2f79e800:pdbrd21e.pdb.fsc.net:NA:CreateNewLineFromSocket: (null)
authlogin failed
marking auth method 0x1000000 failed

this sequence occurs repeatedly.


Expected results:

Login succeeds.

Comment 1

[Martin Wilck]

I am told by our IT guys that the occurence of this problem coincides with a number of Win2K3 patches installed on the Exchange server: KB2820197, KB2829361, KB2804577, KB2804576, KB2838727.

Comment 2

[Wayne Mery (:wsmwk)]

Martin, do you still see this problem when using a current version of Thunderbird??

Comment 3

[Wayne Mery (:wsmwk)]

quite a few other bug reports - https://mzl.la/2iJve0S - in the era when this bug was reported