On Tue, 8 Feb 2011 16:00:11 +0100 (CET) Steffen Kaiser <[email protected]> wrote:
> Maybe it was the rfc2231 encoding. In this case you would need to > recode it into a rfc2047 compliant string, IMHO. So one wouldn't need > Encode in MIME::Tools. That's exactly the strategy in my patch. > Couldn't you drop the use of MIME::WordDecoder in Filer, too, and use > anonymous filenames? Unless I am mistaken, only the deprecated > decode() function would use MIME::WordDecoder then. I think that's a good idea. I see no value in obeying the "filename=xxx" parameter. We should generate safe filenames and the caller can (if desired) rename the file afterwards. [...] > In conjuntion with a general purpose function, e.g. unmime() or > Encode::MIME::Header::decode(), to decode a MIME string into a perl > string. > Maybe, this is exactly what you've answered on Sat Feb 05 10:22:28 > 2011. Indeed! Good, so at least 3 of us are on the same page. Regards, David. _______________________________________________ NOTE: If there is a disclaimer or other legal boilerplate in the above message, it is NULL AND VOID. You may ignore it. Visit http://www.mimedefang.org and http://www.roaringpenguin.com MIMEDefang mailing list [email protected] http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
