Operating System - OpenVMS
cancel
Showing results for 
Search instead for 
Did you mean: 

MIME Version: V1.93 v. duplicate attachment file names (and so on)

 
Steven Schweda
Honored Contributor

MIME Version: V1.93 v. duplicate attachment file names (and so on)

There I was, trying to use the (lame) MIME
utility ("MIME Version: V1.93") on a VMS V8.3
Alpha system, to deal with an ill-formed e-mail
message which contained several attachments
with the same file name. For example:

MIME> list
Message Headers:
[...]
Attachment: 4
Content-Type: image/jpeg
Content-Disposition: inline;
filename=image.jpeg
Content-Transfer-Encoding: Base64
Attachment: 5
Content-Type: image/jpeg
Content-Disposition: inline;
filename=image.jpeg
Content-Transfer-Encoding: Base64
[...]


The result was multiple versions of the (much
too persistent) "temporary" file,
MIME$202181A6_IMAGE.JPEG;*, and every attempt
to extract any particular attachment got the
last one rather than the desired one
(presumably because it tried to deal with
"MIME$202181A6_IMAGE.JPEG" every time).


While I'm here, has anyone tried to get MIME to
extract an attachment into a file with a
lower-case name? I got results like these:

MIME> ext /att = 22 fred22.jpg
%MIME-I-SAVEFILE, saving file . . .
FRED22.JPG

MIME> ext /att = 22 "fred22.jpg"
%MIME-I-FILENAMMOD, file name modified; File =
_fred22.jpg_
%MIME-I-SAVEFILE, saving file . . .
_fred22.jpg_

Is this POS as bad as I think it is, or am I
missing something obvious (again)?