Installing Zimbra on VServer

Revision as of 20:10, 1 October 2007 by Mathx (talk | contribs) (Postfix)

Installation on VServer

These instructions are specifically for Debian VServers, but should be able to be applied to just about any system

WARNING - Upgrading Zimbra will overwrite all of these files - you must patch them after installing and each upgrade.

Debian and VServers



A base Debian vserver doesn't have a "file" utility installed by default. This is needed by amavis. The installer will fail, if getopt isn't installed, for this you need "libgetopt-mixed-perl". Apache and Tomcat will fail, as the base vserver doesn't have "libexpat1" installed. Install it by typing:

apt-get install file libexpat1 libgetopt-mixed-perl

Matter of fact, all packages required for installing Zimbra are:

apt-get install libgetopt-mixed-perl file libc6-i686 sudo libidn11 curl fetchmail libgmp3 \
    libxml2 libstdc++6 openssl libexpat1

Note: As of etch, libgmp3 isnt available anymore, libgmp3c2 or 4xx is required instead. Not finished testing install with 3c2 to see if it works. --mathx


Make sure you have a localhost entry and also an entry with your primary IP. For example:   localhost.localdomain localhost     mail.somehost.zimbra mail


The Zimbra logger process doesn't seem to startup. "zmcontrol status" on my system shows:

vserver:~# /opt/zimbra/bin/zmcontrol status
Host vserver.somedomain
        antispam                Stopped
        antivirus               Stopped
        ldap                    Running
        logger                  Stopped
        mailbox                 Stopped
        mta                     Stopped
        snmp                    Stopped
        spell                   Running

The logger uses MySQL. I'm guessing there is some problem with privileges and/or connecting to localhost in the "mysql" database. Just a hunch though.

I installed Zimbra on a new VServer and the logger seemd to startup properly. "zmcontrol status" shows it running after several stops/starts. However, I'm still not getting any log data. All statistics windows say "Data not available yet.". Oh well.


In postfix/conf/ inet n  -       n       -       -  smtpd
 -o mynetworks=,

Where is your real IP number (not Do not forget to change the mynetworks line as well, or your AV will not be able to connect back to postfix on 10025 for final delivery.

Note: It may not be a good idea to use a real internet IP here, your RFC1918 picked replacement IP for is a better idea. I dont know that it's a good thing to have port 10025 open to the internets.

In postfix/conf/

content_filter = smtp-amavis:[]:10024

As of Zimbra 4.5 (4.5.7 in my case) postfix/conf/ is empty, only exists - I assume the server runs on its defaults. It seems odd that the content_filter default has been compiled in as per the above, but that may well be the case. In which case we need an override line in our own to set the IP to our RFC1918 IP we're using instead of

Recently you also have to change zmmta.conf in /opt/zimbra/conf

POSTCONF content_filter smtp-amavis:[]:10024

or your changes will keep getting overwritten.

Security limits (SuSE OSS 10.0 vserver)

Edit /etc/security/limits.conf and comment the last two lines - otherwise the su command won't work and the installation will fail.

# End of file
#zimbra soft nofile 10000
#zimbra hard nofile 10000

Rerun /opt/zimbra/libexec/ to complete the setup.


Edit /opt/zimbra/amavisd/sbin/amavisd (main Perl script) and explicitly add the IP address of the Zimbra VServer to the "inet_acl" line. I.e:

@inet_acl   = qw( [::1] );  # allow SMTP access only from localhost

Postfix should then be able to talk to Amavis...

You may also need to change BIND address and the two services back to postfix (10025 port). Basically look for (?? This line is overly vague, refine please --mathx)

Additional changes likely required in /opt/zimbra/amavisd/sbin/amavisd (perl script):

$inet_socket_bind = '';  # limit socket bind to loopback interface
$inet_socket_bind = '';  # no loopback in vserver, use rfc1918 internal ip bound to your vserver

also few lines down:

$notify_method  = 'smtp:[]:10025';   # change these to also match your internal
$forward_method = 'smtp:[]:10025';   # rfc 1918 ip addr (can use inet ip, but not recommended)

A bunch of filters in /opt/zimbra/conf/amavisd.conf also need updating from to whatever IP you are using (though many in the default file are commented out, I think I found 3 in the default zimbra amavisd install that needed changing.)

Additionally the local MX for /opt/zimbra/conf/dspam.conf needs changing as well.

Vserver /tmp size

My install of Zimbra wouldn't start clamd with my default debian 16m of /tmp ramdisk space in my vserver. I had to edit /etc/vservers/(name)/fstab and increase it to 128m (though smaller may work, I didnt test), and restart the vserver. 128m lets it start anyway, not sure if I'll run out during operations. --mathx

Tomcat/Java Memory Usage

While trying to get tomcat to start on our Vserver, we kept getting this error in catalina.out:

Invalid initial heap size: -Xms8001m
The specified size exceeds the maximum representable size.
Could not create the Java virtual machine.

By default, tomcat will use 50% of the system memory available (as defined in tomcat_java_heap_memory_percent). On our 16Gb machine, Tomcat tried to use 8Gb and failed. You can override this default by issuing:

zmlocalconfig -e tomcat_java_heap_memory_percent="6"

Where the 6 means 6% (983.04Mb in our case).

Jump to: navigation, search