Patch Name: PHSS_7237 Patch Description: s700_800 10.X OpenMail B.04.01 X400 patch Creation Date: 96/04/16 Post Date: 96/06/14 Hardware Platforms - OS Releases: s700: 10.01 10.10 s800: 10.01 10.10 Products: OpenMail B.04.01 Filesets: OpenMail.OM-CORE,B.04.01 OpenMail.OM-X400,B.04.01 Automatic Reboot?: No Status: General Superseded Critical: No Path Name: /hp-ux_patches/s700_800/10.X/PHSS_7237 Symptoms: PHSS_7237: D500251173: In the Korean environment, admin commands that specify an ORN, when the last field is NULL, place incorrect information in the directory and/or in other Openmail data areas. 1600164509: Need to be able to send Text attachments as File Transfer Body Parts. D500222364: FTBP Object ID's should be in a separate file from the External Body part (15) Object ID's. 5003295386: Openmail should generate an EMA Unknown Attachment FTBP for unconfigured file types. Defect Description: PHSS_7237: D500251173: When ORNs are supplied to an admin command, the ORN is first converted to the T61 interchange character set. Then the ORN is parsed into a of tags and values, each in T61. When the final attribute value is NULL, this parsing incorrectly places the T61 designations and invocations in the value. 1600164509: IA5 or ISO8859-1 or ISO6937 text can now be sent or received using the EMA Unknown Text File Transfer Body Part. D500222364: FTBP Object ID's are now held in ftbpids.map. External Body part (15) Object ID's are held objids.map. 5003295386: Outgoing: Openmail now generates an EMA Unknown Attachment FTBP for unconfigured file types. Incomin: If this object ID is received, it is flagged as Binary. SR: 1600164509 D500222364 5003295386 D500251173 Patch Files: /opt/openmail/bin/x400.hpx.in /opt/openmail/bin/x400.hpx.out /opt/openmail/bin/x400.cds.in /opt/openmail/bin/x400.cds.out /opt/openmail/lib/libom.sl /var/opt/openmail/release.sys/objids.map /var/opt/openmail/release.sys/ftbpids.map /tmp/ominst.7237 what(1) Output: /opt/openmail/bin/x400.hpx.in: ---------------------------------------------------- ------------- PATCHED_B.04.01: 96/04/10 B.04.01.01 x400.hpx.in, x400.cds.in ---------------------------------------------------- ------------- X400-GTWAPI: C.05.22 $Date: 95/11/06 9:25:44 $ /opt/openmail/bin/x400.hpx.out: ---------------------------------------------------- ------------- PATCHED_B.04.01: 96/04/10 B.04.01.01 x400.hpx.out, x400.cds.out ---------------------------------------------------- ------------- X400-GTWAPI: C.05.22 $Date: 95/11/06 9:25:44 $ /opt/openmail/bin/x400.cds.in: ---------------------------------------------------- ------------- PATCHED_B.04.01: 96/04/10 B.04.01.01 x400.hpx.in, x400.cds.in ---------------------------------------------------- ------------- /opt/openmail/bin/x400.cds.out: ---------------------------------------------------- ------------- PATCHED_B.04.01: 96/04/10 B.04.01.01 x400.hpx.out, x400.cds.out ---------------------------------------------------- ------------- /opt/openmail/lib/libom.sl: $Header: gen_vers.c,v 1.18.1.1 96/04/10 14:57:30 ton yn Exp $ Sccs_Id = %W% $Header: mll_access.c,v 5.12 95/07/14 16:33:04 jacki e Exp $ $Header: mll_highl.c,v 5.3 94/06/22 00:43:40 gren Ex p $ Sccs_Id = %W% $Header: bb_find.c,v 1.10 95/09/29 17:02:36 ann Exp $ Sccs_Id = %W% $Header: bb_itm2acl.c,v 1.2 94/11/23 11:16:27 kevins Exp $ Sccs_Id = %W% $Header: bb_utils.c,v 1.38 95/07/14 16:10:18 jackie Exp $ Sccs_Id = %W% $Header: cl_format.c,v 5.25 94/06/21 18:56:33 gren E xp $ Sccs_Id = %W% $Header: da_FmtEnt.c,v 1.22 95/08/11 16:05:51 steve Exp $ Sccs_Id = %W% $Header: da_PrsEnt.c,v 4.43 95/09/26 17:16:34 ann Ex p $ ---------------------------------------------------- ------------ t61_TfmTIS.c PATCHED_B.04.01: 96/04/10 B.04.01.02 oid_ObjId.c, oid_access.h PATCHED_B.04.01: 96/04/10 B.04.01.01 libom.sl ---------------------------------------------------- ------------ Sccs_Id = %W% $Header: usrl_add.c,v 4.29 96/01/04 10:06:29 tonyn E xp $ Sccs_Id = %W% $Header: usrl_del.c,v 4.13 96/01/04 10:07:11 tonyn E xp $ Sccs_Id = %W% $Header: usrl_lic.c,v 4.5 94/06/21 21:55:11 gren Exp $ /var/opt/openmail/release.sys/objids.map: No what strings /var/opt/openmail/release.sys/ftbpids.map: No what strings /tmp/ominst.7237: Installation file for the OpenMail core product cksum(1) Output: 4015502557 1187840 /opt/openmail/bin/x400.hpx.in 3116369438 1175552 /opt/openmail/bin/x400.hpx.out 632230552 2252800 /opt/openmail/bin/x400.cds.in 2653810520 2248704 /opt/openmail/bin/x400.cds.out 349851457 3825664 /opt/openmail/lib/libom.sl 3809621488 7224 /var/opt/openmail/release.sys/objids.map 2897784476 8901 /var/opt/openmail/release.sys/ftbpids.map 67055406 3037 /tmp/ominst.7237 Patch Conflicts: None Patch Dependencies: None Hardware Dependencies: None Other Dependencies: None Supersedes: None Equivalent Patches: PHSS_7234: s700: 9.01 9.03 9.05 9.07 s800: 9.00 9.04 Patch Package Size: 10540 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 PHSS_7237 5a. For a standalone system, run swinstall to install the patch: swinstall -x autoreboot=true -x match_target=true \ -s /tmp/PHSS_7237.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/PHSS_7237.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. The cluster clients must be shut down as described in step 5b. By default swinstall will archive the original software in /var/adm/sw/patch/PHSS_7237. 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 PHSS_7237.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/PHSS_7237.depot of=/dev/rmt/0m bs=2k Special Installation Instructions: SUBSYSTEM_SHUT ---------------------------------------------------------- Configuring FTBP support for Text --------------------------------- 1. The FTBP Object ID's that were in the bottom half of objids.map, have now been moved into a new file ~openmail/sys/ftbpids.map. The format of this file is the same as objids.map. EXCEPT: where the same Object ID is used to map onto different Openmail filecodes, the FIRST one will be used for incoming messages. It used to be the last one. This change should improve performance. 2. New entries have been added to ftbpids.map including EMA Unknown Attachment, and EMA Unknown Text. 3. The madmd.cfg file option PREFERRED_TEXT_BODY_PART can now take one of the following additional values to specify that a text attachment should go out as a FTBP: FTBP-IA5, FTBP-ISO6937 or FTBP-ISO8859_1. If PREFERRED_TEXT_BODY_PART is set to anything else, the attachment will NOT go out as a FTBP. 4. Because EMA Unknown Text does not give any indication of character set, Openmail provides a limited degree of steering as follows: a. Outgoing ----------- Multiple entries for Text (OM file code 1167) exist in ftbpids.map. They are distinguished by the CHARSET token. For outgoing text a match for both OMFILECODE and CHARSET must be made to determine the Object ID. At present, all combinations map onto the EMA Unknown Text OID. This may change if new OID's are defined later by EMA. Note that PREFERRED_TEXT_BODY_PART=FTBP-{charset}, ENCODING=88 and GENERATE_FTBP=TRUE must all be set for the particular route in the madmd.cfg file. BUT the value of {charset} does not matter in the outbound direction. b. Incoming ----------- If a FTBP with an Object ID of "EMA Unknown Text" is received, a matching madmd.cfg route entry is looked-for to determine the value of PREFERRED_TEXT_BODY_PART. If this entry is found and is set to one of the FTBP-{charset} values, that {charset} will be used to mark the text type within Openmail. If the record is not found, IA5 is assumed. -------------------------------------------------- PHSS_7237: This patch corrects the defect for any future use of the administration commands. If a field in a directory entry or other date area already already contains an incorrect null attribute value, this patch will not correct the entry. -------------------------------------------------- NOTE: OpenMail must be shutdown before installing this patch.