The IMAP ENABLE Extension
Metadata
- Publisher
- IETF
- Doc Type
- Standard
- Pages
- 7
- Abstract
- 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]
- Publication Date
- 2008-03-01
- Status Note
- Proposed Standard
- DOI
10.17487/RFC5161- Link
- https://doi.org/10.17487/RFC5161
- Author(s)
- Arnt GulbrandsenAlexey Melnikov
- Keyword(s)
- IMAP
Latest version of IETF RFC 5161
Document Versions — IETF RFC 5161
-
▶ IETF RFC 5161 (2008-03-01)THIS DOC [ACTIVE] [LATEST VERSION]
Normative Reference(s)
- IETF RFC 2119 [Active*]
- IETF RFC 3501 [Superseded*]
- IETF RFC 4551 [Superseded*]
- IETF RFC 5234 [Active, Amended*]
Bibliographic Reference(s)
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC5161.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 5161, The IMAP ENABLE Extension. Available at https://doi.org/10.17487/RFC5161
Snippet:
IETF RFC 5161, The IMAP ENABLE Extension. Available at https://doi.org/10.17487/RFC5161
HTML (ISO 690 compliant)
Preview:
IETF RFC 5161, The IMAP ENABLE Extension. Available at https://doi.org/10.17487/RFC5161
Snippet:
<span class="citation"><cite>IETF RFC 5161</cite>, The IMAP ENABLE Extension. Available at <a href="https://doi.org/10.17487/RFC5161" target="_blank" rel="noopener">https://doi.org/10.17487/RFC5161</a></span>
SMPTE's HTML Pub
Preview:
Snippet:
<li> <cite id="bib-rfc5161">IETF RFC 5161</cite>, The IMAP ENABLE Extension <span class="doi">10.17487/RFC5161</span> </li>
Referenced By
- IETF RFC 5162 [Superseded*]
- IETF RFC 5464 [Active*]
- IETF RFC 5550 [Active*]
- IETF RFC 5738 [Superseded*]
- IETF RFC 6855 [Superseded*]
- IETF RFC 7162 [Active*]
- IETF RFC 8437 [Active*]
- IETF RFC 9051 [Active*]
- IETF RFC 9755 [Active*]