Re: digests and MIME

[Colin Rafferty <craffert@spspme.ml.com>]

>>>>>> "Steven" == Steven L Baur <steve@miranova.com> writes:
>>>>>> "Colin" == Colin Rafferty <craffert@spspme.ml.com> writes:

Colin> It seems that MIME encoded messages that are read as digests
Colin> are not being decoded before they are split.  I think that they
Colin> should be.

Colin> An example is the FAQ that Steven L. Baur (RIP) just posted.

Steven> I'm not dead yet. It's getting better. :-)

Colin> It is formatted incorrectly if it has not been decoded.

Steven> You're getting it transmogrified into QP I presume?

Yes I am.  See firther down for the relevent headers.

Colin> What do people think?

Steven> A better solution is to bug administrators to fix their news and
Steven> mail relays so they don't make the broken conversion 8bit -> QP.
Steven> I don't think there's a `correct' thing to do when the message
Steven> has been corrupted in that fashion, except perhaps to post the
Steven> FAQ as a MIME digest in the first place.

I have to disagree with this.  Some people will intentionally post
digests as MIME messages, the same way that they would post normal
message as MIME.  We should be able to handle this correctly.

As an example, you posted yours that way.  I received it here through
ding@ifi.  Here are the relevent headers from the message:

FAQ> Sender: steve@deanna.miranova.com
FAQ> Subject: Gnus (Emacs Newsreader) FAQ
FAQ> Message-ID: <m2hgmlphdj.fsf@deanna.miranova.com>
FAQ> Mime-Version: 1.0 (generated by tm-edit 7.94)
FAQ> X-Newsreader: Red Gnus v0.65/XEmacs 19.15
FAQ> Content-Transfer-Encoding: quoted-printable
FAQ> Content-Type: text/plain; charset=ISO-8859-1
FAQ> X-Content-Length: 47855

By the way, you have done a great job with the FAQ.  I think that it
probably should be sent in MIME.  It is just that Gnus should insert the
decoded article into " *gnus digest buffer*" rather than the original
article.

-- 
Colin