DIGITAL MAILbus 400 Message Transfer Agent and Application Program Interface, Version 2.0A Cover Letter for OpenVMS VAX AV-QSGGC-TE This Cover Letter lists the functional changes that have been introduced in Version 2.0A of the MAILbus[TM] 400 MTA. There are no functional changes that have been introduced in Version 2.0A of the MAILbus 400 Application Program Interface (API). This Cover Letter also describes how to install Version 2.0A of the MAILbus 400 MTA and API on OpenVMS[TM] VAX[TM]. Functional Changes to the MAILbus 400 MTA The following changes have been made to the MTA for Version 2.0A. Full details of these changes are given in the MAILbus 400 MTA and API Release Notes for OpenVMS VAX. o The MTA no longer fails during a new installation. o The MTA now successfully installs on OpenVMS V7.1 (or later). o The MTA has changed the way it handles the conversion of Exter- nally Defined bodyparts to Bilaterally Defined bodyparts, most commonly used when it downgrades the IPMS message content to messaging systems based on the 1984 MHS Standards. o When the MTA downgrades, to a messaging system based on 1984 MHS Standards, a forwarded message that does not contain an original-encoded-information-type element on the delivery enve- lope, it no longer fails to deliver the message. o When the MTA downgrades, to a messaging system based on 1984 MHS Standards, a message or probe that has a private-domain- identifier element present in any per-domain-bilateral- information element on the envelope, it now deletes the whole of the per-domain-bilateral-information element from the enve- lope, which makes the message or probe compliant with the 1984 MHS Standards. o When a message addressed to more than one actionable recipient is due to be downgraded but its content cannot be downgraded by this MTA, it is now transferred to a peer MTA, if appropriate, for all recipients of the message. o When the MTA receives a File Transfer bodypart message with a FileAttributes parameter that does not include the optional Pathname attribute, the MTA now transfers the message. o Accounting has been improved as follows: - Accounting now distinguishes between delivery and non- delivery reports. - As well as recording the rounded-up size of messages and reports in Kilobytes, Accounting now also records the actual size of messages and reports in bytes (that is, octets). o When the MTA receives a File Transfer bodypart message with a FileAttributes parameter that does not include the optional Pathname attribute, the MTA now transfers the message. o When the MTA converts, to ISO 6937, a bodypart whose last line is not terminated with a CR/LF sequence, the last line is no longer lost. o The MTA now delivers any two or more messages whose delivery is deferred to the same time. o The DIGITAL X.500 Directory Service DSA no longer reports au- thentication failure events when the MTA rebinds after losing the DSA connection. o The MTA no longer logs recoverable DSA communication problems to the event file. o When using a replicated DSA, the MTA on the shadow DSA node no longer gives directory service errors when the master DSA is unavailable. o The MTA now successfully connects to the second and subsequent MTAs in an MTA set when the connection to the first MTA in the set fails. o The MTA now assigns a unique local identifier to each MPDU it processes. o The MTA now ensures that the GDI in the external and internal trace information matches the GDI in the message identifier when the GDI is one of the GDIs specified for the local MTA. Installing Version 2.0A To install this kit follow the instructions in MAILbus 400 MTA Installing on an OpenVMS VAX System or MAILbus 400 API Installing on an OpenVMS VAX 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 DIGITAL[TM] X.500 Directory Service for OpenVMS (Base compo- nent) V3.0 - OpenVMS V7.1, or later DECnet-Plus for OpenVMS V7.1 with ECO1, including the DECnet Application Interface component (formerly known as the OSI Applications Kernel or OSAK[TM]) 2 DIGITAL X.500 Directory Service for OpenVMS (Base component) V3.0 o The approximate disk space required on the system disk (in blocks) during and after installation for the different compo- nents are shown in the following table: ________________________________________________________________ Component Title Space Required (in blocks) _______________________________During___________After___________ MAILbus 400 MTA Mgt 3700 1400 MAILbus 400 MTA Base 3500 2700 MAILbus 400 MTA Server, Mgt, 19700 17300 and Base MAILbus_400_API_and_Base________3500_____________3100___________ o Note that Version 2.0A is no longer distributed on 9-track 1600 BPI Magtape or TK50 Streaming Tape. It is only available as part of the DIGITAL CD-ROM Software Library for OpenVMS VAX Layered Products. This means the installation instructions are different from those in Version 2.0. 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 and API files are located on the CD-ROM in the directory named MTAA020. o The command to install either the MTA or the API is: $ @SYS$UPDATE:VMSINSTAL MTAA020 device-name:[MTAA020] OPTIONS N The image identification of the new images in this kit is MTA V2.0A-135. The version number of the kit when displayed using NCL management is V2.0.135. 3 Digital Equipment Corporation makes no representations that the use of its products in the manner described in this publication will not infringe on existing or future patent rights, nor do the descriptions contained in this publication imply the granting of licenses to make, use, or sell equipment or software in accordance with the description. The following are trademarks of Digital Equipment Corpora- tion: DECnet, DIGITAL, MAILbus, OpenVMS, OSAK, VAX, and the DIGITAL logo. OSI is a registered trademark of CA Management, Inc. ©Digital Equipment Corporation. 1995, 1997. All rights reserved. 4