2008-02-14 10:41:02 -05:00
|
|
|
<?xml version="1.0"?>
|
|
|
|
|
|
|
|
|
|
<document>
|
|
|
|
|
|
|
|
|
|
<properties>
|
|
|
|
|
<title>Setup DavMail as a server</title>
|
|
|
|
|
<author email="mguessan@free.fr">Mickael Guessant</author>
|
|
|
|
|
</properties>
|
|
|
|
|
|
|
|
|
|
<body>
|
|
|
|
|
|
2008-10-28 18:00:59 -04:00
|
|
|
<section name="DavMail Setup as a standalone server">
|
2008-02-14 10:41:02 -05:00
|
|
|
<p>Prerequisite : Sun J2SE 1.5 or 1.6.
|
|
|
|
|
</p>
|
|
|
|
|
|
|
|
|
|
<p>Davmail Gateway can now 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 is
|
|
|
|
|
currently the only way to run DavMail on MacOS X due to poor Java support
|
|
|
|
|
(no Java 6 yet).
|
|
|
|
|
This mode was tested successfully with the Iphone and should work with
|
|
|
|
|
any phone with POP/SMTP client.
|
|
|
|
|
</p>
|
|
|
|
|
|
|
|
|
|
<p>Download the generic DavMail package from Sourceforge and uncompress it with
|
|
|
|
|
your favorite tool, e.g. on Linux:<code>unzip davmail-*.zip</code>.
|
|
|
|
|
</p>
|
|
|
|
|
<p>Prepare a davmail.properties file according to you local needs :
|
|
|
|
|
</p>
|
|
|
|
|
<source>
|
|
|
|
|
davmail.url=http://exchangeServer/exchange/
|
|
|
|
|
davmail.popPort=1110
|
|
|
|
|
davmail.smtpPort=1025
|
|
|
|
|
davmail.keepDelay=30
|
|
|
|
|
davmail.allowRemote=true
|
|
|
|
|
davmail.enableProxy=false
|
|
|
|
|
davmail.proxyHost=
|
|
|
|
|
davmail.proxyPort=
|
|
|
|
|
davmail.proxyUser=
|
|
|
|
|
davmail.proxyPassword=
|
|
|
|
|
davmail.server=true
|
2008-10-28 18:00:59 -04:00
|
|
|
davmail.bindAddress=
|
2008-11-03 07:32:56 -05:00
|
|
|
davmail.server.certificate.hash=
|
2008-02-14 10:41:02 -05:00
|
|
|
</source>
|
|
|
|
|
<p>See
|
|
|
|
|
<a href="gettingstarted.html">Getting started</a>
|
|
|
|
|
for more information on
|
|
|
|
|
the options. Make sure davmail.server is set to true (no icon tray) and allow
|
|
|
|
|
remote connections: davmail.allowRemote=true.
|
|
|
|
|
</p>
|
|
|
|
|
<p>Launch Davmail with the following command:
|
|
|
|
|
<source>nohup davmail.sh davmail.properties &</source>.
|
|
|
|
|
</p>
|
|
|
|
|
<p>Then check messages:
|
|
|
|
|
<source>tail -f nohup.out</source>
|
|
|
|
|
</p>
|
2008-10-28 18:00:59 -04:00
|
|
|
</section>
|
|
|
|
|
|
|
|
|
|
<section name="DavMail Setup as a JEE Web Application">
|
|
|
|
|
<p>Prerequisites : Sun J2SE 1.5 or 1.6 and any JEE compliant web container
|
|
|
|
|
</p>
|
|
|
|
|
|
|
|
|
|
<p>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.
|
|
|
|
|
</p>
|
|
|
|
|
|
|
|
|
|
<p>Download the war DavMail package from Sourceforge <code>davmail-*.war</code>,
|
|
|
|
|
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.
|
|
|
|
|
</p>
|
|
|
|
|
<p>The davmail.properties configuration file is then available under
|
|
|
|
|
<code>davmail-*/WEB-INF/classes</code>.
|
|
|
|
|
</p>
|
|
|
|
|
|
|
|
|
|
<p>See above and
|
2008-02-14 10:41:02 -05:00
|
|
|
<a href="gettingstarted.html">Getting started</a>
|
2008-10-28 18:00:59 -04:00
|
|
|
for more information on
|
|
|
|
|
the options. Make sure davmail.server is set to true (no icon tray) and allow
|
|
|
|
|
remote connections: davmail.allowRemote=true.
|
2008-02-14 10:41:02 -05:00
|
|
|
</p>
|
|
|
|
|
</section>
|
|
|
|
|
</body>
|
|
|
|
|
</document>
|
