Hosting other sites with Zimbra: Difference between revisions

mNo edit summary
(duh, apache over http, zimbra over https)
Line 1: Line 1:
This document applies to Apache 2.0  
==Apache over http (port 80) and Zimbra over https (port 443)==
 
If you don't need to have non-SSL (http/port 80) access to zimbra webmail and you don't need to have SSL (https/port 443) access to apache, [[Zmtlsctl|configure zimbra to only listen on https]] port 443.
 
su - zimbra
zmtlsctl https
tomcat restart
 
That's it! Now apache will serve websites (presumably over port 80), and zimbra will serve webmail (over port 443).
 
==Hosting other sites with Apache, and proxying mail connections to Zimbra==
 
Note: This topic is covered for both Apache 1.3 and 2 at [[ZimbraApache]].
 
This document applies to Apache 2.0.


To do virtual hosts with zimbra is fairly straight forward. This is particularly relevant if you want to use the normal apache release on redhat.
To do virtual hosts with zimbra is fairly straight forward. This is particularly relevant if you want to use the normal apache release on redhat.

Revision as of 23:36, 1 June 2007

Apache over http (port 80) and Zimbra over https (port 443)

If you don't need to have non-SSL (http/port 80) access to zimbra webmail and you don't need to have SSL (https/port 443) access to apache, configure zimbra to only listen on https port 443.

su - zimbra
zmtlsctl https
tomcat restart

That's it! Now apache will serve websites (presumably over port 80), and zimbra will serve webmail (over port 443).

Hosting other sites with Apache, and proxying mail connections to Zimbra

Note: This topic is covered for both Apache 1.3 and 2 at ZimbraApache.

This document applies to Apache 2.0.

To do virtual hosts with zimbra is fairly straight forward. This is particularly relevant if you want to use the normal apache release on redhat.


The first thing to do is to change the mailport (the main listening port for web requests) from 80 to something else (8009 for example)


   /opt/zimbra/bin/zmprov mcf zimbraMailPort 8009
   /opt/zimbra/bin/zmprov gcf zimbraMailPort
   /opt/zimbra/bin/tomcat stop
   /opt/zimbra/bin/tomcat start

Make sure that this is done as the zimbra user. Tomcat doesn't take notice of the changes unless a start stop is done (ie. not a restart)


Assuming that a standard apache install has been done off RPM then it is just a matter of adding the appropriate lines to the VirtualHosts section of the apache conf file


       <VirtualHost *:80>
       ServerAdmin admin@foo.com
       Servername      zimbra.foo.com
       ErrorLog        logs/zimbra.foo.com-error_log
       CustomLog       logs/zimbra.foo-access_log common
       ProxyPass       /       http://localhost:8009/
       ProxyPassReverse   /     http://localhost:8009/
       </VirtualHost>


The critical lines are the ProxyPass lines. This assumes that zimbra is running on the same host.

With this config, any requests that come to zimbra.foo.com are proxied to http://localhost:8009

For more info check out the following links;

Apache Tomcat Connector Apache Virtual Hosts

Jump to: navigation, search