Patch Name: PHSS_29063 Patch Description: s700_800 10.20 OpenMail B.06.00 June 03 Periodic Patch Creation Date: 03/05/14 Post Date: 03/06/04 Hardware Platforms - OS Releases: s700: 10.20 s800: 10.20 Products: OpenMail B.06.00 Filesets: OpenMail.OM-ADM,B.06.00 OpenMail.OM-AMECAT,B.06.00 OpenMail.OM-AMEICE,B.06.00 OpenMail.OM-AMEWEB,B.06.00 OpenMail.OM-APPL,B.06.00 OpenMail.OM-BB,B.06.00 OpenMail.OM-CCMOB,B.06.00 OpenMail.OM-CHSCAT,B.06.00 OpenMail.OM-CHSICE,B.06.00 OpenMail.OM-CHSPSS,B.06.00 OpenMail.OM-CHSWEB,B.06.00 OpenMail.OM-CORE,B.06.00 OpenMail.OM-DESK,B.06.00 OpenMail.OM-DSYNC,B.06.00 OpenMail.OM-ENGCAT,B.06.00 OpenMail.OM-ENGICE,B.06.00 OpenMail.OM-ENGWEB,B.06.00 OpenMail.OM-FINCAT,B.06.00 OpenMail.OM-FINICE,B.06.00 OpenMail.OM-FINWEB,B.06.00 OpenMail.OM-FRECAT,B.06.00 OpenMail.OM-FREICE,B.06.00 OpenMail.OM-FREWEB,B.06.00 OpenMail.OM-GERCAT,B.06.00 OpenMail.OM-GERICE,B.06.00 OpenMail.OM-GERWEB,B.06.00 OpenMail.OM-IMAP4,B.06.00 OpenMail.OM-ITACAT,B.06.00 OpenMail.OM-ITAICE,B.06.00 OpenMail.OM-ITAWEB,B.06.00 OpenMail.OM-KORCAT,B.06.00 OpenMail.OM-KORICE,B.06.00 OpenMail.OM-KORPSS,B.06.00 OpenMail.OM-KORWEB,B.06.00 OpenMail.OM-LC,B.06.00 OpenMail.OM-LDAP,B.06.00 OpenMail.OM-MAN,B.06.00 OpenMail.OM-NIPCAT,B.06.00 OpenMail.OM-NIPICE,B.06.00 OpenMail.OM-NIPPSS,B.06.00 OpenMail.OM-NIPWEB,B.06.00 OpenMail.OM-NOTES,B.06.00 OpenMail.OM-PMOVER,B.06.00 OpenMail.OM-POP3,B.06.00 OpenMail.OM-PTBCAT,B.06.00 OpenMail.OM-PTBICE,B.06.00 OpenMail.OM-PTBWEB,B.06.00 OpenMail.OM-RC,B.06.00 OpenMail.OM-SMS,B.06.00 OpenMail.OM-SPACAT,B.06.00 OpenMail.OM-SPAICE,B.06.00 OpenMail.OM-SPAWEB,B.06.00 OpenMail.OM-SWECAT,B.06.00 OpenMail.OM-SWEICE,B.06.00 OpenMail.OM-SWEWEB,B.06.00 OpenMail.OM-UNIX,B.06.00 OpenMail.OM-X400,B.06.00 Automatic Reboot?: No Status: General Release Critical: No Path Name: /hp-ux_patches/s700_800/10.X/PHSS_29063 Symptoms: PHSS_29063: CR: JAGae59759 SR: 8606296148 When an Asian user on GR6 browses a NDN msg using an IMAP client, the NDN is displayed in English, not in the user's local language, with the non-delivered recipient name being corrupted and truncated, as in :- imaizumi-ma 15=; and the following error is logged a few times to the 'fatal' log file:- [OM 16130] Unable to open localised attribute tag file for interchange character set ISO8859_1. Additionally, if the user is on a mailnode with TTX attributes, the Item Browser may go into a loop continually logging many ERROR [OM 16130]'s. On GR6 this causes the IMAP client 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. CR: JAGae62810 SR: 8606299316 If an attempt is made to install an OpenMail patch on a system which does not have the base OpenMail product installed, an ERROR status is returned in swagent.log. On an HP-UX 11.11 system, it would be more appropriate to return an EXCLUDE status. CR: JAGae69195 SR: 8606306147 An inconsistency has been identified, on GR6 only, in the code whereby a function is called with a structure parameter when the function itself is expecting a pointer to the structure. This is very likely to cause untoward behaviour, particularly on LINUX, where it could crash the UAL Remote Client Interface, with an error like :- SERIOUS ERROR Remote Client (U/I Access ) [OM 10250] Process about to terminate due to error. Signal (Segmentation Violation) trapped by process 5930; code = 0. Procedure trace follows: ... -> sfl_OpenItem -> im_ItemRef2FName <- im_ItemRef2FName -> sfl_OpenSfl -> im_OpenItem -> im_ItemRef2FName <- im_ItemRef2FName <- im_OpenItem -> im_OpenItem but could just as well affect other platforms. CR: JAGae70969 SR: 8606307934 An item has the content line "Content-Type: text/html; charset=" - i.e. is the character set value is NULL. The following IMAP command is given. ". UID FETCH 1 (FLAGS)" The flags are displayed correctly. The further IMAP command is then given ". UID FETCH 1 (rfc822.size)" This causes the response "NO some of the requested messages no longer exist", and the size information is not displayed. This also happens other requests of header information. CR: JAGae70977 SR: 8606307942 A user has a number of corrupt mail items. When the IMAP command ". UID FETCH n (rfc822.size)" is issued for any one of these items, the following response is given "NO some of the requested messages no longer exist". and so the mail item is not displayed. However, these items can be displayed using other clients. The only data displayed is the "subject", but a user is then able to delete these items from their mail box. It was also noticed that omscan does not detect these items as being corrupt. CR: JAGae70980 SR: 8606307945 When some mail items, containing a folder item, are viewed from an IMAP client, the content is lost. The item browser fails to return the requested message content, and so the IMAP DAEMON responds with "No some of the requested messages no longer exist" when an IMAP "UID FETCH (BODY[1.MIME])" command is given. CR: JAGae70984 SR: 8606307949 After some messages have become corrupt, the UAL GET_OBJFILES command returns a corrupt object file. When an attempt is made to create the body structure from the data in this corrupt file, the IMAP daemon child process hangs. The following response is given "NO some of the requested messages no longer exist" and only the messages up to the point of the corrupt one are displayed. CR: JAGae70985 SR: 8606307950 Sometimes the UAL returns no absolute value for delivery acknowledgements. IMAP uses the absolute value to assign the UID value, and is assigning a value of 0 in these cases. Attempting to access an item with a UID value of 0 doesn't work, as the IMAP daemon see this as an invalid value. So the following response is given "NO some of the requested messages no longer exist" and the mail item is not displayed. As an example, if items 1 and 3 have UID values of 0, then the IMAP command ". UID FETCH 1:4 (FLAGS)" processes items 2-4, whereas the command ". UID FETCH 1,2,3,4 (FLAGS)" processes items 2 and 4. This is inconsistent. The presence of items with 0 UID values can confuse clients such as Netscape 4.7. This client seems to issue a fetch command with a UID 2 greater than he actual value in the above case. PHSS_28589: 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: JAGae49796 SR: 8606285855 When OpenMail is installed for the first time on a RedHat system, file OMDATADIR/omhtml/portal.cfg may not be created. In this case, the ICE client will fail with a 'System Error : [SYS 2] No such file or directory' message. Some WAP and PAW configuration files may also not be created (for example, profile.std should be copied to profile). 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_28154: 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. CR: JAGae48115 SR: 8606284168 Cannot reply to the message which came from the local OM user who has long user name (probably with TTX fields). The reply generated contains a truncated name for the original sender which cannot be mailed (address not routable) or cannot be delivered (name not known). PHSS_27677: 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 "OMDATADIR/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: JAGae24726 SR: 8606260403 omsendin does not recognize the sendmail.cf versions later than 8.9 included with some releases of Solaris and AIX. This does not occur with OpenMail B.07 or with OpenMail B.06 on RedHat Linux. 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: 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. PHSS_27059: 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: 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: JAGae15283 SR: 8606248886 There are 3 problems in B.06.00 1) The IMAP_AUTOMATIC_MDN general.cfg option is not always being checked. This means that an acknowledgement may be sent by the server when this option is not set to TRUE and the client has not generated an acknowledgement. This usually happens for the first user. See also JAGac 78827. 2) Disposition notifications generated by Netscape are not always detected as such. This means that a message appears in the sending user's intray, rather than being recorded against the saved copy of the message in the Pending Tray being updated. See also JAGad 45462. 3) If an item requires an acknowledgement and IMAP_AUTOMATIC_MDN is set to FALSE (default), then the item is not marked as read when opened. 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: 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. PHSS_26275: 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: 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: 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_25645: 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: 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: 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: 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: 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 OMDATADIR/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_24873: 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: 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: 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: 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: JAGad73144 SR: 8606203966 Requesting virtual licences from other machines using GR6 Dec 2000 PP fails in some cases, and the license server may abort. The failure happens when there is a decaying license in the shadow file. omaudlic on the other machine shows that the licences have been granted. The failure depends on the order of entries within the shadow file, and therefore appears to be intermittent. It does not seem to be related to any one platform. 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: 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. PHSS_24094: 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: 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: JAGad45881 SR: 8606176644 Omcontain aborts with a segmentation violation on LINUX, when trying to delete a message attachment located in the user's intray and results in the message attachment remaining in the intray. 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: JAGad47890 SR: 8606178664 Some vir*ses can be flagged as being clean if the machine on which they were scanned had been incorrectly configured for scanning. CR: JAGad48440 SR: 8606179216 8-bit text (e.g. German national chars) is displayed as 7-bit by IMAP clients, Netscape and Outlook Express. 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: JAGad53837 SR: 8606184631 Large attachments (>30K) in forwarded messages are not visible to Netscape IMAP client after moving from intray to another folder. 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: JAGad57988 SR: 8606188772 Messages containing ARPA Message Headers (e.g. Subject:) with 8-bit text (e.g. German national chars) are displayed in MIME source format by Netscape IMAP clients. This occurs on the 2nd. and subsequent re- browse of the message. The initial browse of the message is displayed correctly. 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. PHSS_23342: CR: JAGab33574 SR: 1653231704 OpenMail for Solaris's service router will abort if a distribution list contains a blank name in it. The following error is logged and can be seen using omshowlog : SERIOUS ERROR Service Router(Service Router) 09.04.97 [OM 10250] Process about to terminate due to error. Signal (Segmentation Violation) trapped by process 4613; code = 0. Procedure trace follows: < - da_GetAttribDefn -> nm_GetFieldMemPtr < - nm_GetFieldMemPtr -> da_GetAttribDefn -> da_GetMemAttribDefn < - da_GetAttribDefn -> nm_GetFieldMemPtr < - nm_GetFieldMemPtr -> da_GetAttribDefn 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: JAGad24268 SR: 8606154951 omupdtis and associated commands sometimes report illegal message store container references e.g. ~/sys/1000035/0000001:3 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: JAGad41463 SR: 8606172203 The Application Link Layer component does not pass all the basic acceptance tests on Solaris. 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: JAGad41637 SR: 8606172377 Wrong user config file being used when accessing a delegate mailbox. CR: JAGad42631 SR: 8606173373 Openmail GR6 experiencing OM 1209 whenever omscan is run. omscan logs errors in the log file which are nothing to worry about and are normal behaviour. These errors should be correctly trapped to avoid worrying administrators that they may be a problem 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: JAGad43053 SR: 8606173798 When a message is copied from one message store to another using Netscape Message, and an accented character exists in it's content, then the message content file is corrupted. However, the content of the message remains OK in the IMAP index file. This means that the content can be viewed using Netscape Message, but not when using OMGUI or Outlook. CR: JAGad44810 SR: 8606175570 If a user has an address attribute with a backslash in, then when the user's address is validated (checked) the address attributes are displayed within the freeform field (to:). If a backslash is present it prevents the message being sent and displays the message "the user name is not routable" 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: 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: 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: JAGad49581 SR: 8606180360 The original fix for JAGac29290 was missing two files: i4target_ux10 and i4target_ux11. They should be included. JAGac29290 added the ability to run OpenMail on systems where the LSSERV component was not installed. PHSS_23081: CR: JAGad41842 SR: 8606172582 Outlook OFS: The UAL_GETSYNC extracts T.61 text content files without performing any character set conversion on them. This affects Czech text that is synchronized and will also affect Japanese, Korean and Chinese text. CR: JAGad42033 SR: 8606172773 Itemed moved from Inbox whilst offline gets sync'ed twice: Once when the MOVE is synced, and then again when the folder is next synced. CR: JAGad42115 SR: 8606172855 When 2 Outlook clients are connected to the same user mailbox (eg. delegate and principal) there are occasions when Calendar data is changed offline and the appointment date emboldening is not updated for the online user after a sync. CR: JAGad42645 SR: 8606173387 They are occasions when the synchronization a folder (typically the Inbox) will not pick up all of the newly added messages. This is most likely to occur on Inboxes with more than 32 items that have had items added and deleted since the last synchronization. The items not sync'ed to the local Inbox will be in a block starting with one delivered immediately after the last sync. CR: JAGad42878 SR: 8606173621 Message that is deleted completely on the server and modified offline causes a sync. error when the folder is next synced. CR: JAGad44420 SR: 8606175176 Using Outlook OFS can cause spurious WARNINGs to be reported in the OpenMail error log. Happens most frequently when mailing messages that get saved to the Drafts folder during message construction. The warnings of the following type: WARNING Remote Client (U/I Access ) 01.04.01 11:11:35 [OM.UI 578] The Direct Reference supplied is invalid User Name: JONATHAN GEORGE / HP-Pinewood, om1 -> ual_MatchSyncLogEntry <- ual_MatchSyncLogEntry -> ct_ofs_read <- ct_ofs_read -> ual_MatchSyncLogEntry <- ual_MatchSyncLogEntry -> ual_MatchSyncLogEntry <- ual_MatchSyncLogEntry -> ual_ListChangeLogAdd -> ual_ResolveDirectRef -> ct_FindDITEntryByRef -> ct_DecodeDirectRef <- ct_DecodeDirectRef -> ct_FindDITEntry <- ct_FindDITEntry <- ct_FindDITEntryByRef PHSS_22929: CR: JAGad38822 SR: 8606169547 The Content Disposition and Content ID fields of a message become corrupt when replying/forwarding using the Ccmail 6 client. PHSS_22995: CR: JAGad29260 SR: 8606159934 If a message coming in through the unix gateway, destined for a Notes user, contains an empty From address in the header section (HFrom: <>), omrouter non-delivers this message and the following error messages are logged: 08/29/2000 12:39:11 PM OMRTR-GW1210: Failed to add entry to text list.Entry : *NumCCRecips*Bad* 08/29/2000 12:39:11 PM OMRTR-GW2190: Sending Non-Delivery Notification to ... 08/29/2000 12:39:11 PM OMRTR-GW2191: Successfully sent Non-Delivery PHSS_22990: 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. PHSS_22699: CR: JAGad21983 SR: 8606152653 The UXO_CHECK_TYPES_OF_DDA general.cfg configuration option can be used to specify synonyms for the RFC-822 domain defined attrubute type (DDT1). However, for addresses which are NOT routed through the internet gateway, those using DDT1=RFC-822 are treated differently to those which use DDT1= For instance, assuming : There is a route for "unix" through the internet gateway. There is a route for "if" through the SendMail interface. general.cfg contains these settings : UXI_NAME_MAPPING=TRUE UXO_NAME_MAPPING=TRUE BRW_NAME_MAPPING=TRUE UXO_CHECK_TYPES_OF_DDA=a,RFC-822,HPMEXT1,HPMEXT2,HPMEXT3,HP EXT4 Then, the addresses are : As entered Displayed in internet mailbox a/unix(RFC-822|r@m.cow) r@m.cow b/unix(a|r@m.cow) r@m.cow c/if (RFC-822|r@m.cow) r@m.cow d/if (a|r@m.cow) d/if////////a/r#a#m#f#cow@m.cow There are arguments both ways for treating the addresses routed through "if", however, the treatment should be consistent. CR: JAGad25146 SR: 8606155833 No way to specify aliases when creating many users with 'omaddu -bulk'. CR: JAGad25316 SR: 8606156005 On an Ensim Linux machine. When child processes terminate, they do not disappear completely as expected, instead they become zombie processes. These zombie processes are marked with when looking at process id information on a system. This in turn can cause some processes, such as advmail.sckd to hang using large amounts of system resource. This will also cause problems when the system runs out of available process ids because they are all tied up by zombie processes. CR: JAGad26547 SR: 8606157213 Subject and body of message generated for Japanese users exceeding their message store limit should be in Japanese. CR: JAGad27572 SR: 8606158242 According to RFC-1741 binhex file attachments should not be encoded for transport. Item browser by default uses base64 encoding on binary files, with the result that the Eudora client is unable to handle the binhex file attachment. CR: JAGad28647 SR: 8606159318 Service Router takes a long time to stop (omoff -d 0 -s router) and memory consumption is incrementing on heavily loaded systems when vir*s ruleset is enabled (ALL-ROUTER.VIR). In fact each message that passes through service router causes a loss of just over 1K of memory. CR: JAGad28840 SR: 8606159513 Various inconsistencies have been identified in the code within function definitions or calls, e.g. missing or extra parameters or wrong type of parameter. CR: JAGad29235 SR: 8606159909 Automatic filing of an incoming message to a folder by the OpenMail auto-actions doesn't update the item count on the Web Client folder page in the current session. CR: JAGad29644 SR: 8606160320 The Service Router suffers from [OM 28874] errors when processing certain messages from the SendMail interface When doing filetype coercion on the binary attachment it is reading past the end of file while trying to work out what the file type is. CR: JAGad29892 SR: 8606160571 Extensions to the UAL protocol required to support MAPI Offline Folder Sync. development (OpenMail/MAPI B.06.00 release). CR: JAGad31458 SR: 8606162142 Using OpenMail Graphical Interface version B.06.00.00 with OpenMail B.06 and the client language set to GERMAN, it is no longer possible to logon. CR: JAGad31479 SR: 8606162163 On an Ensim machine, the IMAP server randomly drops socket connections to the UAL giving the error message: sock3/BYE: r {OpenMail IMAP Server not available} CR: JAGad32112 SR: 8606162796 Netscape Messenger hangs during first access of a message with a pathname containing backslash characters in the content-type. CR: JAGad33512 SR: 8606164212 The folder size is not updated in the Web Client 5.10 Filing Cabinet listing even after filing a few messages to the folder. The user needs to logoff and re-login to view the updated size. CR: JAGad33773 SR: 8606164474 The OpenMail Internet gateway rejects multipart/signed messages if one of the multipart boundary-end markers is missing. Similarly, if such a message is encountered in the OpenMail message store, the Item Browser may hang while attempting to display the message. CR: JAGad34214 SR: 8606164917 OpenMail GR6 + Oct00PP - Outlook Express (IMAP) fails to download a message that contains a "special" character in the friendly name. Special = ()" CR: JAGad34502 SR: 8606165208 Under some circumstances moving or copying a message to the Bulletin Board Area (rather than an individual BB) causes a fatal UAL error: "The content record requested does not exist in this container." CR: JAGad34729 SR: 8606165435 The top line in the script is #!/bin/sh which does not exist on machines running solaris. CR: JAGad37344 SR: 8606168062 A new username that differs from an existing one in case only (eg. "John deVere" as compared to "John Devere") was not recognised as clashing, potentially resulting in more than one user with the same name. CR: JAGad37410 SR: 8606168129 omlicmon aborts when virtual licensing is used and OpenMail is not omshut/omrc for long periods (months). Same issue also would show up when not using virtual licensing, but when the nodelock file is "touched" a lot. omlicmon aborts with the following in omshowlog output: SERIOUS ERROR Licence Monito(Licence Monito) 10.15.00 19:30:16 [OM 14460] Unexpected error in License monitor. Group = 1; Reason = 24. Error text follows : Too many open files SERIOUS ERROR Licence Monito(Licence Monito) 10.15.00 19:30:16 [SYS 24] Too many open files File Name: OMDATADIR/temp/0ge23mu -> lic_OpenShadowFile <- lic_OpenShadowFile -> im_CrNewTempItem -> im_GetNewTempItemNum <- im_GetNewTempItemNum <- im_CrNewTempItem -> lic_ListShadowFile <- lic_ListShadowFile -> lic_CloseShadowFile <- lic_CloseShadowFile -> lic_OpenShadowFile <- lic_OpenShadowFile -> im_CrNewTempItem -> im_GetNewTempItemNum <- im_GetNewTempItemNum CR: JAGad37711 SR: 8606168431 The OpenMail notif.mon program does not output entry and exit procedure-level trace to the omshowlog log files. PHSS_22457: CR: JAGad30987 SR: 8606161671 OpenMail support required for MAPI Offline Folder Sync. EEP PHSS_22361: CR: JAGab84570 SR: 8606112256 Randomly lost BB ACL flag, causes ACLs to be relaxed on BBs. CR: JAGad05041 SR: 8606135910 Even if the UAL_MSTORE_SIZE_LIMIT is specified and UAL_SIZE_MSG_TO_ENU is set to TRUE in the user's configuration file, when this user's message store size exceeds limit, no message is sent to the ENU to notify this fact. CR: JAGad05207 SR: 8606136077 Multibyte subject of warning message for mbox exceeding the size limit is garbled when viewed with IMAP4 and POP3 clients. CR: JAGad11128 SR: 8606141768 omcpinu fails to restore mailboxes with the error "[OM.PM 1004] Internal problem detected, see the log files" CR: JAGad13619 SR: 8606144279 Unix gateway aborts when certain messages are being sent out. These messages originate from the cc:Mail client and have an invalid CONTENT_FILE record, containing miscellaneous text from the message in the CONTENT-DISPOSITION field. CR: JAGad14574 SR: 8606145237 When a tray is accessed by an IMAP client, a sequence number is assigned to each item. omcpinu does not assign unique sequence numbers to items which it copies into a user's message store. This means that IMAP clients, e.g. Netscape Messager, can become confused and fail to display all items in the user's tray. CR: JAGad15232 SR: 8606145896 Multiple OM 16130 errors get logged to the fatal log file when a Japanese OMGUI client is used to print a message via the OpenMail server. CR: JAGad15339 SR: 8606146003 If an address has the i-tx field and using address mapping format 3 then the address comes out as name.i*i.surname@xxx.yyy.zzz CR: JAGad21220 SR: 8606151881 Following ServiceGuard Failover, omrc sometimes exits with the following error: "omrc : There are still ual.remote/ual.local processes running from a previous OpenMail start-up. If you wish to restart OpenMail cleanly, run omshut or wait for the following processes to terminate, then run omrc: Active Session PID:" CR: JAGad21785 SR: 8606152455 The format of sendmail.cf has changed for Sendmail 8.10. OpenMail needs to be able to configure this file during installation. CR: JAGad21810 SR: 8606152480 OpenMail gets compilation errors when built with RedHat 6.3. CR: JAGad23468 SR: 8606154150 If you install Openmail B.06 on a Linux machine e.g. using "rpm -i" and then remove it e.g. using "rpm -e" a lot of files get left on the machine. CR: JAGad23509 SR: 8606154191 Linux RedHat 6.3 ships xinetd instead of inetd. This means that during OpenMail installation the openmailpxy and ccmtp services are not set up correctly. CR: JAGad23675 SR: 8606154357 unix.in process terminates with bus error when processing a TNEF attachment. CR: JAGad23678 SR: 8606154360 Message "The server responded: Cannot append that message" is displayed when trying to move a message from the (local) "Sent Items" folder to an OpenMail folder using Outlook. If UAL tracing is switched on, the problem seems to be in the UAL include file command processing : INCLUDE FILE Command: Flags=0x20001, File='OMDATADIR/user/u000091/TMPA22529/02rbts9' INCLUDE FILE Command: MsgRef=0, DirectRef=000fdda33baa2e12, ToCode=0, FromCode=0 CharSet=iso-8859-1 INCLUDE FILE Command: Subject = '' INCLUDE FILE Command: Creator = '' INCLUDE FILE Reply : NewItemRef=0, NewAbsRef=0, DirectRef=, Error Text ='' **** REPLY Error Number = 1502 Group = 0, Reason = 0 GET ERROR MSG Command: ErrNo=1502, ErrNoExtra1=0, ErrNoExtra2=0 GET ERROR MSG Reply: ErrorText1: Requested conversion is not available on this system GET ERROR MSG Reply: ErrorText2: CR: JAGad24043 SR: 8606154726 Certain types of non-delivery notification from OpenDesk (such as when a message is sent to an invalid OpenDesk mailnode) do not have the correct Ack ID, after the OpenMail Desk gateway has processed it. If the original message came in via X400, then this problem can lead to the OpenMail X400 gateway rejecting the NDN because the ACK ID does not contain the original CAP (Country, Admin Domain and Private Domain) information. CR: JAGad25016 SR: 8606155703 RedHat's rpmlint reports lots of errors regarding the openmail rpm packages. The number of these errors needs to be reduced. CR: JAGad27743 SR: 8606158413 If the general.cfg setting : MDC_DDS_DELETE_DATA=TRUE is active, then messages browsed using IMAP clients appear to be blank. PHSS_21944: CR: JAGab33837 SR: 1653262501 If a recepient name in the DL is ambiguous while sending a message or while checking DL names from the Web Client 5.10, the list of alternate names is always sorted on the default sorting order even if an alternate sorting order has been specified in the profile file (using the tag DL-ALT-NAME-SORT). CR: JAGab63204 SR: 8606101643 This is an interoperability problem and an ER for Web Clients. When the Web Client attaches a local file, the file name is not displayed correctly on Internet clients (Outlook Express in IE4). The worst situation occurs when a BINARY file is attached (e.g., BMP). The filename is lost and, because it is a binary, OE will display the item's filename as something like ATT00225.dat. It is almost impossible to open such item because both the filetype and filename extension are unknown. Happens for both Web Client 5.10 and Web Client 6.0. CR: JAGab72994 SR: 8606105114 IMAP clients are unable to view attachments of messages which have no body parts (i.e. the message is only an attachment). CR: JAGac29290 SR: 8606114526 It should be possible to install and run OpenMail on HP-UX systems where the LSSERV components have not been installed. This already works on Solaris and Linux. CR: JAGad00687 SR: 8606131537 While viewing the auto-answer text in PAW using IE, line breaks are getting removed and the entire text is appearing in a single line. This problem does not occur on Netscape. In addition, the column size of the auto-answer text box should be increased to 72-80 characters so that the cut/paste operation from clipboard will be easier. The current column size is 40. CR: JAGad01673 SR: 8606132524 The background search process fails to do a search on the contents of a note. CR: JAGad01880 SR: 8606132732 The unix gateway fails to parse certain incoming messages containing Delivery Status Notification reports. CR: JAGad02855 SR: 8606133711 Desk Gateway socket handler (desksock.recv) could sometimes abort with an ENOBUFS error, if memory is short on the machine. CR: JAGad03000 SR: 8606133860 If an attempt is made to update the 000002k file (which holds Outlook delegate information) by using tfbrowse to convert this to a textual representation, edit the textual representation and then convert it back to transaction file format, corruption takes place. For instance, if the name "Outlook Delegate/local" is the name of the delegate and this process is undergone without any edits, after replacing the 000002k file with the new file, the Delegates tab under Tools,Options shows "Delegate/Outlook///local" where before it showed "Outlook Delegate". CR: JAGad03146 SR: 8606134007 Login problem with Web Client 6.0. CR: JAGad03894 SR: 8606134759 omlimits warning messages are not delivered to a user's mailbox when the mailbox size has been exceeded. The problem is specific to users who are using a different language setting to the openmail server. CR: JAGad04005 SR: 8606134871 Japanese cc:Mail Mobile users has a reply problem when the original message is created by Outlook + MAPI. CR: JAGad04018 SR: 8606134884 With the general.cfg option : BRW_NAME_MAPPING=TRUE enabled. The name mapping behaviour is not applied to "Return-Path:" lines for messages originating within the OpenMail network. For instance, if the OpenMail user "auser/local" had an internet address mapping of "auser@laza.not.hp.com", then a message from this OpenMail user will contain the following lines when browsed using an IMAP or POP3 client : Return-Path: From: auser@laza.not.hp.com CR: JAGad05750 SR: 8606136626 Problems decoding UTF7 for non-ASCII folder names in IMAP client CR: JAGad06793 SR: 8606137667 When submitting messages via the SMS2000 X25 protocol, the originator sometimes got back an NDN with the following error text: 'Message unable to be mapped at gateway' [OM 9400] Supplementary Information: (SMS) SMS2000: Operation rejected because argument value(s) missing or invalid. [Result = 1] In all cases that were investigated, the recipient had infact received the SMS message, so the NDN was very misleading. Also, when this happened, the recipient would sometimes receive the message two or three times. CR: JAGad07023 SR: 8606137874 Opendesk Gateway (outgoing) sometimes aborts, when trying to map the ACK database file into memory. CR: JAGad07491 SR: 8606138290 Attachment descriptions of file attachment are corrupted when accessing a B.06.00 OpenMail server using WinOMGUI-J or the ICE-NIPPON web client profile. The filecode is displayed instead of the file description. The display in WinOMGUI-J looks something like : KONO KOMOKU NO TAIPU HA p. (2147) DE TEKISUTOTOSHITE..DEKIMASEN Where capitals represent Japanese Katakana/Hiragana characters. CR: JAGad08966 SR: 8606139655 The Mime internet gateway does not recognise fred.txt.vbs as being of type "vbs". The extension after the final dot should be used when determining the type of a file CR: JAGad11000 SR: 8606141637 In certain network environments, since the changes to the UAL file transfer protocol made in the February 2000 periodic patches, some UAL sessions could disconnect or hang when sending messages. CR: JAGad11143 SR: 8606141783 With the genearal.cfg tweak SR_FILTER_TYPES_OF_ATT=2188 set,the vbs attachment name is deleted but not the Content-Disposition header from the vbs attachment. CR: JAGad12244 SR: 8606142895 An extension of the UAL_GETFIL command is required to allow a client to obtain the name of a server file that contains the settings for the parameters to the Outlook secur*ty patch. These settings must configurable on both a system and per user basis. CR: JAGad12543 SR: 8606143206 The portal daemon dies if the tweak UAL_SINGLE_TEMP_DIR has been specified in the general.cfg file and a hostname lookup request with a new character set is received from a Web Client 6.0 session. CR: JAGad12554 SR: 8606143218 If an ACL is created for a Request Server Script, and a user with a space character in its mailnode name is added to that ACL with execute permissions, any request made by that user to that script fails. The user should be able to access the script if they have been added to the ACL with the appropriate permissions. CR: JAGad21211 SR: 8606151872 Cannot back-out Feb00 or May00 Periodic patches, to a pre-Feb00 version. omunpatch would report errors of the following form: ld.so.1: omeval: fatal: relocation error: file OMBINDIR/lib/libom_nfda.so: symbol er_ErrorInfo: referenced symbol not found Note, backing out from May00 to Feb00 is OK. PHSS_21439: CR: JAGab32379 SR: 1653240259 Unix gateway aborts with OM-UX 1131 if DDV1 address has multibyte characters CR: JAGab32452 SR: 5003366708 Event logging in all areas of SMS is poor. CR: JAGab32488 SR: 5003454405 Messages sent with precedence bulk, junk, or list receive many autoreply messages back (when recipients switch on the autoreply) which is unnecessary. CR: JAGab33999 SR: 1653285569 Missing CREATOR rec. from Del. Envelope causes X400 to non-deliver msg. CR: JAGab34077 SR: 1653296350 Acks are not being re-routed when the SR_RESOLVE_MASK general.cfg option is set. CR: JAGab34096 SR: 1653298653 When using a PDL within another PDL, the PDL can end up pointing at itself as its parent CR: JAGab34157 SR: 1653306589 omscan when run in fix mode (omscan -a -f) removes "lost+found" directories, making fsck impossible CR: JAGab34186 SR: 1653310714 OpenMail does not deliver incoming internet messages correctly when there are whitespaces around the "=" in a MIME Parameter in the qf file, e.g. 'HContent-Type: Multipart/mixed; boundary = "123456789"' (Note the spaces around the '='). On a SUN/Solaris server the messsage is rejected with an [OM 10250] error. On a HP-UX server, the message is delivered, but without the bodyparts. CR: JAGab34785 SR: 5003465195 Openmail GUI 6.0 allows users to send Repeat Reminder messages, under some circunstances, the messages disappear completely from the client's Out box, eventhough, the messages are still being sent out as scheduled. CR: JAGab34850 SR: D500253328 Some general.cfg values could contain charset names that include an underscore. For instance at incoming Desk and UNIX gateways. But general.cfg disallows use of underscore, or replaces it with space maybe. As a result, the above gateways do not work for such character sets. CR: JAGab74208 SR: 8606105866 On GR6 create a message and send it to yourself using Outlook. Using omcontain check that the Inbox and Sent Items (Pending Tray) copies of the message have an object file (MAPI.ObjectProperties). omcpoutu the user, delete the user, re-add the user, omcpinu the user. Now use omcontain to check the message object file - it's gone! CR: JAGab74694 SR: 8606105948 ORNs in text version of tf with no '/' are lost by tfbrowse -g CR: JAGab76033 SR: 8606106702 Local Delivery aborts when File in ~openmail/data is missing. CR: JAGab76643 SR: 8606107035 If the UAL monitor makes 3 unsuccessful consecutive attempts to connect, then it is terminated. There is no delay between these attempts and resulting termination means that the monitor has to be restarted before any further requests can be handled. A tweek, allowing a time delay between attempts to connect, and further additional attempts before failing, would mean that this problem was less likely to happen. CR: JAGab78064 SR: 8606107773 Items containing more than one 'Content-Disposition' lines for an item can cause IMAP4 clients to hang when trying to browse the item. CR: JAGab78752 SR: 8606108351 Local delivery fails with a bus error, reporting the following trace when the LD_AUTOREPLY_CHECK_ON is set and multiple Local Deliveries are in operation. SERIOUS ERROR Local Delivery(Local Delivery) 10.28.99 10:36:09 [OM 10250] Process about to terminate due to error. Signal (Bus Error) trapped by process 6957; code = 0. Procedure trace follows: <- tf_GetINT32 -> tf_MarkPrevRecord <- tf_MarkPrevRecord -> tf_GetINT32 <- tf_GetINT32 -> tf_GetINT32 <- tf_GetINT32 -> tf_ReadRecord <- tf_ReadRecord -> tf_GetINT16 <- tf_GetINT16 -> tf_GetINT32 <- tf_GetINT32 -> ld_AAReplyAlreadySent -> im_ItemRef2FName <- im_ItemRef2FName CR: JAGab82030 SR: 8606109330 cc:Mail Mobile 6.22 OpenMail edition cannot reply to messages which contain RTF files. When an attempt is made to reply to the message, the original RTF text is displayed, however, no modifications can be made to it. Items which have original filenames (created by Outlook clients) were being treated as file attachments regardless of whether they had actually now been converted to text. CR: JAGab82546 SR: 8606109847 The problem occurs when a quoted-printable subject field of a message containing multiple 8-bit characters separated by a '?' character is received at the unix gateway. Only the 8-bit characters before the '?' are decoded correctly. CR: JAGab84515 SR: 8606112206 Japanese messages which are stored in a folder on the server using IMAP4 are not readable from other standard OpenMail clients. CR: JAGab84577 SR: 8606112263 Serialised file handles are not free'd after container compaction has occured. This can cause Local Delivery to abort when it runs out of file handles. The following error is generated: [OM 28870] "To many serialised items open". CR: JAGac29346 SR: 8606114582 omcheck -i does not work on Linux, for filesets where the check data file is less than 8K in size (e.g. everything except the OM-CORE fileset). CR: JAGac29459 SR: 8606114696 MIME Content disposition still has filename under some conditions when it need not. This causes problems for some clients (mostly MS ones) Also, Content-Dispositions are mixed. For example, a multipart alternative body part has the first alternative marked as inline and the other as an attachment when they should both be inline or attachments. CR: JAGac39658 SR: 8606124275 The unix gateway crashes when receiving certain incoming messages. The message is not delivered and no non-delivery acknowledgement is returned. CR: JAGac40185 SR: 8606124793 There are particular messages that arrive through the internet(mime) gateway that causes "Outlook" to lose connection upon reading the folder where they are located in. With "omgui" there is no problem is accessing/reading the folder/msg. Outlook's error-message when opening the folder with the problem msg in: UAL Network Error: Failed to send data. The connection may have been lost. Software caused connection reset. Connection Type: Windows Sockets The ual.remote session aborted on the server; in omshowlog you'll find: SERIOUS ERROR Remote Client (U/I Access ) 12.30.99 08:16:58 [OM 10250] Process about to terminate due to error. Signal (Segmentation Violation) trapped by process 22383; code = 0. Procedure trace follows: -> ual_IsMappingAvail -> cvc_IsMappingAvail2 -> uni_GetCharset -> cvc_IsMappingAvail3 <- cvc_IsMappingAvail3 <- uni_GetCharset <- cvc_IsMappingAvail2 <- ual_IsMappingAvail -> ual_IsMappingAvail -> cvc_IsMappingAvail2 -> uni_GetCharset -> cvc_IsMappingAvail3 <- cvc_IsMappingAvail3 <- uni_GetCharset <- cvc_IsMappingAvail2 <- ual_IsMappingAvail User Name: kinderkanal / hppine83, 01>!] CR: JAGac40230 SR: 8606124838 The unix gateway truncates the incoming UUENCODED attachment file name at the first space. CR: JAGac42791 SR: 8606125848 omdbmon sometimes aborts with SYS:22 error CR: JAGac78718 SR: 8606127917 ccmobile users cannot reply to Microsoft RTF messages. Even with ConvertToRTF=1 set in ccmtp.ini, the reply is virtually illegible to the Outlook user as the standard cc:mail reply colours of yellow text on a blue background become yellow text on a white background. CR: JAGac79005 SR: 8606128205 The checks introduced by JAGab33916 to detect whether an X400 user is infact local, did not work with non-delivery rulesets CR: JAGac86611 SR: 8606129065 item.browse sometimes aborts when processing a msg with multibyte attachment. CR: JAGac86632 SR: 8606129086 ualth doesn't always detect new messages arriving in intrays. CR: JAGac86756 SR: 8606129210 omaddu without options causes segmentation violation on Solaris & Linux systems (GR6+Feb2000 PP) When omaddu is executed with invalid arguments, the usage strings are printed in a different way on Linux & Solaris & are in improper format. On Linux, some garbage charecters appear in the Usage string. On Solaris, each usage string is printed twice. CR: JAGac86786 SR: 8606129240 Segmentation Violation in test viral scanning library. CR: JAGac86878 SR: 8606129332 Dirsync impacts client directory access significantly CR: JAGac87789 SR: 8606129454 The directory synchronisation program does not modify the slave directory entry correctly when attributes have been removed (deleted) from the master directory entry. Note: This problem only occurs when the 'omresyncds' command is used to trigger a directory resynchronisation. The normal directory resynchronisation does not exhibit this problem. CR: JAGac87845 SR: 8606129510 This is an enhancement. Mobile devices do not understand HTML and they do not support Javascript and Frames, hence a new profile is required for connecting to OpenMail from such devices. CR: JAGac87847 SR: 8606129512 When OpenMail is installed, certain directories such as /etc are left with the wrong permissions. Sendmail 8.9 is very strict about permissions and it will issue a large number of error messages; it may even stop delivering the mail altogether. OpenMail does not warn the user about this problem. omrc should issue a warning when the permissions are wrong. CR: JAGac87851 SR: 8606129516 Web Client profile selection page is not accepting the HTTPS protocol in the URL CR: JAGac88829 SR: 8606129914 The November 1999 and February 2000 B.06.00 periodic patches incorrectly documented the default value for the general.cfg setting UXO_ITEMSUB_IS_FNAME as being TRUE. CR: JAGac95131 SR: 8606130260 When a message enters OpenMail through the internet gateway, the comments that are on an smtp address are lost. And consequently, they cannot be displayed when the message is read. For example, the sender: "John A. Smith" <103343.1432@compuserve.com> is saved as <103343.1432@compuserve.com> CR: JAGac95600 SR: 8606130710 in.imap41d crashes when attempting to accept a client connection (on an already busy machine with many clients connected). CR: JAGad00184 SR: 8606131026 Missing system shared library is causing webselect.cgi to abort when it is accessed in a VirtualVault environment. CR: JAGad00185 SR: 8606131027 The portal daemon uses a default value of 3 for the number of matching login names. This sometimes confuses the users when they are not able to find their names in the list. CR: JAGad00350 SR: 8606131199 If a backlog of 500 or more messages have accumulated in the ~openmail/sms/data directory, while the sms.server has been shut down, when the sms.server process is restarted, it fails to process the backlog. CR: JAGad00539 SR: 8606131389 When a fatal error occurs in the sms.server process, the error message is only seen if the sms.server process is run in the foreground, in which case the message appears on the screen. Nothing is logged to the fatal or omshowlog files. If sms.server is run in the background (default) then there is no clue as to what went wrong. CR: JAGad00698 SR: 8606131548 A large value for the DRS default connection timeout is causing performance problems for the portal daemon CR: JAGad01319 SR: 8606132170 The B.05.10.00 version of omsendin does not recognise the 8.9.3 version of sendmail.cf. It also does not recognise the 8.8.8 version available on some versions of Solaris and HP-UX. The B.05.10.00 and B.06.00.00 versions of omsendin do not reliably add an equal sign to the list in the OperatorChars option of sendmail.cf. CR: JAGad01353 SR: 8606132204 If there are more than about 60 top level folders in a user's mailbox, then omtidyu may fail to find messages for deletion in the filing cabinet. The error message : Maximum number of open Lists would be exceeded is displayed and omtidyu exits. CR: JAGad01557 SR: 8606132408 Notification server aborts in Service Guard environment with two or more standby redundant lan cards. CR: JAGad01812 SR: 8606132664 Possible inability to send message using web clients CR: JAGad01851 SR: 8606132703 omaddred will not accept filter unless -I option is given also. CR: JAGad01856 SR: 8606132708 ual library on the server is very slow - reads data 8 bytes at a time! CR: JAGad02689 SR: 8606133544 Outlook Delegate access sometimes fails when accessing the Calendar after Inbox items have been read. (Only seems to happen using Outlook 2000) The difference between OL97 and OL2000 is that when (as a delegate) I read a meeting request in the principal's Inbox the following happens: OL97: Calendar info is explicitly retrieved LocalFreebusy message is retrieved OL2000: LocalFreebusy message is retrieved Calendar info is retrieved The problem is caused by the fact that when the LocalFreebusy is obtained first an implicit list of the Filing Cabinet and Calendar takes place and these implicit list have restricted information in them and in the case of delegate access the AccessCaps are not set up. The subsequent retrieval of the Calendar information picks up the implicitly generated list information and the incorrect AccessCaps. So this problem will occur on OL2000 every time a delegate tries to process a meeting request before opening the Calendar. CR: JAGad03759 SR: 8606134624 The remote client interface is crashing occasionally when using an IMAP client under Linux. The omshowlog command shows that a segmentation violation has occured in the Remote Client Interface. CR: JAGad03776 SR: 8606134641 Attempting to access the PAW on an EP1 Linux box simply gives the ICE web client. CR: JAGad04546 SR: 8606135412 If you install any periodic patch for B.06 earlier than May 00, and then remove it e.g. using swremove (on HPUX), all the previous versions of the patched files get correctly restored EXCEPT for anything in the ...B.06.00.00/lib directory. This problem only occurs on B.06 patches, B.05 patches are fine. CR: JAGad04673 SR: 8606135539 While reading a message, the WAP client is not able to display the message content body page containing a URL. The error message "Page cannot be displayed" is shown thus indicating a WML syntax error. PHSS_20776: CR: JAGab32483 SR: 5003444679 Customer would like to disable sending when a user exceeds there omlimit limits. A new option to omlimits has been added which allows sending to be disabled when required. CR: JAGab33916 SR: 1653272351 NDN is non-delivered back to the originating user. When a message is sent to a non-existant user, the NDN being generated at the local delivery , has the primary recipient marked with all CAP[O] attr. Since we have a X.400 route added for this CAP[O] explicitly, the NDN is routed via X.400. But X.400 aborts while constructing the message and the message(NDN) is not delivered back to the originating user. CR: JAGab34044 SR: 1653291617 When a Web Client running on multiple OpenMail system is accessed,the CGI program aborts. An error 'Which OpenMail system?' is written to the Web Server log. CR: JAGab65807 SR: 8606101854 UAL aborts if Notification Server runs out of memory CR: JAGab69180 SR: 8606103019 In the situation where 2 managers have 2 different delegates who recieve the manager's meeting requests, and a meeting request is sent to both managers only one delegate receives the meeting request. CR: JAGab72452 SR: 8606104741 messages received from remote openmail systems are lost when attempting to deliver to a local mailnode which has a rule-set defined that defers mails depending on their size. CR: JAGab72649 SR: 8606104884 Aliases login doesn't seem to function properly . CR: JAGab72864 SR: 8606105045 NDN_EXTRA_INFO is not included in outgoing messages from the Internet Gateway. For instance, if a rule for an OpenMail route (see ommodrt -d) uses a file containing the lines : SIZE=10 PRIORITY=LOW ACTION=REJECT NDN-INFO="Msg reject as over 10MB" SIZE=10 PRIORITY=MEDIUM ACTION=REJECT NDN-INFO="Msg reject as over 10MB" Messages which are rejected because they match this rule should contain the text : "Msg reject as over 10MB" as specified in the rule file. Internet messages do not contain this. CR: JAGab75968 SR: 8606106664 Problem with openmail setuid programs CR: JAGab75998 SR: 8606106674 The code for the test scanning library and the code supplied by Trend Micro, are not returning the same values (in fact the complete opposites) CR: JAGab76793 SR: 8606107113 SMS gtw stops conversion of characters after @ sign in conv to GSM 03.40 CR: JAGab77480 SR: 8606107301 binary touch coverage checking needs to be done in a different way. CR: JAGab77872 SR: 8606107609 Entering a non-null subject through IE does not get registered by the browser and the subject gets stored as blanks. CR: JAGab81837 SR: 8606109138 smimetxt does not process a pgp mime message correctly. This is because of the quoted protocol. CR: JAGab82255 SR: 8606109555 With multiple sign-ons message store sizes reported by omscan and clients can be incorrect or do not change until log out. each process records it's own size changes but other processes do not have access to this information. It is only written to disk when the process shuts down. Pending deletes only change sizes when the phsyical delete takes place. CR: JAGab83272 SR: 8606110523 Currently all the users using a profile will be connected to the same server. This limitation should be removed by having an automatic lookup facility to locate a user's OpenMail server hostname and then connecting to it. CR: JAGab83274 SR: 8606110525 Openmail LDAP server does not force an unbind of an authenticated session when an anonymous bind is received. This is supposed to be LDAP V3 functionality. CR: JAGab83278 SR: 8606110529 This is an enhancement. To prevent sensitive information from being displayed via the internet, the Bulletin Board feature will be denied from Web Client 6.0. CR: JAGab83749 SR: 8606110999 To improve the access-control for OpenMail via Virtual Vault, a feature is required by which the administrator can selectively enable/disable the Web Client access for a user. CR: JAGab83752 SR: 8606111002 This is an enhancement. Users of IMAP/POP don't have access to the auto-actions functionality of OpenMail. Providing a truncated Web Client profile will be useful to them. CR: JAGab84076 SR: 8606111938 Japanese conversion to ISO-2022-JP does not fully conform to RFC-1468. The end of text should be in ASCII (ESC "(B"). CR: JAGab84362 SR: 8606112091 Messages are undelivered when the file transfer parameter IM_FILE_ATTRIBUTES is not present. CR: JAGac20259 SR: 8606113989 The message store search is failing for the Web Client 6.0 if the previous search results are displayed and the search is submitted in succssion a few times CR: JAGac20262 SR: 8606113992 If any DL in the DL folder is created/updated, then the DL folder contents don't get displayed within the same session. CR: JAGac23147 SR: 8606114169 omreqlic requests to linux machines have there replies rejected 50% of the time with error [OM 28211 ] logged in the log file. CR: JAGac29140 SR: 8606114376 Same as submitter text CR: JAGac29288 SR: 8606114524 If I log onto hpopdlct.pwd.hp.com as user Silver with no password and perform a search for all messages, then the resulting list should contain (currently) 8 items but the list is empty. The UAL is returning a 555 (invalid list ref) to a request for the search list file. CR: JAGac39969 SR: 8606124586 Cannot execute Domino 4.5 Notes Executables on Solaris 2.5.1. When the attempt is made to execute any of the four Notes Api programs in OMBINDIR/notes.inst/sun/4500, the following message is displayed: libc internal error: _rmutex_unlock: rmutex not held. CR: JAGac40302 SR: 8606124910 The situation arises when using Netscape version 4.06 and later. When used with earlier versions of Netscape, and with IE4 and IE5 the OpenMail Web Client 6.0 does not exhibit the problem. The circumstances are as follows: When an attempt is made using the OpenMail Web Client 6.0 to create a Rule to, say, automatically autoforward or redirect incoming mail (eg during a vacation period), and the "Date Range" option is selected, the user is presented with two date range fields, which can be edited, that initially contain by default today's date, and a date a week from today. These dates are presented with a year 100 instead of 2000. When an attempt is made using the OpenMail Web Client 6.0 to search for messages matching some filter criteria on the delivery/create/expiration dates(for example, all messages delivered on a particular date), the user is presented with the default date as today's date. This date is presented with a year 100 instead of 2000. CR: JAGac40677 SR: 8606125286 Unable to customise sendmail.cf version 8.9.1 when installing on Solaris PHSS_20551: CR: JAGab83434 SR: 8606110686 The PC Admin Client can not connect to the OpenMail server. PHSS_20012: CR: JAGab32576 SR: D500419564 The existence of "filename" field in the MIME header for bodypart text will cause most browsers to handle it as an attachment, not the bodypart text. The field is redundant for bodypart text. Please see related problem JAGab37437 which relates to the same problem for the internet gateway. CR: JAGab34141 SR: 1653304451 When the dirsync server , encounters a MODIFY Req for an entry that doesn't exist, it basically ignores it if it is a OM<->OM sync. The function ds_DoUpdate, which handles this, goes ahead to add the request, if we have a OM<->SoftSwitch Sync. A combination of both pEntry1 and pEntry2 which would contain all the necessary attributes, should have been added. CR: JAGab34162 SR: 1653307066 Web Client 6.0 program aborts while attempting to logon with a long multi-byte user name. CR: JAGab34164 SR: 1653307249 Basically, the customer was using the 1984 X.400 standards, which doesn't support -TX ATTR. And, when a mail is sent from One OM User to another OM User (who has -TX ATTR) , and if the mail is routed via X.400, then we encounter a doubly wrapped message at xport.in. This message, though it is decoded, the external Dummy DL is used in this case. Instead, the Internal Encoded DL should be used, which contains the -TX ATTR. CR: JAGab34183 SR: 1653309591 Cannot mail to a recepient having OU*-TX and DDV fields in his address. CR: JAGab34770 SR: 5003458851 The failing of the generation of an NDN causes Local Delivery, Service Router or Unix Gateway to loop and eventually abort. CR: JAGab35487 SR: D500353086 When adding several users to a public distribution list (PDL), omaddpdln fails and the following message is logged to the OpenMail log (viewable with omshowlog) : WARNING Administration(omaddpdln ) 03.16.98 09:27:05 [OM 2214] Unable to re-allocate memory. realloc errno 12 size 77729 ERROR Administration(omaddpdln ) 03.16.98 09:27:06 [OM 2207] Unable to allocate memory. < - da_FindAttribIntName -> da_FindAttribIntName < - da_FindAttribIntName -> nm_IsT61Field < - nm_IsT61Field -> nm_IsT61Field < - nm_IsT61Field -> nm_IsT61Field < - nm_IsT61Field -> nm_IsT61Field < - nm_IsT61Field -> nm_IsT61Field < - nm_IsT61Field -> nm_IsT61Field < - nm_IsT61Field CR: JAGab35885 SR: D500413443 Move a BB with Items in it to another BB and Sync to the Remote Server, Only the BB gets added on the RemoteServer, Items do not get added hence resulting in BBs out of sync. CR: JAGab36268 SR: D500430124 tf.browse -g can't handle people mover records when newline characters are found in a string. CR: JAGab36274 SR: D500430421 The structure of the message store does not allow more than 358,999 users to be configured on a server. CR: JAGab37437 SR: D500420604 Using the subject of an item in the "filename=" part of a Content-Disposition line of a MIME message often causes problems for Internet mail readers. It should be possible to disable this behaviour. Please see related problem JAGab32576 (SR D500419564) which relates to the same problem for Pop3 and IMAP4 client access to the Openmail message store. CR: JAGab39182 SR: 8606100829 If a user is added as a delegate using Outlook and subsequently that user has part of his name or mail address modified then the old delegate name can be listed within Outlook but cannot be deleted. CR: JAGab39209 SR: 8606100833 Directory Mapping uses non-x400 attributes such as FF for lookup. CR: JAGab43863 SR: 8606101161 item.browse crashes when " is present in the attached filename. CR: JAGab45433 SR: 8606101253 The Openmail POP3 server (in.pop3d) since PP4 consumes more CPU time than before PP4. CR: JAGab48848 SR: 8606101412 Server changes to allow Entrust integration: 1. UAL_CHKNAM command extended to return internet-style address to match email address in user's certificate. 2. 'omshowu' command has extra option: -S to display a user's internet address. 3. New directory attribute introduced: SMIME-ADDR (attr. no. 1300) 4. Modify Unix Gateway to process new Clear Signed message format. 5. Modify Item Browser to process new Clear Signed message format. 6. Write smimetxt : a converter from S/MIME to text. CR: JAGab48993 SR: 8606101413 Server and MAPI/SP performance improvements are required for the Outlook 5.30 client. CR: JAGab52686 SR: 8606101484 When OpenMail internet mail gateway service tries to send out a message which has a long subject in multibyte (Japanese) language, the service process loops endlessly in handling this message, passes huge blank message data to sendmail. It makes OpenMail's gateway service stop and server's disk full on /var/spool/mqueue. Problem is more likely to occur when UXO_MIME_SUBJECT_ENCODING is set to "B" or "Q". CR: JAGab63192 SR: 8606101630 When an invalid Read Acknowledgement is received by the x400 out mapper, the mapper aborts rather than gracefully swallowing the error. CR: JAGab63519 SR: 8606101674 POP3 "list" and "stat" commands are inefficient in in.pop3d CR: JAGab65100 SR: 8606101738 GR6 fixes: D500 405621 IMAP server loops when UAL session times out. D500 419747 Server-push prevents use of NS datagrams for UAL_NEWMSG command These fixes are applicable to B.05.10 clients and need to be included in the GR5_PATCH source. (Especially applicable to IMAP and POP clients) CR: JAGab65826 SR: 8606101865 Not deactivating containers correctly. CR: JAGab65894 SR: 8606101892 When a user is running 2 clients, then the sessions can be come out of sync concerning their knowledge of the tray sizes. It is therefore possible to end up with a negative tray size. For instance: This can happen with the filing cabinet is client 1 moves some items into it. Client 2 may then delete these items, so will decrease the tray size, having not increased it in the first place. If an attempt is made to copy stuff back into the filing cabinet from client 2, its tray size is perceived to be negative. This is treated as a hugh positive number and so will exceed it's tray limit. CR: JAGab68818 SR: 8606102816 ccmht2rtf double freeing on exit and so giving a bad exit code. NB the exit code was only ever checked for the July99PP. CR: JAGab69420 SR: 8606103098 SCO did not allow non-root users to do "ps" listings. However, omrunning was SetUID root on all platforms. CR: JAGab69554 SR: 8606103168 Long login names get truncated in the logon page of the Web Client 6.0, the next time the page is accessed. CR: JAGab69581 SR: 8606103183 For some messages either being browsed by internet clients or being sent out through the Internet Gateway using MIME format, inline body parts have a filename specified. The messages contain a line like : Content-Disposition: inline; filename="BDY.RTF" Although this is correct according to the RFC 2183 standard, many internet clients will not display the item inline - they are treated as an attachment instead. This is a significant usability problem and thus, it should be possible to configure OpenMail such that it will not include a filename for any "inline" items. CR: JAGab69827 SR: 8606103270 SUR(omdosur) fails when restoring a mailbox containing messages generated by outlook in MAPI mode but works when restoring a mailbox containing messages generated by other clients such as OMGUI. omdosur fails with the error message : Cannot create file CR: JAGab70399 SR: 8606103536 If a message is sent from in internet user to an OpenMail user who has an autoforward set which : 1. forwards the message to an internet user 2. retains the original sender of the message. The autoforwarded message received by the internet user does NOT have the original sender. CR: JAGab70691 SR: 8606103672 The UAL call is returning error when the changed/newly created private DLs are accessed. CR: JAGab70712 SR: 8606103683 The internet gateway's unix.in process segmentation violates when processing certain MIME messages containing TNEF encoded files CR: JAGab70735 SR: 8606103696 The following default Notes Gateway database files are corrupted by installing the August periodic patches : HP-UX B.05.10 patch PHSS_19170 and PHSS_19171 : OMBINDIR/notes.inst/hpux/4103/omconfig.ntf OMBINDIR/notes.inst/hpux/4103/omnames.ntf OMBINDIR/notes.inst/hpux/4500/omconfig.ntf OMBINDIR/notes.inst/hpux/4500/omnames.ntf OMBINDIR/notes.inst/hpux/r337/omconfig.ntf OMBINDIR/notes.inst/hpux/r337/omnames.ntf AIX B.05.10 patch PASS_17010 : OMBINDIR/notes.inst/aix/4103/omconfig.ntf OMBINDIR/notes.inst/aix/4103/omnames.ntf OMBINDIR/notes.inst/aix/4500/omconfig.ntf OMBINDIR/notes.inst/aix/4500/omnames.ntf OMBINDIR/notes.inst/aix/r337/omconfig.ntf OMBINDIR/notes.inst/aix/r337/omnames.ntf Solaris B.05.10 patch PFSS_17010 : OMBINDIR/notes.inst/sun/4500/omconfig.ntf OMBINDIR/notes.inst/sun/4500/omconfig.ntf OMBINDIR/notes.inst/sun/4500/omnames.ntf HP-UX B.06.00 patch PHSS_19172 and PHSS_19173 : OMBINDIR/notes.inst/hpux/4500/omconfig.ntf OMBINDIR/notes.inst/hpux/4500/omnames.ntf OMBINDIR/notes.inst/hpux/4620/omconfig.ntf OMBINDIR/notes.inst/hpux/4620/omnames.ntf AIX B.06.00 patch PASS_17011 : OMBINDIR/notes.inst/aix/4500/omconfig.ntf OMBINDIR/notes.inst/aix/4500/omnames.ntf OMBINDIR/notes.inst/aix/4620/omconfig.ntf OMBINDIR/notes.inst/aix/4620/omnames.ntf Solaris B.06.00 patch PFSS_17011 : OMBINDIR/notes.inst/sun/4500/omconfig.ntf OMBINDIR/notes.inst/sun/4500/omnames.ntf OMBINDIR/notes.inst/sun/4620/omconfig.ntf OMBINDIR/notes.inst/sun/4620/omnames.ntf This is only a problem when installing a NEW OpenMail Connector for Lotus Notes. Existing installed OpenMail Notes connectors should not be affected. CR: JAGab71129 SR: 8606103949 Users that have had Physical Delivery (PD or PD-TX) attributes added to their directory entries cannot then be looked up cross-server for the purposes of getting their Outlook FreeBusy time or their Outlook delegate capabilities. This causes FreeBusy checking when planning a meeting and replying on behalf of a principal to fail. CR: JAGab72352 SR: 8606104673 The CompMAPIProps of the Sent Items messages get truncated by the UAL when these Props are being rewritten after the mesg has been UAL_MOVEd to the Pending Tray. (Code in ual_mapi.c overwrites the input buffer containing the MAPI props (routine ual_ConvMAPIProps) CR: JAGab73411 SR: 8606105379 The checking performed by omaddred is insufficient. CR: JAGab74688 SR: 8606105942 Repeated calling of the UAL command UAL_DELCAP (get delegate caps) eventually causes a serious server (ual.remote) error: "A fatal error has occurred - see the system log file. Too many Transaction Files open, cannot open any more." CR: JAGab74934 SR: 8606106089 Messages from Lotus contain a 2 digit year field after 2000 whereas x.400 expects a 4 digit year after 2000 as per the mawg specs for file transfer bodyparts. CR: JAGab75964 SR: 8606106663 Not checking parameters enough PHSS_20045: CR: JAGab77877 SR: 8606107612 Service Router leaks memory when rulesets are enabled. PHSS_19172: CR: JAGab32489 SR: 5003454785 When Transient DRS children timeout, there are situations where the DRS could abort. CR: JAGab34013 SR: 1653286757 The unix.in process is not able to process some messages sent by outlook express. The error in omshowlog: SERIOUS ERROR Internet Mail (Incoming ) 10.29.98 07:09:04 [OM 10250] Process about to terminate due to error. Signal (Segmentation Violation) trapped by process 29848; code = 0. Procedure trace follows: < - ux_InStrCaseCmp -> ux_InStrCaseCmp < - ux_InStrCaseCmp -> ux_InParseArpaList -> mim_ScanArpaStrForSpecialChar < - mim_ScanArpaStrForSpecialChar -> mim_SpaceTrimming < - mim_SpaceTrimming -> ux_InConvArpaORNToORN ... The message will remain in the sendmail queue until it has expired. It is related to the layout of the email-addresses: "< "< "Sandrina Hernou""" < shernou@bru-hub.dhl.com> Too many of these will fail the unix.in process. CR: JAGab34149 SR: 1653305789 A kind of corrupt message in outtray, which lacks real data for a DL, can cause omcpinu to fail with bus error. CR: JAGab34153 SR: 1653306381 If an autoforward is set to a non-existant Internet user on a remote machine, the NDN can loop forever between sendmail and Openmail. CR: JAGab34175 SR: 1653308544 Delivery Acks sent from HP Desk and destined for an X400 user, are not accepted by a Microsoft Exchange MTA. CR: JAGab36232 SR: D500428383 Viral cleaning capability required for OpenMail. CR: JAGab36250 SR: D500429423 The following commands do not work on Solaris : omresetmn omaddmnmp ommodmnmp omdelmnmp omshowmnmp The output of the commands is similar to : OMBINDIR/bin/omshowmnmp: function: not found CR: JAGab36271 SR: D500430249 Orphans containing "MAPI 1.0 embedded message" created by some tnef files going through unix.in. This only happens after the June 99 PP. CR: JAGab36273 SR: D500430413 If the UAL test harness is used in simple list mode and an item in a list does not have a creator specified, then on Solaris, and perhaps AIX, the test harness may abort with a segmentation violation. CR: JAGab37632 SR: 1653308734 Gapi fails with OM_TEMPORA_ERROR when it encounters attachments from Internet and also RFC2157 compliant. CR: JAGab39965 SR: 8606100966 When listing files that contain blank lines, the Openmail cd browser may duplicate said lines. CR: JAGab49811 SR: 8606101415 The UAL cannot connect to a local Directory Relay Server in Simple Service Guard configurations. CR: JAGab67687 SR: 8606102175 A new defect was introduced with the July OpenMail periodic patches. If a cc:Mail user receives a message from an Outlook user that contains an RTF attachment (by default an Outlook user will send RTF text), then any attempt to reply to or forward that message will fail. Instead you will get a cc:Mail error dialog box containing the text: 'The file conversion did not succeed [Codes: 1501:0:0] [SRCUAL.C"207]' You cannot then forward that message. If you try to reply to it, everything may appear to be as expected but a body part of the message received is missing. PHSS_18905: CR: JAGab34711 SR: 5003444174 Corruption in the DIT upsets OpenMail very seriously, but problems do not become visible until more damage is done. CR: JAGab34106 SR: 1653299818 omdbmon process occassionally aborts with a SYS 22 error CR: JAGab36206 SR: D500427419 Performance improvement CR: JAGab36209 SR: D500427443 Inefficient code path in the source CR: JAGab36208 SR: D500427435 Inefficient code paths CR: JAGab36207 SR: D500427427 Excessive function calls in the openmail code. CR: JAGab36251 SR: D500429431 An interim enhancement to partially address 1653 240598. Aim for 20% (heavily system dependent) reduction in elasped/cpu time. CR: JAGab32586 SR: D500428334 Unix Gateway fails while trying to decode TNEF CR: JAGab33495 SR: 1653221341 It needs to be made clear that processes accessing a directory before omdiropt has completed will continue to use the original directory, not the new one. CR: JAGab36218 SR: D500427906 Att names decoded from TNEF sometimes mismatch attachments. CR: JAGab36255 SR: D500429530 No 3 requirement for SR 1653229252 not included in May PP. 3. at 'Attach Local File' window, the icon label "tenpu" (attach) is already used in 'New Message' window. We recommend that this be changed to "tenpu jikkou". CR: JAGab36235 SR: D500428839 When omdref is used with a Direct Reference belonging to the Bulletin Area folder (i.e. has item type -70), an error occurs, and the following output is displayed Failed to open parent of 3/2407: The file-id/item-number supplied is invalid: it must be greater then zero CR: JAGab34006 SR: 1653286120 If a coding error in cd.browse causes it to crash, a blank attachment, rather than an error message, can result. CR: JAGab35879 SR: D500413104 With multiple queues, the possibility that a message obsoleting a previous message may arrive before the message it will replace. This is particularly the case if the replacement message is being used to cancel the message (it will therefore be smaller and is more likely to overtake the original). This is not a completely new problem (it could happen with sendmail) but is more likely now as there are more points at which it could happen. The Samsung client makes use of this feature. CR: JAGab36219 SR: D500427914 Multibyte filenames handled incorrectly when extracted from winmail.dat CR: JAGab34063 SR: 1653294579 MIME encoded internet messages originating from a MAPI client often contain an attachment of type : 'application/ms-tnef' This contains information about MAPI properties of the original message. It may also contain attachments to the message. By default, the OpenMail internet gateway saves the whole of this attachment in a file called "WINMAIL.DAT". Clients using pre-OpenMail MAPI B.05.20 service providers expect this WINMAIL.DAT file, however, they do not expect it to contain attachments and do not recognise them. Similarly, non-MAPI clients only recognise a WINMAIL.DAT file and do not know that attachments to the original message are encoded inside them, effectively data loss. The OpenMail internet gateway can be configured to work better with OpenMail MAPI B.05.20 service providers and later by setting the general.cfg option : UX_PRE_5_20_COMPATIBILITY_MODE=FALSE If this is set, the information from the 'application/ms-tnef' attachment is extracted into an object file, except for original message attachments encoded in it, which are extracted as separate attachments to the message. CR: JAGab34116 SR: 1653300889 The outbound unix gateway was using the content originator as the SMTP envelope originator. This meant that if the envelope originator (aka Return-Path:) was different from the content originator (aka From:) then the envelope originator was simply discarded. CR: JAGab34151 SR: 1653305979 If the SR_RESOLVE_MASK general.cfg option is being used then any redirection that occurs in order to send Outlook calendar meeting requestes to delegates will fail to be delivered to teh delegate. A Non-delivery notification gets generated instead and returned to the original meeting request sender. CR: JAGab34126 SR: 1653302042 Receipt acks going back to Exchange via X.400 have the ORN part of the message id stripped. This causes the ack to be not matched when received by the Exchange system. See the submitter text for more details. CR: JAGab36217 SR: D500427898 Certain messages from the Openmail Notes Gateway that contain 8-bit characters cause the X400 Gateway to fail to process the message. CR: JAGab34781 SR: 5003463190 Items in a folder or bulletin board which have been placed there using the Outlook client's "post" functionality cannot be read using cc:Mail CR: JAGab34121 SR: 1653301507 After the B.05.10 October 1998 periodic patch has been installed, a a designate with appropriate capabilities can no longer delete items from a bulletin board. CR: JAGab34021 SR: 1653287946 Bulletin board synchronisation messages arriving out of order can cause synchronisation failures. Example : Message 1 for : 'Add Item A'. Message 2 for : 'Delete Item A'. If 'Message 2' arrives before 'Message 1', Item A will be added and will never be deleted. Previously, the problem text of this SR documented another scenario which could result in synchronisation problems. This has been entered as a new SR - see D500 427351. CR: JAGab34111 SR: 1653300392 If a network problem occurs while some big file is being attached to a message in a Web Client 5.10 session, the user is not able to access his mailbox until the processes on the server are killed by the administrator. CR: JAGab35943 SR: D500415729 For the OpenMail Web Client (B.05.00), the size is not displayed on sending when a file has been attached to the message. CR: JAGab34128 SR: 1653302414 mt_transfer failure error when Single Asn encoded bodyparts found in the message CR: JAGab32579 SR: D500425553 When ITO uses omacmd to call omopcsm or omadmr, there is often a SEGVIOLATION. CR: JAGab34178 SR: 1653308759 MSMail messages to Internet recipients non-delivered by Internet gateway PHSS_18282: CR: JAGab35997 SR: D500418079 If some permissions are set (using Outlook) on a private folder these permissions are lost if the folder is moved (but retained if the folder is copied). CR: JAGab36190 SR: D500426809 If local.delivery is not retaining the message to delivery it into the InTray then only the first AA_REDIRECT record gets processed. CR: JAGab32581 SR: D500426841 There are circumstances where the Container flag BB_HAS_ACL gets unset when it shouldn't. The effect of this is that if some explicit permissions are assigned to a folder these permissions will be ignored when calculating the access caps. of that folder (eg. for delegate access). CR: JAGab34022 SR: 1653287953 If an item is added to a bulletin board and almost immediately deleted. 2 synchronisation messages are created. If these arrive out of order, the item may be added and NOT deleted, because the first message attempts to delete an item which does not exist. This SR asks for a higher level of warning to be associated with the failed deletion so that this situation can be detected. omshowlog -l 7 should show a message similar to : [OM 23989] Bulletin Board Synchronisation has attempted to DELETE an item that doesn't exist yet on this system. See related SR 1653287946. CR: JAGab34089 SR: 1653297937 A bulletin board changelog entry is not written when a basic item is dragged from a container OUTSIDE the bulletin board into the bulletin board. CR: JAGab36171 SR: D500426189 Segmentation violation by ual.remote causes socket disconnection failure reported at Outlook user interface. The trace shows that a large number of notifications (relating to BBs and BB items) are being generated in a short space of time. This high frequency of notifications is causing a segmentation violation in the code that registers that notifications are waiting for the client. CR: JAGab36168 SR: D500426130 A user performing what is essentially a read-only operation can cause notifications to be raised on BBs abd BB items. These unnecessary notifications can have an impact on performance on systems where a large number of Outlook (and/or IMAP) users are accessing the Public folders (BBs in OpenMail terms). CR: JAGab36200 SR: D500427070 When base exists and filter does not the return code should be 0 with no entries returned, but the return code is 32. 32 should only be returned if the base entry does not exist. CR: JAGab32582 SR: D500426965 The remote Outlook delegate capabilities check protocol supported by advmail.sckd does not work properly on the AIX and Solaris platforms: AIX - Segmentation violation --- Solaris - returns incorrect 'send-on-behalf-of' setting for user. ------- CR: JAGab34091 SR: 1653297986 Forwarded messages whose internal message comprises of a distribution list only (no first text part or other attachments) will cause the Internet gateway unix.out program to abort on Solaris machines if UUENCODE routes are used. On HP-UX, a mal-formed message is generated teminating with the line : Encoding: CR: JAGab36170 SR: D500426163 Default BB ACL/permissions don't allow new items to be added by an Outlook client. The default permissions for an Outlook client should be: visible,read,create,sub-folder but instead they are: visible,read,sub-folder Other clients (eg. OMGUI, cc:Mail) are not affected. CR: JAGab34099 SR: 1653299024 X400 inmappper does not strip external attributes of FROM addresses. CR: JAGab33809 SR: 1653256966 Under certain conditions, the Openmail Lotus Notes Gateway can truncate long domain names for Notes users. CR: JAGab34746 SR: 5003450593 The problem is that when the -g option is set the -I option fails to work correctly. The problem can be shown by first setting up an dirsync agreement with the -I option set but not -g :- 1) omaddds -e -l DIRA -x DIRB -m "+DIRSYNC/hppwdj95" 2) omaddds -i -l DIRA -x DIRB -m "+DIRSYNC/hppwdj95" -t "990101 00:00" -P 1 -I 3) omaddent -d DIRB -e "S=Tester/G=A/OU1=Pinewood/OU2=hppwdj95/PHONE-1= 333" * Restart Dirsync * ~ Entry appears in DIRA with 'PROPAGATED-BY=209' ~ 4) ommodent -d DIRA -e "S=Tester" -n "PROPAGATED-BY=400" 5) ommodent -d DIRB -e "S=Tester" -n "PHONE-1=666" * Wait for sync to take place * ~ Entry in DIRA is modified to PHONE-1=666 (Correct) ~ Now if you modify the agreement to also use the -g option :- 1) ommodds -i 1 -g "S/G/OU1" * Restart dirsync * 2) ommodent -d DIRB -e "S=Tester" -n "PHONE-1=888" * Wait for sync to take place" ~ Entry fails to be propagated ~ The error message sent to the ENU states that :- Entry not in the Directory or Propagated By Identifier differs. If the PROPAGATED-BY attribute is set back to its original value for the entry in DIRA then changes are made to the entry in DIRB then these changes are propagated correctly. CR: JAGab34083 SR: 1653297242 MIME filenames derived from T.61 subjects are truncated at the first space, however, MIME filenames derived from either the original filename or the Subject of an item can contain a space. This is inconsistent. CR: JAGab33573 SR: 1653231563 Acknowledgements are sent marked "urgent" by OpenMail. A way of configuring this so that they are either sent with the same priority as the original message or sent with a specific acknowldegement level would be desirable. For instance, a general.cfg option like : AK_ACK_MSG_PRI=0 could be used to force all acknowledgements to be sent with normal priority. (valid values : 0, 1 (non-urgent) and 2 (urgent)) In addition, the following configuration option could be used to tie the priority of the acknowledgement message to be the same as the that for the message being acknowledged : AK_ACK_SAME_PRI=TRUE AK_ACK_SAME_PRI takes precedence over AK_ACK_MSG_PRI, although under some circumstances, the priority of the message isn't known at the time an acknowledgement is being generated and the AK_ACK_MSG_PRI setting is used. CR: JAGab35777 SR: D500401539 FREE/BUSY detail information is not available when referring to a schedule of users who have multi-byte names. CR: JAGab32360 SR: 1653229252 Miscellaneous enhancements to the OpenMail Web Client : 1. at 'New Message' window, the nuance of the Japanese label "ma-ji" (merge) does not seem to portray the nuance of the action. It is better if the label is changed to "atesaki" (destination), to show the user he can select a destination when he clicks this icon. 2. at 'Merge Distribution List from Distribution List Folder' window, again the nuance of the label "ma-ji" is not appropriate. It could be better as "atesaki torikomi" than "ma-ji jikkou" 3. at 'Attach Local File' window, the icon label "tenpu" (attach) is already used in 'New Message' window. We recommend that this be changed to "tenpu jikkou". 4. at 'New Message' window, icon label "sakujo" (delete) is what the program does to the message. For the user, it is better to be "kyanseru" (cancel) in Katakana, for a better feel that the user is in fact cancelling the message he is creating. CR: JAGab32523 SR: D500337337 When IBM extended characters in SJIS portion (0xfa40-0xfefe) entering OpenMail (UNIXJIS -> OMJIS), some of them are illegally entering OpenMail, so the specification need to be cleared and the code need to be fixed - either to accept IBM extended chars or not. CR: JAGab36169 SR: D500426155 unix.in creates an orphan for each TNEF-encoded nested message it processes. CR: JAGab36162 SR: D500425934 The tidy-up routines called at the end of a UAL session can cause a segmentation error. CR: JAGab34730 SR: 5003446914 The OpenMail command ommoddir can be used to set the Directory Change Log Life, and so can the Directory Synchronisation commands 'omaddds -n' and 'ommodds -n'. Internally, these 2 log life values are held in different places. The man pages for omaddds and ommodds do not explain the interaction between these 2 log life settings, or how to reduce the log life. Further the 'omaddds -n' command cannot be used to set the log life to less than the default value of 7. This is not explained. CR: JAGab36133 SR: D500424820 Missing FROM line in MDN/DSN messages CR: JAGab34757 SR: 5003453712 Ux gateway closes down when it gets a 571 return from SM. It should just give a fail responce and carry on. CR: JAGab35992 SR: D500417568 If a message with an incorrect addressee is sent into Openmail via any 'incoming connection' protocol, e.g. SMS2000I, no NDN is returned. CR: JAGab35778 SR: D500401547 Distorted preview of message is shown in Intray if body text of the message starts with English and then Japanese characters follow. CR: JAGab35772 SR: D500399246 Internet gateway can produce incorrect sender addresses CR: JAGab34545 SR: 5003406132 It is possible to build omscan with the '-N' linker option. This will allow omscan to have access to the 'text' internal memory segment, as well as the 'data' internal memory segment. This means that the should have access to more memory during run-time, and so maxdsize can be bigger. CR: JAGab34737 SR: 5003448654 If a message is sent to an address of the format: //ex/us/mci/scjmail/rfc-822/root@beast.mayfield.hp.com ie. No name and no OU's but just CAPO attributes and DDA fields the Service Router will attempt to resolve the name even though there is a valid route for the mailnode //ex/us/mci/scjmail. In certain circumstances this can cause huge delays in the processing of the message. This problem applies to any routable ORN that does not contain a Surname field. CR: JAGab32580 SR: D500426676 Server general.cfg: UXI_TREAT_AS_MIME_SUBJECT=T UXI_UNIX_MAIL_CHARSET=UNIXJIS UXO_MIME_OMIT_DEF_CTENC_HDR=T UXO_MIME_SUBJECT_ENCODING=B UXO_MIME_SUBJECT_BENC_NONASCII=T UXO_MIME_SUBJECT_FOLDING=T UXO_MIME_TEXTFILE_ENCODING=N Clients: Outlook Express J, Outlook 98 Internet mode J, Pocket Outlook Express These clients generate ISO-2022-JP + B-encoding filename and name fields. OpenMail can accept those filenames well, but the outgoing Internet G/W lower cases the B-encoding filename, so as a result, the filename will be garbage. For some clients, it is not possible to download the file, probably because of the filename corruption. CR: JAGab34109 SR: 1653299974 A certain kind of Lotus CD document makes cd.browse loop. CR: JAGab36221 SR: D500428029 Paper clip marks appear in Inbox when messages are sent as Plain Text and contain multi-byte characters in the body part, despite no attached files exist in the messages. This happens with Japanese Outlook98, MAPI-SP5.30(beta) and Windows 95 and NT4.0. CR: JAGab36194 SR: D500426882 If a non-openmail file is found when scanning the sub domain in omscan and it happens to be the first file in the directory the an attempt to record the item is made with no item information available. CR: JAGab36236 SR: D500428953 The details listed for a newly attached message generated as a result of a notification do not have the 'unread' flag set. This causes the client (Outlook) to display the message as already being read. CR: JAGab36234 SR: D500428821 Netscape creates the mime message with no trailing blank lines, which can be seen in the mime blob in the message store. The Item browser then ADDS a blank line at the end of the text message! Netscape then correctly says that the message is altered. CR: JAGab34968 SR: D500293266 omdirex import filters ending in a ")" character make omdirex fail. For instance, (OU1=pine)&(OU1=wood) A UAL error (4500,3,16030) is reported. The 16030 means mismatched parenthesis. CR: JAGab32583 SR: D500427344 This problem asks for a more comprehensive fix to the problem addressed in SR 1653287953. If an item is added to a bulletin board and almost immediately deleted. 2 synchronisation messages are created. If these arrive out of order, the item may be added and NOT deleted, because the first message attempts to delete an item which does not exist. omshowlog -l 7 should show a message similar to : [OM 23989] Bulletin Board Synchronisation has attempted to DELETE an item that doesn't exist yet on this system. BUT, additional information should be supplied which will allow the administrator to determine which Bulletin board the item could not be deleted from and the message-id of the item. See related SR 1653287946. CR: JAGab36055 SR: D500421016 omscan's orphan processing phase can now be frozen in memory to avoid impacting other processes, and re-started at a later time. To freeze omscan : kill -s SIGUSR2 ##### where ##### is the parent omscan process (there are 2 processes) To unfreeze omscan : kill -s SIGUSR2 ##### CR: JAGab36239 SR: D500429050 The LDAP minidit example shuts down and restarts the slapd server, as it changes the configuration. In some case, the script could think that slapd had shutdown before it actually had, causing the subsequent startup to fail. The main affect of this is when the minidit is run repeatedly, as in the autotests. CR: JAGab34717 SR: 5003444901 omscan is terminating early with an 'ILLEGAL INSTRUCTION'. The last thing that was logged was : SERIOUS ERROR Administration(omscan ) 12.18.98 03:45:21 [OM 10250] Process about to terminate due to error. Signal (Illegal Instruction) trapped by process 288914; code = 0. Procedure trace follows: <- scn_RecordItem -> im_FName2ItemRef -> GetFNameElements <- GetFNameElements -> GetElementIndices <- GetElementIndices -> os_str2ul <- os_str2ul -> os_str2ul <- os_str2ul -> im_FormFullItemRef <- im_FormFullItemRef <- im_FName2ItemRef -> scn_GetRecordedItem <- scn_GetRecordedItem -> scn_RecordItem CR: JAGab36230 SR: D500428318 VirtualVault - If an alias is specified for the DEFAULT-OMSERVER or OMSERVER field in the change root environment, Web Client 6.0 returns an error [SYS 1]Not owner. Currently only IP addresses are accepted. CR: JAGab36231 SR: D500428326 VirtualVault - The ownerships of the files in the change root environment should be changed to bin:hpoffice, wherever possible. CR: JAGab34719 SR: 5003445072 After mulitple replies to a message from ccMail through the Openmail Notes Gateway to Notes, the text becomes double-line spaced. CR: JAGab34136 SR: 1653303784 In patches to OpenMail B.05.10 after PP4 (B.05.10.D0) the following problem occurs. Create a new message Attach a local file to this message. In the web page that is then displayed, there is a table with attachment information. The field for the size of the new attachment contains just the letter K. It should contain the size of the attachment in kilobytes. In more general terms, the %%KSIZE%% token used to return the size of the attachment is blank. CR: JAGab36242 SR: D500429183 notif.mon tries to allocate space for a huge number of file descriptors because AIX says it can have that many. CR: JAGab36241 SR: D500429175 On AIX version 4.3, the ldap tools, ldapadd, ldapsearch,..., fail to connect to the host. This message is produced: ldap_bind: Can't contact LDAP server To date, this problem has only shown up on AIX 4.3 plus Y2K patches. However, the OpenMail defect could in principle have caused a similar problem on 4.3 without patches. Defect Description: PHSS_29063: CR: JAGae59759 SR: 8606296148 A coding defect in the brw component ignores Asian Interchange CharSets and limits itself to Latin ones only. A design defect in the tfl component allows it be called recursively when parsing the ORN of an NDN in an Asian user's mailbox, thus overwriting and corrupting its state memory. CR: JAGae62810 SR: 8606299316 The checkinstall patch script was not checking for HP-UX 11.11 or later. In this case, a status of EXCLUDE should be returned if OpenMail is not present. CR: JAGae69195 SR: 8606306147 A coding error in the sfl component calls a function with a structure as a parameter when the function itself is expecting a POINTER to the structure. This is a typical and simple programming error, which was discovered and corrected in GR7 when C function prototypes were introduced but it was not rolled back to GR6. CR: JAGae70969 SR: 8606307934 If a message contained the line "Content-Type: text/html; charset=", and then an attempt was made to construct the imapBodyStrc field, the processing of the NULL charset value caused a corruption and the item browser failed to return then requested data for that item. CR: JAGae70977 SR: 8606307942 When attempting to construct the imapBodyStrc record, a corrupt container can cause an error while attempting to create the Distribution List. This can happen if there is no distribution list. Rather than returning the header information of an item without the distribution list, an attempt is made to create it, and when the item browser cannot find the distribution list in the container, it fails and no header information is returned. CR: JAGae70980 SR: 8606307945 If an item contains a folder, then folder's data is stored in a different container to rest of the data for that message. When attempting to construct the imapBodyStrc record, the subject of the folder needs to be read in. When doing this, the block was read in from the parent container instead of the folder's container. The block being read either contained either contained a value for the subject, which meant that a corrupt subject was read in, or the block contained no such value and the item brwoser failed to return the message content. CR: JAGae70984 SR: 8606307949 The IMAP daemon is looping when trying to process the corrupt header of a message. CR: JAGae70985 SR: 8606307950 The problem was caused by the UAL returning either no Absolute reference value for the Delivery Acks, or a value of 0. The IMAP fetch command does not display items with such a UID. The existence of such messages also means that UID values were missing and Netscape 4.7 became confused. PHSS_28589: 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: JAGae49796 SR: 8606285855 In the RedHat version, the name of a shell variable was changed in the the March 2002 Periodic Patch. The patch install scripts PLSS_xxxxx.postinst and PLSS_xxxxx.preinst were named incorrectly and did not run. This has now been corrected. 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_28154: 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. CR: JAGae48115 SR: 8606284168 When a local user has a very long name/address (exceeding 200 bytes) the name/address gets truncated as the user signs on. This truncated version of the name/address is used in any messages sent by the user, and these messages cannot be successfully replied to as the originator name/address contained within them is incomplete (truncated). PHSS_27677: 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: "OMDATADIR/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: JAGae24726 SR: 8606260403 There have been some minor layout changes in sendmail.cf. omsendin has been updated accordingly. 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: 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. PHSS_27059: 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: 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: JAGae15283 SR: 8606248886 The causes of the problems are 1) The flag which determines whether read acknowledgements should be automatically generated is not being passed to the UAL when preparing to read an item. 2) The SMTP message is not being correctly parsed by unix.in so that Message Disposition Notifications are not always recognised and converted into OpenMail acknowledgements. 3) The 'message has been read' flag is not set by the UAL prepare read command if a message requires an acknowledgement and general.cfg option IMAP_AUTOMATIC_MDN=FALSE is set. 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: 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. PHSS_26275: 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 (see JAGac39658). 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: 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: 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_25645: 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: 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: 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: 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: 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_24873: 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: 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: 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: JAGad71090 SR: 8606201916 Hidden items within the message store were included within the item count when listing the tray or folder areas. CR: JAGad73144 SR: 8606203966 The failure occurs after the license server sends the request to the other license server, or when receiving the reply. When scanning the shadow file, and a decaying license is found in the shadow file before an active license, the license server treats all following entries as decaying, and eventually aborts. 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: 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. PHSS_24094: 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: 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: JAGad45881 SR: 8606176644 The attempted deletion of an attachment in a user's intray, using a pointer to a null container entry, resulted in a segmentation violation and the subsequent premature abort of omcontain. 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: JAGad47890 SR: 8606178664 Incorrectly configured vir*s scanning library was causing messages containing vir*s to not be scanned and potentially cleaned. CR: JAGad48440 SR: 8606179216 A coding defect in the brw component assumes that text messages without a specifed CharSet are 7-bit text. 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: JAGad53837 SR: 8606184631 A coding defect in the ct component causes an inconsistancy, in respect of MIME boundary markers, in a message when it is copied from one folder to another. However only Netscape on displaying larger messages is affected by this discrepancy. It is lead to believe that the copied message's boundary markers are those of the message from which it was copied. This causes it to miss finding the attachments and so not display them. 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: JAGad57988 SR: 8606188772 A coding defect in the brw component results in message headers, containing 8-bit chars, being counted twice in computing the total SIZE of message. This incorrect SIZE causes the Netscape IMAP client to become confused and to give up displaying as a message and revert to just displaying the MIME Source. 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. PHSS_23342: CR: JAGab33574 SR: 1653231704 A recipient-processing library call, was trying to perform a copy of a NULL ORN string. 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: JAGad24268 SR: 8606154951 A coding error in the item structure server was causing it to sometimes corrupt the item references it was reporting. 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: JAGad41463 SR: 8606172203 The omshowapp script was not being run appropriatly as it needs to be run under ksh on solaris. CR: JAGad41471 SR: 8606172211 A segmentation fault occures when parsing a blank line at the top of the mnMapFile which is located in the varOMBINDIR/sys directory. CR: JAGad41637 SR: 8606172377 The delegates unix id and unix username were used when signing on but the openmail id was not. This meant that when the change went in to use user.cfg files by openmail id and not unix id that the wrong file was checked. CR: JAGad42631 SR: 8606173373 If an orphan message is deleted during the omscan process, an attempt to open the orphan message causes the error message OM [1209]. CR: JAGad43052 SR: 8606173797 The IMAP daemon was not converting MIME subject before copying an item into the OpenMail message store. CR: JAGad43053 SR: 8606173798 This problem is caused by the IMAP server daemon failing to convert content the character set from MIME to OpenMail when appending a file to the OpenMail message store. CR: JAGad44810 SR: 8606175570 Certain characters ,=/ when placed within the FF field get escaped with the backslash character When a backslash character is present with the address field (ORN field) and the user validates the name and tries to send a message to that adddress then the error "name is not routable is displayed". 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: 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: 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: JAGad49581 SR: 8606180360 Files i4target_ux10 and i4target_ux11 were missing from CR JAGac29290. PHSS_23081: CR: JAGad41842 SR: 8606172582 The UAL_GETSYNC routine does not extract T.61 content correctly and the resulting content file does not undergo any character set conversion so the data remains as T.61. CR: JAGad42033 SR: 8606172773 Move from Inbox is really a copy and delete and the generation of the DirectRef for the moved item must be delayed until after the move in order to get the correct value. CR: JAGad42115 SR: 8606172855 Update of Local FreeBusy information is caused by the removal of the Local FreeBusy property for the user and the generation of a notification that the Local FreeBusy message has been modified. This causes the Local FreeBusy information to be regenerated and rewritten by the Outlook client. There are some circumstances when there is no FreeBusy information present and this fact meant that the Local FreeBusy message was not modified and therefore no notification was generated and the FB info was not regenerated. CR: JAGad42645 SR: 8606173387 For a synchronisation the calculation of where the first newly attached sync. message at the end of a large folder can be incorrect if items near the end of the folder have been deleted. CR: JAGad42878 SR: 8606173621 Modified offline item generates and explicit GET_ITEM command with the sync. actions. If this item does not exist on the server a spurious error is generated in the UAL_GETSYNC action file. CR: JAGad44420 SR: 8606175176 If OFS has been enabled by an Outlook user then there are occasions when the OFS change log will contain information about items that are no longer present in the message store. Handling such change log entries is causing the WARNINGs to be generated even though no error has occurred. These WARNINGs should be downgraded to minor events. This behaviour is especially likely to occur when a message is being constructed by Outlook and the message gets automatically saved to the Drafts folder (by default after 3 minutes) before the message is mailed. PHSS_22929: CR: JAGad38822 SR: 8606169547 A coding problem in ual.remote causes the Content Disposition and Content ID fields of a mesage to become corrupt when forwarding/replying to email using Ccmail 6.* clients. PHSS_22995: CR: JAGad29260 SR: 8606159934 A coding error in the notes.out part of the Notes Gateway resulted in blank From:, To:, Cc: or Bcc: entries being dropped without adjusting the accompanying counts of said entries. PHSS_22990: 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. PHSS_22699: CR: JAGad21983 SR: 8606152653 UXO_CHECK_TYPES_OF_DDA synonyms for DDT1 setting are not treated in exactly the same way as RFC-822. CR: JAGad25146 SR: 8606155833 The file of new users previously contained only usernames; ie. nowhere for aliases to be specified. The format of this file has been extended to allow specification of aliases. The file format is described in the new man page for omaddu, which is part of this fix. Note that it is not possible to specify aliases when using the '-u' option with '-bulk'. Aliases can only be specified in an input file to omaddu -bulk. CR: JAGad25316 SR: 8606156005 When handling the SIGCLD or SIGCHLD signals on an Ensim Linux machine, the SIG_IGN fails causing zombie () processes to be created. These processes remain on system exhausting process ids. These zombie processes are only removed when the parent process is closed down. The zombie () processes can also cause the parent process to hang using large amounts of CPU. CR: JAGad26547 SR: 8606157213 omlimit functionality was altered in a way which required new messages, however, these messages were not localised. CR: JAGad27572 SR: 8606158242 When Eudora sends an "application/mac-binhex40" file to a Unix internet account, the attachment has the following MIME information with it : Content-Type: application/mac-binhex40; name="Birkenstock.doc" Content-Disposition: attachment; filename="Birkenstock.doc" and the file is not encoded. A message sent to an OpenMail user in the same way has the following MIME information when the message is browsed by an IMAP or POP3 client : Content-Disposition: attachment; filename="Birkenstock.doc" Content-Type: application/mac-binhex40; name="Birkenstock.doc" Content-Transfer-Encoding: base64 and the file IS encoded. Clients like Eudora ignore the encoding and assume the file has not been encoded. For instance, when opening a Word document, Eudora 5 and earlier will open the file before removing the encoding. CR: JAGad28647 SR: 8606159318 A coding defect, introduced when Vir*s Rule Sets were introduced, in the Rules Sets component of the Service Router was causing this process to unnecessarily expand its memory with increasing number of requests, when the Default Vir*s file was activated. CR: JAGad28840 SR: 8606159513 Various inconsistencies identified in the code within function definitions or calls. CR: JAGad29235 SR: 8606159909 The UAL is caching the item information and returning the old item count. CR: JAGad29644 SR: 8606160320 When trying to ascertain the type of a file, no checking was being done to see if an attempt was being made to read past the end of the file. CR: JAGad29892 SR: 8606160571 Support for MAPI Offline Folder Synchronization will be provided by this enhancement. See OpenMail/MAPI B.06.00 relase notes for details. CR: JAGad31458 SR: 8606162142 When the omgui starts up, it reads information from the omgui.dsc file. If this file is not in the correct format, then the omgui fails to start. For the German language, the diratt.loc file on the server does not contain a description for the fields - 99.827, 99.830, 99.822, 99.826, 99.824 and 99.826. If the omgui.dsc file is missing, it is copied from the diratt.loc file on the server and is in the incorrect format for German, causing the omgui session to fail. CR: JAGad31479 SR: 8606162163 A coding problem in the IMAP server causes connections from IMAP to the UAL to be lost. The problem occurs randomly and the IMAP server returns the following error message and then drops the UAL connection: sock3/BYE: r {OpenMail IMAP Server not available} CR: JAGad32112 SR: 8606162796 The OpenMail imap server displayed strings with backslash characters in them, as Quoted strings. Although other IMAP clients could cope with this, Netscape Messenger sometimes could not. CR: JAGad33512 SR: 8606164212 The item size is cached by the UAL and doesn't get updated. CR: JAGad33773 SR: 8606164474 Both the Internet gateway and the Item Browser, were not correctly terminating the message processing, if they could not find the expected boundary marker within a multipart/signed message. CR: JAGad34214 SR: 8606164917 The IMAP server process on the HP-UX machine aborts, causing the IMAP connection to die. The following omshowlog trace is given : SERIOUS ERROR IMAP Server Da(IMAP Server Pr) 10.19.00 17:12:46 [OM 10250] Process about to terminate due to error. Signal (Segmentation Violation) trapped by process 9774; code = 0. Procedure trace follows: <- imapual_getObjectFile <- imapual_mapObjectFile -> imapparse_structure -> parseEnvelopeStructure <- parseEnvelopeStructure -> parseBodyStructure <- parseBodyStructure <- imapparse_structure <- getStructure <- getMessageInfo -> sendMessageInfo -> appendHeaderLines <- appendHeaderLines -> appendEnvelope -> appendImapAddressList -> imapparse_address CR: JAGad34502 SR: 8606165208 Omlimit checking of the Bulletin Board Area before the BBA has been opened causes this problem. CR: JAGad34729 SR: 8606165435 The default shell (#!/bin/sh) invoked at the top of the omdelapp.gen and omaddapp.gen related scripts does not exist on solaris. This was causing the "function not found" errors to arise when omdelapp and omaddapp commands were executed. CR: JAGad37344 SR: 8606168062 The hash values created for existing and new usernames were calculated on the name as retrieved from the directory, or as entered. So two names that differ only in case produced different hash values, and were not therefore noticed as clashing. CR: JAGad37410 SR: 8606168129 The Licence Monitor, when updating the licence shadow cache, creates and opens a tempory file. This file is never closed or deleted and therefore ties up open file descriptors. This problem only occurs when the modification time on the nodelock file has been updated or when virtual licensing is used. CR: JAGad37711 SR: 8606168431 notif.mon did not contain procedure entry/exit trace messages. PHSS_22457: CR: JAGad30987 SR: 8606161671 Extensions to the UAL protocol required to support MAPI Offline Folder Sync. EEP. PHSS_22361: CR: JAGab84570 SR: 8606112256 It is not the ACLs for a BB that are getting lost but it is the ACL flag (ContentFlags/CtCFlags2)for that BB getting reset, this is because while Modifying the BB on the Importer, the original contentFlag info are not saved. CR: JAGad05041 SR: 8606135910 When listing the intray, the ual library was not checking and handling the UAL_MSTORE_SIZE_LIMIT and UAL_SIZE_MSG_TO_ENU options in the user specific configuration files (i.e. the configuration files under ~openmail/sys/user.cfg). So these options were not working. CR: JAGad05207 SR: 8606136077 While generating the "nearing size" Warning message in UAL, the message subject and text are obtained in the same charset encoding, OMJIS,T. Whereas,the subject should be obtained in OMJIS,O & Msg text in OMJIS,T CR: JAGad11128 SR: 8606141768 MAPI and IMAP object files used to be in the parent container record but now are associated with the child container record and the code change to handle this did not function correctly. There were also a number of uninitialised variables and a couple of problems freeing memory incorrectly, causing a change in behaviour. CR: JAGad13619 SR: 8606144279 The corrupt CONTENT DISPOSITION field in the CONTENT_FILE record of the message transaction file is too long and causes a buffer over-run. CR: JAGad14574 SR: 8606145237 If items in a user's message store have been accessed using an IMAP client, then they are assigned with a sequence number. omcpinu recognises that this is the case, but then starts at 1, when assigning sequence numbers to items which it is copying in. This means that some items have the same sequence number, this may confuse an IMAP client. CR: JAGad15232 SR: 8606145896 The changes introduced to the UAL in B.06, to support unicode, caused a change to the usage of an environment variable used by the Item browser to determine the User Display Character set. The logic in the Item Browser code that checks the environment variable, needed to be changed accordingly. CR: JAGad15339 SR: 8606146003 The formatting of initials was incorrect when the i-tx field is used. CR: JAGad21220 SR: 8606151881 The problem lies in the fact that OpenMail records the process ids of OpenMail processes in files. Following a Service Guard failover, the files from the OpenMail on the broken machine are re-read by a new invocation of OpenMail on the new machine. If there are processes on the new machine which happen to have the same ID's as the OpenMail processes from the broken machine, then OpenMail could now think the stored OpenMail processes are still running. This in turn would cause omrc to exit because omrc thinks there is an OpenMail already running. CR: JAGad21785 SR: 8606152455 The format of sendmail.cf has changed for Sendmail 8.10. The smawk script (invoked from omsendin) now recognises the 8.10 format of sendmail.cf, as well as previous formats. CR: JAGad21810 SR: 8606152480 OpenMail gets compilation error when built on RedHat 6.3. This occurs because the C compiler on RedHat 6.3 is more strict. CR: JAGad23468 SR: 8606154150 OpenMail creates the first data instance automatically during installation. This is not removed automatically when "rpm -e" is run - to allow for upgrade situations. So the initial data instance should be made a manual configuration step. CR: JAGad23509 SR: 8606154191 The openmail installation scripts for Applink and CCmail mobile have been enhanced to declare their services to both xinetd and inetd if they are present on the system. CR: JAGad23675 SR: 8606154357 The bus error is caused when a strcpy is attempted to a null pointer. CR: JAGad23678 SR: 8606154360 The UAL INCLUDE_FILE command does not seem to recognise the MIME character set iso-8859-1 as being the same as the OpenMail character set ISO8859_1. CR: JAGad24043 SR: 8606154726 Currently whenever a message is sent from Openmail to Opendesk, the user message ID and the transport id are written into the ackdb (unless disabled) and a new Message ID is generated that satisfies Opendesk's limitation of 16 characters. This is being done for any message, whether the acknowledgement flag is set or not. Upon message return from Opendesk, we check the message type and if it is a delivery acknowledgement, then we restore the original transport ID to the ACK_ID. This was not being done for certain types of non-delivery report which OpenDesk generates. CR: JAGad25016 SR: 8606155703 Various problems found with the Openmail packaging for rpm CR: JAGad27743 SR: 8606158413 The MDC_DDS_DELETE_DATA functionality causes nulls to be written to a file when the last "unlink" from the file-system is made. It is still possible to access a file on a UNIX system if it is already open, even if there are no longer any references to it in the file system and the IMAP client deliberately makes use of this fact to guarantee that temporary files used to cache information are deleted when the IMAP process terminates. PHSS_21944: CR: JAGab33837 SR: 1653262501 There is no logic in place inside UAL_CHKLST to sort the alternate names with a different sort order. CR: JAGab63204 SR: 8606101643 In order for the attachment name to be displayed by many Windows based clients, two of the arguments to UAL_INCFIL need to have the file name as the value. Currently, only one argument contains this value. CR: JAGab72994 SR: 8606105114 A coding problem in the Unix Gateway meant that attachment names on messages with an attachment, and no body parts, were being lost. The Unix Gateway was not getting the attachment information, (eg filename) from the Content-Disposition line of the message and was then giving the attachment the subject of the message as the name. This caused problems when viewing the message using an IMAP client. CR: JAGac29290 SR: 8606114526 OpenMail can be used on HP-UX systems which do not have the LSSERV component installed. CR: JAGad00687 SR: 8606131537 The line breaks are getting removed from the auto-forward and auto- reply text because the newline character is not being escaped properly for IE. CR: JAGad01673 SR: 8606132524 A search on the contents of a note fails. There are 3 reasons for this failure 1) The background search process assumes that the first part of an item is the distribution list, and the second part is the contents. In the case of notes, this is not the case, as there is no ditribution list. The search ends up skipping the contents, and consequently has nothing to search through. 2) Notes are saved as RTF files. The search process incorrectly assumes that the note's content is part of a serialised file, and fails, when trying to extract it from the data file. 3) There is a MAPI problem, which means that the search specification is incorrect and doesn't work for notes. See JAGab35445. CR: JAGad01880 SR: 8606132732 The unix gateway fails to parse the MIME contents of the DSN reports accurately. CR: JAGad02855 SR: 8606133711 If a machine is running short on memory, then an ENOBUFS error may be generated. If an ENOBUFS error is detected by the mdc_accept call, the Desk Gateway socket handler terminates, even if the memory shortage was just temporary. CR: JAGad03000 SR: 8606133860 The type of the "name" part of the DESIGNATE transaction file record is incorrect. It should be treated as an "OpenMail Name/Address value" rather than as a "String value" CR: JAGad03146 SR: 8606134007 This is due to an error in the session handling. CR: JAGad03894 SR: 8606134759 local.delivery is supposed to allow delivery of system-generated messages, even if an omlimit has been exceeded. But it was testing for a message creator name of "MAIL-SYSTEM" in order to do determine that the message was generated by the system. Since this string is localised into different languages, the test was not valid when non-English clients were involved. CR: JAGad04005 SR: 8606134871 ccmtp.run caused changing T61 text to binary file type. CR: JAGad04018 SR: 8606134884 The "Return-Path:" address which is automatically generated for messages which don't already have a setting for it is not formatted in the same way as other addresses in the message. CR: JAGad05750 SR: 8606136626 The UTF-7 to UCS-2 character encoding conversion was sometimes incorrect. (UTF-7 is converted to UTF-8 via UCS-2.) CR: JAGad06793 SR: 8606137667 The OpenMail SMS2000 protocol handler, has a timeout for responses from the SMSC. When this timeout is exceeded, an NDN is generated and sent back to the originator. This timeout was hard-coded at 8 seconds, and appears to be too small in some cases. CR: JAGad07023 SR: 8606137874 If the desk.out gateway tries to map the Ack database into memory, while the desk.in process already has it mapped into its address space, there is a possibility that the desk.out gateway may fail to perform the mapping and then abort. This is due to a known limitation of the HPUX implementation of the mmap() system call. CR: JAGad07491 SR: 8606138290 The environment setup by the ual.remote process for the item.browse sub-process was not correct for browsing messages using a Japanese client. CR: JAGad08966 SR: 8606139655 The incoming Mime gateway scans for the first dot in a filename rather than the lost dot. CR: JAGad11000 SR: 8606141637 The changes made in the February 2000 PP's, meant that it was possible for the server UAL to read the start of the next data packet and assume it to be part of the previous packet. This seemed to only occur in certain slow network environments. CR: JAGad11143 SR: 8606141783 When the CONTENT_FILE record is trashed by the service router, the associated CONTENT_OBJECT_FILE and CONTENT_OBJECT_DATA records should be deleted also, but are not.When the message is delivered, the data in these records for the deleted attachment overwrite the data for the preceding CONTENT_FILE record. CR: JAGad12244 SR: 8606142895 Microsoft have recently released a version of Outlook that restricts what users can do with attachments. This enhancement allows an OpenMail administrator to configure the various attachment secur*ty settings on both a system and per-user basis. CR: JAGad12543 SR: 8606143206 Portal daemon does not disconnect from the UAL and reconnect when a request is received with a new character set. CR: JAGad12554 SR: 8606143218 The request server converts spaces in mailnodes to the _ character before checking the Access Control Lists. The _ character then fails to match on the space in the ACL, and so the request fails. CR: JAGad21211 SR: 8606151872 The patch de-installation script makes use of an openmail executable, omeval, which is part of the system being patched. This is unsafe, because during patch de-installation, there is a period of time in which the shared libraries that it depends-on, may be incompatible with omeval. PHSS_21439: CR: JAGab32379 SR: 1653240259 Multi-byte Characters present in DDV1 field. CR: JAGab32452 SR: 5003366708 The SMS server did attempt to log messages when an error condition was reached, but these messages were being discarded by the code which trapped them. CR: JAGab32488 SR: 5003454405 The enhancement stops the autoreply for those messages with precedence bulk, junk, or list, i.e. the sender won't receive any autoreply messages. CR: JAGab33999 SR: 1653285569 When local delivery is creating the delivery envelope and it comes across an object file or MAPI information a flag was set to not include these records in the delivery envelope. This is not being reset before looking at the next record. CR: JAGab34077 SR: 1653296350 The check on whether the route could be resolved was restricted just to messages - not acks. CR: JAGab34096 SR: 1653298653 A variable used to hold the LID information was being re-used when it should not have been. CR: JAGab34157 SR: 1653306589 When omscan is run in fix mode, it deletes all the entries in ~openmail/tmp & ~openmail/temp except entries starting with "." (i.e ".*") which are 7 (or more) days older. So, it also removes "lost+found" directory (if any) making it impossible for OpenMail to startup automatically after system crash. CR: JAGab34186 SR: 1653310714 OpenMail's Internet Gateway incorrectly assumes that there are no whitespaces sorrounding the "=" betweent token/value pairs in MIME encoded messages. CR: JAGab34785 SR: 5003465195 UAL_DELITM and MOVE_ITEM(for Outlook type clients) isn't aware of repeat reminder messages. It should remove the message from the deferred message queue as well as deleting the message from the pending tray. CR: JAGab34850 SR: D500253328 '_' values in general.cfg are converted to ' ' characters. CR: JAGab74208 SR: 8606105866 Incorrect ItemNumbers are given to the Object files that are added. omcpoutu/omcpinu does not pick up the object file properly. CR: JAGab74694 SR: 8606105948 While parsing the tag=value format of the ORN from the text input , values like "S=Merritt/" and "S=Merritt" are handled differently. CR: JAGab76033 SR: 8606106702 When a message with attachments is sent to a Local User, if any attachment (which you can view using omqdump) is deleted, then restarting Local Delivery checks for all the attachments.If one attachment doesn't exist then local delivery aborts while opening the file associated with the ItemRef which doesn't exist. CR: JAGab76643 SR: 8606107035 The advmail.sckd program makes attempts to connect to the socket. If it experienced 3 consecutive bad accepts, when attempting this, the program will terminate. Adding tweaks to allow the number of bad accept calls, and the delay between retries, to be configured - for more flexibility. CR: JAGab78064 SR: 8606107773 The code handling Content-Disposition lines in a message was unable to handle the (incorrect) situation where there was more than Content-Disposition for the same body part. CR: JAGab78752 SR: 8606108351 The code dealing with the autoreplies did not allow for multiple instances of Local Delivery. As a result of this, a file which is written-to by the autoreply function was never exclusively locked. This resulted in corrupt lines in the file when two or more Local Deliveries were accessing it simultaneously. These corrupt lines when read by the autoreply function caused a Bus Error. CR: JAGab82030 SR: 8606109330 This occurs if the configuration file on the host relevant to the particular user has the value of "ConvertToRTF" set to 0 (the default) rather than 1. Typically, the configuration file is ~openmail/nls/C/ccmtp.ini However, this can be over-ridden by a user specific file if the OpenMail configuration application - documented in the : "cc:Mail Mobile (OpenMail Edition) Technical Guide" is used. The cause of the problem was actually that any attachment that had an original filename was always being treated as a file attachment regardless of whether it is now text or not. CR: JAGab82546 SR: 8606109847 The problem is in the quoted-printable encoding routine. The '?' character is not being coded correctly in the encoded-text. The '?' is an illegal character in the encoded-text portion of the quoted-printable string according to rfc1522 as it is used as a special delimiter. CR: JAGab84515 SR: 8606112206 A coding problem in the UAL caused no character conversion to take place when attaching the message to a folder on the server using an IMAP client. CR: JAGab84577 SR: 8606112263 The SFL compaction code introduced at release 6.0 was creating temporary SFL items when copying out Blocked Items (e.g. containers). These were not being free'd after the compaction. CR: JAGac29346 SR: 8606114582 The problem in omcheck was due to a difference in the operation of lex (actually flex on Linux) - which operates on 8KB chunks of input data at a time on Linux as opposed to one character at a time on other Unix versions. CR: JAGac29459 SR: 8606114696 The unix gateway encodes a multipart alternative body part with Content-Disposition as inline for the text part and as attachment for the other alternative part. CR: JAGac39658 SR: 8606124275 An incoming MIME message containing a winmail.dat (TNEF) attachment but NO MIME Content-Transfer-Encoding line causes the unix gateway to crash. CR: JAGac40185 SR: 8606124793 The problem messages have items whose charsets are not known to OpenMail - for instance, "MIME-Windows-1" and these are not handled correctly. CR: JAGac40230 SR: 8606124838 The unix gateway sends out UUENCODED files, preserving long file names containing spaces. CR: JAGac42791 SR: 8606125848 This problem is due to the way the HPUX readdir system call is implemented. If one process is writing to a directory entry while another process is using readdir to read from the same directory, there is a small window in which the readdir call could fail with an EINVAL error. omdbmon uses this readdir system call when clearing log files from the ~openmail/dblogs/local directory. CR: JAGac78718 SR: 8606127917 Clients such as Outlook ignore the background colour specified by RTF files. CR: JAGac79005 SR: 8606128205 The problem was caused because an explicit check was made in the code to make sure that the message being non-delivered is on the local.delivery queue. CR: JAGac86611 SR: 8606129065 An attachment filename is in Japanese multibyte character encoding which includes a non-escaped quote. CR: JAGac86632 SR: 8606129086 The causes of the problem were an uninitialized memory read and a free memory read. CR: JAGac86756 SR: 8606129210 The segmentation violation in omaddu was due to incorrect handling of a NULL pointer. Also, when "-bulk" option was added to omaddu, the usage string was not correctly updated. CR: JAGac86786 SR: 8606129240 The cause of the Segmentation Violation is the non initialization of a variable. CR: JAGac86878 SR: 8606129332 Directory access problems are caused by dirsync gaining a directory lock for a batch of updates immediately on relinquishing the lock for the previous batch of updates thus excluding other processes from gaining a lock. CR: JAGac87789 SR: 8606129454 When a directory synchronisation is triggered by the omresyncds command, the routine that modifes the directory entry does not remove deleted attributes. CR: JAGac87845 SR: 8606129510 A new profile required that uses WML (undestood by mobile devices) instead of HTML and not using Frames and Javascript is required. CR: JAGac87847 SR: 8606129512 The permissions of directories /etc, /etc/mail, /var and /var/spool are sometimes incorrect. This causes problems with version 8.9 of Sendmail. In some cases, the permissions may have been changed during the installation of OpenMail or its patches; in other cases, they were always wrong. omrc has been changed to issue warnings if these permissions are wrong and Sendmail 8.9 is in use. CR: JAGac87851 SR: 8606129516 The CGI shell script webselect.cgi uses the environment variable SERVER_PROTOCOL to obtain the protocol. However, the web server sets this variable to HTTP/1.1 even if the protocol is https. This is true because the traffic from the browser to the web server is under SSL and beyond that it is ordinary HTTP. Hence the URL called from the profile selection screen contains "http" and the browser will not be able to locate the server. CR: JAGac88829 SR: 8606129914 The default value of UXO_ITEMSUB_IS_FNAME is FALSE for B.06.00 systems. Note that the default value on B.05.00 systems with patches after the November 1999 patch is TRUE CR: JAGac95131 SR: 8606130260 When a message enters OpenMail through the internet gateway, the comments that are on an smtp address are lost. And consequently, they cannot be displayed when the message is read. For example, the sender: "John A. Smith" <103343.1432@compuserve.com> is saved as <103343.1432@compuserve.com> CR: JAGac95600 SR: 8606130710 The IMAP server does not handle the transient error ENOBUFS when accepting client connections. CR: JAGad00184 SR: 8606131026 The shared library libcurses.1 has not been copied to the chroot directory by the installation script. CR: JAGad00185 SR: 8606131027 Though a tweak PORTAL-LIMIT-MATCH has been provided for this purpose, the default value should be increased to a very high value of 512 or 1024 so that the admin has less work to do. CR: JAGad00350 SR: 8606131199 The sms back-end server used a system call to read the directory entries in the ~openmail/sms/data directory. This call would fail if there are too many entries in the directory because the argument line length would be too long. CR: JAGad00539 SR: 8606131389 A number of error messages exist in the sms back-end server process, for situations which might cause an abort. However just before the process terminates, the error message is printed to standard output and then discarded. CR: JAGad00698 SR: 8606131548 The default value of 3000 seconds for the DRS connection timeout is causing the portal lookup feature to take too much time on certain mailnodes CR: JAGad01319 SR: 8606132170 Some later versions of sendmail.cf are not recognised by omsendin (particularly versions 8.8 or 8.9). The problem usually occurs when new versions of sendmail are installed as operating system patches. This can occur on HP-UX, AIX and Solaris. In other cases, sendmail.cf is updated, but the required equal sign is not added to the OperatorChar option (in sendmail.cf) the first time omsendin is run. CR: JAGad01353 SR: 8606132204 UAL folder lists were not being cancelled after a folder had been processed and eventually, the UAL process associated with omtidyu had too many lists active. CR: JAGad01557 SR: 8606132408 The notification server was aborting because it was trying to bind twice to the same IP address as each unused lan detected was given an IP address of 0. CR: JAGad01812 SR: 8606132664 Code fault; error in checking for NULL pointer. CR: JAGad01851 SR: 8606132703 Incorrect checking of the command line arguments for omaddred. CR: JAGad01856 SR: 8606132708 A change made to a read on the UAL input socket, while valid in the Linux environment, has caused all blocks read from the input socket to be read 8 bytes at a time, rather than reading a whole block at one go. CR: JAGad02689 SR: 8606133544 This problem is caused because something (maybe a message in the Inbox with appointment info in it) causes Outlook to access the LocalFreebusy message which is in the Calendar folder. It accesses this message via a DirectRef (stored at the UserFolder level). This DirectRef access causes the Filing Cabinet and Calendar to be listed as part of the resolution of the LocalFreebusy DirectRef. These lists are not full lists and do not contain AccessCaps for delegate usage (because the ACL file (if it exists) for the folder is not accessed. What is happening with this problem is that if the Calendar is subsequently explicitly accessed by the user the old (incomplete) UAL list for the Calendar is picked up and this shows AccessCaps=0. CR: JAGad03759 SR: 8606134624 A structure member was being assigned a value before the structure itself had been allocated in memory. CR: JAGad03776 SR: 8606134641 The postinst script was checking the wrong directory when configuring PAW. CR: JAGad04546 SR: 8606135412 The omunpatch script was failing to set an internal variable when processing files in the B.06.00.00/lib directory. CR: JAGad04673 SR: 8606135539 The Web Client binary converts any URL in the message content to a hyperlink, using HTML tags. Since the WAP client cannot understand HTML tags, the gateway reports a WML syntax error. PHSS_20776: CR: JAGab32483 SR: 5003444679 customer requires that users should not be allowed to send mail while they are exceeding there omlimits. CR: JAGab33916 SR: 1653272351 When the message is sent either using 'omsend' or UAL, the CAP[O] attributes are picked up from the directory and the ITEM_CREATOR in the Transaction File is marked as Mr Originator/local,node/GB/GOLD 400/HP/HP When Local Delivery is unable to find the user[ as it is being sent to a Non-Existant User], an NDN is generated and the Primary Recipient is marked as Mr Originator/local,node/GB/GOLD 400/HP/HP Looking at the attributes and since we have a route to X.400 for this Address, the message is being put in the X.400 queue. But X.400 aborts while constructing the message because the ACK_ID is a normal Openmail MsgID which doesn't have all those tranport IDs. If the message had reached openmail via X.400 the ACK_ID would have been in the required format. CR: JAGab34044 SR: 1653291617 The problem occure because the CGI program does not have access to the environment variable 'OMCURRENT', due to which some of the 'ext_' routines fail. This package name is required by the external routines to resolve the locations of 1. The user program to be invoked. 2. The names of the pipes uses to communicate between CGI and USER programs. 3. The profile/page/image file names. CR: JAGab65807 SR: 8606101854 The cause of the bus error was that a null pointer was not checked for if the Notification Server had run out of memory and couldn't allocate space for a new user. CR: JAGab69180 SR: 8606103019 local.delivery is only generating a single redirection for the situation described in the problem text. This results in only one set of Outlook delegate redirection information being created when the message is delivered. A separate message should be generated for each redirection recipient. CR: JAGab72452 SR: 8606104741 problem lies with the way the messages are handled when they are deferred. and particularly when messages arrive from remote systems due to be delivered to local mailnodes which have rulesets associated with them that would defer messages depending on their size. CR: JAGab72649 SR: 8606104884 Signon fails if the username and alias match, and are unique for that user. CR: JAGab72864 SR: 8606105045 Functionality is missing from the Internet gateway CR: JAGab75968 SR: 8606106664 Problem with OpenMail setuid programs CR: JAGab75998 SR: 8606106674 Difference in behaviour between Trend Micro viral scanning library and the self penned test scanning library. CR: JAGab76793 SR: 8606107113 Because the at-sign in GSM3.40 is a NULL character, this was causing the character conversion routine to stop prematurely. CR: JAGab77480 SR: 8606107301 It is possible to gain root access with the current design. CR: JAGab77872 SR: 8606107609 IE doesn't seem to handle the OnChange event well. The last input field entered does not trigger this event and gets stored as the old value/null. CR: JAGab81837 SR: 8606109138 Incorrect handling of quotes in header lines CR: JAGab82255 SR: 8606109555 The code to handle message store sizes was not suitable for systems with multiple sign-ons and omlimit settings CR: JAGab83272 SR: 8606110523 A new dedicated lookup daemon has been created to perform OpenMail hostname lookup for a given user. Web Client 6.0 will communicate with this process and get the user's hostname. If there are multiple matches to the user name then a list of matching names will be shown from which a name can be selected. If a profile is not specified in the URL then the Web Client 6.0 program can be optionally made to display a profile selection screen based on the value of the tweak SELECT-PGM. From this screen, the user can invoke the logon screen for any of the Web Client profiles. CR: JAGab83274 SR: 8606110525 The Openmail omslapd daemon was not un-binding the previous session if a connection is re-used. CR: JAGab83278 SR: 8606110529 Disabling Bulletin Board access from Web Client 6.0.:: This feature should allow the administrator to enable the BB access for a particular profile or all the profiles. CR: JAGab83749 SR: 8606110999 This is an Enhancement Request for enabling/disabling access to mailbox from the Web Client via VirtualVault. Through this feature the OpenMail administrator can enable or disable a user's mailbox from being accessed from the Internet by the Web Client via VirtualVault. CR: JAGab83752 SR: 8606111002 A truncated Web Client profile named Personal Administration Wizard created to access just the auto-action and password change services available with Openmail server. CR: JAGab84076 SR: 8606111938 The original design, construction was not following the standard RFC- 1468. CR: JAGab84362 SR: 8606112091 The attribute IM_FILE_ATTRIBUTES was considered mandatory in the mapper code which need not be present in the PDU. CR: JAGac20259 SR: 8606113989 Same as JAGac29288 Optimisation code for MAPI driver, was just trying to be too clever. A special case for search results was needed. CR: JAGac20262 SR: 8606113992 New code added for optimisation for MAPI drivers hadn't taken into account usage with older UAL clients. CR: JAGac23147 SR: 8606114169 rand() on linux returns larger integers than other platforms, this caused a variable to overflow CR: JAGac29140 SR: 8606114376 Auto-Actions with internet address in filter does not work because the flag TFV_FLT_NAME_INET for comparing internet address is not set in the filter record. Also when constructing the tf record for filter, wild-card character should be wrapped around the internet-address, so that it is not matched as an Openmail address. CR: JAGac29288 SR: 8606114524 Optimisation code for MAPI driver, was just trying to be too clever. A special case for search results was needed. CR: JAGac39969 SR: 8606124586 A discrepancy on the build machine for these binaries has rendered them inoperative. CR: JAGac40302 SR: 8606124910 The JavaScript(JS) function getYear() does not return identical values for different versions of Javascript. In JS 1.3 this function always returns [year minus 1900]. In JS 1.2 and earlier versions, it returns the [year minus 1900] for years between 1900 and 1999, and for all other years it returns the 4 digit year. The version of JS has changed to 1.3 for Netscape browser versions 4.06 and above. Hence the year 2000 is displayed as 100 [2000 minus 1900]. CR: JAGac40677 SR: 8606125286 Sun Microsystems have issued version 8.9.1 of sendmail.cf. Changes were required to the omsendin script in order to recognise the new version. PHSS_20551: CR: JAGab83434 SR: 8606110686 A coding problem in the Remote Client Interface was not allowing the PC Admin Client to connect to OpenMail. PHSS_20012: CR: JAGab32576 SR: D500419564 It should be possible to disable the functionality that derives a filename from a subject using a new general.cfg option : BRW_ITEMSUB_IS_FNAME=FALSE CR: JAGab34141 SR: 1653304451 When the Importing DirSync Server recevies a MODIFY Req on an Entry NOT Existing, ds_DoUpdates() ignores this request and hence an Error message is sent to the Originator. This problem is simulated when Selectors are set on Import a nd Export side and entry added without the Selector and Modified later. CR: JAGab34162 SR: 1653307066 The memory allocated by the user program is insuffient for handling long user names. CR: JAGab34164 SR: 1653307249 xport.in while decoding a doubly wrapped message uses only the External DL , which in this case doesn't contain the -TX ATTR. Since the customer is using 1984 X.400 Standard, which clearly doesn't support the -TX ATTR, xport.out while encoding the message, ignores all the -TX ATTR and constructs a DL, which doesn't contain -TX ATTR. CR: JAGab34183 SR: 1653309591 A coding error in the program causes the DDV fields to be treated as a part of OUs and this results in the address getting rejected by the system. CR: JAGab34770 SR: 5003458851 When an error condition was encountered in processing a transaction file, the TF record pointer was not being reset correctly. CR: JAGab35487 SR: D500353086 omaddpdln has many memory leaks. The 2 most serious ones both leak the amount of memory for the current PDL every time a name is added. CR: JAGab35885 SR: D500413443 change.log was not written when a BB with items was moved to another hierarchy within the BBAREA. CR: JAGab36268 SR: D500430124 The problem is caused by the TFR_COMP_TEXTPREVIEW record having a newline character in a string. CR: JAGab36274 SR: D500430421 OpenMail wasn't originally designed to have so many users. CR: JAGab37437 SR: D500420604 It should be possible to enable the functionality that derives a filename from a subject using a new general.cfg option : UXO_ITEMSUB_IS_FNAME=TRUE CR: JAGab39182 SR: 8606100829 The delegate deletion code checks the supplied name against the userlist and expects to find a match (ie. a local user of that name). If a match is not found then the delegate deletion fails. This will occur if the address (or name) of a local user has chnaged since the the delegate was added. This fix is to skip the check agains the userlist and if the supplied delegate name/address matches a configured delegate them remove it. CR: JAGab39209 SR: 8606100833 The cause of the problem was that the Outgoing Unix Gateway was using non-X400 attributes such as FF for lookup. CR: JAGab43863 SR: 8606101161 item.browse crashes becasue of an empty character string being used for string manipulation. This is because of the incorrect usage of strtok() in the function brw_parse_disposition(). CR: JAGab45433 SR: 8606101253 The library which handles the Client/Server communications contained some inefficient copying of data buffers. The effects of this was made worse in PP4 when the default size of the communications packets was increased to 28KB. CR: JAGab48848 SR: 8606101412 Server changes to allow Entrust integration: 1. UAL_CHKNAM command extended to return internet-style address to match email address in user's certificate. 2. 'omshowu' command has extra option: -S to display a user's internet address. 3. New directory attribute introduced: SMIME-ADDR (attr. no. 1300) 4. Modify Unix Gateway to process new Clear Signed message format. 5. Modify Item Browser to process new Clear Signed message format. 6. Write smimetxt : a converter from S/MIME to text. CR: JAGab48993 SR: 8606101413 A series of performance improvements have been implemented specifically to improve OpenMail performnace when accessed by the Outlook client. The server changes are all controlled by general.cfg options: UAL_5_40_PERF_CHANGES=TRUE/FALSE - global switch for all 5.40 performance changes. Can set this tweak FALSE and then selectively turn on individual tweaks and vice versa. UAKD_FT_DATA_IN_UAL_REPLY=TRUE/FALSE (used in uakd_main.c) - controls the appending of file-transfer data to a UAL Reply - this is done for UAL_EXPITM, UAL_OBJGET and UAL_SEARCH. UAL_CACHE_DIT_ENTRIES=TRUE/FALSE - controls whether a cache is used for reading of entries. UAL_NO_SINGLE_USER_NOTIFS=TRUE/FALSE - if TRUE then notifications will NOT be generated for message store changes where there is no other user (UAL session) running for that user that wants notifications. UAL_SUPPRESS_UTF_ACTIONS=TRUE/FALSE - 'UTF' is a mechanism that allows non-container attributes to be supplied for a msg (User TF) - e.g. ReplyToUsers If this mechanism is not used (and it is uncommon) then all the checks for UTF files can be removed. UAL_REUSE_WORKFILE=TRUE/FALSE - don't set this for general usage (yet). (It allows for more efficient usage in terms of NOT unlinking the work if it is going to be re-used.) UAL_LESS_BB_CHANGE_LOGGING=TRUE/FALSE - don't call bb_ logging routines for items that are not BB items. UAL_NO_MSG_CONTENT_NOTIFS=TRUE/FALSE - Dont generate a DIT entry or real DirectRef for message contents. Instead use the parent DirectRef+AbsRef. Doing saves DIT entries being created. (Only used for Outlook connections.) NFD_KEEP_MSG_FILES_OPEN=TRUE/FALSE - control whether communication files to notif.mon are kept open all the time or opened/closed for each notif. raised. (nfda_comms.c) LD_ADD_MAPI_ACK_INFO=TRUE/FALSE - control whether Creator/AckId/AckStatus info. gets added to returning Acks. Make Outlook handling of acks. more efficient. (ld_2user.c) CR: JAGab52686 SR: 8606101484 When unix.out does folding for message subject, it tries to break a line at the boundary of a 'unit' (a unit should not be broken by any folding, eg. a multibyte character, an escape sequence.) Multiple contiguous escape sequences were returned together as one unit, in some cases this could be a very long unit that makes folding impossible. CR: JAGab63192 SR: 8606101630 When an invalid Read Acknowledgement is passed to x400 out mapper, the mapper aborts due to improper error handling by the RECOVERY block of the function full_ack_pass2() in xgo_ack.c. CR: JAGab63519 SR: 8606101674 The UAL_LIST commands request all UAL_LIST fields to be returned to the client - however only the content size and (sometimes) the Absolute Reference are used. This results in far more information being retrieved by the POP3 daemon than is necessary. CR: JAGab65100 SR: 8606101738 D500 405621 ----------- Server-push handling in ual_sendcommand wasn't paying any attention to read failures on the socket. Fixed in exuak_lib.c 6.37. Callers of ual_GetNotif (Unix) or ual_getnotif (Windows) must take notice of error returns. Jeff Silver D500 419747 ----------- With server-push enabled on the server, clients that use UAL_NEWMSG always talk to their ual.remote process when polling for new mail, instead of using the Notification Server's datagram service. With server-push disabled, they do use the datagram service. CR: JAGab65826 SR: 8606101865 Containers not being accessed correctly CR: JAGab65894 SR: 8606101892 If a user is running 2 client session, and makes modifications to trays sizes from one, then the other session may not modify it's tray size information accordingly. It is therefore possible for tray sizes to become negative. These negative values are treated as large positive values and may lead to the ual.remote/ual.local session believing that the tray size limits have been exceeded - so reporting a problem. CR: JAGab68818 SR: 8606102816 ccmht2rtf is returning a bad error code as it dies on exit. CR: JAGab69420 SR: 8606103098 omrunning is SetUID root and doesn't need to be. CR: JAGab69554 SR: 8606103168 The username stored in the cookie is truncated to 256 characters by the user program. This length includes the escapes(brackets, ascii value etc.) so the actual length will be even less for multi-byte names. CR: JAGab69581 SR: 8606103183 It should be possible to disable the inclusion of "filename=" in "Content-Disposition" lines for "inline" items using new general.cfg option : INET_INLINE_FNAME_ALLOWED=FALSE CR: JAGab69827 SR: 8606103270 The cause of the problem was a number of uninitialised memory reads. CR: JAGab70399 SR: 8606103536 The July periodic patch contained fix JAGab34116 (1653300889) which preserved the difference between : "From " (Return-Path or OpenMail creator) and "From:" (OpenMail P2 Originator) in messages going out through the internet gateway. This is particularly useful for some redirected messages from mailing lists, as, typically, non-deliveries should go to the "From " address and any replies should go to the "From:" address. Unfortunately, when sending messages through the UUENCODE In ternet Gateway, the "From:" address was not being generated in the case of autoforwarded messages and SendMail was automatically inserting the same address as the "From " address. For an auto-forwarded message, this is the auto-forwarding user and thus, all trace of the original sender is removed. CR: JAGab70691 SR: 8606103672 A missing parameter to the UAL_PRPLST command is causing the checknames to fail on created/modified private DLs. CR: JAGab70712 SR: 8606103683 TNEF files which describe only an attachment in a message rather than the whole message were not being processed correctly. CR: JAGab70735 SR: 8606103696 uuencoded versions of these database files were included in previous patches by mistake CR: JAGab71129 SR: 8606103949 The PD attribute that has been added to the user's directory prevents the successful look-up of the FreeBusy time for that user and also causes the checking of the user's delegate permissions to fail. The PD (Physical Delivery/Postal Delivery) attribute is not being stripped out before performing the search on the FREEBUSY directory. This will cause the FreeBusy look-up to fail if the PD attributes have not been added to the user's entry in the FREEBUSY directory. Similarly the PD attributes are not being stripped out when a Delegate look-up is performed - this will cause the delegate not to be found if the look-up takes place across machines are the supplied username is used (rather that the user-nmber for a local look-up). Richard Hall - OpenMail Lab. (I anticipate that this problem will be fixed in PP-Nov-99) CR: JAGab72352 SR: 8606104673 There has always been a problem with using UAL_MODITM and the computed MAPI props blob: If the CompMAPIProps blob contains a To or CC recpient list and a UAL_MODITM call is issued that modifies the CompMAPIProps blob then the UAL's snapshot of the CompMAPIProps blob becomes truncated (the To/CC recip list info. disappears). If the item is UAL_LISTed then the CompMAPIProps blob appears empty altough the data in the real server msg-store is correct. This has only become a problem at 5.40 because the information for some items (eg. Send Items folder items that are added to the Send Items folder before the folder is opened) is discarded by the SP and refreshed from the complete UAL_LIST info. CR: JAGab73411 SR: 8606105379 Missing check code CR: JAGab74688 SR: 8606105942 The routine that obtains the capabilites assigned to a delegate user for a given principal opens the 'designate TF' for that principal to extract the caps. but does not close the TF. CR: JAGab74934 SR: 8606106089 X.400 is worked around to accept 2 digit years after 2000. However this enhancement will not work dates beyond 2009. CR: JAGab75964 SR: 8606106663 Implementation problem PHSS_20045: CR: JAGab77877 SR: 8606107612 A coding problem in the Service Router causes memory to be allocated every time a message is processed and rulesets are enabled. PHSS_19172: CR: JAGab32489 SR: 5003454785 The method the DRS uses to detect that a transient child has exited, is not robust enough. CR: JAGab34013 SR: 1653286757 Unix incoming gateway was unable to split the addresses in the Arpa Distribution List in some messages from Outlook Express. CR: JAGab34149 SR: 1653305789 omcpinu was unable to handle the situation properly when there isn't a corresponding BASIC_DATA for a BASIC_ITEM of Distribution List in the input data. CR: JAGab34153 SR: 1653306381 In some cases an NDN from the Internet will come into Openmail with a "Mail From" set to "< >". This is not handled well within the Openmail Internet gateway. CR: JAGab34175 SR: 1653308544 The Openmail Desk gateway cannot map the X400 Per-recipient flags of a message from X400, to an equivalent HP Desk Transaction file record. So, when an acknowledgement is generated by the Desk gateway, the the TFR_FULL_ACK TF record is not set up correctly. CR: JAGab36232 SR: D500428383 Added Viral Cleaning capability to service.router CR: JAGab36250 SR: D500429423 omresetmn, omaddmnmp etc are all scripts (actually the same script with different names) This script uses /bin/sh as its shell, but the shell in this location on Solaris is an extremely old implementation of the Bourne shell which does not support functions. CR: JAGab36271 SR: D500430249 Attachments that only contain "MAPI 1.0 embedded message" signify an embeded message follows and should be deleted. CR: JAGab36273 SR: D500430413 ualth's simple list mode assumes that there is a string representing the creator of an item for every item in the list. In fact, if there isn't a creator, this string is set to null and should not be referenced. CR: JAGab37632 SR: 1653308734 X.400 code limits GraphicStrings up to a maximum of 16 octets. The PDU contains a GraphicString of 23 octets which caused the overflow error. CR: JAGab39965 SR: 8606100966 The fix for 5003445072 triggered an existing problem in the code. CR: JAGab49811 SR: 8606101415 If there was no global/config file present on the installation, OpenMail assumed that the machine was not running in a ServiceGuard environment. CR: JAGab67687 SR: 8606102175 Converter errors which were previously ignored were now being noticed and incorrectly handled by the cc:Mail UAL access code. PHSS_18905: CR: JAGab34711 SR: 5003444174 customer missunderstandings lead them to corrupt their message stores. OpenMail attempted to recover from this when it is in fact better to halt processing imediately. CR: JAGab34106 SR: 1653299818 The problem may be caused by spurious error number returned even when the entry is valid. Should only check error number if no valid entry is returned. CR: JAGab36206 SR: D500427419 reducution in openmail cpu usage. CR: JAGab36209 SR: D500427443 reduce openmail cpu usage. CR: JAGab36208 SR: D500427435 reduction in openmail cpu usage. CR: JAGab36207 SR: D500427427 reduce openmail cpu usage CR: JAGab36251 SR: D500429431 An interim enhancement to partially address 1653 240598. Aim for 20% (heavily system dependent) reduction in elasped/cpu time. CR: JAGab32586 SR: D500428334 Unix gateway has problem decoding TNEF files CR: JAGab33495 SR: 1653221341 If services are not re-started after omdiropt, changes to the directory are not noticed by them and this can result in un-necessary time spent by support staff trying to track down why changes aren't being noticed. CR: JAGab36218 SR: D500427906 TNEF att names mismatched if the att name followed the att data in the tnef file CR: JAGab36255 SR: D500429530 Japanese Web client needed to improve the localisation. CR: JAGab36235 SR: D500428839 The problem is caused by an attempt to read details from the parent of the specified direct reference. If no parent exists, as is the case for the Bulletin Board, then the read fails. CR: JAGab34006 SR: 1653286120 When external converter crashes, no proper action is taken to inform the user and system administrator. This was causing the problem that users see a blank item in the message. CR: JAGab35879 SR: D500413104 message order cannot be guarenteed. OpenMail does not retain obsolete message information to check future messages. CR: JAGab36219 SR: D500427914 Filename characterset not used CR: JAGab34063 SR: 1653294579 The way MAPI properties are represented in OpenMail messages has changed, causing a backwards compatibility problem. CR: JAGab34116 SR: 1653300889 This was a coding problem with the unix gateway. This code, written in 1994, gave precedence to content-originators over envelope-originators for deciding a suitable SMTP envelope-originator. The original code had never been tested to make sure that it was correct (note that the envelope originator and content originator of practically all OpenMail messages is exactly the same). CR: JAGab34151 SR: 1653305979 The SR_RESOLVE_MASK general.cfg option causes a recipient redirection record to be added even when a name that is re-resolved has not changed. This causes the improved redirection loop detection introduced with the 5.30 changes (GR5/PP-Dec 1998) to treat this as a loop and generate a NDN. CR: JAGab34126 SR: 1653302042 Receipt acks going back to Exchange via X.400 have the ORN part of the message id stripped. CR: JAGab36217 SR: D500427898 When a Notes users name contains 8-bit characters, the Openmail Notes Gateway encodes it into teletext form and does not produce a degraded, printable form. Thsi causes problems for the X400 Gateway. CR: JAGab34781 SR: 5003463190 Outlook posted items are stored in the OpenMail message store as messages without any distribution list. The cc:Mail client cannot access messages whose first body part is not a distribution list CR: JAGab34121 SR: 1653301507 When the delegate tries to access bulletin board items, he only has read access, where he should have Read, Attach, Modify and Delete access. CR: JAGab34021 SR: 1653287946 Store and forward transport mechanisms such as OpenMail and SendMail do not guarantee that messages will arrive in the same order as they were sent. If a Del-Req for an Item arrived on the Importing Server because of a possible Message ReOrder by SendMail, currently Del-Req is ignored by the BB-Server as 'Trying to Delete an Item NOT Existing' and the Request is ignored. But the Add for the corressponding Item arriving later to Del-Req will Add-Item on the Importer hence leaving BB Servers out of sync. CR: JAGab34111 SR: 1653300392 For the same user ID and profile, all the sessions for Web Client 5.10 use a single user program to handle their requests. If the user program is busy with some command, then the other sessions will not be able to run any command during that time. Moreover, no new sessions can be started for the user. CR: JAGab35943 SR: D500415729 The UAL API returns an empty string for the Total KBytes. CR: JAGab34128 SR: 1653302414 The end of contents octets were not read for single asn encoded body parts which causes this problem when there are more than one such body part. CR: JAGab32579 SR: D500425553 Both the omopcsm and omadmr binaries have sections of code that sometimes pass NULL pointers into expressions. This situation tends to cause SEGVIOLATION on SUN boxes. The situations that occur are valid and the code has been updated to handle them. CR: JAGab34178 SR: 1653308759 A check was introduced to the Mime handling code which dis-allowed addresses which did not contain DDT's. This was introduced in the B.06 version of OpenMail. PHSS_18282: CR: JAGab35997 SR: D500418079 The code to remove an ACL file when a container is detached is placed at too low a level within the ctner access routines. This means that it gets invoked when a move is done as the move is really an attach followed by a delete. CR: JAGab36190 SR: D500426809 If the redirected message is not to be retained in the Inbox then only the first AA_REDIRECT gets recorded and actioned. CR: JAGab32581 SR: D500426841 The BB_HAS_ACL flag in the Inbox container is being unset by a subsequent UAL_MODITM call to change the ListMAPIProps on the Inbox. This is because the UAL List record for the zeroth record (which is a copy of the ctner record) is not being updated with the BB_HAS_ACL flag when the Inbox ACL (permissions) are initially added. CR: JAGab34022 SR: 1653287953 Failed deletion synchronisations are currently ignored. CR: JAGab34089 SR: 1653297937 A check of whether the new item being added was in the bulletin board or not was incorrect. The source container was checked instead of the target container. CR: JAGab36171 SR: D500426189 A buffer being used to receive notification prompts from the Notification Monitor is to small to receive all the data being read into it if many outstanding notifications prompts are in the pipe. CR: JAGab36168 SR: D500426130 There are some places in the code where ctner records are updated when this is either unnecessary for BB items or the update is legitimate but should cause a notification to be raised for a BB item. CR: JAGab36200 SR: D500427070 Incorrect return code from LDAP server for certain failed searches CR: JAGab32582 SR: D500426965 The call to uald_GetDelegCaps in uakd_main.c needs to pass a pointer to the UAL command buffer structure. It is automatically dereferenced on HP-UX but not on AIX or Solaris. CR: JAGab34091 SR: 1653297986 The core dump on Solaris occured because the Encoding string was NULL as it hadn't been set up for the non-existent body-part. The gateway should not have tried to write an "Encoding:" string but it did, and the access to this NULL string resulted in the core dump. CR: JAGab36170 SR: D500426163 This problem is caused by a change to GR5 not being rolled to top-of-tree correctly. ACL_FLDR_PERM_CREATE permissions are missing from the default Outlook-style permissions. CR: JAGab34099 SR: 1653299024 When the tweak X4I_STRIP_ALL_RECIPS or X4I_STRIP_ALL_DL_RECIPS are set, external attributes should be stripped from FROM addresses even if the FROM addresses are not in the active recipient list. External attributes were being stripped only for active recipients. CR: JAGab33809 SR: 1653256966 The Notes documentation specifies that these should be 32 characters, but does not police this and actually supports more. The Openmail Lotus Notes Gateway was implemented to the specification. CR: JAGab34746 SR: 5003450593 The reason the -I option doesn't work with the -g option in this case is that the search filter specified by the -g option has PROPAGATED-BY attached to it automatically which means that any change of value of PROPAGATED-BY means that the entry will not be matched and a non-fatal error raised. CR: JAGab34083 SR: 1653297242 Different OpenMail clients place different information in the subject field. It is not necessarily the filename of an item. The code that attempts to form a filename from a T.61 subject was written at a time when internet mailers which could not handle filenames containing spaces were common. The code is thus over zealous in trying to remove spaces from the potential filename. CR: JAGab33573 SR: 1653231563 Acknowledgements are sent marked "urgent" by OpenMail. A way of configuring this so that they are either sent with the same priority as the original message or sent with a specific acknowldegement level would be desirable. For instance, a general.cfg option like : AK_ACK_MSG_PRI=0 could be used to force all acknowledgements to be sent with normal priority. (valid values : 0, 1 (non-urgent) and 2 (urgent)) In addition, the following configuration option could be used to tie the priority of the acknowledgement message to be the same as the that for the message being acknowledged : AK_ACK_SAME_PRI=TRUE CR: JAGab35777 SR: D500401539 The routine that maps a mailnode to a host name does not handle TTX variants of mailnodes correctly. CR: JAGab32360 SR: 1653229252 Some aspect of the Japanese localisation of the Web Client needed improvment. CR: JAGab36169 SR: D500426155 unix.in is not tidying up its temporary files thus creating the occasional orphan. CR: JAGab36162 SR: D500425934 ual_DeleteList in ual_access.c can be called repeatedly to close the same UAL List as part of the tidyup/shutdown activity at the end of a session. Any memory free'ed should set the pointers to NULL after the free so that a second entry does not free the memory again (illegally). CR: JAGab34730 SR: 5003446914 The OpenMail command ommoddir can be used to set the Directory Change Log Life, and so can the Directory Synchronisation commands 'omaddds -n' and 'ommodds -n'. Internally, these 2 log life values are held in different places. The man pages for omaddds and ommodds do not explain the interaction between these 2 log life settings, or how to reduce the log life. Further the 'omaddds -n' command cannot be used to set the log life to less than the default value of 7. This is not explained. CR: JAGab36133 SR: D500424820 unix.out does not output a From line for MDN/DSNs. CR: JAGab34757 SR: 5003453712 There is no default action for 5* and 4* returns for SM. There should be. CR: JAGab35992 SR: D500417568 Child processes spawned to handle incoming connections were trying to validate the name of the protocol that was configured for NDNs. They can't do this validation properly, because they have discarded all knowledge about protocols other than the incoming one they were spawned to handle. CR: JAGab35778 SR: D500401547 RTF Preview call did not understand multibyte. CR: JAGab35772 SR: D500399246 Parts of mime default mailnode left around with tnef mailnode CR: JAGab34545 SR: 5003406132 omscan's design means that it needs the memory to store the item info of the entire message store in order to detect orphans, therefore it hits the limit when the message store is very large. CR: JAGab34737 SR: 5003448654 A coding defect in the service router meant that routable ORNs without a Surname field were unnecessarily looked up in the directory. CR: JAGab32580 SR: D500426676 A coding problem in the Internet gateway and MIME item browser cause content-type header fields to be converted to lower case when associating a character set with a text content type. CR: JAGab34109 SR: 1653299974 A defect in cd.browse made it fail to fold a long line in some cases, and this was causing the consequence that cd.browse repeatedly processes the same record but does not move on. CR: JAGab36221 SR: D500428029 T.61 text is not being treated as text when local.delivery set the 'MAPI attachment' flag in the msg container. CR: JAGab36194 SR: D500426882 The problem is caused by the file information being recorded even if it is found to be a non-openmail file when scanning the data sub domain. CR: JAGab36236 SR: D500428953 The code to update an existing list of items does not find out whether it is a BB list that is being updated - consequently the read/unread status is taken to be that of the new item rather than using the BB user sequence file to determine whether the item is new for this particular user. CR: JAGab36234 SR: D500428821 The problem was caused by dodgy code in brw_mime.c -- the code set a flag to re-read a blank line even if no blank line had been read. CR: JAGab34968 SR: D500293266 A problem in constructing the form of the filter required for submission to the UAL caused the final ")" character to be dropped from the UAL search request. CR: JAGab32583 SR: D500427344 Failed deletion synchronisations are currently ignored. CR: JAGab36055 SR: D500421016 The omscan orphan scanning process can take a long time and also slows down other OpenMail processes. CR: JAGab36239 SR: D500429050 When checking that the omoff process has completed, the check erroneously included the username, which can vary. CR: JAGab34717 SR: 5003444901 The problem is caused by the limit of 256MB maximum size of stack + data allowed by conventional segmentation on AIX being reached. (See Large Program Support Overview - from AIX 3.2.5 "info" command). CR: JAGab36230 SR: D500428318 The DNS lookup files were not copied to the change root directory. The system could recognize only IP addresses and not aliases. CR: JAGab36231 SR: D500428326 The file ownerships for the OpenMail files in the change root directory were changed to bin:hpoffice, wherever possible. User 'bin' does not have any permissions on the files owned by it. CR: JAGab34719 SR: 5003445072 When ccMail quotes a line that is exactly full, it adds a trailing space. The cd.browser correctly identifies this as a line overflow and wraps the line, effectively adding a new line. CR: JAGab34136 SR: 1653303784 There are 3 causes of this problem : 1 The UAL does not have the correct value for the size when the list command is done. 2 The UAL has a new optimisation for its datacomm which cuts down on sending un-necessary information. Thus, when the size is thought to be 0, no size information is transmitted at all. Before, the value 0 used to be transmitted. 3 The Web client has not been updated to reflect the change mentioned in cause 2. CR: JAGab36241 SR: D500429175 The code called the select system call with Max FD set much larger than the readfds... array sizes. Consequently select failed, and the client could not get the result of its bind call to the server. SR: 8606296148 8606299316 8606306147 8606307934 8606307942 8606307945 8606307949 8606307950 8606110229 8606285855 8606286454 8606288373 8606288693 8606289790 8606224537 8606273505 8606277728 8606277792 8606278311 8606278755 8606279417 8606280333 8606284168 8606201876 8606238864 8606254208 8606260336 8606260401 8606260403 8606261785 8606262840 8606266965 8606267820 8606268859 8606269075 8606269632 8606271509 8606168832 8606245558 8606245561 8606248886 8606251070 8606255018 8606257997 8606258235 8606215723 8606226007 8606228125 8606228536 8606233575 8606237428 8606238426 8606214343 8606214723 8606214740 8606215716 8606215745 8606218500 8606219531 8606219749 8606220921 8606221356 8606222161 8606224187 8606225815 8606226394 8606160818 8606162150 8606196695 8606198411 8606199624 8606200362 8606201464 8606201916 8606203966 8606205540 8606205863 8606206802 8606209895 1653231704 8606100957 8606102906 8606154951 8606162348 8606165799 8606171299 8606172203 8606172211 8606172377 8606173373 8606173797 8606173798 8606174784 8606175570 8606176209 8606176642 8606176644 8606177205 8606177664 8606178664 8606178878 8606179216 8606180360 8606181602 8606184631 8606186206 8606187277 8606187413 8606188546 8606188772 8606189626 8606194177 8606195023 8606195467 1653231704 8606100957 8606102906 8606154951 8606162348 8606165799 8606172203 8606172211 8606172377 8606173373 8606173797 8606173798 8606175570 8606176209 8606176642 8606177664 8606178878 8606180360 8606172582 8606172773 8606172855 8606173387 8606173621 8606175176 8606169547 8606159934 8606173711 8606152653 8606155833 8606156005 8606157213 8606158242 8606159318 8606159513 8606159909 8606160320 8606160571 8606162142 8606162163 8606162796 8606164212 8606164474 8606164917 8606165208 8606165435 8606168062 8606168129 8606168431 8606161671 8606112256 8606135910 8606136077 8606141768 8606144279 8606145237 8606145896 8606146003 8606151881 8606152455 8606152480 8606154150 8606154191 8606154357 8606154360 8606154726 8606155703 8606158413 1653262501 8606101643 8606105114 8606114526 8606131537 8606132524 8606132732 8606133711 8606133860 8606134007 8606134759 8606134871 8606134884 8606136626 8606137667 8606137874 8606138290 8606139655 8606141637 8606141783 8606142895 8606143206 8606143218 8606151872 1653240259 5003366708 5003454405 1653285569 1653296350 1653298653 1653306589 1653310714 5003465195 D500253328 8606105866 8606105948 8606106702 8606107035 8606107773 8606108351 8606109330 8606109847 8606112206 8606112263 8606114582 8606114696 8606124275 8606124793 8606124838 8606125848 8606127917 8606128205 8606129065 8606129086 8606129210 8606129240 8606129332 8606129454 8606129510 8606129512 8606129516 8606129914 8606130260 8606130710 8606131026 8606131027 8606131199 8606131389 8606131548 8606132170 8606132204 8606132408 8606132664 8606132703 8606132708 8606133544 8606134624 8606134641 8606135412 8606135539 5003444679 1653272351 1653291617 8606101854 8606103019 8606104741 8606104884 8606105045 8606106664 8606106674 8606107113 8606107301 8606107609 8606109138 8606109555 8606110523 8606110525 8606110529 8606110999 8606111002 8606111938 8606112091 8606113989 8606113992 8606114169 8606114376 8606114524 8606124586 8606124910 8606125286 8606110686 D500419564 1653304451 1653307066 1653307249 1653309591 5003458851 D500353086 D500413443 D500430124 D500430421 D500420604 8606100829 8606100833 8606101161 8606101253 8606101412 8606101413 8606101484 8606101630 8606101674 8606101738 8606101865 8606101892 8606102816 8606103098 8606103168 8606103183 8606103270 8606103536 8606103672 8606103683 8606103696 8606103949 8606104673 8606105379 8606105942 8606106089 8606106663 8606107612 5003454785 1653286757 1653305789 1653306381 1653308544 D500428383 D500429423 D500430249 D500430413 1653308734 8606100966 8606101415 8606102175 5003444174 1653299818 D500427419 D500427443 D500427435 D500427427 D500429431 D500428334 1653221341 D500427906 D500429530 D500428839 1653286120 D500413104 D500427914 1653294579 1653300889 1653305979 1653302042 D500427898 5003463190 1653301507 1653287946 1653300392 D500415729 1653302414 D500425553 1653308759 D500418079 D500426809 D500426841 1653287953 1653297937 D500426189 D500426130 D500427070 D500426965 1653297986 D500426163 1653299024 1653256966 5003450593 1653297242 1653231563 D500401539 1653229252 D500337337 D500426155 D500425934 5003446914 D500424820 5003453712 D500417568 D500401547 D500399246 5003406132 5003448654 D500426676 1653299974 D500428029 D500426882 D500428953 D500428821 D500293266 D500427344 D500421016 D500429050 5003444901 D500428318 D500428326 5003445072 1653303784 D500429183 D500429175 1653304717 Patch Files: /opt/openmail/patch/filesets/OM-ADM /opt/openmail/patch/filesets/OM-AMECAT /opt/openmail/patch/filesets/OM-AMEICE /opt/openmail/patch/filesets/OM-AMEWEB /opt/openmail/patch/filesets/OM-APPL /opt/openmail/patch/filesets/OM-BB /opt/openmail/patch/filesets/OM-CCMOB /opt/openmail/patch/filesets/OM-CHSCAT /opt/openmail/patch/filesets/OM-CHSICE /opt/openmail/patch/filesets/OM-CHSPSS /opt/openmail/patch/filesets/OM-CHSWEB /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-ENGWEB /opt/openmail/patch/filesets/OM-FINCAT /opt/openmail/patch/filesets/OM-FINICE /opt/openmail/patch/filesets/OM-FINWEB /opt/openmail/patch/filesets/OM-FRECAT /opt/openmail/patch/filesets/OM-FREICE /opt/openmail/patch/filesets/OM-FREWEB /opt/openmail/patch/filesets/OM-GERCAT /opt/openmail/patch/filesets/OM-GERICE /opt/openmail/patch/filesets/OM-GERWEB /opt/openmail/patch/filesets/OM-IMAP4 /opt/openmail/patch/filesets/OM-ITACAT /opt/openmail/patch/filesets/OM-ITAICE /opt/openmail/patch/filesets/OM-ITAWEB /opt/openmail/patch/filesets/OM-KORCAT /opt/openmail/patch/filesets/OM-KORICE /opt/openmail/patch/filesets/OM-KORPSS /opt/openmail/patch/filesets/OM-KORWEB /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-NIPPSS /opt/openmail/patch/filesets/OM-NIPWEB /opt/openmail/patch/filesets/OM-NOTES /opt/openmail/patch/filesets/OM-PMOVER /opt/openmail/patch/filesets/OM-POP3 /opt/openmail/patch/filesets/OM-PTBCAT /opt/openmail/patch/filesets/OM-PTBICE /opt/openmail/patch/filesets/OM-PTBWEB /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-SPAWEB /opt/openmail/patch/filesets/OM-SWECAT /opt/openmail/patch/filesets/OM-SWEICE /opt/openmail/patch/filesets/OM-SWEWEB /opt/openmail/patch/filesets/OM-UNIX /opt/openmail/patch/filesets/OM-X400 /opt/openmail/patch/ompatch /opt/openmail/patch/PHSS_29063/omunpatch /opt/openmail/patch/PHSS_29063/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-AMEWEB: No what strings /opt/openmail/patch/filesets/OM-APPL: No what strings /opt/openmail/patch/filesets/OM-BB: No what strings /opt/openmail/patch/filesets/OM-CCMOB: No what strings /opt/openmail/patch/filesets/OM-CHSCAT: No what strings /opt/openmail/patch/filesets/OM-CHSICE: No what strings /opt/openmail/patch/filesets/OM-CHSPSS: No what strings /opt/openmail/patch/filesets/OM-CHSWEB: 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-ENGWEB: 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-FINWEB: 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-FREWEB: 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-GERWEB: 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-ITAWEB: 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-KORPSS: No what strings /opt/openmail/patch/filesets/OM-KORWEB: 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-NIPPSS: No what strings /opt/openmail/patch/filesets/OM-NIPWEB: No what strings /opt/openmail/patch/filesets/OM-NOTES: No what strings /opt/openmail/patch/filesets/OM-PMOVER: No what strings /opt/openmail/patch/filesets/OM-POP3: No what strings /opt/openmail/patch/filesets/OM-PTBCAT: No what strings /opt/openmail/patch/filesets/OM-PTBICE: No what strings /opt/openmail/patch/filesets/OM-PTBWEB: 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-SPAWEB: 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-SWEWEB: No what strings /opt/openmail/patch/filesets/OM-UNIX: No what strings /opt/openmail/patch/filesets/OM-X400: No what strings /opt/openmail/patch/ompatch: $Header: sh_patch.gen /main/gr6_patch/3 2002/04/26 1 8:34:36 $ /opt/openmail/patch/PHSS_29063/omunpatch: $Header: sh_unpat.gen,v /opt/openmail/patch/PHSS_29063/ompatch.idx: No what strings cksum(1) Output: 77823771 1147480 /opt/openmail/patch/filesets/OM-ADM 2723742393 299995 /opt/openmail/patch/filesets/OM-AMECAT 97813762 112636 /opt/openmail/patch/filesets/OM-AMEICE 618625742 4329 /opt/openmail/patch/filesets/OM-AMEWEB 2334501200 572992 /opt/openmail/patch/filesets/OM-APPL 1743632175 215346 /opt/openmail/patch/filesets/OM-BB 2024990915 196166 /opt/openmail/patch/filesets/OM-CCMOB 1271544808 135776 /opt/openmail/patch/filesets/OM-CHSCAT 1386483880 99560 /opt/openmail/patch/filesets/OM-CHSICE 2211019739 64991 /opt/openmail/patch/filesets/OM-CHSPSS 1510634903 4342 /opt/openmail/patch/filesets/OM-CHSWEB 2469012790 14963065 /opt/openmail/patch/filesets/OM-CORE 1863747397 380326 /opt/openmail/patch/filesets/OM-DESK 3381401968 341658 /opt/openmail/patch/filesets/OM-DSYNC 151107617 299987 /opt/openmail/patch/filesets/OM-ENGCAT 2177679850 112616 /opt/openmail/patch/filesets/OM-ENGICE 2495322358 4318 /opt/openmail/patch/filesets/OM-ENGWEB 1766833831 279284 /opt/openmail/patch/filesets/OM-FINCAT 2367538046 115055 /opt/openmail/patch/filesets/OM-FINICE 194469801 4362 /opt/openmail/patch/filesets/OM-FINWEB 1195435660 279134 /opt/openmail/patch/filesets/OM-FRECAT 3704701904 100432 /opt/openmail/patch/filesets/OM-FREICE 2996573802 4383 /opt/openmail/patch/filesets/OM-FREWEB 1042007863 279516 /opt/openmail/patch/filesets/OM-GERCAT 1786449301 100395 /opt/openmail/patch/filesets/OM-GERICE 2320861921 4354 /opt/openmail/patch/filesets/OM-GERWEB 1628392627 490388 /opt/openmail/patch/filesets/OM-IMAP4 3751779433 276609 /opt/openmail/patch/filesets/OM-ITACAT 2574375940 99784 /opt/openmail/patch/filesets/OM-ITAICE 2667122492 4345 /opt/openmail/patch/filesets/OM-ITAWEB 4208869420 137657 /opt/openmail/patch/filesets/OM-KORCAT 117699745 99926 /opt/openmail/patch/filesets/OM-KORICE 1934313795 66979 /opt/openmail/patch/filesets/OM-KORPSS 3717293182 4362 /opt/openmail/patch/filesets/OM-KORWEB 662126178 1841855 /opt/openmail/patch/filesets/OM-LC 1335545604 292274 /opt/openmail/patch/filesets/OM-LDAP 4007506941 33188 /opt/openmail/patch/filesets/OM-MAN 2349888251 139319 /opt/openmail/patch/filesets/OM-NIPCAT 636623681 102302 /opt/openmail/patch/filesets/OM-NIPICE 2951503145 66010 /opt/openmail/patch/filesets/OM-NIPPSS 2655088552 14443 /opt/openmail/patch/filesets/OM-NIPWEB 1703652919 1194131 /opt/openmail/patch/filesets/OM-NOTES 2516657403 142628 /opt/openmail/patch/filesets/OM-PMOVER 869191986 402105 /opt/openmail/patch/filesets/OM-POP3 2300677460 279981 /opt/openmail/patch/filesets/OM-PTBCAT 3041458208 100362 /opt/openmail/patch/filesets/OM-PTBICE 1582291836 4364 /opt/openmail/patch/filesets/OM-PTBWEB 374518076 3484320 /opt/openmail/patch/filesets/OM-RC 2232565999 419653 /opt/openmail/patch/filesets/OM-SMS 1215493452 277979 /opt/openmail/patch/filesets/OM-SPACAT 3404884024 100169 /opt/openmail/patch/filesets/OM-SPAICE 3774092709 4375 /opt/openmail/patch/filesets/OM-SPAWEB 2417306570 276436 /opt/openmail/patch/filesets/OM-SWECAT 3973538380 114100 /opt/openmail/patch/filesets/OM-SWEICE 3771372353 4347 /opt/openmail/patch/filesets/OM-SWEWEB 3274770588 361238 /opt/openmail/patch/filesets/OM-UNIX 3372349507 1106038 /opt/openmail/patch/filesets/OM-X400 3464775811 31684 /opt/openmail/patch/ompatch 382733169 16635 /opt/openmail/patch/PHSS_29063/omunpatch 1433358596 567739 /opt/openmail/patch/PHSS_29063/ompatch.idx Patch Conflicts: None Patch Dependencies: None Hardware Dependencies: None Other Dependencies: None Supersedes: PHSS_18282 PHSS_18905 PHSS_19172 PHSS_20012 PHSS_20045 PHSS_20551 PHSS_20776 PHSS_21439 PHSS_21944 PHSS_22361 PHSS_22457 PHSS_22699 PHSS_22929 PHSS_22990 PHSS_22995 PHSS_23081 PHSS_23342 PHSS_24094 PHSS_24873 PHSS_25645 PHSS_26275 PHSS_27059 PHSS_27677 PHSS_28154 PHSS_28589 Equivalent Patches: PHSS_29064: s700: 11.00 11.04 11.11 s800: 11.00 11.04 11.11 PFSS_17045: sparcSUN: 5.5.1 5.6 5.7 5.8 PASS_17045: AIX: 4.2.1 4.3 5.1 PLSS_17049: intelLinux: RedHat7.0 RedHat7.1 RedHat7.2 RedHat7.3 Patch Package Size: 31180 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_29063 5a. For a standalone system, run swinstall to install the patch: swinstall -x autoreboot=true -x match_target=true \ -s /tmp/PHSS_29063.depot By default swinstall will archive the original software in /var/adm/sw/patch/PHSS_29063. 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_29063.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_29063.depot of=/dev/rmt/0m bs=2k Special Installation Instructions: SUBSYSTEM_SHUT ================================================= PHSS_28589: ================================================= 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_28154: ================================================= CR: JAGae42811 SR: 8606278755 ------------------------------- The general.cfg option PM_STRIP_MAPI_REPLY_RECIPS=TRUE must be set to activate this new behaviour. ================================================= PHSS_27677: ================================================= 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_27059: ================================================= 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_26275: ================================================= 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_25645: ================================================= 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_24873: ================================================= 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. ================================================= PHSS_22457: ================================================= CR: JAGad30987 SR: 8606161671 ------------------------------- Server components for the MAPI Offline Folder Sync. EEP Set the general.cfg option OFS_ENABLED=TRUE to enable offline folder sync. with Outlook. See MAPI OFS Release Notes for details of OpenMail server and MAPI/SP changes. ================================================= PHSS_22361: ================================================= CR: JAGad23468 SR: 8606154150 ------------------------------- After installing Openmail on Linux, ommakeom needs to be run to create the first data instance, if not already present. This must be done before omrc is run to start OpenMail. CR: JAGad27743 SR: 8606158413 ------------------------------- The general.cfg options : MDC_DDS_DELETE_DATA and MDC_DDS_LOG_FNAME are no longer supported as of the October 2000 periodic patch. ================================================= PHSS_21439: ================================================= CR: JAGab34850 SR: D500253328 ------------------------------- ## Quoted Strings Support in general.cfg ## Generally , '_' characters entered as part {=} string in general.cfg are converted to ' ' characters. With this fix in place, we provide an option to the customer to enter the string within double-quotes, and thereby retaining '_' as '_' itself. Something like UXO_UNIX_MAIL_CHARSET="ISO8859_1". To enable this fix, the customer needs to have another tweak CUST_QUOTED_CFG_OPTIONS_SUPPORTED=TRUE, before the line where the string is entered within double-quotes. This pre-conditional check is done for both the GR5 & GR6 versions. CR: JAGac87851 SR: 8606129516 ------------------------------- If the webselect.cgi CGI script is called with the "https" protocol then the ROOT-URL tweak must be specified in the ~openmail/omhtml/config file. CR: JAGac88829 SR: 8606129914 ------------------------------- The November 1999 and February 2000 periodic patches incorrectly stated that the default valued of the general.cfg setting : UXO_ITEMSUB_IS_FNAME was TRUE. For B.06.00 and later, the default value is FALSE. CR: JAGac95131 SR: 8606130260 ------------------------------- To enable internet address comments to be saved in messages entering OpenMail through the Internet Gateway, and displayed by the IMAP4 and POP3 interfaces, set these 2 options in the ~/sys/general.cfg file: INET_SAVE_IA_COMMENTS=TRUE INET_DISPLAY_IA_COMMENTS=TRUE ================================================= PHSS_20776: ================================================= CR: JAGab32483 SR: 5003444679 ------------------------------- Special 1159 for HKT For further information about all the new enhancements available in this patch, refer to the following web-site: CR: JAGab83272 SR: 8606110523 ------------------------------- 1. The Portal feature is OFF. To enable it please specify the tweaks in /var/opt/openmail/omhtml/portal.cfg. 2. Create symlinks in the web server's cgi-bin directory to /opt/openmail/bin/webselect.cgi and /opt/openmail/bin/select.cgi. If symlinks are not allowed, then copy webselect.cgi and select.cgi from the /opt/openmail/bin directory to the Web server's cgi-bin directory and retain the permissions. ***** NOTE: Perform steps 3-6 only if you want the portal daemon to start automatically during system startup. Otherwise you will have to start or stop the daemon manually ***** 3. On HP-UX - a) Copy /opt/openmail/newconfig/por_config to /etc/rc.config.d/omportal. b) Change perms to 444 and ownership to bin:bin c) Create symlinks from /sbin/rc*.d to /sbin/init.d/omportal. For easy reference the names should end in omportal d) START_PORTAL is 0 in etc/rc.config.d/omportal. Change it to 1 if you want the portal process to start during system startup. 4. On LINUX - a) Copy /opt/openmail/newconfig/por_config to /etc/sysconfig/omportal. b) Change perms to 444 and ownership to root:root c) Create symlinks from /etc/rc.d/rc*.d to /etc/rc.d/init.d/omportal. d) START_PORTAL is 0 in /etc/sysconfig/omportal. Change it to 1 if you want the portal process to start during system startup. 5. On AIX - a) Create an entry in the /etc/inittab file for the portal process (/opt/openmail/bin/portal.daemon) if you want the script to start during system startup. b) Add entry /opt/openmail/bin/kill.portal to the system shutdown script to shutdown cleanly the portal daemon during system shutdown. 6. On SunOS - a) Create files /etc/rc0.d/K09omportal and /et c/rc2.d/S89omportal with perms 555 and ownership root:other b) Create a link to /etc/init.d/omportal.stop from /etc/rc0.d/K09omportal and a link to /etc/init.d/omportal.start from /etc/rc2.d/S89omportal. ***** NOTE: Perform step 7 if you want to manually start or stop the portal daemon ***** 7. To manually start the portal daemon, type /opt/openmail/bin/portal.daemon. To manually stop the portal daemon type /opt/openmail/bin/kill.portal. You must have root privileges. 8. The portal daemon starts a UAL session for performing the lookup of user names. This session is affected by the tag that sets the UAL idle time out (UAL_IDLE_TIMEOUT) in the general.cfg file. If the portal daemon is running and UAL_IDLE_TIMEOUT has been set, the daemon will stop if no user signs on to Web Client 6.0 within the timeout period. You will then need to restart the portal daemon manually. Increase the value of UAL_IDLE_TIMEOUT in general.cfg if necessary, or alternatively edit the configuration file for the user specified as PORTAL-USER in the ~/openmail/sys/user.cfg directory, to add the tag UAL_IDLE_TIMEOUT with the desired value. CR: JAGac39969 SR: 8606124586 ------------------------------- This patch installs new omrouter, omdirex, omdump and setup binaries into the notes.inst directory under the Openmail binaries directory tree. To complete the installation, it is necessary to run the appropriate copy of the setup program for your platform as documented in the original Openmail Lotus Notes Gateway installation instructions. It is only necessary to setup the binaries & messcats if setup has been run before on the Domino installation, although running the full setup will not cause any harm. ================================================= PHSS_20012: ================================================= CR: JAGab32576 SR: D500419564 ------------------------------- A new general.cfg option has been added which affects how the POP3 and IMAP treat filenames in MIME messages : BRW_ITEMSUB_IS_FNAME The defualt value of this is "TRUE". This means that the preference order for choosing a candidate "filename=" value for the Content-Disposition line for a body part is now : 1. Based on the T61 subject if BRW_T61_ITEMSUB_IS_FNAME is set. 2. The basename of any Original filename 3. Based on the subject if BRW_ITEMSUB_IS_FNAME is TRUE (or not set) 4. Nothing. CR: JAGab34141 SR: 1653304451 ------------------------------- Added Tweak DS_MOD_NOENTRY_TO_ADD If Set to TRUE, when DirSync Server recevies a MODIFY Request on an Entry Not-Existing, DirSync Server Adds the Entry. MODIFY Fails, if tweak is set to FALSE. Default = FALSE. Need to ReStart DirSync Service for the new behaviour CR: JAGab34164 SR: 1653307249 ------------------------------- Added Tweak XP_USE_INTERNAL_DL If Set to TRUE, xport.in , while decoding a doubly wrapped message will use the Internal DL, inplace of the External DL. CR: JAGab37437 SR: D500420604 ------------------------------- A new general.cfg option has been added which affects how the internet Gateway treats filenames in MIME messages : UXO_ITEMSUB_IS_FNAME The default value of this is "FALSE". This means that the preference order for choosing a candidate "filename=" value for the Content-Disposition line for a body part is now : 1. Based on the T61 subject if UXO_T61_ITEMSUB_IS_FNAME is set. 2. The basename of any Original filename 3. Based on the subject if UXO_ITEMSUB_IS_FNAME is TRUE 4. Nothing. CR: JAGab39209 SR: 8606100833 ------------------------------- To configure the Outgoing Mail Gateway so that only X400 attributes are used for lookup add the following line to general.cfg : INET_USE_X400_ATTS_FOR_LOOKUP=TRUE Note the default behaviour will change in versions of OpenMail later than B.06.00 CR: JAGab52686 SR: 8606101484 ------------------------------- To let the fix take effect, you need to set CCS_SINGLE_ESC_UNIT=TRUE in general.cfg CR: JAGab69581 SR: 8606103183 ------------------------------- A new general.cfg option has been added which affects how the internet Gateway, and the Pop3 and IMAP4 clients treat filenames for inline items in MIME messages : INET_INLINE_FNAME_ALLOWED The default value is "TRUE". If the value is "FALSE", body parts with Content-Disposition "inline" will not have a "filename" specified. CR: JAGab70399 SR: 8606103536 ------------------------------- To configure the Outgoing Internet Mail Gateway so that the OpenMail message Creator is made the "Return-Path" recipient (this is the "MAIL FROM " address) and the P2_Originator is made the "From:" recipient, add the following line to general.cfg : UXO_P2_ORIGINATOR_IS_PREFERRED_MAIL_FROM=FALSE CR: JAGab73411 SR: 8606105379 ------------------------------- omaddred has been changed so that it can only be used by OpenMail administrators. ================================================= PHSS_19172: ================================================= CR: JAGab36232 SR: D500428383 ------------------------------- Service Router Viral Cleaning Contact Commitment Request on comitreq@pwd.hp.com for more details. CR: JAGab49811 SR: 8606101415 ------------------------------- For Simple ServiceGuard installations of OpenMail, i.e. those which do not make use of a OMDATADIR/global/config file, setting of a new general.cfg tweak is required if using Outlook Free/Busy time functionality. Set GCL_SIMPLE_SG_PKG_NAME={SG package name} to declare the ServiceGuard package name for OpenMail. This will cause the Directory Relay Server to use the package name rather than the machine's hostname. Note: After setting this tweak, new entries put in the mailnode mapping file (OMDATADIR/sys/mnMapFile) by the Directory Relay Server will refer to this package name rather than a host name. But there may still be old entries which refer to the real machine name. So make sure that all servers have their mnMapFile updated either by running omresetmn, or by manually modifying the entries using ommodmnmp. =========================================================== PHSS_18905: =========================================================== CR: JAGab34063 SR: 1653294579 ------------------------------- To activate this feature, add UX_SPLIT_TNEF=TRUE to general.cfg. The winmail.dat file will then be decoded into attachments, but no object files etc will be created. CR: JAGab34021 SR: 1653287946 ------------------------------- Added Tweak BBS_DELLOG_RETENTION_PERIOD=value Specifies the Retention Period for delete log files. The value need to be defined in hours. Eg: if BBS_DELLOG_RETENTION_PERIOD is set to 10, it means that dellog files are retained for 10 hrs on the system from its creation time. DelLog files help in tracking message re-order in the case of Add/Del. The Retention period need to be defined b/w 1-24 else it is defaulted to 24. Need to ReStart BB Service if new value is added =========================================================== PHSS_18282: =========================================================== CR: JAGab33809 SR: 1653256966 ------------------------------- This patch installs new omrouter and omdirex binaries into the notes.inst directory under the Openmail binaries directory tree. To complete the installation, it is necessary to run the appropriate copy of the setup program for your platform as documented in the original Openmail Lotus Notes Gateway installation instructions. It is only necessary to setup the binaries & messcats if setup has been run before on the Domino installation, although running the full setup will not cause any harm. CR: JAGab34083 SR: 1653297242 ------------------------------- 2 new general.cfg settings are available : BRW_MIME_SPACE_OK_IN_FNAME UXO_MIME_SPACE_OK_IN_FNAME These cause the Pop3 / Imap4 servers and the Internet outgoing gateway to allow filenames inferred from the T.61 subject of a message to contain spaces. CR: JAGab33573 SR: 1653231563 ------------------------------- 2 new general.cfg options are available : AK_ACK_MSG_PRI valid values are : 0 (normal) 1 (non-urgent) and 2 (urgent) Determines the priority to use for acknowledgements if AK_ACK_SAME_PRI isn't set or the priority of the message being acknowledged isn't known. AK_ACK_SAME_PRI This causes the priority of an acknowledgement to be the same as that of the message being acknowledged. Note that under some circumstances, the priority of the message being acknowledged cannot be determined. For instance, clients which assume responsibility for generating acknowledgements and use the "MAIL ACK" UAL command. CR: JAGab34737 SR: 5003448654 ------------------------------- The default behaviour of the service router is changed in this patch. Routable ORNs that do not contain a Surname field are no longer looked up in the directory. To change the behaviour back to the original, set the general.cfg option SR_RESOLVE_IF_NO_PN=TRUE CR: JAGab34968 SR: D500293266 ------------------------------- This patch installs new omdirex binaries into the notes.inst directory under the Openmail binaries directory tree. To complete the installation, it is necessary to run the appropriate copy of the setup program for your platform as documented in the original Openmail Lotus Notes Gateway installation instructions. It is only necessary to setup the binaries & messcats if setup has been run before on the Domino installation, although running the full setup will not cause any harm. CR: JAGab32583 SR: D500427344 ------------------------------- When delete requests for non-existent items are processed an entry is written to file : ~openmail/sys/bb/failed.log Each entry contains the details of the attempted synchronisation request extracted from the synchronisation message's first text body part. CR: JAGab36055 SR: D500421016 ------------------------------- The Omscan program's orphan scanning phase can be temporarily suspended in memory by sending a SIGUSR1 signal to the parent omscan process e.g. kill -s SIGUSR1 ##### where ##### is the parent omscan process (there are 2 processes) It is worth checking STDERR. If "Freeze Signal Ignored" has been written to STDERR, you have either : i. sent the signal to the wrong process ii. omscan.orphans is not at a safe stage to freeze yet - try again later. If "Omscan Freeze Requested" has been written to STDERR, the signal has been noted and omscan will stop at the next convenient point. When that point is reached, "Omscan Frozen" is written to STDERR. To unfreeze omscan : kill -s SIGUSR2 ##### After this, "Omscan Unfrozen" should be written to STDERR. CR: JAGab36230 SR: D500428318 ------------------------------- The following steps should be performed BEFORE the installation of this patch on a VirtualVault system. IGNORE these steps for a non-VirtualVault system. 1. Ensure that you are signed on as the root. 2. Execute the command, /tcb/bin/setlevel -s "system" 3. Delete all the files from the /var/opt/openmail/tmp directory. 4. Execute the command, /sbin/chlevel -L "system" /var/opt/openmail/tmp ---------------------------------------------------------- This patch will need the following minimum disk space requirements: /opt/openmail/patch : 100 MB NOTE: ServiceGuard Installations will need twice this amount. ----------------------------------------------------------