
Obviously, this means that Evolution client is not totally successful in communicating with the server for some reason. I ended up going back to the setup I had before, using Davmail to proxy with exchange but I am interested in getting this fixed as I'd rather just go straight to. There are no ‘error’ messages as such, just ‘authentication’ requests (quite sporadically) for the account and access to the server’s ‘Global Address book’ (constantly, e.g. Using davmail to convert IMAP/SMTP to EWS (Exchange Web Services) to that Office365 server, allows emails to be processed much faster, despite the intervening conversions and extra network traffic. After getting the EWS resource set up 'properly', it shows the folder structure in the subscriptions, but nothing shows up in Kmail's folder listings, nor in Korganizer's calendars. Obviously, I can try to find out if the MS Exchange server is up to date and will do in due course. I can access my account quite successfully with a web browser (Firefox), but since I have several email accounts, I prefer to access them all with my evolution application. I am not using a web browser for the email access, but Evolution/EWS. stored in the Drafts folder, as shown in Create an email message by using EWS. If both your browsers and Exchange/IIS have been updated since then, I assume that your connections would be secure and work, but if one or both weren’t upgraded you could still be using TLS1.2 instead of TLS2.0 or some other similar problem. Using Microsoft/Office 365 OAUTH + EWS and Ms Graph API. Features Parses draft and 1. Since you don’t provide any exact error messages, I can only wildly guess that your messages could also be SSL related since the encryption and Diffie-Heilman handshake vulnerabilities were discovered a year ago. When used with Elasticsearch and Kibana (or Splunk), it works as a self-hosted open source alternative to commercial DMARC report processing services such as Agari Brand Protection, Dmarcian, OnDMARC, ProofPoint Email Fraud Defense, and Valimail.

You may also have to experiment with different web browsers. Today, last I heard the pages be straight HTML and not require any proprietary MS code, but YMMV and if Exchange is not latest versions would be a factor. Also, if the Exchange is not currently patched could be a major factor. Thunderbird just connects to Davmail (which is running on your localhost) and davmail connects to your exchange server.

DAVMAIL EWS CODE
You may need to determine the version of your Exchange Server, over the years Exchange Web Services (Accessing Exchange using a Web Browser) has varied how much the page code requires Internet Explorer to provide proprietary code (like ActiveX long ago). Davmail is acting as a man-in-the-middle to your exchange server, relaying info to and from: thunderbird <-> davmail <-> exchange.) and you should be in there like a dirty shirt.
DAVMAIL EWS FULL
Use your full OWA domain as your username to log in (i.e. Use that as your OWA URL in DavMail and also be sure that 'Enable EWS' is selected in the Advanced tab of DavMail settings. Although I don’t support Exchange today, am somewhat familiar with its history over the years. Solution 2 Go to and you should be redirected to a /owa/ address.
