HEWLETT-PACKARD HP MAILbus 400 Message Transfer Agent and Application Program Interface, Version 3.2-12 Cover Letter for OpenVMS Alpha This Cover Letter lists the functional changes that have been introduced in Version 3.2-12 of the MAILbus 400 MTA. This Cover Letter also describes how to install Version 3.2-12 of the MAILbus 400 MTA and API on OpenVMS Alpha. Functional Changes to the MAILbus 400 MTA The following changes have been made to the MTA for Version 3.2-12. o Missing Domain Information When a peer MTA association gets interrupted, domain in- formation does not get recovered. This leads to the domain information not getting logged in the accounting file for the subsequent messages transferred over the recovered associa- tion. This problem is fixed in this release. o MTA crash while extracting filename extension MTA crashes while extracting the filename extension from an FTBP message because of improperly terminated string in extension. This problem is fixed in this release. o MTA crash in the Relayer region MTA crashes while logging information about a structure in the MTA log file. The crash occured in the DECCRTL fprinf routine because incorrect parameters were getting passed. This problem is fixed in this release. o MTA events were logged with incorrect information In cases where a manually configured peer MTA entity is not present, or is incorrectly configured, the Inbound Hard Rejection events logged by the MTA indicated a peer MTA entity of type "Automatically Configured" even when the peer MTA was "Manually Configured". This problem is fixed in this release. Now, the events log the peer MTA type as "Not Configured" in such cases. o MTA crash MTA crashes while posting an Inbound connection failure event. This problem is fixed in this release. Installing Version 3.2-12 To install this kit follow the instructions in MAILbus 400 MTA Installing on an OpenVMS Alpha System or MAILbus 400 API Installing on an OpenVMS Alpha System with the following excep- tions: o Make sure you install one of the following configurations of prerequisite software: - OpenVMS Alpha V7.3-2 HP DECnet-Plus for OpenVMS V7.3-2 including the DECnet Application Interface component. HP Enterprise Directory Service for OpenVMS V5.3 or later. - OpenVMS Alpha V8.2 HP DECnet-Plus for OpenVMS V8.2 including the DECnet Application Interface component. HP Enterprise Directory Service for OpenVMS V5.4 or later. - OpenVMS Alpha V8.3 HP DECnet-Plus for OpenVMS V8.3 including the DECnet Application Interface component. HP Enterprise Directory Service for OpenVMS V5.4 or later. Note: 1. The changes required to include the new attributes (intro- duced in V3.2) in the NCL dictionary have been provided to DECnet engineering. The changes will be included into future releases of HP DECnet-Plus for OpenVMS. (Refer to section 6.1.1 of the Release notes for a workaround) o The approximate disk space required on the system disk (in blocks) during and after installation for the different components 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 2 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-12". The version number of the kit when displayed using NCL manage- ment is V3.2.12. © Copyright 2006 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documen- tation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendors standard commercial license. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. A FULL SOFTWARE PATCH KIT HAS RECEIVED LIMITED TESTING AND IS CONSIDERED APPROPRIATE FOR GENERAL DISTRIBUTION TO CUSTOMERS. DISCLAIMER OF WARRANTY AND LIMITATION OF LIABILITY THIS FULL SOFTWARE PATCH KIT IS PROVIDED "AS IS", WITHOUT WAR- RANTY OF ANY KIND. ALL EXPRESS OR IMPLIED CONDITIONS, REP- RESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR PARTICULAR PURPOSE, OR NON- INFRINGEMENT, ARE HEREBY EXCLUDED TO THE EXTENT PERMITTED BY APPLICABLE LAW. IN NO EVENT WILL HP OR ANY OF ITS SUBSIDIARIES BE LIABLE FOR ANY LOST REVENUE OR PROFIT, OR FOR SPECIAL, IN- DIRECT, CONSEQUENTIAL, INCIDENTAL OR PUNITIVE DAMAGES, HOWEVER CAUSED AND REGARDLESS OF THE THEORY OF LIABILITY, WITH RESPECT TO ANY SOFTWARE PATCH MADE AVAILABLE HERE OR TO THE USE OF SUCH SOFTWARE PATCH. 3