From: Michael M Slusarz <slusarz@curecanti.org>
Date: Fri, 20 Mar 2009 16:54:56 +0000 (-0600)
Subject: First pass at trying to list RFC compliance.
X-Git-Url: https://git.internetallee.de/?a=commitdiff_plain;h=c0c303f0c3a9f2bbfeeaa0a01ba3c64a9a8060dd;p=horde.git

First pass at trying to list RFC compliance.
---

diff --git a/imp/docs/RFCS b/imp/docs/RFCS
new file mode 100644
index 000000000..e1b45b7c4
--- /dev/null
+++ b/imp/docs/RFCS
@@ -0,0 +1,125 @@
+====================
+ IMP RFC Compliance
+====================
+
+IMP is designed to be an RFC compliant mail user agent (MUA). The following
+is a list of RFCs implemented in Horde/IMP. RFC text can be found at:
+
+  http://tools.ietf.org/html/
+
+
+IMAP
+====
+
+RFC 3501 - IMAP4rev1 specification
+
+The following IMAP extensions/features are supported:
+
+RFC 2086/4314   ACL
+RFC 2087        QUOTA
+RFC 2088        LITERAL+
+RFC 2195        AUTH=CRAM-MD5
+RFC 2221        LOGIN-REFERRALS
+RFC 2342        NAMESPACE
+RFC 2595/4616   TLS & AUTH=PLAIN
+RFC 2831        DIGEST-MD5 authentication mechanism.
+RFC 2971        ID
+RFC 3502        MULTIAPPEND
+RFC 3516        BINARY
+RFC 3691        UNSELECT
+RFC 4315        UIDPLUS
+RFC 4422        SASL Authentication (for DIGEST-MD5)
+RFC 4466        Collected extensions (updates RFCs 2088, 3501, 3502, 3516)
+RFC 4551        CONDSTORE
+RFC 4731        ESEARCH
+RFC 4959        SASL-IR
+RFC 5032        WITHIN
+RFC 5161        ENABLE
+RFC 5162        QRESYNC
+RFC 5182        SEARCHRES
+RFC 5255        LANGUAGE/I18NLEVEL
+RFC 5256        THREAD/SORT
+RFC 5267        ESORT
+
+
+POP3
+====
+
+STD 53/RFC 1939 - POP3 specification
+
+The following POP3 extensions/deatures are supported
+
+RFC 1734/5034   POP3 SASL
+RFC 2195        CRAM-MD5 authentication
+RFC 2449        POP3 extension mechanism
+RFC 2595/4616   PLAIN authentication
+
+
+Mail Messages
+=============
+
+RFC 822/2822/3490/5322
+    - Internet Message Format
+
+RFC 2369
+    - The Use of URLs as Meta-Syntax for Core Mail List Commands and their
+      and their Transport through Message Header Fields
+
+RFC 2919
+    - List-Id: A Structured Field and Namespace for the Identification of
+      Mailing Lists
+
+RFC 3490
+    - Internationalizing Domain Names in Applications (IDNA)
+
+RFC 3798
+    - Message Disposition Notification
+
+
+SMTP
+====
+
+RFC 821/2821/5321
+    - Simple Mail Transfer Protocol
+
+RFC 1652
+    - SMTP Service Extension for 8bit-MIMEtransport
+
+
+MIME
+====
+
+RFC 1847
+    - Security Multiparts for MIME: Multipart/Signed and Multipart/Encrypted
+
+RFC 1740
+    - MIME Encapsulation of Macintosh files - MacMIME
+
+RFC 1896
+    - The text/enriched MIME Content-type
+
+RFC 2045
+    - MIME Part One: Format of Internet Message Bodies
+
+RFC 2046
+    - MIME Part Two: Media Types
+
+RFC 2047
+    - MIME Part Three: Message Header Extensions for Non-ASCII Text
+
+RFC 2183
+    - Communicating Presentation Information in Internet Messages: The
+      Content-Disposition Header
+
+RFC 2231
+    - MIME Parameter Value and Encoded Word Extensions: Character Sets,
+      Languages, and Continuations
+
+RFC 2387
+    - The MIME Multipart/Related Content-type
+
+RFC 3156
+    - MIME Security with OpenPGP
+
+RFC 3464
+    - An Extensible Message Format for Delivery Status Notifications