On Wed, Jul 21, 2004 at 06:40:47PM -0700, Dan Quinlan wrote: > I think this is exactly what we do right now, so no problem. We might > want to double check some common MUAs to make sure they do actually decode > lowercase hex, though.
Yeah, and I'm pretty sure we did. I didn't know QP required uppercase, thanks for the reference. As for what we do, 3.0 only decodes parts that specify their encoding. 2.6 wasn't quite as precise (for instance, it didn't deal with messages that had both base64 and qp parts...) BTW, the lowercase thing was added: r6615 | jm | 2004-02-11 02:17:40 -0500 (Wed, 11 Feb 2004) | 1 line QP decoding should deal with lowercase QP as well I assume we did our standard MUA tests and found lowercase is decoded. A quick check now shows it is decoded on: Mutt Exchange (webmail) Apple Mail Since Exchange does it, I assume OE and O will do it too. I don't have access to a box with those installed right now though. > One thing I think you said did give me pause. I'm pretty sure that: > > (in a quoted-printable part) > http://penistone=3D2eopoloveok=3D2ecom/3/ > > should only decode to > > http://penistone=2eopoloveok=2ecom/3/ > > No more than that. I believe that is correct, yes. And that's as far as we go in 3.0 (if I replace the = with =3D): http://penistone=2eopoloveok=2ecom/3/ -- Randomly Generated Tagline: "the curls in your keyboard cord are losing electricity." - Today's BOFH Excuse
pgpttVGYjbJbh.pgp
Description: PGP signature
