As another option if IMAP html display work, why not just have the zimbra backend connect for mail via IMAP and have contacts and calendar work as is via SOAP requests?
ActiveSync 14 support - which they say is needed for HTML to anything other than an iPhone is due as part of z-push 2.0 - and slated for September at the earliest.
Can you clarify - Is it possible to have both the zimbra web client on ssl port 443 via proxy, and at the same time have an alias for /Microsoft-Server-ActiveSync/ on that same port ?
The reason I ask is that people would want to use the default port for web access, and many mobile devices do not allow you to specify an alternative port.
Can you provide a sample config file for apache - as this is something many people including myself would like to do, I'm sure.
The trick is to force jetty using another port in my case I use 9080 and set up a proxy on local machine using ssl to connect the outside world and connecting the proxy to jetty without ssl, which doesn't matter, because the traffic between proxy and jetty never leaves the machine. In my case I use different subdomains with vhosts which are selected by the called subdomain. www.gw.example.org calls the webserver which also hosts z-push; gw.example.org and mail.gw.example.org calls jetty (zimbra) via proxy...Code:NameVirtualHost *:443 <VirtualHost *:443> ServerName gw.example.org ServerAlias mail.gw.example.org ServerAdmin firstname.lastname@example.org ProxyRequests Off <Proxy *> Order deny,allow Allow from all </Proxy> ProxyPass / http://127.0.0.1:9080/ ProxyPassReverse / http://127.0.0.1:9080/ <Location /> Order allow,deny Allow from all </Location> SSLEngine on SSLCertificateFile /etc/apache2/ssl/www.gw.example.crt SSLCertificateKeyFile /etc/apache2/ssl/www.gw.example.key SSLCACertificateFile /etc/apache2/ssl/ca.crt </VirtualHost> <VirtualHost *:443> DocumentRoot /var/www/ ServerName www.gw.example.org ServerAdmin email@example.com ErrorLog /var/log/apache2/error.log CustomLog /var/log/apache2/access.log common SSLEngine on SSLCertificateFile /etc/apache2/ssl/www.gw.example.crt SSLCertificateKeyFile /etc/apache2/ssl/www.gw.example.key SSLCACertificateFile /etc/apache2/ssl/ca.crt #Possible values include: debug, info, notice, warn, error, crit, # alert, emerg. LogLevel warn ServerSignature On Alias /Microsoft-Server-ActiveSync /var/www/z-push/index.php <Directory /> Options FollowSymLinks AllowOverride None </Directory> <Directory /var/www/> Options Indexes FollowSymLinks MultiViews AllowOverride All Order allow,deny allow from all # Uncomment this directive is you want to see apache2's # default start page (in /apache2-default) when you go to / #RedirectMatch ^/$ /apache2-default/ </Directory> ScriptAlias /cgi-bin/ /usr/lib/cgi-bin/ <Directory "/usr/lib/cgi-bin"> AllowOverride None Options +ExecCGI -MultiViews +SymLinksIfOwnerMatch Order allow,deny Allow from all </Directory> Alias /doc/ "/usr/share/doc/" <Directory "/usr/share/doc/"> Options Indexes MultiViews FollowSymLinks AllowOverride None Order deny,allow Deny from all Allow from 127.0.0.0/255.0.0.0 ::1/128 </Directory> </VirtualHost>
Last edited by andywhy; 07-09-2010 at 07:34 AM.
Before I forget, you could run into a small issue with the certificates and the subdomains, because the ssl connection is build up before the vhost is selected. So the default vhost offers his certificate in this initial connection and the browser might wonder why he gets the "wrong" certificate for the subdomain. As a workaround you could use an expensive wildcard certificate *.gw.example.com, ignore the browser error ;-) or use ip based filtering for the vhosts (but if you would only assign one ip, this is no choice)
Another option is to have another ip set to the server, run the non-zimbra apache on that ip only and setup another subdomain for z-push.
That's how we are doing it. I try not to add to much custom stuff into zimbra to avoid having to change a bunch of stuff on an upgrade. Because keep in mind that you will need to change all the configs by hand every time you upgrade your zimbra server.
Last edited by andywhy; 07-09-2010 at 11:42 PM.
Does any of you notice a high increase in CPU usage when z-push clients are connected? Zimbra's main java process goes from almost no cpu usage to a steady 100%-200% with only two clients. Load average goes from 0.50 to 4.0-5.0.
Using z-push 1.4 and backend revision 42 and the two clients are WM6.5, syncing mail, contacts and calendar. Had the same behavior with earlier revisions (37 at least) and z-push 1.3.
There are currently 1 users browsing this thread. (0 members and 1 guests)