Patch Name: PHSS_24875 Patch Description: s700_800 10.X OpenMail B.07.00 September 01 Periodic Patch Creation Date: 01/08/22 Post Date: 01/09/05 Hardware Platforms - OS Releases: s700: 10.20 s800: 10.20 Products: OpenMail B.07.00 Filesets: OpenMail.OM-ADM,B.07.00 OpenMail.OM-AMECAT,B.07.00 OpenMail.OM-AMEICE,B.07.00 OpenMail.OM-AMEPAW,B.07.00 OpenMail.OM-AMEPSS,B.07.00 OpenMail.OM-APPL,B.07.00 OpenMail.OM-BB,B.07.00 OpenMail.OM-CHSICE,B.07.00 OpenMail.OM-CHSPAW,B.07.00 OpenMail.OM-CORE,B.07.00 OpenMail.OM-DESK,B.07.00 OpenMail.OM-DSYNC,B.07.00 OpenMail.OM-ENGCAT,B.07.00 OpenMail.OM-ENGICE,B.07.00 OpenMail.OM-ENGPAW,B.07.00 OpenMail.OM-ENGPSS,B.07.00 OpenMail.OM-FINICE,B.07.00 OpenMail.OM-FINPAW,B.07.00 OpenMail.OM-FREICE,B.07.00 OpenMail.OM-FREPAW,B.07.00 OpenMail.OM-GERICE,B.07.00 OpenMail.OM-GERPAW,B.07.00 OpenMail.OM-IMAP4,B.07.00 OpenMail.OM-ITAICE,B.07.00 OpenMail.OM-ITAPAW,B.07.00 OpenMail.OM-KORICE,B.07.00 OpenMail.OM-KORPAW,B.07.00 OpenMail.OM-LC,B.07.00 OpenMail.OM-LDAP,B.07.00 OpenMail.OM-MAN,B.07.00 OpenMail.OM-NIPICE,B.07.00 OpenMail.OM-NIPPAW,B.07.00 OpenMail.OM-PMOVER,B.07.00 OpenMail.OM-POP3,B.07.00 OpenMail.OM-PTBICE,B.07.00 OpenMail.OM-PTBPAW,B.07.00 OpenMail.OM-RC,B.07.00 OpenMail.OM-SMS,B.07.00 OpenMail.OM-SPAICE,B.07.00 OpenMail.OM-SPAPAW,B.07.00 OpenMail.OM-SWEICE,B.07.00 OpenMail.OM-SWEPAW,B.07.00 OpenMail.OM-UNIX,B.07.00 OpenMail.OM-WEBADM,B.07.00 OpenMail.OM-X400,B.07.00 Automatic Reboot?: No Status: General Superseded Critical: No Path Name: /hp-ux_patches/s700_800/10.X/PHSS_24875 Symptoms: PHSS_24875: CR: JAGad30137 SR: 8606160818 OpenMail B.06.00.00 + MayPP00 unix.in might hang and a message queued on the sendmail queue when the message contains one part only, which is a distribution list. Workaround: Prior to sending the DL, add some text in the body part of the message. CR: JAGad31466 SR: 8606162150 One-way disrsync agreement between OpenMail and Exchange (over OMEXCONN). Updates are done on the Exchange server. When modifying attributes 111 and PHONE-1, then the next dirsync results in the full loss of tis modified entry within the OM directory. (However, the next dirsync cycle will add the corrected entry again). CR: JAGad49568 SR: 8606180347 Defining more than one sender name on the omtidyu command-line makes omtidyu substitute the last defined name as all defined names. For example: omtidyu -B -u "daniel wink" -R -T i -n -w "gren elliot" -n -w "iain parker" will return : CRITERIA : Messages in the InTray NOT matching "iain parker " in SENDER field AND NOT matching "iain parker " in SENDER field. CR: JAGad65896 SR: 8606196695 HPUX 11.x - 10.x Openmail 6.0 Dec '00 PP The incoming internet gateway, unix.in, loops if supplied with a bad RCPT_TO or Arpa ORN that contains more than one @ sign. For instance, To: _//org/co/admd/prmd////RFC-822/pp@inetia.com@a.b.c CR: JAGad67601 SR: 8606198411 Message with a large distribution list (thousands of recipients) can take a long, long time to pass through the X.400 gateway (from OpenMail to X.400). CR: JAGad68810 SR: 8606199624 omshowcda -d displays the mask used to extract directory entries. The format of this mask changed with GR6 PP-Mar. It used to be: S/G/I and now it is: S=/G=/I= This will also occur for other directory related commands that display attribute masks. CR: JAGad69036 SR: 8606199850 WC6.0 and PAW corrupts the autoreply covering text in the languages Japenese, Korean and simplified Chinese when the rule is listed. The covering text is not corrupted when viewed from within the auto-replied message. CR: JAGad69543 SR: 8606200362 Occasionally some message body parts, which require base 64 mime encoding, cause the item.browse binary to perform a segmentation violation. This occurs when a user attempts to read the message from the intray or folder area using an IMAP client (Netscape communicator). CR: JAGad70640 SR: 8606201464 Some scripts included in the OM-APPL component assume that the 'cut' command is located in /usr/bin. In RedHat 7.1, 'cut' is located in /bin. The scripts affected are omaddapp, omaddapppdl, omaddapppdln, omdelapp, omdelapppdl, omdelapppdln, omshowapp, omshowapppdl and omshowapppdln. CR: JAGad70641 SR: 8606201465 During installation of patch PHSS_23491 the script vvice attempts to create the directory /var/opt/openmail/temp/vv_bkp_log and fails. The directory /var/opt/openmail/temp has the sensitivity label "SYSTEM INSIDE" and the vvice script is executed from within the "SYSTEM" environment and therefore does not have sufficient privileges to perform the operation. During installation of the patch PHSS_23491, vvsync attempts to copy the portal.daemon and kill.portal binaries from /opt/openmail/bin to the CHROOTED bin directory and fails. These binaries do not form part of the OpenMail B.07.xx.xx components and therfore are not present in the OpenMail bin directory. During installation of the patch PHSS_23491, user configurable settings are not retained in the general.cfg CR: JAGad71090 SR: 8606201916 Web Client 6.0 may, under certain cirumstances, display the incorrect item count when listing items in the tray areas or the folder areas. CR: JAGad71959 SR: 8606202785 Clear/signed S/MIME message sent into OpenMail via Internet g/w cannot be browsed by IMAP client. The multipart/signed part of the message is empty. The message can be successfully read by the OMGUI client. CR: JAGad74578 SR: 8606205403 Some messages that have come from the internet contain attachments that cannot be opened when using an IMAP client (eg. Internet Explorer or Netscape). Typically these are messages that only contain an attachment and no covering text, but other types of message structure may also suffer from this problem. The user typically sees a copy progress bar that just stops, the transfer of the attachment does not complete. The format of attachment within the MIME message is not correct - it should be base64 and in fact the data is unencoded. CR: JAGad74715 SR: 8606205540 This applies to B.06.00.00 and B.07.00.00 Use of ldapmodify to replace the mhsORAddress or omAddress attributes does not work if attempting to replace existing individual attributes, other than S, S-TX, G and G-TX. For instance, if the entry for S=user111 has an OU1 configured, then # ldapmodify -L UTF8-N -D "cn=clim, o=Openmail" -v dn: cn=user111, o=OpenMail changetype: modify replace: mhsORAddresses mhsORAddresses: S=user111/ou1=japan3 gives ldap_modify: Operations error ldap_modify: additional info: [OM 16092] An attribute has multiple values, but is notconfigured as multi-value. Parameter : Directory Entry Modifier Attribute : OU1Max allowed size : 32 Required syntax : PRINTABLE-STRING The error can also be seen on the server side, on the omslapd debug output. The recommended method is to use ldapmodify to modify the individual attributes explicitly. For instance, the input to ldapmodify would be dn:... changetype: modify replace: 5 5: The internal names of the OU attributes are used as they are not mapped by default in the ~openmail/sys/ldap.attribs file. Mappings could of course be added to this file, so that more meaningful tags could be used in ldapmodify. CR: JAGad75038 SR: 8606205863 Directory entries added using omaddent that contain OCTET-STRING attributes have octets with certain values stripped out. ommodent shows the same problem. The FREEBUSY directory attributes used by Outlook FreeBusy lookup are examples of OCTET-STRING data. A situation where the FREEBUSY attributes may become incorrect is when omdiropt is run on the FREEBUSY directory. This is because omdiropt uses omaddent. Octet \014 (14 decimal) is one value that gets stripped. There may be some other values. CR: JAGad75517 SR: 8606206344 The problem is seen on Linux with OM 7 only. The problem is that issuing a valid IMAP command causes the IMAP4 server to crash, which should not happen. With the test mailbox, issuing the commands: . login "username" "password" . select inbox . fetch 2 (BODY.PEEK[3.HEADER.FIELDS (Resent-Date)]) causes the crash. CR: JAGad75975 SR: 8606206802 The problem is with the way that sendmail converts the address and OpenMail subsequently parses it. If an entry has the format \", then sendmail quotes it and adds an extra \ to the \" sequence. So us\"er , goes to "us\\"er" , Openmail then splits up the address list using commans as the separator. If a separator is in a quote, it ignores it. In the above example, the quote after the \\ is taken to be a closing quote. This means that things get out of sync, as the last quote is taken to be an opening, rather than closing, quote and the address list becomes mangled. In addition, the mangled address list may now contain entries in excess of 1024 characters This can cause a fatal error. CR: JAGad79081 SR: 8606209895 Certain printable chars may be used in the components, e.g. Surname, of OM Personal Names, but should be represented by special characters on input (see man page omattribs). Such a char is that 'space' should be input as '_' to allow for Surnames like "Van Gogh". IMAP makes no allowance for this mapping, and so fails to login because the username as input does not exist as an OM user. CR: JAGad80029 SR: 8606210842 OpenMail may fail to configure auxiliary child processes correctly when using the omsetscv command. This results in the child processes not terminating via the omshut command. CR: JAGad83734 SR: 8606214543 This applies to B.07, when configured to allow duplicate internet addresses in the directory. This is the default for servers upgraded from an earlier version of OpenMail, but not for new B.07 installations. Using OMGUI to send a message, if an internet name is entered that is in the OpenMail system directory twice and the Dist. List is checked then a System Error 2 is generated and the connection is lost (the UAL session is terminated). This only occurs if individual name checking is turned off. This is caused by an error in the UAL Checklist command, when attempting to return the duplicate entries as alternatives. Note that, prior to B.07, UAL CheckList did not actually return alternatives when searching on the internet address field. See also the related CR JAGad 83932, which is not planned for fixing in the September 2001 Periodic Patch. PHSS_23490: CR: JAGab39939 SR: 8606100957 Omfmtent -u creates output that is corrupted. This occures when an attribute name is specified and the attribute value is not. The format of the output is incorrect because it lists the attribute name but assigns no value to it making the output unusable in scripts. ie: Input to omfmtent : s=kessler/i=c/g=richard/q=/ou1=hdqt Output of omfmtent : 1=kessler/3=c/2=richard/4/5=hdqt As you can see by the above example, the output from the omfmtent command is missing an "=" after the 4. CR: JAGab68963 SR: 8606102906 The new server feature of REPEAT REMINDERS in the OMGUI and MOB GUI do not stop sending out reminders after the Expiry date. CR: JAGad31664 SR: 8606162348 Can't reply in OMGUI and ccMail to messages from internet whose address has comments. CR: JAGad35090 SR: 8606165799 If 2 OpenMail users have the same name (but different mailnodes) Single User Restore sometimes selects the wrong message store to be restored. CR: JAGad40563 SR: 8606171299 The web clients do not work with HTTPS and the Apache web server. When the user tries to signon they are presented with the following message: Bad Request Your browser sent a request that this server could not understand. Reason: You're speaking plain HTTP to an SSL-enabled server port. CR: JAGad41471 SR: 8606172211 The UAL sometimes aborts on Redhat 7.0 systems when using the directory relay service, with the following in the OpenMail log: SERIOUS ERROR Remote Client (U/I Access) 11.30.00 07:47:57 [OM 10250] Process about to terminate due to error. Signal (Segmentation Violation) trapped by process 28277; code = 0. Procedure trace follows: -> pc_recv_logical_block <- pc_recv_logical_block <- pc_recvmessage -> ual_SendMessage <- ual_SendMessage -> ual_RecvReply -> ual_GetFreeBusyTime -> ual_ConvORNCheck -> ual_ConvertORN -> ual_GetUserCharSet <- ual_GetUserCharSet <- ual_ConvertORN <- ual_ConvORNCheck -> ual_GetUsersHost -> nm_ParseORN <- nm_ParseORN User Name: UAL TestUser2 / Test, UAL Pid of logging process: 28277 CR: JAGad42968 SR: 8606173711 It is possible using Outlook with a MAPI connection to OpenMail to send a message with an internet address containing 8-bit characters in the domain name. The outgoing Internet Gateway discards these domain names, causing an attempt to be made to deliver the message to a recipient with the same address but no domain name. This is not correct: if an address is invalid, message delivery should not be attempted to a partial address in this manner, as there are potential privacy issues. CR: JAGad43052 SR: 8606173797 When a message with accented characters in the subject is copied across message stores using Netscape messenger, the subject of the message has the MIME character set specifier in it when viewed using omcontain, OMGUI, Outlook. The subject appears OK when using Netscape Messenger. CR: JAGad44030 SR: 8606174784 Openmail does not have a converter from unicode to IA5, but it does have one from unicode to ISO8859_1. When the item browser is used to display a text message using the default format, it has no problem in displaying the message if OM_DEF_USER_CHAR is set to ISO8859_1 in the configuration file. However, if OM_DEF_USER_CHAR is set to IA5, then the item browser isn't able to do the conversion and reports an error. As the error reported in the log file was that a character set conversion between MIME-UTF8 and IA5 was failing, then this is probably the case. The second problem is the way that the item browser displays the message in MIME format. Adding the mapping of UTF-8 to UTF8 in the mime.cs file means that the character set for the message is now UTF8 which is recognised by OpenMail and the message is correctly displayed on most clients. However, for Netscape Messenger, which uses the item browser MIME option, there is a problem. The steering file ~sys/brwmime.str specified that generally character sets should be converted to ISO8859_1 unless otherwise specified. This means that the item browser attempts a conversion from UTF8 to ISO8859_1 and fails. It should be noted that UNICODE is not generally supported on OpenMail when messages are in the MIME format. CR: JAGad45429 SR: 8606176189 When using PAW and Web Client 6.0 rule names may be displayed incorrectly in Korean, Japanese and Simplified Chinese versions. This may cause the browser to hang. CR: JAGad45449 SR: 8606176209 Outlook OFS: Item created offline and synced, and then modified offline but synced online causes a duplicate to be created. CR: JAGad45880 SR: 8606176642 The IMAP/item.browse aborts with a segmentation violation on LINUX, when trying to encode an html attachment into "Quoted-Printable" format. CR: JAGad46439 SR: 8606177205 For an OpenMail server that is configured to support Czech... Messages being sent from X400 with 1992 standard General Text: context-specific 0 (23 octets): GeneralString (21 octets): 1b 28 42 0f 1b 2d 42 1b 7e 31 31 31 31 b1 ea 32 32 32 . ( B . . - B . ~ 1 1 1 1 . . 2 2 2 are not correctly converted by the X400 In Mapper. They should be converted to files of type 1736 with character set T61BASE, and the data of the file should be consistent with this. CR: JAGad46896 SR: 8606177664 The OpenMail Internet gateway rejects multipart/signed messages if one of its composite, multipart or message, part's boundary-end markers is missing. CR: JAGad47713 SR: 8606178486 1) omtidyu -l, -t and -w options - wildcards may get confused in MB. If a multibyte string contains an *, this is assumed to be a wildcard. 2) Username incorrectly displayed if it contains TX fields. The TX fields are concatenated to earlier field values. This is also a problem with other address list attributes. 3) The -l option is not displayed. This displays a list of the requested folders and should be displayed in the full listing. 4) The error/usage string is not displayed if not options are specified. omtidyu either returns nothing, or prompts for the password for the defult user. 5) The -q option does not work. The -q option produce similar output to a full report, and more information than a summary report. 6) The msg type selection is not output. When a full report is requested, the information on each item should include the message type. 7) The -f option no longer includes WB. CR: JAGad48103 SR: 8606178878 If omprepsur is not able to salvage certain files, omdosur is supposed to substitute some dummy containers instead and then continue to create a valid omcpoutu archive. Infact, omdosur was aborting straight after processing the missing container and so was creating a corrupt omcpoutu archive. CR: JAGad50818 SR: 8606181602 If a message is sent from a user who has an INTERNET_ADDR defined, to another machine, e.g. via the SMINTFC gateway, replies to that message do not get returned via the same route - they always get returned via the INTERNET gateway. This occurs when the receiving server does does not have the user's INTERNET_ADDR defined in the directory, and when the sending server is version GR7 CR: JAGad52689 SR: 8606183476 This applies to omsmtpd in Release 7. With heavy usage, the SMTP Relay port 25 listener occasionally stops with a Select error - Bad File Number. The omshowlog output contains: ERROR SMTP Relay (SMTPD Relay Pr) 03.02.01 13:34:27 [OM.DMON 2163] Failed in select. Error: 'Bad file number' Alternatively, after logging this error, omsmtpd may hang. In this case, there will be more than one copy of omsmtpd running, and the parent will be waiting for the child processes, and vice versa. Temporary Workaround: Stop and restart the daemon. Or, if Authorisation or Anti-spam features are not in use, turn off the relay, and rely on sendmail & ommapsmtp to route incoming messages correctly. CR: JAGad55411 SR: 8606186206 When shutting down the Remote Client Interface a segmentation violation is occuring in the Notification Monitor occasionally because of a buffer over-run or under-run. CR: JAGad56484 SR: 8606187277 The OpenMail delegate implementation does not include an equivalent for Exchange's "Delegate can see my private items" option (disabled by default in Exchange). Hence when forwarding Meeting Requests no distinction is made between Private items and others. CR: JAGad56620 SR: 8606187413 Message delivery rulesets are not working with empty subjects. CR: JAGad57754 SR: 8606188546 omredirtcp logs errors "getsockname: Bad file number" when no error has occurred. CR: JAGad58840 SR: 8606189626 MAPI addressbook download fails when trying to download a directory whose first entry is a large entry such as a pdl because a buffer overflow occurs. CR: JAGad63387 SR: 8606194177 A coding defect while processing MIME data sometimes causes a fatal error within the item.browse binary. On the Netscape Client the user is presented with the message: "The current command did not succeed. The mail server responded: Some of the requested messages no longer exist." CR: JAGad64229 SR: 8606195023 Some of the OpenMail patch install scripts may use return codes which are invalid in Software Distibutor (SD). In addition, symbolic names such as $SUCCESS, $FAILURE and $WARNING should be instead of 0, 1 and 2. Some of the messages do not follow the conventions, with a word such as ERROR in column 1 of the first line only, and the text indented to column 10. CR: JAGad64671 SR: 8606195467 When performing searches of large message stores if the ual.remote associated with the in.imap41d terminates due to inactivity or is deliberately killed then in.imap41d goes into a spin. When using TOP or glance the in.imap41d processes appear to be consuming a lot of CPU activity, however, they will not impact on system performance because the kernel will have assigned them a low priority. CR: JAGad66344 SR: 8606197150 When installing OpenMail B.07.00, file ~openmail/release.sys/smtpd.cfg is updated to contain the current domain name in place of the string %LOCALDOMAIN%. This is also done whenever a new OpenMail instance is created. When a patch is installed, the patch scripts need to repeat this edit. This does not affect ~openmail/sys/smtpd.cfg which is intended to be tailored by the OpenMail administrator. This file is not changed during patch installation. Defect Description: PHSS_24875: CR: JAGad30137 SR: 8606160818 This form of message is not a multi-part message, and the code that reads and processes the '.' terminator in this case omitted to include the newline character in the check. Hence the code attempted to continue to read stdin, and hence the hang, as unix.in is waiting for more from sendmail CR: JAGad31466 SR: 8606162150 Exchange Connector resyncs were removing any entry that had a non-addressing attribute changed on the Exchange side - this was caused by the fact that the DS entries coming from Exchange do NOT have a LID attribute so the normal method of getting the entry using DA_SOURCE_LID does not work. CR: JAGad49568 SR: 8606180347 Multiple sender names on the omtidyu command line were all held in a single buffer resulting in the last senders name to be registered for all the sender names. CR: JAGad65896 SR: 8606196695 This was caused by an error in the code that scans Arpa ORNs, when attempting to map domain names to Openmail mailnodes using the unixmap.in configuration file. CR: JAGad67601 SR: 8606198411 The code that is used to build the PDUs for outgoing X.400 messages is not under our control, we use XAPI libraries to give us a higher level interface to ASN.1 structures and independence from the underlying MTA. This code is not particularly efficient and it uses quite large structures in memory when a PDU is being contructed. In the case of a message that has a Distribution List with 10,000 names it will take a long time and use a lot of resources. The fix for this problem is to add some general.cfg options to replace large distribution lists with a single name distribution list. This will not prevent the message from reaching the intended recipients, but it will speed up the transfer of the message through the X.400 gateway. If this DL replacement occurs then the message cannot be successfully replied to 'all' (as the original distribution list has been removed). The general.cfg options are: X4O_MAX_DL_NAMES=n where n is the maximum number of names allowed in a DistList before they get replaced with a single stub DL name. Default is the current behaviour... there is no limit. where the string contains the stub DistList name in positional ORN format (each ORN field separated with a '/' character). %s can be used in this string and will be substituted with the number of names found in the original DistList. For example: X4O_MAX_DL_NAMES=1000 X4O_MAX_DL_NAMES_ORN=DistList/%s-Name///Black/Hole will produce a name that the user sees as: TO: 1001-Name DistList /Black,Hole when a DistList with 1001 names is send through the X.400 gateway. The default for this ORN string is: DISTRIBUTION-LIST/%s-NAME///MAIL-SYS CR: JAGad68810 SR: 8606199624 The fix for JAGab39939 (omfmtent produces illegal directory entries for entries with null values) has caused omshowcda to display the directory mask to be displayed differently. CR: JAGad69036 SR: 8606199850 The cause of the corrupted Korean, Japanese and Simplified Chinese strings was due to an internal formating error. CR: JAGad69543 SR: 8606200362 A coding defect within the item.browse binary resulted in a failure while mime encoding a message. CR: JAGad70640 SR: 8606201464 Some scripts supplied with OM-APPL specified the full path name for the 'cut' command. They needed to be enhanced to support a different location on some OS versions. CR: JAGad70641 SR: 8606201465 The scripts vvice and vvysnc where not updated for OpenMail B.07.00 periodic patches CR: JAGad71090 SR: 8606201916 Hidden items within the message store were included within the item count when listing the tray or folder areas. CR: JAGad71959 SR: 8606202785 The mime browsing library only expects to be dealing with message components in a serialised file. There are occasions when the components of a message are not serialised - when this is the case the browse of that item returns nothing. CR: JAGad74578 SR: 8606205403 The MIME header is slightly strange inasmuch as the value is separated from the tag by two spaces. For example: Content-Transfer-Encoding: base64 This causes the MIME generation routines (in some circumstances) to misinterpret the MIME header field value. In this particular case the MIME header has come in from outside of OpenMail and is being retained in the inetMessageHeader object file associated with the message. CR: JAGad74715 SR: 8606205540 A coding error resulted in the mhsORAddress and omAddress attribute being mapped only to the the Openmail S, S-TX, G and G-TX attributes for the modify:replace option. Consequently, when building the OpenMail modification data, only the former surname and givenname attributes were deleted and 2 values were supplied for OU1 and other modified attributes. CR: JAGad75038 SR: 8606205863 When processing ORNs, omaddent converts to T61 and then breaks the ORN down into a set of T61 substrings. This may mean adding some bytes (T61 characters) at the start of each substring. For non-T61 values, these bytes are later removed before the value is stored in the directory. This defect was also removing bytes whose values are the same as the T61 characters, but which were not added by the initial parsing. CR: JAGad75517 SR: 8606206344 The code that constructs the command output was erroneously attempting to dereference a pointer whose value was NULL. CR: JAGad75975 SR: 8606206802 Sendmail modifies entries of the form user/"test to "user//"test" . Openmail takes this and assumes that the second " ends the quoted text, then the third quote opens further quoted text and the To: input can become out of sync. Further, it becomes possible for mangled addresses to be greater in size that that expected causing a serious error to occur. CR: JAGad79081 SR: 8606209895 A coding defect in the IMAP Server does not take any account of the special chars in OM Personal Names as input and therefore fails to map them into those they represent. CR: JAGad80029 SR: 8606210842 The child process IDs were corrupted within the process ID configuration file due to incorrect file locking mechanisms CR: JAGad83734 SR: 8606214543 UAL Checklist searches on the internet address field, and records in the DL the entries with alternatives/duplicates. Later it reprocesses the DL, re-searching to get the alternatives in a new file, which is then appended to the DL. However, the re-search is on the X400 attributes, not on the internet address, and the alternatives file is not created. But the attempt to append continued anyway, and tried to open a non-existent file. PHSS_23490: CR: JAGab39939 SR: 8606100957 The parser does not take into account the case when there is an attribute name but no attribute value. CR: JAGab68963 SR: 8606102906 When a Repeat Reminder is set, the message is placed in the message list DEFER.UA by the UAL. While calculating the next submission date-time of the message, the final reminder date is calculated based on the current date and the value of the current reminder. If the next submission date of the reminder message is less than the final reminder date, then the message is placed on the Service router for routing. Otherwise it is deleted from the message list, so that no more repeat reminders will be sent. But since the final reminder date is calculated using the current date the submission date is ALWAYS less than the final reminder date. CR: JAGad31664 SR: 8606162348 The Outgoing Internet Gateway is confused by addresses that can be generated by the cc:Mail client, such as : "S=Friendly Name .gren/OU1=mime/ DDT1=RFC-822/DDV1=Friendly Name / INTERNET-ADDR=Friendly Name " =========================================================== A coding defect in the ux component tries to enclose the "Comment " within angle brackets <>, by only inserting a start bracket < at the beginning, before passing it to Sendmail, resulting in unmatched brackets, which naturally generates a Sendmail error. CR: JAGad35090 SR: 8606165799 The algorithm used to select the approprate user's message store to restore selects the last message store that matches just the name part of the user's address. CR: JAGad40563 SR: 8606171299 The Root-URL is used initially when sending back the Location: header on signon. The SERVER-PROTOCOL environment variable is used to construct part of the URL. It appears that the Apache web server sets the SERVER-PROTOCOL variable to HTTP/1.0 regardless of whether you are talking HTTP or HTTPS, however it identifies the fact that we are talking HTTPS by setting the environment variable HTTPS="on" CR: JAGad41471 SR: 8606172211 A segmentation fault occures when parsing a blank line at the top of the mnMapFile which is located in the var/opt/openmail/sys directory. CR: JAGad42968 SR: 8606173711 A design defect in the mim component restricts the search for an internet address within an ORN to the ordinary DDA fields of the ORN. However an 8-bit address is stored in a teletex DDA-TX field, which is ignored by this search and so the internet address is effectively discarded. CR: JAGad43052 SR: 8606173797 The IMAP daemon was not converting MIME subject before copying an item into the OpenMail message store. CR: JAGad44030 SR: 8606174784 The item browser fails to convert UTF8 to ISO8859_1 when a message is in MIME format, even though a converter exists. It recognises that a converter exists, but fails to convert the UTF8 characters to UCS2 first in the case of the MIME format. The conversion is then incorrect. In the case of non MIME text, this two stage conversion is completed successfully. UNICODE conversions for MIME formatted messages are not generally supported in OpenMail and so the 2 step conversion required had not been implemented. CR: JAGad45429 SR: 8606176189 When the rule name is read from the OpenMail Auto-Actions file, tcl expects the format of the string to be UTF-8. OpenMail does not store the rule names in UTf-8 format, thus if the rule name is modified in anyway then it becomes corrupted. CR: JAGad45449 SR: 8606176209 When a folder is listed (UAL_PRPLST/UAL_LIST) any messages in the list that not have TextPreview data setup get it dynamically generated. This causes the ModifiedDate in the ctner to be updated. This updated ModifiedDate in the ctner means that the sync. process treats this as a conflict. The fix is to suppress the ModifiedDate update for this behind-the-scenes modification. As far a synchronisation goes the TextPreview is a 'computed' field, dynamically created in an offline store and is not synchronised data- so this change is good both architecturally and pragmatically. CR: JAGad45880 SR: 8606176642 The attempted encoding of a ' ' character followed by a 'n' as the 1015 and 1016 characters of a line in an html attachment resulted in the premature abort of the item.browser and a subsequent segmentation violation. CR: JAGad46439 SR: 8606177205 The General Text handling code at the incoming X400 interface was written on the assumption that the interchange charset for non-Latin-1 single byte languages would be based on an ISO8859_n charset, as used in General Text bodyparts. When the Czech version of OpenMail was done, it was decided to use T61BASE as the interchange charset. However, the X400 incoming mapper was not changed to properly convert and map the bodyparts. CR: JAGad46896 SR: 8606177664 A coding defect in the ux component tries to run off the end of the temporary file holding the Multipart/Signed part of the Sendmail message, when this part has missing end-boundaries of composite contents types, Multipart or Message. CR: JAGad47713 SR: 8606178486 ) omtidyu -l, -t and -w options - wildcards may get confused in MB. The * character is assumed to be the wildcard character in all cases. This may not be so for certain MB strings. 2) Username incorrectly displayed if it contains TX fields. The display routine does not take the address group separator 027 into consideration. 3) The -l option is not displayed. This is an enhancement request. 4) The error/usage string is not displayed if not options are specified. A check to no parameters is not done. 5) The -q option does not work. The reporting mechanism displays a full report if a SUMMARY report is not requested, rather than if a FULL report is requested. 6) The msg type selection is not output. This is an enhancement request. 7) The -f option no longer includes WB. In GR7, the -T w option is used to display the waste basket CR: JAGad48103 SR: 8606178878 Some changes introduced to omdosur as part of the 5.20 MAPI work, was failing to take into account the possibility of a missing container. CR: JAGad50818 SR: 8606181602 When the OMGUI processes a reply, it takes the Distribution List of the original message and supplies it to UAL Checklist, requesting Lookup of the 167 attribute in the UnixMap directory for ORNs that have a group 5 internet address field. Messages received from GR7 may contain the internet address of Openmail users as well as of internet users. If the GR7 internet addresses are not present in the directory of the server where the reply is constructed, the 167 lookup will fail to find a match. The code then assumes the recipient is an internet user and adds the address of the internet Gateway to the ORN. CR: JAGad52689 SR: 8606183476 When the relay is heavily loaded, it creates one or more child relay processes to share the incoming requests. The child processes later stop when they have been idle for a while (30 seconds by default). The select error can occur when the parent is processing the Termination signal from the child, if the signal is received between when the code decides to look for input from the child (FD SET) and doing the select. After hitting this error, the code does not explicitly stop the child relay processes, but does wait for them to die. As the child processes may be waiting for instructions from the parent, a hang can occur. CR: JAGad55411 SR: 8606186206 The segmentation violation in the Notification Monitor is caused by dirty data in a buffer which then causes a buffer under-run or over-run to then occur. This dirty data appears to be generated by a large number of deregistrations for notifications which happens when the RCI is shut down and timing problems cause a write to the buffer to be killed thus generating the dirty data which is then read. The current write is in two stages with the possibility that the process can be terminated inbetween these two writes. CR: JAGad56484 SR: 8606187277 Currently the client does not set up a filter on the Outlook delegate redirection to prevent private items being redirected. The best solution to this problem is to change the server code so that by default a private Outlook meeting request will NOT be redirected to a delegate. This behaviour can be overridden by the LD_SENSITIVE_ITEM_DELEG_REDIR=TRUE config option (user.cfg and general.cfg) CR: JAGad56620 SR: 8606187413 Subject is not currently matched (via user-supplied script) if the subject of the message is null (blank). The fix is to change the code to allow a blank subject to be matched. The old behaviour will be reinstated by setting the RSL_MATCH_BLANK_SUBJECT=FALSE general.cfg option. CR: JAGad57754 SR: 8606188546 Porting changes for Linux have caused a problem with the EINTR signal handling to become visible in the syslog. EINTR signal handling corrected so that this interrupt is silently swallowed. CR: JAGad58840 SR: 8606189626 The failure to download the directory was caused by a buffer overflow when reading in a large directory entry in order to pass them to the client. CR: JAGad63387 SR: 8606194177 The cause of this failure was due to incorrectly parsing the Content-Disposition response header which sometimes resulted in corrupted memory. CR: JAGad64229 SR: 8606195023 The patch installation scripts contained hard-coded exit codes of 0, 1 and 2, instead of the preferred $SUCCESS, etc. Also, there were some cases where values other than 0, 1 or 2 could be returned. CR: JAGad64671 SR: 8606195467 in.imap41d was going into a spin in the function imapsearch because although conn->state was set to TERMINATED when the ual socket had died this was not checked for. CR: JAGad66344 SR: 8606197150 ~openmail/release.sys/smtpd.cfg was replaced by an unconfigured file during patch installation. It is now edited so it contains a domain name. This is similar to the work done during initial B.07.00 installation. SR: 8606160818 8606162150 8606180347 8606196695 8606198411 8606199624 8606199850 8606200362 8606201464 8606201465 8606201916 8606202785 8606205403 8606205540 8606205863 8606206344 8606206802 8606209895 8606210842 8606214543 8606100957 8606102906 8606162348 8606165799 8606171299 8606172211 8606173711 8606173797 8606174784 8606176189 8606176209 8606176642 8606177205 8606177664 8606178486 8606178878 8606181602 8606183476 8606186206 8606187277 8606187413 8606188546 8606189626 8606194177 8606195023 8606195467 8606197150 Patch Files: /opt/openmail/patch/filesets/OM-ADM /opt/openmail/patch/filesets/OM-AMECAT /opt/openmail/patch/filesets/OM-AMEICE /opt/openmail/patch/filesets/OM-AMEPAW /opt/openmail/patch/filesets/OM-AMEPSS /opt/openmail/patch/filesets/OM-APPL /opt/openmail/patch/filesets/OM-BB /opt/openmail/patch/filesets/OM-CHSICE /opt/openmail/patch/filesets/OM-CHSPAW /opt/openmail/patch/filesets/OM-CORE /opt/openmail/patch/filesets/OM-DESK /opt/openmail/patch/filesets/OM-DSYNC /opt/openmail/patch/filesets/OM-ENGCAT /opt/openmail/patch/filesets/OM-ENGICE /opt/openmail/patch/filesets/OM-ENGPAW /opt/openmail/patch/filesets/OM-ENGPSS /opt/openmail/patch/filesets/OM-FINICE /opt/openmail/patch/filesets/OM-FINPAW /opt/openmail/patch/filesets/OM-FREICE /opt/openmail/patch/filesets/OM-FREPAW /opt/openmail/patch/filesets/OM-GERICE /opt/openmail/patch/filesets/OM-GERPAW /opt/openmail/patch/filesets/OM-IMAP4 /opt/openmail/patch/filesets/OM-ITAICE /opt/openmail/patch/filesets/OM-ITAPAW /opt/openmail/patch/filesets/OM-KORICE /opt/openmail/patch/filesets/OM-KORPAW /opt/openmail/patch/filesets/OM-LC /opt/openmail/patch/filesets/OM-LDAP /opt/openmail/patch/filesets/OM-MAN /opt/openmail/patch/filesets/OM-NIPICE /opt/openmail/patch/filesets/OM-NIPPAW /opt/openmail/patch/filesets/OM-PMOVER /opt/openmail/patch/filesets/OM-POP3 /opt/openmail/patch/filesets/OM-PTBICE /opt/openmail/patch/filesets/OM-PTBPAW /opt/openmail/patch/filesets/OM-RC /opt/openmail/patch/filesets/OM-SMS /opt/openmail/patch/filesets/OM-SPAICE /opt/openmail/patch/filesets/OM-SPAPAW /opt/openmail/patch/filesets/OM-SWEICE /opt/openmail/patch/filesets/OM-SWEPAW /opt/openmail/patch/filesets/OM-UNIX /opt/openmail/patch/filesets/OM-WEBADM /opt/openmail/patch/filesets/OM-X400 /opt/openmail/patch/ompatch /opt/openmail/patch/PHSS_24875/omunpatch /opt/openmail/patch/PHSS_24875/ompatch.idx what(1) Output: /opt/openmail/patch/filesets/OM-ADM: No what strings /opt/openmail/patch/filesets/OM-AMECAT: No what strings /opt/openmail/patch/filesets/OM-AMEICE: No what strings /opt/openmail/patch/filesets/OM-AMEPAW: No what strings /opt/openmail/patch/filesets/OM-AMEPSS: No what strings /opt/openmail/patch/filesets/OM-APPL: No what strings /opt/openmail/patch/filesets/OM-BB: No what strings /opt/openmail/patch/filesets/OM-CHSICE: No what strings /opt/openmail/patch/filesets/OM-CHSPAW: No what strings /opt/openmail/patch/filesets/OM-CORE: No what strings /opt/openmail/patch/filesets/OM-DESK: No what strings /opt/openmail/patch/filesets/OM-DSYNC: No what strings /opt/openmail/patch/filesets/OM-ENGCAT: No what strings /opt/openmail/patch/filesets/OM-ENGICE: No what strings /opt/openmail/patch/filesets/OM-ENGPAW: No what strings /opt/openmail/patch/filesets/OM-ENGPSS: No what strings /opt/openmail/patch/filesets/OM-FINICE: No what strings /opt/openmail/patch/filesets/OM-FINPAW: No what strings /opt/openmail/patch/filesets/OM-FREICE: No what strings /opt/openmail/patch/filesets/OM-FREPAW: No what strings /opt/openmail/patch/filesets/OM-GERICE: No what strings /opt/openmail/patch/filesets/OM-GERPAW: No what strings /opt/openmail/patch/filesets/OM-IMAP4: No what strings /opt/openmail/patch/filesets/OM-ITAICE: No what strings /opt/openmail/patch/filesets/OM-ITAPAW: No what strings /opt/openmail/patch/filesets/OM-KORICE: No what strings /opt/openmail/patch/filesets/OM-KORPAW: No what strings /opt/openmail/patch/filesets/OM-LC: No what strings /opt/openmail/patch/filesets/OM-LDAP: No what strings /opt/openmail/patch/filesets/OM-MAN: No what strings /opt/openmail/patch/filesets/OM-NIPICE: No what strings /opt/openmail/patch/filesets/OM-NIPPAW: No what strings /opt/openmail/patch/filesets/OM-PMOVER: No what strings /opt/openmail/patch/filesets/OM-POP3: No what strings /opt/openmail/patch/filesets/OM-PTBICE: No what strings /opt/openmail/patch/filesets/OM-PTBPAW: No what strings /opt/openmail/patch/filesets/OM-RC: No what strings /opt/openmail/patch/filesets/OM-SMS: No what strings /opt/openmail/patch/filesets/OM-SPAICE: No what strings /opt/openmail/patch/filesets/OM-SPAPAW: No what strings /opt/openmail/patch/filesets/OM-SWEICE: No what strings /opt/openmail/patch/filesets/OM-SWEPAW: No what strings /opt/openmail/patch/filesets/OM-UNIX: No what strings /opt/openmail/patch/filesets/OM-WEBADM: No what strings /opt/openmail/patch/filesets/OM-X400: No what strings /opt/openmail/patch/ompatch: $Header: sh_patch.gen /main/gr7_patch/2 2001/05/25 1 9:57:32 pl $ /opt/openmail/patch/PHSS_24875/omunpatch: $Header: sh_unpat.gen,v /opt/openmail/patch/PHSS_24875/ompatch.idx: No what strings cksum(1) Output: 2563010459 867870 /opt/openmail/patch/filesets/OM-ADM 123293032 217298 /opt/openmail/patch/filesets/OM-AMECAT 3527150296 11625 /opt/openmail/patch/filesets/OM-AMEICE 187311781 3002 /opt/openmail/patch/filesets/OM-AMEPAW 140089432 22204 /opt/openmail/patch/filesets/OM-AMEPSS 105824458 178043 /opt/openmail/patch/filesets/OM-APPL 3319223691 83447 /opt/openmail/patch/filesets/OM-BB 238726588 11569 /opt/openmail/patch/filesets/OM-CHSICE 2825477539 2985 /opt/openmail/patch/filesets/OM-CHSPAW 2894316148 11775686 /opt/openmail/patch/filesets/OM-CORE 2982144279 107753 /opt/openmail/patch/filesets/OM-DESK 799011246 174294 /opt/openmail/patch/filesets/OM-DSYNC 1674303856 217296 /opt/openmail/patch/filesets/OM-ENGCAT 3790901248 11602 /opt/openmail/patch/filesets/OM-ENGICE 2235330151 3005 /opt/openmail/patch/filesets/OM-ENGPAW 795982391 22201 /opt/openmail/patch/filesets/OM-ENGPSS 2755330426 11592 /opt/openmail/patch/filesets/OM-FINICE 2544443159 2995 /opt/openmail/patch/filesets/OM-FINPAW 2530289775 11568 /opt/openmail/patch/filesets/OM-FREICE 3584823076 3002 /opt/openmail/patch/filesets/OM-FREPAW 3281301337 11564 /opt/openmail/patch/filesets/OM-GERICE 2906193592 2997 /opt/openmail/patch/filesets/OM-GERPAW 966295597 82283 /opt/openmail/patch/filesets/OM-IMAP4 330946973 11595 /opt/openmail/patch/filesets/OM-ITAICE 4148776937 2994 /opt/openmail/patch/filesets/OM-ITAPAW 86296471 11541 /opt/openmail/patch/filesets/OM-KORICE 747298057 2990 /opt/openmail/patch/filesets/OM-KORPAW 4132779009 721406 /opt/openmail/patch/filesets/OM-LC 1996253070 84127 /opt/openmail/patch/filesets/OM-LDAP 3312224094 6906 /opt/openmail/patch/filesets/OM-MAN 3121064114 11616 /opt/openmail/patch/filesets/OM-NIPICE 1057547640 2987 /opt/openmail/patch/filesets/OM-NIPPAW 2222530952 63342 /opt/openmail/patch/filesets/OM-PMOVER 3112748287 24599 /opt/openmail/patch/filesets/OM-POP3 2242362813 11570 /opt/openmail/patch/filesets/OM-PTBICE 3086417870 2989 /opt/openmail/patch/filesets/OM-PTBPAW 1213499564 477008 /opt/openmail/patch/filesets/OM-RC 103652571 208071 /opt/openmail/patch/filesets/OM-SMS 2266880193 11595 /opt/openmail/patch/filesets/OM-SPAICE 675133638 2984 /opt/openmail/patch/filesets/OM-SPAPAW 1310431551 11607 /opt/openmail/patch/filesets/OM-SWEICE 2706322921 3006 /opt/openmail/patch/filesets/OM-SWEPAW 4241761766 129578 /opt/openmail/patch/filesets/OM-UNIX 1645463432 717023 /opt/openmail/patch/filesets/OM-WEBADM 2204386602 1020766 /opt/openmail/patch/filesets/OM-X400 839793273 26586 /opt/openmail/patch/ompatch 4120277454 11249 /opt/openmail/patch/PHSS_24875/omunpatch 245439138 87529 /opt/openmail/patch/PHSS_24875/ompatch.idx Patch Conflicts: None Patch Dependencies: None Hardware Dependencies: None Other Dependencies: None Supersedes: PHSS_23490 Equivalent Patches: PHSS_24876: s700: 11.00 11.04 11.11 s800: 11.00 11.04 11.11 PFSS_17032: sparcSUN: 5.6 5.7 5.8 PASS_17032: AIX: 4.3 PLSS_17036: intelLinux: RedHat7.0 Patch Package Size: 17220 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_24875 5a. For a standalone system, run swinstall to install the patch: swinstall -x autoreboot=true -x match_target=true \ -s /tmp/PHSS_24875.depot By default swinstall will archive the original software in /var/adm/sw/patch/PHSS_24875. 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_24875.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_24875.depot of=/dev/rmt/0m bs=2k Special Installation Instructions: SUBSYSTEM_SHUT ================================================= PHSS_24875: ================================================= CR: JAGad75038 SR: 8606205863 ------------------------------- Directory entries that have been affected by the defect should be rewritten with the correct values. A way to force the republishing the FreeBusy info. is for the user to do the following in Outlook: Tools/Options/Preferences tab - Calendar Options - FreeBusy Options - Set publish months... to 0 and hit OK - FreeBusy Options - Set publish months... to what is was before (eg 2) and hit OK This will cause the FreeBusy info to be rewritten to the server. NOTE: OpenMail must be shutdown before installing this patch. ---------------------------------------------------------- This patch will need the following minimum disk space requirements: /opt/openmail/patch : 60 MB NOTE: ServiceGuard Installations will need twice this amount. ----------------------------------------------------------