Basic zimbra configuration

<yambe:breadcrumb>Zimbra server configuration|Zimbra</yambe:breadcrumb>

Zimbra

Installation

1. Zimbra setup can be downloaded from http://www.zimbra.com/downloads/os-downloads.html Steps mentioned below are specific to http://files2.zimbra.com/downloads/8.0.7_GA/zcs-8.0.7_GA_6021.RHEL6_64.20140408123911.tgz and may get changed slightly based on version being installed.
2. Verify md5sum and then extract download archive.
3. Stop and disable any existing SMTP servers, if any, using:
   • service sendmail stop
   • chkconfig sendmail off
   • service postfix stop
   • chkconfig postfix off
4. Edit /etc/hosts
   1. Ensure that it contains 127.0.0.1 localhost.localdomain localhost and no other aliases for 127.0.0.1
   2. For machines ethernet / public IP it should contain FQDN, followed by hostname, followed by other aliases. For example 10.3.3.241 zimbratest.iiit.ac.in zimbratest lab320-pc9 mfsmaster
5. Ensure that DNS entry for FQDN resolves to machine's IP. Further MX record for email domain should resolve to Zimbra server FQDN directly or through CNAME.
6. Create folder /opt/zimbra. Mount partitons/folder in which you want to install zimbra to /opt/zimbra. This step is required only if you want all Zimbra files to go to separate partition and not to / or /opt.
7. Use 'yum -y install nc libaio sysstat' to install required packages
8. Go to extracted folder and use './install.sh' from root user
9. Enter 'Y' for agreeing with terms of service
10. Enter 'Y' for agreeing with license agreement
11. Enter 'Y' for installing Zimbra-ldap, Zimbra-logger, Zimbra-mta, Zimbra-snmp, Zimbra-store, Zimbra-apache and Zimbra spell
12. Enter 'N' for installing Zimbra-memcached and Zimbra-proxy
13. Enter 'Y' for system will be modified warning. The setup should now install various rpms for Zimbra.
14. If FQDN is different from domain name (eg FQDN zimbra.example.com, domain example.com) then Zimbra will give error that MX record cannot be resolved. Enter 'Yes' for change domain name.
15. Enter new correct domain name such as example.com
16. This would bring setup to Zimbra configuration menu. Only admin password needs to be configured rest all can be left as it is for basic setup. To configure admin password use menu option '3' followed by '4'. Set appropriate admin password.
17. Press 'r' to return to previous menu and then 'a' for applying configuration
18. Enter 'Yes' for saving configuration to a file
19. Press enter for file path option and continue with whatever file name has been suggested
20. Enter 'Yes' for system will be modified warning
21. Now setup should take really long time for various installations and configurations
22. Enter 'No' for notify Zimbra of installation for test machines. In case of production machines you can optionally enter 'Yes'.
23. Press return to exit on 'Press return to exit' message :)
24. Now zimbra admin interface can be accessed at https://<FQDN>:7071/ and mail can be checked using web interface at https://<FQDN>/

Relaying mails through other MTA

If test system does not has access to internet then mails can be relayed through other MTA which has access to Internet (Similar to SMART_HOST for sendmail). To configure relay MTA

1. Login in to zimbra administrative console at https://<IP>:7071/ with user admin
2. Go to Configuration -> Global Settings -> MTA
3. Set relay MTA for external delivery appropriately.

Stopping and starting zimbra

1. Login as root
2. Use 'su - zimbra'
3. Use 'zmcontrol' command to check zimbra status, start or stop it.

Firewall configuration

Zimbra firewall configuration can be learned from http://wiki.zimbra.com/index.php?title=Firewall_Configuration

Changing Zimbra http port

We can change zimbra http port using:

1. su - zimbra
2. zmprov ms server.domain.tld zimbraMailPort <http_port> zimbraMailSSLPort <SSL_port>
3. zmmailboxctld restart

Note:

• This does not seems to work for HTTPS port

Backup

Zimbra backup and restore is discussed at http://wiki.zimbra.com/wiki/Backing_up_and_restoring_Zimbra_%28Open_Source_Version%29#Another_option

Debugging

Ldap start issue

If ldap server does not starts and gives this error

Failed to start slapd.  Attempting debug start to determine error.
bdb_db_close: database "": txn_checkpoint failed: Invalid argument (22).
backend_startup_one (type=hdb, suffix=""): bi_db_open failed! (22)
bdb_db_close: database "": alock_close failed

First verify that domain to IP mapping in /etc/hosts file is correct. If domain to IP mapping in /etc/hosts is not correct then Zimbra will not be able to start listening socket on incorrect IP and hence ldap may fail to start. Also zimbra must be stopped before changing machine IP. Then IP should be changed on system and in /etc/hosts. Then zimbra should be started.

If problem is not due to incorrect IP then:

1. Login as root
2. Go to dir '/opt/zimbra/data/ldap/hdb/db'
3. Use command '/opt/zimbra/bdb/bin/db_recover'

Fixing permisssions on zimbra files

If permissions on zimbra directory could be wrong then following can be use to fix permissions:

chown -R zimbra:zimbra /opt/zimbra
/opt/zimbra/libexec/zmfixperms -verbose -extended

Miscellaneous

If you want to store zimbra on mooseFS then storing entire /opt/zimbra on mooseFS will not work. Specially keeping /opt/zimbra/data on moosefs does not works. Hence directories /opt/zimbra/db, /opt/zimbra/index and /opt/zimbra/store can be shifted to other filesystems to preserve space / improve filesystem performance.

Tutorials and documentation related to zimbra are available at http://www.zimbra.com/downloads/os-downloads.html

<yambe:breadcrumb>Zimbra server configuration|Zimbra</yambe:breadcrumb>