RFC 5259: Internet Message Access Protocol - CONVERT Extension
In plain English — editorial summary, not part of the RFC
CONVERT defines extensions to IMAP allowing clients to request adaptation and/or transcoding of attachments. Clients can specify the conversion details or allow servers to decide based on knowledge of client capabilities, on user or administrator preferences, or on server settings. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5259
- Published
- July 2008
- Authors
- A. Melnikov; P. Coates
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- app
- Pages
- 30
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5524Extended URLFETCH for Binary and Converted PartsCurrent
May 2009
- RFC 5550The Internet Email to Support Diverse Service Environments (Lemonade) ProfileCurrent
August 2009
- RFC 5616Streaming Internet Messaging AttachmentsCurrent
August 2009
- RFC 4468Message Submission BURL ExtensionUpdated
May 2006
- RFC 4416Goals for Internet Messaging to Support Diverse Service EnvironmentsCurrent
February 2006
- RFC 5257Internet Message Access Protocol - ANNOTATE ExtensionCurrent
June 2008
- RFC 5255Internet Message Access Protocol InternationalizationCurrent
June 2008
- RFC 5232Sieve Email Filtering: Imap4flags ExtensionCurrent
January 2008
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?