[7065] in SIPB bug reports
exmh bug: MIME attachments after-the-fact
daemon@ATHENA.MIT.EDU (Kev)
Thu Dec 3 23:38:11 1998
To: bug-sipb@MIT.EDU
Date: Thu, 03 Dec 1998 23:38:03 EST
From: Kev <klmitch@MIT.EDU>
version 2.0.2 2/24/98
SunOS x15-cruise-basselope.mit.edu 5.6 Generic_105181-05 sun4u sparc SUNW,Ultra-5_10
Tk 8.0 Tcl 8.0
Exmh doesn't handle MIME attachments correctly the way I try to do them.
What I do: I begin the text of the message on the line directly below the
line of dashes; when I have completed the first part of the message, I select
'Attach file' from More->Attachment; after selecting the file to attach,
Exmh reformats the message to be MIME compliant--almost. The first line
of the message I have already typed binds with the standard mail headers,
while the line of dashes appears after the MIME part seperator; I have to
manually swap the two lines.
To make what I'm doing a little clearer, here's an example:
-------------------- Begin sample message -------------------------------
To:klmitch@mit.edu
Subject:test message
--------
Line one of the message
Line two of the message
Line four of the message.
-------------------- End sample message ---------------------------------
At this point, I attempt to attach, say, my .zsigs, resulting in:
-------------------- Begin sample message -------------------------------
To:klmitch@mit.edu
Subject:test message
Mime-Version: 1.0
Content-Type: multipart/mixed ;
boundary="==_Exmh_18472125300"
Line one of the message
This is a multipart MIME message.
--==_Exmh_18472125300
Content-Type: text/plain
--------
Line two of the message
Line four of the message.
--==_Exmh_18472125300
Content-Type: text/plain ; name=".zsigs"
Content-Description: .zsigs
Content-Disposition: attachment; filename=".zsigs"
All Glory to God in the Highest!
[snip]
-------------------- End sample message ---------------------------------
I've just verified that this also happens if a blank line appears after the
line of dashes; if I replace the line of dashes with a blank line and
start my message on the next line, the problem occurs again. This seems to
me to be a pretty systematic error...I don't believe my exmh customization
would have any effect on this, but it is publically-readable if it is
needed.
--
Kevin L. Mitchell <klmitch@mit.edu>
------------------------- -. .---- --.. ..- -..- --------------------------
http://web.mit.edu/klmitch/www/ (PGP5 keys availiable from here)
DSS Key ID ED0DB34E: D9BF 0E74 FDCB 43F5 C597 878F 9455 EC24 ED0D B34E
DH Key ID 2A2C31D4: 1A77 4BA5 9E32 14AE 87DA 9FEC 7106 FC62 2A2C 31D4
