RFC 5550: The Internet Email to Support Diverse Service Environments (Lemonade) Profile
In plain English — editorial summary, not part of the RFC
This document describes a profile (a set of required extensions, restrictions, and usage modes), dubbed Lemonade, of the IMAP, mail submission, and Sieve protocols. This profile allows clients (especially those that are constrained in memory, bandwidth, processing power, or other areas) to efficiently use IMAP and Submission to access and submit mail. This includes the ability to forward received mail without needing to download and upload the mail, to optimize submission, and to efficiently resynchronize in case of loss of connectivity with the server. The Lemonade Profile relies upon several extensions to IMAP, Sieve, and Mail Submission protocols. The document also defines a new IMAP extension and registers several new IMAP keywords. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5550
- Published
- August 2009
- Authors
- D. Cridland; A. Melnikov; S. Maes
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- app
- Pages
- 41
- Also known as
- —
- Obsoletes:
- RFC 4550
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 5616Streaming Internet Messaging AttachmentsCurrent
August 2009
- RFC 5429Sieve Email Filtering: Reject and Extended Reject ExtensionsCurrent
March 2009
- RFC 5784Sieve Email Filtering: Sieves and Display Directives in XMLCurrent
March 2010
- RFC 5259Internet Message Access Protocol - CONVERT ExtensionCurrent
July 2008
- RFC 6009Sieve Email Filtering: Delivery Status Notifications and Deliver-By ExtensionsCurrent
October 2010
- RFC 4468Message Submission BURL ExtensionUpdated
May 2006
- RFC 4416Goals for Internet Messaging to Support Diverse Service EnvironmentsCurrent
February 2006
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?