Open Xchange Server Source-code Released 94
d3vi1 writes "Netline, the main developer of Open-Xchange, has just released the GPL licenced version to the masses. The product is mostly known by users because of SuSE's Open-Xchange Server, a product started from "comFire Groupware".
Open-Xchange is a groupware suite with WebDAV interface (XML), LDAP, iCal and HTTP(S) support. An Evolution plugin is on the way."
Very ncie, but ... (Score:5, Interesting)
Re:Very ncie, but ... (Score:4, Informative)
There's also Bynari Insight Server which has a somewhat impressive feature list [bynari.net], including an Exchange migration tool. We're testing it now. I would be interested in knowing if anyone here uses that.
Re:Very ncie, but ... (Score:2, Informative)
Very ncie, but ...Debutante software. (Score:3, Interesting)
Re:Very ncie, but ...Debutante software. (Score:3, Interesting)
Very good question. It's highly pathetic IMHO. I keep hearing about organization after organization switching to Exchange, despite the fact that it's by far the most expensive available (my organization did a cost study on several different gr
Re:Very ncie, but ...Debutante software. (Score:5, Funny)
Have you really gone through and looked at what you get when you go the whole Exchange route vs. what else is out there? Microsoft pricing and security aside for the moment (yes, it sucks. That's a given. No arguments.) the equivalent you get in the Open Source world for Exchange is...
SMTP server
NNTP server
LDAP server
IMAP server
POP server
HTTP server
Database Server
MS-Specific (MAPI) server
This is all the back-end stuff that has nothing to do with Outlook. In addition, all of the various servers act well distributed and use the ldap server for central authentication for all users. The database server currently doesn't do replication for individual mailboxes but does for the NNTP portion. The SMTP server uses the LDAP server to reference valid mailbox addresses and
the specific database server users's mailboxes reside on. The MAPI, POP and IMAP servers all use LDAP to reference where the specific database server user's mailboxes reside on. They also use LDAP for authentication.
(This is why you can use IMAP [which is still supported half-assed in Exchange 2003] or POP with any client - and the http stuff with any modern web client)
Then let's add the Outlook client. This builds the calendaring into the picture. Server-side everyone's scheduling information is stored in a newsgroup and an entry in the database. When building a new meeting, the client queries the newsgroup to see if time is clear or not (to allow checking to see if everyone is free) and then sends the meeting info out to the various invites.
Oh - and the client also allows setting up for viewing other's calendars and administrative assistants can handle their bosses' mail and calendaring functions through the client without having to lose their own stuff or log in as their boss. And I haven't touched a lot of the other server-side stuff and how 3rd parties have built tools around it.
Consider the complexity of mail and groupware. It can't be squat compared to, say, the Linux Kernel. So why is it so evasive?
Ease of use. Ease to support. Interoperability. Support of just about any mail client. Ties to make the functions that are not mail-specific work even with non-MS mail clients. (link on meeting invite to the web based item for completion)
These are just a few of the reasons why organizations go this route and it has nothing to do with being in Microsoft's pocket to begin with. And it doesn't include things like tying your voice mail into your inbox so that it is available via your wireless device, your phone or your e-mail client.. or being able to schedule multi-user conference calls that update calendars and send out notifications or..
The open source packages that are available today do not have the level of integration or functionality that is offered via Exchange to an organization. Once the above si working fairly seamlessly as an integrated package that could be deployed - then a true challenge to Exchange would exist - for now it isn't there.
Re:Very ncie, but ...Debutante software. (Score:4, Interesting)
If you want to replace exchange look to replace outlook first.
Re:Very ncie, but ...Debutante software. (Score:2)
It is the same with MP3 players. Look at the thousands of MP3 players out there and then look at the number of people with iPods. Ask people (non geeks) about MP3 players and most people will nearly always say 'oh you mean an iPod'.
Re:Very ncie, but ... (Score:4, Informative)
Hey, look what I found! (Score:5, Interesting)
EXMERGE (Score:1, Informative)
Re:Very ncie, but ... (Score:1)
It's nice to see someone offer an F/OSS alternative, now to get it up to par with exchange.
business opportunity (Score:4, Informative)
Re:Very ncie, but ... (Score:4, Interesting)
Meh. This is why I'm putting my money and energy into Exchange4Linux [exchange4linux.org] -- it's a MUCH better Exchange Server replacement than anything else I've tried, and that includes SLOX, Bynari, OGO, Kroupware, Samsung Contact and whatever else I've forgotten. Server is free and totally open-source (written in Python) and runs Postgres for the backend. Outlook connectors are reasonably priced, too.
You have no idea how wonderful it is to just drag and drop the user's store into E4L and then be able to use straight SQL to pull data out. I haven't yet tried inserting data but it looks to be just as straightforward. And no goofy-ass web-based crap is involved. :-)
Re:History repeating (Score:1)
I eagerly await all the agonizing, cliche OSS moments that will come from this product.
:-) I agree the name sucks ass but it's better than its other name: BILL Open Workgroup Project.
Re:History repeating (Score:3, Interesting)
Yes, they should change their name ASAP (as in NOW you morons !).
But other than that it seems like a reasonable approach to me.
Python allows for rapid developement, performance critical parts can be done in C. Postgres, while no performance wonder, seems like a reasonable stable foundation. I have not seen their code (in fact all I know is from a glimpse at their website) but with some skilled and dedicated coders they should be able to get somewhere in a couple months.
O
Re:History repeating (Score:2)
I'm sure it's a fine product, honest.
Re:History repeating (Score:1)
Re:Very ncie, but ... (Score:1)
Re:Very ncie, but ... (Score:3, Interesting)
There's always the option of upgrading Exchange to conventional standards compliant email - but that is difficult and painful because of the lock in to the wierd undocumented MS Exchange way of doing things - plus the tendancy of users to use Outlook for everything and put the only copies of critical company information into those nasty PST files (somehow got it out of there and into clearquest, and from there to anywhere).
With every other mail server on the planet it
Would this tool help conversions? (Score:1)
I haven't looked at the ' Open-Xchange' product yet, does it have an 'import' option?
Re:Why java ? (Score:1, Flamebait)
Then..
And then..
Either you a) just gravely insulted the Open Xchange developers or b) should not be in charge of making any significant decision
Re:Why java ? (Score:1)
If I state that's a tough decision for you, that's arguably an insult.
I suppose I should have emphasized the bit about being a tough decision. That was my point.
For what it's worth, I'm a Java developer myself and while C and PHP have their merits, I also prefer Java development.
Re:Why java ? (Score:1)
Re:Why java ? (Score:3, Insightful)
Re:Why java ? (Score:2)
Re:Why java ? (Score:2)
Re:Why java ? (Score:2)
Re:Why java ? (Score:2)
Re:Why java ? (Score:2)
Re:Why java ? (Score:2)
To recap:
rute20740 posted [slashdot.org]:
"Python would have also been a good choice. Being a modern object oriented language with a lot of the s
Re:Why java ? (Score:2)
This is what irked me:
My opinion is that free software wich strongly depends on proprietary components is not as free as software that doesn't. in short: if it runs on GCJ/Kaffe it's more free than
Re:Why java ? (Score:2, Insightful)
Evolution -- excellent, but Outlook -- mandatory (Score:5, Interesting)
If that's the case, I'd be a bug on the ass of my LAN manager to convert us immediately, and he'd probably jump at it.
Re:Evolution -- excellent, but Outlook -- mandator (Score:2)
Re:Evolution -- excellent, but Outlook -- mandator (Score:2)
Re:Evolution -- excellent, but Outlook -- mandator (Score:2, Interesting)
Re:Evolution -- excellent, but Outlook -- mandator (Score:3, Insightful)
Companies have forms, applications, scheduling, shared files, shared contact lists and a whole bunch of things built on top of Exchange Server and a big part of it simply can't be migrated. It's completely different from an individual user's experience and satisfaction with 3rd party MUA.
Re:Evolution -- excellent, but Outlook -- mandator (Score:2)
Re:Evolution -- excellent, but Outlook -- mandator (Score:2)
Re:Evolution -- excellent, but Outlook -- mandator (Score:4, Insightful)
Outlook bonds with Exchange (which we also use -- a slightly older version which works poorly with Evolution's calendaring) so that we cannot leave Outlook, and therefore cannot leave Windows. If we can get a work-alike for Exchange, we can slowly move people into a hetrogeneous (or even completely non-Windows) evironment.
We COULD upgrade our Exchange to allow Evolution to be more of a replacement for Outlook than it is, but that means spending money on a service, and our uppers would, after that, be unwilling to let us scrap it.
The optimal path would be to replace the Exchange server with something that plays well with Outlook, then migrate our people to Linux desktop, where those people don't need Windows speghettified apps.
Re:Evolution -- excellent, but Outlook -- mandator (Score:1, Interesting)
Anybody know of any MAPI service provider development project for Open-Xchange?
Re:Evolution -- excellent, but Outlook -- mandator (Score:2)
--dave
Re:Evolution -- excellent, but Outlook -- mandator (Score:2)
I suspect the future is not MS Outlook or evolution, but webmail that will work on telephones - just like what some people have been using for a while.
Re:Evolution -- excellent, but Outlook -- mandator (Score:1)
Danger, Danger! (Score:1, Informative)
Then Microsoft will upgrade their Office Suite. Your PHB will insist on upgrading. And suddenly the clouds roll in. It just won't work right anymore. And who's to blame? Microsoft? Nah, they're just being a good little feudal kingdom, and behaving in the
Whoa! (Score:4, Interesting)
With Evolution, Connector and now Open Exchange the barriers to interoperability are breaking down.
Microsoft made a deft move by bundling together database and mail server technologies for Exchange (Outlook/Exchange gets used heavily at MyCorp).
It's good to see some opens source alternatives become available, not least because of the competitive pricing pressure it will put on those heavily used products.
It's not all that good (Score:5, Informative)
We recently installed this and tried using it in our office and found it to be very buggy and unstable. The first version we installed, 4.0, wouldn't even create user accounts properly. It would screw up the samba each time it tried to create the account.
The whole fact that it uses IMAP for its email made it clumsy to use in Outlook as you had your personal folders and then also had your IMAP folders and then also had your SLOX folders. Was quite confusing for most of the users. Also the calendar sharing wasn't that well designed at all. The user was forced to have two calendars, one in public folders and their own one. There was no way to share your normal calendar around the network.
SuSE have a good product here but it is still far from a proper Exchange replacement. We ended up sending the software back and getting Exchange instead.
Re:It's not all that good (Score:5, Informative)
It misses Knowledge Management (but has already a bugzilla request) and forum. OX's KM module wasn't very useful though compared with OGO's request.
The only drawback we saw for OGO it's the language - Objective C, but it has a nice way to use xml-rpc requests so we can add java or php functionality over it (forum, if needed). OX it's a mix of Java, perl and C.
Re:It's not all that good (Score:2)
We neded up using http://stalker.com's CommuniGate Pro. That's pity, because I liked OpenGroupware.
Re:It's not all that good (Score:1)
At least with Slox/Open-Xchange, you can try out the connectors: http://www.sloxhelp.org/filemgmt/index.php/ [sloxhelp.org].
Re:It's not all that good (Score:3, Insightful)
It may not be ready for prime time today, but in 6 months or so I bet it is. This is the most needed FOSS project yet (IMHO). Anything that keeps me from having to maintane an Exchange server is awesome in book.
Re:It's not all that good (Score:1)
Re:It's not all that good (Score:2)
Source code comments in German (Score:5, Interesting)
Other than that, the code seems organized well, from a quick glance.
Re:Source code comments in German (Score:1)
We'd better get used to it, more and more software is being written outside the English speaking world (it always was but open source brings it to ya). Just think how anoying writing C is for Germans, all the keywords are En
Re:Source code comments in German (Score:1)
By the way, I really prefer English keywords because mostly they are shorter than their german translations.
We need a standard. (Score:5, Interesting)
A few months ago, the folks at the Citadel [citadel.org] project took notice of the specs for the Kolab [kolab.org] project, and began promoting its storage and network formats as a proposed standard [citadel.org] for open source groupware. It was a nice, simple, elegant design, using vCard and vCalendar formats. Others shared the same view: for example, the Aethera [thekompany.com] people joined in, and made their client Kolab-compatible. We at the Citadel project made our server Kolab-compatible. This was shaping up to be something good.
So what did the Kolab people do? They designed "Kolab 2" which uses data formats that are neither forward nor backward compatible with Kolab 1. They completely disregarded not only their installed base, but other projects that were working towards compatibility. The new format is proprietary (documented and unencumbered, but proprietary) and gratuitously abuses XML instead of following the industry-standard vCard and vCalendar formats.
The Aethera and Citadel projects are currently in discussions to work together to create a true. open, standards-compliant, cross-platform, end-to-end groupware solution. We invite others to participate as well -- we won't ignore you the way the Kolab people have.
As for OpenXchange? As others have suggested, this is really just a couple of bells and whistles glued onto someone else's IMAP server. It's not really a true solution.
Need some info (Score:3, Interesting)
Also since you just noticed the specs a few months ago it
Free/Cheap Host (Score:5, Interesting)
Re:Free/Cheap Host (Score:2)
A friend and I have been sharing a Virtual Private Server for a while now. $35/month gets us 6 GB of disk space (don't recall the memory limit, but we're on a dual 2.8 GHz Xeon with 4 GB RAM, and I think they have 30 people as their maximum. The thing *FLIES*), and 75 GB of bandwidth. (We're hosting with Dinix [dinix.com].) You can probably find a lot cheaper soon, especially when EV1Servers (formerly RackShack) rolls out their Virtuozzo licenses for some
Re:Free/Cheap Host (Score:1)
http://spinweb.net/solutions/hosting/suse-linux-o
What baffles me... (Score:5, Insightful)
Bynari - too buggy.
SLOX - not tried yet.
We ended up using CommuniGate Pro from stalker.com.
I don't like it.. server is too closed source and inflexible.
BUT it has _excellent_ OL interoperability... My boss just forced me to use it because of this.
When we'll see some open source or at least free Outlook Connector to these exch-replacing systems, we effectively killed exchange.
Like this? (Score:1)
Re:Like this? (Score:2)
I need outlook->open source server connector. So client is Outlook and server is some open source server such as SLOX or OpenExchnage or Exchange4Linux.
Re:What about Groupwise? (Score:2, Informative)
XServe integration (Score:2)
does it run on gcj or Kaffe? (Score:1)
Re:does it run on gcj or Kaffe? (Score:1)
Sun might, for example, decide that the only Linux they are going to support from now on is going to be their own version and they can refuse to license Java to anybody who wants to port it to any other version. Or Sun might simply screw up technically and break things (arguabl
Options for Exchange/Outlook replacement? (Score:3, Interesting)
- feature list compared with Exchange / Outlook (calendar, public folders)
- plays well with Outlook (many sites just want to replace Exchange, but still use Outlook)
I've got several small business customers who are well informed and don't want to get caught up in MS dependency. They're either running demo Exchange (with the built in time bomb), or an email-only server and wishing they had calendaring. In general, they'd prefer to use Outlook as long as they have the ability to dump it and replace it with something else with little / no business impact.
Any pointers / URLs?
Win32 version of Evolution. (Score:1, Flamebait)
Scalix (Score:1)
groupware overview (Score:1)