Linked by Thom Holwerda on Fri 2nd Feb 2007 11:30 UTC, submitted by anonymous
Novell and Ximian When Novell and Microsoft announced their unlikely partnership, a part of the arrangement that got little attention at the time was that they'd create a joint research facility, where both company's technical experts would collaborate on new joint software solutions. Now, they're staffing up.
Thread beginning with comment 208386
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: ms/novell
by butters on Fri 2nd Feb 2007 16:05 UTC in reply to "ms/novell"
butters
Member since:
2005-07-08

What Linux really needs is open specifications for communicating with Exchange Server. I don't see Exchange interoperability listed in the agreement, and I'm really disappointed in Novell for not pushing for this.

When Microsoft went into this deal, the executives must have said, "offer them interoperability, use popular buzz-words like virtualization, throw them a bone on ODF support in MS Office (they won't use it if it's not the default), but DON'T let them in on our Exchange racket."

Edited 2007-02-02 16:06

Reply Parent Score: 4

RE[2]: ms/novell
by IanSVT on Fri 2nd Feb 2007 17:25 in reply to "RE: ms/novell"
IanSVT Member since:
2005-07-06

What Linux really needs is open specifications for communicating with Exchange Server. I don't see Exchange interoperability listed in the agreement, and I'm really disappointed in Novell for not pushing for this.

I don't think there was any mention of this, mostly because it's already available. There is an Exchange connector available for Outlook/Exchange interoperability. It's GPL.

From the server end, it would be an almost inpossible task to get Exchange server modules working on Linux. They would have to port AD over if I'm not mistaken.

If you want a cross platform groupware system, use GroupWise. It works fine on mulitple platform on both the server and client(although the cross platforms GroupWise client leaves a bit to be desired).

Edited 2007-02-02 17:26

Reply Parent Score: 1

RE[3]: ms/novell
by butters on Sat 3rd Feb 2007 01:23 in reply to "RE[2]: ms/novell"
butters Member since:
2005-07-08

I'm aware of the Exchange plugins available for non-Outlook email clients. They use the OWA web-based API, and they tend to suck. Even Microsoft's own OWA web frontend doesn't work properly with the OWA API. Apparently, they need to do all sorts of HTML tricks to get it to work.

There are many better ways to implement email and collaboration features than using Exchange. However, most businesses use Exchange anyway. A discussion of why they act so irrationally is beyond the scope of this thread. But suffice it to say that the majority of businesses run Exchange, and a majority of those aren't interested in migrating to a different collaboration suite.

There ways a Slashdot post about this the other day. Some Dell employee apparently has nothing better to do than try installing Linux every few years and test if it has a collaboration client that integrates well with Dell's Exchange implementation. According to this luser, it still doesn't work. The comments mainly included Linux fanboys ranting about Microsoft not publishing the Exchange API and making it as hard as possible to interoperate with non-Outlook clients. The minority opinion was that it doesn't matter how unhelpful Microsoft is, that it would apparently be really simple to reverse engineer the API if the Linux crybabies would stop whining and get to work.

I don't know how the corporate world managed to fall for Microsoft's ploy to proprietize email. But they did, and there's not much we can do about that. That's why we need a fully-functional Exchange client for Linux.

Reply Parent Score: 3