RFC 2162 (rfc2162) - Page 3 of 34
MaXIM-11 - Mapping between X
Alternative Format: Original Text Document
RFC 2162 MaXIM-11 January 1998
This document also covers the case of Mail-11 systems implementing
the "foreign mail protocol" allowing Mail-11 to interface other mail
systems, including RFC 822 based system.
Chapter 2 - Message Elements
2.1. Service Elements
Mail-11 protocol offers a very restricted set of elements composing a
Inter Personal Message (IPM), whereas X.400 and RFC 822/MIME
specifications support a complex and large amount of service
elements. Considering the case where a message is relayed between
two X.400 MHS or MIME Message Transport System (MTS) via a Mail-11
messaging system this could result in a nearly complete loss of
information.
To minimise the inconvenience, any of the X.400 or MIME service
elements which do not map directly into Mail-11 equivalent ones
accordingly to this specification, will be included into Mail-11 text
body parts as an additional RFC 822-like header; this additional
header will be inserted between the Mail-11 P2 headers (From:, To:,
CC:, Subj:) and the other Mail-11 bodyparts. In particular, X.400
elements will also be at first converted into textual representation
before insertion.
An example, where a multimedia message has been encoded into mail-11
after having crossed also a MIME-MHS (MIXER conformant) gateway:
From: smtp%"" "Erik" 18-OCT-1994 13:55:00.49
To: ALLOCCHIO
CC: smtp%""
Subj: enjoy this nice picture!
X400-Originator:
X400-Recipients: ,
Sender: Erik Newmann [email protected]>
Organisation: SURFnet bv
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="----- =_aaaaaa0"
Content-ID: [email protected]>
------- =_aaaaaa0
Content-Type: text/plain; charset="us-ascii"
Content-ID: [email protected]>
look... you never saw this one!!
I just include the picture in the next bodypart
and I hope you get it fine.
Allocchio Experimental
