ECO NUMBER: VMS73_MIME-V0100 PRODUCT: OpenVMS Alpha OPERATING SYSTEM V7.3 UPDATE PRODUCT: OpenVMS Alpha OPERATING SYSTEM V7.3 COVER LETTER 1 KIT NAME: VMS73_MIME-V0100 2 KITS SUPERSEDED BY THIS KIT: None. 3 KIT DEPENDENCIES: 3.1 The following remedial kit(s), or later, must be installed BEFORE installation of this, or any required kit: VMS73_UPDATE-V0100 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.3 4.2 Files patched or replaced: o [SYSEXE]MIME.EXE (new image) o [SYSEXE]MIME$HELP.HLB (new file) 5 PROBLEMS ADDRESSED IN VMS73_MIME-V0100 KIT o Mime message corruption can occur for messages created with OpenVMS Mime that have text of more than just a few lines. Messages appear to be truncated or text may appear garbled or out of context. This happens when the textual message part has a length (when combined with the Mime header area) that exceeds 1024 characters. -- COVER LETTER -- Page 2 4 September 2002 Images Affected: - [SYSEXE]MIME.EXE - SYSHLP]MIME.EXE o Multipart messages created with OpenVMS Mime may cause the error: "Invalid boundary marker" when attempting to read (decode) the message. Images Affected: - [SYSEXE]MIME.EXE - [SYSHLP]MIME$HELP.HLB o The file name (known as the Disposition file name), would be added more than once when multiple edits and saves occur. Images Affected: - [SYSEXE]MIME.EXE - [SYSHLP]MIME$HELP.HLB o A SYSTEM-F-ACCVIO error can occur when a SAVE is performed on a message when a message part has previously been removed. Images Affected: - [SYSEXE]MIME.EXE - [SYSHLP]MIME$HELP.HLB o When the MIME> LIST command is used for a message with only one main part, (a single part message), no attachment number is listed. This may confuse the user as to which attachment number to specify with the EXTRACT command, which requires an attachment number. On-line help has been modified to specify attachment number one for single part messages, as follows: EXTRACT Format: EXTRACT/ATTACHMENT=attachment-number [filename] NOTE: The /ATTACHMENT qualifier is required with EXTRACT. This qualifier specifies the number of the attachment as displayed by the LIST command. In a single part message, no attachment number is displayed. For this case specify -- COVER LETTER -- Page 3 4 September 2002 attachment number one. Images Affected: - [SYSEXE]MIME.EXE - [SYSHLP]MIME$HELP.HLB o Error messages can be overwritten or garbled when errors occur while reading a Mime message. Images Affected: - [SYSEXE]MIME.EXE - [SYSHLP]MIME$HELP.HLB o Problems occur while attempting to EXTRACT, EDIT, or REMOVE message parts due to an improper attachment range check or an illegal range of message part numbers being accepted when actually invalid. Typically the symptom is either the part fails to extract due to an erroneous error, or the incorrect part is extracted, edited, or removed. This may include removal or extraction of non-message parts or non-leaf attachments, such as multipart or multipart alternative parts. Images Affected: - [SYSEXE]MIME.EXE - [SYSHLP]MIME$HELP.HLB o When exiting and prompted to save file, a typographical error would be accepted as a negative response and the file would not be saved. Images Affected: - [SYSEXE]MIME.EXE - [SYSHLP]MIME$HELP.HLB o While reading a message, the screen may be improperly restored which causes the screen output to be displayed improperly. This may happen when returning from a spawned process that provided output to the same screen device, executed commands in DCL that caused errors, and so forth. -- COVER LETTER -- Page 4 4 September 2002 Images Affected: - [SYSEXE]MIME.EXE - [SYSHLP]MIME$HELP.HLB o Other miscellaneous errors and problems that were corrected are: 1. Certain file errors were not being reported or handled properly during opening and editing of a message. 2. Fix regression where multiple SAVEs were not saving the file and only the first save was being written. 3. Code optimization in remove attachment. 4. If an error occurred during ADD, the message would be corrupted (there was no message recovery) 5. Under certain situations a message would not be saved during a SAVE, EXIT, CLOSE, NEW, OPEN, and ^Z operation. 6. Errors would occur while attempting to use the edit command as defined in MIME$MAILCAP.DAT. 7. No support for edit of HTML attachments (Unix-style file name parsing. 8. Errors on, or failure to read plain text due to an erroneous content-type parameter match on text style. 9. Update this version image IDENT, MIME Version and MIME HELP (MIME$HELP.HLB) to V1.7 10. Updated MIME HELP Images Affected: - [SYSEXE]MIME.EXE - [SYSHLP]MIME$HELP.HLB o For a large MIME message (262 Mbyte) comprised of 40 attachments, attachments are not listed properly. Observing the output from the MIME> LIST command and typing Control_S/Q shows the attachments and the filenames. However, manually scrolling back to review attachments and filenames results in a display where attachment numbers and/or most filenames are omitted. In trying to duplicate the problem, other large messages with many attachments did not reproduce the problem. -- COVER LETTER -- Page 5 4 September 2002 Images Affected: - [SYSEXE]MIME.EXE - [SYSHLP]MIME$HELP.HLB 6 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. 7 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 VMS73_MIME /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. 7.1 Special Installation Instructions: 7.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 -- COVER LETTER -- Page 6 4 September 2002 - Add the following qualifiers to the PRODUCT INSTALL command and add that command to the DCL procedure. /PROD=DEC/BASE=AXPVMS/VER=V1.0 - De-assign the logicals assigned For example, a sample command file to install the VMS73_MIME-V0100 kit would be: $ $ DEFINE/SYS NO_ASK$BACKUP TRUE $! $ PROD INSTALL VMS73_MIME/PROD=DEC/BASE=AXPVMS/VER=V1.0 $! $ DEASSIGN/SYS NO_ASK$BACKUP $! $ exit Copyright (c) Compaq Computer Company, 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 are 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. 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.