RFC 8508: IMAP REPLACE Extension
In plain English — editorial summary, not part of the RFC
This document defines an IMAP extension that can be used to replace an existing message in a message store with a new message. Message replacement is a common operation for clients that automatically save drafts or notes as a user composes them.
Document record
- Document ID
- RFC8508
- Published
- January 2019
- Authors
- S. Brandt
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 11
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8514Internet Message Access Protocol (IMAP) - SAVEDATE ExtensionCurrent
January 2019
- RFC 8498A P-Served-User Header Field Parameter for an Originating Call Diversion (CDIV) Session Case in the Session Initiation Protocol (SIP)Current
February 2019
- RFC 8497Marking SIP Messages to Be LoggedCurrent
November 2018
- RFC 8486Ambisonics in an Ogg Opus ContainerCurrent
October 2018
- RFC 8484DNS Queries over HTTPS (DoH)Current
October 2018
- RFC 8474IMAP Extension for Object IdentifiersCurrent
September 2018
- RFC 8463A New Cryptographic Signature Method for DomainKeys Identified Mail (DKIM)Current
September 2018
- RFC 8457IMAP "$Important" Keyword and "\Important" Special-Use AttributeCurrent
September 2018
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?