RFC 5267: Contexts for IMAP4
In plain English — editorial summary, not part of the RFC
The IMAP4rev1 protocol has powerful search facilities as part of the core protocol, but lacks the ability to create live, updated results that can be easily handled. This memo provides such an extension, and shows how it can be used to provide a facility similar to virtual mailboxes. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5267
- Published
- July 2008
- Authors
- D. Cridland; C. King
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- —
- Pages
- 18
- Also known as
- —
Topics
Referenced by
2 later RFCs formally update or obsolete part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5403RPCSEC_GSS Version 2Updated
February 2009
- RFC 5738IMAP Support for UTF-8Obsoleted
March 2010
- RFC 6132Sieve Notification Using Presence InformationCurrent
July 2011
- RFC 7861Remote Procedure Call (RPC) Security Version 3Current
November 2016
- RFC 9586IMAP Extension for Using and Returning Unique Identifiers (UIDs) OnlyCurrent
May 2024
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?