Slashdot Mirror

← Back to Stories (view on slashdot.org)

Open Xchange Server Source-code Released

Posted by Hemos on from the msft-exchange-gets-a-new-competitor dept.

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."

9 of 94 comments (clear)

  1. Re:Very ncie, but ... by Micah · · Score: 3, Informative

    That might be the same with my organization, although Exchange (5.5) is only used in one location.

    There's also Bynari Insight Server which has a somewhat impressive feature list, including an Exchange migration tool. We're testing it now. I would be interested in knowing if anyone here uses that.

  2. It's not all that good by a.koepke · · Score: 4, Informative

    This product sounds good but out of personal experience it leaves quite a bit to be desired.

    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.

    --


    (\(\
    (^.^)
    (")")
    *This is the cute bunny virus, please copy this into your sig so it can spread
    1. Re:It's not all that good by mandreiana · · Score: 5, Informative
      Try OpenGroupware, it doesn't have these problems (except IMAP email, for which it has a simple web client). I recently had to compare them both for a company and OpenGroupware was better in terms of stability, implementation and community.

      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.

  3. EXMERGE by Anonymous Coward · · Score: 1, Informative

    export your stuff to psts, then import it to your (imap) mailbox. i still wouldn't use the product though.

  4. Re:Very ncie, but ... by KodaK · · Score: 2, Informative

    We've been using it for two years and are happy with it. If you're interested in further discussion, feel free to email.

    --
    --J(K) DOS is like Unix in exactly the same way that a pinto is like an aircraft carrier.
  5. business opportunity by Doc+Ruby · · Score: 3, Informative

    The "outlook" ;) for upgrades is less daunting. There is an upgrade *path*, though it's not as automated as we'd like. Publishing and supporting a migration tool sounds like a good way to make a living, capitalizing on the migration from Exchange to Open-Xchange. Especially if it were a plugin installed when O-X is installed, which led the installer through the upgrade path with data import and a tutorial. A "Call for Help" button connected to a live support desk could also clock some ducats, while ensuring a graceful migration. Corporate IT departments love that kind of organizational reliability when risking any platform change.

    --

    --
    make install -not war

  6. Re:Very ncie, but ... by sw155kn1f3 · · Score: 3, Informative

    CommuniGate Pro is an exchange replacement too

    --
    - Arwen, I'm your father, Agent Smith.
    - Well, you're just Smith, but my father is Aerosmith!
  7. Re:What about Groupwise? by o517375 · · Score: 2, Informative

    Groupwise is very nice but still the client is a few light years behind Outlook 2003. But the Server has certain features that make it light years ahead of Exchange. So you end up with a few Outlook junky grumblers and a majority of satisfied users. The problem is when some of the grumblers are at the top of the company comparing notes with Outlook users at other companies. They don't understand the technical justifications for Groupwise over Exchange and the herd mentality dominates. Then there's always of Groupwise's high cost and of course it's closed.

    )))))))))))))))))))))

    Vote for the liberal. It's important.

  8. Danger, Danger! by Anonymous Coward · · Score: 1, Informative

    You know what will happen, don't you? You will replace Exchange on the backend. Your replacement will interface with Outlook like shit on a stick. Everyone will be happy, birds will be singing, small animals will skip and play in the sunny meadow.

    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 best interests of their money grubbing shareholders. One of whom is your PHB. No, it's you, you stooge. You broke Microsoft! And you're outta here!

    The right answer to everyone's need to integrate mail and calendaring is to use a different system altogether. One built on open standards. No Microsoft in the front, no Microsoft in your rear. And everyone will live happily ever after.