RFC 5092: IMAP URL Scheme
In plain English — editorial summary, not part of the RFC
IMAP (RFC 3501) is a rich protocol for accessing remote message stores. It provides an ideal mechanism for accessing public mailing list archives as well as private and shared message stores. This document defines a URL scheme for referencing objects on an IMAP server. This document obsoletes RFC 2192. It also updates RFC 4467. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5092
- Published
- November 2007
- Authors
- A. Melnikov; C. Newman
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- app
- Pages
- 32
- Also known as
- —
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2017Definition of the URL MIME External-Body Access-TypeCurrent
October 1996
- RFC 1959An LDAP URL FormatObsoleted
June 1996
- RFC 1733Distributed Electronic Mail Models in IMAP4Current
December 1994
- RFC 1732IMAP4 Compatibility with IMAP2 and IMAP2bisCurrent
December 1994
- RFC 1731IMAP4 Authentication MechanismsCurrent
December 1994
- RFC 2732Format for Literal IPv6 Addresses in URL'sObsoleted
December 1999
- RFC 2927MIME Directory Profile for LDAP SchemaCurrent
September 2000
- RFC 2683IMAP4 Implementation RecommendationsUpdated
September 1999
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?