Wed May 11 08:40:25 CEST 2016 (1462948825510) CaldavConnection-14581 22 ERROR Ews endpoint not available at /ews/exchange.asmx status 500 .buildSessionInfo(EwsExchangeSession.java:245) Wed May 11 08:40:24 CEST 2016 (1462948824974) CaldavConnection-14581 20 DEBUG Ews endpoint not available at /ews/exchange.asmx status 500 .buildSessionInfo(EwsExchangeSession.java:234) Wed May 11 08:40:24 CEST 2016 (1462948824705) CaldavConnection-14581 19 DEBUG Authentication form not found at, will try direct EWS access .formLogin(EwsExchangeSession.java:159) Wed May 11 08:40:24 CEST 2016 (1462948824703) CaldavConnection-14581 18 DEBUG Form based authentication detected .formLogin(EwsExchangeSession.java:155) Log messages from Thunderbird attempting to connect follows: (Outlook 2010 and Thunderbird), and the computer has been rebooted, and I have tried stopping and starting both davmail the clients Same version of davmail, and with an Office 365 account for the same

(same model computer, with same OS in the same domain, running the exact The curious thing is that a colleague's setup that should be identical Weekend, when davmail suddenly started failing again. May 5th, and that worked fine until either early Monday or sometime this I changed the davmail.url setting to Kayvan Sylvan's setting on Thursday To: davmail suddenly started failing again

Mickael Well sent this earlier and I saw the same thing happen at my domain: => they probably decided to make a webmail only entry The fact that it used to work with other urls is just a side effect ofД®xchange standard setup that publishes all the services at the same place. > The mysteries of Office365 will never cease. > But why was it still working for my colleague with a setup identical to > Overnight the following stopped working: Those API might make it easier to get the application registered, but I'm not sure if it helps otherwise.>David Well sent this earlier and I saw the same thing happen at my domain: The device flow can not expect to use only the built-in pre-registered applications, but needs to be configurable for any other client application.Д«oth these implement own proprietary interfaces to read and process mail that also require the OAuth2 token ( #96). If getting a pre-registered application for parsedmac approved on Google and Microsoft is difficult, users can register their own apps. Both Google and Microsoft will require own registrations, as will require any other authorization server. If IMAP server did not support device flow, the token would need to be acquired in some other way and manually configured.ДЄll these require the application registered for parsedmac. It would then need a writable file where it can save the received token for next launch. Once user has authenticated on that page, parsedmac would receive the token. On launch when parsedmac does not find the token, it would print out the URL and instructions so that the admin can perform the authentication. I believe Google and Microsoft both support the device flow, so that would be great. The imapclient seems to expect the token already acquired. It seems the imapclient OAuth2 support is behind the use of mailsuite, that wraps it to unconditionally only perform the user+password login.Д«ut if we get past that limitation, we still need the token.

Mozilla davmail outlook office365