I'm posting this, because I'm going to start Zimbra for production use soon, and I would hate to miss out on something important.

I've got Zimbra 4.5.5 up and running on Debian Etch 32bit doing some of the things already mentioned in other posts.

install the following packages:

sudo curl fetchmail libgmp3c2 libssl0.9.7 libdb3 libxml2 perl libexpat1 libpcre3 file

It seems that

libio-socket-ssl-perl
libmail-imapclient-perl
libmail-pop3client-perl

and a few others, spell modules for example are also necessary

edit /etc/debian_version to 3.1 from 4.0
edit /utils/utilfunc.sh and change script to look for libgmp3c2 not libgmp3

But, I found it necessary to set up the following soft links in /usr/lib

libcrypto.so.0.9.7 -> libcrypto.so.0.9.8
libssl.so.0.9.7 -> libssl.so.0.9.8

With that and some dns-tweaking everything seems to run just fine.

I have some questions for the Zimbra guys though.

Firstly, is this installation method likely to cause major problems, when upgrading zimbra some day?

Secondly, it looks as if there are three files in /opt/zimbra with wrong usernames. They are created during installation.
Is this a bug? Changing ownership to zimbra manually seems to be ok.

-rw-r--r-- 1 zimbra zimbra 20 2007-06-13 23:57 .bash_history
-r--r--r-- 1 503 503 232 2007-05-04 02:45 .bash_profile
-r--r--r-- 1 503 503 1009 2007-05-04 02:45 .bashrc
-r--r--r-- 1 503 503 62 2007-05-04 02:45 .exrc

Thirdly, in the log, the amavis-process only loads some things, se below.
Is this important, or should something be done about it?

Jun 14 01:12:05 zimbra amavis[20018]: Amavis::Cache code loaded
Jun 14 01:12:05 zimbra amavis[20018]: SQL base code NOT loaded
Jun 14 01:12:05 zimbra amavis[20018]: SQL::Log code NOT loaded
Jun 14 01:12:05 zimbra amavis[20018]: SQL::Quarantine NOT loaded
Jun 14 01:12:05 zimbra amavis[20018]: Lookup::SQL code NOT loaded
Jun 14 01:12:05 zimbra amavis[20018]: Lookup::LDAP code loaded
Jun 14 01:12:05 zimbra amavis[20018]: AM.PDP-in proto code loaded
Jun 14 01:12:05 zimbra amavis[20018]: SMTP-in proto code loaded
Jun 14 01:12:05 zimbra amavis[20018]: Courier proto code NOT loaded
Jun 14 01:12:05 zimbra amavis[20018]: SMTP-out proto code loaded
Jun 14 01:12:05 zimbra amavis[20018]: Pipe-out proto code NOT loaded
Jun 14 01:12:05 zimbra amavis[20018]: BSMTP-out proto code NOT loaded
Jun 14 01:12:05 zimbra amavis[20018]: Local-out proto code loaded
Jun 14 01:12:05 zimbra amavis[20018]: OS_Fingerprint code NOT loaded
Jun 14 01:12:05 zimbra amavis[20018]: ANTI-VIRUS code loaded
Jun 14 01:12:05 zimbra amavis[20018]: ANTI-SPAM code loaded
Jun 14 01:12:05 zimbra amavis[20018]: ANTI-SPAM-SA code loaded
Jun 14 01:12:05 zimbra amavis[20018]: Unpackers code loaded
Jun 14 01:12:05 zimbra amavis[20018]: Found $file at /usr/bin/file
Jun 14 01:12:05 zimbra amavis[20018]: No $dspam, not using it

The last entry for dspam can be changed to load it by uncommenting line 104 in /opt/zimbra/conf/amavisd.conf.in :

#$dspam = '/opt/zimbra/dspam/bin/dspam';

Why is this commented out by default?

Fourthly, I guess that the following server-start log-stuff is just normal, as everything seems completely stable, once the server is running. Spam-checks seem to work etc.

Jun 14 01:12:05 zimbra zimbramon[19396]: 19396:info: Starting mta
Jun 14 01:12:05 zimbra amavis[20018]: SpamControl: initializing Mail::SpamAssassin
Jun 14 01:12:05 zimbra amavis[20018]: SpamControl: init_pre_fork done
Jun 14 01:12:05 zimbra postfix/postqueue[20056]: fatal: Queue report unavailable - mail system is down
Jun 14 01:12:07 zimbra postfix/postfix-script: warning: not owned by root: /opt/zimbra/postfix-2.2.9/conf/main.cf
Jun 14 01:12:07 zimbra postfix/postfix-script: starting the Postfix mail system

Finally, I must say, that I'm really impressed with this product.
We've been running qmail with different frontends for some years. The server part is great, but it has been impossible to find a modern web-interface that is satisfactory for modern use.
The Zimbra client is a little slow to load but otherwise FANTASTIC in every aspect.
If I'm sucessful with this, well definitely consider upgrading to one of the payment versions.

Danish greetings

Hans Otto Lunde