![davmail domain davmail domain](https://1.bp.blogspot.com/-JThTkKwmlhI/Wu2RzEdMUQI/AAAAAAAACdA/IqgKGXCw7tE4Ej8QwwRzbhzWg4tEY56VACLcBGAs/s1600/davmail-settings.png)
Note: this tutorial uses as the example corporate mail domain (OWA) and Gmail as the non-corporate mail service. You are capable of appropriately securing services, e.g.However, there should be few differences if you are running Debian, and it should be easy enough to adapt this configuration to accommodate RPM-based distributions You have a Gmail account with POP enabled (this tutorial could be easily adapted to other service providers).You have the OWA service configured on your Exchange server, e.g.If you want the quickest and simplest route to getting mail from OWA into your MUA of choice, and are fine with it being pulled down into the local folders of a MUA, you might be better off using Davmail in its desktop configuration and without the complexity of Postfix + Fetchmail + Courier IMAP. This particular configuration is perhaps best suited to a more advanced desktop configuration, else as the basis for a server-based resource where you may have multiple desktops and want to synchronize mail across devices. This tutorial explains how to use a recipe of Davmail + Fetchmail + Postfix + Courier IMAP to interface standards-based e-mail clients with Exchange‚Äôs OWA, and to integrate corporate and non-corporate e-mail accounts into a single inbox and one that is not buried inside the store of the MUA. Whilst Exchange has the capability to provide an IMAP and/or POP service these are frequently disabled, leaving Outlook Web Access (OWA) as the only remaining hope for users of non-Microsoft mail user agents (MUAs). Copy the final link (with the token in the parameters) showing an empty page, back to the DavMail dialog.Īfter successful authentication, close davmail and locate the davmail.Many enterprises use Microsoft Exchange for corporate e-mail, and there is frequently no avoiding its use regardless of where you might sit in the organization or the freedom afforded to you in terms of desktop configuration. This opens a dialog of DavMail with a link which you can use in any browser, authenticate to Microsoft and provide the SMS/auth token and authorize the DavMail application.
![davmail domain davmail domain](http://lh3.ggpht.com/_vaWw1rY23DU/TWKXWm9CtlI/AAAAAAAAAmw/pxR8H_2hifc/image_thumb%5B16%5D.png)
The easiest way to trigger the MFA authentication is to open the CalDAV interface at and log in with your email and password. Install DavMail on a desktop system and keep the default values, except change the authentication method to O365Interactive. The workaround is to register through the desktop version and then copy the authentication token to the headless deployment. Unfortunately the headless version does not yet have an oauth workflow to log in with the two-factor authentication. For a single desktop client, the first is fine, but I wanted to have access from my phone too. There are two possible operation modes, one as a local deamon to run on desktop systems and one server/headless version. It works by being a client to EWS and then exposing a server interface on the usual ports shifted up by 1000 (e.g. This leaves the option to use the provided webinterface which I think is inconvenient.įortunately there exists the DavMail project, which is a bridge between the ExchangeWebServices and open protocols.
![davmail domain davmail domain](https://faq.redit.co.uk/wp-content/uploads/2019/11/0001.png)
Recently I started at an institution which uses a groupware which is deliberately incompatible with open groupware protocols such as IMAP,SMTP,CalDAV.