RFC 1426: SMTP Service Extension for 8bit-MIMEtransport
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 1652.
Current document in this lineage: RFC 6152 — SMTP Service Extension for 8-bit MIME Transport
In plain English — editorial summary, not part of the RFC
This memo defines an extension to the SMTP service whereby an SMTP content body containing octets outside of the US ASCII octet range (hex 00-7F) may be relayed using SMTP.
Document record
- Document ID
- RFC1426
- Published
- February 1993
- Authors
- J. Klensin; N. Freed; M. Rose; E. Stefferud; D. Crocker
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- app
- Pages
- 6
- Also known as
- —
- Obsoleted by:
- RFC 1652
Topics
Standards lineage
This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.
- RFC 1426 (1993)
- RFC 1652 (1994)
- RFC 6152 (2011) ✓
Read the full history of SMTP Service Extension for 8-bit MIME Transport →
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 1425SMTP Service ExtensionsObsoleted
February 1993
- RFC 1427SMTP Service Extension for Message Size DeclarationObsoleted
February 1993
- RFC 1428Transition of Internet Mail from Just-Send-8 to 8bit-SMTP/MIMECurrent
February 1993
- RFC 1494Equivalences between 1988 X.400 and RFC-822 Message BodiesCurrent
August 1993
- RFC 1495Mapping between X.400 and RFC-822 Message BodiesObsoleted
August 1993
- RFC 1496Rules for downgrading messages from X.400/88 to X.400/84 when MIME content-types are present in the messagesCurrent
August 1993
- RFC 1502X.400 Use of Extended Character SetsCurrent
August 1993
- RFC 1523The text/enriched MIME Content-typeObsoleted
September 1993
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?