From 51c2d3b1a0c3b15b38146120e634d5b3138a77e2 Mon Sep 17 00:00:00 2001 From: mguessan Date: Thu, 21 Oct 2010 09:05:14 +0000 Subject: [PATCH] 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 --- src/site/xdoc/build.xml | 6 ++++-- src/site/xdoc/faq.xml | 32 +++++++++++++------------------- src/site/xdoc/sslsetup.xml | 14 ++++++++++---- 3 files changed, 27 insertions(+), 25 deletions(-) diff --git a/src/site/xdoc/build.xml b/src/site/xdoc/build.xml index 5bf4e2fe..6082215b 100644 --- a/src/site/xdoc/build.xml +++ b/src/site/xdoc/build.xml @@ -25,8 +25,10 @@ -
  • Download and unzip ant from ant.apache.org, - add ant/bin full path to the PATH environment variable +
  • Check if you already have Apache Ant installed :
    + ant -version
    + If you don't, download and unzip ant from ant.apache.org, + add ant/bin full path to the PATH environment variable.
  • Get DavMail source package from sourceforge and uncompress it: tar xvzf davmail-src-*.tgz diff --git a/src/site/xdoc/faq.xml b/src/site/xdoc/faq.xml index f6df1186..adc3d412 100644 --- a/src/site/xdoc/faq.xml +++ b/src/site/xdoc/faq.xml @@ -18,7 +18,7 @@ How do I create a WIRE debug log ?

    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.

    You can then reproduce your issue and send the log file to @@ -83,7 +83,7 @@

  • Select the IIS role, then add Role Services
  • Add WebDav Publishing (both Cas server and Mailbox Server)
  • On the Mailbox server, add the ISAPI extensions Role Service to the IIS role
    • -
  • On the Default Web Site (each server) , enable WebDav
    • +
  • On the Default Web Site (each server), enable WebDav
  • Should not have to enable any additional WebDav rules
  • Install the server roles
  • Create a test mailbox (see Exchange Docs)
    • @@ -99,9 +99,13 @@

    Is Exchange 2010 supported ?

    -

    Currently, the answer is no. As Microsoft decided to drop WebDav support in Exchange 2010, DavMail - will not work with this new version. Experimental Exchange Web Service support compatible with - Exchange 2010 is available in subversion, but not complete yet. +

    As Microsoft decided to drop WebDav support in Exchange 2010, I had to implement a new backend from + scratch to support the new Exchange Web Services interface. This support is still experimental, + but is working quite well. However, you still need to enable it manually in .davmail.properties + with the following line: +
    + davmail.enableEws=true +

    @@ -126,19 +130,10 @@

    Communication between the messaging client and DavMail is not secured by default. This is not an issue in standalone mode as all communication is local, but you - may want - to improve this in server (shared) mode. + may want to improve this in server (shared) mode.

    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 Getting - started. - 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. + the key store section in DavMail settings, see SSL Setup.

    @@ -166,8 +161,7 @@ calendar.debug.log.verbose=true]]>

    Lightning 0.9 mail notifications are broken, activate Caldav notifications to outbox instead:

    -

    Check the following parameter in Thunderbird, it should be set - to true +

    Check the following parameter in Thunderbird, it should be set to true

    calendar.caldav.sched.enabled=true @@ -196,7 +190,7 @@ calendar.debug.log.verbose=true]]>

    Message deleted over IMAP still visible through OWA

    -

    Message move does not exist in IMAP, thus the move is a delete followed by a create. +

    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 delete a message.

    diff --git a/src/site/xdoc/sslsetup.xml b/src/site/xdoc/sslsetup.xml index 8c44b969..a11e69e7 100644 --- a/src/site/xdoc/sslsetup.xml +++ b/src/site/xdoc/sslsetup.xml @@ -24,6 +24,8 @@ pkcs12 -validity 3650 -dname cn=davmailhostname.company.com,ou=davmail,o=sf,o=net +

    Note to iPhone users: iOS does not support the default DSA algorithm, make sure you use an RSA key pair

    +

    Then add this keystore to DavMail settings:

    -

    Restart DavMail, all DavMail listeners will switch to secure mode. 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. +

    If your already have your keystore in JKS format, just set keystoreType to JKS in DavMail + settings. keystorePass is the password used to open the KeyStore, keyPass protects the private key + inside the KeyStore. +

    +

    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.

    +

    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