Zimbra Collaboration Suite - A Full Exchange Replacement

For a long time, Zimbra has been an ‘almost but not quite’ Exchange alternative - it offered the web GUI and the Outlook compatibility, but not the standards based calendar protocol (CalDAV) or the mobile device support of its big brother. Zimbra’s latest version, which has only been in the wild for a few months, is different.

Client Software Compatibility

Zimbra provides an Outlook connector enabling Windows users to continue using the app they were trained on. All features in outlook down to shared folders and the GAL are provided. On top of this, in its latest 5.0 version, it has introduced wide ranging mobile device support, covering all major smartphones with the exception currently of the iPhone (though a web interface is provided specifically for iPhone users, this isn’t quite the same as total integration).

A connector for Apple Sync Services is provided, enabling Mac users to connect the native Address Book and iCal applications to tue server with full functionality and interoperability with their Outlook using counterparts.

Zimbra also advertises its mail and calendar facilities in a standard way so that a growing number of standards based clients can also access this information. CalDAV clients such as Apple iCal 3.0 (in MacOS X 10.5), Novell Evolution and Mozilla Sunbird are leading this increase in awareness of a standard calendaring protocol, and Zimbra does well to support it.

Mobile Devices

Most notably, Zimbra 5.0 introduced the dealmaker: support for PalmOS and Windows Mobile smartphones via an installable application, and blackberry support via an extension to BlackBerry’s BES server. This finally puts Zimbra on the radar for corporate deployment.

Support for IT Infrastructure

On top of all this, Zimbra supports largescale clustering and a massive number of clustered storage/backup options available to it due to its reliance on Linux and MacOS X as the server operating system of choice, and integration with Active Directory - IT departments everywhere will be able to work Zimbra into their infrastructure.

With the 5.0 release, Zimbra Collaboration Suite meets these criteria and has become the first answer to Microsoft Exchange.

Yahoo Buyout Attempts - The Empire Strikes Back

In September 2007, Zimbra’s parent company was purchased by Yahoo! and Microsoft began making hostile moves toward buying out  Yahoo! shortly thereafter. One has to wonder what Microsoft would have done to Yahoo!’s Zimbra division if this had taken place - it’s unlikely Zimbra would have survived (Microsoft is famous for using phrases like “knife the baby” in its business deals). Had Yahoo! not rejected these attempts, there may not have been any alternative at all.

Fortunately, Yahoo! has so far rejected all attempts at being bought by Microsoft. Let’s hope this continues, because I find it doubtful that the US DoJ would notice the destruction of a potential Exchange competitor.

That is until…

Stay tuned for part 2, which will cover the first of these: Kerio MailServer 6.5.

And More

This is a simple, condensed list of the absolute basics needed when evaluating a replacement for Exchange. Many organizations will have other specific criteria and as such will need to do their homework when researching viable options.

Alternatives Are Appearing - A New Hope

As mentioned and as is the purpose of this series, there are now replacements for Exchange Server - 2 of them, and both of these have appeared on the scene within the last 6 months. Though both have existed for longer, their latest versions now sport a featureset rich enough for them to have the “right stuff”, and I consider both to be drop-in replacements based on the above criteria in a large number of cases.

Stay tuned for part 2, which will cover the first of these: Zimbra Collaboration Suite.

Here’s a good tip for you iPhone 3G users: 3G network coverage in many parts of North America is quite poor, even though coverage maps may indicate otherwise. While 3G is the big hype, especially since the release of Apple’s 3G handset came out, its deployment in the New World (and even some parts of Europe) isn’t sufficient to support largescale use of network intensive devices like the iPhone.

So: If you’re finding really poor call quality, dropped calls and generally poor data performance on your iPhone 3G, go into Settings > General > Network and turn off 3G Networking. You may be surprised to see your bars jump up and your call quality increase.

3G may be a big deal someday in parts of the world other than Japan and California. But not today.

This is my first post from the iPhone. It’s been a long time in coming, and there have been several hangups.

The 2.0 iPhone firmware presented me with the App Store, and the WordPress iPhone app appeared shortly afterward. Thing is, the app crashes repeatedly when I enter my login info. Once I’ve figured out why, I’ll update this post.

Meantime, I’ve upgraded to WordPress 2.6 and am using the WPhone plugin. Working very nicely so far - it lacks the image uploading feature I wanted in the native app, but it’ll do for now.

Much to-do has been made over the past week regarding Apple’s Safari web browser using “secret” undocumented code to make it run faster than competing web browsers.

It’s important to note that this was simply an overreaction on the part of a Mozilla developer which became a shot heard around the world.

An important comment on this same blog elaborates on the fact that this is in fact not super-secret undocumented code, and that the forces of corporate evil are in fact not out to get us.

Many credit Microsoft’s Mac support for saving the platform in the late 90’s. This is very true, but while they did this it’s important to keep hold of the more objective view of their Mac support.

It’s whitewash.

Microsoft’s motivation to support Apple in its hour of need was clear. Antitrust proceedings forced Microsoft into a corner, and the destruction of Apple would have only proven Microsoft’s nature as a monopoly force that was eradicating its competition.

While Microsoft maintains a set of apps for the Mac which appear reasonable and complete, these are designed only to exhibit lack of support for crucial items.

1. Microsoft’s current Office product for Mac does not open or save Office 2007 formatted documents, and will not until 2008, over a year after the release of the Windows version. This makes the Mac more difficult to use in workplaces and even homes where individual users are beginning to adopt Office 2007. Even Apple itself has introduced Office 2007 document support into its own applications, and indeed integrated it with its latest version of the operating system. Are we to believe Microsoft’s engineering team are incapable of doing this? Clearly one must assume this is by design.
2. Microsoft’s Entourage mail client, part of Office for Mac, lacks crucial Exchange support such as MAPI and Global Address List, which makes it nearly useless in the corporate environment. Further, its device synchronization support with devices such as PalmOS or Windows Mobile is non-existent. One has to use third-party applications to accomplish this.
3. Microsoft’s Entourage client also purports to synchronize its calendar and contacts with the Macintosh ‘iCal’ and ‘Address Book’ applications - however in so doing it removes all categories and other important data from the synced items, throwing a well organized calendar or address book into total disarray. Implementing this is not difficult, and has also been developed by third parties - but having to add third party apps makes no case for corporate or home use.
4. Microsoft’s upcoming Office 2008:mac will do away with support for VBscript and Excel macros, which are crucial for use in the business environment. Many businesses now using Office for Mac in these situations will be forced to either not upgrade and face document format incompatibilities, or switch to the Windows version of Office.
5. Microsoft Messenger, the Mac MSN client, lacks audio and video chat support. These items are so trivial to implement that 2 developers could do so in a day of work. Even Yahoo! messenger supports audio/visual chat, and one can’t say Yahoo’s Mac engineering team is as large as Microsoft’s. This is by design. Many users employ video chat to speak with friends and acquaintances, and the lack of this support in MSN on the Mac makes it highly undesirable.

Microsoft has claimed that their next version of MSN Messenger for Mac will support video, but has included the crucial detail that this will be for ‘corporate users‘. I take this to mean that home users, the principal users of audio/visual chat on MSN, will still be left without. Given Microsoft Office:mac’s nonviability in the corporate environment for other reasons, this would be a highly cynical act.

This is only a short list. Microsoft kneecaps their Macintosh product line in order to keep people interested in Windows, and I’m annoyed with the tech press for ignoring this issue.

Back in the late 80’s and through to the mid-90’s, document format compatibility was key to getting computers to work together and getting them adopted for use, and it was very difficult. This is 2007. In a world where computers of all kinds speak to each other freely using international standards, why are we still dealing with this?

UPDATE

If you’ve arrived here looking to use iSCSI with Time Machine, I’ve switched to another more robust method. I’ve run into some of the same problems as commenters below, and I’ve become convinced the iSCSI angle is too risky for now.

Open a terminal and run:

defaults write com.apple.systempreferences TMShowUnsupportedNetworkVolumes 1

Then you can use a Samba or AppleShare (even Netatalk) server share as a time machine backup location. This works perfectly, as Time Machine creates a disk image with an HFS+ filesystem on which to perform backups, and mounts that.

I’ll leave the original post here for those interested.

Got Leopard? Too cheap/lazy to go get a USB drive for backups? Like taking risks? Etc.

One of the things I was looking forward to in MacOS X 10.5 was Time Machine. To my knowledge, Time Machine was to support two ways of backing up - to a locally connected hard drive, or to a hard drive connected to an AirPort base station. I figured I’d mix it up a little and try centralizing my backup storage to my Linux servers. To do this, I employed iSCSI to connect storage space on the Linux server to the Mac. iSCSI accomplishes this in such a way that MacOS (and any other iSCSI client) sees the disk as a locally connected SCSI disk, and therefore it passes the criteria for Time Machine. You even format it as HFS+ in the normal way when a new disk is connected.

If you have a fileserver capable of delivering iSCSI LUNs, (and if you don’t know what iSCSI LUNs are, go get a USB drive), you can use the globalSAN iSCSI Initiator for OS X to do this with Leopard. They don’t specifically mention compatibility with Leopard, but this has been working for me for several hours now as of the time of this writing.

Caveat emptor: I did hard lock the iMac during a first attempt at an initial backup, but it’s hard to say whether it was iSCSI or one of the myriad other things I was doing at the time. Factor in Leopard being brand spankin’ new, and I can’t say for sure what caused it. If you have a sense of adventure, try this out.

One of my Macs is a 2001 vintage G4 733 with a dual 1.8GHz G4 upgrade. This should fit well within Leopard’s minimum system requirements, but the CPU upgrade I’m using presented a complication.

Without a kernel extension from Gigadesigns called ‘Giga-Meter’, MacOS recognizes the upgraded CPU’s as ‘PowerPC 60? 467MHz’ and therefore won’t update due to the new minimum requirement of 867MHz. This extension can’t be loaded from a DVD since you’re booted from the Leopard installation CD at the time you get denied.

I resolved this by doing the following (this is for fairly advanced users):

1. Click OK to the dialog informing you your Mac isn’t fast enough, NOT RESTART
2. You’ll be presented with an idle desktop, and will be able to choose ‘Terminal’ from the Utilities menu.
3. Run ‘kextload /Volumes/Macintosh\ HD/System/Library/Extensions/Giga-Meter.kext‘. This extension loads into the leopard kernel without difficulty.
4. Quit Terminal, choose ‘System Profiler’ from the Utilities menu. It should now report your CPU at the proper speed.
5. Relaunch the MacOS X Installer by choosing Terminal again from the Utilities menu and running the following:/System/Installation/CDIS/Mac\ OS\ X\ Installer.app/Contents/MacOS/Mac\ OS\ X\ Installer /System/Installation/Packages/OSInstall.mpkg

(All on one line)

Leopard install will proceed normally.

Leopard also requires a CoreImage capable graphics card for a lot of its new stuff, so if people don’t have a Radeon 9600 Mac Edition in their upgraded G4’s, now’s the time to get one. This graphics card upgrade works fine under Leopard as well.

Evidently the intention has been to allow third party apps on the iPhone all along. This is good news - while the current selection of web apps are higher in quality and usefulness than the unofficial native apps, official support will result in some vendors stepping up and creating some good stuff (and as mentioned, a lot of other vendors stepping up and writing crap - caveat emptor).

Quoted from apple.com/hotnews/:

Third Party Applications on the iPhone

Let me just say it: We want native third party applications on the iPhone, and we plan to have an SDK in developers’ hands in February. We are excited about creating a vibrant third party developer community around the iPhone and enabling hundreds of new applications for our users. With our revolutionary multi-touch interface, powerful hardware and advanced software architecture, we believe we have created the best mobile platform ever for developers.

It will take until February to release an SDK because we’re trying to do two diametrically opposed things at once—provide an advanced and open platform to developers while at the same time protect iPhone users from viruses, malware, privacy attacks, etc. This is no easy task. Some claim that viruses and malware are not a problem on mobile phones—this is simply not true. There have been serious viruses on other mobile phones already, including some that silently spread from phone to phone over the cell network. As our phones become more powerful, these malicious programs will become more dangerous. And since the iPhone is the most advanced phone ever, it will be a highly visible target.

Some companies are already taking action. Nokia, for example, is not allowing any applications to be loaded onto some of their newest phones unless they have a digital signature that can be traced back to a known developer. While this makes such a phone less than “totally open,” we believe it is a step in the right direction. We are working on an advanced system which will offer developers broad access to natively program the iPhone’s amazing software platform while at the same time protecting users from malicious programs.

We think a few months of patience now will be rewarded by many years of great third party applications running on safe and reliable iPhones.

Steve

P.S.: The SDK will also allow developers to create applications for iPod touch. [Oct 17, 2007]

(This’ll be the last iPhone related post, I promise).

There’s been a lot of overreaction in the press regarding the latest iPhone firmware. Thankfully it’s beginning to die down as reporters are realizing they’re standing up for hackers and unlockers, and people who generally aren’t interested in supporting the corporate interests of their sponsors, but I digress.

Lots of articles were published slamming Apple for “bricking” iPhones that have been modified. The reality of the situation is quite different. Apple issued a press release announcing their concerns about third party SIM unlocks; they created unmanageable incompatibilities and issues with the firmware upgrade process. Nowhere did they say they were going to intentionally disable iPhones.

When you’re about to update your firmware, you receive a confirmation dialog with the following warning:

So if you managed to “brick” your iPhone with the latest firmware update, you should consider three things.

1. You were warned about the modifications you made creating compatibility issues Apple can’t support
2. If you know how to modify your iPhone such that you can unlock it, you should know enough to wait on updates until there are known methods of unlocking _them_ or known methods of safely updating.
3. Your iPhone is not bricked. If you knew how to unlock the iPhone you should know how to restore it to working condition. If you don’t, you shouldn’t have tried unlocking it. Welcome to being “on your own”.

The update also removes all your custom apps. I’ve learned a couple of things about the custom apps, and have come to some conclusions about custom apps for mobile devices in general.

• The RSS reader is useless. No documentation in the world will explain how to get it to import an RSS feed. The fact that it can’t get them out of Safari is bad enough.
• Both the IM and IRC clients succeed only in disconnecting all the time or crashing the iPhone outright.
• I haven’t found a practical use for the file manager, as it doesn’t do anything meaningful except let you look at the filesystem contents. You can’t use it to copy files onto or off of the device.
• The eBook reader only takes plaintext.
• The VNC client is useless, not sending mouse events properly or at all.
• The UNIX and OpenSSH stuff is pretty cool and useful for exploring but that’s about it.

Basically, all the custom apps are crap so far. This shouldn’t be a surprise, as there’s no official support or documentation. But it does raise another interesting point.

Interestingly, almost all the third party apps for other mobile operating systems are crap too, even with documentation and developer support. On Windows Mobile for example, you can’t get away with installing more than maybe 3 apps before the system is so starved for resources and destabilized that you need to restore the device. I bought “Agile Messenger”, an IM client for Windows Mobile for the hefty sum of about $65 as it was the best IM client I could find, and it caused me to have to reboot Windows daily, would interrupt calls by crashing the handset, you name it. Money well wasted.

As I mentioned in my last post, Palm has nothing innovative to offer. It and all its custom apps are out of the running (though some of Palm’s custom apps were nice, considering the devices have the capabilities of a computer from the late 80’s).

Blackberry has a similarly small selection of decent software. Everyone will want to reply to this with their pet app, but remember, run your app in combination with everyone else’s pet app and your blackberry will become a brick too.

Basically, only a select few of the thousands of custom applications for every mobile device are worth using. I usually settled on 2 or 3 apps that didn’t crash my device and whose clumsiness I could put up with when I owned Palms, Blackberry and Windows Mobile devices.

Not to mention, the majority of blackberry users (a large demographic of non-geek users) don’t even care about custom apps. The functionality built into the device is just fine with them (and the iPhone possesses almost all of this).

Apple has been very insistent on web apps being the preferred direction for application development on the iPhone. So far I’ve replaced 2/3 of the custom applications with web based ones and have actually gained extra functionality as a result.

So my opinion on custom apps on the iPhone is changing. It’s meant to be used with unlimited data plans, so it’s designed to be practical for use with web apps.

Man Up

This is a shout out to all you geeks and tech press editors whining that Apple bricked your iPhone. Man up, you were warned about the incompatibilities you introduced. Don’t blame Apple for a situation you created.

What, the iPhone was designed to be used with AT&T, and now that you tried to change that fundamental aspect it won’t work anywhere? Shucks. Better get to fixing that.

And to everyone (including myself a few days ago) who think the ability to install custom software is the key to the iPhone’s future success, I no longer agree. Check out some of the high-quality web apps out there before jumping to conclusions.