Re: More on forwarding quoted-printable encoded messages

[Shenghuo ZHU <zsh@cs.rochester.edu>]

>>>>> "Steinar" == Steinar Bang <sb@metis.no> writes:

>> The original message I'm trying to forward has a c-t-e of 8bit.  I'm
>> wondering if things had been different if it had been q-p, but I don't 
>> know how to force a q-p message in the folders, so I don't know how to 
>> test this.

Steinar> I tried that.  If the forwarded message has a c-t-e of
Steinar> base64, and the message/rfc822 part could be safely said to
Steinar> have a c-t-e of 7bit, the forwarded message ends up with 8bit
Steinar> and the message/rfc822 ends up with no q-t-e header.

I don't think that the problem is simply the c-t-e of
message/rfc822. In the current version, the message/rfc822 part is
only charset-decoded (gnus-article-decode-hook). When the message is
sent, the part is re-encoded.  I don't think this is a right solution.
The message/rfc822 part should be unchanged or totally
decoded/re-encoded (mml <-> mime). The former solution is not
acceptable to many users, because those users may want to change the
content. In the latter solution, the c-t-e is not necessary at all.

-- 
Shenghuo