Comcast Goes to Zimbra
tenchiken writes "Zimbra, an Open Source enterprise messaging app, just scored a major win. Comcast will be moving mail services to Zimbra for all of their customers. Zimbra has been picking up steam for a while now, and appears to really be challenging Microsoft in a area that Exchange has been dominated in. Add in support for Samba Domain Controllers and Linux Authentication, Offline Access and Evolution Support and we might finally have our long desired Open Source Exchange killer."
They have been know to make horrible technology decisions in the past.
I found it pretty simple. They have a pre-configured VMWare image you can download and play with, I found it incredibly handy and quick to play with. Seems pretty promising, but I don't know if I like the "offline client" it is a resource hog.. I would love to see them add a plugin for the thunderbird-sunbird calendar tools.
What are we going to do tonight Brain?
So, Comcast is moving customers from something to something else, and that means that one of those somethings compares with Microsoft Exchange. I'd have to presume that Exchange wasn't what Comcast is moving from. ISPs want mail servers. They expect that mail will be relatively independent between users. They presume that administrators want to have nothing to do with emails inside the email boxes. They presume that if a user calls up and says "I deleted an email and I want you to get it back" that a polite "go away" is a sufficient answer.
None of that has anything to do with what Exchange is aimed for. Exchange is not used for any major ISP that I'm aware of (not even Microsoft's public email services), nor should it be. Exchange is built to integrate with Domain Services. It's made so that you can have resource scheduling integrated with calendars and busy notification. It's made so that a secretary can log into her boss's account and check all his emails and send emails as herself or under his name as if he sent them himself. It's made so that when the idiot sends out the video of the latest commercial he thinks is cute that there is only one copy of the video on the server, and the emails point to it, rather than replicating it 1000 times.
Exchange is not a mail server. It is a messaging server (with integrated calendar functionality). This submission is written by someone that is either too stupid to know the difference, or who knows that the comparison is stupid and is just trying to drum up support for a product through misrepresentation. Either way, though the product being touted may be interesting, the submission is crap.
Learn to love Alaska
If you're setting this up for a small outfit (like, I host email for my friends/family), then the minimum requirements may be a bit high (cached link here.) On an Intel 32-bit machine (recommended at least 2GHz):
minimum memory: 2G
recommended memory: 4G.
That's for a box dedicated to being a mail server and webmail/calendaring client (forget about sharing it with other hosting needs, like a Webserver).
For a company (small or whatever), having a dedicated box for this sort of thing is reasonable and expected... and, please forgive the pun, the suite looks sweet. 8)
But, as an individual/uber-small hoster, those requirements put it outside the range of "host this on an old box."
That's not to say that Zimbra was targeted at me to start (so, please don't take it as a complaint). I just wanted to break the news (hopefully gently) to those hobbyists that were getting excited about hosting it. 8/
Diplomacy is the art of saying, "Nice doggie!" until you can find a rock.
Maybe you're barking up the wrong tree completely. Do you actually think Comcast is using Exchange to supply mail service to all their customers? I'm one of those customers and I know they instructed me to use POP/IMAP for the protocols. I can't even imagine trying to scale an Exchange server up to that number of users. Maybe it is possible, but it seems highly unlikely.
I strongly suspect Comcast is migrating from Sendmail or some other common e-mail server that is built to scale well. I don't know where the idea that they are moving from Exchange come from though.
That sounds like quite the pain in the ass. Just the same, it should be in the repository and the other pieces can be dependencies. Install Ubuntu server, enable repositories, apt-get update, apt-get install zimbra. At that point all the dependencies work themselves out and a basic functional zimbra with the most commonly needed configuration comes out of the box. After another 10 minutes or less of tweaking you have a zimbra server. AND you can run other services on it if you are putting it in an office with 10-20 users instead of 50,000!
They could go the easy route and have the package conflict with other MTA's (all that other stuff can just run on alternative ports). I know, I know, sounds like a great idea. Why don't I get right on that? *grumble grumble*