RFC 1026: Addendum to RFC 987: (Mapping between X.400 and RFC-822)
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 1327, RFC 2156.
Current document in this lineage: RFC 2156 — MIXER (Mime Internet X.400 Enhanced Relay): Mapping between X.400 and RFC 822/MIME
In plain English — editorial summary, not part of the RFC
This memo suggest a proposed protocol for the Internet community, and request discussion and suggestions for improvements.
Document record
- Document ID
- RFC1026
- Published
- September 1987
- Authors
- S.E. Kille
- Status
- UNKNOWN
- Stream
- Legacy
- Area
- —
- Pages
- 4
- Also known as
- —
- Updates:
- RFC 987
Standards lineage
This document is one revision in a chain of 7 RFCs, each formally replacing the one before it.
Referenced by
4 later RFCs formally update or obsolete part of this document.
- RFC 1138Mapping between X.400(1988) / ISO 10021 and RFC 822Obsoleted
December 1989
- RFC 1148Mapping between X.400(1988) / ISO 10021 and RFC 822Obsoleted
March 1990
- RFC 1327Mapping between X.400(1988) / ISO 10021 and RFC 822Obsoleted
May 1992
- RFC 2156MIXER (Mime Internet X.400 Enhanced Relay): Mapping between X.400 and RFC 822/MIMECurrent
January 1998
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?