Re: pgnus-0.77 bug in forwarding mime messages

[lantz moore <lmoore@contigo.com>]

>>>>> "Lars" == Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

Lars> lantz moore <lantzm@contigo.com> writes:
>> then i forwarded said message to myself.  the resulting message didn't
>> turn out quite like i expected.  neither gnus nor metamail could
>> decipher the mime components of the original message.  all the '=' in
>> the original message were encoded to =3D (which seems resonable, i
>> guess).

Lars> Hm.  Sounds like something qp-encododed the message.  Did the
Lars> headers say something about Content-Transfer-Encoding or the like?

the headers on the part are:
Content-Type: message/rfc822
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

mm-encode.el is definitely qp-encododing the message/rfc822 part on
purpose.

from mm-encode.el
(defvar mm-content-transfer-encoding-defaults
  '(("text/.*" quoted-printable)
    ("message/rfc822" quoted-printable)
    ("application/emacs-lisp" 8bit)
    ("application/x-patch" 8bit)
    (".*" base64))
  "Alist of regexps that match MIME types and their encodings.")

i changed the message/rfc822 from quoted-printable to 8bit in the alist
and forwarded the message to myself again.  using 8bit, things worked like
you would think that they would, ie, both gnus and metamail were able to
render the message.  but i still don't see what problem the
quoted-printable content-transfer-encoding is causing.

you should be able to reproduce this yourself by sending yourself a gif
and then forwarding that message back to yourself...  (pgnus-0.77).

on a somewhat related point, why do we need to qp-encode text/.* and
message/rfc822?  shouldn't we really only have to quote an occurance of
the boundary in the message text (which is quite unlikey anyway)?  just
curious.

-l