Example 14-1 shows a sample PMDF-MB400 configuration dialogue using the PMDF CONFIGURE MB400 utility, and Example 14-2 shows a corresponding sample checklist file. The sample site EXAMPLE.COM is as described in Chapter 4 with the addition of a PMDF-MB400 gateway on the NAPLES system. PMDF-MB400 has been installed on node NAPLES, and the configuration is being performed on NAPLES.

Whenever appropriate, each prompt also supplies a default answer which is enclosed within square brackets. (If you have previously run the PMDF CONFIGURE MB400 utility, you will be asked whether or not CONFIGURE should present your previous answers as the default answers; in the sample dialogue shown below, the PMDF CONFIGURE MB400 utility had been run previously, but we choose not to be reminded of those previous answers.) Simply pressing return, [RETURN], selects the default answer.

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

Example 14-1 Example PMDF-MB400 Configuration

$ SET DEFAULT PMDF_TABLE: $ PMDF CONFIGURE MB400 PMDF-MB400 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-MB400'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-MB400 databases. You have a history file from a previous run of the configure utility. Do you want to use answers from the previous run as defaults [N]? n Do you wish to continue [Y]? y 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.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 []? R and D 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 []? Widgets Organizational Unit []? [RETURN] PMDF-MB400 connects to MAILbus 400 using a particular client name. This name must match the name configured into MAILbus 400. Be sure to choose a name that is NOT currently in use. MAILBus 400 client name [PMDF-MB400]? PMDF-MB400 PMDF-MB400 uses the XAPI interface to connect to your MAILbus 400 MTA. XAPI allows for the MAILbus 400 MTA to be colocated with PMDF-MB400 on the same system, or remote from PMDF-MB400 across a suitable network connection. If your MAILbus 400 MTA is colocated with this PMDF-MB400 on the same system, then answer YES to this question, otherwise answer NO. Is the MAILbus 400 MTA running on the same system as PMDF-MB400 [Y]? y 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_TABLE:TO_MB400.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_TABLE:FROM_MB400.TXT]? [RETURN] This procedure generates an options file that contains the client name and other information needed to connect to MAILBus 400. Gateway options file [PMDF_TABLE:XAPI_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_TABLE:TO_MB400.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_TABLE:FROM_MB400.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_TABLE:MB400.RULES]? [RETURN] Enter the name of the file to contain the channel block definition for the PMDF-MB400 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_TABLE:MB400.CHANS]? [RETURN] This procedure generates a checklist file that contains the list of actions you must perform in order to make the PMDF-MB400 gateway operational. This procedure does *NOT* perform these operations itself; you must do them manually. PMDF-MB400 checklist file name [PMDF_TABLE:MB400.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]? y 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 rewrite rules file... Rewrite rules file is complete. Generating the channel definitions file... Channel 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-MB400 configuration, carry out the steps * detailed in the setup checklist PMDF_TABLE:MB400.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 14-2 Example Checklist File for PMDF-MB400 Configuration

$ TYPE PMDF_TABLE:mb400.checklist Checklist for setting up your PMDF-MB400 gateway. Written by SYSTEM, 1-NOV 18:16:14 This file was created by the PMDF-MB400 configuration generator V6.2. (1) The rewrite rules for PMDF-MB400 have been written out to a file. You can simply include this file in your configuration by adding the line <PMDF_TABLE:MB400.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-MB400 ! !<PMDF_TABLE:MB400.RULES around the middle of your PMDF.CNF file. In this case, merely uncomment the line "!<PMDF_TABLE:MB400.RULES" and, if necessary, change the file name so that it reads ! ! Rewrite rules for PMDF-MB400 ! <PMDF_TABLE:MB400.RULES (2) The channel definitions for PMDF-MB400 have been written out to a file. You can simply include this file in your configuration by adding the line <PMDF_TABLE:MB400.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-MB400 channels ! !<PMDF_TABLE:MB400.CHANS towards the end of your PMDF.CNF file. In this case, merely uncomment the "!<PMDF_TABLE:MB400.CHANS" line and, if necessary, change the file name so that it reads ! ! PMDF-MB400 channels ! <PMDF_TABLE:MB400.CHANS (3) Configure the MAILbus 400 MTA for the PMDF-MB400 XAPI Agent using the NCL commands: NCL> create mta agent "PMDF-MB400" type xapi NCL> set mta agent "PMDF-MB400" invocation filename "PMDF_COM:xapi_slave.com" NCL> enable mta agent "PMDF-MB400" You also need to add this command to your MAILbus 400 startup procedures to ensure that the agent is defined after system initialization. Finally, you need to define ORADDRESS routing to your MAILbus 400 MTA routing tables so that messages sent to the PMDF-MB400 ORADDRESS will be transferred to the PMDF-MB400 agent. Definition of MAILbus 400 routing information is a one-time procedure, and is not repeated during each system startup. Refer to your MAILbus 400 documentation if you need additional information on configuring MAILbus 400 for an XAPI gateway agent. (4) PMDF-MB400 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!