metasystema.org
ObsoletedLegacy stream

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

The X.400 series protocols have been defined by CCITT to provide an Interpersonal Messaging Service (IPMS), making use of a store and forward Message Transfer Service. It is expected that this standard will be implemented very widely. This document describes a set of mappings which will enable interworking between systems operating the X.400 protocols and systems using RFC-822 mail protocol or protocols derived from RFC-822. This RFC suggests a proposed protocol for the ARPA-Internet community, and requests discussion and suggestions for improvements.

Document record

Document ID
RFC987
Published
June 1986
Authors
S.E. Kille
Status
UNKNOWN
Stream
Legacy
Area
—
Pages
69
Also known as
—
Obsoleted by:
RFC 1327, RFC 2156
Updated by:
RFC 1026, RFC 1138, RFC 1148

Standards lineage

This document is one revision in a chain of 7 RFCs, each formally replacing the one before it.

  1. RFC 987 (1986)
  2. RFC 1026 (1987)
  3. RFC 1138 (1989)
  4. RFC 1148 (1990)
  5. RFC 1327 (1992)
  6. RFC 1495 (1993)
  7. RFC 2156 (1998) ✓

Read the full history of MIXER (Mime Internet X.400 Enhanced Relay): Mapping between X.400 and RFC 822/MIME →

Referenced by

5 later RFCs formally update or obsolete part of this document.

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?

canonical URL: /rfc/987-mapping-between-x-400-and-rfc-822