Re: Un-MIMEified MIME message

[Shane Holder <holder@rsn.hp.com>]

>>>>> "Kai" == Kai Grossjohann <Kai.Grossjohann@CS.Uni-Dortmund.DE> writes:

  Kai> Shane Holder <holder@rsn.hp.com> writes:
  >> I've got a message that pgnus doesn't seem to want to MIMEify
  >> (buttonize).  From reading the manual it seems that there isn't really 
  >> anything that needs to be done for pgnus to do mime other than hit
  >> M-t, am I correct?

  Kai> Hm.  Buttonizing and MIMEification are two different things.
  Kai> You can get at the original message with C-u g.  Buttonization
  Kai> means that buttons are displayed for all parts.  The default
  Kai> behavior is to not display buttons for inline parts.

I guess I don't understand how buttonization differs from
MIMEification.  I expected buttonization to be Gnus' way of saying
"Hey I understand this and here's a button to show you what I can do
with it." 

Under Gnus 5.x and TM, it would buttonize the attachment but I
couldn't extract it.

Here are the headers with content deleted.  The First Content-Type: is
from the mail header, the rest are in the body.

> Content-Type: multipart/mixed; boundary="openmail-part-1ca8043e-00000001"
> 
> --openmail-part-1ca8043e-00000001
> Date: Tue, 23 Feb 1999 14:29:50 -0500
> Content-Type: message/rfc822
> 
> Subject: FW: the acne game
> MIME-Version: 1.0
> From: <deleted>
> TO: <deleted
> Content-Type: multipart/Mixed; boundary="openmail-part-1ca8043e-00000002"
> 
> 
> --openmail-part-1ca8043e-00000002
> Content-Type: application/octet-stream; name="1.txt"
> Content-Disposition: attachment; filename="1.txt"
> Content-Transfer-Encoding: base64
> 
> UmVjZWl2ZWQ6IGZyb20gYXRscmVsMS5ocC5jb20gKGF0bHJlbDEuaHAuY29tIFsxNS4xMC4x
> NzYuMTBdKSBieSBpMzEyNW9tMy5hdGwuaHAuY29tIHdpdGggRVNNVFAgKDguOC42IChQSE5F
> [...]
> ZW50LVR5cGU6IG11bHRpcGFydC9taXhlZDsKCWJvdW5kYXJ5PSItLS0tXz1fTmV4dFBhcnRf
> MDAwXzAxQkU1RjRBLjUzN0RGRjVDIgo=
> 
> --openmail-part-1ca8043e-00000002
> Content-Type: text/plain;charset="iso-8859-1"
> Content-Disposition: inline; filename="FW:"
> Content-Transfer-Encoding: 7bit
> 
> <stuff deleted>
> 
> --openmail-part-1ca8043e-00000002
> Content-Type: application/octet-stream; name="acne.exe"
> Content-Disposition: attachment; filename="acne.exe"
> Content-Transfer-Encoding: base64
> 
> TVqiAAEAAAAEABEA//8HAAABZUAAAAAAQAAAAAEAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
> AAAAAAAAsAAAAOhTAFRoaXMgcHJvZ3JhbSByZXF1aXJlcyBNaWNyb3NvZnQgV2luZG93cy4N
> [...]
> VUhUAAAAAE1VSFQAAAAATVVIVAAAAABNVUhUAAAAAE1VSFQAAAAATVVIVAAAAABNVUhUAAAA
> AD6/CwA=
> 
> --openmail-part-1ca8043e-00000002
> Content-Type: text/plain
> Content-Transfer-Encoding: quoted-printable
> 
> FROM: <deleted>
> TO: <deleted>
> 
> --openmail-part-1ca8043e-00000002
> Content-Type: text/plain
> Content-Transfer-Encoding: quoted-printable
> 
> TO: <deleted>
> 
> --openmail-part-1ca8043e-00000002--
> 
> --openmail-part-1ca8043e-00000001--


When I M-t the message I get one button up at the very top
[1. message/rfc822]. This is coming through HP's Openmail system
interfaced by CC:Mail, so it could be inserting foobar'd headers.  But
I don't speak enough MIME to tell.

Shane