Patch Name: PHNE_10898 Patch Description: s700_800 10.X HP X400 D.02.0[01] cumulative patch Creation Date: 97/04/29 Post Date: 97/06/02 Hardware Platforms - OS Releases: s700: 10.01 10.10 10.20 s800: 10.01 10.10 10.20 Products: HP_X.400 D.02.00 D.02.00.01 Filesets: X400.X400-RUN,D.02.00,D.02.00.01 X400.X400-GAPI-PRG,D.02.00,D.02.00.01 Automatic Reboot?: No Status: General Superseded Critical: No (superseded patches were critical) PHNE_8148: OTHER OpenMail and user XAPI applications fail. Path Name: /hp-ux_patches/s700_800/10.X/PHNE_10898 Symptoms: PHNE_10898: 1653208546: The maximum time to transfer a message does not operate for any messages after the first when several messages are queued for an adjacent MTA. Once a transfer is started with a message which can not be transferred within the specified time, that first message is correctly returned back to the MTA. However any following large message that takes longer than that time to transfer is transferred completely and is not returned to the MTA. 1653189498: This SR arises because of a problem reported in OpenMail. When processing file transfer body parts, the XAPI library leaves temporary files in /var/opt/x400/tmp. These have the prefix 'g' and contain a copy of the body part. The resulting disc usage was a problem for heavily used systems. 1653148627: When using RFC1327 feature to translate from X400 domain names and RFC822 domain names (using entries in the x42rfc.map file), recipient names are not being correctly mapped in resulting messages sent to sendmail, which rejects them with an NDR indicating User agent not known at destination. D500264606: The RFC1327 facility does not support the wild-card address translation feature (allowing for omitted parts of the domain hierarchy). For example, entries of the form O$@ within the x42rfc.map file are not processed. 5003352682: When using the RFC1327 address translation facility, a valid RFC822 address that appears within a DDA component of an X400 address is not used, though if RFC1327 is disabled then it is used correctly. 1653157339: The HP X400 MTA product does not ignore leading blanks in OR attributes as is required by X.402. In some circumstances when working with other MTAs, this gave rise to looping of messages. PHNE_8697: D500276121: X4admin fails to delete a route under certain circumstances. It seems that for any particular MTA, the first route in the list of routes for that MTA cannot be deleted. Instead, the program outputs the warning: (X4MSG 4536) WARNING: This route contains T.61 characters. You should enter another route containing printable string equivalents for the following fields: Organization Unit Names Domain Defined Attributes A success message is then output although the route is not deleted. 4701263723: Under certain circumstances, the RTS program appears to loop, outputting a large number of errors of the type 04/16-19:49:55 * TOO MANY SESSION EVENTS * (X4EVENT 3551) 04/16-19:49:55 * TOO MANY SESSION EVENTS * (X4EVENT 3551) to the r###.evnt file, and also not responding to the x4stop command. D500284067: An interoperability problem with a new third-party has been identified, relating to the data passed when the RTS makes an initial connection to the adjacent MTA. (This data is contained in the session connection identifier). The adjacent rejects the connect request with a validation failure. 5000716738: Certain truncated or corrupt PDUs when submitted to the MTA cause the MTA to loop. Excessive CPU is consumed and the program does not respond to the x4stop command. D500283655: Access to files necessary to support X400 under MC/ServiceGuard available only with the OpenMail product, and so are not available when running X400 "standalone". D500283663: With the introduction of sendmail version 8.7 on HP-UX 10.20 the HP X.400 sendmail gateway no longer works. With the new format of the sendmail.cf file, x4mailer is not recognised as the relevant sendmail mailer. PHNE_8148: D500271205: XAPI library in released version of HP X.400 D.02.00 (on the August 1996 applications release media) is not backwards compatible with previous versions of the product. As a result, it will not function correctly with OpenMail or with any existing user applications that utilise the API. D500271593: A further change was made to make the product conformant with the latest MAWG spec in the area of file transfer body part data element creation. However this has given rise to interoperatability problems with other existing MTAs that do not support the latest version of the spec. (Messages received from the HP MTA appeared corrupt). Defect Description: PHNE_10898: 1653208546: The reported symptom shows because the transfer timer is not properly reset after a timeout. This problem has been fixed as follows: The transfer timer is started before the AP-Connect request (to catch a possible timeout due to non-responding RTS peer). It is then cleared and re-started on each PDU that is transmitted. If a PDU transmission fails because of excessive length or network problems, it is returned to the MTA for re-routing. 1653189498: The XAPI was creating temporary files and did not remove them. The handling of FTBP15 messages has been changed to remove these temporary files. 1653148627: This problem resulted from a situation where mapping would either not take place at all, or that it did not take place in a case-insensitive way. The x4mailer program has been corrected to deal with these situations. D500264606: Code to support the wild-card address translation capability did not exist and has now been provided. Now, a wild-carded element in the map files is effectively ignored in the construction of an X400 address from and rfc822 address, and in the reverse will not be prepended to the domain address when this is constructed from an X400 address. 5003352682: Code to support extraction of rfc-822 addresses from a DDA element when RFC1327 is enabled did not exist and has now been provided. 1653157339: The parsing and formatting routines are taking the O/R addresses as received from PDU or calling routines. This handling is non-conformant to X.402. The MTA parsing has been changed to convert any incoming Standard Attributes and Domain Defined Attributes (of O/R Names and Global ID's) to conform to X.402 character restrictions, which are that leading, trailing or more than one consecutive embedded space characters will be ignored. The XAPI interface is also affected. Both the MTA and XAPI interface will accept non-conforming Standard Attributes and DDAs, but will convert them to and transmit them in the conforming format. PHNE_8697: D500276121: A defect was introduced into x4admin which prevented the deletion of the first route of an MTA during the development of unrelated enhancements. This patch corrects that defect. 4701263723: A looping RTS arises from an unexpected (incorrect) return code from OTS, that occurs when an RFC1006 subnet was configured and no 802.3 subnet, and the NSAP is invalid for an adjacent MTA. OTS returns the primitive code 0x8422, rather than sending a provider abort indication to the RTS as it should. This patch includes an interim fix that prevents the RTS looping and makes it possible to shut down in the conventional way. The RTS will stall when it hits the invalid address, although the relevant MTA can be determined from the last r### file logged to. D500284067: The contents of the session connection identifier (SCID) were rejected because the TSAP of the local system transmitted to the remote system is in the incorrect format, although previously tested MTAs do not validate the field so rigidly. 5000716738: When copying a truncated PDU to the output queue for subsequent transmission, the length taken for the body part is taken to be that recorded in the PDU, even though truncation has taken place. Looping resulted because the MTA failed to register when end of file had been hit. The offending PDU is now transferred to the undeliverable queue, and this is indicated in the event file. D500283655: Files necessary to build up an MC/ServiceGuard package to support HP X.400 not released with HP X.400, but only with OpenMail. The necessary files are included in this patch: /opt/x400/newconfig/control.sh /opt/x400/newconfig/services.ascii (empty) D500283663: The format of sendmail.cf has changed such that the x4smupdate script no longer comments out the relevant entries in the file to make x4mailer the sendmail mailer for X400. This patch includes a corrected version of x4smupdate. NOTE: To make use of the HP X.400 sendmail interface on HP-UX 10.20 the patch PHNE_8702 (and NOT PHNE_8011 as indicated elsewhere), a patch to sendmail itself, MUST be installed. PHNE_8148: D500271205: This results from a change to the EMA MAWG spec for the File Transfer Body Part, relating to the object items IM_SIZE and IM_LAST_MODIFICATION_DATE. The released D.02.00 product assigned values to these items as per the latest specification. However this gave rise to compatibility problems, and so the values have been reversed, in keeping with the version of the spec supported by HP X.400 D.01.01 and earlier. D500271593: A further change was made to make the product conformant with the latest MAWG spec in the area of file transfer body part data element creation, so that the data is encoded as OCTET_ALIGNED, rather than as a SINGLE_ASN1_TYPE. This patch reverts that change. SR: 1653157339 1653208546 1653148627 1653189498 D500264606 5003352682 D500276121 4701263723 D500284067 5000716738 D500283655 D500283663 D500271205 D500271593 Patch Files: /opt/x400/lbin/admin /opt/x400/lbin/rts /opt/x400/lbin/mta /opt/x400/bin/x4smupdate /opt/x400/newconfig/control.sh /opt/x400/newconfig/services.ascii /opt/x400/lib/gtwapi/libMT.a /opt/x400/lib/gtwapi/ximp88 /opt/x400/lib/gtwapi/include/ximp.h /opt/x400/lbin/x4mailer what(1) Output: /opt/x400/lbin/admin: X400-RUN: D.02.00.01 $Date: 96/09/02 11:29:01 $ /opt/x400/lbin/rts: X400-RUN: D.02.00.03 $Date: 97/04/18 22:02:01 $ /opt/x400/lbin/mta: X400-RUN: D.02.00.03 $Date: 97/04/29 22:15:11 $ /opt/x400/bin/x4smupdate: X400-RUN: D.02.00.01 $Date: 96/11/13 09:25:41 $ /opt/x400/newconfig/control.sh: None /opt/x400/newconfig/services.ascii: None /opt/x400/lib/gtwapi/libMT.a: X400-GTWAPI: D.02.00.03 $Date: 97/04/22 21:35:48 $ /opt/x400/lib/gtwapi/ximp88: None /opt/x400/lib/gtwapi/include/ximp.h: None /opt/x400/lbin/x4mailer: X400-RUN: D.02.00.01 $Date: 97/01/30 18:12:48 $ 9.X nsswitch patch Rev B cksum(1) Output: 4037327546 1302788 /opt/x400/lbin/admin 3240638563 630784 /opt/x400/lbin/rts 2586161329 987136 /opt/x400/lbin/mta 3667907843 4931 /opt/x400/bin/x4smupdate 1964020355 26436 /opt/x400/newconfig/control.sh 4294967295 0 /opt/x400/newconfig/services.ascii 2736031739 8589 /opt/x400/lib/gtwapi/include/ximp.h 890228227 1948716 /opt/x400/lib/gtwapi/libMT.a 2741427272 3358 /opt/x400/lib/gtwapi/ximp88 2874021217 847872 /opt/x400/lbin/x4mailer Patch Conflicts: None Patch Dependencies: None Hardware Dependencies: None Other Dependencies: None Supersedes: PHNE_8148 PHNE_8697 Equivalent Patches: None Patch Package Size: 5690 Kbytes Installation Instructions: Please review all instructions and the Hewlett-Packard SupportLine User Guide or your Hewlett-Packard support terms and conditions for precautions, scope of license, restrictions, and, limitation of liability and warranties, before installing this patch. ------------------------------------------------------------ 1. Back up your system before installing a patch. 2. Login as root. 3. Copy the patch to the /tmp directory. 4. Move to the /tmp directory and unshar the patch: cd /tmp sh PHNE_10898 5a. For a standalone system, run swinstall to install the patch: swinstall -x autoreboot=true -x match_target=true \ -s /tmp/PHNE_10898.depot 5b. For a homogeneous NFS Diskless cluster run swcluster on the server to install the patch on the server and the clients: swcluster -i -b This will invoke swcluster in the interactive mode and force all clients to be shut down. WARNING: All cluster clients must be shut down prior to the patch installation. Installing the patch while the clients are booted is unsupported and can lead to serious problems. The swcluster command will invoke an swinstall session in which you must specify: alternate root path - default is /export/shared_root/OS_700 source depot path - /tmp/PHNE_10898.depot To complete the installation, select the patch by choosing "Actions -> Match What Target Has" and then "Actions -> Install" from the Menubar. 5c. For a heterogeneous NFS Diskless cluster: - run swinstall on the server as in step 5a to install the patch on the cluster server. - run swcluster on the server as in step 5b to install the patch on the cluster clients. By default swinstall will archive the original software in /var/adm/sw/patch/PHNE_10898. If you do not wish to retain a copy of the original software, you can create an empty file named /var/adm/sw/patch/PATCH_NOSAVE. Warning: If this file exists when a patch is installed, the patch cannot be deinstalled. Please be careful when using this feature. It is recommended that you move the PHNE_10898.text file to /var/adm/sw/patch for future reference. To put this patch on a magnetic tape and install from the tape drive, use the command: dd if=/tmp/PHNE_10898.depot of=/dev/rmt/0m bs=2k Special Installation Instructions: 1. General HP X.400 and any applications utilising the XAPI interface must be shut down before installing this patch. 2. XAPI Interface The following applies to the HP X.400 released on the August 1996 Applications Release media ONLY. - This patch MUST be installed if using HP X.400 version D.02.00 in conjunction with OpenMail. - This patch MUST be installed if using HP X.400 version D.02.00 with any previously created user applications that utilise the XAPI programmatic interface - Any XAPI applications that were built using the XAPI library and header files MUST be recompiled and relinked with this patch installed. The cause of the problem giving rise to the above requirements has been fixed in the subsequent applications release (November/December 1996). This patch can be installed over that version of HP X.400 with no adverse effect. 3. MC/ServiceGuard support of HP X.400 Standalone The support of OpenMail and X400 together under MC/ServiceGuard is described at length in the document "OpenMail MC/ServiceGuard Technical Guide", which can be found under the Enterprise Messaging Encyclopedia on the web. (Go to URL location: http://www.ice.hp.com and search for "ServiceGuard".) It is strongly recommended that this document is read thoroughly before proceeding. The files provides in this patch provide the means to run HP X400 under MC/ServiceGuard, without OpenMail also being installed. The control.sh file is a template and will require editing to suit the requirement of the system on which HP X.400 is installed. Where references to the file /opt/openmail/newconfig/omsg/control.sh are made in the above document (see "Creating the Package"), the control.sh file supplied in this patch should be used. The services.ascii file should also be substituted. 4. Session Connection ID format change The following steps should be taken in the specific circumstance where an interoperability problem occurs with another X400 system, relating to the format of the session connection identifier. Two problems have been encountered, which are corrected by the presence of the indicated trigger files when the RTS program is started. a) If the adjacent MTA is configured with: "use unstructured SCID = N", the session connect id (SCID) is not T61 encoded. This has been found to be a problem for some X400 products, and is corrected by the presence of the files: /etc/opt/x400/.send_t61_callid (on 10.x) or /usr/lib/x400/.send_t61_callid (on 9.x). (Just "touching" the file is sufficient). b) To ensure that the local TSAP (or local SSAP if one is configured) is encoded in the SCID character for character rather than as a string of characters equivalent to the hex representation (eg as "MHS" (hex 4D 48 53) rather than "4D4853" (hex 34 44 34 38 35 33)) touch the file: /etc/opt/x400/.plain_copy_callid (on 10.x) or /usr/lib/x400/.plain_copy_callid (on 9.x). Note: The default behaviour of the RTS is unchanged.