An X.400 address is composed by providing the value for all required attributes and any optional attributes until a unique address is created. The following table illustrates the required and optional attributes that can be used to create a mnemonic X.400 address with Microsoft Exchange Server. All attribute values can contain numeric or alphanumeric characters.
Attribute | Comments |
Personal name | Includes Given Name, Initials, Surname, and Generation. If the Personal Name attributes are used, the Surname is required. |
Common name | Optional |
Organization | Optional |
Organizational units | Optional |
PRMD | Optional |
ADMD | Required. A single blank character can be used in the ADMD field to indicate that no ADMD is specified. |
Country | Required |
DDAs | Optional |
Note
At least one of the Personal Name, Common Name, Organization, Organizational Units, or PRMD attributes must be used in addition to ADMD and Country. If a DDA is used, you still must specify one of the other optional fields.
Microsoft Exchange Server can use X.121 addresses in the X.400 environment. X.121 is a standard universal addressing scheme for public data networks. The following table illustrates the required and optional attributes that can be used to create an X.121 address with Microsoft Exchange Server. All attribute values can contain numeric or alphanumeric characters.
Attribute | Comments |
X.121 address | Required |
PRMD | Required only for 1988 X.400 compatibility. |
ADMD | Required. A single blank character can be used in the ADMD field to indicate that no ADMD is specified. |
Country | Required |
DDAs | Optional |
For more information about X.400 address attributes, see Microsoft Exchange Server Administrator's Guide.
Microsoft Exchange Server uses the X.400 global domain identifier (GDI) in a relay environment. The GDI is comprised of the country, ADMD, and PRMD name of the remote MTA. It is used for inserting trace elements and can be used for troubleshooting an unsuccessful relay attempt. It is also used to prevent message looping in wide-area messaging environments.
If you are using a public X.400 network as a backbone between two Microsoft Exchange Servers, messages may not be routed correctly if the GDI used for Microsoft Exchange Server is the same as the GDI of a connected foreign system.