moparisthebest/davmail
1
0
Fork 0
mirror of https://github.com/moparisthebest/davmail synced 2024-12-14 11:42:23 -05:00
Code Issues Releases Wiki Activity

Add an FAQ entry on DavMail settings location

Browse Source 
git-svn-id: http://svn.code.sf.net/p/davmail/code/trunk@945 3d1905a2-6b24-0410-a738-b14d5a86fcbd
This commit is contained in:
mguessan 2010-02-12 10:29:34 +00:00
parent dc6c916a73
commit a282a63108
1 changed files with 26 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

37
src/site/xdoc/faq.xml
View File

@ -54,6 +54,13 @@
<p>Your Exchange server expects HTTPS (secured) connections, use https instead of http in <p>Your Exchange server expects HTTPS (secured) connections, use https instead of http in
OWA url. OWA url.
</p> </p>
<p>
<strong>Where can I find DavMail settings file</strong>
</p>
<p>The default location for DavMail settings is a file named .davmail.properties in user home
folder. This file is hidden under Linux and OSX. On windows, the user home folder is under
<code>Document and Settings</code></p>
</subsection> </subsection>
<subsection name="Exchange setup"> <subsection name="Exchange setup">
@ -82,16 +89,23 @@
<strong>How do I secure DavMail connections ?</strong> <strong>How do I secure DavMail connections ?</strong>
</p> </p>
<p>Communication between DavMail and you Exchange server is secured by default as long as you access <p>Communication between DavMail and you Exchange server is secured by default as long as you access
OWA over HTTPS. Communication between the messaging client and DavMail is <em>not</em> secured by OWA over HTTPS.
default. This is not an issue in standalone mode as all communication is local, but you may want </p>
to improve this in server (shared) mode. This is quite simple: you just need to get a server <p>Communication between the messaging client and DavMail is
certificate in PKCS12 or JKS format and add it in the key store section in DavMail settings, <em>not</em>
see <a href="gettingstarted.html">Getting started</a>. You need to choose the key store type in secured by default. This is not an issue in standalone mode as all communication is local, but you
davmail.ssl.keystoreType: PKCS12 for .p12 file and JKS for java generated key stores. Then set the full may want
path to your certificate file in davmail.ssl.keystoreFile and the certificate file password in to improve this in server (shared) mode.
davmail.ssl.keystorePass. You may also have a key password in addition to the file password, specify it </p>
in davmail.ssl.keyPass. <p>This is quite simple: you just need to get a server certificate in PKCS12 or JKS format and add it in
This will switch all DavMail services to SSL mode: POP3S/IMAPS/SMTPS/HTTPS/LDAPS. the key store section in DavMail settings, see<a href="gettingstarted.html">Getting 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>
@ -110,8 +124,7 @@
on. To detect errors at this level, you may activate calendar log settings on. To detect errors at this level, you may activate calendar log settings
under Tools/Options/Advanced: under Tools/Options/Advanced:
</p> </p>
<source> <source>calendar.debug.log=true
calendar.debug.log=true
calendar.debug.log.verbose=true calendar.debug.log.verbose=true
</source> </source>