DIGITAL MAILbus 400 Message Transfer Agent and Application Program Interface, Version 2.0A Cover Letter for DIGITAL UNIX AV-QSGKC-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. 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 DIGITAL UNIX. 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 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 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 uses the TCP/IP Transport Service to make con- nections to peer MTAs in the same routing domain when it is directed to do so by the "set mta transport service options" command. 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 a DIGITAL UNIX System or MAILbus 400 API Installing on a DIGITAL UNIX System, with the following exceptions: o Make sure you install one of the following configurations of prerequisite software: - DIGITAL[TM] UNIX[R] V3.2G DECnet/OSI for DIGITAL UNIX V3.2B DIGITAL X.500 Directory Service for DIGITAL UNIX (Base Sub- set) V3.0 (not required for the API) - DIGITAL UNIX V4.0B with patches: OSF410-400151 (44.00), OSF410-400196 (85.00), and OSF410-400239-1 (136.01), or later DECnet/OSI for DIGITAL UNIX, V4.0A or later with dnaevld patched to 12-MAR-97, or later DIGITAL X.500 Directory Service for DIGITAL UNIX (Base Sub- set) V3.1, or later (not required for the API) 2 o The command to deinstall any MAILbus 400 MTA or API subsets already installed on your systems is one of the following: # setld -d MTAABASE14? MTAASRVR14? MTAANETMAN14? MTAACLNT14? MTAAMAN14? # setld -d MTAABASE20? MTAASRVR20? MTAANETMAN20? MTAACLNT20? MTAAMAN20? The question mark (?) in subset names is a wildcard character. 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 MTAANETMAN201 1800 60 (DIGITAL UNIX) MAILbus 400 MTA Server MTAASRVR201 29300 120 (DIGITAL UNIX) MAILbus 400 MTA Base MTAABASE201 4400 70 (DIGITAL UNIX) MAILbus 400 API (DIGITAL MTAACLNT201 11000 minimal UNIX) MAILbus 400 API Reference MTAAMAN201 200 minimal Pages_(DIGITAL_UNIX)_______________________________________________ o The installation instructions are: 1. Mount the disk as follows: # mount -r /dev/cdrom-device-name /mnt where cdrom-device-name is the name of your CDROM device special file, usually rz4c. 2. Load the subsets as follows: For the MTA: # setld -l /mnt/mtaa201/kit For the API: # setld -l /mnt/mtax201/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 procedure installs a new template /var/mta/scripts/start_mta.ncl file. After the subsets have been successfully installed, reapply 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 DIGITAL UNIX, you will need to relink your application after you have installed Version 2.0A. 3 The version number of this kit when displayed using NCL management is V2.0.135. To identify this kit, type the following command: # what /usr/sbin/mta/mta | grep MAILbus The following is the response from this command: MAILbus 400 MTA (V2.0A-135) Mon Sep 8 14:31:13 BST 1997 Be aware that if you have installed Version 2.0A of the MTA on a version of DIGITAL UNIX prior to V4 and want to upgrade DIGITAL UNIX to V4 (or later), you must deinstall and then reinstall Ver- sion 2.0A of the MTA before you run Version 2.0A on the upgraded DIGITAL UNIX system. If you fail to do this and attempt to run the MTA without deinstalling and reinstalling it on DIGITAL UNIX V4, the MTA reports a Forced Exit event accompanied by a System Interface Error event when you try to start the MTA, as follows: Event: System Interface Error from: Node nodename MTA at : 1997-08-01-11:04:05.822+00:00I0.279 System Interface Error = Process Creation Parameter = "Reinstall MTA for this UNIX version" Error Text = "Version mismatch" Event: Forced Exit from: Node nodename MTA at : 1997-08-01-11:04:05.839+00:00I0.279 Exit Point = Management Agent If you see this error, deinstall Version 2.0A and then reinstall Version 2.0A. You can do this after you have upgraded to V4 of DIGITAL UNIX. Copyright Information 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 Corporation: DIGITAL, MAILbus, and the DIGITAL logo. UNIX is a registered trademark in the United States and other countries licensed exclusively through X/Open Company Ltd. ©Digital Equipment Corporation. 1997. All rights reserved. 4