Patch Name: PHSS_28591 Patch Description: s700_800 10.20 OpenMail B.07.00 March 03 Periodic Patch Creation Date: 03/02/11 Post Date: 03/03/04 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-CHSCAT,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-FINCAT,B.07.00 OpenMail.OM-FINICE,B.07.00 OpenMail.OM-FINPAW,B.07.00 OpenMail.OM-FRECAT,B.07.00 OpenMail.OM-FREICE,B.07.00 OpenMail.OM-FREPAW,B.07.00 OpenMail.OM-GERCAT,B.07.00 OpenMail.OM-GERICE,B.07.00 OpenMail.OM-GERPAW,B.07.00 OpenMail.OM-IMAP4,B.07.00 OpenMail.OM-ITACAT,B.07.00 OpenMail.OM-ITAICE,B.07.00 OpenMail.OM-ITAPAW,B.07.00 OpenMail.OM-KORCAT,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-NIPCAT,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-PTBCAT,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-SPACAT,B.07.00 OpenMail.OM-SPAICE,B.07.00 OpenMail.OM-SPAPAW,B.07.00 OpenMail.OM-SWECAT,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_28591 Symptoms: PHSS_28591: CR: JAGab82932 SR: 8606110229 When an Outlook created msg with embedded image, is sent over the Internet, the image is no longer visible to a recipient, on a non-Linux server, using Outlook. Instead, it is replaced by a BINARY file "Untitled Attachment" which is not executable, even if it is first saved as a file with the correct extension. In fact it is not even in the correct format for its application, Paintbox. Also occurs with embedded .XLS spreadsheets and probably any other type of file that can be embedded in the main msg body. It does not seem to happen with embedded Word .DOCs, probably because RTF is capable of representing these entirely. Problem does not appear when same msg is sent internally to OM recipient over OpenMail SMINTFC gateway or sent over the Internet to a recipient on a Linux server; the embedded image is visible just like it was sent out from Outlook. CR: JAGae50393 SR: 8606286454 The ~/sys/mime.types has no filetype for *.vsd or visio. The same problem for the AutoCAD file (.dwg). CR: JAGae52304 SR: 8606288373 UAL PUT_SYNC_CHANGES command processes an action file which is passed to it. If this action file contains records which are larger than 4096 byes, then the remote client interface may become corrupted. A typical symptom of this corruption is that the rci hangs and fails to return a reply. CR: JAGae52624 SR: 8606288693 There are some missing quotes in the OpenMail patch checkinstall scripts. All instances of the problem involve calls to awk imbedded in a backtick execution, such as `echo "$FSET_SIZES" | awk ' ... ... ` The shell expects the single quote after awk to be closed before the backtick is closed. At the moment, the closing backtick appears to end the awk sequence, so the scripts execute properly. But the scripts do need to be repaired in case the behaviour of the shell changes. CR: JAGae53719 SR: 8606289790 The Item Browser goes into a loop on any message containing a MIME body part with two (or more) non-consecutive MIME Content-Disposition Headers. This construct appears to be used by some emailers for embedding graphics in the main body of the message. However such constructs are at the very least ambiguous, and most probably invalid. It is open to individual Browsers on how they handle it, if at all. On GR6 this causes any IMAP browser to hang when the msg is viewed and the mailstore filestore to fill up with work files. For GR7, IMAP browsing is carried out using the newer Mime Browser which does not exhibit this problem. PHSS_28156: CR: JAGad93625 SR: 8606224537 There is no mechanism within omshut to remove ice.user sessions. This could cause problems for any process which requires all OpenMail processes to have terminated before continuing. CR: JAGae37593 SR: 8606273505 The incoming Internet Gateway, on receiving a msg with a MIME part with a non-ASCII filename, does not recognise the filename. This happens while it is working out the mapping, given in mime.types, from MIME contents-types to OM filetypes. The true filename is not lost, as it shows correctly in the stored msg by all the browsers; it is just not used in the filetype mapping, resulting in the MIME part being incorrectly mapped to be BINARY filetype. It works OK when the filename is in plain ASCII. CR: JAGae41797 SR: 8606277728 A message coming into OpenMail via the Internet gateway causes a segmentation violation and is put on the delayed queue to be retried later and to fail again. Error in log: SERIOUS ERROR Internet Mail (Incoming ) 09.10.02 06:55:09 [OM 10270] Process about to terminate due to error. Signal (Segmentation Violation) trapped by process 17922 Procedure trace follows: <- GetMailText -> StripCrNl <- StripCrNl -> ux_InParseCommandLine <- ux_InParseCommandLine -> GetMailText <- GetMailText -> StripCrNl <- StripCrNl -> ux_InParseCommandLine <- ux_InParseCommandLine -> GetMailText <- GetMailText -> StripCrNl <- StripCrNl -> ux_InParseCommandLine CR: JAGae41856 SR: 8606277792 After reading and processing incoming Bulletin Board messages, the BB Server waits unnecessarily and inconsistently before exporting the resultant synchronization requests to other servers, in 50% of cases depending on the whether an even number of messages were just read. By default, this delay could be up to 1 hour. CR: JAGae42370 SR: 8606278311 The incoming Internet gateway (unix.in) fails to decode the valid WINMAIL.DAT attachment (TNEF) of some messages. The TNEF is valid and should be converted at the Internet gateway into MAPI properties. These messages cause a warning to be logged: WARNING Internet Mail (Incoming ) 09.06.02 09:07:45 [OM.UX 1546] MAPI property within TNEF attachment is too big. The TNEF attachment may be corrupt. The WINMAIL.DAT attachment is retained and converted into a text attachment. This attachment seems to cause some clients problems when browsing the message (e.g. Netscape/IMAP hangs). This problem only occurs when the general.cfg tweak UX_PRE_5_20_COMPATIBILITY_MODE=FALSE is set (this is the default on GR7). CR: JAGae42811 SR: 8606278755 Some messages that originate from an OpenMail system cannot be moved from a PST to an Exchange server. They produce a "Can't move the items. The item could not be moved. It was either already moved or deleted, or access was denied." error. CR: JAGae43470 SR: 8606279417 A forwarded DL, containing long lines, probably resulting from comments in addresses and/or encoded non-ASCII char sets, which is forwarded on its own via the Internet Gateway, is corrupted at the recipient, with lines being truncated in the middle of addresses. The problem does not occur to the DL when the complete message is forwarded. CR: JAGae44306 SR: 8606280333 When attachments with common PC file extensions, like .PDF, .PS, .FM, .MPP, .ZIP are received from the outside Internet with unexpected, but not incorrect, MIME Contents Types, they are not recognised as being their correct filetype. The are treated instead as the BINARY filetype and therefore cannot always be selected from PC OMGUI and associated with their corresponding PC application, e.g. .PDF files are not always automatically passed on to Adobe Acrobat. PHSS_27679: CR: JAGad71050 SR: 8606201876 Symptoms: Downloaded quoted-printable .CSV (Comma Separated Values) file attachment to PC is missing carriage returns. Despite it being perfectly acceptable to MS Excel. Problem: OM does not know that .CSV files are really text files and therefore they need their newlines uprated to CRLF on PCs. CR: JAGae07887 SR: 8606238864 omcpinu with the '-e' option fails to correctly merge folders whose names contain multibyte data. CR: JAGae18540 SR: 8606254208 The check_relay feature of sendmail does not work when sendmail is invoked from omredirtcp. CR: JAGae24659 SR: 8606260336 The "man" page for omupdtis etc. gives the directory path containing the Item Structure Server database (default or otherwise) as "/var/opt/openmail/dir/../is/" in 3 places. Although this is correct, it is not clear to the reader that the UNIX directory convention of "../" is being used here to mean "the parent of". This is confusing and prone to be misinterpreted. CR: JAGae24724 SR: 8606260401 OpenMail does not support sendmail on AIX 5.1L. The sendmail.cf file is in a different location compared with AIX 4.x. In addition, omrc needs to check file permissions when sendmail versions later than 8.9 are in use. CR: JAGae26104 SR: 8606261785 The autotests imap_JAGae15283.u and imap_JAGae12028.u fail about 80% of the time on Linux because they run "StartSvc imap" immediately after "StopSvc imap" and the imap daemon fails to start. On HPUX11, running omoff -s imap followed by omon -s imap, several times in quick succession causes the state of the imap to fail to start properly. CR: JAGae27170 SR: 8606262840 When Bulletin Board changes are being synchronised - if a basic item (i.e. message content rather than a whole message) is added to a Bulletin Board and then deleted in the same email client session the ADD will be synchronised but the DELETE will not be. CR: JAGae31209 SR: 8606266965 omredirtcp sometimes cannot be restarted. It either fails silently or writes a "bind failed: Address already in use" error message to the syslog. CR: JAGae32060 SR: 8606267820 Some messages from Exchange to OpenMail contain incorrectedly encoded WINMAIL.DAT attachments. This illegal encoding can cause the unix.in process to abort with a segmentation violation. (This is another example of the problem described in JAGad95079.) CR: JAGae32230 SR: 8606267991 Mime Browser Controller terminates, without logging, when a client connection, ual.remote, goes away between requesting a browse and getting the reply. This most likely occurs when some user stops browsing in the midstream, on a heavily loaded system; maybe closing his client. Mime Browser Controller then chooses to terminate itself rather than service all the other many connections. CR: JAGae32345 SR: 8606268107 When a large number of users are connected to OpenMail on a machine running RedHat Linux, there are memory management problems resulting in segmentation violations and other errors. CR: JAGae33094 SR: 8606268859 A message with a "Mail from" command containing a comment-only email address coming into OpenMail via the Internet gateway causes a message with no originator to be generated. If this message is routed via the X.400 gateway it is rejected as an originator is a mandatory field. CR: JAGae33310 SR: 8606269075 When the outbound Internet gateway processes a message that contains recipients on both the TNEF and MIME routes the steering file used may be either the MIME one (~openmail/sys/mimeout.str) or the TNEF one (~openmail/sys/tnefout.str) depending on the order of the recipients. The message should be split in this case and the appropriate steering file used for each type of recipient. CR: JAGae33867 SR: 8606269632 Using PC Admin new PDL members cannot be successfully added. An OM16095 error is reported: "Illegal attribute type within compound value." The PDL member can be added successfully using the backend OpenMail 'omaddpdln' command. CR: JAGae35717 SR: 8606271509 On AIX 5.1L, the omrc command may give incorrect '[OM 10350] Warning: File system is full' messages. The message does not state which file system is meant to be full. CR: JAGae36951 SR: 8606272845 A message from an Internet user with a non-ASCII comment in his name cannot be successfully replied to when using the Outlook client. The reply is rejected at the Internet gateway with a 'Name cannot be mapped' error. A non-delivery report is returned. The same message can be successfuly replied to with the OMGUI client. PHSS_27061: CR: JAGad38110 SR: 8606168832 The Web Clients create temporary files under /var/tmp which may have world-writable permissions, and always have world-readable permissions. CR: JAGae05328 SR: 8606236267 omtclsh (used within the webadmin interface) could hang on Linux RedHat 7.2 CR: JAGae12028 SR: 8606245558 Using an IMAP client to copy/move a message from a local folder to an OpenMail folder leaves the new message with the user running the IMAP session as the message creator and an incorrect received date. This is only a problem if a non-IMAP client is subsequently used to read the message. CR: JAGae12031 SR: 8606245561 Using the ICE web client to log on to Openmail - as soon as you select a button or click on something in the Main Menu you get the logon page again with a SESSION EXPIRED error message. CR: JAGae17136 SR: 8606251070 Handling of the SIGCLD (SIGCHLD) interrupt changed at Dec. 2000 to make the code suitable for both SystemV and BSD unix variants. However this change has caused some problems now that the death of a child process is not ignored. These problems include: 1. ual.remote zombie process accumulating. 2. scripts no longer executable from TCL within web client page templates. 3. omredirtcp not invoking sendmail successfully in some circumstances. CR: JAGae18238 SR: 8606253906 When a new password is supplied as a result of an old password being either expired or pre-expired by the administrator the new password is not checked against any password composition rules set using omconfpwd. (This problem only occurs with OpenMail B.07.00) CR: JAGae19347 SR: 8606255018 It is not possible to configure the Internet gateway to produce simple inline RTF content without associated filename information. This filename info. often causes email clients to treat the RTF as an attachment. Configuration for this feature is possible when a multipart/alternative MIME structure is being generated. However a Content Disposition of 'inline' isn't configurable for a simple (non-multipart/alternative) content unless a 'filename' attribute is added as well. CR: JAGae22300 SR: 8606257997 When the Internet Gateway is configured to use the content T.61 subject as the MIME 'filename' a long T.61 subject can cause a Segmentation Violation in unix.out. CR: JAGae22536 SR: 8606258235 A badly formed RCPT TO: address of the form: ";"@dept.acme.com results in a looping unix.in process. CR: JAGae23835 SR: 8606259517 This is a problem in B.07.00 only When the IMAP_AUTOMATIC_MDN tweak is set to TRUE, the server does not automatically generate read acknowledgements. PHSS_26277: CR: JAGad84900 SR: 8606215723 The individual X.400 printable string attributes of a mail address, of all ORNs within a message, are being truncated to the size limits imposed by the X.400 Standard, by the incoming Internet Gateway. This can cause confusing and incomplete addresses in the ORN, particularly in the fields holding the Internet address. CR: JAGad95079 SR: 8606226007 Some messages from Exchange to OpenMail contain incorrectedly encoded WINMAIL.DAT attachments. This illegal encoding can cause the unix.in process to abort with a segmentation violation. CR: JAGad97183 SR: 8606228125 When a Service Router rule is set up to REJECT a message using the RECIPIENT-SERVICE-LEVEL criterion the non-delivery notification (NDN) generated incorrectly specifies the NDN reason as "Mailbox exceeds size limit". The correct text should be: "The message could not be delivered to the recipient as the service level for their mailbox doesn't allow that operation". CR: JAGad97593 SR: 8606228536 With Portal Access enabled, when a duplicate username is entered, the ICE Web Client 6.0 user program should display the Duplicate Usernames page containing a list of alternative names from which to pick the correct name. When used with a Web Client 5.10 profile, this list of alternative names is not displayed and the Duplicate Usernames page stalls at this point: Please select an alternative from: At GR6, the Duplicate Usernames page is not even displayed at all; the Logon page remains without any feedback that something is amiss. CR: JAGad98210 SR: 8606229157 general.cfg setting UAL_LOCAL_IGNORE_PASSWORD=TRUE does not work with GR7. If set a password is still required for local UAL clients (e.g omlist) that are run within the mailbox user's unix logon. CR: JAGae02798 SR: 8606233575 For some IMAP clients (e.g. Outlook Express) the date of messages in a sub-folder is the date the message was copied to the folder rather than the date the message was received. CR: JAGae03973 SR: 8606234784 There is a problem with omlogon and omlogoff on Linux. If the omlogoff command is issued to terminate a user session, followed by a omlogon command to start a new session, the omlogon is not always successful. The omlogon is able to recognise that there is no other user session running, and so doesn't fail to start. However, it then terminates the session which was starting, so that further commands such as omlist expect a username and password to be provided. If the omlist is part of an autotest, the test will hang until a password is manually provided. The problem does not occur if a sleep is placed between the omlogoff and the next omlogon. CR: JAGae03977 SR: 8606234788 If a ualth.sck call is made followed by a omlogon, then the omlogon call may fail. This failure seems to be intermittent - 50% of the time approx and only occurs on Linux RedHat 7.2. It is predominently a timing problem which goes away if a sleep is places between the 2 calls when part of an autotest. CR: JAGae06468 SR: 8606237428 omdosur fails with the error message "(OM 24602) Cannot create file" CR: JAGae07450 SR: 8606238426 The first mailnode created on a system is not always made the Primary Mailnode. Shown by absence of '**' in omshowmn output. Virtual Licensing assumes that this mailnode to be the Primary Mailnode, which it needs to refer to. As a result, Virtual License Server crashes, with Segmentation Violation, when trying to grant licenses that have been requested but not yet granted. May occur during start-up if the request was made while the system is shut down, or at the time of the request if system is up. PHSS_25647: CR: JAGad83534 SR: 8606214343 If an auto-redirect is enabled for a users inbox, then all other auto- actions are excluded from execution for that mailbox. CR: JAGad83915 SR: 8606214723 If, when creating an auto-forward rule using the PAW-client the user deletes the auto-forward covering text, local delivery fails to forward the message. CR: JAGad83932 SR: 8606214740 B.06 and B.07 This concerns the UAL Checklist command, when the flag is set to search the directory on the internet-addr (167) attribute. When more than one match is found, the command does not return the entries found as alternatives. This is unlike UAL Checkname, which does. This affects the OMGUI, for example. When entering the duplicate internet address into a DL, the behaviour varies depending on whether the Auto Name Checking option is on. If on, Checkname is used, and you see the X400 attributes of the entries. If off, you get an error when the message is Mailed. When you click on the name in error, you get a message that no alternatives can be displayed, or else you get an empty box that is supposed to show the alternatives. CR: JAGad84893 SR: 8606215716 If a message that contains an ORN with a DDVn field greater than the maximum 128 bytes, the X400 outgoing gateway correctly rejects this message, and will generate a non-delivery if appropriate. If the message is a return of contents (the normal type of non-delivery), then all subsequent messages that are not return of contents will be rejected by the gateway. An error 6019 appears in the omshowlog output for each rejected message. After a number of the 6019 errors (200 at most), the gateway will abort, with log output showing 'too many transaction files open'. CR: JAGad84922 SR: 8606215745 If no auto-reply text is provided for an auto-reply rule, then local delivery fails to send the auto-reply message. CR: JAGad87535 SR: 8606218386 B.07: omtidyu -B alters the last signon time of the user. In previous releases it did not. CR: JAGad87649 SR: 8606218500 Using the Outlook client delegate permissions cannot be set if the delegate has the Common Name (CN) attribute set. An error is displayed in the Outlook interface. CR: JAGad88671 SR: 8606219531 When the X400 outgoing gateway processes a message with a non-textual content item, and with GENERATE_FTPBP=TRUE in the ~sys/madmd.cfg file, x400.hpx.out leaks approximately 4Kbytes of memory on the message. The workaround is to stop and start the X400 gateway periodically, before the process fails with insufficient memory. CR: JAGad88889 SR: 8606219749 IMAP: rereading messages with many attachments can result in raw base64 encoded information being displayed. CR: JAGad89888 SR: 8606220752 Signatures which include 8-bit text will appear corrupted when added to the message body using the B.07.00 ICE client. CR: JAGad90057 SR: 8606220921 An Internet Ack which contains a NULL character will cause unix.in to fail. CR: JAGad90490 SR: 8606221356 Reading Non-Delivery Notifications for a non-english user (e.g. German) using an IMAP cleint (e.g. Netscape Navigator) gives text where the accented characters (e.g. umlaute) are displayed incorrectly. CR: JAGad90761 SR: 8606221627 Failure to check if enough memory is available before doing a write results in the corruption of the shared memory used by the notification server. The result of this is that local delivery and UAL remote abort. CR: JAGad91276 SR: 8606222161 omupdtis does not return an error result when interrupted. CR: JAGad93282 SR: 8606224187 The unix.out gateway, when processing tnef routed messages, should generate IDs for Mapi Named Properties, in the range 8000-FFFE. The gateway increments the ID each time that a named property is processed, generating IDs like 80000003, 8001000b, 80020003.... If the gateway runs for some time, the Named Property IDs become undefined, once FFFE has been reached. CR: JAGad93317 SR: 8606224222 The audit log only contains entries for successful signons. At B.06 unsuccessful signons (e.g. password wrong) were logged to the audit file with an indication of the signon error. CR: JAGad94573 SR: 8606225486 When connecting to the OpenMail message store via the Web Client 5.10 on a Virtual Vault machine with the portal access disabled, the error message "cannot connect to the specified host" is displayed. CR: JAGad94888 SR: 8606225815 The OpenMail daemons omvvrelay, ompop3, omimap and omportal (B.06.00) cannot be started or stopped manually by root in a VirtualVault 4.5 environment, due to root not having sufficient authorisation. CR: JAGad95463 SR: 8606226394 This applies to B.06 and B.07 of the Openmail Server. See also JAGad 94299, against the MAPI Service Providers. With the outgoing internet tnef gateway configured to convert rtf to text (tnefout.str), and with the /var/opt/openmail/sys/general.cfg option UXO_NO_RETAIN_IF_CONVERTED=TRUE set, 1) In Outlook/OpenMail begin to create a 'New Message'. 2) Add a Subject, an Exchange users name and some message text to the body. 3) Save and close the message. 4) Open message; add some more text and send it to the Exchange user. 5) The Exchange user receives a message with a blank message body. 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 An address list, such as a TO: field, may be corrupted if it contains a quote character ("). This occurs because of the way that sendmail converts the address and OpenMail subsequently parses it. In the following text, # is used to represent the character. If an entry has the format #", then sendmail quotes it and adds an extra to the #" sequence. So us#"er , becomes to "us##"er" , OpenMail then splits up the address list using commas as the separator. If a separator is in a quote, it is ignored. 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_28591: CR: JAGab82932 SR: 8606110229 A coding defect in the incoming Internet Gateway fails to take into account INTEL byte reversal of the integer field used to signify an OLE object, which it tests in order to determine whether to retain the object within the MAPI properties or to split it out into a separate attachment. CR: JAGae50393 SR: 8606286454 The Internet Gateway does not recognise these file types and treats them as of type BINARY. CR: JAGae52304 SR: 8606288373 The UAL_PUT_SYNC_CHANGES command fails on large messages due to the buffer size used for processing the message being exceeded. This means that the remote client reports a serious error and fails to complete the UAL command. CR: JAGae52624 SR: 8606288693 There were some missing closing quotes in awk statements in the checkinstall script (only used during patch installation on HP-UX). The missing quotes have been added. CR: JAGae53719 SR: 8606289790 A coding defect in the brw component attempts to read twice any subsequent MIME Content-Disposition headers, when it reaches EOF. PHSS_28156: CR: JAGad93625 SR: 8606224537 The omshut command does not currently remove ice.user processes which are still running. CR: JAGae37593 SR: 8606273505 A coding defect, in the Incoming Internet Gateway, did not decode encoded MIME filename parameters before looking up their filetype mappings. CR: JAGae41797 SR: 8606277728 The buffer used to hold a MIME header field is not big enough to hold the amount of data read in if the MIME header is garbled. CR: JAGae41856 SR: 8606277792 A coding defect, in the Bulletin Board Server, waits on the import queue for up to an hour, by default, once the import queue is empty before it exports synchronization requests, after having just read an even number of messages from the queue. When it reads an odd number, it immediately finds the queue empty and there is no delay. CR: JAGae42370 SR: 8606278311 The checking carried out on the validity of the TNEF is incorrect for some MAPI properties that exceed 512 bytes in length and a legal TNEF file is treated as being corrupt. An error is logged and the TNEF is converted to text to preserve it for further investigation. This binary file that is labeled as being textual can cause problems for some clients (e.g. Netscape/IMAP). CR: JAGae42811 SR: 8606278755 The problem message contain the PR_REPLY_RECIPIENTS_ENTRIES property with names associated with the OpenMail Address Book Provider. This information is unresolvable on the Exchange system and causes the messages to be rejected. To overcome this problem a new general.cfg option is introduced: PM_STRIP_MAPI_REPLY_RECIPS=TRUE Setting this option causes omcpoutu to strip out the MAPI properties that cause the migration problem. This user can then be restored and the message store copied to Exchange via a PST. CR: JAGae43470 SR: 8606279417 Forwarded DLs are always sent as MIME type 'application/x-openmail-1166' encoded as Quoted-Printable. A coding defect, in the Incoming Internet Gateway, did not decode the QP-encoded MIME part of type 'application/x-openmail-1166' before processing it. CR: JAGae44306 SR: 8606280333 The sending email system sends out some application type attachments, e.g. a .PDF file, under the MIME catch-all Content Type, 'application/octet-stream', whereas the Internet Gateway is only expecting a more specific Content Type; 'application/pdf' in this case. PHSS_27679: CR: JAGad71050 SR: 8606201876 The only file attachment that OM recognises as of type text are .TXT files. It is not told that .CSV files need treating in the same way with regard to newlines. CR: JAGae07887 SR: 8606238864 The failure to merge folders whose names contain multibyte data correctly was due to only the downgraded folder names being compared for matches, ignoring any existance of T61 folder names. CR: JAGae18540 SR: 8606254208 When sendmail is invoked from omredirtcp it is called with the -bs option for single execution. When this option is used the 'check-relay' functionality is not performed, so connections from IP addresses that should be rejected are allowed. To overcome this deficiency in the omredirtcp environment the -x option has been added to omredirtcp to allow a file of IP addresses to be rejected to be specified. See the omredirtcp MAN page for details. CR: JAGae24659 SR: 8606260336 Although obscure and indirect, the directory path: "/var/opt/openmail/dir/../is/" is strictly correct and in fact necessary, due to the possibility that "~openmail/dir" may be a symbolic link to a completely different location, and "is/" is always within the physical parent of the "~openmail/dir". This needs pointing out to the user by rewording the man page in 2 places. However, understanding the location of the ISDB is simply background information; it is not necessary for the use of these commands. CR: JAGae24724 SR: 8606260401 AIX 5.1L keeps the sendmail.cf files in /etc/mail. 8.9 is no longer the latest version of sendmail.cf, so omrc is changed to check certain file permissions for sendmail 8.9 or later. CR: JAGae26104 SR: 8606261785 The problem is caused by omon failing to wait for the Required state of a service to move from "disabling" to "disabled" before attempting to start a service. CR: JAGae27170 SR: 8606262840 The code that handles the delete of the item does not think that the newly added item is within a Bulletin Board as a this information has not been added to the transient record that represents the item in the BB list. CR: JAGae31209 SR: 8606266965 When omredirtcp fork/execs sendmail to handle an incoming SMTP connection the sendmail process inherits the SMTP socket. While the sendmail process is servicing this SMTP connection the SMTP socket cannot be re-established (the 'bind' call will fail). Therefore if omredirtcp is killed it cannot be restarted until all its sendmail children have exited. CR: JAGae32060 SR: 8606267820 The primary cause of the problem is the fact that the TNEF file after decoding from the MIME encoding (quoted-printable in this instance) is corrupt and contains field length information that points beyond the end of the TNEF data. The secondary problem is that the quoted-printable encoding of a TNEF attachment is illegal according to Microsoft's rules for this type of attachment. The fix detects when a TNEF attachment is not encoded as "base64" and logs an informative error to the OpenMail log. The TNEF file is decoded according to the general.cfg UX_PRE_5_20_COMPATIBILITY_MODE setting. If any corruption is detected the TNEF attachment will either be treated as a text attachment or the message will be rejected according to the general.cfg UXI_NON_DELIVER_BAD_TNEF setting. CR: JAGae32230 SR: 8606267991 A design defect, in the Mime Browser Controller, of shutting down immediately on encountering a SIGPIPE signal from any broken connections (client or child) out of its many connections. CR: JAGae32345 SR: 8606268107 The problems occur because ual.remote is built with thread support, even though each logged-in user has a separate copy. As similar problems could happen in the IMAP server, the MIME browser and the item browser, these components should be built without the use of threads. CR: JAGae33094 SR: 8606268859 When the Sender name is examined the fact that it has a comment means that it is treated as a non-null email address. After stripping out the comments a null email is left and this is then treated as a valid originator. CR: JAGae33310 SR: 8606269075 The code does not differentiate enough between a TNEF recipient and a MIME recipient to split the message and allow different steering for the different types of recipient. As the fix for this problem will cause a change in behaviour on systems that have different TNEF and MIME steering files then the old (incorrect) behaviour can be reinstated by setting the following general.cfg option: UXO_OLD_TNEFOUT=TRUE CR: JAGae33867 SR: 8606269632 When using PC Admin to create/modify PDLs the ommodpdln command is used on the server. If the user being added/modified has an INTERNET-ADDR (IA) attributed configured in the directory then this attribute is supplied in the entry. The presence of this IA attribute is causing 'ommodpdln' to report an error. CR: JAGae35717 SR: 8606271509 On AIX 5.1L, the df command lists an entry for a file system called /proc. All the sizing parameters for this file system are listed as hyphens. This confuses the omdiskfull command which issues a message announcing a full file system. The 'omeval omdf' command (for AIX) has been changed to ignore this entry. CR: JAGae36951 SR: 8606272845 The non-ASCII characters in the comment part of the ARPA name confuse unix.out and it thinks that the name is illegal and therefore refuses to process the name and generates a NDN for the message. It seems that only Outlook (under some circumstances) preserves the comment field when generating a reply, other clients discard the comment and therefore are not affected by this problem. PHSS_27061: CR: JAGad38110 SR: 8606168832 Both Web Clients create workfiles in /var/tmp. The umask system call should be invoked to ensure that the files are neither world-readable nor world-writable. CR: JAGae05328 SR: 8606236267 If a program loads a dynamic library which has been compiled with threads enabled, then file I/O is unstable within the dll unless there has been file I/O within the calling program first. This appears to be a problem in Linux Redhat 7.2. CR: JAGae12028 SR: 8606245558 When an APPEND command is issued by an IMAP client the OpenMail creator of the item being appended is not set to be the Sender of the item. Neither is the OpenMail create date set to be the IMAP internal date of the item. The existing code does make the message Sender a FROM recipient in the distribution list - this means that other IMAP clients see the correct sender/creator, however non-IMAP clients see an incorrect msg creator. A new general.cfg option is introduced with the fix for this problem: IMAP_ALLOW_MOD_CREATOR=TRUE will set up the OpenMail creator to be the message Sender - this is the default. IMAP_ALLOW_MOD_CREATOR=FALSE will reinstate the old behaviour. CR: JAGae12031 SR: 8606245561 The ICE session is terminated because the REMOTE_ADDR value passed to the cgi program changes during the course of the email session. The code expects this value not to change, but there are circumstances when it does. It can happen when web access is provided by an ISP. In order to provide flexibility in this situation a new web access and profile option will be provided to control the behaviour of the web profile with respect to a changing value of REMOTE_ADDR during a session. The REMOTE_ADDR value can legitimately change if an ISP is being used, so this behaviour is now contolled by the option: Allow-Remote-Addr-Change = 0 # REMOTE_ADDR value can't # change (default and old # behaviour) Allow-Remote-Addr-Change = 1 # REMOTE_ADDR can change # if SessId is in cookie. Allow-Remote-Addr-Change = 2 # REMOTE_ADDR can change # with no checking. This option can be set at the individual profile level: ~openmail/omhmtl//profile or for all web profiles: ~openmail/omhtml/config The individual profile setting (if set) will take precedence. An Allow-Remote-Addr-Change setting of 1 is recommended to overcome any premature SESSION EXPIRED problems - this will work if the web browser is using cookies to provide session id hiding. A setting of 2 means that no checking of REMOTE_ADDR is done at all and if cookies are not being used then the session id information is passed within URLs that are visible on the computer screen and could be used from another web browser. CR: JAGae17136 SR: 8606251070 The handling of the SIGCLD (SIGCHLD) interrupt has changed from being ignored to being trapped ('reaped'). This change has had some unforeseen side-effects. CR: JAGae18238 SR: 8606253906 The code to check a new password against any password composition rules was removed when the PAM mechanism was incorporated in the B.07.00 code. CR: JAGae19347 SR: 8606255018 Content Disposition of 'inline' should be configurable without a 'filename' value. A new general.cfg option has been added to allow this to be configured: INET_INLINE_FILETYPES=nnnn where 'nnnn' is an OpenMail filetype. Several filetypes can be specfied by separating with commas, for example: INET_INLINE_FILETYPES=2130,2133 will cause both RTF and HTML to be given a Content Disposition of 'inline'. The INET_INLINE_FNAME_ALLOWED=FALSE option should still be set in general.cfg to suppress the 'filename'. Additionally the ~openmail/sys/mimeout.str file should be editted to uncomment the lines for 2130 and 2133 if the multipart/alternative structure is not required for these filetypes. CR: JAGae22300 SR: 8606257997 The T.61 subject can become large when encoded as a MIME string as each separate T.61 sub-string will be preceded by a character set specification. This long string can then overflow the buffer used to hold the MIME filename string causing a Segmentation Violation. CR: JAGae22536 SR: 8606258235 A coding defect, in the incoming Internet Gateway, of failing to increment a loop count on encountering a NULL X400 address, as occurs in this case, causes an infinite loop. CR: JAGae23835 SR: 8606259517 There is no test for whether read acknowedgements are required when an IMAP message is read, and no attempt is made to generate an acknowledgement if it is. PHSS_26277: CR: JAGad84900 SR: 8606215723 The incoming Internet Gateway normally truncates all X.400 printable string attributes, of all ORNs within a message, to the size limits stipulated in the X.400 standard, just in case the message is sent through the X.400 Gateway. A new Tweak, INET_NO_TRUNC_X400_ATTS, has been introduced to inhibit this truncation. CR: JAGad95079 SR: 8606226007 The primary cause of the problem is the fact that the TNEF file after decoding from the MIME encoding (quoted-printable in this instance) is corrupt and contains field length information that points beyond the end of the TNEF data. The secondary problem is that the quoted-printable encoding of a TNEF attachment is illegal according to Microsoft's rules for this type of attachment. The fix detects when a TNEF attachment is not encoded as "base64" and logs an informative error to the OpenMail log. The TNEF file is decoded according to the general.cfg UX_PRE_5_20_COMPATIBILITY_MODE setting. If any corruption is detected the TNEF attachment will either be treated as a text attachment or the message will be rejected according to the general.cfg UXI_NON_DELIVER_BAD_TNEF setting. CR: JAGad97183 SR: 8606228125 The text in the message catalogue for the message rejection due to a recipient user's 'service level' value is incorrect. It describes this error as a mailbox size limit violation. CR: JAGad97593 SR: 8606228536 There is no code whatsoever in the Web ICE Client 6.0 to cope with the %%SIGNONALTS%% markup in the Duplicate Usernames page of the 5.10 profiles, which is significantly different from the 6.0 profiles. It has no code of its own to do all the extra work that the Web Client 5.10 does in this case. Also, at GR6, the Portal Access facility was not available with the Web Client 5.10, and so when its profiles are used with the ICE Client 6.0, it has no ability to display a list of alternative names; the Duplicate Usernames page is absent. CR: JAGad98210 SR: 8606229157 Pluggable Authentication Modules (PAM) changes to GR7 have accidently removed the UAL_LOCAL_IGNORE_PASSWORD option. CR: JAGae02798 SR: 8606233575 The code of the in.imap41d program does not use the 'received date' information when retrieving the INTERNALDATE attribute of a message. CR: JAGae03973 SR: 8606234784 The problem was that omlogoff terminates while the omlogon process is still running. If running another omlogon immediately afterwards, the first omlogon would delete out the user pipes which the second omlogon had just created. Although this second omlogon appeared to have succeeded, it was unable to process further requests - e.g. omlist. An omlist call would then expect the username and password to be entered manually. This caused various of the OpenMail autotests to hang. CR: JAGae03977 SR: 8606234788 The cause of the problem was the errno value being changed when a successful accept() call was made. It is possible for this to happen on Linux. The pcmonitor returns an error condition to a calling function if the errno indicates an error, even if the accept call was successful. This caused omlogon to fail. CR: JAGae06468 SR: 8606237428 The failure of omdosur was caused by trying to access files in the live message store rather than those in the alternative working directory which is specified when omdosur is called. Each time a Content Record is opened in omdosur a transient flag is set to indicate that the alternative working directory should be used when opening files. For IMAP object file information this did not succeed as the Content Record was reread unsetting this flag. CR: JAGae07450 SR: 8606238426 A coding defect of an uninitiallised return parameter, in the User Directory Access component, causes the return of a spurious Primary Mailnode when none exists, in very rare circumstances. The caller does not defend against this condition. Encountered only on Solaris 8, but could occur rarely anyplace, anytime. PHSS_25647: CR: JAGad83534 SR: 8606214343 This is an enhancement to the behaviour of the auto-actions. Auto- redirect may now be controlled by two directives from the config file; EXECUTE_AA_ON_REDIRECT and DELETE_INTRAY_MSG_ON_REDIRECT. The values they take are 0 or 1. Before the introduction of this enhancement an auto-redirect prevented other auto-actions from being honoured. The first of these two directives ensures that if any other auto-actions are enabled then they are honoured, however the trigger message is delivered to the intray. The second directive will delete the trigger message from the intray. CR: JAGad83915 SR: 8606214723 An empty auto-forward covering text string prevents the file, held within the users g directory, which holds the covering text from being generated. If this file is not present the local delivery agent fails to forward the message. CR: JAGad83932 SR: 8606214740 The UAL checklist command did a check to see if the specified address matched the internet address before looking for a match on the X400 attributes. If alternatives were found, then the list of alternatives was compiled by researching the directory. however, the search to create the list was only being done on the X400 attributes and no internet search was done on the internet directory. This resulted in no matches being found and the list being empty. In addition, the internet search was done only on the internet attribute. So if X400 attributes had been specified, these were ignored when determining a match from the internet directory. CR: JAGad84893 SR: 8606215716 After processing a erroneous Return of Contents, the X400 outgoing gateway failed to clear a global data item. This led to subsequent messages being incorrectly handled, and rejected with 6019 log error numbers. Processing following the detection of the 6019 errors failed to close the transaction file of the message or distibution list, and eventually the limit for the maximum number of open transaction files was reached. CR: JAGad84922 SR: 8606215745 An empty auto-reply covering text string prevents the file, held within the users g directory, which holds the covering text from being generated. If this file is not present the local delivery agent fails to generate an auto-reply message. CR: JAGad87535 SR: 8606218386 In GR7 a session monitor daemon was introduced which does some of the work of the UAL. One thing it does is to update the user's signon information, and the functionality of when to update the last signon time was not implemented. Instead, the last signon time is always updated - which does not correspond to the GR6 functionality when an admin session or a session run by a trusted user is doing the signon. CR: JAGad87649 SR: 8606218500 The UAL_BBACL command that set Outlook permissions on folders uses the ACL name checking code which (incorrectly) will not allow the Common Name field to be specified with other Mnemonic ORN fields. Eg. Teresa Green/acme,sales/CN=tg will be rejected as an invalid delegate name. CR: JAGad88671 SR: 8606219531 The code in the X400 intrinsics, that processes non-textual content items using the EMA BodyPart 15 rules, allocates memory on a per message basis for a number of linked data structures, and fails to release all of them at the end of the message. CR: JAGad88889 SR: 8606219749 Extra spurious content is displayed for an IMAP client when there are more that 9 top level contents. This is due to an incorrect comparison of the content item number. CR: JAGad89888 SR: 8606220752 An internal format error within TCL strings caused 8-bit strings to appear corrupted. CR: JAGad90057 SR: 8606220921 When the message type is multipart/report, the message is written out to a temporary file. The length of the line is noted and if less than 1, an error is reported. If the first character of a line is null, then the length is 0, incorrectly causing a fatal error. CR: JAGad90490 SR: 8606221356 Non-ascii NDN text from message catalogue is not given the correct charset specification in the MIME header. CR: JAGad90761 SR: 8606221627 One write to the shared memory used by the Notification Server failed to check if enough space was available before commencing the write. CR: JAGad91276 SR: 8606222161 The omupdtis code traps the SIGHUP and SIGTERM to allow processing of the omupdtis command to be interrupted but does not set a error return when this happens. CR: JAGad93282 SR: 8606224187 The Named Property Id is incremented each time a named property is generated. There is no check for the actual maximum of FFFE, or for overflow at FFFF. So once the value FFFE was exceeded, the named property id's take undefined values. CR: JAGad93317 SR: 8606224222 PAM changes for B.07 cause unsuccessful signons to return early without doing any audit logging. CR: JAGad94573 SR: 8606225486 The tweaks DEFAULT-OMSERVER and OMSERVER where not honoured if the portal access mechanism was disabled. CR: JAGad94888 SR: 8606225815 At VV4.5 root does not have the required authorisation level to execute the setlevel command. CR: JAGad95463 SR: 8606226394 The cause appears to be the value of the PR_RTF_SYNC* properties, in particular the PR_RTF_SYNC_BODY_COUNT. These properties are correctly set when the message is initially created. However, after the message has been saved and re-edited, these properties are NOT updated causing a mismatch between the properties and the actual content of the sent message. 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 In the following text, # is used to represent the character. 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 than 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: 8606110229 8606286454 8606288373 8606288693 8606289790 8606224537 8606273505 8606277728 8606277792 8606278311 8606278755 8606279417 8606280333 8606201876 8606238864 8606254208 8606260336 8606260401 8606261785 8606262840 8606266965 8606267820 8606267991 8606268107 8606268859 8606269075 8606269632 8606271509 8606272845 8606168832 8606236267 8606245558 8606245561 8606251070 8606253906 8606255018 8606257997 8606258235 8606259517 8606215723 8606226007 8606228125 8606228536 8606229157 8606233575 8606234784 8606234788 8606237428 8606238426 8606214343 8606214723 8606214740 8606215716 8606215745 8606218386 8606218500 8606219531 8606219749 8606220752 8606220921 8606221356 8606221627 8606222161 8606224187 8606224222 8606225486 8606225815 8606226394 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-CHSCAT /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-FINCAT /opt/openmail/patch/filesets/OM-FINICE /opt/openmail/patch/filesets/OM-FINPAW /opt/openmail/patch/filesets/OM-FRECAT /opt/openmail/patch/filesets/OM-FREICE /opt/openmail/patch/filesets/OM-FREPAW /opt/openmail/patch/filesets/OM-GERCAT /opt/openmail/patch/filesets/OM-GERICE /opt/openmail/patch/filesets/OM-GERPAW /opt/openmail/patch/filesets/OM-IMAP4 /opt/openmail/patch/filesets/OM-ITACAT /opt/openmail/patch/filesets/OM-ITAICE /opt/openmail/patch/filesets/OM-ITAPAW /opt/openmail/patch/filesets/OM-KORCAT /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-NIPCAT /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-PTBCAT /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-SPACAT /opt/openmail/patch/filesets/OM-SPAICE /opt/openmail/patch/filesets/OM-SPAPAW /opt/openmail/patch/filesets/OM-SWECAT /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_28591/omunpatch /opt/openmail/patch/PHSS_28591/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-CHSCAT: 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-FINCAT: 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-FRECAT: 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-GERCAT: 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-ITACAT: 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-KORCAT: 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-NIPCAT: 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-PTBCAT: 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-SPACAT: 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-SWECAT: 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/4 2002/04/26 1 8:35:41 pl $ /opt/openmail/patch/PHSS_28591/omunpatch: $Header: sh_unpat.gen,v /opt/openmail/patch/PHSS_28591/ompatch.idx: No what strings cksum(1) Output: 2154995486 867941 /opt/openmail/patch/filesets/OM-ADM 292089781 224608 /opt/openmail/patch/filesets/OM-AMECAT 4286625374 17014 /opt/openmail/patch/filesets/OM-AMEICE 1976576121 13847 /opt/openmail/patch/filesets/OM-AMEPAW 1684358712 106404 /opt/openmail/patch/filesets/OM-AMEPSS 2355547680 177984 /opt/openmail/patch/filesets/OM-APPL 2923985127 83456 /opt/openmail/patch/filesets/OM-BB 1310211376 124055 /opt/openmail/patch/filesets/OM-CHSCAT 2287731925 17077 /opt/openmail/patch/filesets/OM-CHSICE 1148414482 14135 /opt/openmail/patch/filesets/OM-CHSPAW 1698092642 11927951 /opt/openmail/patch/filesets/OM-CORE 3010073381 107721 /opt/openmail/patch/filesets/OM-DESK 2300797750 174292 /opt/openmail/patch/filesets/OM-DSYNC 2473546742 224607 /opt/openmail/patch/filesets/OM-ENGCAT 258723475 16990 /opt/openmail/patch/filesets/OM-ENGICE 3991603781 13842 /opt/openmail/patch/filesets/OM-ENGPAW 2375897090 106409 /opt/openmail/patch/filesets/OM-ENGPSS 2896639217 252187 /opt/openmail/patch/filesets/OM-FINCAT 2798506077 17094 /opt/openmail/patch/filesets/OM-FINICE 2362269684 14255 /opt/openmail/patch/filesets/OM-FINPAW 2783237940 251564 /opt/openmail/patch/filesets/OM-FRECAT 2919665112 17041 /opt/openmail/patch/filesets/OM-FREICE 2960502187 14170 /opt/openmail/patch/filesets/OM-FREPAW 1867657442 252216 /opt/openmail/patch/filesets/OM-GERCAT 924509893 17066 /opt/openmail/patch/filesets/OM-GERICE 3041679699 14095 /opt/openmail/patch/filesets/OM-GERPAW 2730103896 82620 /opt/openmail/patch/filesets/OM-IMAP4 3713096464 249993 /opt/openmail/patch/filesets/OM-ITACAT 3129887498 17037 /opt/openmail/patch/filesets/OM-ITAICE 641525321 14061 /opt/openmail/patch/filesets/OM-ITAPAW 613092520 125613 /opt/openmail/patch/filesets/OM-KORCAT 701015575 17086 /opt/openmail/patch/filesets/OM-KORICE 3626044597 14290 /opt/openmail/patch/filesets/OM-KORPAW 1213689066 722078 /opt/openmail/patch/filesets/OM-LC 2568758881 84122 /opt/openmail/patch/filesets/OM-LDAP 2439132044 10324 /opt/openmail/patch/filesets/OM-MAN 4151587613 125740 /opt/openmail/patch/filesets/OM-NIPCAT 3013581315 17126 /opt/openmail/patch/filesets/OM-NIPICE 2009430120 14318 /opt/openmail/patch/filesets/OM-NIPPAW 3496738599 65169 /opt/openmail/patch/filesets/OM-PMOVER 3945789965 24599 /opt/openmail/patch/filesets/OM-POP3 1840994262 252351 /opt/openmail/patch/filesets/OM-PTBCAT 3772517749 17065 /opt/openmail/patch/filesets/OM-PTBICE 288201382 14109 /opt/openmail/patch/filesets/OM-PTBPAW 533736402 477652 /opt/openmail/patch/filesets/OM-RC 1528090277 208068 /opt/openmail/patch/filesets/OM-SMS 2877661055 251076 /opt/openmail/patch/filesets/OM-SPACAT 650082590 17077 /opt/openmail/patch/filesets/OM-SPAICE 2142555875 14114 /opt/openmail/patch/filesets/OM-SPAPAW 694147314 250058 /opt/openmail/patch/filesets/OM-SWECAT 2746655178 17047 /opt/openmail/patch/filesets/OM-SWEICE 3707545788 14094 /opt/openmail/patch/filesets/OM-SWEPAW 1143973703 130335 /opt/openmail/patch/filesets/OM-UNIX 316418039 714591 /opt/openmail/patch/filesets/OM-WEBADM 1232380431 1019709 /opt/openmail/patch/filesets/OM-X400 1357410443 26524 /opt/openmail/patch/ompatch 4120277454 11249 /opt/openmail/patch/PHSS_28591/omunpatch 3302757168 159026 /opt/openmail/patch/PHSS_28591/ompatch.idx Patch Conflicts: None Patch Dependencies: None Hardware Dependencies: None Other Dependencies: None Supersedes: PHSS_23490 PHSS_24875 PHSS_25647 PHSS_26277 PHSS_27061 PHSS_27679 PHSS_28156 Equivalent Patches: PHSS_28592: s700: 11.00 11.04 11.11 s800: 11.00 11.04 11.11 PFSS_17044: sparcSUN: 5.6 5.7 5.8 PASS_17044: AIX: 4.3 5.1 PLSS_17048: intelLinux: RedHat7.0 RedHat7.1 RedHat7.2 RedHat7.3 Patch Package Size: 19920 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_28591 5a. For a standalone system, run swinstall to install the patch: swinstall -x autoreboot=true -x match_target=true \ -s /tmp/PHSS_28591.depot By default swinstall will archive the original software in /var/adm/sw/patch/PHSS_28591. 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_28591.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_28591.depot of=/dev/rmt/0m bs=2k Special Installation Instructions: SUBSYSTEM_SHUT ================================================= PHSS_28591: ================================================= CR: JAGae50393 SR: 8606286454 ------------------------------- For these file extensions to be recognised by OMGUI, the following lines should be added to ~/sys/appmap and its version number incremented so that it gets downloaded to clients : 1743 B WN G '????' '????' '.DWG' // AutoCAD 2144 B WN G '????' '????' '.VSD' // Microsoft Visio ================================================= PHSS_28156: ================================================= CR: JAGae42811 SR: 8606278755 ------------------------------- The general.cfg option PM_STRIP_MAPI_REPLY_RECIPS=TRUE must be set to activate this new behaviour. ================================================= PHSS_27679: ================================================= CR: JAGae33310 SR: 8606269075 ------------------------------- The old behaviour - not splitting the message when MIME and TNEF recipients are present and a separate steering file exists for these routes (~openmail/sys/mimeout.str and ~openmail/sys/tnefout.str) - can be reinstated by setting the general.cfg option: UXO_OLD_TNEFOUT=TRUE ================================================= PHSS_27061: ================================================= CR: JAGae12028 SR: 8606245558 ------------------------------- The old behaviour can be reinstated by setting the IMAP_ALLOW_MOD_CREATOR=FALSE option in ~openmail/sys/general.cfg CR: JAGae12031 SR: 8606245561 ------------------------------- To fix the problem of a premature SESSION EXPIRED error when using web clients via an ISP web connection a new web client configuration option has been introduced. This option controls the behaviour of the ice.user program with respect to the value of the REMOTE_ADDR environment variable supplied by the Web server: Allow-Remote-Addr-Change = 0 # not allowed (default and # old behaviour) Allow-Remote-Addr-Change = 1 # Remote Addr can change # if SessId is in cookie. Allow-Remote-Addr-Change = 2 # Remote Addr can change # with no checking. This option can be set at the individual profile level: ~openmail/omhmtl//profile or for all web profiles: ~openmail/omhtml/config The individual profile setting (if set) will take precedence. An Allow-Remote-Addr-Change setting of 1 is recommended to overcome any premature SESSION EXPIRED problems - this will work if the web browser is using cookies to provide session id hiding. A setting of 2 means that no checking of REMOTE_ADDR is done at all and if cookies are not being used then the session id information is passed within URLs that are visible on the computer screen and could be used from another web browser. CR: JAGae19347 SR: 8606255018 ------------------------------- A new general.cfg option has been added to allow a specified OpenMail filetype to have a MIME Content-Disposition of 'inline': INET_INLINE_FILETYPES=nnnn where 'nnnn' is an OpenMail filetype. Several filetypes can be specfied by separating with commas, for example: INET_INLINE_FILETYPES=2130,2133 will cause both RTF and HTML to be given a Content-Disposition of 'inline'. The INET_INLINE_FNAME_ALLOWED=FALSE option should still be set in general.cfg to suppress the 'filename' attribute. Additionally the ~openmail/sys/mimeout.str file should be editted to uncomment the lines for filetypes involved (2130 and 2133 in the example above) if the multipart/alternative structure is not required. ================================================= PHSS_26277: ================================================= CR: JAGad84900 SR: 8606215723 ------------------------------- The incoming Internet Gateway normally truncates all X.400 printable string attributes, of all ORNs within a message, to the size limits stipulated in the X.400 standard, just in case the message is sent through the X.400 Gateway. A new Tweak has been introduced to prevent this truncation :- INET_NO_TRUNC_X400_ATTS If set TRUE: The X.400 attributes of an ORN are never truncated. If set FALSE: The X.400 attributes of an ORN are truncated to the limits set by the standard, as usual. Default: FALSE OpenMail does not need to be restarted for this option to take effect. CR: JAGad95079 SR: 8606226007 ------------------------------- The fix detects when a TNEF attachment is not encoded as "base64" and logs an informative error to the OpenMail log. The TNEF file is decoded according to the general.cfg UX_PRE_5_20_COMPATIBILITY_MODE setting. If any corruption is detected the TNEF attachment will either be treated as a text attachment or the message will be rejected according to the general.cfg UXI_NON_DELIVER_BAD_TNEF setting (see JAGac39658). ================================================= PHSS_25647: ================================================= CR: JAGad83534 SR: 8606214343 ------------------------------- The behaviour of the redirect rule can be controlled by the directives EXECUTE_AA_ON_REDIRECT and DELETE_INTRAY_MSG_ON_REDIRECT specified in the /var/opt/openmail/omhtml/config file. The values these directives can take are 0 or 1. The directive EXECUTE_AA_ON_REDIRECT will force local delivery to retain a copy of the message in the users intray, thus allowing the auto-actions to be executed. The directive DELETE_INTRAY_MSG_ON_REDIRECT will force deletion of the message from the users intray after it has been delivered and the auto actions have been executed. ================================================= 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 : 69 MB NOTE: ServiceGuard Installations will need twice this amount. ----------------------------------------------------------