r13 - 13 Jul 2007 - 12:01:28 - MimiYinYou are here: OSAF >  Projects Web  >  ProductManagement > ChandlerEcosystem20030808 > ThirdPartyServerInteroperability

Third Party Server Ecosystem

UNDER SERIOUS CONSTRUCTION

This is a temporary page for notes on the ecosystem of third-party servers for the protocols that Chandler will need to support.

Because the email specs are open, and because the POP and SMTP protocols are so simple, there are a huge number of POP and SMTP products. Most POP and SMTP products -- and essentially all commercial POP and SMTP products -- deliver POP and SMTP as a side effect of their value proposition (e.g. anti-spam) or as a freebie to make their package look beefier.

Summary of protocols

SMTP

Sendmail for years was almost synonymous with SMTP. However, there have been a number of well-publicized security breaches of sendmail. (Not surprising, since it was designed at a time when Internet users didn't have to worry so much about vandals, theives, perverts, and jerks.) The Sendmail author developed a commercial version that is more heavyweight, but it faces stiff competition. Qmail, an open source program, was specifically designed to be more secure. It was followed by postfix, also designed to be more secure.

And SMTP server also comes with most of the IMAP offerings.

There is a survey of SMTP servers available. However, it is both old and limited to the *.net domain -- which is mostly ISPs. ISPs use a much higher percentage of Unix-based, public-domain code than businesses do.

According to a 1998 survey by the qmail author, 90% of reachable hosts in the *.net TLD (not to be confused with Microsoft's .NET!) supported ESMTP.

The commercial version of Sendmail incorporates anti-spam.

Very nice tabular comparison of Sendmail, qmail, postfix, exim, and Courier.

Sysadmin-based reviews of smail, exim, sendmail, qmail, postfix, MMDF, zmailer.

POP

There are zillions of POP servers. While SMTP is a little tricky because of the different mailbox formats and risk of spammers hijacking the service, POP really truly is an incredibly simple protocol. It is even more of an afterthought than SMTP is.

Issues: virtual hosting?

IMAP

IMAP has fewer implementations than POP, in part because IMAP is a huge spec with a ton of features. IMAP has many features that would be client-side features in POP. IMAP packages also usually include SMTP and POP.

In accordance with some version of Murphy's law, the servers that exist not only have different IMAP feature sets, but different interpretations of the features.

Open source server:

Commercial:

See The IMAP Connection for a more complete list.

Also see comparison of IMAP server features.

See the list of IMAP extensions

LDAP

Jabber

Kerberos

WebDAV?)"> Exchange (MAPI/Jungle.WebDAV)

-- DuckySherwood - 09 Aug 2003

Edit | WYSIWYG | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: r13 < r12 < r11 < r10 < r9 | More topic actions
 
Open Source Applications Foundation
Except where otherwise noted, this site and its content are licensed by OSAF under an Creative Commons License, Attribution Only 3.0.
See list of page contributors for attributions.