mirror of
https://github.com/moparisthebest/davmail
synced 2024-12-13 03:02:22 -05:00
Doc: fixes and updates on ssl setup and build
git-svn-id: http://svn.code.sf.net/p/davmail/code/trunk@1514 3d1905a2-6b24-0410-a738-b14d5a86fcbd
This commit is contained in:
parent
af6afe9042
commit
51c2d3b1a0
@ -25,8 +25,10 @@
|
|||||||
</li>
|
</li>
|
||||||
</ul>
|
</ul>
|
||||||
</li>
|
</li>
|
||||||
<li>Download and unzip ant from <a href="http://ant.apache.org/">ant.apache.org</a>,
|
<li>Check if you already have Apache Ant installed :<br/>
|
||||||
add ant/bin full path to the PATH environment variable
|
<source>ant -version</source><br/>
|
||||||
|
If you don't, download and unzip ant from <a href="http://ant.apache.org/">ant.apache.org</a>,
|
||||||
|
add ant/bin full path to the PATH environment variable.
|
||||||
</li>
|
</li>
|
||||||
<li>Get DavMail source package from sourceforge and uncompress it:
|
<li>Get DavMail source package from sourceforge and uncompress it:
|
||||||
<source>tar xvzf davmail-src-*.tgz</source>
|
<source>tar xvzf davmail-src-*.tgz</source>
|
||||||
|
@ -18,7 +18,7 @@
|
|||||||
<strong>How do I create a WIRE debug log ?</strong>
|
<strong>How do I create a WIRE debug log ?</strong>
|
||||||
</p>
|
</p>
|
||||||
<p>In DavMail trackers and forums, I often ask for a WIRE debug log. To create this
|
<p>In DavMail trackers and forums, I often ask for a WIRE debug log. To create this
|
||||||
log file, you will need to change DavMail settings under the advanced tab.
|
log file, you will need to change DavMail settings under the Logging tab.
|
||||||
Set the WIRE logging category to DEBUG level.
|
Set the WIRE logging category to DEBUG level.
|
||||||
</p>
|
</p>
|
||||||
<p>You can then reproduce your issue and send the log file to
|
<p>You can then reproduce your issue and send the log file to
|
||||||
@ -83,7 +83,7 @@
|
|||||||
<li>Select the IIS role, then add Role Services</li>
|
<li>Select the IIS role, then add Role Services</li>
|
||||||
<li>Add WebDav Publishing (both Cas server and Mailbox Server)</li>
|
<li>Add WebDav Publishing (both Cas server and Mailbox Server)</li>
|
||||||
<li>On the Mailbox server, add the ISAPI extensions Role Service to the IIS role</li>
|
<li>On the Mailbox server, add the ISAPI extensions Role Service to the IIS role</li>
|
||||||
<li>On the Default Web Site (each server) , enable WebDav</li>
|
<li>On the Default Web Site (each server), enable WebDav</li>
|
||||||
<li>Should not have to enable any additional WebDav rules</li>
|
<li>Should not have to enable any additional WebDav rules</li>
|
||||||
<li>Install the server roles</li>
|
<li>Install the server roles</li>
|
||||||
<li>Create a test mailbox (see Exchange Docs)</li>
|
<li>Create a test mailbox (see Exchange Docs)</li>
|
||||||
@ -99,9 +99,13 @@
|
|||||||
<p>
|
<p>
|
||||||
<strong>Is Exchange 2010 supported ?</strong>
|
<strong>Is Exchange 2010 supported ?</strong>
|
||||||
</p>
|
</p>
|
||||||
<p>Currently, the answer is no. As Microsoft decided to drop WebDav support in Exchange 2010, DavMail
|
<p>As Microsoft decided to drop WebDav support in Exchange 2010, I had to implement a new backend from
|
||||||
will not work with this new version. Experimental Exchange Web Service support compatible with
|
scratch to support the new Exchange Web Services interface. This support is still experimental,
|
||||||
Exchange 2010 is available in subversion, but not complete yet.
|
but is working quite well. However, you still need to enable it manually in .davmail.properties
|
||||||
|
with the following line:
|
||||||
|
<br/>
|
||||||
|
<source>davmail.enableEws=true</source>
|
||||||
|
<br/>
|
||||||
</p>
|
</p>
|
||||||
</subsection>
|
</subsection>
|
||||||
|
|
||||||
@ -126,19 +130,10 @@
|
|||||||
<p>Communication between the messaging client and DavMail is
|
<p>Communication between the messaging client and DavMail is
|
||||||
<em>not</em>
|
<em>not</em>
|
||||||
secured by default. This is not an issue in standalone mode as all communication is local, but you
|
secured by default. This is not an issue in standalone mode as all communication is local, but you
|
||||||
may want
|
may want to improve this in server (shared) mode.
|
||||||
to improve this in server (shared) mode.
|
|
||||||
</p>
|
</p>
|
||||||
<p>This is quite simple: you just need to get a server certificate in PKCS12 or JKS format and add it in
|
<p>This is quite simple: you just need to get a server certificate in PKCS12 or JKS format and add it in
|
||||||
the key store section in DavMail settings, see <a href="gettingstarted.html">Getting
|
the key store section in DavMail settings, see <a href="sslsetup.html">SSL Setup</a>.
|
||||||
started</a>.
|
|
||||||
You need to choose the key store type in davmail.ssl.keystoreType: PKCS12 for .p12 file and JKS for
|
|
||||||
java generated key stores. Then set the full path to your certificate file in
|
|
||||||
davmail.ssl.keystoreFile
|
|
||||||
and the certificate file password in davmail.ssl.keystorePass. You may also have a key password in
|
|
||||||
addition
|
|
||||||
to the file password, specify it in davmail.ssl.keyPass. This will switch all DavMail services to
|
|
||||||
SSL mode: POP3S/IMAPS/SMTPS/HTTPS/LDAPS.
|
|
||||||
</p>
|
</p>
|
||||||
|
|
||||||
<p>
|
<p>
|
||||||
@ -166,8 +161,7 @@ calendar.debug.log.verbose=true]]></source>
|
|||||||
<p>Lightning 0.9 mail notifications are broken, activate
|
<p>Lightning 0.9 mail notifications are broken, activate
|
||||||
Caldav notifications to outbox instead:
|
Caldav notifications to outbox instead:
|
||||||
</p>
|
</p>
|
||||||
<p>Check the following parameter in Thunderbird, it should be set
|
<p>Check the following parameter in Thunderbird, it should be set to true
|
||||||
to true
|
|
||||||
</p>
|
</p>
|
||||||
<source>calendar.caldav.sched.enabled=true</source>
|
<source>calendar.caldav.sched.enabled=true</source>
|
||||||
|
|
||||||
@ -196,7 +190,7 @@ calendar.debug.log.verbose=true]]></source>
|
|||||||
<p>
|
<p>
|
||||||
<strong>Message deleted over IMAP still visible through OWA</strong>
|
<strong>Message deleted over IMAP still visible through OWA</strong>
|
||||||
</p>
|
</p>
|
||||||
<p>Message move does not exist in IMAP, thus the move is a delete followed by a create.
|
<p>Message move does not exist in IMAP, thus the move is a copy followed by a delete.
|
||||||
And a delete is not immediate with IMAP: you need to EXPUNGE the folder to actually
|
And a delete is not immediate with IMAP: you need to EXPUNGE the folder to actually
|
||||||
delete a message.
|
delete a message.
|
||||||
</p>
|
</p>
|
||||||
|
@ -24,6 +24,8 @@
|
|||||||
pkcs12 -validity 3650 -dname cn=davmailhostname.company.com,ou=davmail,o=sf,o=net
|
pkcs12 -validity 3650 -dname cn=davmailhostname.company.com,ou=davmail,o=sf,o=net
|
||||||
</source>
|
</source>
|
||||||
|
|
||||||
|
<p>Note to iPhone users: iOS does not support the default DSA algorithm, make sure you use an RSA key pair</p>
|
||||||
|
|
||||||
<p>Then add this keystore to DavMail settings:
|
<p>Then add this keystore to DavMail settings:
|
||||||
</p>
|
</p>
|
||||||
<source><![CDATA[
|
<source><![CDATA[
|
||||||
@ -31,12 +33,16 @@ davmail.ssl.keystoreType=PKCS12
|
|||||||
davmail.ssl.keyPass=password
|
davmail.ssl.keyPass=password
|
||||||
davmail.ssl.keystoreFile=davmail.p12
|
davmail.ssl.keystoreFile=davmail.p12
|
||||||
davmail.ssl.keystorePass=password]]></source>
|
davmail.ssl.keystorePass=password]]></source>
|
||||||
<p>Restart DavMail, all DavMail listeners will switch to secure mode. You will also need to enable SSL
|
<p>If your already have your keystore in JKS format, just set keystoreType to JKS in DavMail
|
||||||
in
|
settings. keystorePass is the password used to open the KeyStore, keyPass protects the private key
|
||||||
client applications and manually accept the certificate as it's not signed by a trusted
|
inside the KeyStore.
|
||||||
Certification Authority.
|
</p>
|
||||||
|
<p>Restart DavMail, all DavMail listeners will switch to secure mode: POP3S/IMAPS/SMTPS/HTTPS/LDAPS.
|
||||||
|
You will also need to enable SSL in client applications and manually accept the certificate as it's
|
||||||
|
not signed by a trusted Certification Authority.
|
||||||
</p>
|
</p>
|
||||||
</subsection>
|
</subsection>
|
||||||
|
|
||||||
<subsection name="DavMail to Exchange">
|
<subsection name="DavMail to Exchange">
|
||||||
<p>In most cases, using https in OWA url is enough to secure communication between DavMail and Exchange.
|
<p>In most cases, using https in OWA url is enough to secure communication between DavMail and Exchange.
|
||||||
However, with Exchange servers setup to require mutual authentication, you will have to register
|
However, with Exchange servers setup to require mutual authentication, you will have to register
|
||||||
|
Loading…
Reference in New Issue
Block a user