Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>The roadmap is <em>reasonably</em> short. Start with the IMAP 4rev1 RFC, <a href="http://tools.ietf.org/html/rfc3501" rel="nofollow">RFC 3501</a>. It has a <a href="http://tools.ietf.org/html/rfc3501#appendix-A" rel="nofollow"><code>Normative References</code></a> appendix that lists all the RFCs it directly depends on, and it references those RFCs in the appropriate places in the document.</p> <p>The really crucial ones -- you can read them in this order -- are Internet Message Format (I'd recommend <a href="http://tools.ietf.org/html/rfc5322" rel="nofollow">RFC 5322</a> instead of RFC 2822 to be more up-to-date), the MIME RFCs (<a href="http://tools.ietf.org/html/rfc2045" rel="nofollow">RFC 2045</a>, <a href="http://tools.ietf.org/html/rfc2046" rel="nofollow">2046</a>, and <a href="http://tools.ietf.org/html/rfc2047" rel="nofollow">2047</a>), Content-Disposition (<a href="http://tools.ietf.org/html/rfc2183" rel="nofollow">RFC 2183</a>), TLS (<a href="http://tools.ietf.org/html/rfc2595" rel="nofollow">RFC 2595</a>), and UTF-7 (<a href="http://tools.ietf.org/html/rfc2152" rel="nofollow">RFC 2152</a>) to handle non-ASCII folder names.</p> <p>Once you've got the baseline protocol finished, you'll want to start looking at extensions. Some of them will make your life much easier... when the server also provides support. You'll definitely want IDLE (<a href="http://tools.ietf.org/html/rfc2177" rel="nofollow">RFC 2177</a>) and UIDPLUS (<a href="http://tools.ietf.org/html/rfc4315" rel="nofollow">RFC 4315</a>). SORT (<a href="http://tools.ietf.org/html/rfc5256" rel="nofollow">RFC 5256</a>) is a good one as well, and NAMESPACE (<a href="http://tools.ietf.org/html/rfc2342" rel="nofollow">RFC 2342</a>) may be useful. You'll probably also need to handle some extra SASL authentication mechanisms, so start with <a href="http://tools.ietf.org/html/rfc1731" rel="nofollow">RFC 1731</a> and go from there as necessary.</p> <p>Here's the text from Appendix A:</p> <pre><code>The following documents contain definitions or specifications that are necessary to understand this document properly: [ABNF] Crocker, D. and P. Overell, "Augmented BNF for Syntax Specifications: ABNF", RFC 2234, November 1997. [ANONYMOUS] Newman, C., "Anonymous SASL Mechanism", RFC 2245, November 1997. [CHARSET] Freed, N. and J. Postel, "IANA Character Set Registration Procedures", RFC 2978, October 2000. [DIGEST-MD5] Leach, P. and C. Newman, "Using Digest Authentication as a SASL Mechanism", RFC 2831, May 2000. [DISPOSITION] Troost, R., Dorner, S. and K. Moore, "Communicating Presentation Information in Internet Messages: The Content-Disposition Header", RFC 2183, August 1997. [IMAP-TLS] Newman, C., "Using TLS with IMAP, POP3 and ACAP", RFC 2595, June 1999. [KEYWORDS] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [LANGUAGE-TAGS] Alvestrand, H., "Tags for the Identification of Languages", BCP 47, RFC 3066, January 2001. [LOCATION] Palme, J., Hopmann, A. and N. Shelness, "MIME Encapsulation of Aggregate Documents, such as HTML (MHTML)", RFC 2557, March 1999. [MD5] Myers, J. and M. Rose, "The Content-MD5 Header Field", RFC 1864, October 1995. [MIME-HDRS] Moore, K., "MIME (Multipurpose Internet Mail Extensions) Part Three: Message Header Extensions for Non-ASCII Text", RFC 2047, November 1996. [MIME-IMB] Freed, N. and N. Borenstein, "MIME (Multipurpose Internet Mail Extensions) Part One: Format of Internet Message Bodies", RFC 2045, November 1996. [MIME-IMT] Freed, N. and N. Borenstein, "MIME (Multipurpose Internet Mail Extensions) Part Two: Media Types", RFC 2046, November 1996. [RFC-2822] Resnick, P., "Internet Message Format", RFC 2822, April 2001. [SASL] Myers, J., "Simple Authentication and Security Layer (SASL)", RFC 2222, October 1997. [TLS] Dierks, T. and C. Allen, "The TLS Protocol Version 1.0", RFC 2246, January 1999. [UTF-7] Goldsmith, D. and M. Davis, "UTF-7: A Mail-Safe Transformation Format of Unicode", RFC 2152, May 1997. The following documents describe quality-of-implementation issues that should be carefully considered when implementing this protocol: [IMAP-IMPLEMENTATION] Leiba, B., "IMAP Implementation Recommendations", RFC 2683, September 1999. [IMAP-MULTIACCESS] Gahrns, M., "IMAP4 Multi-Accessed Mailbox Practice", RFC 2180, July 1997. </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POWhat RFCs need to be considered in developing an IMAP client?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USdkarp
    1. USdkarp
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POWhat RFCs need to be considered in developing an IMAP client?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload