| Concepts and Planning | << | >> |
|---|
A management domain is a set of messaging systems managed by an organization that contains at least one MTA. The management domain is divided into two parts: an administrative management domain (ADMD) and a private management domain (PRMD).
An ADMD is managed by a public service provider and is the highest level management domain that transmits third-party message traffic. The service is usually provided by a telephone carrier such as Sprint, AT&T, or British Telecom.
A PRMD is a network owned by a private company. PRMDs can communicate with ADMDs and other PRMDs but are not permitted to relay messages between PRMDs.
The ADMD and PRMD structure is similar to that of the telephone system. An ADMD can be compared with a telephone carrier that provides your phone service. The service is leased from the ADMD in the form of a PRMD. This is similar to the way in which a telephone line is assigned. The PRMD has a unique network address that can have multiple users.
Users of an MTS are identified by an O/R name. The O/R name is included on the P1 envelope and is used by the MTS to route and deliver messages.
Microsoft Exchange Server automatically creates X.400 addresses for every mailbox based on the site and organization name you specify during Setup. It is important to understand the elements of O/R addresses to modify the site address, create custom-recipient addresses, and specify the addresses of other X.400 systems in the X.400 Connector configuration.
The O/R address consists of required and optional fields containing attributes and values. The attributes necessary for a valid address vary depending on the recipient system. Not all attributes are required for delivery in an X.400 system. After the correct attributes are identified, the attribute and its value are combined in an address format with an equal sign (=) separating the two. A delimiter is added between fields for parsing. X.400 fields can be separated by a semicolon (;) or a slash (/). Different systems can require different delimiters.
You can use either the abbreviation or the label to identify an attribute. The following table shows valid abbreviations and labels, as well as the maximum length allowed for the value. The domain-defined attribute (DDA) field is case sensitive; the other attributes are not.
| Attribute Type | Abbreviation | Label | Maximum Characters |
|---|---|---|---|
| Given name | Given name | G | 16 |
| Initials | Initials | I | 5 |
| Surname | Surname | S | 40 |
| Generation qualifier | Generation | Q | 3 |
| Common name | Common name | CN | 32 |
| X.121 address | X.121 | X.121 | 15 |
| User agent numeric ID | N-ID | N-ID | 32 |
| Terminal type | T-TY | T-TY | 3 |
| Terminal identifier | T-ID | T-ID | 24 |
| Organization | Organization | O | 64 |
| Organizational unit 1 | Org.Unit.1 | OU1 | 32 |
| Organizational unit 2 | Org.Unit.2 | OU2 | 32 |
| Organizational unit 3 | Org.Unit.3 | OU3 | 32 |
| Organizational unit 4 | Org.Unit.4 | OU4 | 32 |
| Private management domain name | PRMD | P | 16 |
| Administrative management domain name | ADMD | A | 16 |
| Country | Country | C | 2 |
| Domain-defined attribute | DDA | DDA | 8,128 |
DDA uses the format DDA:type=value; for example, DDA:SMTP=MariaBlack@fab.com. There may be up to four DDAs in a single X.400 address. DDAs are order dependent. When parsing from left to right, the first DDA is encoded first, the second DDA is encoded second, and so on.
With the exception of DDA, the format for the fields is Label=Value; for example, g=Joe.
The following are examples of valid X.400 addresses using labels and different delimiters:
An X.400 address is created by providing the value for all required attributes and any optional attributes until a unique address is formed. 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 Operations.
Microsoft Exchange Server uses the X.400 global domain identifier in a relay environment. The global domain identifier consists 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 global domain identifier used for Microsoft Exchange Server is the same as the global domain identifier of a connected foreign system.