RFC 5161: The IMAP ENABLE Extension
In plain English — editorial summary, not part of the RFC
Most IMAP extensions are used by the client when it wants to and the server supports it. However, a few extensions require the server to know whether a client supports that extension. The ENABLE extension allows an IMAP client to say which extensions it supports. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5161
- Published
- March 2008
- Authors
- A. Gulbrandsen; A. Melnikov
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- —
- Pages
- 7
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5162IMAP4 Extensions for Quick Mailbox ResynchronizationObsoleted
March 2008
- RFC 5182IMAP Extension for Referencing the Last SEARCH ResultCurrent
March 2008
- RFC 4978The IMAP COMPRESS ExtensionCurrent
August 2007
- RFC 4959IMAP Extension for Simple Authentication and Security Layer (SASL) Initial Client ResponseCurrent
September 2007
- RFC 5464The IMAP METADATA ExtensionCurrent
February 2009
- RFC 5465The IMAP NOTIFY ExtensionCurrent
February 2009
- RFC 5466IMAP4 Extension for Named Searches (Filters)Current
February 2009
- RFC 5738IMAP Support for UTF-8Obsoleted
March 2010
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?