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.

On being part of the problem... 3 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Complaining hasn't worked. Period.

    Bouncing hasn't worked. Period.

    Now we're trying to remove the economy of spam, by making sure the user never sees the spam. I think hitting the Spammers in the wallet is the only place they're going to take any notice.
    • I know complaining and bouncing haven't worked--the first are ignored, the second spoofed to bother some poor sucker somewhere else in the world. But making spam silently disappear on the end-user's machine doesn't help much either. The spammers don't give a damn if some of their spam gets filtered, as they expect almost all of it to be ignored anyway.

      The problem with the anti-spam software is it's actually taken away some of the disincentives that mail admins used to use. When AOL blacklists your IP addr

      • What I recommend is modifying qpsmtpd's spamassassin capabilities to reject rather than filter if you see a high scoring spam.

        I don't recommend this to everyone, as some people have mail that SpamAssassin scores rather highly, but for regular geeks it's probably a good idea.

        I do feel sympathy though. I know exactly what you mean. But I don't really have a solution yet. :-/
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.