RFC 2156:MIXER (Mime Internet X.400 Enhanced Relay...
RFC-Ref

Addressing


Click on the red underlined text to get to the source

... protocol elements. 4. Addressing - This considers the mapping between X.400 OR ...


... Addressing and Message IDs ...
... Addressing is the most complex aspect of X.400 <-> RFC 822std11(-> 2822prop) gateway ...
... global equivalence between X.400 and RFC 822std11(-> 2822prop) addressing. To meet user needs to the extent possible, this specification provides for equivalence where there is sufficient co-operation. To be useful, ...
... gateway. Because of third party addressing, a MIXER gateway will work best with the ...
... 822std11(-> 2822prop) nodes below this point, and addressing is managed in a manner which ensures the equivalence. The rules to achieve this are defined by MIXER ...
... 822std11(-> 2822prop) local system, which does not use global addressing), then it may choose a private domain defined attribute, different to "RFC-822". An RFC 1327(-> 2156prop) ...


... mapped to a single recipient that has a free from name "BCC" and no other addressing information. This alternate treatment is allowed because some X.400 systems cannot handle a zero lenght ...


... 987(-> 2156prop | 1327(-> 2156prop)). 4. Addressing - Support for new addressing ...
... Addressing - Support for new addressing attributes - The message ID ...


... object identifier is changed slightly 3. Addressing - A global mapping of domain ...


... 822std11(-> 2822prop) four year dates. 4. Addressing - Replaced the mandatory global address mapping ...



Google
Web
RFC-Ref