CONTENTS

  Title Page

  Copyright Page

  Preface

  1      The MAILbus 400 Message Transfer Agent

  1.1     What is the MAILbus 400 MTA?

  1.2     The MAILbus 400 MTA and the DEC X.500 Directory Service

  1.3     The MAILbus 400 MTA and MAILbus

  1.4     Operating Over DECnet/OSI and TCP/IP Networks
    1.4.1      The MAILbus 400 MTA and DECnet/OSI
    1.4.2      The MAILbus 400 MTA and TCP/IP

  1.5     Using the MAILbus 400 MTA
    1.5.1      Providing Connectivity to Other X.400 Messaging Systems
    1.5.2      Providing Connectivity to Non-X.400 Messaging Systems Through Gateways
    1.5.3      Providing a Backbone Message Transfer Service for X.400 Mail Users

  1.6     What to Do Next?

  2      The MAILbus 400 MTA and X.400

  2.1     The 1992 MHS Standards
    2.1.1      The 1992 Revisions to the 1988 MHS Standards

  2.2     An X.400 Message Handling System and its Components
    2.2.1      The Role of the Message Transfer Agent
    2.2.2      The Role of the User Agent
    2.2.3      The Role of the Access Unit
    2.2.4      The Role of the Message Store

  2.3     Messages, Reports and Probes in an X.400 MHS
    2.3.1      What is a Message?
      2.3.1.1      Structure of a Message
      2.3.1.2      Interpersonal Messages
    2.3.2      What is a Report?
    2.3.3      What is a Probe?

  2.4     Addressing in an X.400 MHS
    2.4.1      O/R Addresses
      2.4.1.1      Mnemonic O/R Addresses
      2.4.1.2      Numeric O/R Addresses
      2.4.1.3      Postal O/R Addresses
      2.4.1.4      Terminal O/R Addresses
    2.4.2      Ensuring the Uniqueness of O/R Addresses
    2.4.3      Distribution Lists

  2.5     What to Do Next?

  3      Additional Features of the MAILbus 400 MTA

  3.1     The DEC X.500 Directory Service Used by the MTA
    3.1.1      Advantages of Using a Distributed Directory
    3.1.2      Regulating Access to the Directory

  3.2     Routing Domains
    3.2.1      Connecting Your Routing Domain to Other Routing Domains
    3.2.2      Dividing Your Routing Domain into Areas to Optimize Message Transfer

  3.3     Conformance to the Enterprise Management Architecture

  3.4     Minimal MTA Setup and Maintenance

  3.5     Using MTA Sets to Optimize MTA Availability

  3.6     Collecting Information About Messages in Your Routing Domain

  3.7     Recovering Messages From an MTA

  3.8     Types of Agent
    3.8.1      XAPI Interface
    3.8.2      Shared File 1984 Interface

  3.9     IPM Bodypart Conversion

  3.10    What to Do Next?

  Glossary
    1984 downgrading . . . administration management domain (ADMD)
    Agent . . . attribute
    bad message . . . Compound Document Architecture (CDA)
    connectionless network service (CLNS) . . . DEC ODA Compound Document Architecture (CDA) Gateway
    DEC X.500 Directory Service . . . Domain entity
    downgrading . . . event sink
    export . . . inbound message
    Interface Region . . . MAILbus
    MAILbus 400 . . . Message Protocol Data Unit (MPDU)
    message splitting . . . MTA module
    MTA set . . . Open Systems Interconnection (OSI)
    O/R address . . . postal O/R address
    Presentation address . . . Relayer
    Reliable Transfer Service Element (RTSE) . . . submission
    TCP/IP . . . X/Open
    XAPI interface . . . XAPI interface

  FIGURES

  1 How to Use the MTA Documentation

  1-1        MAILbus 400 MTAs and the DEC X.500 Directory Service

  1-2        MAILbus 400 and MAILbus

  1-3        X.400 and Non-X.400 Connections

  1-4        Serving X.400 Mail Users

  2-1        An X.400 Message Handling System

  2-2        Structure of a Message

  2-3        Structure of an IPM Content

  2-4        Distribution List Expansion

  3-1        How MTAs Use the Directory

  3-2        Different Routing Domains

  3-3        Connecting Indirectly to Another Routing Domain

  3-4        The MTA Module in the EMA Entity Hierarchy

  3-5        The MTS Module in the EMA Entity Hierarchy

  3-6        Agent Interfaces

  TABLES

  1 Related Documents