On Fri, 14 May 2004 10:51:48 +0200 (Romance Daylight Time) Vadim Zeitlin <[EMAIL PROTECTED]> wrote:
> you're creating a pseudo MIME part for the uuencoded contents, > right? If so, everything should work as expected. Exactly. The only point is that (almost) all the MIME headers of this fake MIME part are empty, but it seems to work correctly nevertheless. I only implemented what I discovered to be necessary. This idea of building a MIME part from some data is also what's necessary to implement decrypting of messages: it's just that the decoding would be done by GPG instead. This should be very easy to do for inline encrypted messages (that can only give back some text or a single file, and I think all the code is already there), but it will probably be a little trickier to handle PGP-MIME encrypted messages, as those do give back a full MIME structure. At this point, the MimePartRaw class that I implemented would probably break (or lack features). > this is a useful feature (even > 10 years after MIME > standardization...) I was quite amazed to receive uuencoded files from a Microsoft Exchange user. I would never have thought of that. I wonder on what criterion Exchange decides between uuencoding and MIME... -- Xavier Nodet "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." - Benjamin Franklin, 1759.
pgp00000.pgp
Description: PGP signature
