doc/Development/rfc_documents.txt

   1 SquirrelMail "talks" several protocols.  To make sure that we are
   2 standards-compatible, we need to refer to RFC documents.  Here's a list of
   3 the ones we use a lot:
   4
   5 They are available from a wide variety of places on the net.
   6 For instance, if you want RFC 822, you can jump directly to it at
   7     http://www.faqs.org/rfcs/rfc822.html
   8     http://www.rfc-editor.org/rfc/rfc822.txt
   9     http://www.imc.org/Searchable/rfc822
  10
  11 NUMBER     DESCRIPTION
  12 -----------------------------------------------------------
  13 RFC 822    Format of ARPA Internet text messages
  14 RFC 1730   IMAP version 4 (obsoleted by 2060)
  15 RFC 2045   MIME Part One: Format of Internet Message Bodies
  16 RFC 2046   MIME Part Two: Media Types
  17 RFC 2047   MIME Part Three: Message Header Extensions for Non-ASCII Text
  18 RFC 2060   IMAP version 4rev1 (obsoleted by 3501)
  19 RFC 2183   Content-Disposition MIME header
  20 RFC 2195   IMAP/POP AUTHorize Extension for Simple Challenge/Response
  21 RFC 2221   IMAP4 Login Referrals
  22 RFC 2298   Details return receipts
  23 RFC 2342   The IMAP4 NAMESPACE command
  24 RFC 2369   The Use of URLs as Meta-Syntax for Core Mail List Commands and their
  25            Transport through Message Header Fields
  26            (implemented in listcommands plugin)
  27 RFC 2616   HTTP/1.1
  28 RFC 2683   IMAP4 Implementation Recommendations
  29 RFC 2822   Format of an email message (sendmail)
  30 RFC 2831   Using Digest Authentication as a SASL Mechanism (digest-md5)
  31 RFC 3501   IMAP version 4rev1