Zarafa Chief Executive Brian Joseph--having ported, as he put it, "all the Exchange features to the Linux platform with full MAPI (messaging application programming interface) implementation"-- said there are significant gaps in the Microsoft documentation released to date. Zarafa makes an e-mail server that is compatible with Outlook
Speaking to ZDNet UK at the CeBIT conference, Joseph said Microsoft's start is not promising: "This could definitely make life easier for developers, but we have spotted over 200 undocumented exceptions, including one that allows you to create recurring calendar appointments in Exchange. It was in the documentation for Exchange 2000, but they forgot to document it for Exchange 2003 and Exchange 2007."
Zarafa produces the eponymous e-mail server that runs on Linux and is used by enterprises such as car-rental company Sixt, which recently migrated its entire e-mail server infrastructure to Zarafa. Zarafa uses the MAPI open standard to communicate to e-mail clients such as Outlook. While Microsoft Exchange uses MAPI too, it also uses a large number of proprietary APIs that let the Outlook client perform actions such as creating recurring calendar appointments on the Exchange server.
"I am very positive about unconditional publication of APIs," said Joseph, "but only time will tell if this is justified, given Microsoft's history. I think hundreds of thousands of developers around the world are very interested in full publication with regular updates, but the devil is in the detail; for policy makers, these gaps in the Exchange documentation should put another light on the value of Microsoft's announcement."
Zimbra Vice President John Robb agreed that Microsoft's announcement is a good move, but again expressed reservations. His company produces the Zimbra Collaboration Suite, which also runs on Linux platforms and servers. The Zimbra Collaboration suite runs 11 million mailboxes through the commercial version of its product and many more through the open-source version.
"The MAPI protocol is open anyway, so that doesn't affect us directly," Robb said, "but we are concerned that Microsoft has not announced which APIs have patent conditions, nor what those conditions are. We're anxiously awaiting details."
Matt Loney of ZDNet UK reported from London.
See more CNET content tagged:
MAPI,
API,
Microsoft Exchange Server,
e-mail server,
gap





As far as MSFT is concerned, all email systems must run on Exchange, or be destroyed.
Their only recent product that hasn't been regarded widely as a disaster? Office 2k7 - a tepid upgrade with a re-arranged menu.
The only thing that hasn't killed them entirely is inertia and heavy vendor lock-in (both of which are showing signs of erosion).
Quite simply, their options are two: Stand Pat, or Fall. I'm thinking that the latter has begun.
/P
- Microsoft should give away all their secrets
-
by Vegaman_Dan
March 10, 2008 2:55 PM PDT
- I find it funny to think that companies complain because Microsoft won't give away all their secrets to the public.
-
Reply to this comment
-
-
- API's != secrets.
-
by Penguinisto
March 10, 2008 3:41 PM PDT
- Source code is a secret. Sales techniques are secrets.
-
View
reply
-
(10 Comments)*WHY* should they give out all their information? Especially to a competing company in that particular product field?
I wasn't aware that requiring Microsoft to give away its proprietary secrets was a right guaranteed by the US Constitution. Hmm.
API's are not secrets - they are hooks into the OS by which applications can access its functions.
[i]"I wasn't aware that requiring Microsoft to give away its proprietary secrets"[/i]
Count yourself lucky. By all rights, Microsoft should have been broken up after their conviction for monopolistic anti-trust practices in the late 1990's.
/P