7. Links

TODO: This chapter should provide links to external sources of information. PHP manuals, SquirrelMail API documentation, etc.

7.1 RFC standardization documents

SquirrelMail "talks" several protocols. To make sure that we are standards-compatible, we need to refer to RFC documents. Here's a list of the ones we use a lot:

• 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 - Content-Disposition MIME header
• RFC 2195 - IMAP/POP AUTHorize Extension for Simple Challenge/Response
• RFC 2221 - IMAP4 Login Referrals
• RFC 2298 - Details return receipts
• RFC 2342 - The IMAP4 NAMESPACE command
• RFC 2369 - The Use of URLs as Meta-Syntax for Core Mail List Commands and their Transport through Message Header Fields (implemented in listcommands plugin)
• RFC 2616 - HTTP/1.1
• RFC 2683 - IMAP4 Implementation Recommendations
• RFC 2822 - Internet Message Format (obsoletes RFC 822)
• RFC 2831 - Using Digest Authentication as a SASL Mechanism (digest-md5)
• RFC 3028 - Sieve: A Mail Filtering Language (implemented in the Avelsieve plugin)
• RFC 3501 - IMAP version 4rev1 (obsoletes RFC 1730 and RFC 2060)
• RFC 6851 - IMAP4 MOVE Extension