RFC 2157: Mapping between X.400 and RFC-822/MIME Message Bodies
In plain English — editorial summary, not part of the RFC
This document defines how to map body parts of X.400 messages into MIME entities and vice versa, including the handling of multipart messages and forwarded messages. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2157
- Published
- January 1998
- Authors
- H. Alvestrand
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- app
- Pages
- 49
- Also known as
- —
Topics
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 2158X.400 Image Body PartsCurrent
January 1998
- RFC 2159A MIME Body Part for FAXCurrent
January 1998
- RFC 2160Carrying PostScript in X.400 and MIMECurrent
January 1998
- RFC 2161A MIME Body Part for ODACurrent
January 1998
- RFC 2162MaXIM-11 - Mapping between X.400 / Internet mail and Mail-11 mailCurrent
January 1998
- RFC 2163Using the Internet DNS to Distribute MIXER Conformant Global Address Mapping (MCGAM)Updated
January 1998
- RFC 2112The MIME Multipart/Related Content-typeObsoleted
March 1997
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?