ee99ee :: Blog

I received what I can only assume is a new type of spam today. It was a short MP3 file and I dared to listen to it. Inside was a low voice behind some static that made it very hard to understand. If you listened closely, the woman was telling me how a new website that was successful in Canada and Europe was being launched in the US. She then proceeded to thank me for listening.

It was very disturbing. Spammers sure are becoming very desperate in their attempts to penetrate filters these days. It’s pathetic.

-Chris

P.S. — No, I didn’t visit the website and won’t share it or the file with anyone.

Jake has been testing our Zimbra 4.6.7 setup using the beta version of the Zimbra Connector for Outlook. We contacted Zimbra directly and were able to get access to the beta. In our tests, the functionality of the connector is good, but the stability is not. Jake is running Vista and Outlook 2007 and is reporting almost unusable stability of Outlook when using the Zimbra client. Hopefully these issues will be resolved soon and I think we’ll be set to use it in production.

Additionally, he tested the mobility features and found that they work well on his Windows Mobile smart-phone.

Zimbra the Release Candidate of Zimbra 5.0 (Network Edition) should be out soon — like, next week — so I look forward to seeing what changes have been implemented there.

Additionally, Jake is in discussions with Scalix about pricing, features and such so if the price is right we’ll be looking at that soon too. I also want to take a look at Open Exchange and will be doing so soon.

Today I installed Zimbra for the first time. Zimbra is an open-source, Linux-/UNIX-based collaboration and mail server suite, similar in features to Microsoft Exchange. It has native support for MAPI and is supposed to work great with Outlook. It also has advanced mobility features that put it on par with Exchange.

I spun up a Virtual Machine on our VMware server and loaded Ubuntu 6.06 Server. Once the base install was done, I removed the CD-ROM source from /etc/sources.list and ran:

# apt-get update

This made the package manager know it was to use FTP or HTTP to download packages. Next, I ran the following:

# wget http://files.zimbra.com/downloads/4.5.7_GA/zcs-NETWORK-4.5.7_GA_1319.UBUNTU6.tgz
# tar zxf zcs-NETWORK-4.5.7_GA_1319.UBUNTU6.tgz
# cd zcs
# sudo ./install.sh

This ran through the initial process and listed several packages that needed to be installed, so I installed them next and re-ran the installer:

# sudo apt-get install libidn11 curl fetchmail libpcre3 libgmp3c2 libxml2 libstdc++6 openssl perl libexpat1 libstdc++5
# sudo ./install.sh

This went through several very obvious questions as part of installation, including the administrator password. At one point near the end, it asked for my license file. I signed up for a free trial on Zimbra’s website, and that was emailed to me in the form of a XML file. I simply used SCP to move that up to the server, typed in the path to the file and it worked great.

I made one big mistake though: The password I provided for the admin account had a special character that must have thrown the setup program off. Although it reported the admin user was created, post-installation user account listings showed that other default users had been created but the admin user was nowhere to be found. Additionally, I couldn’t login to the admin using the admin username and password I provided. Bummer…

So, I spent the next two hours trying to figure out how to add a new admin. It wound up being a very simple command:

# zmprov ca testadmin@domain.com test123 zimbraIsAdminAccount TRUE

The key here is the “zimbraIsAdminAccount TRUE” attribute. Once I did that, I was able to login to the admin panel and everything worked out of the box as far as I can tell. I was able to point my domain’s MX record to the public IP of the server (I placed it behind a NAT) and before long I had setup another domain with a few user accounts and had mail flowing.

Had the admin password not screwed up, it would have been working about 20 minutes — which is amazing.

It seems to use a local LDAP server by default, but I did have the option to specify an LDAP server during the installation as well as clustering options that I didn’t touch, since this was a VM. Apparently it stores user account data in LDAP and mail schema information in a MySQL 5.0 database which was also installed. I’m not sure yet where it stores the data (email, etc.) but I think it’s on the raw file system as it should be.

The web interface is pretty cool with lots of AJAX. That said, it doesn’t work in Safari 3.x beta yet; I read they’re working on that. Since that is my primary browser, I was using Camino 1.5 instead.

Jake is going to be testing the MAPI connector and the mobility features and I’m sure he’ll report on that soon.

I’m going to move on to setting up a Scalix server next I believe. We’re looking for a good open-source, Outlook-supporting collaboration server that’s on par with Exchange server.

So I was upgrading WordPress for a client today, going from version 2.1.1 to 2.3. I uploaded the files, ran the upgrade script and got a bunch of errors. Apparently I had forgotten to give the database user more access than just select, insert and update; the update had to create a few tables.So I went back, edit the database user and gave them full access to the database. I went to run the upgrade script again and it said my database was up to date. Looking at the public blog, I just got a bunch of MySQL errors about the wp_terms table gone missing. Great…So, looking into this further I found how to fix it:

1.  Change the “db_version” to 3441, which is the version for 2.0.
2. Re-run the database update script (making sure to have full access for the db user)

All in all, that fixed it!