(replacing ‚ÄòN.N.N-NNN‚Äô with the version number)Įdit the file WEB-INF/classes/davmail.properties as appropriate, for example: davmail.url= davmail.popPort=1110 davmail.smtpPort=1025 davmail.ldapPort=1389 davmail.caldavPort=1080 davmail.keepDelay=60 ntKeepDelay=180 davmail.caldavPastDelay=60 davmail.enableProxy=false davmail.proxyHost= davmail.proxyPort= davmail.proxyUser= davmail.proxyPassword= davmail.allowRemote=true davmail.bindAddress= rver=true davmail.disableUpdateCheck=false =DEBUG log4j.rootLogger=WARN =WARN .commons.httpclient=WARN
If the build is successful proceed to configure the web application archive (WAR file) version of Davmail: $cd dist $jar xvf davmail-N.N.N-NNN.war For checkout details see the Sourceforge page. Hash the certificates: $sudo c_rehash /etc/ssl/local/certs Build and Configure Davmail Install the Gmail POP3S certificate: $openssl s_client -connect :995 -showcertsįrom the output of the command select the certificate (the first block to appear between and including lines ‚Äú‚Äî‚ÄìBEGIN CERTIFICATE‚Äî‚Äì‚Äù and ‚Äú‚Äî‚ÄìEND CERTIFICATE‚Äî‚Äì‚Äù) and copy and paste this into a new file: /etc/ssl/local/certs/googlepop.pem Install the Equifax root CA certificate (required for Gmail POP3S): $sudo wget -O /etc/ssl/local/certs/equifax.pem Equifax_Secure_Certificate_Authority.cer $sudo openssl x509 -inform der -in 'Thawte Premium Server CA.cer' -out /etc/ssl/local/certs/thawte.pem Convert the CA certificate to PEM format and install:.Unzip the ZIP archive and locate the file: Thawte Premium Server CA.cer.Go to Thawte and download their root CA certificates.Install the Thawte root CA certificate (required for Gmail SMTPS): To be sure that we are actually connecting to Gmail and to encrypt e-mail to and from the service we need to set up a few certificates.Ĭreate a local certificate store: $mkdir -p /etc/ssl/local/certs/ Install Packagesįetchmail, Postfix and Courier IMAP and dependencies can all be installed via the package management system: $sudo apt-get install postfix fetchmail courier-imap sun-java6-jdk tomcat6 tomcat6-admin ant Configure Certificates You could just as easily have multiple Exchange accounts and/or standards-based e-mail accounts. Note: this tutorial uses as the example corporate mail domain (OWA) and Gmail as the non-corporate mail service. You are capable of appropriately securing services, e.g.However, there should be few differences if you are running Debian, and it should be easy enough to adapt this configuration to accommodate RPM-based distributions You have a Gmail account with POP enabled (this tutorial could be easily adapted to other service providers).You have the OWA service configured on your Exchange server, e.g.If you want the quickest and simplest route to getting mail from OWA into your MUA of choice, and are fine with it being pulled down into the local folders of a MUA, you might be better off using Davmail in its desktop configuration and without the complexity of Postfix + Fetchmail + Courier IMAP.
This particular configuration is perhaps best suited to a more advanced desktop configuration, else as the basis for a server-based resource where you may have multiple desktops and want to synchronize mail across devices. This tutorial explains how to use a recipe of Davmail + Fetchmail + Postfix + Courier IMAP to interface standards-based e-mail clients with Exchange’s OWA, and to integrate corporate and non-corporate e-mail accounts into a single inbox and one that is not buried inside the store of the MUA. Whilst Exchange has the capability to provide an IMAP and/or POP service these are frequently disabled, leaving Outlook Web Access (OWA) as the only remaining hope for users of non-Microsoft mail user agents (MUAs). Many enterprises use Microsoft Exchange for corporate e-mail, and there is frequently no avoiding its use regardless of where you might sit in the organization or the freedom afforded to you in terms of desktop configuration.