Re: Gnus doesn't understand its own message/rfc forwarding

[Steinar Bang <sb@metis.no>]

>>>>> Shenghuo ZHU <zsh@cs.rochester.edu>:

>>>>> "Steinar" == Steinar Bang <sb@metis.no> writes:
>>>>> Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann):
>>> Steinar Bang <sb@metis.no> writes:
>>>> The rfc822 part looks like this at the start:
>>>> [...]
>>>> ie. I don't get to the forwarded message in such a way that I can
>>>> reply to it, and as far as I can remember, this used to be possible.

>>> Can you reply to the (innermost) text part?

Steinar> Nope.  It doesn't show up as a message.  It's not even
Steinar> decoded from q-p when I go down there.

> I did a little change on the forwarding. Could you test your cases?

I have now tested with the forwarded message being both CTE 8bit and
q-p (with US-ASCII) headers, and with the message with CTE 8bit and
RFC2047 headers, and all of them appeared fine in Gnus (no CTE or
charset on the message/rfc822 part and q-p encoding of the message
itself). 

I was able to go to the message by doing C-d, and reply to the
message. 

I've also forwarded a CTE 8bit, charset=iso-8859-1 message ot people
with Outlook98/Outlook2000, reading email through exchange servers,
and they saw the message as a forwarded message is supposed to be
displayed in that program.

Great work!  Thanx! :-)