Prerequisite : Sun J2SE 1.5 or 1.6.

Davmail Gateway can run in server mode as a gateway between the mail client and the Outlook Web Access (Exchange) server. In server mode Davmail can run on any Java supported platform. This mode was tested successfully with the Iphone and should work with any phone with POP/IMAP/SMTP/LDAP/Caldav/Carddav client. In this mode many users can share the same DavMail instance.

Download the generic DavMail package from Sourceforge and uncompress it with your favorite tool, e.g. on Linux: unzip davmail-*.zip.

Prepare a davmail.properties file according to your local needs :

See Getting started for more information on the options. Make sure davmail.server is set to true (no icon tray) and allow remote connections: davmail.allowRemote=true.

To disable a service, set an empty port value.

Launch Davmail with the following command: nohup davmail.sh davmail.properties &.

Then check messages: tail -f nohup.out

A new experimental davmailservice.exe wrapper is available in the windows package.

To register DavMail as a windows service, use: davmailservice install or sc create DavMail binPath= \path\to\davmailservice.exe type= own start= auto

Prerequisites : Sun J2SE 1.5 or 1.6 and any JEE compliant web container

Davmail Gateway can now be deployed in any JEE application server using the war package. In this mode, DavMail listener threads run inside the application server and follow the web application lifecycle (start, stop, deploy, undeploy). The following items describe Tomcat deployment, details will vary according to the specific application server available.

Download the war DavMail package from Sourceforgedavmail-*.war, and deploy it inside the application server. In Tomcat, this means copy the war file to the webapps directory. If Tomcat is started and automatic deployment enabled (this is the default configuration), the package is automatically uncompressed and started.

The davmail.properties configuration file is then available under davmail-*/WEB-INF/classes.

Note: DavMail does not use the standard Tomcat HTTP connector and uses the same listeners in war and server modes. This means the HTTP port for Caldav url is specified in davmail.properties

See above and Getting started for more information on the options. Make sure davmail.server is set to true (no icon tray) and allow remote connections: davmail.allowRemote=true.