Hewlett-Packard MAILbus 400 Message Transfer Agent and Application Program Interface, Version 3.2 Cover Letter for OpenVMS Alpha This Cover Letter lists the functional changes that have been introduced in Version 3.2 of the MAILbus[TM] 400 MTA. There are no functional changes that have been introduced in Version 3.2 of the MAILbus 400 Application Program Interface (API). This Cover Letter also describes how to install Version 3.2 of the MAILbus 400 MTA and API on OpenVMS[TM] Alpha. Functional Changes to the MAILbus 400 MTA The following changes have been made to the MTA for Version 3.2. Full details of these changes are provided in the MAILbus 400 MTA and API Release Notes for OpenVMS. o MTA V3.2 provides a revised filter mechanism for restricting the delivering and relaying of mails to user agents/gateways or peer MTA's. The filter behavior is governed by "Origina- tor Restriction" attribute and provides the ability for a User to define an "Authorized Originators" and "Denied Origina- tors" list of Originators Partial or Complete Oraddress at the recipient Oraddress level. o MTA V3.2 resolves the CDIF converter crash problem and the problem of missing bodyparts whenever an FTBP bodypart is pre- ceded by a forwarded message. (CFS.95953 and CFS.101523) o The retry interval for agent has been made a configurable pa- rameter. (CFS.96374) o Comparison of routing instruction attributes, agents and do- mains has been made case-insensitive. (CFS.96741) o NCL output buffer size has been increased to 64K. This allows user to view large number of entries in the NCL output. o STA functionality can be enabled/disabled by means of an envi- ronment variable MTA$STA. o 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. o Fix for conversion failures when MTA tries to convert a message containing Euro character. Also, the associated error logs do not contain sufficient information to deduce the cause of the failure. (CFS.105896 & CFS.105897) o Fix for MTA crash while processing a message containing an FTBP body part whose extension field is of unusual length. (QXCM1000085860) o "No such entity" problem. Fix for MTA crash (CFS.102871 /QXCM1000201330) o Fix for NCL commands reporting "noresource available" error. (CFS.99692) o When a message without any subject and bodypart arrives from an external domain to an MTA and inserting warning text feature is enabled, the MPDU thus transferred would be in "Awaiting Processing Retry" state. This problem has been fixed in this release. Installing Version 3.2 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 Alpha V7.3-2 DECnet-Plus for OpenVMS V7.3-2 including the DECnet Applica- tion Interface component. HP X.500 Directory Service for OpenVMS V5.3 or later. Note: 1. The changes required to include the new attributes in the NCL dictionary have been provided to DECnet engineering. The changes will be included into future releases of DECnet-Plus for OpenVMS, after this kit has been installed and tested on the customer systems. (Refer to section 6.1.1 of the Release notes for a workaround) 2. Due to limitations in the schema supplied with hp Enterprise Directory for e-Business V4.0-25 to V5.2, not all the new features of the MTA V3.2 are available with these versions of the Directory. If this is the case, you can update the schema by manu- ally re-compiling it. The schema files, which contains the Revised Filter attributes are provided along with the kit. (Refer to section 6.1.2 of the Release notes for a workaround) 2 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 4300 2400 MAILbus 400 MTA Base 5300 4400 MAILbus 400 MTA Server, Mgt, 30000 28000 and Base MAILbus_400_API_and_Base_______5300______________4600___________ 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 and API files are located on the CD-ROM in the directory named MTA032. o The command to install either the MTA or the API is: $ @SYS$UPDATE:VMSINSTAL MTA032 device-name:[MTA032] The image identification of the new images in this kit is "MTA V3.2-0". The version number of the kit when displayed using NCL management is V3.2.0 3 Hewlett-Packard Company 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 descrip- tions 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 Hewlett-Packard Development Com- pany, L.P.: DEC-net, DIGITAL, MAILbus, OpenVMS, OSAK, and the HP logo. OSI is a registered trademark of CA Management, Inc. © Copyright 2005 Hewlett-Packard Development Company, L.P. All rights reserved. 4