<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: How to Stop Spam Harvesting With Email Obfuscation</title>
	<atom:link href="http://www.sitepoint.com/blogs/2009/05/05/stop-spam-harvesting-email-obfuscation/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.sitepoint.com/blogs/2009/05/05/stop-spam-harvesting-email-obfuscation/</link>
	<description>News, opinion, and fresh thinking for web developers and designers. The official podcast of sitepoint.com.</description>
	<lastBuildDate>Mon, 23 Nov 2009 00:48:44 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Craig Buckler</title>
		<link>http://www.sitepoint.com/blogs/2009/05/05/stop-spam-harvesting-email-obfuscation/comment-page-1/#comment-926032</link>
		<dc:creator>Craig Buckler</dc:creator>
		<pubDate>Tue, 26 May 2009 11:30:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=8534#comment-926032</guid>
		<description>@jj
&lt;blockquote&gt;...all I’m seeing is the obfuscated address&lt;/blockquote&gt;

The code is either failing or not being started. Run it in Firefox with the error console open (Tools &gt; Error Console) - that should tell you if there are any obvious errors. Otherwise, post a link to your page URL and I&#039;ll take a look.</description>
		<content:encoded><![CDATA[<p>@jj</p>
<blockquote><p>&#8230;all I’m seeing is the obfuscated address</p></blockquote>
<p>The code is either failing or not being started. Run it in Firefox with the error console open (Tools > Error Console) &#8211; that should tell you if there are any obvious errors. Otherwise, post a link to your page URL and I&#8217;ll take a look.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: jj</title>
		<link>http://www.sitepoint.com/blogs/2009/05/05/stop-spam-harvesting-email-obfuscation/comment-page-1/#comment-925982</link>
		<dc:creator>jj</dc:creator>
		<pubDate>Mon, 25 May 2009 18:27:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=8534#comment-925982</guid>
		<description>I tried it but it&#039;s not working. I put in the email.js file to the server, linked to it in the header, added the &#039;window.onload&#039; line at the bottom, and used &quot;class&quot; in the email link (actually I copied/pasted and just changed the email address), but all I&#039;m seeing is the obfuscated address. And I&#039;m almost 100% sure that I have javascript enabled.</description>
		<content:encoded><![CDATA[<p>I tried it but it&#8217;s not working. I put in the email.js file to the server, linked to it in the header, added the &#8216;window.onload&#8217; line at the bottom, and used &#8220;class&#8221; in the email link (actually I copied/pasted and just changed the email address), but all I&#8217;m seeing is the obfuscated address. And I&#8217;m almost 100% sure that I have javascript enabled.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: visual28</title>
		<link>http://www.sitepoint.com/blogs/2009/05/05/stop-spam-harvesting-email-obfuscation/comment-page-1/#comment-925465</link>
		<dc:creator>visual28</dc:creator>
		<pubDate>Mon, 11 May 2009 22:46:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=8534#comment-925465</guid>
		<description>I agree with omnicity, the spammers are far to smart and the email is easily hacked using common replacement techniques. I use a modified algorithm of the Project Honeypot system found here:
http://www.projecthoneypot.org/how_to_avoid_spambots_3.php

Even it&#039;s not perfect, and will surely be defeated soon enough if not already. The only decent way to protect your email is through the use of a contact form.</description>
		<content:encoded><![CDATA[<p>I agree with omnicity, the spammers are far to smart and the email is easily hacked using common replacement techniques. I use a modified algorithm of the Project Honeypot system found here:<br />
<a href="http://www.projecthoneypot.org/how_to_avoid_spambots_3.php" rel="nofollow">http://www.projecthoneypot.org/how_to_avoid_spambots_3.php</a></p>
<p>Even it&#8217;s not perfect, and will surely be defeated soon enough if not already. The only decent way to protect your email is through the use of a contact form.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: omnicity</title>
		<link>http://www.sitepoint.com/blogs/2009/05/05/stop-spam-harvesting-email-obfuscation/comment-page-1/#comment-925464</link>
		<dc:creator>omnicity</dc:creator>
		<pubDate>Mon, 11 May 2009 22:26:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=8534#comment-925464</guid>
		<description>There is plenty of evidance to suggest that the spam-bots are already using regExp patterns to look for even partial email addresses.
Where only a domain name is found, they then launch a dictionary attack with that, though domain names can just as easily be found via DNS.</description>
		<content:encoded><![CDATA[<p>There is plenty of evidance to suggest that the spam-bots are already using regExp patterns to look for even partial email addresses.<br />
Where only a domain name is found, they then launch a dictionary attack with that, though domain names can just as easily be found via DNS.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Stomme poes</title>
		<link>http://www.sitepoint.com/blogs/2009/05/05/stop-spam-harvesting-email-obfuscation/comment-page-1/#comment-925338</link>
		<dc:creator>Stomme poes</dc:creator>
		<pubDate>Fri, 08 May 2009 08:13:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=8534#comment-925338</guid>
		<description>[quote]Re-captcha allows you to protect your email with a security image.[/quote]

More and more sites, I cannot contact the owners because of captchas.  I can&#039;t read most of them, and I&#039;m not blind.

I&#039;ve been using numerical charcter entities for the whole email addresses, the mailto and the text in the anchor, and sometimes also with the word &quot;email&quot;.  I also don&#039;t know how well this works, but I&#039;ll keep doing it so long as I know there are still many bots who can&#039;t read them.</description>
		<content:encoded><![CDATA[<p>[quote]Re-captcha allows you to protect your email with a security image.[/quote]</p>
<p>More and more sites, I cannot contact the owners because of captchas.  I can&#8217;t read most of them, and I&#8217;m not blind.</p>
<p>I&#8217;ve been using numerical charcter entities for the whole email addresses, the mailto and the text in the anchor, and sometimes also with the word &#8220;email&#8221;.  I also don&#8217;t know how well this works, but I&#8217;ll keep doing it so long as I know there are still many bots who can&#8217;t read them.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: soundjet</title>
		<link>http://www.sitepoint.com/blogs/2009/05/05/stop-spam-harvesting-email-obfuscation/comment-page-1/#comment-925337</link>
		<dc:creator>soundjet</dc:creator>
		<pubDate>Fri, 08 May 2009 07:53:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=8534#comment-925337</guid>
		<description>Nice one! guaranteed? ;)</description>
		<content:encoded><![CDATA[<p>Nice one! guaranteed? ;)</p>]]></content:encoded>
	</item>
	<item>
		<title>By: roger</title>
		<link>http://www.sitepoint.com/blogs/2009/05/05/stop-spam-harvesting-email-obfuscation/comment-page-1/#comment-925325</link>
		<dc:creator>roger</dc:creator>
		<pubDate>Fri, 08 May 2009 00:02:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=8534#comment-925325</guid>
		<description>Of course,  unfortunately, you have also provided in this article the source code for the spammer to look at currently obfuscated email addresses and harvest them.

... Hey dude,  just look for anything that is class email and then run it through this code ...

Maybe calling the class &#039;honeypot&#039; would be more appropriate.

great code btw, but those spammers have more time on their hands than we have to defeat them.

Of course by suggesting it in this comment I am also aiding them ...  Wheres the delete key ?</description>
		<content:encoded><![CDATA[<p>Of course,  unfortunately, you have also provided in this article the source code for the spammer to look at currently obfuscated email addresses and harvest them.</p>
<p>&#8230; Hey dude,  just look for anything that is class email and then run it through this code &#8230;</p>
<p>Maybe calling the class &#8216;honeypot&#8217; would be more appropriate.</p>
<p>great code btw, but those spammers have more time on their hands than we have to defeat them.</p>
<p>Of course by suggesting it in this comment I am also aiding them &#8230;  Wheres the delete key ?</p>]]></content:encoded>
	</item>
	<item>
		<title>By: justseth</title>
		<link>http://www.sitepoint.com/blogs/2009/05/05/stop-spam-harvesting-email-obfuscation/comment-page-1/#comment-925287</link>
		<dc:creator>justseth</dc:creator>
		<pubDate>Thu, 07 May 2009 02:54:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=8534#comment-925287</guid>
		<description>using a contact form is the best of solutions for many reasons:
1) the developer can control the conversation, ensuring the required information is sent
2) forms are trackable / measurable
3) auto-responses can be delivered based upon an array of conditions.
4) contact forms are routable. meaning, depending upon subject, will determine where the email is sent.</description>
		<content:encoded><![CDATA[<p>using a contact form is the best of solutions for many reasons:<br />
1) the developer can control the conversation, ensuring the required information is sent<br />
2) forms are trackable / measurable<br />
3) auto-responses can be delivered based upon an array of conditions.<br />
4) contact forms are routable. meaning, depending upon subject, will determine where the email is sent.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: heggaton</title>
		<link>http://www.sitepoint.com/blogs/2009/05/05/stop-spam-harvesting-email-obfuscation/comment-page-1/#comment-925278</link>
		<dc:creator>heggaton</dc:creator>
		<pubDate>Wed, 06 May 2009 23:44:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=8534#comment-925278</guid>
		<description>@Patrick, I completely understand now and yeah, you&#039;re way is much better than using the noscript tag :)

I think I&#039;ll stick to my original way of obfuscating and directing people to the feedback form on JavaScript failover but use your method of replacing HTML rather than the noscript.

Cheers</description>
		<content:encoded><![CDATA[<p>@Patrick, I completely understand now and yeah, you&#8217;re way is much better than using the noscript tag :)</p>
<p>I think I&#8217;ll stick to my original way of obfuscating and directing people to the feedback form on JavaScript failover but use your method of replacing HTML rather than the noscript.</p>
<p>Cheers</p>]]></content:encoded>
	</item>
	<item>
		<title>By: PatrickSamphire</title>
		<link>http://www.sitepoint.com/blogs/2009/05/05/stop-spam-harvesting-email-obfuscation/comment-page-1/#comment-925246</link>
		<dc:creator>PatrickSamphire</dc:creator>
		<pubDate>Wed, 06 May 2009 11:49:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=8534#comment-925246</guid>
		<description>@heggaton, I was simply suggesting approaching it from the other direction to come up with the same solution. So, rather than having noscript for those without javascript, have the link to the contact form included in the html as default for everyone (but not inside noscript), then use javascript to remove that link and replace it with the obfuscated email. 

That way, you don&#039;t need a noscript tag at all.

The result will be exactly the same, and there&#039;s no particular reason that anyone should go this more complicated route, but I just like things to look neat, and noscript always seemed a little ugly to me. :)</description>
		<content:encoded><![CDATA[<p>@heggaton, I was simply suggesting approaching it from the other direction to come up with the same solution. So, rather than having noscript for those without javascript, have the link to the contact form included in the html as default for everyone (but not inside noscript), then use javascript to remove that link and replace it with the obfuscated email. </p>
<p>That way, you don&#8217;t need a noscript tag at all.</p>
<p>The result will be exactly the same, and there&#8217;s no particular reason that anyone should go this more complicated route, but I just like things to look neat, and noscript always seemed a little ugly to me. :)</p>]]></content:encoded>
	</item>
</channel>
</rss>
