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

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.
  • methinks it's time to write a plonk filter for that sender. If you're not using procmail or Mail::Audit, it's a great reason to start.

    There's a mail virus that *really* likes me; it's sent me about 100 pieces of spam in the last month, roughly totalling 50MB. I read most of my mail on the server, so this works for me (no download-and-delete issue on the downstream pipe).

    • Unfortunately they're all coming from different people--I don't think I've gotten two from the same person yet. I'm a little hesitant to just start throwing mail filters at the problem yet. I get a fair amount of unsolicited email as it is, and I'd rather not take the chance of throwing away someone's real mail.

      I'm running OS X, so it's not like I'm vulnerable to this particular problem. It's just damned annoying.
      • by gnat (29) on 2002.04.20 3:23 (#7303) Journal
        I installed SpamAssassin and haven't looked back. Between procmail and SA, I can nuke most spam. I don't shitcan spam, I store it in a folder that I check once every couple of days to see whether any unspam was accidentally trapped. I believe they call this "gray" mail (as opposed to black and white shitcanning or passing through of email).

        --Nat