RFC 4550: Internet Email to Support Diverse Service Environments (Lemonade) Profile
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 5550.
Current version: 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) of the IMAP and mail submission 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 Internet Email to Support Diverse Service Environments (Lemonade) profile relies upon extensions to IMAP and Mail Submission protocols; specifically, the URLAUTH and CATENATE IMAP protocol (RFC 3501) extensions and the BURL extension to the SUBMIT protocol (RFC 4409). [STANDARDS-TRACK]
Document record
- Document ID
- RFC4550
- Published
- June 2006
- Authors
- S. Maes; A. Melnikov
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- app
- Pages
- 23
- Also known as
- —
- Obsoleted by:
- RFC 5550
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 4314IMAP4 Access Control List (ACL) ExtensionCurrent
December 2005
- RFC 4978The IMAP COMPRESS ExtensionCurrent
August 2007
- RFC 5162IMAP4 Extensions for Quick Mailbox ResynchronizationObsoleted
March 2008
- RFC 5465The IMAP NOTIFY ExtensionCurrent
February 2009
- RFC 5466IMAP4 Extension for Named Searches (Filters)Current
February 2009
- RFC 5738IMAP Support for UTF-8Obsoleted
March 2010
- RFC 5957Display-Based Address Sorting for the IMAP4 SORT ExtensionCurrent
July 2010
- RFC 4549Synchronization Operations for Disconnected IMAP4 ClientsCurrent
June 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?