RFC 8437: IMAP UNAUTHENTICATE Extension for Connection Reuse
In plain English — editorial summary, not part of the RFC
This specification extends the Internet Message Access Protocol (IMAP) to allow an administrative client to reuse the same IMAP connection on behalf of multiple IMAP user identities.
Document record
- Document ID
- RFC8437
- Published
- August 2018
- Authors
- C. Newman
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 11
- Also known as
- —
- Updates:
- RFC 3501
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8438IMAP Extension for STATUS=SIZECurrent
August 2018
- RFC 8474IMAP Extension for Object IdentifiersCurrent
September 2018
- RFC 8514Internet Message Access Protocol (IMAP) - SAVEDATE ExtensionCurrent
January 2019
- RFC 8301Cryptographic Algorithm and Key Usage Update to DomainKeys Identified Mail (DKIM)Current
January 2018
- RFC 8292Voluntary Application Server Identification (VAPID) for Web PushCurrent
November 2017
- RFC 8601Message Header Field for Indicating Message Authentication StatusCurrent
May 2019
- RFC 8265Preparation, Enforcement, and Comparison of Internationalized Strings Representing Usernames and PasswordsCurrent
October 2017
- RFC 7888IMAP4 Non-synchronizing LiteralsCurrent
May 2016
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?