RFC 1830: SMTP Service Extensions for Transmission of Large and Binary MIME Messages
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 3030.
Current version: RFC 3030 — SMTP Service Extensions for Transmission of Large and Binary MIME Messages
In plain English — editorial summary, not part of the RFC
This memo defines two extensions to the SMTP service. The first service enables a SMTP client and server to negotiate the use of an alternate DATA command "BDAT" for efficiently sending large MIME messages. The second extension takes advantage of the BDAT command to permit the negotiated sending of unencoded binary data. This memo defines an Experimental Protocol for the Internet community.
Document record
- Document ID
- RFC1830
- Published
- August 1995
- Authors
- G. Vaudreuil
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- app
- Pages
- 8
- Also known as
- —
- Obsoleted by:
- RFC 3030
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 2156MIXER (Mime Internet X.400 Enhanced Relay): Mapping between X.400 and RFC 822/MIMECurrent
January 1998
- RFC 2442The Batch SMTP Media TypeCurrent
November 1998
- RFC 2936HTTP MIME Type Handler DetectionCurrent
September 2000
- RFC 1844Multimedia E-mail (MIME) User Agent ChecklistCurrent
August 1995
- RFC 1845SMTP Service Extension for Checkpoint/RestartCurrent
September 1995
- RFC 1846SMTP 521 Reply CodeUpdated
September 1995
- RFC 1867Form-based File Upload in HTMLObsoleted
November 1995
- RFC 1869SMTP Service ExtensionsObsoleted
November 1995
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?