PMDF System Manager's Guide

The MTA identification is meaningful only to the local PMDF-X400 configuration and only used when configuring for multiple MTA support. The MTA identification is only used to locate the necessary MTA information in the MTAID database. It is located via the logical name PMDF_X400_MTAID_DATABASE (OpenVMS) or the PMDF tailor file option PMDF_X400_MTAID_DATABASE (UNIX), and hence is normally the file x400-mtaid.dat located in the PMDF table directory.

The MTAID database is a standard PMDF CRDB (OpenVMS) or pmdf crdb (UNIX) format database. It is maintained as an editable text file which is converted into the database for use by PMDF-X400 using the OpenVMS command:

$ PMDF CRDB/DUPLICATE/LONG/QUOTED/REMOVE x400-mtaid.txt x400-mtaid.dat

or the UNIX command

# pmdf crdb -duplicates -long_records -quoted -remove x400-mtaid.txt x400-mtaid

The MTAID database consists of two sections. Each section consists of entries which contain a key on the left-hand-side and a value for the key on the right-hand-side. One section contains the MTA identification used in the X400-ORNAME-TO-MTAID mapping as the key. The value information for each MTAID key lists all of the configuration information required by the X400_LOCAL channel to establish a connection to the MTA. Each channel option specifies a value and is separated from the next option by a semicolon, ;. The information provided for each MTAID is the same as that provided in the x400_local_option file under a single-MTA configuration and is used by the X400_LOCAL channel to make an outgoing RTSE connection to the specified remote MTA.

The other section is the inverse information. Options and values are used on the left-hand-side as a key while the right-hand-side contains the corresponding MTAID. This section is used by X400_LOCAL to identify the MTA on an incoming connection based on the remote Presentation or Transport address and MTA name.

As database records used with X400-MTAID can be complex, careful formatting and use of the backslash, \, character for line continuation is recommended. Note that apparently minor format errors in the text format can render the database useless.

An example file x400-mtaid.txt for the three-MTA configuration used above is shown in Example 41-2.

Example 41-2 Sample X.400 MTA Information Database

! x400-mtaid.txt - X.400 MTA definitions ! !----------------------------------------------------------------------- ! Master rules supply outgoing connection information based on the ! MTA ID associated with this connection. The MTA ID was determined ! from the recipient name through the X400-ORNAME-TO-MTAID mapping ! in the MAPPINGS file. ! TELEMAIL LOCAL_MTANAME = "spacely"; LOCAL_PASSWORD = "vms"; \ LOCAL_ADDR = "PMDF-X400" ; \ REMOTE_MTANAME = "telemail" ; REMOTE_PASSWORD = "costs"; \ REMOTE_ADDR = "X400-MRX"/Int-X25=12345678 ; \ TEMPLATE=CONS ; \ MODE = 1988-X410 ! UNIX-PP LOCAL_MTANAME = "spacely"; LOCAL_PASSWORD = "vms"; \ LOCAL_ADDR = "PMDF-X400" ; \ REMOTE_MTANAME = "unix" ; REMOTE_PASSWORD = " "; \ REMOTE_ADDR = "591"/Internet=unix.spacely.com ; \ MODE = 1988-NORMAL ! MSEX LOCAL_MTANAME = "spacely"; LOCAL_PASSWORD = "vms"; \ LOCAL_ADDR = "PMDF-X400" ; \ REMOTE_MTANAME = "pclan" ; REMOTE_PASSWORD = "ntbox"; \ REMOTE_ADDR = "X400"/NSAP=49004008002B1D6A1F21 ; \ TEMPLATE=CLNS ; \ MODE = 1984 ! !----------------------------------------------------------------------- ! ! Slave rules handle incoming connection information. Probe is based ! on REMOTE_ADDR and REMOTE_MTANAME. Supply MTAID which will then ! be looked up in the above section in order to get corresponding ! parameters. ! REMOTE_ADDR=*;REMOTE_MTANAME=telemail; TELEMAIL ! REMOTE_ADDR=*;REMOTE_MTANAME=unix; UNIX-PP ! REMOTE_ADDR="X400"/49004008002B1D6A1F21;REMOTE_MTANAME=pclan; MSEX

So that you can copy and modify the template for your own configuration, this sample X.400 MTAID database is provided in the file x400-mtaid.template located in the PMDF table directory