Installing Zimbra MTA on a Server

When zimbra-mta is installed, the LDAP host name and the Zimbra LDAP password must be known to the MTA server. If not, the MTA cannot contact the LDAP server and is not able to complete the installation.

1.	Follow steps 1 through 4 in Starting the Installation Process to open a SSH session to the MTA server, log on to the server as root, and unpack the Zimbra software.

2.	Type Y and press Enter to install the zimbra-mta package. The other packages should be marked N. In the following screen shot example, the package to be installed is emphasized.

Note: If SNMP is used, it is installed on every server.

Select the packages to install Install zimbra-ldap [Y] N Install zimbra-logger [Y] N Install zimbra-mta [Y] Y Install zimbra-snmp [Y] N Install zimbra-store [Y] N Install zimbra-apache [Y] N Install zimbra-spell [Y] N Installing: zimbra-mta This system will be modified. Continue [N} Y Configuration section

3.	Type Y, and press Enter to install the selected package(s).

The Main menu displays the default entries for the Zimbra component you are installing. To expand the menu to see all the configuration values type x and press Enter.

To navigate the Main menu, select the menu item to change. You can modify any of the values.

Main menu 1) Common Configuration: +Hostname: mta-1.example.com ******* +Ldap master host: UNSET +Ldap port: 389 ******* +Ldap Admin password: UNSET         +Require secure interprocess communications: yes +TimeZone: (GMT-08.00) Pacific Time (US & Canada) 2) zimbra-mta: Enabled ********+MTA Auth host: mta-1.example.com +Enable Spamassassin: yes +Enable Clam AV: yes +Notification address for AV alerts:  admin@mta-1.example.com ******* +Bind password for postfix ldap user: UNSET ******* +Bind password for amavis ldap user: UNSET 3) zimbra-snmp: Enabled    4) zimbra-spell: Enabled    5) Enable default backup schedule: yes r) Start servers after configuration yes s) Save config to file x) Expand menu q) Quit

4.	The Main menu displays. Type 1 and press Enter to go to the Common Configuration menu.

Common Configuration:     1)Hostname:                          mta-1.example.com     2)Ldap master host:                  mta-1.example.com     3)Ldap port: 389     4)Ldap Admin password: set     5)Require secure interprocess communications      Yes     6)TimeZone:              (GMT-08.00) Pacific Time (US & Canada)

The mailbox server hostname is displayed. You must change the LDAP master host name and password to be the values configured on the LDAP server.

•	Type 2, press Enter, and type the LDAP host name. (ldap-1.example.com in this example.)

•	Type 4, press Enter, and type the LDAP password.

After you set these values, the server immediately contacts the LDAP server. If it cannot contact the server, you cannot proceed.

•	Type 6 to set the correct time zone, if your time zone is not Pacific Time.

5.	Type r to return to the Main menu.

6.	Type 2 to go to the Mta menu.

Select, or press 'a' to apply config (? - help) 2 Mta configuration   1) Status: Enabled **2) MTA Auth host:                           UNSET   3) Enable Spamassassin: yes   4) Enable Clam AV: yes   5) Notification address for AV alerts: admin@mta-1.example.com **6) Bind password for postfix ldap user: UNSET **7) Bind password for amavis ldap user: UNSET

•	Type 2 to set the MTA Auth host. This is the MTA authentication server host name and is set to one of the Zimbra mailbox server’s hostname.

•	You can change 5, AV alerts notification address. This should be an address on the domain, such as the admin address. (admin@example.com)

Note: If you enter an address other than the admin address, you must provision an account with that address after the installation is complete.

You must set the same postfix ldap user password and the same amavis ldap user password that is configured on the LDAP master server.

•	Type 6 and enter the postfix password.

•	Type 7 and enter the amavis password.

7.	Type r to return to the Main menu.

8.	When the MTA server is configured, return to the Main menu and type a to apply the configuration changes. Press Enter to save the configuration data.

9.	When Save Configuration data to a file appears, press Enter.

10.	The next request asks where to save the files. To accept the default, press Enter. To save the files to another directory, enter the directory and then press Enter.

11.	When The system will be modified - continue? appears, type y and press Enter.

The server is modified. Installing all the components and configuring the MTA server can take a few minutes. This can include setting passwords, setting ports, setting time zone preferences, and starting the server, among other processes.

12.	When Installation complete - press return to exit displays, press Enter.

The installation of the MTA server is complete.

Starting the Installation Process

For the latest Zimbra software download, go to www.zimbra.com. Save the Zimbra Collaboration Suite tar file to the computer from which you are installing the software.

For servers other than Mac servers, step 1 through step 4 are performed for each server to be installed.

For Mac servers, see Starting the Installation Process on the Mac Server.

1.	Log in as root to the Zimbra server and cd to the directory where the Zimbra Collaboration Suite archive file is saved (cd /var/<tmp>/var). Type the following commands.

•	tar xzvf [zcs.tgz] to unpack the file

•	cd [zcs filename] to change to the correct directory. The file name includes the release and build date.

•	./install.sh to begin the installation.

Note:  

Note: As the installation proceeds, press Enter to accept the defaults that are shown in brackets [ ] or enter the appropriate answer for your configuration.

The screen shots are examples of the Zimbra installation script.

[root@mailhost tmp]# tar xzvf zcs.tgz zcs/ . . . zcs/packages/ zcs/packages/zimbra-spell-6.0.0_xx_1_5469.RHEL4-4116.i386.rpm zcs/packages/zimbra-apache-6.0.0_xx_5469.RHEL4-4116.i386.rpm zcs/packages/zimbra-core-6.0.0_xx_5469.RHEL4-4116.i386.rpm zcs/packages/zimbra-logger-6.0.0_xx_5469.RHEL4-4116.i386.rpm zcs/packages/zcs-cluster-6.0.0_GA_1469.RHEL4.tgz zcs/packages/zimbra-cms-6.0.0_xx_5469.RHEL4-4116.i386.rpm zcs/packages/zimbra-ldap-6.0.0_xx_5469.RHEL4-4116.i386.rpm zcs/packages/zimbra-store-6.0.0_xx_5469.RHEL4-4116.i386.rpm zcs/packages/zimbra-mta-6.0.0_xx_5469.RHEL4-4116.i386.rpm zcs/packages/zimbra-snmp-6.0.0_xx_5469.RHEL4-4116.i386.rpm zcs/README.txt zcs/readme_binary.txt zcs/docs/ . . . [root@mailhost tmp]# cd zcs-NETWORK-6.0.0_XX_5469.RHEL4.4116 [root@mailhost zcs-NETWORK-6.0.0_xx_5469.RHEL4.4116]# ./install.sh Operations logged to /tmp/install.log.27584 Checking for existing installation... zimbra-ldap...NOT FOUND zimbra-logger...NOT FOUND zimbra-mta...NOT FOUND zimbra-snmp...NOT FOUND zimbra-store...NOT FOUND zimbra-apache...NOT FOUND zimbra-spell...NOT FOUND            zimbra-core...NOT FOUND

2.

The installation process checks to see if Sendmail, Postfix, and MySQL software are running. If any application is running, you are asked to disable it. The default is Yes to disable the applications. Disabling MySQL is optional, but highly recommended. Sendmail and Postfix must be disabled for the Zimbra Collaboration Suite to start correctly.

3.	The Zimbra software agreement is displayed and includes a link to the license terms for the Zimbra Collaboration Suite. Read the agreement and press Enter to continue.

PLEASE READ THIS AGREEMENT CAREFULLY BEFORE USING THE SOFTWARE.ZIMBRA, INC. ("ZIMBRA") WILL ONLY LICENSE THIS SOFTWARE TO YOU IF YOU FIRST ACCEPT THE TERMS OF THIS AGREEMENT. BY DOWNLOADING OR INSTALLING THE SOFTWARE, OR USING THE PRODUCT, YOU ARE CONSENTING TO BE BOUND BY THIS AGREEMENT. IF YOU DO NOT AGREE TO ALL OF THE TERMS OF THIS AGREEMENT, THEN DO NOT DOWNLOAD, INSTALL OR USE THE PRODUCT. License Terms for the Zimbra Collaboration Suite: http://www.zimbra.com/license/index.html Press Return to continue

4.	Next, the installer checks to see that the prerequisite software is installed. If NPTL, sudo, libidn, cURL, fetchmail, GMP or compat-libstdc++- are not installed, the install process quits. You must fix the problem and start the installation again.

Note: Before the Main menu is displayed, the installer checks to see if the hostname is resolvable via DNS and if there is an error asks you if would like to change the hostname. The domain name should have an MX record configured in DNS.