<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Simple Wordpress anti-spam for shared hosting</title>
	<atom:link href="http:///simple-wordpress-anti-spam-for-shared-hosting/2006/12/21/feed/" rel="self" type="application/rss+xml" />
	<link>/simple-wordpress-anti-spam-for-shared-hosting/2006/12/21/</link>
	<description>Backup, monitor and sync shared hosting accounts</description>
	<pubDate>Wed, 07 Jan 2009 17:58:06 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.5</generator>
		<item>
		<title>By: Brian</title>
		<link>/simple-wordpress-anti-spam-for-shared-hosting/2006/12/21/#comment-2178</link>
		<dc:creator>Brian</dc:creator>
		<pubDate>Mon, 06 Aug 2007 08:00:51 +0000</pubDate>
		<guid isPermaLink="false">http://clonepanel.com/simple-wordpress-anti-spam-for-shared-hosting/2006/12/21/#comment-2178</guid>
		<description>Hmmm ... some great stuff here, thanks for the resources; hadn't realized that it was just so easy to install Akismet/Spam Karma etc!

Re the site getting kicked off the server for 1 spam attempt per second - that's extreme, and shows that the host didn't know what it was doing, at least to some extent.  I haven't tested this out, so I'll pull my head in if required, but I can't imagine that a simple spam block should consume much resource.  Perhaps they were doing an Akismet check (possibly resource-heavy) first and putting something else in front of that might have knocked off much of the attempts.  I do remember hearing somewhere else that changing the comment form name was enough to knock off spam and that's a neat trick; there are some similar things that can be done with MX records to kill off spam ('nolisting').

There are some nice free firewall products available now which should block such attempts automatically (CSF); mind you, I'm not sure if they do, but it could save a server quite some CPU time if it was able to proactively firewall such IPs.</description>
		<content:encoded><![CDATA[<p>Hmmm &#8230; some great stuff here, thanks for the resources; hadn&#8217;t realized that it was just so easy to install Akismet/Spam Karma etc!</p>
<p>Re the site getting kicked off the server for 1 spam attempt per second - that&#8217;s extreme, and shows that the host didn&#8217;t know what it was doing, at least to some extent.  I haven&#8217;t tested this out, so I&#8217;ll pull my head in if required, but I can&#8217;t imagine that a simple spam block should consume much resource.  Perhaps they were doing an Akismet check (possibly resource-heavy) first and putting something else in front of that might have knocked off much of the attempts.  I do remember hearing somewhere else that changing the comment form name was enough to knock off spam and that&#8217;s a neat trick; there are some similar things that can be done with MX records to kill off spam (&#8217;nolisting&#8217;).</p>
<p>There are some nice free firewall products available now which should block such attempts automatically (CSF); mind you, I&#8217;m not sure if they do, but it could save a server quite some CPU time if it was able to proactively firewall such IPs.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
