COMPAQ MAILbus 400 Message Transfer Agent and Application Program Interface, Version 3.0 Cover Letter for Tru64 UNIX AV-QSGKF-TE This Cover Letter lists the functional changes that have been introduced in Version 3.0 of the MAILbus[TM] 400 MTA. There are no functional changes that have been introduced in Version 3.0 of the MAILbus 400 Application Program Interface (API). This Cover Letter also describes how to install Version 3.0 of the MAILbus 400 MTA and API on Tru64 UNIX. Functional Changes to the MAILbus 400 MTA The following changes have been made to the MTA for Version 3.0. Full details of these changes are given in the MAILbus 400 MTA and API Release Notes for Tru64 UNIX. o MTA V3.0 includes a new feature called "secured distribution list" which prevents unauthorized users from sending mail 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. o The MTA V3.0 also performs the "Maximum Content Length Check", while relaying messages to peer MTAs. o The MTA V3.0 generates unique names for FTBP attachments, while upgrading bodyparts from BP15 to FTBP. o The Non-DEC OID translation failure problem is resolved in the MTA version 3.0. o The MTA V3.0 fixes the problem of Set command fails after Cre- ate command on an MTS Replica. o The MTA V3.0 does not crash while decoding certain types of IPM extension field in the message. o The MTA V3.0 fixes the problem of forced exit in the relayer region. o The MTA V3.0 is certified for Multi-CPU machines. 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 V3.0 includes the functionality for the customized built CDIF PCBOX Converter. o The MTA was earlier unable to display very large lists in re- sponse to an NCL query.This problem has been resolved now. o The MTA would, under certain conditions, not log the domain name for "Transfer In" entries in the accounting logs. This problem has been resolved now. o The outbound message stall problem under high message traffic condition is resolved in MTA V3.0. o The MTA V3.0 is supported on Tru64 UNIX 4.0G or later. Installing Version 3.0 To install this kit, follow the instructions in MAILbus 400 MTA Installing on a Tru64 UNIX System or MAILbus 400 API Installing on a True64 UNIX System, with the following exceptions: o Make sure you install one of the following configurations of prerequisite software: - Tru64 UNIX V4.0G DECnet-Plus for Tru64 UNIX V4.0C or later Compaq X.500 Directory Service for Tru64 UNIX (Base Sub- set)V4.0.25 or Tru64 UNIX Enterprise Directory V5.0, V5.1, V5.2 - Tru64 UNIX V5.0, V5.1, V5.1A DECnet-Plus Tru64 UNIX 5.0-1 or later Compaq X.500 Directory Service for Tru64 UNIX (Base Sub- set)V4.0.25 or Tru64 UNIX Enterprise Directory V5.0, V5.1, V5.1A Note: 1. Due to limitations in the schema supplied with Compaq X.500 V4.0-25, not all the new features of the MTA V3.0 are avail- able with this version of the Directory. 2. If your system is running DECnet V4.0C, V5.0B or V5.1, you need to install the "libdnamgmt.so.vxxx.5Aug2002.gz" DECnet patch. Where xxx is the version number 2 o The approximate disk space required (in Kilobytes) for each of the MAILbus 400 MTA and API subsets in /usr/opt and /var/opt, and the corresponding softlinks for the files in /usr and /var are shown in the following table: ___________________________________________________________________ Space Required Subset Title Subset Name (in kB) _____________________________________________/usr_________/var_____ MAILbus 400 MTA Mgt MTAANETMAN300 1800 80 (Tru64 UNIX) MAILbus 400 MTA Server MTAASRV300 29900 120 (Tru64 UNIX) MAILbus 400 MTA Base MTAABASE300 4400 70 (Tru64 UNIX) MAILbus 400 API (Tru64 MTAACLNT300 11000 minimal UNIX) MAILbus 400 API Reference MTAAMAN300 200 minimal Pages_(Tru64_UNIX)_________________________________________________ o From the root user account on the node where you want to in- stall a MAILbus 400 MTA component or the API, mount the CD-ROM as follows: # mount -r /dev/cdrom-device-name /mnt where cdrom-device-name is the name of your CDROM device spe- cial file, usually rz4c. o To load the subsets follow the following steps For the MTA # setld -l /mnt/mtaa300/kit For the API # setld -l /mnt/mtax300/kit When you deinstall the MTA, the MTA startup script (/var/mta /scripts/ start_mta.ncl) is renamed to /var/mta/scripts/start_ mta.ncl.savn, where n is a number. The MTA installation pro- cedure installs a new template /var/mta/scripts/start_mta.ncl file. After the subsets have been successfully installed, reap- ply your saved changes to the new copy of the start_mta.ncl file. For the MAILbus 400 API, if you are using the archive libraries on Tru64 UNIX, you will need to relink your application after you has installed Version 3.0. The version number of this kit when displayed using NCL manage- ment is V3.0.0. To identify this kit, type the following command: # what /usr/sbin/mta/mta | grep MAILbus the following is the response from this command 3 MAILbus 400 MTA (V3.0-0) Aug DD hh:mm:ss IST 2002 4 Compaq Computer 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 Compaq Information Technologies Group, L.P.: DEC-net, DIGITAL, MAILbus, OpenVMS, OSAK, and the COMPAQ logo. OSI is a registered trademark of CA Management, Inc. © 2002 Compaq Information Technologies Group, L.P.1995,2002. All rights reserved. 5