Handling attached .eml files

[Gary Johnson <garyjohn@xxxxxxxxxxxxxxx>]

(Sigh.)  I just received a message containing a forwarded message as 
an attached .eml file.  Mutt doesn't seem to know what to do with
it.  Here is the message structure and relevant headers.

   From somebody@xxxxxxxxxxxxx  Fri Mar  7 15:13:30 2008
   ...
   MIME-Version: 1.0
   Content-Type: multipart/mixed; 
           boundary=----_SmarterMail_NextPart_6375165417771275
   Date: Fri, 7 Mar 2008 15:13:11 -0800
   Subject: fw: [Fwd: ...]
   From: "Some Body" <somebody@xxxxxxxxxxxxx>
   To: <me@xxxxxxxx>
   Cc: 
   Message-ID: <aef343d15cd54ea1aeeaff9d19508b07@xxxxxxxxxxxxxxxxxxxx>

   This is a multi-part message in MIME format.

   ------_SmarterMail_NextPart_6375165417771275
   Content-Type: text/plain;
           charset=iso-8859-1
   Content-Transfer-Encoding: quoted-printable

   Bla bla bla.=0D=
   =0AOriginal message attached. 

   ------_SmarterMail_NextPart_6375165417771275
   Content-Type: application/octet-stream;
           name="original message.eml"
   Content-Disposition: attachment; filename="Original Message.eml"
   Content-Transfer-Encoding: base64

   UmV0dXJuLVBhdGg6IDxqcGl0dG1vbkBnbWFpbC5jb20+DQpSZWNlaXZlZDogZnJvbSBweS1vdXQt
   ...
   L2h0bWw+DQoNCi0tLS0tLS0tLS0tLS0tMDMwNzA2MDkwMTAyMDIwNjAyMDMwNjA4LS0NCg==
   ------_SmarterMail_NextPart_6375165417771275--

When I open the message from mutt's index view, the pager displays
the text/plain part just fine, but shows the attachment as

   [-- application/octet-stream is unsupported (use 'v' to view this part) --]

The attachment menu shows the message as

     I     1 <no description>           [text/plain, quoted, iso-8859-1, 0.1K]
     A     2 Original Message.eml            [applica/octet-stre, base64, 33K]

When I open the .eml attachment, mutt shows me the contents after
base64 decoding, but otherwise unformatted.  If I save that
attachment, add a phoney mbox "From " header to the top, and open
that file with mutt, I see the original message properly formatted,
and see this in the attachment menu:

     I     1 <no description>                  [multipa/alternativ, 7bit, 22K]
     I     2 |-><no description>          [text/plain, 7bit, iso-8859-1, 7.0K]
     I     3 `-><no description>            [text/html, 7bit, iso-8859-1, 15K]

I realize that the forwarded message should have been sent as
Content-Type message/rfc822, but I don't have control over that.

I can edit the content-type using ^E from the attachment menu,
change it to message/rfc822, and then view one of the alternative
parts in the pager and from the attachment menu, but I can't get to
the other attachment type.  In particular, I can't view the
text/html part in a browser.  Even if I press ^V on the attachment
in the attachment menu, I see only this:

     I     1 <no description>           [text/plain, quoted, iso-8859-1, 0.1K]
     A     2 Original Message.eml                [message/rfc822, base64, 33K]
     I     3 `-><no description>             [text/plain, 7bit, us-ascii, 33K]

I would normally add rules to my .mime.types and mailcap to handle
oddball attachments, but this really shouldn't be handled by an
external viewer, it needs to be handled by something that
understands MIME and RFC822 attachments recursively, that is, mutt
itself.

So my questions are:

1.  For right now, how do I get mutt to display these sorts of
    forwarded messages?

2.  In the long term, should mutt able to handle these sorts of
    forwarded messages?  If so, what needs to be done to make this
    Just Work?

3.  Is the sender's e-mail client broken, or is this method of
    forwarding messages acceptable?  (I know that's a loaded term.)

Regards,
Gary