Patch Name: PHSS_19172 Patch Description: s700_800 10.X OpenMail B.06.00 August 99 Periodic Patch Creation Date: 99/07/31 Post Date: 99/08/18 Hardware Platforms - OS Releases: s700: 10.20 10.24 10.30 s800: 10.20 10.24 10.30 Products: OpenMail B.06.00 Filesets: OpenMail.OM-ADM,B.06.00 OpenMail.OM-AMECAT,B.06.00 OpenMail.OM-APPL,B.06.00 OpenMail.OM-BB,B.06.00 OpenMail.OM-CCMOB,B.06.00 OpenMail.OM-CORE,B.06.00 OpenMail.OM-DESK,B.06.00 OpenMail.OM-DSYNC,B.06.00 OpenMail.OM-ENGCAT,B.06.00 OpenMail.OM-IMAP4,B.06.00 OpenMail.OM-LC,B.06.00 OpenMail.OM-LDAP,B.06.00 OpenMail.OM-MAN,B.06.00 OpenMail.OM-NIPCAT,B.06.00 OpenMail.OM-NIPWEB,B.06.00 OpenMail.OM-NOTES,B.06.00 OpenMail.OM-PMOVER,B.06.00 OpenMail.OM-POP3,B.06.00 OpenMail.OM-RC,B.06.00 OpenMail.OM-SMS,B.06.00 OpenMail.OM-UNIX,B.06.00 OpenMail.OM-X400,B.06.00 Automatic Reboot?: No Status: General Superseded Critical: No Path Name: /hp-ux_patches/s700_800/10.X/PHSS_19172 Symptoms: PHSS_19172: CR: JAGab32489 SR: 5003454785 When Transient DRS children timeout, there are situations where the DRS could abort. CR: JAGab34013 SR: 1653286757 The unix.in process is not able to process some messages sent by outlook express. The error in omshowlog: SERIOUS ERROR Internet Mail (Incoming ) 10.29.98 07:09:04 [OM 10250] Process about to terminate due to error. Signal (Segmentation Violation) trapped by process 29848; code = 0. Procedure trace follows: < - ux_InStrCaseCmp -> ux_InStrCaseCmp < - ux_InStrCaseCmp -> ux_InParseArpaList -> mim_ScanArpaStrForSpecialChar < - mim_ScanArpaStrForSpecialChar -> mim_SpaceTrimming < - mim_SpaceTrimming -> ux_InConvArpaORNToORN ... The message will remain in the sendmail queue until it has expired. It is related to the layout of the email-addresses: "< \"< \\"Sandrina Hernou\\"\"" < shernou@bru-hub.dhl.com> Too many of these will fail the unix.in process. CR: JAGab34149 SR: 1653305789 A kind of corrupt message in outtray, which lacks real data for a DL, can cause omcpinu to fail with bus error. CR: JAGab34153 SR: 1653306381 If an autoforward is set to a non-existant Internet user on a remote machine, the NDN can loop forever between sendmail and Openmail. CR: JAGab34175 SR: 1653308544 Delivery Acks sent from HP Desk and destined for an X400 user, are not accepted by a Microsoft Exchange MTA. CR: JAGab36232 SR: D500428383 Viral cleaning capability required for OpenMail. CR: JAGab36250 SR: D500429423 The following commands do not work on Solaris : omresetmn omaddmnmp ommodmnmp omdelmnmp omshowmnmp The output of the commands is similar to : OMBINDIR/bin/omshowmnmp: function: not found CR: JAGab36271 SR: D500430249 Orphans containing "MAPI 1.0 embedded message" created by some tnef files going through unix.in. This only happens after the June 99 PP. CR: JAGab36273 SR: D500430413 If the UAL test harness is used in simple list mode and an item in a list does not have a creator specified, then on Solaris, and perhaps AIX, the test harness may abort with a segmentation violation. CR: JAGab37632 SR: 1653308734 Gapi fails with OM_TEMPORA_ERROR when it encounters attachments from Internet and also RFC2157 compliant. CR: JAGab39965 SR: 8606100966 When listing files that contain blank lines, the Openmail cd browser may duplicate said lines. CR: JAGab49811 SR: 8606101415 The UAL cannot connect to a local Directory Relay Server in Simple Service Guard configurations. CR: JAGab67687 SR: 8606102175 A new defect was introduced with the July OpenMail periodic patches. If a cc:Mail user receives a message from an Outlook user that contains an RTF attachment (by default an Outlook user will send RTF text), then any attempt to reply to or forward that message will fail. Instead you will get a cc:Mail error dialog box containing the text: 'The file conversion did not succeed [Codes: 1501:0:0] [SRC\UAL.C"207]' You cannot then forward that message. If you try to reply to it, everything may appear to be as expected but a body part of the message received is missing. PHSS_18905: 5003444174: Corruption in the DIT upsets OpenMail very seriously, but problems do not become visible until more damage is done. 1653299818: omdbmon process occassionally aborts with a SYS 22 error D500427419: Performance improvement D500427443: Inefficient code path in the source D500427435: Inefficient code paths D500427427: Excessive function calls in the openmail code. D500429431: An interim enhancement to partially address 1653240598. Aim for 20% (heavily system dependent) reduction in elasped/cpu time. D500428334: Unix Gateway fails while trying to decode TNEF 1653221341: It needs to be made clear that processes accessing a directory before omdiropt has completed will continue to use the original directory, not the new one. D500427906: Att names decoded from TNEF sometimes mismatch attachments. D500429530: No 3 requirement for SR 1653229252 not included in May PP. 3. at 'Attach Local File' window, the icon label "tenpu" (attach) is already used in 'New Message' window. We recommend that this be changed to "tenpu jikkou". D500428839: When omdref is used with a Direct Reference belonging to the Bulletin Area folder (i.e. has item type -70), an error occurs, and the following output is displayed Failed to open parent of 3/2407: The file-id/item-number supplied is invalid: it must be greater then zero 1653286120: If a coding error in cd.browse causes it to crash, a blank attachment, rather than an error message, can result. D500413104: With multiple queues, the possibility that a message obsoleting a previous message may arrive before the message it will replace. This is particularly the case if the replacement message is being used to cancel the message (it will therefore be smaller and is more likely to overtake the original). This is not a completely new problem (it could happen with sendmail) but is more likely now as there are more points at which it could happen. The Samsung client makes use of this feature. D500427914: Multibyte filenames handled incorrectly when extracted from winmail.dat 1653294579: MIME encoded internet messages originating from a MAPI client often contain an attachment of type : 'application/ms-tnef' This contains information about MAPI properties of the original message. It may also contain attachments to the message. By default, the OpenMail internet gateway saves the whole of this attachment in a file called "WINMAIL.DAT". Clients using pre-OpenMail MAPI B.05.20 service providers expect this WINMAIL.DAT file, however, they do not expect it to contain attachments and do not recognise them. Similarly, non-MAPI clients only recognise a WINMAIL.DAT file and do not know that attachments to the original message are encoded inside them, effectively data loss. The OpenMail internet gateway can be configured to work better with OpenMail MAPI B.05.20 service providers and later by setting the general.cfg option : UX_PRE_5_20_COMPATIBILITY_MODE=FALSE If this is set, the information from the 'application/ms-tnef' attachment is extracted into an object file, except for original message attachments encoded in it, which are extracted as separate attachments to the message. 1653300889: The outbound unix gateway was using the content originator as the SMTP envelope originator. This meant that if the envelope originator (aka Return-Path:) was different from the content originator (aka From:) then the envelope originator was simply discarded. 1653305979: If the SR_RESOLVE_MASK general.cfg option is being used then any redirection that occurs in order to send Outlook calendar meeting requestes to delegates will fail to be delivered to teh delegate. A Non-delivery notification gets generated instead and returned to the original meeting request sender. 1653302042: Receipt acks going back to Exchange via X.400 have the ORN part of the message id stripped. This causes the ack to be not matched when received by the Exchange system. See the submitter text for more details. D500427898: Certain messages from the Openmail Notes Gateway that contain 8-bit characters cause the X400 Gateway to fail to process the message. 5003463190: Items in a folder or bulletin board which have been placed there using the Outlook client's "post" functionality cannot be read using cc:Mail 1653301507: After the B.05.10 October 1998 periodic patch has been installed, a a designate with appropriate capabilities can no longer delete items from a bulletin board. 1653287946: Bulletin board synchronisation messages arriving out of order can cause synchronisation failures. Example : Message 1 for : 'Add Item A'. Message 2 for : 'Delete Item A'. If 'Message 2' arrives before 'Message 1', Item A will be added and will never be deleted. Previously, the problem text of this SR documented another scenario which could result in synchronisation problems. This has been entered as a new SR - see D500427351. 1653300392: If a network problem occurs while some big file is being attached to a message in a Web Client 5.10 session, the user is not able to access his mailbox until the processes on the server are killed by the administrator. D500415729: For the OpenMail Web Client (B.05.00), the size is not displayed on sending when a file has been attached to the message. 1653302414: mt_transfer failure error when Single Asn encoded bodyparts found in the message D500425553: When ITO uses omacmd to call omopcsm or omadmr, there is often a SEGVIOLATION. 1653308759: MSMail messages to Internet recipients non-delivered by Internet gateway PHSS_18282: D500418079: If some permissions are set (using Outlook) on a private folder these permissions are lost if the folder is moved (but retained if the folder is copied). D500426809: If local.delivery is not retaining the message to delivery it into the InTray then only the first AA_REDIRECT record gets processed. D500426841: There are circumstances where the Container flag BB_HAS_ACL gets unset when it shouldn't. The effect of this is that if some explicit permissions are assigned to a folder these permissions will be ignored when calculating the access caps. of that folder (eg. for delegate access). 1653287953: If an item is added to a bulletin board and almost immediately deleted. 2 synchronisation messages are created. If these arrive out of order, the item may be added and NOT deleted, because the first message attempts to delete an item which does not exist. This SR asks for a higher level of warning to be associated with the failed deletion so that this situation can be detected. omshowlog -l 7 should show a message similar to : [OM 23989] Bulletin Board Synchronisation has attempted to DELETE an item that doesn't exist yet on this system. See related SR 1653287946. 1653297937: A bulletin board changelog entry is not written when a basic item is dragged from a container OUTSIDE the bulletin board into the bulletin board. D500426189: Segmentation violation by ual.remote causes socket disconnection failure reported at Outlook user interface. The trace shows that a large number of notifications (relating to BBs and BB items) are being generated in a short space of time. This high frequency of notifications is causing a segmentation violation in the code that registers that notifications are waiting for the client. D500426130: A user performing what is essentially a read-only operation can cause notifications to be raised on BBs abd BB items. These unnecessary notifications can have an impact on performance on systems where a large number of Outlook (and/or IMAP) users are accessing the Public folders (BBs in OpenMail terms). D500427070: When base exists and filter does not the return code should be 0 with no entries returned, but the return code is 32. 32 should only be returned if the base entry does not exist. D500426965: The remote Outlook delegate capabilities check protocol supported by advmail.sckd does not work properly on the AIX and Solaris platforms: AIX - Segmentation violation --- Solaris - returns incorrect 'send-on-behalf-of' setting for user. ------- 1653297986: Forwarded messages whose internal message comprises of a distribution list only (no first text part or other attachments) will cause the Internet gateway unix.out program to abort on Solaris machines if UUENCODE routes are used. On HP-UX, a mal-formed message is generated teminating with the line : Encoding: D500426163: Default BB ACL/permissions don't allow new items to be added by an Outlook client. The default permissions for an Outlook client should be: visible,read,create,sub-folder but instead they are: visible,read,sub-folder Other clients (eg. OMGUI, cc:Mail) are not affected. 1653299024: X400 inmappper does not strip external attributes of FROM addresses. 1653256966: Under certain conditions, the Openmail Lotus Notes Gateway can truncate long domain names for Notes users. 5003450593: The problem is that when the -g option is set the -I option fails to work correctly. The problem can be shown by first setting up an dirsync agreement with the -I option set but not -g :- 1) omaddds -e -l DIRA -x DIRB -m "+DIRSYNC/hppwdj95" 2) omaddds -i -l DIRA -x DIRB -m "+DIRSYNC/hppwdj95" -t "990101 00:00" -P 1 -I 3) omaddent -d DIRB -e "S=Tester/G=A/OU1=Pinewood/OU2=hppwdj95/PHONE-1= 333" * Restart Dirsync * ~ Entry appears in DIRA with 'PROPAGATED-BY=209' ~ 4) ommodent -d DIRA -e "S=Tester" -n "PROPAGATED-BY=400" 5) ommodent -d DIRB -e "S=Tester" -n "PHONE-1=666" * Wait for sync to take place * ~ Entry in DIRA is modified to PHONE-1=666 (Correct) ~ Now if you modify the agreement to also use the -g option :- 1) ommodds -i 1 -g "S/G/OU1" * Restart dirsync * 2) ommodent -d DIRB -e "S=Tester" -n "PHONE-1=888" * Wait for sync to take place" ~ Entry fails to be propagated ~ The error message sent to the ENU states that :- Entry not in the Directory or Propagated By Identifier differs. If the PROPAGATED-BY attribute is set back to its original value for the entry in DIRA then changes are made to the entry in DIRB then these changes are propagated correctly. 1653297242: MIME filenames derived from T.61 subjects are truncated at the first space, however, MIME filenames derived from either the original filename or the Subject of an item can contain a space. This is inconsistent. 1653231563: Acknowledgements are sent marked "urgent" by OpenMail. A way of configuring this so that they are either sent with the same priority as the original message or sent with a specific acknowldegement level would be desirable. For instance, a general.cfg option like : AK_ACK_MSG_PRI=0 could be used to force all acknowledgements to be sent with normal priority. (valid values : 0, 1 (non-urgent) and 2 (urgent)) In addition, the following configuration option could be used to tie the priority of the acknowledgement message to be the same as the that for the message being acknowledged : AK_ACK_SAME_PRI=TRUE AK_ACK_SAME_PRI takes precedence over AK_ACK_MSG_PRI, although under some circumstances, the priority of the message isn't known at the time an acknowledgement is being generated and the AK_ACK_MSG_PRI setting is used. D500401539: FREE/BUSY detail information is not available when referring to a schedule of users who have multi-byte names. 1653229252: Miscellaneous enhancements to the OpenMail Web Client : 1. at 'New Message' window, the nuance of the Japanese label "ma-ji" (merge) does not seem to portray the nuance of the action. It is better if the label is changed to "atesaki" (destination), to show the user he can select a destination when he clicks this icon. 2. at 'Merge Distribution List from Distribution List Folder' window, again the nuance of the label "ma-ji" is not appropriate. It could be better as "atesaki torikomi" than "ma-ji jikkou" 3. at 'Attach Local File' window, the icon label "tenpu" (attach) is already used in 'New Message' window. We recommend that this be changed to "tenpu jikkou". 4. at 'New Message' window, icon label "sakujo" (delete) is what the program does to the message. For the user, it is better to be "kyanseru" (cancel) in Katakana, for a better feel that the user is in fact cancelling the message he is creating. D500337337: When IBM extended characters in SJIS portion (0xfa40-0xfefe) entering OpenMail (UNIXJIS -> OMJIS), some of them are illegally entering OpenMail, so the specification need to be cleared and the code need to be fixed - either to accept IBM extended chars or not. D500426155: unix.in creates an orphan for each TNEF-encoded nested message it processes. D500425934: The tidy-up routines called at the end of a UAL session can cause a segmentation error. 5003446914: The OpenMail command ommoddir can be used to set the Directory Change Log Life, and so can the Directory Synchronisation commands 'omaddds -n' and 'ommodds -n'. Internally, these 2 log life values are held in different places. The man pages for omaddds and ommodds do not explain the interaction between these 2 log life settings, or how to reduce the log life. Further the 'omaddds -n' command cannot be used to set the log life to less than the default value of 7. This is not explained. D500424820: Missing FROM line in MDN/DSN messages 5003453712: Ux gateway closes down when it gets a 571 return from SM. It should just give a fail responce and carry on. D500417568: If a message with an incorrect addressee is sent into Openmail via any 'incoming connection' protocol, e.g. SMS2000I, no NDN is returned. D500401547: Distorted preview of message is shown in Intray if body text of the message starts with English and then Japanese characters follow. D500399246: Internet gateway can produce incorrect sender addresses 5003406132: It is possible to build omscan with the '-N' linker option. This will allow omscan to have access to the 'text' internal memory segment, as well as the 'data' internal memory segment. This means that the should have access to more memory during run-time, and so maxdsize can be bigger. 5003448654: If a message is sent to an address of the format: //ex/us/mci/scjmail/rfc-822/root@beast.mayfield.hp.com ie. No name and no OU's but just CAPO attributes and DDA fields the Service Router will attempt to resolve the name even though there is a valid route for the mailnode //ex/us/mci/scjmail. In certain circumstances this can cause huge delays in the processing of the message. This problem applies to any routable ORN that does not contain a Surname field. D500426676: Server general.cfg: UXI_TREAT_AS_MIME_SUBJECT=T UXI_UNIX_MAIL_CHARSET=UNIXJIS UXO_MIME_OMIT_DEF_CTENC_HDR=T UXO_MIME_SUBJECT_ENCODING=B UXO_MIME_SUBJECT_BENC_NONASCII=T UXO_MIME_SUBJECT_FOLDING=T UXO_MIME_TEXTFILE_ENCODING=N Clients: Outlook Express J, Outlook 98 Internet mode J, Pocket Outlook Express These clients generate ISO-2022-JP + B-encoding filename and name fields. OpenMail can accept those filenames well, but the outgoing Internet G/W lower cases the B-encoding filename, so as a result, the filename will be garbage. For some clients, it is not possible to download the file, probably because of the filename corruption. 1653299974: A certain kind of Lotus CD document makes cd.browse loop. D500428029: Paper clip marks appear in Inbox when messages are sent as Plain Text and contain multi-byte characters in the body part, despite no attached files exist in the messages. This happens with Japanese Outlook98, MAPI-SP5.30(beta) and Windows 95 and NT4.0. D500426882: If a non-openmail file is found when scanning the sub domain in omscan and it happens to be the first file in the directory the an attempt to record the item is made with no item information available. D500428953: The details listed for a newly attached message generated as a result of a notification do not have the 'unread' flag set. This causes the client (Outlook) to display the message as already being read. D500428821: Netscape creates the mime message with no trailing blank lines, which can be seen in the mime blob in the message store. The Item browser then ADDS a blank line at the end of the text message! Netscape then correctly says that the message is altered. D500293266: omdirex import filters ending in a ")" character make omdirex fail. For instance, (OU1=pine)&(OU1=wood) A UAL error (4500,3,16030) is reported. The 16030 means mismatched parenthesis. D500427344: This problem asks for a more comprehensive fix to the problem addressed in SR 1653287953. If an item is added to a bulletin board and almost immediately deleted. 2 synchronisation messages are created. If these arrive out of order, the item may be added and NOT deleted, because the first message attempts to delete an item which does not exist. omshowlog -l 7 should show a message similar to : [OM 23989] Bulletin Board Synchronisation has attempted to DELETE an item that doesn't exist yet on this system. BUT, additional information should be supplied which will allow the administrator to determine which Bulletin board the item could not be deleted from and the message-id of the item. See related SR 1653287946. D500421016: omscan's orphan processing phase can now be frozen in memory to avoid impacting other processes, and re-started at a later time. To freeze omscan : kill -s SIGUSR2 ##### where ##### is the parent omscan process (there are 2 processes) To unfreeze omscan : kill -s SIGUSR2 ##### D500429050: The LDAP minidit example shuts down and restarts the slapd server, as it changes the configuration. In some case, the script could think that slapd had shutdown before it actually had, causing the subsequent startup to fail. The main affect of this is when the minidit is run repeatedly, as in the autotests. 5003444901: omscan is terminating early with an 'ILLEGAL INSTRUCTION'. The last thing that was logged was : SERIOUS ERROR Administration(omscan ) 12.18.98 03:45:21 [OM 10250] Process about to terminate due to error. Signal (Illegal Instruction) trapped by process 288914; code = 0. Procedure trace follows: <- scn_RecordItem -> im_FName2ItemRef -> GetFNameElements <- GetFNameElements -> GetElementIndices <- GetElementIndices -> os_str2ul <- os_str2ul -> os_str2ul <- os_str2ul -> im_FormFullItemRef <- im_FormFullItemRef <- im_FName2ItemRef -> scn_GetRecordedItem <- scn_GetRecordedItem -> scn_RecordItem D500428318: VirtualVault - If an alias is specified for the DEFAULT-OMSERVER or OMSERVER field in the change root environment, Web Client 6.0 returns an error [SYS 1]Not owner. Currently only IP addresses are accepted. D500428326: VirtualVault - The ownerships of the files in the change root environment should be changed to bin:hpoffice, wherever possible. 5003445072: After mulitple replies to a message from ccMail through the Openmail Notes Gateway to Notes, the text becomes double-line spaced. 1653303784: In patches to OpenMail B.05.10 after PP4 (B.05.10.D0) the following problem occurs. Create a new message Attach a local file to this message. In the web page that is then displayed, there is a table with attachment information. The field for the size of the new attachment contains just the letter K. It should contain the size of the attachment in kilobytes. In more general terms, the %%KSIZE%% token used to return the size of the attachment is blank. D500429183: notif.mon tries to allocate space for a huge number of file descriptors because AIX says it can have that many. D500429175: On AIX version 4.3, the ldap tools, ldapadd, ldapsearch,..., fail to connect to the host. This message is produced: ldap_bind: Can't contact LDAP server To date, this problem has only shown up on AIX 4.3 plus Y2K patches. However, the OpenMail defect could in principle have caused a similar problem on 4.3 without patches. Defect Description: PHSS_19172: CR: JAGab32489 SR: 5003454785 The method the DRS uses to detect that a transient child has exited, is not robust enough. CR: JAGab34013 SR: 1653286757 Unix incoming gateway was unable to split the addresses in the Arpa Distribution List in some messages from Outlook Express. CR: JAGab34149 SR: 1653305789 omcpinu was unable to handle the situation properly when there isn't a corresponding BASIC_DATA for a BASIC_ITEM of Distribution List in the input data. CR: JAGab34153 SR: 1653306381 In some cases an NDN from the Internet will come into Openmail with a "Mail From" set to "< >". This is not handled well within the Openmail Internet gateway. CR: JAGab34175 SR: 1653308544 The Openmail Desk gateway cannot map the X400 Per-recipient flags of a message from X400, to an equivalent HP Desk Transaction file record. So, when an acknowledgement is generated by the Desk gateway, the the TFR_FULL_ACK TF record is not set up correctly. CR: JAGab36232 SR: D500428383 Added Viral Cleaning capability to service.router CR: JAGab36250 SR: D500429423 omresetmn, omaddmnmp etc are all scripts (actually the same script with different names) This script uses /bin/sh as its shell, but the shell in this location on Solaris is an extremely old implementation of the Bourne shell which does not support functions. CR: JAGab36271 SR: D500430249 Attachments that only contain "MAPI 1.0 embedded message" signify an embeded message follows and should be deleted. CR: JAGab36273 SR: D500430413 ualth's simple list mode assumes that there is a string representing the creator of an item for every item in the list. In fact, if there isn't a creator, this string is set to null and should not be referenced. CR: JAGab37632 SR: 1653308734 X.400 code limits GraphicStrings up to a maximum of 16 octets. The PDU contains a GraphicString of 23 octets which caused the overflow error. CR: JAGab39965 SR: 8606100966 The fix for 5003445072 triggered an existing problem in the code. CR: JAGab49811 SR: 8606101415 If there was no global/config file present on the installation, OpenMail assumed that the machine was not running in a ServiceGuard environment. CR: JAGab67687 SR: 8606102175 Converter errors which were previously ignored were now being noticed and incorrectly handled by the cc:Mail UAL access code. PHSS_18905: 5003444174: customer missunderstandings lead them to corrupt their message stores. OpenMail attempted to recover from this when it is in fact better to halt processing imediately. 1653299818: The problem may be caused by spurious error number returned even when the entry is valid. Should only check error number if no valid entry is returned. D500427419: reducution in openmail cpu usage. D500427443: reduce openmail cpu usage. D500427435: reduction in openmail cpu usage. D500427427: reduce openmail cpu usage D500429431: An interim enhancement to partially address 1653240598. Aim for 20% (heavily system dependent) reduction in elasped/cpu time. D500428334: Unix gateway has problem decoding TNEF files 1653221341: If services are not re-started after omdiropt, changes to the directory are not noticed by them and this can result in un-necessary time spent by support staff trying to track down why changes aren't being noticed. D500427906: TNEF att names mismatched if the att name followed the att data in the tnef file D500429530: Japanese Web client needed to improve the localisation. D500428839: The problem is caused by an attempt to read details from the parent of the specified direct reference. If no parent exists, as is the case for the Bulletin Board, then the read fails. 1653286120: When external converter crashes, no proper action is taken to inform the user and system administrator. This was causing the problem that users see a blank item in the message. D500413104: message order cannot be guarenteed. OpenMail does not retain obsolete message information to check future messages. D500427914: Filename characterset not used 1653294579: The way MAPI properties are represented in OpenMail messages has changed, causing a backwards compatibility problem. 1653300889: This was a coding problem with the unix gateway. This code, written in 1994, gave precedence to content-originators over envelope-originators for deciding a suitable SMTP envelope-originator. The original code had never been tested to make sure that it was correct (note that the envelope originator and content originator of practically all OpenMail messages is exactly the same). 1653305979: The SR_RESOLVE_MASK general.cfg option causes a recipient redirection record to be added even when a name that is re-resolved has not changed. This causes the improved redirection loop detection introduced with the 5.30 changes (GR5/PP-Dec 1998) to treat this as a loop and generate a NDN. 1653302042: Receipt acks going back to Exchange via X.400 have the ORN part of the message id stripped. D500427898: When a Notes users name contains 8-bit characters, the Openmail Notes Gateway encodes it into teletext form and does not produce a degraded, printable form. Thsi causes problems for the X400 Gateway. 5003463190: Outlook posted items are stored in the OpenMail message store as messages without any distribution list. The cc:Mail client cannot access messages whose first body part is not a distribution list 1653301507: When the delegate tries to access bulletin board items, he only has read access, where he should have Read, Attach, Modify and Delete access. 1653287946: Store and forward transport mechanisms such as OpenMail and SendMail do not guarantee that messages will arrive in the same order as they were sent. If a Del-Req for an Item arrived on the Importing Server because of a possible Message ReOrder by SendMail, currently Del-Req is ignored by the BB-Server as 'Trying to Delete an Item NOT Existing' and the Request is ignored. But the Add for the corressponding Item arriving later to Del-Req will Add-Item on the Importer hence leaving BB Servers out of sync. 1653300392: For the same user ID and profile, all the sessions for Web Client 5.10 use a single user program to handle their requests. If the user program is busy with some command, then the other sessions will not be able to run any command during that time. Moreover, no new sessions can be started for the user. D500415729: The UAL API returns an empty string for the Total KBytes. 1653302414: The end of contents octets were not read for single asn encoded body parts which causes this problem when there are more than one such body part. D500425553: Both the omopcsm and omadmr binaries have sections of code that sometimes pass NULL pointers into expressions. This situation tends to cause SEGVIOLATION on SUN boxes. The situations that occur are valid and the code has been updated to handle them. 1653308759: A check was introduced to the Mime handling code which dis-allowed addresses which did not contain DDT's. This was introduced in the B.06 version of OpenMail. PHSS_18282: D500418079: The code to remove an ACL file when a container is detached is placed at too low a level within the ctner access routines. This means that it gets invoked when a move is done as the move is really an attach followed by a delete. D500426809: If the redirected message is not to be retained in the Inbox then only the first AA_REDIRECT gets recorded and actioned. D500426841: The BB_HAS_ACL flag in the Inbox container is being unset by a subsequent UAL_MODITM call to change the ListMAPIProps on the Inbox. This is because the UAL List record for the zeroth record (which is a copy of the ctner record) is not being updated with the BB_HAS_ACL flag when the Inbox ACL (permissions) are initially added. 1653287953: Failed deletion synchronisations are currently ignored. 1653297937: A check of whether the new item being added was in the bulletin board or not was incorrect. The source container was checked instead of the target container. D500426189: A buffer being used to receive notification prompts from the Notification Monitor is to small to receive all the data being read into it if many outstanding notifications prompts are in the pipe. D500426130: There are some places in the code where ctner records are updated when this is either unnecessary for BB items or the update is legitimate but should cause a notification to be raised for a BB item. D500427070: Incorrect return code from LDAP server for certain failed searches D500426965: The call to uald_GetDelegCaps in uakd_main.c needs to pass a pointer to the UAL command buffer structure. It is automatically dereferenced on HP-UX but not on AIX or Solaris. 1653297986: The core dump on Solaris occured because the Encoding string was NULL as it hadn't been set up for the non-existent body-part. The gateway should not have tried to write an "Encoding:" string but it did, and the access to this NULL string resulted in the core dump. D500426163: This problem is caused by a change to GR5 not being rolled to top-of-tree correctly. ACL_FLDR_PERM_CREATE permissions are missing from the default Outlook-style permissions. 1653299024: When the tweak X4I_STRIP_ALL_RECIPS or X4I_STRIP_ALL_DL_RECIPS are set, external attributes should be stripped from FROM addresses even if the FROM addresses are not in the active recipient list. External attributes were being stripped only for active recipients. 1653256966: The Notes documentation specifies that these should be 32 characters, but does not police this and actually supports more. The Openmail Lotus Notes Gateway was implemented to the specification. 5003450593: The reason the -I option doesn't work with the -g option in this case is that the search filter specified by the -g option has PROPAGATED-BY attached to it automatically which means that any change of value of PROPAGATED-BY means that the entry will not be matched and a non-fatal error raised. 1653297242: Different OpenMail clients place different information in the subject field. It is not necessarily the filename of an item. The code that attempts to form a filename from a T.61 subject was written at a time when internet mailers which could not handle filenames containing spaces were common. The code is thus over zealous in trying to remove spaces from the potential filename. 1653231563: Acknowledgements are sent marked "urgent" by OpenMail. A way of configuring this so that they are either sent with the same priority as the original message or sent with a specific acknowldegement level would be desirable. For instance, a general.cfg option like : AK_ACK_MSG_PRI=0 could be used to force all acknowledgements to be sent with normal priority. (valid values : 0, 1 (non-urgent) and 2 (urgent)) In addition, the following configuration option could be used to tie the priority of the acknowledgement message to be the same as the that for the message being acknowledged : AK_ACK_SAME_PRI=TRUE D500401539: The routine that maps a mailnode to a host name does not handle TTX variants of mailnodes correctly. 1653229252: Some aspect of the Japanese localisation of the Web Client needed improvment. D500426155: unix.in is not tidying up its temporary files thus creating the occasional orphan. D500425934: ual_DeleteList in ual_access.c can be called repeatedly to close the same UAL List as part of the tidyup/shutdown activity at the end of a session. Any memory free'ed should set the pointers to NULL after the free so that a second entry does not free the memory again (illegally). 5003446914: The OpenMail command ommoddir can be used to set the Directory Change Log Life, and so can the Directory Synchronisation commands 'omaddds -n' and 'ommodds -n'. Internally, these 2 log life values are held in different places. The man pages for omaddds and ommodds do not explain the interaction between these 2 log life settings, or how to reduce the log life. Further the 'omaddds -n' command cannot be used to set the log life to less than the default value of 7. This is not explained. D500424820: unix.out does not output a From line for MDN/DSNs. 5003453712: There is no default action for 5* and 4* returns for SM. There should be. D500417568: Child processes spawned to handle incoming connections were trying to validate the name of the protocol that was configured for NDNs. They can't do this validation properly, because they have discarded all knowledge about protocols other than the incoming one they were spawned to handle. D500401547: RTF Preview call did not understand multibyte. D500399246: Parts of mime default mailnode left around with tnef mailnode 5003406132: omscan's design means that it needs the memory to store the item info of the entire message store in order to detect orphans, therefore it hits the limit when the message store is very large. 5003448654: A coding defect in the service router meant that routable ORNs without a Surname field were unnecessarily looked up in the directory. D500426676: A coding problem in the Internet gateway and MIME item browser cause content-type header fields to be converted to lower case when associating a character set with a text content type. 1653299974: A defect in cd.browse made it fail to fold a long line in some cases, and this was causing the consequence that cd.browse repeatedly processes the same record but does not move on. D500428029: T.61 text is not being treated as text when local.delivery set the 'MAPI attachment' flag in the msg container. D500426882: The problem is caused by the file information being recorded even if it is found to be a non-openmail file when scanning the data sub domain. D500428953: The code to update an existing list of items does not find out whether it is a BB list that is being updated - consequently the read/unread status is taken to be that of the new item rather than using the BB user sequence file to determine whether the item is new for this particular user. D500428821: The problem was caused by dodgy code in brw_mime.c -- the code set a flag to re-read a blank line even if no blank line had been read. D500293266: A problem in constructing the form of the filter required for submission to the UAL caused the final ")" character to be dropped from the UAL search request. D500427344: Failed deletion synchronisations are currently ignored. D500421016: The omscan orphan scanning process can take a long time and also slows down other OpenMail processes. D500429050: When checking that the omoff process has completed, the check erroneously included the username, which can vary. 5003444901: The problem is caused by the limit of 256MB maximum size of stack + data allowed by conventional segmentation on AIX being reached. (See Large Program Support Overview - from AIX 3.2.5 "info" command). D500428318: The DNS lookup files were not copied to the change root directory. The system could recognize only IP addresses and not aliases. D500428326: The file ownerships for the OpenMail files in the change root directory were changed to bin:hpoffice, wherever possible. User 'bin' does not have any permissions on the files owned by it. 5003445072: When ccMail quotes a line that is exactly full, it adds a trailing space. The cd.browser correctly identifies this as a line overflow and wraps the line, effectively adding a new line. 1653303784: There are 3 causes of this problem : 1 The UAL does not have the correct value for the size when the list command is done. 2 The UAL has a new optimisation for its datacomm which cuts down on sending un-necessary information. Thus, when the size is thought to be 0, no size information is transmitted at all. Before, the value 0 used to be transmitted. 3 The Web client has not been updated to reflect the change mentioned in cause 2. D500429175: The code called the select system call with Max FD set much larger than the readfds... array sizes. Consequently select failed, and the client could not get the result of its bind call to the server. SR: 5003454785 1653286757 1653305789 1653306381 1653308544 D500428383 D500429423 D500430249 D500430413 1653308734 8606100966 8606101415 8606102175 5003444174 1653299818 D500427419 D500427443 D500427435 D500427427 D500429431 D500428334 1653221341 D500427906 D500429530 D500428839 1653286120 D500413104 D500427914 1653294579 1653300889 1653305979 1653302042 D500427898 5003463190 1653301507 1653287946 1653300392 D500415729 1653302414 D500425553 1653308759 D500418079 D500426809 D500426841 1653287953 1653297937 D500426189 D500426130 D500427070 D500426965 1653297986 D500426163 1653299024 1653256966 5003450593 1653297242 1653231563 D500401539 1653229252 D500337337 D500426155 D500425934 5003446914 D500424820 5003453712 D500417568 D500401547 D500399246 5003406132 5003448654 D500426676 1653299974 D500428029 D500426882 D500428953 D500428821 D500293266 D500427344 D500421016 D500429050 5003444901 D500428318 D500428326 5003445072 1653303784 D500429183 D500429175 1653304717 Patch Files: /opt/openmail/patch/filesets/OM-ADM /opt/openmail/patch/filesets/OM-AMECAT /opt/openmail/patch/filesets/OM-APPL /opt/openmail/patch/filesets/OM-BB /opt/openmail/patch/filesets/OM-CCMOB /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-IMAP4 /opt/openmail/patch/filesets/OM-LC /opt/openmail/patch/filesets/OM-LDAP /opt/openmail/patch/filesets/OM-MAN /opt/openmail/patch/filesets/OM-NIPCAT /opt/openmail/patch/filesets/OM-NIPWEB /opt/openmail/patch/filesets/OM-NOTES /opt/openmail/patch/filesets/OM-PMOVER /opt/openmail/patch/filesets/OM-POP3 /opt/openmail/patch/filesets/OM-RC /opt/openmail/patch/filesets/OM-SMS /opt/openmail/patch/filesets/OM-UNIX /opt/openmail/patch/filesets/OM-X400 /opt/openmail/patch/ompatch /opt/openmail/patch/PHSS_19172/omunpatch /opt/openmail/patch/PHSS_19172/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-APPL: No what strings /opt/openmail/patch/filesets/OM-BB: No what strings /opt/openmail/patch/filesets/OM-CCMOB: 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-IMAP4: 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-NIPCAT: No what strings /opt/openmail/patch/filesets/OM-NIPWEB: No what strings /opt/openmail/patch/filesets/OM-NOTES: 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-RC: No what strings /opt/openmail/patch/filesets/OM-SMS: No what strings /opt/openmail/patch/filesets/OM-UNIX: No what strings /opt/openmail/patch/filesets/OM-X400: No what strings /opt/openmail/patch/ompatch: $Header: sh_patch.gen,v 6.39 99/07/20 12:29:52 gren Exp $ /opt/openmail/patch/PHSS_19172/omunpatch: $Header: sh_unpat.gen,v /opt/openmail/patch/PHSS_19172/ompatch.idx: No what strings cksum(1) Output: 2376576064 1139723 /opt/openmail/patch/filesets/OM-ADM 3014540662 208727 /opt/openmail/patch/filesets/OM-AMECAT 1535266694 572106 /opt/openmail/patch/filesets/OM-APPL 2437048181 216162 /opt/openmail/patch/filesets/OM-BB 3619120595 198178 /opt/openmail/patch/filesets/OM-CCMOB 3242469559 14448418 /opt/openmail/patch/filesets/OM-CORE 1396341 380877 /opt/openmail/patch/filesets/OM-DESK 386640961 341865 /opt/openmail/patch/filesets/OM-DSYNC 4010609812 208713 /opt/openmail/patch/filesets/OM-ENGCAT 1729569859 483729 /opt/openmail/patch/filesets/OM-IMAP4 2030838120 1741855 /opt/openmail/patch/filesets/OM-LC 1964711960 290938 /opt/openmail/patch/filesets/OM-LDAP 1284360 12723 /opt/openmail/patch/filesets/OM-MAN 4256880701 2280 /opt/openmail/patch/filesets/OM-NIPCAT 3253061835 14143 /opt/openmail/patch/filesets/OM-NIPWEB 2940929129 1620214 /opt/openmail/patch/filesets/OM-NOTES 1021914494 140285 /opt/openmail/patch/filesets/OM-PMOVER 2572840522 405396 /opt/openmail/patch/filesets/OM-POP3 253390766 3281830 /opt/openmail/patch/filesets/OM-RC 4061651415 414113 /opt/openmail/patch/filesets/OM-SMS 4059115190 355018 /opt/openmail/patch/filesets/OM-UNIX 4033916378 1104847 /opt/openmail/patch/filesets/OM-X400 3545428347 31327 /opt/openmail/patch/ompatch 796058149 16549 /opt/openmail/patch/PHSS_19172/omunpatch 2164774187 95753 /opt/openmail/patch/PHSS_19172/ompatch.idx Patch Conflicts: None Patch Dependencies: None Hardware Dependencies: None Other Dependencies: None Supersedes: PHSS_18282 PHSS_18905 Equivalent Patches: PHSS_19173: s700: 11.00 s800: 11.00 PFSS_17011: sparcSUN: 5.3 5.4 5.5 PASS_17011: AIX: 4.1.0 4.1.1 4.1.2 4.1.3 4.1.4 4.2 Patch Package Size: 27190 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_19172 5a. For a standalone system, run swinstall to install the patch: swinstall -x autoreboot=true -x match_target=true \ -s /tmp/PHSS_19172.depot By default swinstall will archive the original software in /var/adm/sw/patch/PHSS_19172. 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_19172.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_19172.depot of=/dev/rmt/0m bs=2k Special Installation Instructions: SUBSYSTEM_SHUT ================================================= PHSS_19172: ================================================= CR: JAGab36232 SR: D500428383 ------------------------------- Service Router Viral Cleaning Contact Commitment Request on comitreq@pwd.hp.com for more details. CR: JAGab49811 SR: 8606101415 ------------------------------- For Simple ServiceGuard installations of OpenMail, i.e. those which do not make use of a OMDATADIR/global/config file, setting of a new general.cfg tweak is required if using Outlook Free/Busy time functionality. Set GCL_SIMPLE_SG_PKG_NAME={SG package name} to declare the ServiceGuard package name for OpenMail. This will cause the Directory Relay Server to use the package name rather than the machine's hostname. Note: After setting this tweak, new entries put in the mailnode mapping file (OMDATADIR/sys/mnMapFile) by the Directory Relay Server will refer to this package name rather than a host name. But there may still be old entries which refer to the real machine name. So make sure that all servers have their mnMapFile updated either by running omresetmn, or by manually modifying the entries using ommodmnmp. =========================================================== PHSS_18905: =========================================================== 1653294579: ----------- To activate this feature, add UX_SPLIT_TNEF=TRUE to general.cfg. The winmail.dat file will then be decoded into attachments, but no object files etc will be created. 1653287946: ----------- Added Tweak BBS_DELLOG_RETENTION_PERIOD=value Specifies the Retention Period for delete log files. The value need to be defined in hours. Eg: if BBS_DELLOG_RETENTION_PERIOD is set to 10, it means that dellog files are retained for 10 hrs on the system from its creation time. DelLog files help in tracking message re-order in the case of Add/Del. The Retention period need to be defined b/w 1-24 else it is defaulted to 24. Need to ReStart BB Service if new value is added =========================================================== PHSS_18282: =========================================================== 1653256966: ----------- This patch installs new omrouter and omdirex binaries into the notes.inst directory under the Openmail binaries directory tree. To complete the installation, it is necessary to run the appropriate copy of the setup program for your platform as documented in the original Openmail Lotus Notes Gateway installation instructions. It is only necessary to setup the binaries & messcats if setup has been run before on the Domino installation, although running the full setup will not cause any harm. 1653297242: ----------- 2 new general.cfg settings are available : BRW_MIME_SPACE_OK_IN_FNAME UXO_MIME_SPACE_OK_IN_FNAME These cause the Pop3 / Imap4 servers and the Internet outgoing gateway to allow filenames inferred from the T.61 subject of a message to contain spaces. 1653231563: ----------- 2 new general.cfg options are available : AK_ACK_MSG_PRI valid values are : 0 (normal) 1 (non-urgent) and 2 (urgent) Determines the priority to use for acknowledgements if AK_ACK_SAME_PRI isn't set or the priority of the message being acknowledged isn't known. AK_ACK_SAME_PRI This causes the priority of an acknowledgement to be the same as that of the message being acknowledged. Note that under some circumstances, the priority of the message being acknowledged cannot be determined. For instance, clients which assume responsibility for generating acknowledgements and use the "MAIL ACK" UAL command. 5003448654: ----------- The default behaviour of the service router is changed in this patch. Routable ORNs that do not contain a Surname field are no longer looked up in the directory. To change the behaviour back to the original, set the general.cfg option SR_RESOLVE_IF_NO_PN=TRUE D500293266: ----------- This patch installs new omdirex binaries into the notes.inst directory under the Openmail binaries directory tree. To complete the installation, it is necessary to run the appropriate copy of the setup program for your platform as documented in the original Openmail Lotus Notes Gateway installation instructions. It is only necessary to setup the binaries & messcats if setup has been run before on the Domino installation, although running the full setup will not cause any harm. D500427344: ----------- When delete requests for non-existent items are processed an entry is written to file : ~openmail/sys/bb/failed.log Each entry contains the details of the attempted synchronisation request extracted from the synchronisation message's first text body part. D500421016: ----------- The Omscan program's orphan scanning phase can be temporarily suspended in memory by sending a SIGUSR1 signal to the parent omscan process e.g. kill -s SIGUSR1 ##### where ##### is the parent omscan process (there are 2 processes) It is worth checking STDERR. If "Freeze Signal Ignored" has been written to STDERR, you have either : i. sent the signal to the wrong process ii. omscan.orphans is not at a safe stage to freeze yet - try again later. If "Omscan Freeze Requested" has been written to STDERR, the signal has been noted and omscan will stop at the next convenient point. When that point is reached, "Omscan Frozen" is written to STDERR. To unfreeze omscan : kill -s SIGUSR2 ##### After this, "Omscan Unfrozen" should be written to STDERR. D500428318: ----------- The following steps should be performed BEFORE the installation of this patch on a VirtualVault system. IGNORE these steps for a non-VirtualVault system. 1. Ensure that you are signed on as the root. 2. Execute the command, /tcb/bin/setlevel -s "system" 3. Delete all the files from the OMDATADIR/tmp directory. 4. Execute the command, /sbin/chlevel -L "system" OMDATADIR/tmp ---------------------------------------------------------- This patch will need the following minimum disk space requirements: /opt/openmail/patch : 82 MB NOTE: ServiceGuard Installations will need twice this amount. ----------------------------------------------------------