metasystema.org
ObsoletedPROPOSED STANDARDIETF stream

RFC 1495: Mapping between X.400 and RFC-822 Message Bodies

This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by 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

Since the introduction of X.400(84), there has been work ongoing for defining mappings between MHS and RFC-822. The most recent work in this area is RFC-1327 [3], which focuses primarily on translation of envelope and headers. This document is complimentary to RFC-1327 as it focuses on translation of the message body. [STANDARDS-TRACK]

Document record

Document ID
RFC1495
Published
August 1993
Authors
H. Alvestrand; S. Kille; R. Miles; M. Rose; S. Thompson
Status
PROPOSED STANDARD
Stream
IETF
Area
app
Pages
11
Also known as
—
Obsoleted by:
RFC 2156
Updates:
RFC 1327

Topics

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

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.

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/1495-mapping-between-x-400-and-rfc-822-message-bodies