The information in this article applies to:
SUMMARYThe MIME Internet X.400 Enhanced Relay (MIXER) (RFC 2156) does not provide any specifications for mapping variations in user names. Consequently, it is important to understand the limitations of using the address mapping scheme. MORE INFORMATIONWhen the MIXER maps an SMTP address to an X.400 address, the user name mapping is as follows: Case 1:When the MIXER maps an X.400 address to an SMTP address, the user name mapping is as follows:SMTP address is name@domainCase 2: Case 1:In most Exchange Server topologies, the SMTP address for users is the Exchange Server default, which is alias@domain. If the MIXER mapping strategy is in use in this environment, the SMTP-to-X.400 mapping works only if all X.400 addresses are in the following form:X.400 address is s=lastnameCase 2: X.400:c=country;a=admd;p=prmd;o=org;s=aliasThis is possible only if the administrator does not populate First Name and Last Name fields during mailbox creation. The administrator can also populate the Last Name field with the alias, if necessary. The reverse of this problem is also true if the administrator wants to provide X.400-to-SMTP mapping. If, as mentioned above, the administrator has populated the First Name and Last Name fields at mailbox creation, the X.400 address is in the following form: X.400:c=country;a=admd;p=prmd;o=org;s=LastName;g=FirstNameThe translated SMTP address in this case renders as: FirstName.LastName@domainThis mapping does not work if the default SMTP addressing scheme of alias@domain is being used in this environment. Additional query words: MIXER RFC2156
Keywords : exc55sp3 |
Last Reviewed: September 14, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |