Installation Wiki

Zimbra

From InstallationWiki

Jump to: navigation, search
Zimbra
Official Page
Project Documentation
Download
Source Book
200px-2080_Front_Cover.png
ISBN 978-1-847192-08-0
Publisher Packt Publishing
Author(s) Marty Resnick, David Touitou

The Zimbra Collaboration Suite (ZCS) Web Client is a full-featured collaboration suite that supports email and group calendars using an Ajax web interface that enables tool tips, draggable items, and right-click menus in the UI.

This tutorial will go over the installation of ZCS using emailcs.com as our domain. In the examples that follow, feel free to replace emailcs.com with your organization's domain name to follow along.

The Zimbra Collaboration Suite is a very straightforward install. However, like most software deployments, you want to be sure to prepare for the installation and make sure your system has the recommended hardware and software configurations before attempting the install. This, potentially, could save you a lot of time and money by simply making sure all of your bases are covered. This tutorial will cover the following to prepare you for a successful and efficient install of ZCS, beginning with the system requirements. At this time, please download the latest ZCS package from http://www.Zimbra.com and register for a free limited-term license to follow along with the install described in this package.

Contents

[edit] Before the Installation

As mentioned earlier, it is imperative we understand fully what the system requirements (hardware and software) of the Zimbra Collaboration Suite are, before attempting an install. First, we will discuss the minimum recommended hardware requirements for the suite. Keep in mind that depending on your organization size and the amount of users you will be supporting, the hardware must be adjusted accordingly.

[edit] Hardware

For a production server running ZCS, and assuming that this is a standalone box running no other network services and servicing 100 users, you will need the following:

  • A current 32-bit processor of at least 2.0 GHZ (Intel or AMD). For MAC OS X users, the processor should be G5 or better, Intel Core Solo, or Intel Core Duo.
  • At least 2GB of RAM. (However, 4GB is recommended.)
  • 10 GB free disk space for software and logs.
  • Additional disk space for mail. I usually assume 500MB of mail per user. So at 100 users, I would recommend at least 100GB of disk space for mail. Why not 50GB (50*100)? Because you need space for your backups. Zimbra stores only one copy of an attachment sent to several users (that can save a lot of space) but needs space for its databases (indexes, etc).
  • As the email server is a mission-critical application for any enterprise, I would recommend some sort of hardware fault-tolerance solution. A rule of thumb is that RAID 5 is OK for 100 users. As the organization exceeds that number, RAID 5 is not recommended. Scalability white papers are available on Zimbra's website (for single or multi-server installs).

[edit] Software

Zimbra Collaboration Suite Network Edition supports the following operating systems (end of July 2007):

  • Red Hat Enterprise Linux 4 (AS or ES), 32 and 64 bits
  • MAC OS X 10.4.7
  • SUSE Enterprise Server 9 and OpenSUSE 10
  • rPath (beta)

Please note: the Open Source Edition also supports other operating systems including:

  • Fedora Core 4 and 5
  • Ubuntu Linux (6.0.6.1 LTS)
  • Debian Linux
  • Mandriva Linux (beta)

During the install process, the installer will do a check on the operating system to ensure the following are installed on the server. If any of these are missing, the installer will fail.

  • PTL (??)
  • sudo
  • libidn
  • CURL
  • fetchmail
  • GMP
  • compat-libstdcc++-33 (and compat-libstdc++-296 for Red Hat, both 32 bits and 64 bits version of the library are needed for a 64 bits OS)
  • Java 1.5 as default Java (MAC OS X )

Also, I would recommend SSH is installed for remote management (Zimbra needs it anyway to communicate with itself for mail queue management). DNS should be installed and configured prior to installation of the Zimbra Collaboration Suite, but after the installation and initial testing, I would host the DNS record elsewhere. This will be discussed later in the tutorial. Finally, when installing the operating system, do not install any Apache or MySQL servers. These will be installed with the ZCS installer and if they are already running on the box, this may cause problems later.

[edit] Editing the HOSTS File

Regardless of which operating system you choose to run, there are a couple of configurations you will need to complete prior to installing the software. The first is a simple fix of the hosts file.

The hosts file is used to translate network names to IP addresses and is usually located in the /etc directory of the computer file-system. This is a static file and with the advent of DNS is not used very often. However, most operating systems use this file for local host information and it could also be used to statically map a network name to an IP address without the need for creating a DNS zone file.

Due to the fact that Zimbra uses a MySQL database and uses MySQL permissions to grant access to users from localhost, the /etc/hosts file must be correctly configured or the installer will abort. To edit the /etc/hosts, you will use your preferred text editor (in this case, we will be using vi) and follow the instructions below:

  1. You must be the Superuser to save changes to the /etc/hosts file: su
  2. Next, we will open the file with our text editor: vi /etc/hosts
  3. The first line of the file defines the IP address of localhost as follows: 127.0.0.1 localhost.localdomain localhost
  4. The second line will include the private IP address and hostname of the server: 10.0.0.253 zimbra.emailcs.com zimbra
  5. The final file should resemble the following screenshot.
  6. Once the file is correct, simply type :wq to save and close the file.

Once we have fixed the /etc/hosts file, the next step is to configure DNS.

[edit] Configuring DNS

By default, most operating systems install BIND when it installs a DNS server. DNS is used to dynamically map network names to IP addresses and also to inform other computers on the network which server the email should be sent to (via an MX record) in order to reach its intended recipient. Since we are building an email server, Zimbra wants to ensure there is an MX record for the initial domain that we are installing the Zimbra Collaboration Suite for. So initially, what we do is configure a zone file for our local domain for testing and development purposes, but once we are ready to "go live" with the email server in production, it is highly recommended we host our DNS information on another server.

To configure DNS for our server domain name, in our case emailcs.com, we need to edit two files. The first being the named.conf which BIND uses to let the DNS server know which domain names we have local information for. To edit the named.conf file, you will have to do the following:

  1. Just like the /etc/hosts file, we will need to be root before we could save any changes to the named.conf file. So our first step would be: su
  2. The named.conf will sometimes be located in the /etc directory. However, if your installation of BIND is using chroot, (which is the case for most of them) the named.conf file is located in the /var/named/chroot/etc/ directory. To open the named.conf file for editing: vi /var/named/chroot/etc/named.conf
  3. In the named.conf file, we will add an entry for our emailcs.com domain. Essentially, what we are doing is informing BIND where to find the master file of the domain and where to find the DNS information for our domain. See the following screenshot to see what the entry should look like:
  4. Once we add the information, save and close the named.conf file by entering (in command mode) :wq!.
  5. Next, we will create our zone file. As defined in the named.conf file, we are going to simply name the file containing the DNS information emailcs.com. This file will be located in the /var/named/chroot/var/named directory (assuming BIND is chrooted), if not, the file will be created in the /var/named/ directory. vi emailcs.com
  6. The file will contain specific information. BIND needs to be able to resolve all of the information needed for our emailcs.com mail server. We will create an "A" record, which maps the network name to an IP address. We will also create an MX record, which Zimbra and other Mail Transport Agents require in order to know what server handles email for our domain, and then also a CNAME record, which will create an ALIAS of a server that we will use for our mail server. So the file when completed, should look similar to the one in the following screenshot::

Let's take a moment to review a few key items in this zone file. As this is not a comprehensive book on DNS, some items will not be covered in detail. The first line of the file is the time to live. In our case it is set to 3h or 3 hours. The next line begins with an ampersand (@) and is used to let BIND know that this file will serve as the "authority" for all DNS information of the emailcs.com domain.

Note: Whenever a domain name is written out in a Zone file it must end with a period (.).

So in this case, we write emailcs.com as emailcs.com. The next entry is the domain administrator's email address. This line is unique as the ampersand is replaced with a period and again the domain name ends with a period. We then define the periods for refreshing the zone file, and the serial number of the file itself. This information is used when transferring zone files between DNS servers and also, each time a zone file is changed, the administrator should change the serial number so BIND knows a change has been made.

The next set of lines will give specific information about our domain. The first line is the A record which, as discussed earlier, simply lets DNS know what the IP address is of our domain. The next line is a NS record, informing all DNS servers which server has the authoritative information about this domain. The next line is a key line for us, as it lets BIND know which server will handle our email. And lastly, an alias record, or CNAME, is defined which, will let BIND know where Zimbra.emailcs.com is actually located. In this case, it is just an alias of emailcs.com.

  1. Once we add the information, save and close the emailcs.com file by entering (in command mode) :wq!.
  2. Now we can restart our BIND server and load our zone file, essentially making it active: service named restart
  3. Before we move forward, we must test our DNS configuration using the nslookup command: nslookup emailcs.com

This command should return the IP address of our domain name emailcs.com, in our case it is 10.0.0.42.

To test our MX record configuration we will use the dig command: 

dig emailcs.com mx

A successful result will return an ANSWER SECTION listing the MX record as displayed below:

[edit] Turning Off Sendmail

Sendmail is a popular open source mail transfer agent (MTA) that is installed by default in most Unix or Linux based distributions. Since it is an MTA, we must disable the service so it does not conflict with the Zimbra MTA. Each operating system may be a little different in how to disable a service, but we are going to walk through how to disable the service in Red Hat. There are two steps to this process. First, we want to stop the sendmail service, if it is running. Secondly, we need to disable the service so it does not start up again after a reboot.

  1. To stop the sendmail service, type the following command as root: service sendmail stop
  2. Now to disable the service from starting up again, we will use the chkconfig command (for RHEL, check your OS documentation to find the equivalent command). Again this must be run as root: chkconfig sendmail off

So if we had a running server and configured the HOSTS file, DNS, and turned sendmail off, we would be ready to install our Zimbra Collaboration Suite. However, in an ideal world we would be able to further prepare our server by running through an install of the operating system that will even further optimize our Zimbra install. The following section will walk through an entire installation of the operating system. We will start with Red Hat and then once the server is up and running, we will install Zimbra on the Red Hat server. We will then look at installing the Zimbra Collaboration Suite on both Suse 9 and MAC OS X server. Because there are subtle differences between configuring the servers prior to the Zimbra install, we will not be going into an indepth installation of Suse and MAC. Therefore, I would highly recommend that if you are going to use one of those two operating systems, you still read through the Red Hat walk-through as there are some key points that are transferable to the other systems.

[edit] Installing on Red Hat Enterprise Linux 4

Let me start out this section by mentioning that if you have a choice on what operating system to use for your Zimbra Collaboration Suite implementation, I would recommend using Red Hat Enterprise Linux 4 (RHEL4). The reason for this is that, according to the Zimbra documentation, all features ZCS is made up of, are offered on RHEL4. The other two major operating systems (SUSE and MAC OS X) each have limitations as will be discussed later in the tutorial. All that being said, Email Collaboration Services, Inc (EmailCS) will use RHEL4 (32 bits) as its operating system of choice. Now we will walk through the Red Hat installation process.

[edit] Installing the Red Hat Operating System

  1. When the Red Hat installer boots up from the install CD, the user is presented with the initial splash screen, shown in the following screenshot. Once the screen is loaded, simply click on Next to proceed.
  2. The next screen prompts the user to select the Language they would like to use during the installation. Click on the language of choice and click NEXT. I recommend choosing English here.
  3. The Keyboard Selection screen is next, and the user will now have the opportunity to select which keyboard layout they would prefer to use during the installation. Choose the correct language, depending on your own keyboard.
  4. The first part of the installation where we have an opportunity to optimize our installation for Zimbra comes next, which is the Disk Partitioning Setup screen. In our case, we will choose to Manually Partition with Disk Druid.
  5. The easiest way to partition our disk, is to delete any current partitions we do not need. I am making the assumption that this server will only be running one operating system, RHEL4, and will not be a dual or multi-boot situation. Once the partitions are cleaned up, we will create a partition scheme consisting of the following:
    • /boot partition of 100MB
    • swap partition of twice our physical memory (RAM)
    • / partition that is able to grow to fill the remainder of the diskspace
    The following screenshot shows how to create the /boot partition. You may use this as a template to create the other two partitions. Obviously, this partition scheme is OK for our test/demo server, but you should create your own partition scheme depending on your "real life" needs. Once the partitions are created, the partitioning scheme should match the one shown in the following screenshot.
  6. The following screen will ask for a choice of the bootloader you would prefer to use. I would leave this screen as default and click Next.
  7. Due to the fact we are creating an email server, it is critical the server has a static IP address and network configuration. It should not use any DHCP client information, including hostname, DNS, and Gateway. So on the network setup screen, the first thing we need to do is edit our eth0 device and give it a static IP address by clicking the Edit button. At this point, we need to uncheck the Configure Using DHCP checkbox and also make sure that Activate on boot is checked (if you don't, your network card won't be "up" after boot and your server will be unreachable). After entering our IP address information, which you may need to ask your Network Administrator to provide, click on OK. The rest of the screen should be used to enter the rest of the networking information including the hostname. The hostname should be the fully qualified domain name (FQDN) of the server. In our case, that would be zimbra.emailcs.com. Also, please note that the DNS server will be the same IP address of the server we are creating. This is because we want to make sure we have complete control of the DNS information when configuring our server. After Zimbra is installed, I would recommend not running DNS on this server, but providing another server to handle DNS by editing the /etc/resolv.conf file.
  8. At the time the server is installed and until Zimbra has been installed, you should disable the firewall. This is recommended by Zimbra, due to the several "non standard" ports used by Zimbra to communicate with itself. Once your server is running, you'll be able to re-enable it with the correct configuration. You'll have to disable SELinux too (mandatory from Zimbra).
  9. Now Red Hat will try and make you think twice about disabling the firewall and will prompt you with a warning message. Simply continue with the message, by clicking Proceed, knowing that we will enable the firewall as soon as Zimbra is up and running.
  10. The following screens will prompt the user to enter any additional languages, set the time zone, and create a root password. These are all user-specific so once you have completed these three screens, the installation will ask you what packages to install with the installation. This is a great way to save time on preparing the server for the Zimbra installation, as we could customize the packages Red Hat installs, so we will not need to install them later. So please make sure you click on the Customize software packages to be installed radio button before proceeding.
  11. Considering we're setting up a test/demo server, we can add some graphical interface and additional tools. These tools are not mandatory and I think they should not be set-up on a production server. On the package selection screen, select the following packages: Desktops X Windows System Gnome Desktop Environment Applications Editors Graphical Internet Text-based Internet Servers Server Configuration Tools DNS Name Server Development Development Tools Gnome Software Development Legacy Software Development System Administration Tools System Tools
  12. The final screen of the install gives you a chance to make any changes to the install configuration before any changes are made to the server. By clicking Next on this screen, the installation will begin. The entire installation process will take anywhere from 10 to 30+ minutes, depending on the speed and hardware configuration of the server.
  13. Once the install is complete, the system will reboot and a post-installation screen will present the user with an opportunity to join the Red Hat Network and also to configure the screen resolution of your monitor. Once you have completed these screens, the main login screen will be displayed, and our server is ready to be installed.

[edit] Installing Zimbra Collaboration Suite

  1. After the server has been installed, and prior to installing Zimbra, you must follow the instructions defined earlier for modifying the /etc/hosts file, configuring DNS, and disabling sendmail.
  2. As mentioned at the beginning of this tutorial, by now you should have downloaded the Zimbra Collaboration Suite and also registered for a free trial license. So we will continue assuming that the ZCS installation file has been downloaded to our server. Please note from now on, make sure you are logged in as root or have switched to the root user by entering: su
  3. To install ZCS, we will need to unzip the download package. The best way to handle this would be to create a temporary directory to unpack the installation files by logging in as root and then from a terminal typing the following command: mkdir /temp
  4. Once the temp directory is created, copy the zipped installation file to the temp directory. I have downloaded the file to my Desktop, so I will copy the file from my Desktop to the /temp directory using the following command: cp /home/mresnick/Desktop/zcs-NETWORK-4.5.6_GA_1044.RHEL4.tgz /temp
  5. Now we will change our directory into the /temp directory: cd /temp If you have not downloaded the file yet, you can do it now, using the wget command line tool: wget http://files2.zimbra.com/downloads/4.5.6_GA/ zcs-NETWORK-4.5.6_GA_1044.RHEL4.tgz
  6. In the same directory, put the License file you received by email: ZCSLicense.xml
  7. In the /temp directory, we could now unpack the installation files: tar xvzf zcs-NETWORK-4.5.6_GA_1044.RHEL4.tgz
  8. Unpacking the file will create a zcs directory within /temp that we will need to change directory into, to install our server: cd zcs
  9. From within the /temp/zcs directory there is a file called install.sh. This is the file that will launch the installer for Zimbra. ./install.sh
  10. The first thing the installation program will do is check and make sure there are no other installs of the Zimbra Collaboration Suite. Since this is a fresh install, no previously installed Zimbra components are found and we could hit Return to continue.
  11. The second step of the install process is to check and make sure that all prerequisites and requirements have been met, prior to continuing with the installation. If you followed every step in this tutorial, then during the install the check should be successful. If not, the installer will let you know what needs to be installed or configured prior to proceeding with the installation. Assuming all is OK, hit RETURN to continue.
  12. Now we will be prompted which components we would like to install. As the installer cycles through the installable packages, you could just hit the ENTER key as the Y is the default to install the package. If you would like to exclude a package, type N and then hit ENTER on that package as it is prompted. In our case, we will install everything. After selecting the desired packages, the installer will prompt the user with a summary of packages to be installed. If all looks well, type Y and hit ENTER to continue. The default here is N, to not continue.
  13. After all of the packages are installed, we are prompted with an opportunity to change any of the default settings. At this time, the only change we will make is to change the administrator password for administering the Zimbra server. First enter 6 at the Address unconfigured items prompt and press ENTER.
  14. Next, you will be presented with a list of options that could be changed. Type 4 for the admin password at the Select prompt and hit ENTER.
  15. Type in the new password at the prompt noting that the password must be a minimum of 6 characters. Also note that the password is case-sensitive.
  16. After entering the password hit ENTER and then you will be returned to the Store Configuration screen.
  17. Now type 12 then ENTER to change the web server mode and activate http and https.
  18. Type both in order to have both http and https working, then hit ENTER.
  19. Now type 20 then ENTER, in order to enter the path of the license file.
  20. Type /temp/ZCSLicense.xml, then hit ENTER.
  21. Type r and then hit ENTER to return to the main menu.
  22. Once all changes have been made, you'll see CONFIGURATION COMPLETE at the bottom of the Main menu. Type a to apply the new configuration. At this time, we are also prompted to save the configuration file, and then we are prompted to make sure we are ready to modify the system. Be careful and notice that the default here is No, so before hitting ENTER too fast, type Yes at the continue prompt.
  23. The installer will now proceed to finalize the Zimbra installation and when all is said and done, a prompt notifying the user that the configuration is complete will be displayed. Hit ENTER to exit; and the installation of Zimbra Collaboration Suite on Red Hat Enterprise Linux 4 is complete.

[edit] Installing on SUSE ES 9

The install of SUSE Enterprise Server 9 should be similar to Red Hat in that you will want to partition the drives the same way as described in step 5, as follows:

  • /boot partition of 100MB.
  • swap partition of twice our physical memory (RAM).
  • / partition that is able to grow to fill the remainder of the diskspace.

A "default install" should be used. In the Network Devices section, a static IP address should be used along with entering Zimbra for the hostname and emailcs.com for the domain, creating a Fully Qualified Domain Name of Zimbra.emailcs.com.

Also, during the install, you will be prompted to configure the OpenLDAP server. At this time, the OpenLDAP server should be disabled, as to not conflict with the Zimbra-LDAP server. Once the operating system is installed, there will be a few more pre-installation steps prior to installing the Zimbra Collaboration Suite. Also please note that on SUSE ES 9, the Zimbra clustering feature is not supported.

[edit] Preparing SUSE ES 9 for Zimbra

  1. The Default Install does not install GMP (GNU Multiple-Precision Library). So the first thing we need to do is use the YaST (Yet Another Setup Tool) to install the GMP library. Open up the YaST tool and select Install and Remove Software.
  2. In the Search text box, enter in GMP and click on Search. Then proceed to select the GMP checkbox and click Accept.
  3. With the YaST tool open, we will also need to install BIND to configure DNS on the server. So in the Search box, type bind and click Search. Just as we did with GMP, select the bind and bind-utils checkbox and click Accept.
  4. YaST offers a GUI tool for configuring the DNS server, which you could use to configure the DNS information required for the install of Zimbra. However, if you prefer to configure DNS manually, you can edit the /etc/named.conf and /var/lib/named/master/emailcs.com files as described in the section above. To use the DNS Server Tool, reopen YaST and select DNS Server from the Control Center.
  5. The first screen will ask if we want to set any Forwarder Settings; we could just leave the default setting of Set Forwarders Manually and click Next.
  6. The next screen will ask us to create a zone file. We will proceed to name the Zone emailcs.com and leave the Zone Type as Master. We can then click Add, which will add emailcs.com to Configured DNS Zones. To edit the DNS information of our newly created zone, we will click on Edit Zone.
  7. In the Zone Editor, there will be several tabs displayed. We will first start with the NS Records tab and add zimbra.emailcs.com as our Name Server.
  8. The next tab will be the MX Records tab. Here we will add zimbra.emailcs.com as our MX record, with a Priority of 10 and then click Add. Note- Priority is used when you have several MX records and you want to organise the order the MX are used by the other mail servers on the Internet. The lower the number is, the higher the priority is: if you have two MX, one with priority 5 and the other with priority 10, the other MTA on the Internet will send the mail to the "5" MX. If this one does not answer, they'll try the "10" one.
  9. Finally, on the Records tab, we will need to enter two records. An A record for mapping our host name emailcs.com to the IP address of the server, and also creating a CNAME for zimbra.emailcs.com. When entering the CNAME, be sure to enter a period (.) after zimbra.emailcs.com. and emailcs.com., just as we would if we edited the files manually.
  10. Lastly, we need to make sure that our DNS server will start up at reboot. To do this, we need to edit the DNS Start Behavior and make sure the radio button for On Start DNS Server Now and When Booting is selected. Once all of this is completed, click Finish and we are ready to start installing Zimbra. The installation of the Zimbra Collaboration Suite is identical to that of installing the Suite on Red Hat Enterprise Linux 4. Therefore, please follow the steps described in the Installing Zimbra Collaboration Suite earlier in this tutorial.

However, be sure to download the correct ZCS archive from Zimbra's website there's a different archive for each supported operating system.

[edit] Installing on MAC OS X

The MAC OS X server does not include these Zimbra features:

Searching and indexing attachments

Viewing attachments as HTML

Clustering

However, if you choose to use MAC OS X server (it should be version 10.4.7) as your operating system of choice, there are a few configurations you will want to have completed before attempting to install the suite.

[edit] Preparing MAC OS X Server for Zimbra

When installing MAC OS X server, the default install should work fine and install all of the necessary prerequisites for Zimbra. However, it is important that you configure a static IP address and hostname (zimbra.emailcs.com) during the install, or at least prior to attempting the install of Zimbra. Also, you may follow the instructions above to manually configure DNS on the server. On MAC OS X, the files that need to be configured are /etc/named.conf and /var/named/emailcs.com. Once DNS is configured, you will need to start the DNS service as follows:

  1. Open up Server Admin by clicking on Go | Applications | Server | Server Admin.
  2. With the Server Admin application open, find DNS in the list and make sure to start the service in the upper-right-hand corner of the screen, as displayed in the following screenshot: Java 1.5 is required to be installed and configured on the server prior to installing Zimbra as well. Java package could be installed with the Software update application. Once it is installed, you need to follow these steps to configure Java 1.5 as the default Java Virtual machine on the server.
  3. Open up a terminal and change directory to the following: cd /System/Library/Frameworks/JavaVM.Framework/Versions
  4. Remove the CurrentJDK symbolically linked file sudo rm CurrentJDK
  5. Create a new symbolic link to the 1.5 version of Java sudo ln s 1.5.0 CurrentJDK Once this process is completed, we can go ahead and install Zimbra.

[edit] Installing the Zimbra Collaboration Suite

When downloading the Zimbra Collaboration Suite from zimbra.com, you are actually downloading a Disk Image (dmg) package, and therefore the process for installing Zimbra on MAC starts out completely different than the linux servers discussed earlier. To begin the installation:

  1. Double click on the zcs.dmg file and a window will open up displaying the zcs.mpkg file. Double-clicking this file will start the installation.
  2. Next the package will check to make sure the software is compatible with the server you will be installing it on. Simply click on Continue to proceed with the installation.
  3. When the server check is complete, the Welcome to the Zimbra Collaboration Suite Installer screen will appear. Again, simply click on Continue.
  4. No software installer would be complete without a Software License Agreement screen, which of course appears next, along with an opportunity to select the language you would like to use. Click Continue and then Agree to continue with the installation.
  5. Next we must select a destination for the installer to place the Zimbra files. In our case, we only have one hard drive, so we will select the drive and click Continue.
  6. Finally, when all is done, the installer is ready to go by clicking Install.
  7. Once the installer is completed, we will be given instructions to run a perl script to complete the setup of the suite.
  8. To complete the install, we must run the zmsetup.pl script by opening a terminal and entering the following command: sudo /opt/zimbra/libexec/zmsetup.pl
  9. The zmsetup.pl script behaves similarly to the install.sh script we ran on our Linux servers. So at this time you could just follow steps 9 to 17 in the Installing Zimbra Server earlier in this section.
  10. You should now have Zimbra Collaboration Suite successfully installed on MAC OS X Server.

[edit] Post-Installation Steps

Now that our Zimbra Collaboration Suite server has been configured and installed, there are a few post-installation steps we will need to complete before moving on. We will be using Red Hat Enterprise Linux 4 to make these changes, however, you could just apply these steps to your operating system. The first step will be to enable our firewall so our server is protected.

[edit] Configuring the Firewall

As you will recall, we disabled the firewall when installing our operating system. With Zimbra installed, we can now open up just the ports necessary to successfully use our collaboration server:

  1. First, we must login as root on our server by typing su at the shell prompt.
  2. Next, we will open up the firewall configuration tool by typing: system-config-securitylevel
  3. This will open up the Security Level Configuration Tool as shown on the next page. Here we will need to enable the firewall and select the checkbox next to SSH to allow for remote access to the server (and self access for mail queues management). We will also need to open up the following ports by typing them into the Other ports text box:
    • ttps:tcp
    • 930:tcp
    • op3:tcp
    • map:tcp
    • maps:tcp
    • dap:tcp
    • op3s:tcp
    • 025:tcp
    • 800:tcp
    • 900:tcp
    • 071:tcp
    • 895:tcp
    • 894:tcp
  4. With all the ports entered, click OK and you will be prompted to restart the firewall. Click YES and the firewall configuration is complete.

[edit] Uninstalling Zimbra

If at any time you find it necessary to uninstall the Zimbra Collaboration Suite, the process is actually very simple and straightforward. Uninstalling the ZCS also means deleting all the data (emails accounts, emails, etc.). On Red Hat and Suse you need to:

  1. From a command line, change directory to the /temp/zcs, where you first unzipped the installation file.
  2. As root run the following command: ./install.sh u
  3. The u switch informs the installer to remove any instances of Zimbra it finds.

On MAC OS X, the script is different. Go to the directory you installed Zimbra, and from the command line run the following command: 

sudo install.mac.sh -u

[edit] Summary

In this tutorial, we installed our Zimbra Collaboration Suite for use by Email Collaboration Services, Inc. Although, the company will be using Red Hat Enterprise Linux 4, we discussed installing the Suite on SUSE ES 9 and MAC OS X 10.4.7 as well. We also looked at preparing the server for the installation including editing the /etc/hosts file, installing and configuring DNS, making Java 1.5 the default virtual machine on MAC OS X and turning sendmail off. We also discussed configuring the firewall after installing Zimbra.

Finally, we ended the tutorial with a look at uninstalling the Zimbra Collaboration Suite when and if necessary.

[edit] Source

The source of this content is Chapter 2: Installing Zimbra of Zimbra: Implement, Administer and Manage by Marty Resnick, David Touitou(Packt Publishing, 2007).

Retrieved from "http://www.installationwiki.org/Zimbra"
Personal tools