Once upon a time at a NASA space flight center a long way away, I was an e-mail administrator. At the time, the 1980s, e-mail was still chaotic. The RFC 822 standard was only beginning to bring rhyme and reason to e-mail. One of RFC 822’s competitors, the Common Messaging Calls (CMC) X.400 standard, wasn’t making much progress, but then Microsoft adopted it in 1992, added the concepts of folders to it, and re-named the result Mail Application Programming Interface (MAPI). And, ever since, the e-mail world can broadly be divided into two camps: the RFC 822 Internet compliant e-mail group and the MAPI-compliant Microsoft Outlook/Exchange pack.
Many of us assume that all e-mail works by using such RFC-822isms as e-mail addresses that look like “name@SomePlaceOrTheOther.com.” Not so. MAPI takes a quite different approach. In addition to simply handling e-mail, extended MAPI and Collaboration Data Objects (CDO), which became Microsoft’s default protocol set in Exchange 2003, added the power to manage calendars and addresses. So it is that Exchange and Outlook, while primarily used for e-mail, is also a groupware package.
And, I might add, a very popular one. A recent survey by Ferris Research revealed that Exchange has about 65% market share across all organizations. Lotus Notes/Domino is a distant number two with 10% of the market. POP/IMAP, (Post Office Protocol/Internet Message Access Protocol), the usual way incoming RFC-822 mail is handled? All the dozens of RFC-822 mail servers, including Sendmail, Qmail, and Postfix combined, have only 15% of the business/organization e-mail market.
As for the open-source groupware servers that try to directly compete with Exchange, such as Scalix, Open-Xchange, and Zimbra, Richi Jennings, a Ferris Research analyst, dismissed them as being mere ‘noise’ in the business e-mail market.