Difference between revisions of "Basic zimbra configuration"
m |
m |
||
Line 12: | Line 12: | ||
##For machines ethernet / public IP it should contain FQDN, followed by hostname, followed by other aliases. For example <tt>10.3.3.241 zimbratest.iiit.ac.in zimbratest lab320-pc9 mfsmaster</tt> | ##For machines ethernet / public IP it should contain FQDN, followed by hostname, followed by other aliases. For example <tt>10.3.3.241 zimbratest.iiit.ac.in zimbratest lab320-pc9 mfsmaster</tt> | ||
#Create folder /opt/zimbra. Mount partitons/folder in which you want to install zimbra to /opt/zimbra. | #Create folder /opt/zimbra. Mount partitons/folder in which you want to install zimbra to /opt/zimbra. | ||
#Use '<tt>yum -y install nc libaio sysstat</tt>' to install required packages | |||
#Go to extracted folder and use '<tt>./install.sh --platform-override</tt>' from root user | #Go to extracted folder and use '<tt>./install.sh --platform-override</tt>' from root user | ||
#Agree to license agreement and choose 'Y' for each component to be installed. | #Agree to license agreement and choose 'Y' for each component to be installed. |
Revision as of 09:30, 23 April 2014
<yambe:breadcrumb>Zimbra server configuration|Zimbra</yambe:breadcrumb>
Zimbra
Installation
- Zimbra setup can be downloaded from http://www.zimbra.com/downloads/os-downloads.html
- Verify md5sum and then extract download archive
- service sendmail stop
- chkconfig sendmail off
- Edit /etc/hosts
- Ensure that it contains 127.0.0.1 localhost.localdomain localhost and no other aliases for 127.0.0.1
- 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
- Create folder /opt/zimbra. Mount partitons/folder in which you want to install zimbra to /opt/zimbra.
- Use 'yum -y install nc libaio sysstat' to install required packages
- Go to extracted folder and use './install.sh --platform-override' from root user
- Agree to license agreement and choose 'Y' for each component to be installed.
- Choose 'Y' for install anyway and system will be modified prompts.
- For test setups ignore DNS hostname and MX record errors
- In the configuration menu
- Go to common configuration and setup
- Ldap admin password
- Correct timezone
- Go to ldap configuration and setup
- Ldap root password
- Ldap replication password
- Ldap postfix password
- Ldap amavis password
- Ldap nginx password
- Go to zimbra store and setup
- Admin password
- Virus quarantine email address
- Spam training user
- Non-spam training user
- Go to Default Class of Service configuration and enable disable features as per requirement
- Save config to file - Remember the name of configuration file
- Apply configuration ('a')
- Go to common configuration and setup
- Yes for System will be modified
- You can choose to notify Zimbra if system is connected to Internet
- Exit from installation by pressing enter
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
- Login in to zimbra administrative console at https://<IP>:7071/ with user admin
- Go to Configuration -> Global Settings -> MTA
- Set relay MTA for external delivery appropriately.
Stopping and starting zimbra
- Login as root
- Use 'su - zimbra'
- 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:
- su - zimbra
- zmprov ms server.domain.tld zimbraMailPort <http_port> zimbraMailSSLPort <SSL_port>
- 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:
- Login as root
- Go to dir '/opt/zimbra/data/ldap/hdb/db'
- 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>