p0.88 misparses 2nd-level message forwarding

[Karl Kleinpaste <karl@justresearch.com>]

1. Send yourself a test message -- normal message, text/plain.
2. Forward that message to yourself -- an inline message/rfc822.
3. Forward *that* message to yourself.
You now have an inline message/rfc822 containing another inline
message/rfc822.

p0.88's display of this will be...confused.

Assuming that you prefix each forwarding with a bit of text/plain as
well, you will see:

        [1. text/plain]
        containing the "outermost" (3rd level) new text.

        [2. message/rfc822]
        containing nothing but (in my case) an X-Sent: header (which BTW
        erroneously duplicates the topmost X-Sent; I sent a bug report
        about this last week).

        [3. text/plain]
        containing the 2nd level text which prefaced the original message
        on 1st forwarding...  *followed by* the entire remaining message
        displayed as text/plain, including both the 2nd level and 1st
        level messages...  all as part of a single "3." section.

        [4. message/rfc822]
        containing the original, 1st level forwarded message.

Note that the innermost, original text is duplicated in both the
3. and 4. sections.

Perhaps significantly, the buttonized (`K b') display of these
sections will show the button areas as
        [1. text/plain] in *bold*
        [2. message/rfc822] in *bold*
        [3. text/plain] in /italic/
        [4. message/rfc822] in *bold*
Shouldn't these be labelled something hierarchical anyway, such as 1., 
2., 2.1, 2.2, 2.2.1?

Something Truly Evil happened to MIME interpretation recently...

--karl