RFC 4468: Message Submission BURL Extension
In plain English — editorial summary, not part of the RFC
The submission profile of Simple Mail Transfer Protocol (SMTP) provides a standard way for an email client to submit a complete message for delivery. This specification extends the submission profile by adding a new BURL command that can be used to fetch submission data from an Internet Message Access Protocol (IMAP) server. This permits a mail client to inject content from an IMAP server into the SMTP infrastructure without downloading it to the client and uploading it back to the server. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4468
- Published
- May 2006
- Authors
- C. Newman
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- app
- Pages
- 14
- Also known as
- —
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 4416Goals for Internet Messaging to Support Diverse Service EnvironmentsCurrent
February 2006
- RFC 5259Internet Message Access Protocol - CONVERT ExtensionCurrent
July 2008
- 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 4467Internet Message Access Protocol (IMAP) - URLAUTH ExtensionUpdated
May 2006
- RFC 5232Sieve Email Filtering: Imap4flags ExtensionCurrent
January 2008
- RFC 5255Internet Message Access Protocol InternationalizationCurrent
June 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?