       COMPAQ     ;  MAILbus 400 Message Transfer Agent and Application Program   Interface, Version 3.0.    Cover Letter for OpenVMS Alpha     AV-QSGMF-TE      >  This Cover Letter lists the functional changes that have beenC  introduced in Version 3.0 of the MAILbus[TM] 400 MTA. There are no C  functional changes that have been introduced in Version 3.0 of the 1  MAILbus 400 Application Program Interface (API).   C  This Cover Letter also describes how to install Version 3.0 of the .  MAILbus 400 MTA and API on OpenVMS[TM] Alpha.  )  Funtional Changes to the MAILbus 400 MTA   A  The following changes have been made to the MTA for Version 3.0. B  Full details of these changes are provided in the MAILbus 400 MTA#  and API Release Notes for OpenVMS.   @  o  MTA V3.0 includes a new feature called "Secured Distribution@     List" that prevents unauthorized users from sending mails to"     the secured distribution list.  @  o  The new "Secured Deliver/Secured Transfer To Domain" feature@     prevents unauthorized users from sending mail to the secured#     recipients and secured domains.   B  o  The MTA V3.0 also performs the "Maximum Content Length Check",C     while relaying messages to the peer MTAs. This check was previ- 2     ously done only during delivery to recipients.  C  o  The MTA V3.0 generates unique names for FTBP attachments, while *     upgrading bodyparts from BP15 to FTBP.  A  o  The XAPI performance has been improved in the MTA V3.0 on Al-      pha.  B  o  The Non-DEC OID translation failure problem is resolved in the     MTA Version 3.0.  ?  o  The MTA V3.0 does not crash while decoding certain types of %     IPMS extension field in messages.   A  o  The MTA V3.0 resolves the NCL "set" command failure on an MTS      replica.  C  o  The MTA on OpenVMS Alpha provides a specialised API for message 7     traffic analysis - the System Traffic Analyzer API.   9  o  The MTA V3.0 supports 256 parallel agent connections.        @  o  Now the MTA identifies a relocated DSA and continues working      without requiring a restart.  ?  o  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.  C  o  The MTA now successfully displays very large distribution lists      in response to NCL queries.     Installing Version 3.0   C  To install this kit follow the instructions in MAILbus 400 MTA In- B  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 V7.2-1 or laterC        DECnet-Plus for OpenVMS V7.2-1 with ECO2 or later, including 2        the DECnet Application Interface component.A        Compaq X.500 Directory Service for OpenVMS V3.1 or V4.0-25 5        or OpenVMS Enterprise Directory V5.0 or later.        -  OpenVMS Alpha V7.3 B        DECnet-Plus for OpenVMS V7.3, including the DECnet Applica-         tion Interface component.A        Compaq X.500 Directory Service for OpenVMS V3.1 or V4.0-25 5        or OpenVMS Enterprise Directory V5.0 or later.   	     Note:   ?     1. The new MTA attributes for Secured Distribution List and B        Secured Delivery and Secured Transfer to Domain will not beC        available if your DECnet version is earlier than DECnet-Plus         for OpenVMS V7.2-1 ECO3. E        (Refer to section 5.1.1 of the Release notes for a workaround)   ?     2. The new MTA attributes for Secured Distribution List and B        Secured Delivery and Secured Transfer to Domain will not be@        available if you are using Compaq X.500 Directory Service        V4.0.25 or earlier.E        (Refer to section 5.1.2 of the Release notes for a workaround)                       #                                   2        >  o  The approximate disk space required on the system disk (inB     blocks) during and after installation for the different compo-+     nents are shown in the following table:   D     ________________________________________________________________@     Component Title                   Space Required (in blocks)  D     ______________________________During____________After___________  9     MAILbus 400 MTA Mgt            4300              2400   9     MAILbus 400 MTA Base           5300              4400   9     MAILbus 400 MTA Server, Mgt,  30000             28000      and Base  D     MAILbus_400_API_and_Base_______5300______________4600___________  A  o  From the SYSTEM account on the node or cluster where you want @     to install a MAILbus 400 MTA component or the API, mount the     CD-ROM as follows:  '        $ MOUNT device-name volume-label   >     where device-name and volume-label are as specified in the?     OpenVMS Layered Products Compact Disk User's Guide. The MTA B     and API files are located on the CD-ROM in the directory named     MTA030.   8  o  The command to install either the MTA or the API is:  :        $ @SYS$UPDATE:VMSINSTAL MTA030 device-name:[MTA030]  ?  The image identification of the new images in this kit is "MTA 	  V3.0-0".   B  The version number of the kit when displayed using NCL management
  is V3.0.0                                  #                                   3        >  Compaq Computer Corporation makes no representations that the@  use of its products in the manner described in this publicationB  will not infringe on existing or future patent rights, nor do theA  descriptions contained in this publication imply the granting of C  licenses to make, use, or sell equipment or software in accordance   with the description.  @  The following are trademarks of Compaq Information Technologies>  Group, L.P.: DECnet, DIGITAL, MAILbus, OpenVMS, OSAK, and the
  COMPAQ logo.   5  OSI is a registered trademark of CA Management, Inc.                         =   Compaq Information Technologies Group, L.P. 1995,2002. All   rights reserved.                                                           #                                   4 