views:

1267

answers:

14

I have a forum on a website I master, which gets a daily dose of pron spam. Currently I delete the spam and block the IP. But this does not work very well. The list of blocked IP's is growing quickly, but so is the number of spam posts in the forum.

The forum is entirely my own code. It is built in PHP and MySQL.

What are some concrete ways of stopping the spam?

Edit The thing I forgot to mention is that the forum needs to be open for unregistered users to post. Kinda like a blog comment.

A: 

Don't let anybody post until they respond to an email sent to their registered email address. You'll see lots of forums and mailing lists generate a unique email address or web url that is sent to the new user's given email address, and they have to respond to the email or click on the link to finalize their registration.

Paul Tomblin
+5  A: 

One way that I know which works is to use JavaScript before submitting the form. For example, to change the method from GET to POST. ;) Spambots are lousy at executing JavaScript. Of course, this also means that non-Javascript people will not be able to use your site... if you care about them that is. ;) (Note: I don't)

Vilx-
I often leave the action of the form blank and set it in script too.
Diodeus
+4  A: 

You could use a captcha, there are some good scripts like PHPCaptcha or use a spam control service, like Akismet, they have a PHP API.

CMS
+2  A: 

You might want to look at this question, which has several answers that describe how you could implement a non-intrusive captcha.

Another thing to consider is to require time between posts to prevent massive spamming.

Sasha
+8  A: 

In a guestbook app I wrote, I implemented two features which prevent most of the spam:

  • Don't allow POST as the first request in a session

  • Require a valid HTTP Refer(r)er when posting

devio
I like the 'don't allow post as the first request in a session'; thanks
Jacco
I like these kinds of solutions better than CAPTCHA. CAPTCHA inconveniences all your legitimate users, whereas the solutions above don't.
Bill Karwin
"Require a valid HTTP Refer(r)er when posting" <-- This can be easily faked, as it's just a header coming from the user
R. Bemrose
A: 

Captcha is definitely the easiest method - try KittenAuth if you want something bot-proof (Although I got pandas this time)

Mike Robinson
+3  A: 

In my experience, the best easy defenses come from just doing something "non-standard". If you make your site non-standard, this makes it so that any automated spam would have to be coded specifically for your site, which (no offense) probably isn't worth the effort. Note that if the spam is coming from human spammers, there's not really anything you can do that won't also stop legitimate posters. So the goal is to find a solution that will throw away any "standard" posts - that is, "fill out the whole form and push submit".

A couple examples that come to mind of things that you could try:

  • Have a hidden form field with a name that sounds like something a spammer would want to fill out, like "website" or "homepage" or something like that. If the form field gets filled out, throw away the message instead of posting it, because it was a bot automatically filling in the whole form, even invisible fields.
  • You don't have to use a "real" captcha, but even something simple like "Enter the following word backwards: <random backwards word>" or "What is the domain name of this website?". Easy for a human to do, but it would require a fairly complex bot to figure out what to fill in.
Chad Birch
A: 

What do you think about implementing a Captcha system for the comments and Trackbacks? I'll verify that the people who comments is really a person and no a BOT :)

+2  A: 

Include a CAPTCHA that is always "orange".

Instantsoup
A: 

There is no single answer since Spam is really a matter of economics: how much is it worth it to someone to put their stuff onto the web. There, however, some solutions that seem pretty good

Joe Soul-bringer
+1  A: 

The spams may be by bots or humans - bots are more likely.

To stop the bots, put in a hidden field populated by Javascript - there is a 99.5% chance that a standard, stupid bot that isn't customised to your site will fail to fill that in.

If they fail to fill it in correctly, give them a message that Javascript is required or something, and give them an opportunity to post some other way (e.g. with a captcha or registration). That way anonymous users who aren't spambots can (mostly) still post with no problems, and most spambots (which haven't been tailored for your specific site) won't.

Don't bother blacklisting IP addresses or using third party blacklists, that will just generate false positives. Almost all bots use the same IP addresses as (some) legitimate users.


Another trick is to put in a text field with a plausible sounding name, which is made difficult to see with CSS - anyone filling this field in with anything is considered to be a bot.

MarkR
A: 

I want to say that in most time, a CAPTCHA is enough for you to prevent SPAMers. But do use a strong one, like http://www.captcha.net/.

Remember that SPAMers do not want to spend much time to deal with a particular site(except heavy traffic sites), they use a tool to post AD on a lot of sites. So make your FORM a little unusual, (e.g. give the user a image says '1.5+2.4=?' and let users to answer, this will block most of the spam tools :) )

Colin Niu
A: 

Advanced solutions:

You can try your luck with non-standard form:

  • fields that must stay empty hidden with CSS
  • fields with misleading names, e.g. <input name=email> for something that is not an e-mail.

For me CAPTCHA is like giving up to spammers and letting them damage your forum anyway – except that instead of spam damage, you get usability and accessibility damage.

porneL
+2  A: 

Something I've found to be surprisingly effective: disallow comments that contain too many URLs (more than, say, 5). Since doing that, I've had zero comment spam.

Edit: Since writing the above, I've had recurring comment spam with only one link. I have now added some honeypot fields and have had no commend spam for a few months now.

Michael Borgwardt