V. INSTALLING ZIMBRA
Estimated Time : 10 minutes

Minimal server appliance has all required package for installing Zimbra. Postfix and all other applications that could potentially conflict with Zimbra package deactivated automatically on initial boot. You do not need to install additional package because all necessary package is bundled inside the appliance.

1. Go to folder /opt, download Zimbra binary installer from  Zimbra Website (At this writing, zimbra latest version is version 7.1.3), uncompress and then run the setup installer

   cd /opt
   wget -c http://files.zimbra.com/downloads/7.1.3_GA/zcs-7.1.3_GA_3346.SLES11_64.20110930001521.tgz
   tar -zxvf zcs-7.1.3_GA_3346.SLES11_64.20110930001521.tgz
   cd zcs-7.1.3_GA_3346.SLES11_64.20110930001521
   ./setup.sh
   

   `
   

2. Answer the question “Do you agree with the terms of the software license agreement? [N]“ with Y. Off course, because if you answer N, the installation process will simply stopped successfully
3. Press ENTER for all installation package. The default answer is Y. Leave the “zimbra-memcached” and “zimbra-proxy” as is (will not be install) because zimbra-memcached and zimbra-proxy only required for multi server installation.
   `
   
4. Zimbra will install the required application package and at the end will be check DNS records. On the DNS confirmation : “DNS ERROR resolving MX for mail.vavai.net
   It is suggested that the domain name have an MX record configured in DNS
   Change domain name? [Yes]“. Just answer “Y” for change domain and then typing your domain name (in my case : vavai.net) instead of your hostname (mail.vavai.net)
   `
   
5. Press 3  on the question “Address unconfigured (**) items  (? – help)” and press 4 on the question “Select, or ‘r’ for previous menu [r]“ to change the default password for Zimbra Admin
6. Fill in Zimbra Admin password. Note : Password will be displayed on plain text
7. Press ENTER on question “Select, or ‘r’ for previous menu [r]“
8. Press A on question “*** CONFIGURATION COMPLETE – press ‘a’ to apply
   Select from menu, or press ‘a’ to apply config (? – help)” and then press ENTER twice, following with “Y” and then  press ENTER on question “The system will be modified – continue? [No]“
   `
   
9. Zimbra will perform the system installation process. Please be patient . The installation will took 5-10 minutes depending your server performance (processor and memory)
10. Zimbra Open Source Edition will asking an optional registering your installation for statistics purpose only. Answer for this question are up to you

    You have the option of notifying Zimbra of your installation.
    This helps us to track the uptake of the Zimbra Collaboration Suite.
    The only information that will be transmitted is:
    The VERSION of zcs installed (7.1.3_GA_3346_SLES11_64)
    The ADMIN EMAIL ADDRESS created (admin@vavai.net)Notify Zimbra of your installation? [Yes]
    

11. Installation is complete, run the command :

    su - zimbra
    zmcontrol -v
    zmcontrol status
    

    `
    

12. Open the browser and go to http://your-zimbra-server-ip (in my case : http://192.168.1.250) or http://zimbra-hostname (in my case : http://mail.vavai.net) to access Zimbra Webmail
    `
    
13. Zimbra management can be done using the web admin with https protocol and default port 7071 : https://192.168.1.250:7071 or https://mail.vavai.net:7071

VI. SUMMARY

Zimbra Installation is very easy and requires a short time if we use the right tools. It can be done by using an appliance to simplify the installation process because I’ve prepare all the Zimbra requirement packages to the appliance and remove unnecessary application.

Hopefully this is useful for anyone who needs it. Warm regards from Jakarta-Indonesia

Note : I’m using YaST for openSUSE screenshot because I already have it. However, there should no significant difference between a screenshot with YAST configuration on SLES

IV. CONFIGURING LOCAL DNS SERVER

Estimated time : 3 minutes

Zimbra need an A & MX records that pointing to it’s IP Address. We could use/modify existing DNS records to meet with our requirement but I would prefer to installing local DNS server for it’s flexibility. If you’re currently using an existing & running mail server and need to replace it with Zimbra, you should not change any MX entry before completing and testing the configuration. Incomplete configuration on production mail server may impact to bounce mail, so, we need a local DNS server to prevent the impact and to do a full test before activating mail server for production use.

Setting up a DNS server on openSUSE for Zimbra requirement should be easy by using YAST. Below is a step by step, please change the IP and host name to meet with your environment on previous tutorial.

1. Type : yast dns-server on the console/terminal
2. Click Next on first configuration wizard : Forwarder List
   

   DNS Server wizard : Initial Windows

3. Add a new Zone. Typing your domain name on Zone name, choose Masteron type of zone and then click Add (ALT+A)
   

   Add DNS Zone

4. Press ALT+I (Edit) to modify your zone
   `
   
5. Just leave the first tab (Basics) as is. Press ALT+D to move to the second tab : NS Records
6. Write ns1 on Name Server to Add option and then press ALT+A to add the records. YAST will be smart enough to autocompleting the entry and give a fully qualified domain name to the records
   `
   
7. Press ALT+X to move to the third tab, MX Records. Fill in mail as Zimbra host name (see your configuration on first tutorial) on Address option, Give it a priority number (lower means highest priority) and then Press ALT+A to add MX records. Again, YAST will be smart enough to autocompleting the entry and give a fully qualified domain name to the MX records
   `
   
8. Leave the fourth tab as is, except you need to modify to SOA option
9. Move to final tab. Type : ns1 on Record key, choose A (Address Records) as records type and write Zimbra IP on records value and then press ALT+A to Add the records. Still on the final tab (Records), create the second Address Records for Zimbra hostname. Type mail on Record key, choose A (Address Records) as records type and write Zimbra IP on records value and then press ALT+A to add the mail Address Records
   `
   
10. Press ALT+O (OK)
11. Press ALT+N to go to the next wizard
12. Press ALT+S to Choose On : Start up now and When Booting and then press ALT+F  to completing DNS configuration. This will ensure that DNS service will be active on start up
    `
    
13. Restarting DNS Service by running the command : service named restart on console/terminal
14. Testing the DNS records using dig and nslookup : nslookup ns1.domain.tld and nslookup mail.domain.tld. if the setting is done correctly, DNS Server will respond with the Zimbra IP.
    `
    
    `
    
15. Here is my DNS server configurations that can be accessed on the file /var/lib/named/master/vavai.net
    `
    

Continue to the third part : Installing Zimbra Mail Server on SLES 11 SP1 64 bit in less than 30 Minutes-Part 3

1. WARNING : This guide using Preload ISO and will erase the entire contents of hard disk!  If you do not want to delete your existing data, consider using Virtualization server or use ISO-LiveCD.
2. Zimbra server will be using a private IP which will be translated into public IP using NAT
3. Zimbra will be setting up using Split-DNS concept. This means that in the internal network, mail server will be recognized based on a private IP network, while from the outside will be recognized based on the public IP. For this purpose, the internal DNS will be set up in Zimbra Mail Server
4. Zimbra Fully Qualified Domain Name : mail.vavai.net, private IP : 192.168.1.250

I. DOWNLOAD MINIMAL SERVER

DomainKeys or DKIM signature  basically  allowing good senders to “sign” a message to prove that it really did come from them. This process is obtained by signing  the outgoing mail with a specific code corresponding domain name and identity of the mail server so it is considered valid and convincing as an authorized sender.

Domain Keys Identified Mail (DKIM) is a technology designed to make it difficult or impossible for criminals to steal the identities of legitimate organizations. This authentication technology allows good senders to “sign” a message to prove that it really did come from them..

DKIM originally written as sender authentication protocol developed in order to address the problem of forged email messages. Yahoo! released the DomainKeys specification and Cisco released the Internet Identified Mail specification. Both methods are based on cryptographic message signing. The two efforts have been merged, and the combined specification is known as DomainKeys Identified Mail (DKIM).

The problem is, DKIM is not very easy to set up. We need to setup the mail server  and also add a TXT records into public DNS server. Not all providers provided and authorized us to add or modify TXT records. In some cases, we must create a support ticket so they make the TXT records according to our requirement. If so, how can we check that the TXT records are made is correct?

There are 4 ways that we can do to test DKIM Records in DNS, which is as follows:

1. By using CLI with the following command : dig namaselector._domainkey.namadomain.tld TXT ex : dig selector._domainkey.vavai.web.id TXT. Belor are an example of the response :

   # dig selector._domainkey.vavai.web.id TXT; <<>> DiG 9.7.1-P2 <<>> selector._domainkey.vavai.web.id TXT
   ;; global options: +cmd
   ;; Got answer:
   ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 63688
   ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0;; QUESTION SECTION:
   ;selector._domainkey.vavai.web.id. IN TXT;; ANSWER SECTION:
   selector._domainkey.vavai.web.id. 172800 IN TXT "v=DKIM1\; r=postmaster\; g=*\; k=rsa\; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDJ5IZT5e5nvmkotroz5ylTlwU8yEEZ+v/576aI+w6TkbP4XibYxDsWVweXXtVeQQmw8AwYuK5R9b373Xqu+Hv9HNAJoAteKF/qlKcZc5Akhj5B7P1imXaurZkkIBp63yBZyZRralzQYNT3UrVB7M/xONMWXcU9xm7Zv1PzH1Y1OQIDAQAB";; Query time: 85 msec
   ;; SERVER: 192.168.1.1#53(192.168.1.1)
   ;; WHEN: Mon Dec 5 08:18:00 2011
   ;; MSG SIZE rcvd: 316

2. By using web  : http://dkimcore.org/tools/dkimrecordcheck.html. Type the name of the selector and the domain name then click the Check button.
   `
   
   `
   
3. By sending a blank email to the following address : sa-test@sendmail.net or check-auth@verifier.port25.com or autorespond+dkim@dk.elandsys.com and check the respon.
4. By sending an email to a Gmail address or Yahoo and see the message header Signed By as shown  below`
   

Hopefully this can help to check whether your DKIM  records meets with standard or still require a modification.

Imapsync is one very useful tool because it can be used to perform backup and synchronization of all email content, both structure and content. For example, if we have an inbox, sent items, drafts, trash, etc in the old mail server, we can copy the structure and content seamlessly into the new mail server. Imapsync even able to backup a folder other than the default folder, such as copying a folder called “Vavai” and “Urgent”, etc inside my inbox folder.

The following tutorial is the process of installation and usage of Imapsync on SUSE Linux Enterprise Server 11 SP 1, although Imapsync can be run in almost all Linux systems.

INSTALLATION

Run the following command via the console / terminal:

zypper ar http://download.opensuse.org/repositories/devel:/languages:/perl/SLE_11 perl
http://download.opensuse.org/repositories/home:/pheinlein/SLE_11_SP1/ imapsync
zypper ref
zypper in imapsync perl-Date-Manip perl-Mail-IMAPClient

Note : I’m using package on openSUSE Build Services to install Imapsync. Do not forget to change the version and type of openSUSE distribution in accordance with your running system.

USAGE

Here is an example of using Imapsync to synchronize a mailbox from the mail server with an IP 192.168.10.2 to the mail server with an IP 192.168.10.1 (Imapsync can also use server hostname instead of ip address):

imapsync - host1 192.168.10.2 - user1 budi@namadomain.com - passwordbudi password1 - host2 192.168.10.1 - vavai@namadomain.co.id user2 - password2 passwordvavai - noauthmd5 -ssl1 -ssl2

The above command will copy the mailbox budi@namadomain.com on server 192.168.10.2 to the mailbox vavai@namadomain.co.id on server 192.168.10.1.

Let’s see the user account between primary server and secondary server. As you may notices, Imapsync can be used to copy the email user A to the same mailbox on another server or to a different mailbox on another server

NOTE:

1. - – follows by words are Imapsync parameters. –user1 budi@namadomain.com means that user account in first server is budi@namadomain.com
2. Imapsync can be used to synchronize all mail server that supports the IMAP protocol (as the name implies, Imapsync, not POPsync especially lipsync ), so it can be used on Postfix+Imap, Sendmail + Imap, Qmail+Imap, MDaemon, Microsoft Exchange etc
3. Imapsync requires a password for each account to be successfully synchronized.
4. Imapsync is able to synchronize the password if we know both accounts and password. We have to equate all the passwords if you want to easily synchronize with the command above. Oon some mail servers, we can use Imapsync with the – -authuser to access user mailboxes by using admin privileges.

I’m using openSUSE 12.1 64 bit on this tutorial but the steps can also be applied to earlier versions (11.x) as well as on SLES 11 SP1. I also use VirtualBox for All distributions binary package, although for openSUSE we can also use an RPM-binary package.

Lets get started :

1. Install openSUSE 12.1 Minimal Server (Text Mode)
2. Installing package for VirtualBox Kernel Modul

   zypper in kernel-source make gcc gcc-c++ pam-devel kernel-syms SDL

3. Download VirtualBox binary package with the Extension Pack from www.virtualbox.org

   cd /opt/
   wget -c http://download.virtualbox.org/virtualbox/4.1.6/VirtualBox-4.1.6-74727-Linux_amd64.run
   wget -c http://download.virtualbox.org/virtualbox/4.1.6/Oracle_VM_VirtualBox_Extension_Pack-4.1.6-74713.vbox-extpack
   

4. Install Virtualbox

   chmod +x VirtualBox-4.1.6-74727-Linux_amd64.run
   ./VirtualBox-4.1.6-74727-Linux_amd64.run
   

5. Install the Extension Pack

   chmod +x Oracle_VM_VirtualBox_Extension_Pack-4.1.6-74713.vbox-extpack
   VBoxManage extpack install Oracle_VM_VirtualBox_Extension_Pack-4.1.6-74713.vbox-extpack
   

6. Create a user for VirtualBox web access

   useradd vbox
   passwd vbox
   New Password : vbox
   Reenter New Password : vbox
   

7. Create a VirtualBox web configuration on /etc/default/

   vi /etc/default/virtualbox
   

   with the following contents :

   VBOXWEB_USER=vbox
   

8. Install LAMPP server and php5-soap package by using zypper

   zypper in -t pattern 'lamp_server'
   zypper in php5-soap
   

9. Edit /etc/apache2/default-server.conf and replace Options None to Options ALL so Apache will display the contents of the directory index

   vi /etc/apache2/default-server.conf
   

10. Download latest phpvirtualbox package

    cd /opt
    wget http://phpvirtualbox.googlecode.com/files/phpvirtualbox-4.1-5.zip
    unzip phpvirtualbox-4.1-5.zip -d /srv/www/htdocs
    cd /srv/www/htdocs
    mv phpvirtualbox-4.1-5 phpvirtualbox
    cd phpvirtualbox
    

11. Rename config.php-example to config.php and modify the contents to an appropriate configuration

    mv config.php-example config.php
    vi config.php
    

    var $username = 'vbox';
    var $password = 'vbox';
    var $location = 'http://192.168.1.111:18083/';
    var $consoleHost = '192.168.1.111';
    

    Note : 192.168.1.111 is my VBoxHeadless Server

12. Restart web server and run the VirtualBox services

    service apache2 restart
    vboxwebsrv --host 192.168.1.111 -b
    

13. Open a browser and go to http://VBOXHeadLess-Address/phpvirtualbox, login with the default user: admin with password : admin

On the client side, access the VirtualBox VM by using rdesktop or krdc with following examples :

rdesktop 192.168.1.111:3389

Here is the view of VM on VBoxHeadless, running Minimal Server Appliance.

Note :

1. If you encounter an error message: PHP does not have the SOAP extension enabled, install php5-soap package from openSUSE 11.2 OSS repository
2. If the Console does not open or error, power off the virtual OS then click on Settings -> Select Display -> Remote Display -> Checklist on the Enable Server and give the port on the Server Port, for example 3389 -> OK then run again. If you have more than one virtual OS,  do the similar process and change Server Port to 3390 and so on

How to use this small script to fit with our requirement ?

1. If you have fast and stable Internet connection, skip step 2. We can directly use network installation by using download.openSUSE.org as base installation source
2. Preparing network installation source.  I’m using http installation source by mounting openSUSE 12.1 64 bit ISO image onto apache root folder directory. Server has ip address 192.168.1.104 and I mount the iso file to a folder /srv/www/htdocs/12.1 so my repository can be accessed via an http address http://192.168.1.104/12.1
3. Download the script (Right clik and save as). I make a backup of script on my blog : http://bit.ly/tgPUi2
4. Run the script with the following command :

   chmod +x setupgrubfornfsinstall.sh
   ./setupgrubfornfsinstall.sh
   

5. Follow the instructions given by the wizard
6. Step 1 : Choose either x86 or x86_64 architecture. The initial wizard will be shown if your system supporting the x86_64 architecture

   

7. Step 2 : Choose installation source. I choose “Specify URL manually” for current scenario, although I can choose another option (SLP or internet install from openSUSE.org)

   

8. Type the address of the repository as noticed on  the second step, on mine : http://192.168.1.104/12.1
9. Select the most convenient  screen resolution based on your preferences
10. Klik OK and wait until finished
11.  finally, reboot your computer and choose network installation from GRUB menu while rebooting system

Below are a simple script to bulk-reset Zimbra account password :

#!/bin/bash
clear
USERS=`su - zimbra -c 'zmprov -l gaa'`;

for ACCOUNT in $USERS; do
ACC1=`echo $ACCOUNT | awk -F@ '{print $1}'`;
ACC=`echo $ACC1 | cut -d '.' -f1`;

if [ $ACC == "admin" ] || [ $ACC == "wiki" ] || [ $ACC == "galsync" ] || [ $ACC == "ham" ] || [ $ACC == "spam" ]; then
echo "Skipping system account, $NAME...";
else
echo "Modifying $ACCOUNT password...";
su - zimbra -c "zmprov sp $ACCOUNT NewGeneratedPassword";
su - zimbra -c "zmprov ma $ACCOUNT zimbraPasswordMustChange TRUE;
echo "Done!"
echo ""
# read anykey
fi
done
echo "Modifying password for all user has been finished successfully"

Note : I think it would be better to include some personal ID (part of user name or any fields) into generated-password so all password will be a semi-random password. In my case, I’m using user birth date or part of their name for their generated password to prevent anyone trying to login to any mailbox. It’s not really secure but in my case, it was sufficient for temporary purpose.

If you have similar experience, I’ve accumulated a few tips to improve mail server performance. I’ve applied all of them on my mail server (also on my client mail server), mostly with Zimbra Mail Server but all the tips can also be applied on another mail server engine :

1. Has a public static IP, not dynamic IP. A lot of mail servers are generally reject or refused mail  delivery connection from mail server with dynamic IP,  because it is often used as a medium of open relay email. If you do not have a public static IP, the best option to be able to sending an eligible email is using relay email through your ISP’s by using SMTP-Authentication
2. IP is not Blacklisted. Mail server with good configuration usually using an RBL Blacklist services such as  barracudacentral blacklist, Spamhaus, SpamCop, etc. If your mail server got trapped by RBL Blacklist provider, the destination mail server would  refused to receive an email from your mail server. Ensure that your mail server is not listed on RBL Provider. Check it out by using a free services from http://www.mxtoolbox.com. If your mail server got blacklisted, try to remove from list by by following the guidelines given from RBL provider
3. Server is not an Open Relay Mail Servers. Open Relay means that mail server act as relay mail server for all domain. Mail server should only sending email from our domain and receive email for our domain. Check your mail server whether it’s an open relay or no by using http://www.checkor.com. Sometimes, mail server accidentally act as an open relay due to incorrect setting on MTA Trusted Networks, e.g : Defining incoming route as trusted network
4. Good DNS Configuration. Bad DNS configuration may caused  delays on delivery & receiving emails. Check your DNS setting by using DNS check provider such as http://www.pingability.com
5. Public IP have a reverse DNS / PTR Records. When you register a domain name with a domain registrar, you usually become responsible for that Forward DNS domain. In DNS terms, the domain is delegated to you.However, you are not also responsible for your reverse records. Your Reverse DNS records are still most likely to be the responsibility of your hosting facility or Glossary Link ISP.To make changed to your Reverse DNS PTR records, you must contact the company where you get your IP addresses from, usually a hosting facility or an ISP. Alternatively, your ISP or hosting company may delegate a range of IP addresses to you, in which case you must configure Reverse DNS and PTR records in your DNS server.
   Reverse DNS Example :

   # nslookup mail.vavai.net
   Server: 172.26.0.8
   Address: 172.26.0.8#53Non-authoritative answer:
   Name: mail.vavai.net
   Address: 202.43.114.252# nslookup 202.43.114.252
   Server: 172.26.0.8
   Address: 172.26.0.8#53Non-authoritative answer:
   252.114.43.202.in-addr.arpa name = mail.vavai.net.
   

   as shown on the above example, mail.vavai.net has public IP 202.43.114.252 and public IP 202.43.114.252 correctly reverse as mail.vavai.net

6. Using RBL Spammer Blacklist to Reject Email from Untrusted Mail Server. This tips utilizing free services from RBL Services Provider by  add an online facility to verifying sender ip/hostname, whether they are eligible sender or spammer. RBL Services prevent any mail transaction if the sender got trapped on their spammer list. This will reduce spam & viruses checking because RBL reject the spammer before going to the mail server.
   
7. Equipped with SPF. Sender Policy Framework (SPF) is an email validation system designed to prevent email spam by detecting email spoofing, a common vulnerability, by verifying sender IP addresses. SPF allows administrators to specify which hosts are allowed to send mail from a given domain by creating a specific SPF record (or TXT record) in the Domain Name System (DNS). Below are an example of SPF TXT records :

   vavai.web.id. IN TXT "v=spf1 a mx include:mail.vavai.web.id ~all"
   mail IN A 202.158.52.xxx
   

   Below are the explanation for the above records :
   
   Mxtoolbox has a service for checking SPF records for your DNS Server records.

8. Using  DomainKeys or DKIM for signing mail. Domain Keys Identified Mail (DKIM) is a technology designed to make it difficult or impossible for criminals to steal the identities of legitimate organizations. This authentication technology allows good senders to “sign” a message to prove that it really did come from them.DKIM originally written as sender authentication protocol developed in order to address the problem of forged email messages. Yahoo! released the DomainKeys specification and Cisco released the Internet Identified Mail specification. Both methods are based on cryptographic message signing. The two efforts have been merged, and the combined specification is known as DomainKeys Identified Mail (DKIM)I’ve written a tutorial about “How to Activating DKIM with Zimbra Mail Server on SUSE Linux Enterprise Server” that may be useful as opendkim implementation guidance on mail server
9. Applying Rate-Limit Sending Message Rules. Rate Limit is a set of rule that could limit the delivery of emails within certain interval. This feature quite useful for preventing DoS or mail spam flooding from  compromised account. Cluebringer PolicyD usually used for rate-limit sending messages
10. Applying SMTP-Authentication for Sending Message. SMTP Authentication is a configuration that requires all e-mail client to authorize and authenticate the user name and password using TLS/SSL protocol  to prevent the possibility of spam from trusted networks

All these  tips should be enough to increase our mail server performance, at least to prevent IP blacklists, viruses and spam. I did not include a backup facility as one of the tips as this will be covering on next article. Hope this helps mail server Administrator to make their life a lot easier than before. Have a lot of fun.

At first, installing server is an interesting jobs but after similar works on some client, I feel bored with the process, ie :

1. Virtualization Server (VMWare, KVM, OpenVZ, Xen, etc) Installation
2. Server OS installation
3. Application Installation
4. Customizing the configuration

I think I could reduce the time for processing the above task by making an appliance using SUSE Studio. An appliance will contains my default server setup and all of packages required by application. The results are Minimal Server Appliance.

Minimal Server Appliance based on SUSE Linux Enterprise Server 11 SP1 64 bit Just Enough Operating System (JeOS). It has all minimal server package with DRBD+Heartbeat from High Availability Extension (HAE) Addons.

The Appliance was successfully tested to running Zimbra Collaboration Suite 7.×.x (latest testing with Zimbra 7.1.3) on VMWare ESXi, Proxmox VE, VirtualBox and KVM Virtualization. Use the following user name and password credentials to make modification to the appliance configuration :

User Name : root
Password : opensuse

By using this application I can reduce the installation time to just a few minutes only. If you wish to make some modification, feel free to clone the appliance and making your own.

Notes from latest releases :

001 : Change Appliance Size to 50 GB (Dynamic Size)
002 : Add netcat package, required by Zimbra zmconfigd
003 : Add Indonesian Local Mirror for SLES 11 SP1 64 bit
004 : Add imapsync package for mail migration and synchronization
005 : Add nmap package for port tracking
006 : Add opendkim package for Zimbra DKIM signature
007 : Add ntp and yast2-ntp-client for time synchronization
008 : Add sqlite3 package, required by Zimbra 7.×.x

I’m intended and mostly using the appliance for Zimbra mail server deployment on top of SLES 11 SP1 64 bit but the appliance itself could be setting up as web server, database server, proxy server, file server, etc.

Minimal Server Appliance available on ISO LiveCD, Preload ISO for physical server deployment and Virtual Image (OVF and VMX extension) for virtual server deployment.

Please let me know if you found any bugs regarding the appliance.