Slashdot Mirror
Open Source Microsoft Exchange Replacements?
Carl Farrington asks: "Do you think you could try to raise public awareness of the importance for an open source replacement for Microsoft Exchange (Outlook/MAPI compatible for shared/public folders). Current offerings are SuSE Linux Groupware Server, Communigate Pro (Stalker Software), Samsung Contact (ex. HP OpenMail) all of which are not open source / free. Kroupware is in development, but there will be no Outlook Connector for it. otlkcon is in slow development as a possible connector for Kroupware. There is also OSER (Open Source Exchange Replacement) which again looks like it needs more help. Is there any chance of getting some people to back this stuff? It's so important and is probably the major problem facing Linux as viable replacements for Win2000 servers." While this seems to be a question that
keeps
popping up in one form or another, it's always worthwhile to come back and point out alternatives, in development, that might need your help to get off the ground and running. So, if you're looking for an alternative to Exchange, would you be willing to contribute some time to one of the projects listed above? If you've been using Unix as an Exchange replacement, what did you do and how well has it been working?
You're right, Communigate isn't open source. It is, however one of the greatet things since sliced bread in terms of functionality/ease of use/stability. It runs on open source, isn't from Microsoft, works wonderfully, and isn't all that expensive.
Good enough for me.
Mod point free since 2001
Many people have become familiar with using services such as hotmail or yahoo as their main form of email.
You could take this oppertunity to use something like http://www.phpgroupware.org/ which will replicate all the mail/collabaration/task/meeting scheduling functions of Outlook.
Also its free and open sores software, take a look at some of these screenshots or try out the live demo and see for your self how great it is.
I'd like to mention that I have no affiliation except having a linux server hidden somewhere at work running this and allowing many people who get stupid outlook viruses an account on it too see if they like it, so far I'm getting a great response.
There is no god
We started using the Open Exchange groupware where I work, and I must say, it is a very capable and professional package. Beyond the usual email, adressbook, and calendar functionality, I have used it to track jobs and projects, maintain document revisions, and it has all worked very well. I have even become a fan of the web interface, because it really is convenient to be able to access all of the above from any given computer.
Definately a contender to keep in mind...
It's hard to tell the cool to chill, my favorite hotel room has a view to an ill.
- SMTP - Outlook Express and Netscape/Mozilla and most other email clients can send mail using SMTP.
- POP3 - Older standard for email retrieval, which Outlook Express and Netscape/Mozilla can use.
- IMAP - Newer standard for email retrieval, which can manage group and folder types of functions. Many email clients use it; not sure if Outlook does.
- NNTP - Usenet standard for groups - works Just Fine, and there are lots of clients, including Netscape / Mozilla's mail clients and newsreaders.
- Web Conference Boards - There are *so* many of these out there, and they're often a much better choice than shared folders or similar groupware. Depending on how many messages you're trying to handle, your users will often find simple dumb systems friendlier than powerful complex systems.
- HTTP and/or FTP - If you're trying to publish files to people, these are much better standards than email. Some of the web conference board things have convenient uploading interfaces, or otherwise you'll need to do permissions of some sort.
- Shared File Systems - SAMBA, etc. - If you're enough of a Microsoft shop to be running Exchange, surely you're also running a file server network of some sort. Set aside a directory for people to drag files into, and tell them to mount it as their "G Drive" or whatever.
- Calendar Systems - This is the other hard one to replace, but I've seen a number of calendar systems out there, typically web-based, and you can email people URLs to click on if you want to integrate with email. The one thing MS seems to have done well is encourage Palm and Nokia and other PDA makers to develop tools for syncing their PDAs with Outlook Calendar. I think some of the Linux-based systems have probably done that.
MS Outlook lumps a whole bunch of functions into one program, so if your people get used to using any two of them they tend to be hooked for life. It's not a very good choice, and if you're going to do something like that, it's much cleaner to use a browser as the one big tool you're hooked on.Bill Stewart
New Fast-Compression-only CPR http://preview.tinyurl.com/dy575ks
Look - here is a real one for ya all. Dual PIII-1000 system, 1 gig of RAM, mirrored pair of 72 Gig 10K SCSI drives in a 2U SuperMicro chassis connected to a 100 mb/s burstable circuit at level 3. That's what my company uses to host our exchange users; our own use plus those we host for.
Setup? Lesse, a basic load of W2K, hit windows update and did'em all. Single vendor provided driver was for the SCSI 0-channel RAID card. Time? About an hour.
Loading Exchange 2000? First, run dcpromo to turn this box into an Active directory domain controller. This process also automatically installed and configured the DNS. Then stuck Exchange 2000 CD in drive, followed the next next next, finish clicks and sat back. About 30 minutes later Exchange was running.
Configuration? Added domain name, added a user and left the checkbox for "Create Exchange mailbox" checked. Bingo, new user with automatically assigned e-mail address based on policy we wanted to use.
Full web access. Done. Full shared calendars and public folders. Done. Delegate access with full ACLs. Done. Offline support. Done. POP3 support. Done. IMAP support? It's in there. NNTP? All set. Instant Messenging? It's in there. IRC (chat) - It's in there. x.400 and SMTP, of course. No open relays by default. S/MIME? Digital certificates? Yep and yep. The list goes on, I won't bother with any more.
Total time to get up and running, a single afternoon.
OK, so it's up - now what? Well... nothing. Every night we do a backup, using built-in APIs that allow backing up without taking the information store offline. Virus scanning runs automatically and updates itself daily automatically. Antispam is fully automatic using statistical and phrase filtering. Nothing to do but look at the cute charts of spam blocked by user. Every so often there might be an applicable windows update to do - ok, so, hit windows update, download and (the ONLY part that sucks, I'll admit it) reboot.
That's it. Our uptime is 100.00% The only reboots are planned. Period. The hardware is not esoteric. The loads are easily managable on a simple dual PIII.
Client performance is flawless, and very fast. Database corruption? What's that? Never seen it. During preproduction testing we regularly would pull both power cables simultaneously while the machine was doing an full-text indexing crawl across our 60 gigabyte stores. Upon restoring power the entire server came up without a single hitch and without any delay whatsoever; the failed crawl was detected, and restarted. Transaction logs were played back and 0% loss sustained. We did this at least 30 times without ever suffering a single corruption or anything more than a few red Xs (something needs fixing) in the event log (followed by a few yellows (we're fixing it) then pretty blue I's to tell us "it's fixed.")
Anyone that thinks Exchange is just a POP/SMTP/IMAP server hasn't a clue. Anyone who would like to tell you that Exchange crashes is either lying or can't run a server. Period. With over 75 Exchange boxes in production and never a single chance to test our off-line disaster recovery plan -- we could not be more pleased.