Updated: 24-SEP-2003 (Use your browsers' Reload button to ensure you're viewing the most recent version)
VAXMIME01_073 MIME Fixes ECO Summary
*OpenVMS] VAXMIME01_073 MIME Fixes ECO Summary
New Kit Date: 15-OCT-2002
Modification Date: Not Applicable
Modification Type: NEW KIT
Copyright (c) Compaq Computer Corporation 2002. All rights reserved.
OP/SYS: OpenVMS VAX
COMPONENT: MIME
SOURCE: Compaq Computer Corporation
ECO INFORMATION:
ECO Kit Name: VAXMIME01_073
ECO Kits Superseded by This ECO Kit: None
ECO Kit Approximate Size: 306 Blocks
Kit Applies To: OpenVMS VAX V7.3
System/Cluster Reboot Necessary: No
Rolling Re-boot Supported: Not Applicable
Installation Rating: INSTALL_3
3 - To be installed by customers experiencing the problems
corrected.
Kit Dependencies:
The following remedial kit(s) must be installed BEFORE
installation of this kit:
None
In order to receive all the corrections listed in this
kit, the following remedial kits should also be installed:
None
ECO KIT SUMMARY:
An ECO kit exists for MIME on OpenVMS VAX V7.3. This kit addresses the
following problems:
PROBLEMS ADDRESSED IN VAXMIME01_073 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.
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
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.
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.
Images Affected:[SYSEXE]MIME.EXE
[SYSHLP]MIME$HELP.HLB
RELATED ARTICLES:
Detailed articles describing the problems listed above may exist in
the OPENVMS database. To view these articles, open the appropriate
product database and perform a query using either of the following
search strings: 'VAXMIME01_073' or 'VAXMIME'.
ECO KIT ORDERING INSTRUCTIONS:
If after an evaluation you wish to obtain this kit, request it
electronically using the appropriate Advanced Electronic Services
(AES) Service Tool. If you are not familiar with how to request
kits electronically, open the DIA, WIS or DSNLINK database and
review the article entitled:
[AES] How To Electronically Request ECO Kits Using Service Tools
INSTALLATION NOTES:
No reboot is necessary after successful installation of the kit.
Install this kit with the VMSINSTAL utility by logging into the
SYSTEM account, and typing the following at the DCL prompt:
@SYS$UPDATE:VMSINSTAL VAXMIME01_073 [location of the saveset]
The saveset location may be a tape drive, CD, or a disk directory
that contains the kit saveset.
All trademarks are the property of their respective owners.
==========================================================================
| Table of Kit Image Information |
+----------------------------+----------+-----------------+--------------+
| | Overall | Image File | Image Link |
| Image Name | Checksum | Identification | Date/Time |
+----------------------------+----------+-----------------+--------------+
| MIME.EXE |%X98C9B224| V1.6 | 29-MAR-2002 |
| | | 21:32:47.86 |
+----------------------------+----------+-----------------+--------------+
|
