Slashdot Mirror
Can We Finally Ditch Exchange?
"With new releases on the way, like Mandrake 9.0 and the new Lycoris can we who try to use Free Software in business environments hope for any change? Do the commercial Linux distros have any plans to implement a free replacement for Exchange, including a Win32 client-side bridge? If not, why not? Do you feel it is too cost prohibitive to imitate Bynari in this case, or is it a decision more along the lines of 'we'd rather you used Evolution and Mandrake/Lycoris/Whatever, rather than OutLook and Win32'? If it's the latter I'd be severely disappointed, and I don't think I'm alone. Any discussion on this topic would be appreciated; but what I'd really love is a community push to get this done. Perhaps a running Web-A-Thon to raise the money to simply purchase the technology from Bynari? I personally think it would be a great move towards grabbing market share from some of the other distributions, some of which have the technology but choose to keep it closed, as well as from the Great Dragon. What do you think?"
Untill there is a standard calendar protocol, and that protocol is supported by exchange, you won't be able to get rid of it.
second society
1.) Companies are having difficulty implementing the calendar system that Exchange uses properly. 2.) Microsoft professional support, big business likes the idea of having someone to blame when things don't work. They sign contacts that make people have it fixed within a specific time period or they recieve massive compensation.
Translation: "Me and a bunch of people got drunk, thought we could code, submitted the idea and produced a fancy web page. It's now two years later and the project has no files to download and is STILL on Stage 1, Planning."
Finally, math books without any of that base 6 crap in them.
At the place I work at, we have both an exchange server and a POP3/IMAP server. We catch so much flak from our users over the exchange server than the POP3 server, Then again 90% of our users use OutLook even though we have a site license for Eudora,and offer Netscape and an IMAP web client. They get lost even though we have an excellent web-directory and one of the best calendar projects around. Everyone has a public folder that they can put stuff into to share with the rest of the network byt they still insist on using Exchange. Personally I can't find any feature that justifies all of the garbage we have to put up with to get it running. Outlook sucks!(there goes my karma) Outlook crashes more often then IE, Outlook is targeted my more virii then ever. If these people would change their mail client, they wouldn't have this problem. The exchange server is jacked up as well. We have to call and have it re-set every three days and I'd bet that the network "gurus"(/sarcasm) don't know how to admin it either!!!... argh!
Alot of companies/admins are waiting for an Exchange replacement. I for one have considered dropping exchange for a flat out mail server that runs in a *nix environment but it always comes back to the scheduling of exchange. With all of the people out there writing code, it still amazes me that nothing has surfaced. Why not take time off f the useless mp3 player/id3 reader/all of the other crap and contribute to a worthwhile project?
My sig of choice is Marlboro
First, most non-tech corporate types have heard of Exchange. Next, they like to have someone to sue. Even those projects with companies behind them don't have much to go after. Even though Microsoft has a EULA that supposedly frees them from any liability if the software screws up, it makes the corporate types feel better. Also, they can hire any MCSE off the streets to run the Exchange server. There aren't many standard certs that they can rely on when they need to hire your replacement after you've bundled together all this unfamiliar software on their servers. When you consider the hiring difficulties, lack of certifications, and lack of accountability of the authors of the software, the open source projects may, in fact, cost a good bit more than the $10,000 worth of Microsoft software. The entry costs of this software look enormous to individuals, but to corporations, it often doesn't appear to be much money. Corporations care much less about software politics than most of us do. The open source solution has the benefit of getting out of proprietary formats, but I don't think that's very high up on the list of priorities of the people making the decisions.
This is not trying to be a troll, but it seems there is always one more "clincher" in the movement away from MS products. IE / Office / Outlook / Photoshop you name it, but now it is Exchange. OSS always makes a replacement, but it is only 98% there in terms of functionality in most cases. As soon as we get Exchange out of the way, there will still be something else left to take its place to prevent adoption.
Buying a Dell computer is equivalent to dropping the soap in a prison shower.
Formerly HP's Openmail is another Exchange replacement, but exactly like Bynari's product it still requires some licensing.
I've been surprised that there hasn't been more effort on the Linux side of things to create a replacement. I would have thought that Redhat would have come up with something. Since as the poster notes, Exchange functionality tends to be a big killer whenever you flirt with replacing in house systems. If you can't provide the integrated and shared calendaring it usually won't fly.
Check out Samsung Contact. It used to be HP OpenMail. HP discontinued it, and Samsung bought it, because they were using it heavily internally. I think it does everything that Exchange does. There are a few nits with Outlook that make it look a little different than an Exchange server, but even those seem to be getting worked out. They're also fully standards-based.
Software sucks. Open Source sucks less.
At work, we've been trying to switch over from using exchange but a lot of people have implemented some very neat features, like for instance. If I have an appointment to do a stress test on a patient, the nurses send an email so that it is loaded onto my palm pilot when i sync and a letter is automatically printed out letting the patient know when the test is scheduled.
The IT guys think they may have found an exchange server replacemetn with SUSE but for now exhcnage is very useful and would be very hard to replace.
Thanks for reading
Sigs are dangerous coy things
There has been plenty of call for an open source groupware application like Exchange and as yet there are still none. My appologies to the folks at PHP-Groupware but, even though this is often cited as a solution, it simply isn't an adequate solution especially for a medium or large enterprise.
Frankly, I had always thought that the Sendmail folks would be the one to deliver. They have certainly nailed down the mail side and I feel that they could do a great job integrating calendaring and other groupware features, most importantly a programming interface to make it an extensible solution like Exchange or Notes. Unfortunately, as of yet, they have not indicated that they are pursuing this.
OSS is still out in the cold when it comes to an OSS Groupware application that scales.
The problem with evolutions is that is doesn't run on windows, so it is fairly usless to mixed shops. Also, it only supports exchange AFAIK when it comes to calendar/scheduling. In theory it supports LDAP for the address book, but the gloss factor in the manual on that point is very high. (see for yourself: here)
I know that the small software company I work for would love to have Evolution on every desktop (windows and linux) using LDAP for a shared address book and calendar, but it just can't happen today. Oh well, here is hoping that the Kompany can get Aethera right sometime this decade...
apt-get install redhat please god - Me (take it easy, I love Debian)
The whole concept of Exchange, in my opinion, is flawed. Each Exchange server recreates a mini-internet within a lan, that connects to other mini-internets within other lans, tied together by wans (or mans--as the case may be) and also tied together by the real internet [a nebulous definition goes here].
Here, we have one Exchange server for 150 people. But then there are 9 locations, from San Francisco to san Diego. They all hit the same server through the wan.
Remote users (15+) also use outlook web access (i't really Exchange web access if you think about it) to access their mail. We have to allow that traffic through the firewall.
And every single one of our people have one or more other email addresses (AOL, Earthlink, RR, whatever).
I would say: have better addressing handling.
Email was first created by geeks for geeks (at univs. and gov.) and served its purpose well. When the move was made to the company, the whole transition was just done wrong.
I say the Exchange servers should be totally eliminiated in favor of a non-lan/wan centric solution (watch your step, marketing words all around), namely a true internet application, shared, replicable, and reliable.
As far as calendaring is concerned, we don't use it much. Our corporate values promote face-time and intelligent conversation more than lines on a spreadsheet, so meetings are more dynamic, more fluid, and less apt tp be "scheduled". Usually it's a phone call.
Anyway, I digress.
But this may be the reason no open-sourcer wants to tackle that issue. It may subconsciously feel flawed to recreate the Exchange architecture.
"Piter, too, is dead."
- An OSS backend that replaces Exchange for calendaring at least. We can use IMAP and LDAP and such for the other functionality because at least there exist standard protocols, but there is no competetive backend for calendaring applications. It would be really nice to have an OSS all-in-one that does IMAP/LDAP/calendaring, but first things first.
- An OSS front-end like Evolution, but one that works on Windows as well as Unixes.
At our organization (a small university), we are desperately looking for a comprehensive calendaring solution -- one that supports teams, conflict resolutions, notifications, palm synching, and can be used either at home or at the office. I am the OSS advocate in our IT department, but I just can't find a suitable OSS solution. In fact, the only solution I can think of that even remotely fits the bill is Outlook and Exchange.The unfortunate part is that we're using Netscape 4.x here, mainly because of its mail client. (We're using IMAP and LDAP on our backend and NS 4.x Messenger is still pretty good, even though the browser sucks.) Netscape 7.x / Mozilla 1.x is nearly there, but not quite. If there was a calendar solution that worked with Mozilla/NS7 that had those features and had a OSS server, it would be like a dream come true. As it stands, I may have to roll out a small deployment of Outlook and Exchange just to solve this problem (which has come down from the president BTW, so it can't just be ignored until a suitable OSS solution comes along). Now suddenly we're mix-mashing between NS 4.x over IMAP with Outlook and Exchange. You can see what is going to happen with that nice IMAP/LDAP solution in a year.
I think what we really need is a standard protocol, de facto or otherwise, for network calendaring. There is iCal, but from what little I know about it, it's just not comprehensive enough. (Does it deal with network transport?)
Jason.
If we truely want to provide an alterative to Exchange as someone who works in an entirely exchange based environment, here is my analysis of what my PHB's would have to see.
Server Side:
1. The replacement must support Outlook as a client, people actually like Outlook as an integrated client.
2. The Replacement must work with the Sendto functions of Microsoft Office
3. The Replacement must be able to scale to 10's of thousands of users, in geographically diverse locations.
4. Must Support Multipule languages
5. Must be easily scannable for Virus protection, and must be able to deny delivery of messages that fit certain criteria
6. Easy rules based scripting of mail events stored on the server as part of the user's mail box.
7. Must support enterprise calendaring/scheduling.
8. Must inter-operate with Exchange during migration
9. Must support server and OS of choice at the company(You know what that means)
10. Must offer web mail capabilities equal too or better than OWA(this includes the ability to secure the web mail client via SecureID)
11. Must support massive data stores, on the order of 500GB-1TB(yes exchange can do this)
12. Must Integrate with our directory services, like exchange 2000 integrates with AD.
13 In short it has to do all the things that exchange can do, and more, and better.
Client Side:
1. Must have a client which supports all the functions of the server side. In short its gotta work like Outlook.
2. Must Support OS, and hardware of choice.
3. Easy Rules based scripting interface to server and client side rules(Think Outlook rules wizard)
4. Must be dead simple for users to use, users don't learn they want everything to work just like it always has, even if you give them a new application to do it. When we moved from Banyan Beyond Mail to Outlook when we went from a banyan network to an NT one it was a nightmare for all of the administrative assistants as their workflow was massively changed.
So there you have it....rebuild exchange as an OSS roject and get back to us...this is not meant as Troll, this is a real world example of how a corporation is going to look at such a thing.
Power Corrupts,Absolute Power Corrupts Absolutely, leaving one person(group)in charge is absolutely corrupt.
I was approached by Bruce Perens at LWE and he stated that Debian needed better support for Open Office. I looked at him and told him as soon as one of us had a reason to care we would.
This is the fundamental problem with Open Source in business land -- you need a coder who has the time to code and actually cares about making it work. I see lots of sysadmin types complain about Exchange but no one seems to hate it enough to sit down and work on something better. Most of the businesses approaching Mandrake, RH, etc are looking to dump the Microsoft solutions entirely so Exchange is not a big deal there. Or they are only looking for server -> server solutions and not desktops.
Last but not least you have the problem that Exchange is 100% proprietary. Look at all of the "fun" Samba has had trying to get smb interoperability right. I also bet Microsoft would be VERY apt to sue a company that did this into the ground. Might as well paint a target on your head.
As with every other itch you just need to find someone to scratch it. You mentioned "clients", why not funnel some of that contracting cash to coders willing to work on the project.
What about RFC 2447? The iCalendar protocol looks to have been developed jointly by Netscape, MS and Lotus. Exchange may support this, and even if it doesn't, this would be a good place to start.
As for the client-side, I think that I fully-featured web mail system can easily replace Outlook on the corporate desktop. They may all have Office, but they've got browsers too!
Comment removed based on user account deletion
OEone and Mozilla are working on an Open Source calendar server. Support it!
Wouldn't that make a great story?
Corporate Board Meeting
_______________________
Mean Boss: What the hell is wrong with our email system? Why do we keep getting virii and trojans on our network filesystems?
Burned out IT worker: Because we were told to buy software that was known to have many exploits and a number of design flaws, against our better judgement.
Mean Boss: Whoever told you to do that should be fired, I wanna know their names!
Burned out IT worker: Sir, it was you...
Mean Bosses Meaner Boss: Well Bob, hope you've polished up that resume'.
__________________________
AP news story: Someone fired for buying Microsoft!
Casca
I know that mentioning Lotus Notes violates the Code of Slashdot Posting, but take a look at Notes sometime. The people who designed that system spent a long time thinking very hard about how to build a mobile, distributed, secure groupware system (note: you do not need to agree with the solution they built to acknowledge that they thought very deeply about the problem). Then - they spent a lot of time and money building what they had designed.
(Exchange is basically an imitation of the 45% of Notes' features that are most commonly used, without the thought, design, or security).
Who in the Free Software/Open Source world is going to spend that kind of time and effort? Particularly given that most Linuxians fall into the "don't like groupware" camp?
sPh
...because the problem isn't interesting enough.
Open source shows a strong prediliction for solving interesting problems well ahead of boring ones. For instance, we had useful, powerful distributed databases, cryptography, new languages and C compilers long before we had a functional word processor and spreadsheet combo. Quite simply, we have already solved mail distribution and address-book sharing on their own, and have relatively little interest in peeling apart a proprietary MS standard for same which is liable to change next week. This is also the reason why OpenOffice is great for everything except reading and writing Word documents.
This flows into my new theory about how Microsoft intends to go about attacking Linux: A deluge of boring, repetitious, pointless APIs and interfaces for problems that were long ago solved but now must be addressed using these new, uselessly variant interfaces simply because that's what everyone else has to do. (Think dotnet.) A hacker's familiarity with extant interfaces is his or her number-one resource, and is therefore that which he or she will part with least readily --- even at the expense of the compatibility or useability of the code they're writing.
Microsoft's strategy is reminiscent, in some ways, of an ancient Incan technique for pacifying politically difficult villages and towns. By forcibly migrating the entire settlement to some distant part of the empire, the usefulness of the skill-sets of these hunter-gatherers was greatly reduced, making them dependent on the (massively centralized) government for handouts, and therefore suddenly rather polite in their relations with the regime.
In the same way that a hunter-gatherer depends on his knowledge of the land, a geek depends on knowledge of the problem and solution spaces. Furthermore, most OSS projects are extremely long-term endeavours; think GCC, think Emacs, think the Linux kernel(*). OSS developers work by building things slowly and correctly with a minimal expenditure of precious manpower; Microsoft works by using more coders, more money, insane work hours and a blase attitude toward standards (even difficult, complicated, important standards) so that they may get to market early , recoup such expenditures, and get to work on the next total (and totally incompatible) revision of their product, which people will use simply because of the upgrade path that MS will kludge together with exactly the same bloodyminded application of superior capital.
Simply put, we need stability more than they do, because they have more time and money. We write things right the first time, whereas they have the luxury of making as many mistakes as they need to in order to grab market share. But more importantly, we need the projects of the past to have been written right the first time; we need a working libc, kernel, and so forth, otherwise OSS simply doesn't happen. Microsoft has no such prerequisites to its growth, as, in a pinch, *it can simply replace its foundations by fiat*. Their hunter-gatherers can, metaphorically speaking, simply create (with a certain expenditure of time and effort) the landscape best suited to their requirements. Thus they can march along beside us, setting the pace, forcing a speedup, replacing good APIs with new because every step into new territory costs them less than it costs us, dissociates us from our well-known and powerful (if somewhat lacking) APIs and encourages our work to depend on their own work, which will then be changed, etc, rendering ours much less useful.
Ultimately, the strategy is designed to encourage hackers to go take up billiards or chess or something with a potential of being useful to remember or think about or use five minutes hence. The ultimate goal of cycling APIs is to induce *indifference*, as we face a choice between working harder on minutia or walking away, hands in the air.
(*)Note that, of these projects, two are sufficiently low-level to be immune to all but the most radical shifts in design; this is again indicative of what OSS excels at.
- undoware.ca
I've implemented several Exchange servers in a few large organizations in my day and to replicate what it does would be not be easy.
I think this is part of the problem with any existing attempts or lack thereof to replicate it...Exchange very elegantly handles messaging, calendaring and basic groupware with elegance.
For instance Exchange uses databases with transactional capability to provide extreme scaleability and reliability on the back-end. It has backup APIs that support amazing throughput for on-line hot backups. The database reclaims pages and defragments itself essentially in real time. Exchange supports every protocol in the book...but most customers implement it with their proprieatary MAPI protocol because it actually works a lot better than things like POP3, & IMAP.
Single instance storage allows Sally from marketing to send out her corporate spam to all internal unsuspecting users and the message will only be stored once in the database, there are semaphore links that track who has read the message or deleted it from their mailbox, disk consumption and server I/O load is dramatically reduced, especially when the message is 5 megabytes across 15,000 users!
I could easily come with a design document for a system that would essentially clone Exchange, the problem is around actually programming the system.
You would need a robust database back-end with excellent management support for things like hot backup and real-time database page reclamation, powerful & scaleable MTAs, an arm's length list of supported protocols and APIs, a user friendly cross platform client...
The ability to get all the developpers to agree on how to solve all of the above would be the biggest challenge.
Nobody ever got fired for buying Microsoft.
I know of three people who did get fired for buying Microsoft.
A friend of mine is now providing consulting to the companies in question. Two are running Twig on Linux servers, the other has their old non-ms, non-unix server back up and working (again) while they slowly transition to Linux.
Despite all the "I'll sound wise and neutral if I make out to be 'admitting' free software's flaws and giving Microsoft its due" commentary one sees here on slashdot as either an effort at karma whoring, or an effort at pro-Microsoft propoganda and astroturfing, the fact remains that there are really very few shops that cannot do without Microsoft, and many that actually benefit from running other platforms.
What is very interesting is the number of non-technical people who are coming to realize that, and while they don't necessarilly embrace free software in general, or GNU/Linux in particular, they are beginning to recognize just what a financial, technical, and time drain Microsoft and their products have become to their enterprises, and they are looking for ways out.
Even to the point where, now, people are starting to get fired for blindly purchasing Microsoft, and treating MS propoganda as a substitute for technical research and savvy.
Its a rather refreshing change, actually.
The Future of Human Evolution: Autonomy
Eww, sourceforge! Actually, there's not even a webpage- waste of time until there's something I'm willing to put up. ;)
But there are about seventy-five pages of analysis of Domino and Notes in real-world settings, some design documents and a few prototypes of critical components (probably about 200-300h of work so far). I like doing things the right way, which takes time.
Things like Domino and Exchange can be pretty effective if used well, but frankley they're not very smart. My personal research interest is managing the complexity of business and research processes, and I've found that Domino and Exchange don't really help the problems much: they don't help manage the complexities, they simply space-shift them. There's a lot of really interesting and hard problems when you start trying to solve the failings of these two systems. :)
- They dont have STABLE standards support (IMAP, POP3, iCal, etc...)
;p
I use IMAP and POP3 through GWIA for 700+ users, off one box. It's been up 60 days, and that's because we moved offices two months ago.
- They still havent integrated GW's user/password database into Novell's famed eDirectory/NDS database.
Maybe not, but I manage them using the same utility. Nobody has anything better, really. And because of the way the post office works, you have to communicate with a specific server agent, not just any server in the tree, so intergrating passwords wouldn't really help any, unless you have no tape backups.
- Very little administrative control over the mailboxes.
What complete bullshit. In NWAdmin, I can control every option of the GroupWise client, I can set it remotely, and I can grey out the option so the user can't change it. What the can't you do? You want to add rules or specific proxy access, just go in to their box with the client, and do it.
- Poor backup solution (you MUST shutdown the email system to get a reliable backup). No, the GWTSA's dont cut it (based on my personal experiences, and statements from senior techs at Novell)...
Not based on my experience with Backup Exec 9.0. Even if you don't use the GWTSA's, you just make everyone access the post office over IP, instead of file access, and backup the directory. The files locked by the agent can be rebuilt from the files that will never be locked.
- Novell has POOR support for automated administration and report generation out of GroupWise - GWCheck just does not cut it...
Hmmmm... I've never cared about getting a report, really. Besides, GWCheck is for repairing the system, not reporting. But since I don't know what kind of reports you'd like, I'll leave this one alone.
Groupwise is *great*. No, I don't work for Novell. Yes, I do administer a 2000 user enterprise system that runs Groupwise 5.5. We don't even need a dedicated e-mail guy, even for all 2000 users. And it doesn't even take up a big chunk of my time. I have 15 domains, 22 post offices, two internet gateway agents, and WebAccess set up. No issues, anywhere.
*ever*
I think you're doing something wrong.
I work as sysadmin on an Air Force base. We have a commercial support contract with Sun that specifies they get replacement parts to us in 4 hours. The other day a hard drive died, and I had the amusement of writing in the support request, "I know where Sun's headquarters are; get me a new hard drive in 4 hours or I call in an airstrike."
(Then I thought some more about it and erased that sentence. Damn humorless paper-pushers. (So of course it took six hours for the drive to get to me.) Oh well.)
You cannot apply a technological solution to a sociological problem. (Edwards' Law)
I've been trying to do this for a couple of years. I wrote the Exchange Server Replacement HOWTO back in '99 when it looked like this might be possible very soon.
Essentially I talked about how to get IMAP/POP3/SMTP with a global Address Book and authentication and user accounts via LDAP. I've been watching this space with a lot of interest since then. The lack of updates to the HOWTO should give you some idea of what's changed, not much.
As far as calendaring goes, here's the skinny: CAP is the current IETF draft, and has been for some time, although when it will be finalized is anybody's guess. Why aren't there any shared calendaring servers? Cause there's no shared calendaring standard. You can get asynchronous calendaring in IMAP by having a decent IMAP client and using a Calendar folder, but that's hardly as feature rich as Outlook/Exchange. libical has kept up with the draft but has no server process. It's used in Evolution and the Mozilla Calendar client. So we have calendaring on the client side, but nothing on the server side. From what I've been able to discern, nobody wants to write a CAP based server till CAP is finalized, since it's gone through too many changes during the drafting process already.
The other problem is the outlook clients. The way Bynari and OpenMail (Contact) have gotten around the proprietary Exchange RPC call stuff, is to write a MAPI driver for Outlook that intercepts the client calls and sends them to the server in whatever proprietary method they might have. Integrating Outlook clients will either require a server side project on the level of Samba or a client side MAPI replacement that uses CAP, unless M$ has a change of heart and decides to support it.
In order to replace the functionality of Exchange you would need, a Calendar Server (none exists in the Open Source world), a searchable document share (WebDav on Apache can't index M$Office documents AFAIK), searchable email w/ public folders and mailing lists (Cyrus + majordomo or Sympa could feasibly work), a global address book (OpenLDAP).
Now,the real kicker, it has to all be integrated, single point of management and have a web interface for users to boot. There are a million and one PHP/Perl based web interfaces to one piece of this or another. However, trying to integrate all of this is impossible. Why?
For starters, everyone seems to want to do LAMP, as if these apps all live alone and users want to log into a seperate web interface for each function then cut and paste data between web pages and not be able to search everything as one data repository, if they can search at all.
LDAP has been available for years, and the guys at OpenLDAP have been there to solve a lot of these problems for years. Quit using an RDBMS for everything, for data that applications should share, use LDAP, stuff like authentication and application user information. LDAP has seemingly been ignored by a lot of open source programmers. Evolution's LDAP support has flat out been broken, everytime I've tried it. Mozilla's works but lacks some functionality. Granted LDAP takes about as much knowledge as learning an RDBMS to understand, but ther are currently about 3 decent LDAP management tools (lape, Directory Administrator and GQ). With LDAP you can essentially have a database schema that all apps can program to, cause it's standardized (inetOrgPerson, etc.)
Other apps seem to be developed without a thought to integrating with other apps. I tried to integrate Sympa, OpenCA, cyrus, sendmail and OpenLDAP with a custom web front end about a year ago. I paid the salaries of myself and 2 other developers for about 8 months, trying to do this. It was a failure, especially in the cases of the Perl pieces. The CPAN Perl libraries didn't do LDAPv3 extensions, isolating code in most of these projects to use a different front end was hopeless and providing an interface to manage the configuration files for the servers was a lot of work. We got about 80% done before I sold the company (and codebase). We had originally planned to GPL our work then sell support and customization, with a calendaring solution and MAPI driver for outlook in the 2.0 feature set.
Most of the frustration we had and was due to using other people's code that was not extensible or modularized. If I had to do it over again, I'd do it in Java on JBoss (esp considering the BEEP servlets JSR for CAP and the great LDAP support via JNDI).
I don't think that developer's of various open source projects need to have some overreaching design group (a la GNOME or KDE) to implement these projects with integration in mind. There are plenty of standards already out there. It just takes some good design and up front research (something I've done a lot of) and thinking about how other developers and users might want to use this stuff for their projects.
Now, I don't want to sound like I'm whining about my own failures, I should have made sure we had enough capital to do it all from scratch. I'm more concerned about our ability to compete with the Exchange servers and Lotus Notes of the world and have a stable, customizable platform that we own. Quit rewriting the same stuff over and over and build new stuff... innovate, be creative, push the industry forward.
There is a glimmer of hope, the Open Source Java community is doing fantastic stuff. I've never seen more modularization, code reuse, integration and faster development in any environment or community. JBoss really takes the lead, the feature list is amazing and I've used it in several corporate environments where it beat out commercial J2EE app servers. JBoss pulls from Ant, XDoclet, Jetty, Tomcat, JacORB, Axis, HyperSonic SQL and a bunch of other projects. Struts and the Java commons and taglib projects at Jakarta are another example of really cool work.
The point is, it all works together. End users don't care if you wrote it in Perl, PHP, Python, C or Java... Just that it makes their lives easier, if we want Open Source to get more places we have to make sure we can deliver on this. Considering most of us make a living programming, supporting or administering networked systems, which would you rather have, propietary crap or really good open source stuff? So next time your designing that project, or writing some more code think about how you can make integration easier. Documentation helps too... we shouldn't have to know fifteen languages and countless codebases to get stuff working together. Most of us specialize in a couple of things.
Well, that's been my experience and is currently my struggle, so hope you get something out of this... BTW, I'd loved to be proved wrong on any pessimism I may currently have.
Arrogance is Confidence which lacks integrity. -- me
Exchange has it's plusses and minuses. I like how easy it is to set up, I like how easy it is to maintain, and it's pretty easy to make the features it has useful.
However, there are two issues with it that bother the hell out of me: (Note: This is Exchange 5.5, not the latest one. Nobody where I work is interested in paying gobs more when there's free stuff out there.)
1.) The copy we have is limited to 25 licenses. This means that 25 connections are allowed at one time. More than that and Exchange punts you. "Sorry, you have to wait until a connection is open."
The IMAP protocol is particularly attractive, so it's used a lot. But it counts as 2 connections because it makes one for inbound and one for outbound. So you can have 12.5 simultaneous connections before Exchange says "Sorry, give me more money."
What makes it worse is that IMAP is rather persistent, as opposed to POP3 that just hops in and hops out. My company of 19 had to tighten control over who uses what and when over it. This alone is enough to make us move away from MS.
2.) You cannot uninstall Exchange 5.5. I boogered up the install once and had to reinstall WinNT because it wouldn't give me the option to remove Exchange and start over. Maybe a little more poking and prodding could have solved it without a rebuild, but I was in emergency 'We need it yesterday!!' mode and didn't have the keys to the company Tardis.
Exchange gets points for being very easy to use and run, but it is a huge moneypit. If I were running on less than 15 people, I'd be fine with it. However, for more than that I'm ready to learn how Linux works and build a server with that.
"Derp de derp."
I see many people here aren't real fond of Lotus, but what would happen if IBM really decided to shoot the whole works on Linux and release Lotus as open source on Linux/Unix platforms? Here are some points for and against it - I suppose only IBM really knows how they would balance out.
For:
1) Would be a huge boost to their Linux effort, and might convince a lot of companies to get a Linux solution from IBM.
2) As open source, people could finally start to address all the things they don't care for in Lotus. Perhaps a license could be arrived at which retained for IBM exclusive rights to distribute binaries for non-open platforms, and include on those platforms innovations submitted by the open developers. For open platforms such as Linux and BSD, full availability.
3) As a free and open solution, Lotus might begin to do some serious damage to that end of Microsoft's business, and at the same time focus more IT departments interest on IBM.
4) Support contracts could still be offered, and in large scale operations would probably still be bought. Even with an open Lotus, IBM is still the logical supporter for the programs.
Against:
1) IBM wouldn't get any direct license fee income from Lotus on Linux.
2) Legal issues with releasing the code could be considerable.
"I object to doing things that computers can do." -- Olin Shivers, lispers.org
This AskSlashdot is trying to demand code from the Open Source community. That is rude in my opinion. If he wants a copy of Exchange and Outlook, I expect him to put the effort into it. Learn to code and then start a project. Demanding that people who code on things for enjoyment start working on something else just because you need a free alternative to a costly product, that is arrogant as well as rude. From the sounds of it, he wouldn't even like to contribute to the project only use it.
Check out the Citadel project. This started as a BBS server, but it's gradually being built up into a groupware system. We've spent the last couple of years building up a solid messaging architecture and a fast, efficient server architecture. Right now it does IMAP, POP3, and SMTP natively (no tedious mucking about with Sendmail or Cyrus), and it's got a web interface, too. It has a single-instance, transactional data store. It has a pluggable, extensible architecture. And one of our design tenets is that it must be easy to install.
No calendaring yet, I'm afraid. We're still finishing up the server foundation. As soon as there are some decent calendar clients out there to test CAP (Calendar Access Protocol) with, we'll start building the calendar server.
I am absolutely serious about this project. This is not vaporware.
Tired of FB/Google censorship? Visit UNCENSORED!
Some time ago I came accros this link, I havn't read the details, but it seems to be a free exchange server implementation... Maybe there's a catch somewhere... ;) Have phun, Thomas.
/ home
The link:
http://www.billworkgroup.org/billworkgroup
Well, take vpopmail/vmailmgr+phpgroupware+axisgroupware+mozil la+ldap+mailman, install it and you have an almost ready, PalmSync enabled, collaboration featured web groupware suite.
They are all projects in very active development, i know of medium to large enterprises installing this kind of setup and working very fine with it, thank you. I cannot disclose right now who those enterprises are, but they will come forth as soon as the deployments are stable.
The projects ive mentioned even have some methods/scripts and knowledge to migrate from Exchange to this setup.
Give it time, by the end of the year, this combined suite of Free Software projects will have a fully enabled intranet collaboration suite.
Is it as easy to install, configure and administrate as exchange?? NO, its not. But it saves a bundle of dough (pays well too).
So, sit tight, contribute to this projects, and you will see.
Now, on the other hand. If you dont need windows on the desktop, evolution is a GREAT groupware suite supporting icalendar and other open protocols which include the sending/receiving of calendar data, tasks and contacts from one evo to the other. Of course the damned thing is b0rken in debian for which some people should be shot or...err... helped or whatever....
NO SIG
Where's Bourne shell??? Where's vi, sed, and egrep???
Here.
How do I get GUI applications to display over the network???
With this.
How do I read a PostScript file???
With this.
I know that many of these things can be done on Windows eventually
Red Hat Cygwin. The future is now.
No, Red Hat is not paying me to plug Cygwin.
Will I retire or break 10K?
It's made by Fujitsu, and runs on Linux, Solaris and NT. It has a really good web client, and fat (desktop resident) clients for WinX.
It does calendering, email, forums, file sharing and syncs across multiple sites. Directory services use X400/LDAP.
It's really cheap compared to Exchange and you can talk to it via IMAP, NNTP and, in version 6.0, webdav.
Check it out at www.teamware.com.
Chris.
-- I don't have a cool sig.
The reason that Exchange/Outlook are #1, is because they do the most things that people want done, more OFTEN and naturally than its competition.
Bullshit. Exchange is #1 because Office (and hence Outlook) is #1. Nothing else.
The only thing difficult about making an Exchange replacement is the technical (and legal) difficulty of deciphering MS' proprietary protocols. If the Justice Department made MS disclose that interface you'd see Exchange's marketshare drop overnight.
Hell, I remember when Lotus Notes installs had to cross their fingers every time they sent an attachment.
Hmmm, I remember when MS shops had to reboot their Exchange servers nightly to avoid lockups. Oh wait, people still have to do that.
I'm not ENTIRELY going to agree with the "easy to set up". Silly me wanted to grant access to certain newsgroups via the server and I must have done something wrong, because it tried to download the entire feed from news.wol.dk which is some 21+ thousand groups ...
... 21+ thousand times ...
...
How do you delete 21+ thousand groups from the server then? ONE BY ONE!!! You cannot select more than one group to manipulate.
ARGH!!!!!
[space] [delete] [y] [space] [delete] [y] [space] [delete] [y]
I killed a keyboard that weekend
We do not live in the 21st century. We live in the 20 second century.
If Lotus spent so much time thinking about Notes' design, why did they get it so horribly, horribly wrong?
News for Nerds. Stuff that Matters? Like hell.