Message forwarding annoyance and message-forward-show-mml

[Hrvoje Niksic <hniksic@iskon.hr>]

It seems that the changes to message forwarding in the last months are
going from bad to worse.  We seem to be reliving the early pgnus
nightmare all over again.

So I press `S o m' to forward a relatively complex message.  What do I
get?  A bunch of MML!  No, Virginia, I almost never want Gnus to muck
with the original message -- for one because it's so easy to fuck up
and send garbage.  But even when it doesn't fuck up, I resent the idea
of destructuring a forwarded message to MML only to re-assemble it
again two seconds later without intermediate changes.  In most cases,
I don't want to edit the messages I forward.

Looking for ways to break the legs of "helpful" MML-ification of
forwarded messages, I stumble upon `message-forward-show-mml'.  Great,
said I, setting this to nil will surely make things sensible again.
But what do I get:

    <$part type=message/rfc822 disposition=inline buffer=" *Gnus forward*<3>">
    <$/part>
    (# intentionally transformed to $)

Now I don't even get to *see* the message I'm forwarding.  If it's not
MML, I'm not supposed to see it at all lest I be made into a pillar of
salt by raw MIME.  And I don't even want to know about the "<3>"
following the buffer name.

Could this please be fixed to behave sensibly, specifically so that
pressing `S o m' inserts this:

    <$part type=message/rfc822 disposition=inline>
    ... *raw* message (except for quoting of MML-like keywords ...
    <$/part>

Pretty please?