ECO NUMBER: VMS721H1_MAIL-V0300 PRODUCT: OpenVMS Alpha OPERATING SYSTEM V7.2-1H1 UPDATE PRODUCT: OpenVMS Alpha OPERATING SYSTEM V7.2-1H1 COVER LETTER 1 KIT NAME: VMS721H1_MAIL-V0300. 2 KITS SUPERSEDED BY THIS KIT: VMS721H1_MAIL-V0200. 3 KIT DEPENDENCIES: 3.1 The following remedial kit(s), or later, must be installed BEFORE installation of this, or any required kit: VMS721H1_UPDATE-V0400. 3.2 In order to receive all the corrections listed in this kit, the following remedial kits, or later, should also be installed: None. 4 KIT DESCRIPTION: 4.1 Version(s) of OpenVMS to which this kit may be applied: OpenVMS Alpha V7.2-1H1. 4.2 Files patched or replaced: o [SYSLIB]MAILSHR.EXE (new image) o [SYSLIB]MAILSHRP.EXE (new image) o [SYSEXE]MAIL_SERVER.EXE (new image) o [SYSEXE]MAIL.EXE (new image) 5 PROBLEMS ADDRESSED IN VMS721H1_MAIL-V0300 KIT o MAILSHR.EXE needs to be installed before MAIL.EXE is installed. This was not being done. -- COVER LETTER -- Page 2 3 January 2002 Images Affected: - [SYSLIB]MAILSHR.EXE 6 PROBLEMS ADDRESSED IN VMS721H1_MAIL-V0200 KIT o After installation of the VMS721H1_MAIL-V0100 ECO kit, the MAILSHR.EXE image has the wrong file protection. The protection is (RWED,RWED,RE,), it should be (RWED,RWED,RE,RE). This could cause some TCP/IP services to fail. Images Affected: - [SYSLIB]MAILSHR.EXE 7 PROBLEMS ADDRESSED IN VMS721H1_MAIL-V0100 KIT o If a username logical is defined using /TRANSLATION=TERMINAL, sending a mail message to that person will fail with a "%MAIL-E-NOSUCHUSR, no such user logical_name" error. See example below: $ define/translation=terminal js john_smith On a Alpha V6.1 platform: $ mail MAIL> send To: js Subject: On a Alpha V7.1-2 platform: $ mail MAIL> send To: js %MAIL-E-NOSUCHUSR, no such user JS Images Affected: - [SYSEXE]MAIL.EXE o After a COMPRESS command fails, subsequent mail commands cannot be processed. See example below: MAIL> compress %MAIL-E-NOFILEOPEN, no mail file open MAIL> dir -- COVER LETTER -- Page 3 3 January 2002 %MAIL-E-NOFILEOPEN, no mail file open MAIL> read %MAIL-E-NOFILEOPEN, no mail file open %MAIL-E-NOMSGS, no messages MAIL> sel A %MAIL-E-NOFILEOPEN, no mail file open MAIL> exit %MAIL-E-NOFILEOPEN, no mail file open %MAIL-E-NOFILEOPEN, no mail file open ETOSHA> Images Affected: - [SYSEXE]MAIL.EXE o If a message line containing an embedded NULL character was extracted to a file, the message line was truncated at the NULL character. example message: 111111111111111111111111111111 111111111111^@1111111111111111 111111111111111111111111111111 Extract results in output file: 111111111111111111111111111111 111111111111111111111111111111 111111111111111111111111111111 Images Affected: - [SYSEXE]MAIL.EXE o Using callable mail routines over a period of time may fail with '%LIB-F-INSVIRMEM, insufficient virtual memory'. Callable Mail allocates free memory space, but does not return all of it. Images Affected: - [SYSLIB]MAILSHR.EXE o Attempting to DEFINE/KEY function keys F6 thru F14 fails without an error message; the newly defined key will not function. -- COVER LETTER -- Page 4 3 January 2002 Images Affected: - [SYSEXE]MAIL.EXE o The statistics returned in a call to MAIL$MAILFILE_PURGE_WASTE are incorrect. The MAIL$_MAILFILE_TOTAL_RECLAIM and MAIL$_MAILFILE_DATA_RECLAIM item codes to the MAIL$MAILFILE_PURGE_WASTE callable mail routine always return identical values. Further, the value returned when using the item code MAIL$MAILFILE_DELETED_BYTES is always 0. The OpenVMS documentation states that this field returns the number of bytes deleted from a mail file. See example below: %MAIL-I-RECLPLSWAIT, reclaiming deleted file space. Please wait... Data buckets reclaimed: [6] Number of data buckets scanned: [7] Number of index buckets reclaimed [0] Number of deleted bytes: [0] Number of messages deleted: [68] Number of bytes reclaimed: [6] Images Affected: - [SYSLIB]MAILSHR.EXE o If a user is in Mail and issues a SET FILE command for a different Mail subdirectory. Mail ignores the command. See the example below: PROMPT> mail MAIL> sho ver Mail V1.0 MAIL> sho file Your current mail file is SYS$SYSROOT:[SYSMGR]MAIL.MAI. MAIL> set file SYS$SYSDEVICE:[BAT.MAIL] MAIL> dir/fol Listing of folders in SYS$SYSROOT:[SYSMGR]MAIL.MAI Press CTRL/C to cancel listing MAIL MAIL> sho file Your current mail file is SYS$SYSROOT:[SYSMGR]MAIL.MAI. MAIL> exit Images Affected: -- COVER LETTER -- Page 5 3 January 2002 - [SYSEXE]MAIL.EXE o Errors can occur when copying a Mail folder from one file to another. Not all of the files may be copied and no error message is displayed. See the example below: MAIL> sel "MAIL-nov-1998" %MAIL-I-SELECTED, 3121 messages selected MAIL> sel/sinc=01-jan-80 %MAIL-I-SELECTED, 3121 messages selected MAIL> copy/all "MAIL-nov-1998" dua3:[mpiati] MAIL> set file dua3:[mpiati] MAIL> sel "MAIL-nov-1998" %MAIL-I-SELECTED, 169 messages selected Images Affected: - [SYSLIB]MAILSHR.EXE o The DATE in the header of a message is omitted from extracted messages. Images Affected: - [SYSEXE]MAIL.EXE o When a new message arrives and the mail file in use is not the default, the READ/NEW command does not close the current mail file and open the default mail file. An explicit SET FILE command to the default mail file must be executed before the READ/NEW command is issued. Further, the new messages remain in the NEWMAIL folder. Images Affected: - [SYSEXE]MAIL.EXE o UCX$SMTP_MAILSHR.EXE fails with an 'ACCVIO, access violation' when sending a mail message with a record greater than 1,000 bytes. Images Affected: -- COVER LETTER -- Page 6 3 January 2002 - [SYSLIB]MAILSHR.EXE o The SEND/LAST command fails to include the text from the previous mail message when MAIL is invoked with MAIL/EDIT. This only occurs when the /EDIT qualifier is used without the MAIL DCL command. Images Affected: - [SYSEXE]MAIL.EXE o Sending mail from VMSMAIL to Microsoft Exchange mail using TCP/IP merges the To: and CC: lines to one To: line in the received message. See example below: MAIL> Send/CC To: SMTP%"A.B@C.COM" CC: SMTP%"D.E@F.COM" The To: line in Exchange: To: A.B@C.COM,D.E@F.COM Images Affected: - [SYSEXE]MAIL.EXE - [SYSLIB]MAILSHR.EXE o OVMS Mail does not filter out the character on the header fields, i.e., From:, To:, CC: and Subj: strings. In some instances, a mail message could be received with a type of VT Escape Sequence that could modify the behavior of a user's terminal; the potential would be to render the terminal unusable. Images Affected: - [SYSEXE]MAIL.EXE o An %MAIL-E-ALTPRIJOB error message displays without cause. See example below: $ MAIL MAIL> 22 (Message #22 is displayed) MAIL> print MAIL> 5 -- COVER LETTER -- Page 7 3 January 2002 (Message #5 is displayed) MAIL> print/queue=32$lb2a %MAIL-E-ALTPRIJOB, error altering parameters of job 505 queue 32$LB2A Job MAIL (queue 34$LB4L, entry 505) started on 34$LB4L MAIL> exit $ In this example, print queue 34$LB4L is the default print queue in the user's MAIL profile. This error is benign because the print job eventually is released to the printer (32$LB2A in the example above), even though the user is not notified. Images Affected: - [SYSEXE]MAIL.EXE 8 KIT INSTALLATION RATING: The following kit installation rating, based upon current CLD information, is provided to serve as a guide 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. 9 INSTALLATION INSTRUCTIONS: Install this kit with the POLYCENTER Software installation utility by logging into the SYSTEM account, and typing the following at the DCL prompt: PRODUCT INSTALL VMS721H1_MAIL /SOURCE=[location of Kit] The kit location may be a tape drive, CD, or a disk directory that contains the kit. Additional help on installing PCSI kits can be found by typing HELP PRODUCT INSTALL at the system prompt No reboot is necessary after successful installation of the kit. -- COVER LETTER -- Page 8 3 January 2002 9.1 Special Installation Instructions: 9.1.1 Scripting of Answers to Installation Questions During installation, this kit will ask and require user response to several questions. If you wish to automate the installation of this kit and avoid having to provide responses to these questions, you must create a DCL command procedure that includes the following definitions and commands: - $ DEFINE/SYS NO_ASK$BACKUP TRUE - Add the following qualifiers to the PRODUCT INSTALL command and add that command to the DCL procedure. /PROD=DEC/BASE=AXPVMS/VER=V3.0 - De-assign the logicals assigned For example, a sample command file to install the VMS721_MAIL-V0300 kit would be: $ $ DEFINE/SYS NO_ASK$BACKUP TRUE $ DEFINE/SYS NO_ASK$REBOOT TRUE $! $ PROD INSTALL VMS721_MAIL/PROD=DEC/BASE=AXPVMS/VER=V3.0 $! $ DEASSIGN/SYS NO_ASK$BACKUP $! $ exit Copyright (c) Compaq Computer Corporation, 2002 All Rights Reserved. Unpublished rights reserved under the copyright laws of the United States. COMPAQ, the Compaq logo, VAX, Alpha, VMS, and OpenVMS are registered in the U.S. Patent and Trademark Office. All other product names mentioned herein may be trademarks of their respective companies. Confidential computer software. Valid license from Compaq required for possession, use, or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. Compaq shall not be liable for technical or editorial errors or omissions contained herein. The information in this document is provided as is without warranty of any kind and is subject to change without notice. The warranties for Compaq products are set forth in the express limited warranty statements accompanying such products. Nothing herein should be construed as constituting an additional warranty. -- COVER LETTER -- Page 9 3 January 2002 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 COMPAQ 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.