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.
  • 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.
    • The problem with blacklists is "how not to block valid emails?"...

      grinder [perl.org] had a very good idea to hit spammers where it hurts [perl.org]. Quote:

      And what I'm toying with is something a little more radical. Sure I'll probably sign up with an RBL or two, but what I'm going to do is I'm still going to accept everything. But. When I come acrosss mail that comes from a suspected spammer, I'm going to put sleep(120) or so between each step in the transfer dialog.
      If enough people start doing this (and maybe people do; I haven't looked into the matter) then spammers are going to be hit where it hurts: raw throughput. Instead of pumping out 100 000 messages per hour, they're gonna start choking on sites which take minutes to complete.
      If you are an innocent site, well, tough, from time to time you'll have a socket tied up on your mailer to a remote site, but as sending email isn't the be-all and end-all of your business, that's not going to be a big problem. But if you're a spammer, you're going to find that you can't bomb as many people in the same time frame as you used to. Spamming therefore becomes more uneconomical.
      And that, in my books, is a Good Thing.