On Fri, Mar 29, 2002 at 12:04:54PM -0600, Jay Jacobs wrote:
> I just got some spam that had the entire body base64 encoded, it's
> content-type was "multipart/mixed" with one part, the base64, which was
> listed as type "text/html".
>
> Here's what hit:
> PLING,BASE64_ENC_TEXT
>
> I see two big
Yes, there are a number of multipart/mixed loopholes at the moment.
Planning to use MIME::Tools to do some more serious deconstruction on
the messages and their parts in future release. At the moment I'm
actually thinking it'll be in 2.3 and I'll release 2.2 in the coming
week, since the MIME::T
I just got some spam that had the entire body base64 encoded, it's
content-type was "multipart/mixed" with one part, the base64, which was
listed as type "text/html".
Here's what hit:
PLING,BASE64_ENC_TEXT
I see two big issues:
1) it should have hit on the "html only" test, even though it was la
