Change your httpd.conf file in this area of the file:

# Controls who can get stuff from this server.
#
# below is a specific block of a spammer ip
Order allow,deny
Allow from all
deny from xxx.xxx.xxx.xxx
deny from xxx.xxx.xxx.
# the deny part is the ip you are blocking
# the deny part with the last group of x’s removed blocks a whole ton # of ip’s.. [smile] – but some of these big spammer have many ip’s

Don’t forget to stop and restart your httpd daemon
> service httpd stop
> service httpd start

Note this is the same as putting the deny directive in an .htaccess file (if you don’t have access to the Apache configuation httpd.conf file)

Cheers,
Bob

I appreciate the mention Paul.

I’ve got one particularly persistent spammer. I entered his IP address in the Comment Blacklist field, but the spam from that address keeps ending up in my Akismet spam folder. In other words, despite having his/her IP address in the comment blacklist field, spam from that IP address is getting through.

Is there something obvious that I’m missing? Do we need to preface the IP address with some sort of code?

For The Wordpress Annoyed Blogger’s
Check Out What Paul Stamatiou did When he  received spam comments from one spammer in Abu Dhabi.   The comments were not picked up by Akismet, nor did Akismet learn to recognize them as spam . The Next Day …

Thanks for the feed back.

But I use both methods, Just for extra Protection ;)

Perfectly idea.

:)

Although the plugin is still beta, it does its job. It is still under development as individuals have began to post some bugs. None-the-less I appreciate any and all support towards the cause of Bannage.

If you have multiple ip’s it’s nicer to use an array in this way. And more easy to add more ipadresses.

$iparray = array(“0.0.0.0″, “1.1.1.1″, “2.2.2.2″);
if (in_array($_SERVER['REMOTE_ADDR'], $iparray))
{
echo “spam isn’t appreciated!”;
exit;
}

Derek, the footer message can be unchecked in the Bad Behavior options. ;)
Manually blocking IP’s is good for quick operations like in Paul’s case, although I personally prefer .htaccess. Mid 2003 I started a disallow, deny htaccess, after 3 months I gave up. If I remember well all the rules where 30kB without different mod_rewrites rules. The server performance obviously suffered under this.

Personally I wouldn’t mind to pay for my ISP for an international service maintaining professional lists allowing to block blacklisted IPs immediately at the backbones. Imagine every flatrater pays monthly $0.10 for this. Enough of money to maintain such a service worldwide. And the internet would become faster again.

What I do know is that BB doesn’t work with GoDaddy, but also that is stated in the guidelines.
Using *looks around* Google’s Web Accelerator there are no problems, unlike with EE.