« Before you blink the feature is there - add geo location information to your Ajax applications. |
Main|
Reader Fields - extreme Edition (update) »
In a recent request by a government customer we were asked about the compliance of Domino with various RFC. I've listed them here for reference:
| RFC | Description | Domino | Remarks |
|---|
| RFC 1123 | Requirements for Internet Hosts Application and Support (STD 3) | Yes | |
| RFC 1870 | SMTP Service Extension for Message Size Declaration (obsoletes: RFC 1653) | Yes | |
| RFC 2476 | Message Submission Obsolete | | see RFC 4409 below. |
| RFC 2505 | AntiSpam Recommendations for SMTP MTAs (BCP 30) | Yes | |
| RFC 5321 | The Simple Mail Transfer Protocol (obsoletes RFC 821 aka STD 10, RFC 974, and RFC 1869, RFC 2821) | Yes | |
| RFC 5322 | Internet Message Format (obsoletes RFC 822 aka STD 11, and RFC 822) | Yes | |
| RFC 2920 | SMTP Service Extension for Command Pipelining (STD 60) | Yes | |
| RFC 3030 | SMTP Service Extensions for Transmission of Large and Binary MIME Messages | No | |
| RFC 3207 | SMTP Service Extension for Secure SMTP over Transport Layer Security (obsoletes RFC 2487) | Yes | |
| RFC 3461 | SMTP Service Extension for Delivery Status Notifications (obsoletes RFC 1891) | Yes | |
| RFC 3462 | The Multipart/Report Content Type for the Reporting of Mail System Administrative Messages (obsoletes RFC 1892) | Yes | |
| RFC 3463 | Enhanced Status Codes for SMTP (obsoletes RFC 1893 ) | Yes | |
| RFC 3464 | An Extensible Message Format for Delivery Status Notifications (obsoletes RFC 1894) | Yes | |
| RFC 3834 | Recommendations for Automatic Responses to Electronic Mail | Yes | |
| RFC 4409 | Message Submission for Mail (obsoletes RFC 2476) | Partial | Domino can be configured to act as an MSA, but is not strictly compliant (e.g. does not qualify unqualified domains in addresses) |
| RFC 4952 | Overview and Framework for Internationalized Email | | This is not a standard - only an informational document |
| RFC 4954 | SMTP Service Extension for Authentication (obsoletes RFC 2554) | Yes | |
| RFC 5068 | Email Submission Operations: Access and Accountability Requirements (BCP 134) | Yes | This is not a standard - it is a document describing a set of operational best practices. Domino can be configured to support these practices |
Disclaimer
This site is in no way affiliated, endorsed, sanctioned, supported, nor enlightened by Lotus Software nor IBM Corporation. I may be an employee, but the opinions, theories, facts, etc. presented here are my own and are in now way given in any official capacity. In short, these are my words and this is my site, not IBM's - and don't even begin to think otherwise. (Disclaimer shamelessly plugged from Rocky Oliver)
© 2003 - 2012 Stephan H. Wissel - all rights reserved as listed here:
Unless otherwise labeled by its originating author, the content found on this site is made available under the terms of an Attribution/NonCommercial/ShareAlike Creative Commons License, with the exception that no rights are granted -- since they are not mine to grant -- in any logo, graphic design, trademarks or trade names of any type.
Google+
Comments
Posted by Stephan H. Wissel At 09:23:26 On 04/15/2009 | - Website - |
thanks for publishing. Perfect listing, I will reuse that.
Claus
Posted by Claus Allweil At 19:36:36 On 04/16/2009 | - Website - |
How do others compare (Exchange, SendMail, qmail, etc)?
Posted by Dave Harris At 18:48:21 On 04/14/2009 | - Website - |