ECO NUMBER: ALPMAIL02_062 PRODUCT: OpenVMS Alpha OPERATING SYSTEM 6.2 UPDATE PRODUCT: OpenVMS Alpha OPERATING SYSTEM 6.2 COVER LETTER 1 KIT NAME: ALPMAIL02_062 2 KITS SUPERSEDED BY THIS KIT: ALPMAIL01_062 3 KIT DESCRIPTION: 3.1 Version(s) of OpenVMS to which this kit may be applied: OpenVMS Alpha V6.2, V6.2-1H1, V6.2-1H2, V6.2-1H3 3.2 In order to receive the full fixes listed in this kit the following remedial kits also need to be installed: None 3.3 Files patched or replaced: o [SYSEXE]MAIL.EXE (new image) o [SYSLIB]MAILSHR.EXE (new image) o [SYSLIB]MAILSHRP.EXE (new image) o [SYSEXE]MAIL_SERVER.EXE (new image) 4 PROBLEMS ADDRESSED IN ALPMAIL02_062 KIT o Sending a mail message to a large distribution list (between 200 to 700 local users) intermittently signals a nonfatal SSRVEXCEPTN bugcheck for the sending process. 5 PROBLEMS ADDRESSED IN ALPMAIL01_062 KIT o In the event of an error opening or reading SYSUAF.DAT, and a subsequent continuation or unwind request, the protected image's condition handler must place the condition value in the mechanism array. If this does not occur, SIGNAL returns an undefined value, the error does not get passed back to the user -- COVER LETTER -- Page 2 7 January 1998 mode code, and MAIL attempts to continue. o One of the privileged code condition handlers expects the address of the privileged context block in the enable vector when it is invoked. It then attempts to store the signal arguments at an offset within that context block. However, under certain circumstances, the address of the privileged context is zero when a UAF record locked condition is being handled. The ACCVIO occurs because the offset for the signal arguments within the context block is invalid. o When calling MAIL$MAILFILE_PURGE_WASTE from a detached process, the image was aborting with a LIB$_NOCLI message. o Programs using callable MAIL routines from AST level code will often receive ACCVIOs when RMS errors are signaled. o Strange characters are displayed in DIR command when a user has no mail messages and no folders. o A program using callable mail routine MAIL$USER_GET_INFO will receive an EXEC mode access violation and the process is deleted. A non-fatal SSRVEXCEPTN bugcheck is generated. o A program using callable mail routine MAIL$USER_GET_INFO will receive an EXEC mode access violation and the process is deleted when the MAIL$_USER_NEXT item code is used before MAIL$_USER_FIRST or MAIL$_USER_USERNAME. A non-fatal SSRVEXCEPTN bugcheck is generated. o Two SSRVEXCEPTION crashes in MAILSHRP when running LBN disk I/O or UETP, in the context of the image DTWM. o When using callable mail to send messages, it will eventually run out of virtual memory. There is a memory leak in both MAIL$SEND_BEGIN and MAIL$SEND_END routines. o Defining a Logical for Username in the following manner produces Forward Loop in MAIL. $DEFINE/TRANSLATION_ATTRIB=TERMINAL name node::name eg. $ define/tran=terminal system quebit::system MAIL> send To: system %MAIL-E-FORWLOOP, infinite forwarding detected sending to user netaly o The TO line in a received message can become so skewed that passwords for remote distribution lists may be visible in a received message. -- COVER LETTER -- Page 3 7 January 1998 o When sending mail to a REMOTE and LOCAL user of the same name, and the send to the REMOTE recipient-name fails, the mail message is NOT sent to the LOCAL recipient-name either. However, other recipient names listed receive the mail. o When a mail message is sent and the TO: field incorporates a set of quotes, and the TO: field/addressee is incorrect, there is no error message returned. o A VAX C application that uses the MAIL$ callable API runs for varied lengths of time, then crashes due to insufficient virtual memory. o When using MAIL$MESSAGE_COPY to copy messages from one mail file to another version of the same file, the messages are not copied to the target file, but rather are copied to the source file. o Depending on DECnet Plus namespace configuration, appearance of MAIL> prompt can be very slow 6 KIT INSTALLATION RATING: The following kit installation rating, based upon current CLD information, is provided to serve as a guide as to which customers should apply this remedial kit. (Reference attached Disclaimer of Warranty and Limitation of Liability Statement) INSTALLATION RATING: INSTALL_3 : To be installed by customers experiencing the problems corrected. 7 INSTALLATION INSTRUCTIONS: Install this kit with the VMSINSTAL utility by logging into the SYSTEM account, and typing the following at the DCL prompt: @SYS$UPDATE:VMSINSTAL ALPMAIL02_062 [location of the saveset] The saveset location may be a tape drive, or a disk directory that contains the kit saveset. No reboot is necessary after successful installation of this kit. If you have other nodes in your VMScluster, they should be rebooted or install this kit in each system in order to make use of the new image(s). -- COVER LETTER -- Page 4 7 January 1998 Copyright (c) Digital Equipment Corporation, 1998 All Rights Reserved. Unpublished rights reserved under the copyright laws of the United States. The software contained on this media is proprietary to and embodies the confidential technology of Digital Equipment Corporation. Possession, use, or dissemination of the software and media is authorized only pursuant to a valid written license from Digital Equipment Corporation. DISCLAIMER OF WARRANTY AND LIMITATION OF LIABILITY THIS PATCH IS PROVIDED AS IS, WITHOUT WARRANTY OF ANY KIND. ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR PARTICULAR PURPOSE, OR NON-INFRINGEMENT, ARE HEREBY EXCLUDED TO THE EXTENT PERMITTED BY APPLICABLE LAW. IN NO EVENT WILL DIGITAL BE LIABLE FOR ANY LOST REVENUE OR PROFIT, OR FOR SPECIAL, INDIRECT, CONSEQUENTIAL, INCIDENTAL OR PUNITIVE DAMAGES, HOWEVER CAUSED AND REGARDLESS OF THE THEORY OF LIABILITY, WITH RESPECT TO ANY PATCH MADE AVAILABLE HERE OR TO THE USE OF SUCH PATCH.