Previous | Contents | Index |
The name of the mapping table used for X.400 routing is
X400-ORNAME-TO-MTAID
. A wildcard pattern is applied to the
ORname and if it matches, the MTAID specified by the mapping is used to
identify the MTA to which the message will be transferred.
For example, the following mapping defines patterns for identifying three separate remote MTAs based on recipient ORname:
X400-ORNAME-TO-MTAID */O=Spacely$ Sprockets/OU=Finance/* MSEX */O=Spacely$ Sprockets/OU=Engineering/* UNIX-PP /C=US/ADMD=TELEMAIL/* TELEMAIL |
/O=Spacely
Sprockets/OU=Finance/
will be directed to the MTA for which
we've chosen to use the MTA identification MSEX
. Similarly
/O=Spacely Sprockets/OU=Engineering/
will be directed to
UNIX-PP
. Finally, any ORname beginning with
/C=US/ADMD=TELEMAIL/
will be directed to the MTA we
identify as TELEMAIL
.
Note that the presence of a space character in some of the ORname fields in the pattern required the use of the $ quoting character, as required by the mapping file.
The actual MTA identifiers, e.g. MSEX, UNIX-PP, and TELEMAIL, are arbitrary names that you assign. They can contain up to 32 characters consisting of upper-case alphanumerics plus "-" and "_". The only requirement on these names is that they match entries you create in the MTA Information database, described below. The MTA identifiers are only used to associate MTA connection information, in the MTA information database, with portions of ORnames so that PMDF-X400 can route based on ORname to the appropriate MTA.
Previous | Next | Contents | Index |