Re: GIF/jpeg attached as quoted-printable in MIME?

[Toby Speight <Toby.Speight@streapadair.freeserve.co.uk>]

Johan> Johan Kullstam <URL:mailto:kullstam@ne.mediaone.net>

0> In article <m2r9jle47q.fsf@sophia.axel.nom>, Johan wrote:

Johan> the qp-or-base64 choser function has been bogus in 0.9[56].  in
Johan> 0.96 it would choose quoted-printable for all long attachments.
Johan> since the chooser should now be fixed, these kinds of image
Johan> sent with quoted-printable problems should go away.

I hope people haven't been put off by the chooser bugs in 0.96; I
think that the principle is sound.  There have been two recent patches
to this, including one that eliminates the use of floating-point maths
in the calculation.


Johan> however, this doesn't mean we ought not fix quoted-printable in
Johan> the first place.

I have a concern about whether we do the Right Thing with newlines in
quoted-printable.  In text parts, newlines must also have carriage
returns; the q-p body will have CRs too, so newlines need not be
encoded.  In non-text parts, newlines must not (in general) have CRs
added - except those introduced by the QP-encoding.  So "foo\nbar" in
a non-text part should become "foo=0Abar" or "foo=0a=\nbar".

Do we canonicalise text EOLs before applying the encoding?  And do we
encode naked LFs?