RFC 2157: Mapping between X.400 and RFC-822/MIME Message Bodies

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…

Read RFC 2157 on the RFC Editor

Outgoing relationships (15 related RFCs)

Informative reference — RFC 2119: Key words for use in RFCs to Indicate Requirement Levels
Informative reference — RFC 822: STANDARD FOR THE FORMAT OF ARPA INTERNET TEXT MESSAGES
Informative reference — RFC 2046: Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types
Informative reference — RFC 2047: MIME (Multipurpose Internet Mail Extensions) Part Three: Message Header Extensions for Non-ASCII Text
Informative reference — RFC 1327: Mapping between X.400(1988) / ISO 10021 and RFC 822
Informative reference — RFC 1806: Communicating Presentation Information in Internet Messages: The Content-Disposition Header
Informative reference — RFC 1468: Japanese Character Encoding for Internet Messages
Informative reference — RFC 1494: Equivalences between 1988 X.400 and RFC-822 Message Bodies
Informative reference — RFC 1502: X.400 Use of Extended Character Sets
Informative reference — RFC 1428: Transition of Internet Mail from Just-Send-8 to 8bit-SMTP/MIME
Informative reference — RFC 1496: Rules for downgrading messages from X.400/88 to X.400/84 when MIME content-types are present in the messages
Informative reference — RFC 1495: Mapping between X.400 and RFC-822 Message Bodies
Informative reference — RFC 2158: X.400 Image Body Parts
Informative reference — RFC 2160: Carrying PostScript in X.400 and MIME
Informative reference — RFC 2161: A MIME Body Part for ODA