In my role as one of the senior partners at Miley Watts LLP, I've been looking at email/calendaring servers, since we need to move on from the simple email-only setup that we have been using.
I wanted a server that runs under Linux/Unix (SUSE Linux if possible, to make life easiest for me). There are a lot of mail server options for Windows, but security worries me. I know that Windows servers can be secured, I've known people who are very good at it, but I'm not one of them. I feel much happier with the out-of-the-box security that (SUSE) Linux comes with (but feel free to educate me if you think I'm wrong on this).
Of the servers available for Linux, the ones that seemed to match our needs at the brochure-ware level were Novell GroupWise and Zimbra Collaboration Suite. However, the things I've heard from GroupWise users haven't been so complimentary, so we've decided to try out Zimbra first.
My plan is to run Zimbra in a VMware Server virtual session that runs SUSE Linux 10.1. Zimbra's only SUSE release is for SUSE Enterprise Linux 9, but the good news is that it installs without any particular problems under 10.1. You have to make sure you have a couple of packages installed beforehand (as noted in the installation documentation), and otherwise it's pretty smooth. It does help a bit if you already have the mail server configured in your DNS, since Zimbra checks the DNS setup during installation.
After you set the configuration parameters, the installation fails. That's not a big problem, thankfully. Zimbra prints a message to the command line that asks you to correct the problem, and tells you what command to use to restart the installation from where it failed. When you check the log file ("/tmp/zmsetup.log.*"), you see that "/etc/sudoers" has the wrong permissions (440 instead of 640). So, I change the permissions, restart the build, and it completes (I did this a few times as I was playing around).
I really like the fact that when something does go wrong, Zimbra gives a clear indication of what the problem was, and what to do next.
A virtual server looks like a good choice for running Zimbra, because Zimbra wants to be the only application running on the server. We aren't that big a partnership, so it would be wasteful of us to allocate a whole physical server to Zimbra. I'm currently testing Zimbra in a virtual server with 256M of RAM allocated to it (as opposed to the 1G that Zimbra recommend). I can always expand that later as required (the physical server has 4G, or which 3.5G are available for use by VMware virtual sessions).
So far I have established that I can install Zimbra. I've installed it into a virtual session on my development server. Next, I will move that virtual session to our production server, so we can test how it works in practice. I'll let you know how it goes.
Recent Comments