Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

dws (341)

dws
  (email not shown publicly)
http://www.davewsmith.com/

Journal of dws (341)

Wednesday November 27, 2002
12:37 AM

HTML-only spam

[ #9167 ]
Looking around for low-overhead ways of catching spam (no point in going heavyweight if lightweight will do), I came across the following simple procmail trick:

:0
^Content-type:.*html
htmlspam

A quick check showed that nobody was sending html-only email that I cared about, so I gave it a try. It caught 50 spams in 2 days, or about 25% of my daily volume.

Next into the bit-bucket, base64-encoded text/plain entities. A good excuse to play with MIME::Parser and MIME::Entity.

Now I should have been cleaning my study...

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • You can assign an arbitrary "likelyhood of spam" value, and have it spam-bucket anything that comes like that.

    And despite you not having a false positive on such email, with the volume of email I get I've found that I can't just delete those: an occasional legitimate piece of email gets sent that way. So I'm forced to watch that folder about once every other day or so to see if some person is asking me something important.

    That's the problem with spam filters for me: I can't afford to ignore legitimate

    --
    • Randal L. Schwartz
    • Stonehenge
    • I checked a 5+ year email archive, and found no HTML-only messages that weren't spam. But you're right, it could happen that a legitimate email arrives without a TEXT fork. Are you seeing particular MUAs that send HTML-only?