Comment 65 for bug 207723

Revision history for this message
Michael Carpenter (mcarpent) wrote :

Looks similar. Unfortunately I can't duplicate exactly at the moment. Exchange server at work has been upgraded to 2007 and Evolution detects it as exchange 5.5 and refuses to continue. Setting the debug level does give behaviour similar to what you describe, although I'm not seeing any posts.

I see the following chain of events:

GET /owa/
401 Unauthorized
GET /owa/ (with authorization header)
302 Moved ( Location https://owaurl/owa/auth/logon.aspx?url=newowaurl )

And then Evolution complains exchange is version 5.5 and continues no further.