[Davmail-users] Not able to auth to Office 365 calendar any more

[Christopher Samuel]

Hi folks,

I'm struggling with Office 365 at the moment, their IMAP and SMTP
service (accessed directly) is fine, but when I access the calendar
using Davmail and Caldav from Thunderbird+Lightning I'm getting auth
failures.

2017-02-23 11:21:20,251 WARN [CaldavConnection-44376] org.apache.commons.httpclient.HttpMethodBase - Cookie rejected: "$Version=0; esctx=[cookie elided]; $Path=/; $Domain=.login.microsoftonline.com". Illegal domain attribute ".login.microsoftonline.com". Domain of origin: "login.microsoftonline.com"

2017-02-23 11:21:21,011 ERROR [CaldavConnection-44376] davmail.exchange.ExchangeSession - Authentication failed: invalid user or password, retry with domain\user or use default domain setting

I'm using the "auto" protocol to the endpoint https://outlook.office365.com/owa/

This was working for me for ages, so I'm guessing something has
changed at their end, any ideas anyone?

Yesterday it broke for a while in the morning (again) but
then was working in the afternoon. Very odd.

All the best!
Chris

[Christopher Samuel]

Post by Christopher Samuel
This was working for me for ages, so I'm guessing something has
changed at their end, any ideas anyone?

I found that changing the protocol from "Auto" to "EWS" fixed the
problem. I tried "WebDav" first but that was having the same issue as
before, and so obviously was the one being selected by "Auto".

Perhaps a bug?

All the best,
Chris

[Mickaël Guessant]

Post by Christopher Samuel

Post by Christopher Samuel
This was working for me for ages, so I'm guessing something has
changed at their end, any ideas anyone?

I found that changing the protocol from "Auto" to "EWS" fixed the
problem. I tried "WebDav" first but that was having the same issue as
before, and so obviously was the one being selected by "Auto".
Perhaps a bug?

Just a little bit of context: when EWS did not exist DavMail accessed
Exchange through WebDav, then Exchange 2007 added EWS support, but
WebDav was still the main entry point.

=> auto mode is a best effort at choosing the right protocol, but will
not always work

In recent Exchange versions (including Office365), WebDav is no longer
supported

=> auto mode is no longer the best option, direct EWS is the way to go

By the way the reference URL for Office365 is
https://outlook.office365.com/EWS/Exchange.asmx