Anti-Harvester Methods?

[Mr_N]

I was wondering if anyone could shed light on what the best methods of avoiding email harvesters are right now. Do the people who create them regularly make adjustments to compensate for new scripts and other methods webmasters use to protect their sites' email addresses from harvesters? What are the best, most user-friendly means of keeping the harvesters at bay? I'm at a point with my site right now where the spam is getting pretty bad, so if there's a way to reduce it that would be great.

[kwasher]

<script language="JavaScript"><!--
// hide script
var sb_domain = "domain.com"
var sb_user = "emailusername"
var sb_recipient = sb_user + "@" + sb_domain
var sb_url = "mailto:" + sb_recipient
document.write(sb_recipient.link(sb_url));
// --></script>

replace domain.com with your domain

replace emailusername with your .. well, email username

[Dreamquick]

Also see the following thread, I personally feel the techniques the Hiveware guys are using are infinitely more robust than the majority of the "generic" javascript hacks which have the potential to be easily broken with simple, low processing cost, find and replace logic.

They cracked "name (at) example.com" and other such mungs (including my favourite trick - ASCII encoding) precisely because they could be broken using a "low cost" attack to neutralise the defence.

[webmasterworld.com...]

-Tony

[nalin]

If you have access to apache there mod_rewrite - basically you set your server up in such a manner that it contains a robots.txt and a honeypot (a disallowed page), and kill access from robots that fetch the honeypot, as there are numerous threads with example rule etc. on it I will not elaborate.

I have found this invaluable.