CONTENTS

  Title Page

  Copyright Page

  Preface

  Part I    Planning

  1      Planning a Naming Scheme

  1.1     Defining a Hierarchy for Your Organization

  1.2     Choosing a Naming Scheme

  2      Naming MTAs, Agents and Routing Domains

  2.1     Naming Your Routing Domain
    2.1.1      Global Domain Identifier
    2.1.2      Understanding the Layout of Your Routing Domain

  2.2     MTA Sets

  2.3     Dividing Your Routing Domain into Areas

  2.4     Naming MTAs

  2.5     Naming Agents
    2.5.1      Registered Agents
    2.5.2      Unregistered Agents

  2.6     Naming Other Routing Domains

  2.7     Peer MTA Entities
    2.7.1      Automatically-Configured Peer MTA Entities
    2.7.2      Manually-Configured Peer MTA Entities

  2.8     Summary of Planning MTA and Routing Domain Names

  2.9     Summary of Planning Peer MTA Entities

  2.10    Summary of Planning Agent Entities

  2.11    What to Do Next

  3      O/R Addresses and Routing Information

  3.1     Why You Need O/R Addresses

  3.2     O/R Address Attributes
    3.2.1      O/R Address Attribute Descriptions
      3.2.1.1      Country Name
      3.2.1.2      Administration Domain Name
      3.2.1.3      Private Domain Name
      3.2.1.4      Organization Name
      3.2.1.5      Organizational Unit Name
      3.2.1.6      Common Name
      3.2.1.7      Personal Name
      3.2.1.8      Domain Defined
      3.2.1.9      Numeric User Identifier

  3.3     Allocating O/R Address Attributes to Individuals in Your Routing Domain
    3.3.1      Resolving Naming Ambiguities

  3.4     Representing O/R Addresses for Individuals in Other Routing Domains

  3.5     Addressing and Gateways
    3.5.1      Complete Address Translation
    3.5.2      Partial Address Translation

  3.6     Alias O/R Addresses

  3.7     Routing Information for Complete O/R Addresses

  3.8     Routing Information for Partial O/R Addresses

  3.9     Routing Information for Other Routing Domains

  3.10    Routing Information for Different Forms of O/R Address

  3.11    Content Information

  3.12    Distribution Lists

  3.13    Permission to Send Mail to Another X.400 Management Domain

  3.14    Warning Text on Messages Arriving from Other X.400 Management Domains

  3.15    What to Do Next

  4      Planning the Use of the DEC X.500 Directory Service

  4.1     The MTA and the DEC X.500 Directory Service

  4.2     DEC X.500 Directory Service Setup Required

  4.3     Ensuring Routing Information is Available to MTAs

  5      Summary of Managing Routing Information

  5.1     The MTS Module
    5.1.1      Replication
    5.1.2      Access Control

  5.2     Routing Information Held Locally at an MTA

  5.3     Routing Information Held in the Directory

  5.4     O/R Address Information

  5.5     Routing Domain Information

  5.6     Area and MTA Information

  5.7     Foreign Address Information

  5.8     What to Do Next

  Part II    Setup

  6      Setting Up your Routing Domain on a DEC OSF/1 System

  6.1     Description of Files Used when Setting Up the MTA

  6.2     Tasks to Complete Before Setting Up Any MTAs
    6.2.1      Ensure the Directory Server Subset is Installed and Set Up
    6.2.2      Ensure the Directory Base Subset is Installed
    6.2.3      Ensure the Required MTA Subsets are Installed
    6.2.4      What to Do Next

  6.3     Upgrading from a Previous Version of the Product
    6.3.1      Check that There is a DUA Defaults File on the System
    6.3.2      Add Your Customizations to the New Startup File
    6.3.3      Run the MTA Setup Procedure
    6.3.4      Create the MTA Entry in the Directory
    6.3.5      Start the MTA
    6.3.6      Checking create_mta_cons_templates.ncl
    6.3.7      What to Do Next

  6.4     Setting Up an MTA in the Routing Domain for the First Time
    6.4.1      Set Up Access to a DSA
      6.4.1.1      Create a Naming Context for the MTA
      6.4.1.2      Create the DUA Defaults File
    6.4.2      Create the Routing Domain and Area Entries for the MTA
      6.4.2.1      Create the MTS Entity for Your Routing Domain
      6.4.2.2      Add Global Domain Identifiers
      6.4.2.3      Create Area Entries
    6.4.3      What to Do Next

  6.5     Adding More MTAs to Your Routing Domain
    6.5.1      Set Up Access to a DSA
    6.5.2      Provide Authorization to Manage the MTA's Routing Information
    6.5.3      Run the MTA Setup Procedure
      6.5.3.1      Create the MTA Entry in the Directory
    6.5.4      Start the MTA
    6.5.5      Checking create_mta_cons_templates.ncl

  6.6     Running the Verification Procedure

  6.7     Keeping the MTA Startup Script Up-to-Date

  6.8     What to Do Next

  6.9     Setting Up Remote Access to the Routing Information in the Directory

  7      Setting Up your Routing Domain on an OpenVMS System

  7.1     Setting Up the MTA in a Cluster

  7.2     Tasks to Complete Before Setting Up Any MTAs
    7.2.1      Ensure the Directory Server Component is Installed and Set Up
    7.2.2      Ensure the Directory Base Component is Installed
    7.2.3      Ensure the Required MTA Components are Installed
    7.2.4      What to Do Next

  7.3     Upgrading from a Previous Version of the Product
    7.3.1      Check that There is a DUA Defaults File on the System
    7.3.2      Initialize the MTS Process
    7.3.3      Run the MTA Setup Procedure
    7.3.4      Add Your Customizations to the New Startup File
    7.3.5      Create the MTA Entry in the Directory
    7.3.6      Start the MTA
    7.3.7      Check MTA$CREATE_CONS_TEMPLATES.NCL
    7.3.8      Updating System Startup Files
    7.3.9      What to Do Next

  7.4     Setting Up an MTA in the Routing Domain for the First Time
    7.4.1      Set Up Access to a DSA
      7.4.1.1      Create a Naming Context for the MTA
      7.4.1.2      Create the DUA Defaults File
    7.4.2      Create the Routing Domain and Area Entries for the MTA
      7.4.2.1      Create the MTS Entity for Your Routing Domain
      7.4.2.2      Add Global Domain Identifiers
      7.4.2.3      Create Area Entries
    7.4.3      What to Do Next

  7.5     Adding More MTAs to Your Routing Domain
    7.5.1      Set Up Access to a DSA
    7.5.2      Provide Authorization to Manage the MTA's Routing Information
    7.5.3      Run the MTA Setup Procedure
    7.5.4      Create the MTA Entry in the Directory
    7.5.5      Start the MTA
    7.5.6      Check MTA$CREATE_CONS_TEMPLATES.NCL
    7.5.7      Updating System Startup Files

  7.6     Using the MTA Verification Procedure

  7.7     Keeping the MTA Startup Script Up-to-Date

  7.8     What to Do Next

  7.9     Setting Up Remote Access to the Routing Information in the Directory

  8      Setting Up the Remaining Routing Information

  8.1     Routing Information Stored in the Directory

  8.2     Adding Peer MTA Entities at the MTA

  8.3     Adding Agent Entities at the MTA

  9      Setting Up Connections from Agents to the MTA

  9.1     Setup for Agents That Use the XAPI Interface
    9.1.1      Agents That Connect Directly to the MTA
    9.1.2      Agents That Use the API Server

  9.2     Setup for Gateways That Use the Shared File Interface
    9.2.1      MAILbus 400 MTA Queues
    9.2.2      Contents of gateway.dat for Shared File 1984 Interface
    9.2.3      Contents of gateway.dat for Shared File 1992 Interface

  10     Example User Agent

  10.1    Prerequisites

  10.2    Submitting a Message to the MTA
    10.2.1     Step by Step Instructions for Submitting a Message
    10.2.2     Example

  10.3    Taking Delivery of a Message with MTAmail
    10.3.1     Displaying the Structure of a Delivered Message

  A   Postal and Terminal O/R Addresses

  A.1     Postal O/R Address

  A.2     Terminal O/R Address

  B   MTS Script for ACME

  C   MTS Module Entities and Attributes

  D   Country Codes

  EXAMPLES

  9-1        Example gateway.dat for OpenServer 400 NetWare MHS Gateway to X.400

  9-2        Example gateway.dat for ISOCOR X.400 Router for Lotus Notes

  9-3        Example gateway.dat for ISOGATE for cc:MAIL

  10-1       Display of a Message Delivered by MTAmail

  FIGURES

  1-1        Hierarchy for ACME Shoe Corporation

  1-2        Geographical Hierarchy for ACME Shoe Corporation

  1-3        Business Card

  1-4        Recommended Hierarchy for ACME Shoe Corporation

  1-5        ACME Expanding to Invercargill

  2-1        The MTA's Routing Domain Entry in the Directory

  2-2        Layout of ACME Routing Domain

  2-3        Areas and Area Servers

  2-4        Structure of an MTA Name

  2-5        The ACME Routing Domain Within its X.400 Management Domain

  2-6        ACME Connections Through Intermediate Routing Domains

  2-7        Domain Entries in the Directory

  3-1        How Mnemonic O/R Addresses are Constructed

  3-2        How Numeric O/R Addresses are Constructed

  3-3        Gateways and Addressing

  3-4        Individuals in Your Routing Domain

  3-5        Individuals in Other X.400 Routing Domains

  5-1        MTS Module and Entities

  5-2        MTA Module and Entities

  5-3        Directory Entries for O/R Addresses

  5-4        Directory Entries for Routing Domains

  5-5        Directory Entries for Areas and MTAs

  5-6        Directory Entries for Foreign Addresses

  9-1        MTA Input and Output Queues

  A-1        How Postal O/R Addresses are Constructed

  A-2        How Terminal O/R Addresses are Constructed

  TABLES

  2-1        Worksheet for Your Routing Domain

  2-2        Worksheet for Peer MTA Entity

  2-3        Worksheet for Agent Entity

  3-1        O/R Address Attributes

  3-2        O/R Address for Sally Payne

  A-1        Postal O/R Address Attributes and Values

  A-2        Terminal O/R Address Attributes and Values

  C-1        MTS Entity Attributes

  C-2        MTA Entity Attributes

  C-3        Area Entity Attributes

  C-4        ORaddress Entity Attributes

  C-5        Domain Entity Attributes

  C-6        Foreign Address Entity Attributes

  D-1        Country Codes