<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	
	xmlns:georss="http://www.georss.org/georss"
	xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#"
	>

<channel>
	<title>spam &#8211; Dabbled</title>
	<atom:link href="https://dabbled.org/tag/spam/feed/" rel="self" type="application/rss+xml" />
	<link>https://dabbled.org</link>
	<description>Experiments in Art, Craft, and Food - an archive</description>
	<lastBuildDate>Tue, 13 Jul 2010 16:22:06 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	
<site xmlns="com-wordpress:feed-additions:1">145231836</site>	<item>
		<title>Dealing with Comment Spam, Part 2</title>
		<link>https://dabbled.org/dealing-with-comment-spam-part-2/</link>
		
		<dc:creator><![CDATA[Dot]]></dc:creator>
		<pubDate>Tue, 13 Jul 2010 16:20:07 +0000</pubDate>
				<category><![CDATA[website design]]></category>
		<category><![CDATA[blocking spam]]></category>
		<category><![CDATA[comment spam]]></category>
		<category><![CDATA[htaccess]]></category>
		<category><![CDATA[spam]]></category>
		<category><![CDATA[trackback spam]]></category>
		<category><![CDATA[wordpress plugins]]></category>
		<guid isPermaLink="false">http://dabbled.org/?p=4150</guid>

					<description><![CDATA[<p><a href="http://dabbled.org/wp-content/uploads/2010/07/2607573904_74f05e1d75.jpg"></a>Here is part 2 on dealing with Comment Spam&#8230; the bane of a blogger&#8217;s existence.  In <a href="http://dabbled.org/2010/07/how-to-deal-with-comment-spam-part-1.html" target="_self">part 1 we talked about Comment Moderation and Blacklisting</a>, so, to continue&#8230;</p>
<p>(If you missed it: <strong><a href="../2010/07/how-to-deal-with-comment-spam-part-1.html" target="_blank">How to deal with Comment Spam, Part 1)</a></strong></p>
<strong>Those evil (more educated) comment spammers who look almost real</strong>
<p>Lately I&#8217;ve been noticing a trend of spammers who look like they have actually read your post, and respond with a somewhat intelligent comment, not full of spam links. &#8230; <a href="https://dabbled.org/dealing-with-comment-spam-part-2/" class="read-more"> [ KEEP READING ] </a></p>]]></description>
										<content:encoded><![CDATA[<p><a href="http://dabbled.org/wp-content/uploads/2010/07/2607573904_74f05e1d75.jpg"><img decoding="async" loading="lazy" class="alignright size-medium wp-image-4139" title="Spam 70th anniversary by dok1 on flickr" src="http://dabbled.org/wp-content/uploads/2010/07/2607573904_74f05e1d75-275x237.jpg" alt="Spam 70th anniversary by dok1 on flickr" width="275" height="237" srcset="https://dabbled.org/wp-content/uploads/2010/07/2607573904_74f05e1d75-275x237.jpg 275w, https://dabbled.org/wp-content/uploads/2010/07/2607573904_74f05e1d75.jpg 500w" sizes="(max-width: 275px) 100vw, 275px" /></a>Here is part 2 on dealing with Comment Spam&#8230; the bane of a blogger&#8217;s existence.  In <a href="http://dabbled.org/2010/07/how-to-deal-with-comment-spam-part-1.html" target="_self">part 1 we talked about Comment Moderation and Blacklisting</a>, so, to continue&#8230;</p>
<p>(If you missed it: <strong><a href="../2010/07/how-to-deal-with-comment-spam-part-1.html" target="_blank">How to deal with Comment Spam, Part 1)</a></strong></p>
<h3><strong>Those evil (more educated) comment spammers who look almost real</strong></h3>
<p>Lately I&#8217;ve been noticing a trend of spammers who look like they have actually read your post, and respond with a somewhat intelligent comment, not full of spam links.  These can be almost more annoying, because they can slip by automated checks, and because they require more work.  Plus, sometimes you&#8217;re not even sure if they are really a spammer.  These will be notable by either a really odd name (like &#8220;Boys Birthday Cards&#8221; or &#8220;Best Home Loans&#8221;) which link back to their spam site, or they&#8217;ll have a normal name (like &#8220;Sue Smith&#8221; or &#8220;Jessica&#8221;) but their name links to something like myspammyloansite.com.</p>
<p style="text-align: right;"><em>Photo credit: <a onclick="javascript:pageTracker._trackPageview('/outbound/article/www.flickr.com');" href="http://www.flickr.com/photos/dok1/2607573904/">Spam</a> by <a onclick="javascript:pageTracker._trackPageview('/outbound/article/www.flickr.com');" href="http://www.flickr.com/photos/dok1/">dok1</a></em></p>
<p>So what to do about them?  You can just delete them like normal spam.  But what if they&#8217;ve asked a relevant question that other people might want to know the answer to?  Or if other commenters have already responded to their comment?  Then I hate to just delete them.  So&#8230;</p>
<p>Well, if you have your comments links set to nofollow (more on that  below) you could just leave them.  They aren&#8217;t getting any page rank  juice out of the link anyway.  But (particularly if the name is suspect) I don&#8217;t like to look like I didn&#8217;t notice the spam, and I don&#8217;t want my readers to click on their name and give them any traffic.  Also, what if a real commenter has just a suspect website name, I&#8217;d hate to delete them.</p>
<p>If you&#8217;re using WordPress, you can delink them, and even change the name.</p>
<h3><strong>De-linking a dubious comment</strong></h3>
<p>In WordPress, click on the Comments section in your Dashboard Sidebar.  When you hover over the comment, you&#8217;ll see the Quick Edit option.</p>
<p><span id="more-4150"></span>Click that, and the comment will open for editing.  Delete any suspect links in the URL field, and the comment remains, but is no longer linked to the spam site.  If you want, you can also change a suspect name (like &#8220;Cheap Home Loans&#8221;) to something like &#8220;possible spam, link removed&#8221;, but that may be going overboard.  I usually just delete those comments instead.</p>
<p><a href="http://dabbled.org/wp-content/uploads/2010/07/editspammer.jpg"><img decoding="async" loading="lazy" class="alignnone size-large wp-image-4151" title="Delinking a Spammer in WordPress" src="http://dabbled.org/wp-content/uploads/2010/07/editspammer-575x272.jpg" alt="Delinking a Spammer in WordPress" width="575" height="272" srcset="https://dabbled.org/wp-content/uploads/2010/07/editspammer-575x272.jpg 575w, https://dabbled.org/wp-content/uploads/2010/07/editspammer-275x130.jpg 275w, https://dabbled.org/wp-content/uploads/2010/07/editspammer.jpg 727w" sizes="(max-width: 575px) 100vw, 575px" /></a></p>
<h3>A little about the nofollow attribute</h3>
<p>In the comments for Part 1, we talked about what value spammers get out of leaving Comment Spam, and a commenter brought up that they are trying to get search engine page rank juice out of the comment.  Search engines crawling your site will follow the link and help the spammer move up in search engine rankings.</p>
<p>However, most blogs these days (WordPress and Blogger, at least) automatically add the nofollow attribute to any outgoing links in the comments.  The nofollow attribute tells the search engines not to follow or score the link.   More here: <a onclick="javascript:pageTracker._trackPageview('/outbound/comment/en.wikipedia.org');" rel="nofollow" href="http://en.wikipedia.org/wiki/Nofollow">http://en.wikipedia.org/wiki/Nofollow</a>.  It was  created primarily for the purpose of addressing the comment spam issue.</p>
<p>According to the wiki article, Google, Yahoo, and Bing all pay  attention to this.  So leaving comment spam SHOULD NOT help the spammer’s pagerank.</p>
<p>So in theory, having the nofollow attribute enabled should cut down on Comment Spam, if the spammer is paying attention to that.  Unfortunately, spam is cheap, so spammers just hit as many sites as they can, without worrying about whether it&#8217;s helping them or not.</p>
<p>The problem with nofollow is that your real commenters don&#8217;t get any link juice either, so some sites disable this feature by using dofollow instead. There are pros and cons, and I haven&#8217;t really done the research to address it here.  If you&#8217;re interested,<a href="http://www.google.com/search?hl=&amp;q=dofollow&amp;sourceid=navclient-ff&amp;rlz=1B3GGLL_en___US375&amp;ie=UTF-8" target="_blank"> google is your friend</a>.</p>
<p>But, the basic point is that unless you&#8217;ve bypassed nofollow, the spammer is basically not getting any value for his or her links.</p>
<p><strong>Blocking IPs using .htaccess, instead of WordPress settings</strong></p>
<p>The Blacklist feature we discussed in part 1 will stop known bad actors comments appear on your site.  The comments just go straight to Spam.  But that can still be a little annoying, if you have your comments emailed to you.  They still exist, so you&#8217;ll still be notified via email.  So once you have a nice little list of IPs in your Blacklist, you can block them from your site, period!</p>
<p>You can do this if you host your own blog and have access to the file structure (like most self-hosted WordPress blogs), and have an .htaccess file (I think if you&#8217;re running WP on Unix, you have one &#8211; it&#8217;s where your &#8216;Pretty Permalinks&#8217; settings are).</p>
<p>Use your FTP program to locate your .htaccess file, in your main directory (may be www).  Save that file down (save an extra copy of the original- just in case you break something &#8211; if you have problems after trying this, just copy the original file back up).</p>
<p>Pull it up in a text editor and add something like the following:</p>
<p>order allow,deny<br />
deny from 91.201.66.6<br />
deny from 110.82.142.143<br />
deny from 122.182.10.212<br />
deny from 120.28.179.165<br />
deny from 203.76.116.66<br />
allow from all</p>
<p>Where each &#8216;deny from&#8217; line is the IP address of your already identified spammer.</p>
<p>Copy your file back up to the server, and enjoy!</p>
<h3><strong>Stopping Trackback Spam</strong></h3>
<p><a href="http://en.wikipedia.org/wiki/Trackback" target="_blank">Trackbacks </a>are a great way to see who&#8217;s linking to a particular post, and are very useful, but spammers have figured out that Trackbacks are useful to them too, and will create links to your blog just to add a trackback (along with lots of lovely spam links).  Some people turn off trackbacks because of this, and that&#8217;s a shame, because they are quite easy to stop, at least on WordPress, with a plugin.  I&#8217;m sure there are several out there, but I&#8217;ve been using <a href="http://wordpress.org/extend/plugins/simple-trackback-validation/" target="_blank">Simple Trackback Validation</a> for a while, and it seems to stop them 99% of the time.  (<a title="Permanent Link" rel="bookmark" href="http://sw-guide.de/wordpress/plugins/simple-trackback-validation/">Simple Trackback Validation Plugin official site</a>)</p>
<p>The settings I recommend:</p>
<p><a href="http://dabbled.org/wp-content/uploads/2010/07/tbspam.jpg"><img decoding="async" loading="lazy" class="alignright size-medium wp-image-4152" title="Settings recommended for Simple Trackback Validation plugin - wordpress" src="http://dabbled.org/wp-content/uploads/2010/07/tbspam-275x334.jpg" alt="" width="275" height="334" srcset="https://dabbled.org/wp-content/uploads/2010/07/tbspam-275x334.jpg 275w, https://dabbled.org/wp-content/uploads/2010/07/tbspam-575x699.jpg 575w, https://dabbled.org/wp-content/uploads/2010/07/tbspam.jpg 617w" sizes="(max-width: 275px) 100vw, 275px" /></a>(Click on the image to the right to see configuration screen with the settings I use for Foodwhirl.com)</p>
<p><strong>How to deal with spam trackbacks: </strong> [x] Discard Trackback</p>
<p><em>(I never want to see the spam or deal with it.)</em></p>
<p>[x]<strong> Validate IP Address (yes)<br />
</strong></p>
<p>[x<strong>] Validate URL (yes)</strong></p>
<p><strong>Strictness: </strong></p>
<p><strong>[x] Any link beginning with the following URL is allowed</strong></p>
<p><em>(enter your site&#8217;s main URL)</em></p>
<p><strong>[] Moderate in case of errors (no)</strong></p>
<p><strong>[x] Enable Log (yes)</strong></p>
<p><em>(Since you&#8217;re sending all trackbacks that the plugin finds straight to the trash, it&#8217;s nice to have them logged.</em>)</p>
<h3>Conclusion</h3>
<p>Hopefully these tips will help you manage your comment spam, so it&#8217;s less of a headache!  If you have tips or other recommended plug ins, leave them in the comments!</p>
<p>-dot</p>
]]></content:encoded>
					
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">4150</post-id>	</item>
		<item>
		<title>How to deal with comment spam.. Part 1</title>
		<link>https://dabbled.org/how-to-deal-with-comment-spam-part-1/</link>
					<comments>https://dabbled.org/how-to-deal-with-comment-spam-part-1/#comments</comments>
		
		<dc:creator><![CDATA[Dot]]></dc:creator>
		<pubDate>Sun, 11 Jul 2010 17:27:24 +0000</pubDate>
				<category><![CDATA[website design]]></category>
		<category><![CDATA[comment spam]]></category>
		<category><![CDATA[spam]]></category>
		<category><![CDATA[website tips]]></category>
		<category><![CDATA[wordpress]]></category>
		<guid isPermaLink="false">http://dabbled.org/?p=4137</guid>

					<description><![CDATA[<p><a href="http://dabbled.org/wp-content/uploads/2010/07/2607573904_74f05e1d75.jpg"></a>If you blog, you know all about Comment Spam.  It&#8217;s those lovely little comments whose sole purpose is to link back to and/or promote some totally unrelated product or website.  Honestly, I&#8217;m not sure what value the spammers even get out of it, but that doesn&#8217;t stop them from doing it.  And it&#8217;s a pain to deal with.</p>
<p>In my other life where I do <a href="http://dabbledstudios.com">web design</a>, I&#8217;ve helped my blogger friends figure out how to best manage the deluge, and I figured the rest of you might like some of these insights too. &#8230; <a href="https://dabbled.org/how-to-deal-with-comment-spam-part-1/" class="read-more"> [ KEEP READING ] </a></p>]]></description>
										<content:encoded><![CDATA[<p><a href="http://dabbled.org/wp-content/uploads/2010/07/2607573904_74f05e1d75.jpg"><img decoding="async" loading="lazy" class="alignright size-medium wp-image-4139" title="Spam 70th anniversary by dok1 on flickr" src="http://dabbled.org/wp-content/uploads/2010/07/2607573904_74f05e1d75-275x237.jpg" alt="Spam 70th anniversary by dok1 on flickr" width="275" height="237" srcset="https://dabbled.org/wp-content/uploads/2010/07/2607573904_74f05e1d75-275x237.jpg 275w, https://dabbled.org/wp-content/uploads/2010/07/2607573904_74f05e1d75.jpg 500w" sizes="(max-width: 275px) 100vw, 275px" /></a>If you blog, you know all about Comment Spam.  It&#8217;s those lovely little comments whose sole purpose is to link back to and/or promote some totally unrelated product or website.  Honestly, I&#8217;m not sure what value the spammers even get out of it, but that doesn&#8217;t stop them from doing it.  And it&#8217;s a pain to deal with.</p>
<p>In my other life where I do <a href="http://dabbledstudios.com">web design</a>, I&#8217;ve helped my blogger friends figure out how to best manage the deluge, and I figured the rest of you might like some of these insights too.  It&#8217;s tailored mostly to WordPress blogs/websites, but some of the tips are universal.  As I started writing it, I realized it was getting pretty long, so here&#8217;s Part 1&#8230; Part 2 will be coming later in the week!</p>
<p style="text-align: right;"><em>Photo credit: <a href="http://www.flickr.com/photos/dok1/2607573904/">Spam</a> by <a href="http://www.flickr.com/photos/dok1/">dok1</a></em></p>
<h3>We HATE Spam, but love our readers.</h3>
<p>As a blogger, you want to make commenting on your posts as easy as possible for your &#8216;real&#8217; readers.  But as hard as possible for spammers, and it&#8217;s a delicate balance.  On one end of the spectrum is registration only sites&#8211;sites where you have to sign up, and in some cases even be verified, prior to posting a comment.  Much less likely to get spammers, but you are likely losing out on valuable real people too.  I know I won&#8217;t generally go to the effort to comment on a site I have to sign up for.</p>
<p>On the other side of the coin, with no protections at all, it&#8217;s easy for your commenters to post, but spammers (both automated bots and humans) will have a field day.  I was working on a new website for a client once (it wasn&#8217;t live yet, but it was accessible on the web), and I hadn&#8217;t gotten around to installing any spam protection yet on the blog.  Overnight there were hundreds of automated comments on it, as some spam bot had somehow stumbled across it, and went to town.  I deleted them, no harm done, but if that had been a live active site, what a pain it would have been!</p>
<h3>Those evil spam-bots</h3>
<p>So, minimally you need protection from bots.  Many sites use some form of a Captcha (<a href="http://en.wikipedia.org/wiki/CAPTCHA" target="_blank">what is a captcha?</a>), where the commenter must type in a phrase or something to prove they are a human.  Captcha isn&#8217;t perfect, and it can be a little bit of a pain to real users, but it&#8217;s pretty standard.  There are other methods too&#8230; for my WordPress based sites, like this one, I use a plugin called <a href="http://wordpress.org/extend/plugins/wp-captcha-free/" target="_blank">WP-CaptchaFree</a>, which uses some technology tricks to attempt to identify spam bots and stop them.  I&#8217;ve been very happy with it.  There&#8217;s also <a href="http://en.wikipedia.org/wiki/Akismet" target="_blank">Akismet</a>, which tries to guess which comments are spam, and blocks spammers and is provided with WordPress, but I&#8217;ve never used it.</p>
<h3>Those evil human comment spammers</h3>
<p>Must harder to keep out are actual humans who have chosen to be paid to be spammers-usually from other (3rd world) countries where labor is cheap.  Conveniently, being humans they leave manageable amounts of spam, so cleanup is less of a pain that a bot attack.  But since they are human, they can get around captchas and other things that detect bots. They are quite easy for YOU to detect as spammers because their comment makes no sense or has nothing to do with the post!</p>
<p>So what to do about them? Read on&#8230;</p>
<h3><span id="more-4137"></span>Comment Moderation</h3>
<p>This is particularly for WordPress blogs, but other blog platforms likely have similar settings.</p>
<p><strong>Moderate Everything: </strong> Turning on comment moderation on your blog (in WP this is under the Discussion settings) means that every time someone posts a comment it has to be approved before it can be viewed.  While this will ensure you catch spam before it appears on your blog, it also means more work for you.  And you still have to deal with the spam, it just keeps your readers from seeing it.  Plus you have to approve all your good readers comments as well.  I find this more trouble than it&#8217;s worth.</p>
<p><strong>Moderate Some Things: </strong> There&#8217;s a setting (&#8220;Before a Comment Appears&#8221; in WordPress) that you only send new commenters (ones which have not had a comment approved before) automatically to moderation.  Depending on how many new commenters you have&#8211;If most of your commenters are repeat commenters, this might be a helpful alternative.  But if you get lots of legit new commenters, then this may be more trouble that it&#8217;s worth to you.</p>
<p><strong>Moderate Likely Spam only: </strong> The Comment Moderation section of your Discussion Settings will let you set which items to send to moderation.  For example, items with more than x number of links (I set mine to 2 or more) are automatically sent to moderation.  Also, you can also pick words that show up typically in spam and not typically in your comments.  You can see I few I have set below.  I just added &#8216;loan&#8217; to the list, because where I can see that a comment could legitimately contain that word, 80% of my spam comments seem to have it these days!</p>
<p><a href="http://dabbled.org/wp-content/uploads/2010/07/commentmoderation.jpg"><img decoding="async" loading="lazy" class="alignnone size-large wp-image-4140" title="How to set discussion settings in wordpress Comment Moderation" src="http://dabbled.org/wp-content/uploads/2010/07/commentmoderation-575x212.jpg" alt="How to set discussion settings in wordpress Comment Moderation" width="575" height="212" srcset="https://dabbled.org/wp-content/uploads/2010/07/commentmoderation-575x212.jpg 575w, https://dabbled.org/wp-content/uploads/2010/07/commentmoderation-275x101.jpg 275w, https://dabbled.org/wp-content/uploads/2010/07/commentmoderation.jpg 600w" sizes="(max-width: 575px) 100vw, 575px" /></a></p>
<h3>Comment Blacklist</h3>
<p>Once you have a spammer post on your site, you can block their IP so they can&#8217;t do so again.  You don&#8217;t have to deal with it at all, once they are on the blacklist.  This is helpful because they often come back again and again, once they  find your site.  In WordPress, this is also done in the Discussion  Settings.</p>
<p>Get the IP of your spammer:  In the Comments section of your WP Dashboard, you can see all the details on your spammer. You&#8217;ll note in the example below, our scum has left two comments, under 2 different names, but the IP address is the same.  They left the second one a day after the first.  We don&#8217;t want to deal with this IP again, so copy it (it&#8217;s highlighted in yellow below).</p>
<p><a href="http://dabbled.org/wp-content/uploads/2010/07/commentsip.jpg"><img decoding="async" loading="lazy" class="alignnone size-large wp-image-4142" title="Find the IP of your spammer in the comments section" src="http://dabbled.org/wp-content/uploads/2010/07/commentsip-575x231.jpg" alt="Find the IP of your spammer in the comments section" width="575" height="231" srcset="https://dabbled.org/wp-content/uploads/2010/07/commentsip-575x231.jpg 575w, https://dabbled.org/wp-content/uploads/2010/07/commentsip-275x110.jpg 275w, https://dabbled.org/wp-content/uploads/2010/07/commentsip.jpg 818w" sizes="(max-width: 575px) 100vw, 575px" /></a></p>
<p>You&#8217;ll need to add this IP to the Comment Blacklist section:</p>
<p><a href="http://dabbled.org/wp-content/uploads/2010/07/commentblacklist.jpg"><img decoding="async" loading="lazy" class="alignnone size-large wp-image-4143" title="How to add IP to comment blacklist section in WordPress" src="http://dabbled.org/wp-content/uploads/2010/07/commentblacklist-575x151.jpg" alt="How to add IP to comment blacklist section in WordPress" width="575" height="151" srcset="https://dabbled.org/wp-content/uploads/2010/07/commentblacklist-575x151.jpg 575w, https://dabbled.org/wp-content/uploads/2010/07/commentblacklist-275x72.jpg 275w, https://dabbled.org/wp-content/uploads/2010/07/commentblacklist.jpg 600w" sizes="(max-width: 575px) 100vw, 575px" /></a></p>
<p>Just add the IP to the list, and their comments will never appear, they&#8217;ll just go automatically to your Spam folder.  The only downside to this method is that you still may receive email notifications of the comment, even though it never appears on the site.</p>
<h3><strong>Coming in part 2&#8230;</strong></h3>
<ul>
<li><strong>Those evil (more educated) comment spammers who look almost real</strong></li>
<li><strong>De-linking a dubious comment</strong></li>
<li><strong>Blocking IPs using .htaccess, instead of WordPress settings</strong></li>
<li><strong>Stopping Trackback Spam</strong></li>
</ul>
<p><strong>So stay tuned!</strong></p>
<blockquote><p><a href="http://dabbled.org/feed">(Don&#8217;t want to miss anything? Get the RSS Feed)</a><strong><br />
</strong></p></blockquote>
<p style="text-align: right;"><em><br />
<a href="http://www.flickr.com/photos/dok1/"></a></em></p>
]]></content:encoded>
					
					<wfw:commentRss>https://dabbled.org/how-to-deal-with-comment-spam-part-1/feed/</wfw:commentRss>
			<slash:comments>5</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">4137</post-id>	</item>
	</channel>
</rss>
