Prior to running the PMDF-X400 configuration utility you must have installed PMDF-MTA with PMDF-X400 support and have configured PMDF-MTA. Refer to Chapters 1, 2, 3, and 4 if you have not already installed and configured PMDF.

You must also have a network transport supported by PMDF-X400 installed and configured. Transports supported by PMDF-X400 are described in the PMDF System Manager's Guide.

The PMDF CONFIGURE X400 utility will prompt for several pieces of required information. You should be prepared to provide the following:

• The domain name for the PMDF-X400 gateway. This is the domain name that originators on the PMDF side of the gateway will use to direct messages through PMDF-X400.
• The X.400 Originator-Recipient name, or ORname, for your PMDF-X400 gateway. This consists of the various fields of an X.400 address that remote X.400 users will specify when they originate messages intended for recipients that are reachable on the PMDF side of your PMDF-X400 gateway. Whenever PMDF-X400 receives a message from another X.400 MTA, ORnames containing these fields will be recognized and passed to PMDF for further delivery. The ORname fields that can be specified are, in order:
  • 1. Country
    2. Administrative Mail Domain
    3. Private Mail Domain
    4. Organization
    5. up to four Organizational Units
  The Country field must be specified; all other fields are optional.
  • The Selector portion of the OSI Presentation Address used to distinguish an incoming network connection intended for PMDF-X400. You should supply a Presentation Selector, PSEL, Session Selector, SSEL, and Transport Selector, TSEL. Do not enter the local Network Service Access Point, or NSAP, portion of the 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.
  • The network transport stack, whether OSI transport, TCP/IP transport, or both.
  • MTA information for both the remote X.400 MTA and the local PMDF-X400 MTA. Information which is required consists of:
  • Transfer mode. Determines whether PMDF-X400 should use 1988 Normal mode, 1988 X.410 mode, or 1984 mode with this remote MTA.
  • Local MTA name and password. These will be sent by PMDF-X400 any time that a network connection with the other MTA is established. The connection could be rejected if the name and password do not match what the other MTA is expecting to see.
  • Remote MTA name and password. These will be provided by the remote MTA when a network connection is established between the two. PMDF-X400 might reject the connection if the name and password do not match.
  • Local MTA address. This is the Selector portion of the OSI Presentation address used by PMDF-X400 to identify itself when connecting to the remote MTA. For 1984 or 1988 X.410 transfer modes, the configuration utility will provide by default the local TSEL specified previously. For 1988 Normal mode, the configuration utility will provide by default all three Selectors specified previously. Use the default unless you know that the other MTA can only recognize some other address for PMDF-X400.
  • Remote MTA address. This is the OSI Presentation address PMDF-X400 is to use when connecting to the remote X.400 MTA. For 1988 Normal mode, you must provide the complete PSAP (Presentation Service Access Point), consisting of PSEL, SSEL, TSEL, and NSAP (Network Service Access Point). For 1988 X.410 or 1984 transfer modes, you need only provide a TSAP (Transport Service Access Point), consisting of a TSEL and NSAP. See the PMDF-X400 chapter of the PMDF System Manager's Guide for more information on the accepted forms of Presentation address.

  Note The NSAP address specified must be acceptable to the transport stack you chose previously. For example, if you only specified that a TCP/IP transport is to be used, don't provide an OSI (VOTS address) form here. Additionally, PMDF-X400 depends upon the transport layer to interpret the address and make the network connection. The NSAP provided must be acceptable to the transport. In other words, if you specify a TCP/IP address, your TCP/IP package must have been configured to know how to reach the address. Similarly, if you specify a VOTS address, you must have configured the VOTS component of DECnet Extensions or DECnet/OSI to handle the address.

  Your local MTA information will need to be shared with the administrator of the remote MTA before any network connection can be established. In addition, the remote MTA administrator will need to know the NSAP address of your PMDF-X400 gateway. See the PMDF-X400 chapter of the PMDF System Manager's Guide for further details on local and remote MTA information.