Patch Name: PHSS_18282 Patch Description: s700_800 10.X OpenMail B.06.00 June 99 Periodic Patch Creation Date: 99/05/26 Post Date: 99/06/03 Repost: 99/07/30 A problem has been discovered with superseding patch PHSS_18905. It introduces a defect whereby a cc:Mail user will not be able to forward or reply to a message containing a Microsoft RTF attachment. PHSS_18282 does not exhibit this problem and is being re-released until a replacement patch is available. 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-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-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_18282 Symptoms: 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. 1653304717: The Item Browser fails when the filename of an attachement contains a semi-colon (;). The Item Browser crashes causing a Bus Error. Defect Description: 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. 1653304717: A coding problem in the Item Browser caused the attachment filename containing a semi-colon to be truncated after the semi-colon. This then caused the truncated filename not to be found and the Item Browser to crash. SR: 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-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-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_18282/omunpatch /opt/openmail/patch/PHSS_18282/ompatch.idx what(1) Output: /opt/openmail/patch/filesets/OM-ADM: 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-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.37 99/05/26 12:55:13 tonyn Exp $ /opt/openmail/patch/PHSS_18282/omunpatch: $Header: sh_unpat.gen,v /opt/openmail/patch/PHSS_18282/ompatch.idx: No what strings cksum(1) Output: 3129695677 1151143 /opt/openmail/patch/filesets/OM-ADM 1401750173 571458 /opt/openmail/patch/filesets/OM-APPL 1348848825 219187 /opt/openmail/patch/filesets/OM-BB 191557057 197263 /opt/openmail/patch/filesets/OM-CCMOB 304221976 14231004 /opt/openmail/patch/filesets/OM-CORE 3143566525 381629 /opt/openmail/patch/filesets/OM-DESK 343038079 353314 /opt/openmail/patch/filesets/OM-DSYNC 1156105545 487408 /opt/openmail/patch/filesets/OM-IMAP4 3495032392 1785397 /opt/openmail/patch/filesets/OM-LC 2008569280 290763 /opt/openmail/patch/filesets/OM-LDAP 784288166 11535 /opt/openmail/patch/filesets/OM-MAN 3159238758 2285 /opt/openmail/patch/filesets/OM-NIPCAT 1391838729 14283 /opt/openmail/patch/filesets/OM-NIPWEB 4268670589 966894 /opt/openmail/patch/filesets/OM-NOTES 589339575 144023 /opt/openmail/patch/filesets/OM-PMOVER 4094420483 408248 /opt/openmail/patch/filesets/OM-POP3 471698872 3379967 /opt/openmail/patch/filesets/OM-RC 3047686645 415305 /opt/openmail/patch/filesets/OM-SMS 2377534381 358737 /opt/openmail/patch/filesets/OM-UNIX 1025815591 1122110 /opt/openmail/patch/filesets/OM-X400 2549052299 31305 /opt/openmail/patch/ompatch 571320865 16543 /opt/openmail/patch/PHSS_18282/omunpatch 663258287 70512 /opt/openmail/patch/PHSS_18282/ompatch.idx Patch Conflicts: None Patch Dependencies: None Hardware Dependencies: None Other Dependencies: None Supersedes: None Equivalent Patches: PHSS_18283: s700: 11.00 s800: 11.00 PASS_17005: AIX: 4.2.1 4.3 PFSS_17005: sparcSUN: 5.5.1 5.6 Patch Package Size: 26100 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_18282 5a. For a standalone system, run swinstall to install the patch: swinstall -x autoreboot=true -x match_target=true \ -s /tmp/PHSS_18282.depot 5b. For a homogeneous NFS Diskless cluster run swcluster on the server to install the patch on the server and the clients: swcluster -i -b This will invoke swcluster in the interactive mode and force all clients to be shut down. WARNING: All cluster clients must be shut down prior to the patch installation. Installing the patch while the clients are booted is unsupported and can lead to serious problems. The swcluster command will invoke an swinstall session in which you must specify: alternate root path - default is /export/shared_root/OS_700 source depot path - /tmp/PHSS_18282.depot To complete the installation, select the patch by choosing "Actions -> Match What Target Has" and then "Actions -> Install" from the Menubar. 5c. For a heterogeneous NFS Diskless cluster: - run swinstall on the server as in step 5a to install the patch on the cluster server. - run swcluster on the server as in step 5b to install the patch on the cluster clients. By default swinstall will archive the original software in /var/adm/sw/patch/PHSS_18282. 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_18282.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_18282.depot of=/dev/rmt/0m bs=2k Special Installation Instructions: SUBSYSTEM_SHUT =========================================================== 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 /var/opt/openmail/B.06.00.00/tmp directory. 4. Execute the command, /sbin/chlevel -L "system" /var/opt/openmail/B.06.00 .00/tmp ---------------------------------------------------------- This patch will need the following minimum disk space requirements: /opt/openmail/patch : 76 MB NOTE: ServiceGuard Installations will need twice this amount. ----------------------------------------------------------