MAILbus 400 Message Transfer Agent and Application Program
                 Interface, Version X2.0-167 for OpenVMS Alpha


This Cover Letter lists the functional changes that have been introduced
in Version X2.0-167 of MAILbus 400 MTA.


Functional Changes
------------------

MTA Version X2.0-167 is based on MTA V2.0C and it includes the fixes for
the following IPMTs, ASN.1 Vulnerabilities and also a system wide 
logical to enable/disable STA.


1. IPMT CFS.77437
   Fix for MTA crash while decoding certain types of IPMS extension 
   field in messages.

2. IPMT CFS.79710
   Fix for Non-DEC OID translation failure problem.

3. IPMT CFS.80088
   The MTA would, under certain conditions, not log the domain name for 
   "Transfer In" entries in the accounting log. This problem has been 
   resolved now. 

4. IPMT CFS.81442
   The MTA now successfully displays very large distribution lists in 
   response to NCL queries.

5. The MTA on OpenVMS Alpha provides a specialised API for message 
   traffic analysis - the System Traffic Analyzer API.

   A system-wide logical, namely 'MTA$STA' has been introduced in the 
   MTA which will allow the customer to turn ON/OFF the STA from the MTA
   at the time of MTA startup.

   The command to be used for the same:

      $ DEFINE/SYS MTA$STA "<value>"

   For Ex.
   If STA needs to be enabled, then the logical has to be set to a value
   of "TRUE":
      $ DEFINE/SYS MTA$STA "TRUE"

   The creation of the STA threads in the MTA is dependent on the value
   "TRUE" assigned to the Logical. If ANY OTHER value is assigned or the
   logical has not been defined at all, then the STA threads would not 
   get created in the MTA.


6. The MTA X2.0-167 supports 256 parallel agent connections.

7. Fix for SSRT3624 X.400 potential security vulnerability via ASN.1
   cross reference: NISCC (006489) 
   A potential denial of service has been identified that may allow a
   remote initiated Buffer Overflow when malformed ASN.1 messages are 
   submitted. This potential buffer overflow has been fixed in this 
   version.


Installation Prerequisites and Procedure:
-----------------------------------------

Versions of OpenVMS Alpha that this patch should be installed on:

This patch should be installed on all the OpenVMS Alpha machines that are 
running MAILbus 400 MTA V2.0C and X2.0-x versions.

 To install this kit follow the instructions in MAILbus 400 MTA In-
 stalling on an OpenVMS Alpha System or MAILbus 400 API Installing
 on an OpenVMS Alpha System with the following exceptions:

 o  Make sure you install one of the following configurations of
    prerequisite software:
	-  OpenVMS V6.2
           DECnet[TM]/OSI[R] for OpenVMS V6.3 with ECO8
           DIGITAL[TM] X.500 Directory Service for OpenVMS (Base compo-
           nent) V3.0 (or later)

        -  OpenVMS V7.1,
           DECnet-Plus for OpenVMS V7.1 with ECO2, including the DECnet
           Application Interface component (formerly known as the OSI
           Applications Kernel or OSAK[TM])
           DIGITAL X.500 Directory Service for OpenVMS (Base component)
           V3.0 (or later)

        -  OpenVMS V7.2
           DECnet-Plus for OpenVMS V7.2, including the DECnet Ap-
           plication Interface component (formerly known as the OSI
           Applications Kernel or OSAK[TM], V3.0-003O
           DIGITAL X.500 Directory Service for OpenVMS (Base component)
           V3.0 (or later)

 
Following is a brief description about the Installation procedure:
(For detailed installation procedure, refer the steps described in the 
Manual "MAILbus400 Message Transfer Agent Installing on an OpenVMS Alpha
System " Version 2.0.)

 1. Copy the MTA savesets to a directory. For example, 
    device-name:[MTA030]

 2. The command to install either the MTA or the API is:

       $ @SYS$UPDATE:VMSINSTAL MTAC020 device-name:[MTAC020]

 The image identification of the images in this kit is "MTA X2.0-167"

 The version number of the kit when displayed using NCL management
 is X2.0.167


Problem reporting:
------------------
Problems relating specifically to this kit should be reported through 
your normal HP support channel.