Example 18-1 configures a PMDF-X400 gateway at EXAMPLE.COM on node NAPLES, and Example 18-2 shows a corresponding checklist file. This is the same sample site pictured in Figure 4-1 and configured in Example 4-1.

In this example, EXAMPLE has added an X.400 gateway to the fictional service provider GALACTIMAIL. Prior to configuring PMDF-X400, EXAMPLE has been assigned an X.400 address consisting of:

	Country:	US
	Administrative Domain:	GALACTIMAIL
	Private Domain:	Example Corp
	Organization:	HQ

EXAMPLE and the management of the remote X.400 MTA have coordinated the use of MTA information and network addresses. They will be using X.400 1988 Normal transfer mode, and the OSI connectionless network transport (CLNS). EXAMPLE has already installed and configured DECnet/OSI, including the creation of a CLNS template which they have named CLNS. The relevant parameters on which they've agreed are:

Parameter	EXAMPLE's PMDF-X400 MTA	GALACTIMAIL's MTA
Presentation Selector:	"MTA"	"BIG"
Session Selector:	"MTA"	"BUCKS"
Transport Selector:	"PMDF-X400"	"X400"
CLNS Address:	49004008002B1DAA3F21	49004008002B1D2A5421
MTA Name:	naples	galactimail
MTA Password:		secret

Note that EXAMPLE is using an empty password string for their PMDF-X400 MTA which will be specified to PMDF-X400 using empty double-quotes. In this example, the other MTA name and password strings do not require quoting. The MTA name and password strings are case-sensitive and should be entered exactly as expected by both MTAs.

Remember that the values used in this sample are for purposes of example only. Be sure to use the values appropriate for your system when you perform the actual configuration.

Whenever appropriate, each prompt supplies a default answer which is enclosed within square brackets. Simply pressing return, [RETURN], selects the default answer. In this example configuration no answer has had to be specified to many of the prompts since the defaults are usually sufficient.

Example 18-1 Example PMDF-X400 Configuration

$ SET DEFAULT PMDF_TABLE: $ PMDF CONFIGURE X400 PMDF-X400 Configuration Utility, Version 6.2 This utility creates an initial pair of databases for mapping PMDF's 822-style addresses to X.400 addresses and back again. Only minimal mappings are created; no attempt is made to create a complete domain name to ORname mapping of the type specified in RFC1327. Note that this is a limitation of this configuration procedure only; the database is quite capable of supporting such a sophisticated mapping. Important note: No changes are made to existing PMDF-X400's database information until all questions have been answered. This utility can be aborted at any prompt by entering a CTRL/C. The files output by this utility can optionally be redirected to a different location so they will have no impact on the existing PMDF-X400 databases. Do you wish to continue [Y]? YES Do you wish to have a detailed explanation printed before each question [Y]? Y Enter the most widely used domain name that corresponds to your local host. Normally this is the official channel host name associated with PMDF's local channel. Official local host name [NAPLES.EXAMPLE.COM]? example.com A standard domain-style host name is used to refer to the gateway from the Internet/822 side. X.400 addresses then appear relative to this gateway on the Internet/822 side. For example, if you choose a domain name like X400.EXAMPLE.COM for the gateway, an address of the form /C=US/ADMD=MCI/PRMD=DEC/S=Doe/@X400.EXAMPLE.COM might be used from the Internet/822 side to send messages to an X.400 user. The choice of the X400.domain format is a common one. Be sure that the name you choose is within a domain or subdomain that you have administrative authority over. Also be sure to choose a name that is NOT currently in use. Domain name for the X.400 gateway [x400.NAPLES.EXAMPLE.COM]? x400.example.com Enter the ORname components that serve to identify messages to be processed by this MTA. User-specific fields should not be specified. ORname stem for the local PMDF MTA Enter a ISO3166 two character alphabetic country code. Country [US]? US Optionally enter an Administration Domain Name (ADMD). Administration Domain []? GALACTIMAIL Optionally enter a Private Domain Name (PRMD). Private Domain []? EXAMPLE Corp Optionally enter an Organization name (O). Organization []? HQ Optionally enter 1-4 Organization Unit names (OU). You will be prompted for each one separately; press RETURN when there are no more Organizational Units to specify. Organizational Unit []? [RETURN] Enter the Presentation Address that PMDF-X400 should use to receive incoming X.400 RTS network connections. You should supply a Presentation Selector, PSEL, Session Selector, SSEL, and Transport Selector, TSEL. Do not enter your Network Service Access Point, or NSAP, address as that will be determined automatically. Transport level connection requests to the TSEL you provide here will be directed to PMDF-X400. In addition, you will need to provide remote MTAs with these selectors as well as your Network Server Access Point, or NSAP, before they will be able to initiate connections to PMDF-X400. Hit RETURN for more: [RETURN] Supported Selector formats are: Type Syntax Example ------------ --------------------------- ----------- string "<printable-string>" "PMDF-X400" numeric #<decimal-number> #591 octet-stream '<hexadecimal-byte-string>'H '353931'H You must enter all three selectors, and you must separate them with / characters, in the order: PSEL / SSEL / TSEL For example: "MTA"/"MTA"/"PMDF-X400" Presentation Address for PMDF-X400 ["MTA"/"MTA"/"PMDF-X400"]? [RETURN] Answer YES if PMDF-X400 should be configured for network communications over the OSI lower layers using DECnet OSI. Configure PMDF-X400 for OSI transport stack [Y]? [RETURN] Answer YES if PMDF-X400 should be configured for network communications over the TCP/IP lower layers in accordance with RFC1006. Configure PMDF-X400 for TCP/IP transport stack [Y]? NO You will now be asked to provide the information required to set up connections to a single remote MTA. This configuration procedure currently only generates configurations that connect to a single remote MTA. Configurations that connect to multiple MTAs are supported but must be built manually. MTA connection information... Enter the X.400 Transfer Mode to be used with this MTA. Valid responses are 1988-NORMAL, 1988-X410, and 1984. If 1984 is chosen, messages will be downgraded to 1984 X.400 and 1984 Reliable Transfer Service will be used. If 1988-X410 is chosen, messages will comply with 1988 X.400, but 1984 RTS will be used. If 1988-NORMAL is chosen, messages will comply with 1988 X.400 and 1988 RTSE. Transfer mode for this MTA [1988-NORMAL]? [RETURN] Enter the Presentation Address that's used to identify the local system when connecting to the remote MTA. You should use the default provided unless the remote MTA specifically requires some other address. Do not enter the Network Service Access Point, or NSAP, address at this point, enter only the selector portion of the address. Note that if 1984 or 1988-X410 transfer mode has been chosen, only the Transport Selector, TSEL, is used here. Local MTA address ["MTA"/"MTA"/"PMDF-X400"]? [RETURN] Enter the MTA name that your system should use to identify itself when connecting to the remote MTA. This string is transferred as part of connection setup. Local MTA name []? naples Enter the password that your system should use to identify itself when connecting to the remote MTA. This string is transferred as part of connection setup. Local MTA password []? "" Enter the complete Presentation Address associated with the remote MTA. PMDF-X400 will connect to this address when transferring messages to the remote MTA. If using 1984 or 1988-X410 transfer modes, then you must enter only a single Transport Selector, or TSEL. If using 1988-NORMAL mode you must enter all three selectors, and you must separate them with / characters. Finally, you must also include the Network Service Access Point, or NSAP for the remote MTA. Separate the NSAP from the selectors using a / character, in the order: PSEL / SSEL / TSEL / NSAP Some examples: 1984 RFC-1006 (TCP): "X400"/Internet=111.222.3.4 1984 CONS (X.25) : "X400"/Int-X25=0113123450 1984 CLNS : "X400"/NSAP=49004008002B1D161521 1988 RFC-1006 (TCP): "MTA"/"MTA"/"X400"/Internet=111.222.3.4 1988 CONS (X.25) : "MTA"/"MTA"/"X400"/Int-X25=0113123450 1988 CLNS : "MTA"/"MTA"/"X400"/NSAP=49004008002B1D161521 Remote MTA address []? "BIG"/"BUCKS"/"X400"/NSAP=49004008002B1D2A5421 Enter the name of the DECnet/OSI Transport template that is to be used for this connection. You will need to define the template using the NCL command "CREATE OSI TRANSPORT TEMPLATE" followed by the template name. You might also be required to set template parameters using the NCL command "SET OSI TRANSPORT TEMPLATE". DECnet/OSI Transport template [PMDF-CLNS]? [RETURN] Enter the MTA name that you expect the remote MTA to return. This string is transferred as part of connection setup. Remote MTA name []? galactimail Enter the password that you expect the remote MTA to return. This string is transferred as part of connection setup. Remote MTA password []? secret The PMDF address of the local PostMaster is used when blank addresses (which are allowed in RFC822 but not in X.400) are encountered that must be converted into X.400 addresses. Please enter a full domain address for the local PostMaster. Do not use shortform host names since there is no guarantee that the address will be interpreted in the context where the shortform name is valid. RFC822 address of local PostMaster []? system@example.com Enter the name of the file to which the text form of the PMDF to X.400 mapping should be written. This file will be created automatically by this configuration procedure. Any old versions of the file will be superseded. PMDF to X.400 mapping text file [PMDF_ROOT:[TABLE]TO_X400.TXT]? [RETURN] Enter the name of the file to which the text form of the X.400 to PMDF mapping should be written. This file will be created automatically by this configuration procedure. Any old versions of the file will be superseded. X.400 to PMDF mapping text file [PMDF_ROOT:[TABLE]FROM_X400.TXT]? [RETURN] This procedure generates an options file that contains X.400 connection information, addresses, MTA names, and passwords. This file is read by the gateway as it initializes and provides the information needed to establish connections to a remote X.400 MTA. WARNING: This file contains password information and should be protected against world read access! Gateway options file [PMDF_ROOT:[TABLE]X400_LOCAL_OPTION.]? [RETURN] Enter the name of the file to contain the database form of the PMDF to X.400 mapping. This file will be created automatically by this configuration procedure. Any old versions of the file will be superseded. This file name must agree with the TO_X400_DATABASE channel option or with the PMDF_TO_X400_DATABASE logical name for it to be actually used by the gateway. PMDF to X.400 mapping database [PMDF_ROOT:[TABLE]TO_X400.DAT]? [RETURN] Enter the name of the file to contain the database form of the X.400 to PMDF mapping. This file will be created automatically by this configuration procedure. Any old versions of the file will be superseded. This file name must agree with the FROM_X400_DATABASE channel option or with the PMDF_FROM_X400_DATABASE logical name for it to be actually used by the gateway. X.400 to PMDF mapping database [PMDF_ROOT:[TABLE]FROM_X400.DAT]? [RETURN] Enter the name of the file to contain the PMDF configuration rewrite rules created by this procedure. This file should subsequently be included in your PMDF configuration file. Rewrite rules text file [PMDF_ROOT:[TABLE]X400.RULES]? [RETURN] Enter the name of the file to contain the channel block definition for the PMDF-X400 channels. This file will be created automatically by this configuration procedure. Any old versions of the file will be superseded. Channel definitions text file [PMDF_ROOT:[TABLE]X400.CHANS]? [RETURN] PMDF-X400 requires the presence of an ISOENTITIES file. This procedure will create the appropriate file. PMDF-X400 ISOENTITIES file name [PMDF_ROOT:[TABLE]ISOENTITIES.]? [RETURN] PMDF-X400 requires the presence of an ISOMACROS file. This procedure will create the appropriate file. PMDF-X400 ISOMACROS file name [PMDF_ROOT:[TABLE]ISOMACROS.]? [RETURN] PMDF-X400 requires the presence of an ISOTAILOR file. This procedure will create the appropriate file. PMDF-X400 ISOTAILOR file name [PMDF_ROOT:[TABLE]ISOTAILOR.]? [RETURN] PMDF-X400 requires the presence of an NCL service definitions file. This procedure will create the appropriate file. PMDF-X400 NCL service definitions file name [PMDF_ROOT:[TABLE]PMDF_X400_SERVICE. NCL]? [RETURN] This procedure generates a checklist file that contains the list of actions you must perform in order to make the PMDF-X400 gateway operational. This procedure does *NOT* perform these operations itself; you must do them manually. PMDF-X400 checklist file name [PMDF_ROOT:[TABLE]X400.CHECKLIST]? [RETURN] All configuration questions have been answered. This question gives you a last chance to change your mind before any files are written. Answer NO if you are not sure you want to generate the configuration you have specified. Answer YES if you do. Do you wish to generate the configuration files [Y]? YES Generating PMDF to X.400 mapping text file... PMDF to X400 mapping text file is complete. Generating X400 to PMDF mapping text file... X.400 to PMDF mapping text file is complete. Generating the X400.RULES file... X400.RULES file is complete. Generating the X400.CHANS file... X400.CHANS file is complete. Generating the ISOENTITIES file... ISOENTITIES file is complete. Generating the ISOMACROS file... ISOMACROS file is complete. Generating the ISOTAILOR file... ISOTAILOR file is complete. Generating the NCL service definitions file... NCL service definitions file is complete. Generating the setup checklist... Checklist file is complete. Converting the PMDF to X.400 mapping text file to a database... Entries converted: 21 Exceptions generated: 0 Entries too long to fit: 0 PMDF to X.400 mapping conversion is complete. Converting the X.400 to PMDF mapping text file to a database... Entries converted: 108 Exceptions generated: 0 Entries too long to fit: 0 X.400 to PMDF mapping conversion is complete. Generating options file... Options file is complete. *********************************************************************** * * To complete your PMDF-X400 configuration, carry out the steps * detailed in the setup checklist PMDF_ROOT:[TABLE]X400.CHECKLIST;. * *********************************************************************** Enter Yes if you want to see the checklist now. You can still type the file out later if you say No. Do you want to see the checklist now [Y]? n $

Example 18-2 Example Checklist File for PMDF-X400 Configuration

$ TYPE x400.checklist Checklist for setting up your PMDF-X400 gateway. Written by SYSTEM, 1-NOV-2002 17:58 This file was created by the PMDF-X400 configuration generator V6.2. (1) The rewrite rules for PMDF-X400 have been written out to a file. You can simply include this file in your configuration by adding the line <PMDF_TABLE:X400.RULES to the rewrite rules section of your pmdf.cnf file; it should be be added before any general TCP/IP rewrite rules (e.g., .COM, .EDU, etc.). Note: You can find the lines ! ! Rewrite rules for PMDF-X400 ! !<PMDF_TABLE:X400.RULES around the middle of your PMDF.CNF file. In this case, merely uncomment the line "!<PMDF_TABLE:X400.RULES" and, if necessary, change the file name so that it reads ! ! Rewrite rules for PMDF-X400 ! <PMDF_TABLE:X400.RULES (2) The channel definitions for PMDF-X400 have been written out to a file. You can simply include this file in your configuration by adding the line <PMDF_TABLE:X400.CHANS to the very end of your PMDF.CNF file; it should be preceded by a single blank line. Note: You can find the lines ! ! PMDF-X400 channels ! !<PMDF_TABLE:X400.CHANS towards the end of your PMDF.CNF file. In this case, merely uncomment the "!<PMDF_TABLE:X400.CHANS" line and, if necessary, change the file name so that it reads ! ! PMDF-X400 channels ! <PMDF_TABLE:X400.CHANS (2) The channel definitions for PMDF-X400 have been written out to a file. You can simply include this file in your configuration by adding the line <PMDF_TABLE:X400.CHANS to the very end of your PMDF.CNF file; it should be preceded by a single blank line. Note: You can find the lines ! ! PMDF-X400 channels ! !<PMDF_TABLE:X400.CHANS towards the end of your PMDF.CNF file. In this case, merely uncomment the "!<PMDF_TABLE:X400.CHANS" line and, if necessary, change the file name so that it reads ! ! PMDF-X400 channels ! <PMDF_TABLE:X400.CHANS (3) Ensure that the DECnet/OSI Transport template PMDF-CLNS is properly defined in the file: PMDF_TABLE:PMDF_X400_SERVICE.NCL This procedure has included the necessary NCL commands to create the template with the supplied name and default characteristics. (4) Configure the OSI Transport for incoming X.400 connections by defining the OSI Transport Application using the command: $ MCR NCL @PMDF_ROOT:[TABLE]PMDF_X400_SERVICE.NCL; You also need to add this command to your system startup procedures to ensure that incoming X.400 network connections are dispatched to PMDF-X400 after system initialization. Make sure that the NCL command is executed after PMDF_STARTUP.COM and after DECnet/OSI has started. (5) PMDF-X400 is capable of converting between various types of X.400 body parts (attachments) and MIME attachment types. You should consider enabling such attachment handling. Sample mappings can be found in the file PMDF_TABLE:X400_MAPPINGS.SAMPLE. To enable these mappings, paste the contents of the sample file into the PMDF_TABLE:MAPPINGS. file. That's all! $