Changes

From SME Server
Jump to navigationJump to search
1,474 bytes removed ,  15:26, 19 December 2008
→‎SSL: added to smeserver-zarafa-0_9_0-10_el4_sme
Line 31: Line 31:     
  Hi Paul, please submit separate bug reports detailing all your customization notes. Darrell
 
  Hi Paul, please submit separate bug reports detailing all your customization notes. Darrell
  −
=== SSL ===
  −
  −
I've been trying to get SSL working for both IMAP and the Outlook configuration. For IMAP, I edited the gateway.cfg template to point to the SME Server certificate and key files:
  −
  −
File with RSA key for SSL:
  −
  −
ssl_private_key_file    =      /home/e-smith/ssl.key/host.domain.com.key
  −
  −
File with certificate for SSL:
  −
  −
ssl_certificate_file    =      /home/e-smith/ssl.crt/host.domain.com.crt
  −
  −
On restart of the daemon, I was successfully able to connect. In looking further at the Outlook side, SSL support for the server is configured in server.cfg, where it requires a path to CA certificates. Using the steps outlined in the zarafa-server man page, I created a CA and certificate which I then specified in server.cfg. I was then able to configure the Outlook profile to use port 237 and connect successfully.
  −
  −
N.B. There is a typo in the man page - the shell script should be /usr/share/zarafa/ssl-certificates.sh - the man page is missing the "s" in certificates.
  −
  −
NOTE: There is no need to create any additional certificates, the SME self signed certificates work just fine for Outlook SSL connections.  In server.cfg in the SSL section (on or about line 104) you need to point to the correct certs and paths like this:
  −
  −
server_ssl_key_file    = /home/e-smith/ssl.pem/host.domain.com.pem
  −
  −
server_ssl_ca_file      = /home/e-smith/ssl.crt/host.domain.com.crt
  −
  −
server_ssl_ca_path      = /home/e-smith/ssl.crt/
  −
  −
sslkeys_path            = /home/e-smith/ssl.pem/
 

Navigation menu