<?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: Stopping Web to Lead Spam</title>
	<atom:link href="http://sfdc.arrowpointe.com/2007/01/31/stopping-web-to-lead-spam-poor-mans-way/feed/" rel="self" type="application/rss+xml" />
	<link>http://sfdc.arrowpointe.com/2007/01/31/stopping-web-to-lead-spam-poor-mans-way/</link>
	<description>Authored by Scott Hemmeter of Arrowpointe Corp, this blog is written from the perspective of a Salesforce.com solution provider and contains information on Arrowpointe's AppExchange products as well as tips, findings, sample code, functionality wishes, etc.</description>
	<pubDate>Wed, 20 Aug 2008 18:17:02 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: &#160; Salesforce spam: fixing web-to-lead&#160;by&#160;tins ::: Rick Klau&#8217;s weblog</title>
		<link>http://sfdc.arrowpointe.com/2007/01/31/stopping-web-to-lead-spam-poor-mans-way/#comment-35871</link>
		<dc:creator>&#160; Salesforce spam: fixing web-to-lead&#160;by&#160;tins ::: Rick Klau&#8217;s weblog</dc:creator>
		<pubDate>Tue, 04 Sep 2007 13:01:38 +0000</pubDate>
		<guid isPermaLink="false">http://sfdc.arrowpointe.com/2007/01/31/stopping-web-to-lead-spam-poor-mans-way/#comment-35871</guid>
		<description>[...] at Arrowpointe for their suggestions over at Perspectives on Salesforce blog. Two weeks ago, they documented their approach, which is conceptually what we&#8217;ve [...]</description>
		<content:encoded><![CDATA[<p>[...] at Arrowpointe for their suggestions over at Perspectives on Salesforce blog. Two weeks ago, they documented their approach, which is conceptually what we&#8217;ve [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marco Casalaina</title>
		<link>http://sfdc.arrowpointe.com/2007/01/31/stopping-web-to-lead-spam-poor-mans-way/#comment-17998</link>
		<dc:creator>Marco Casalaina</dc:creator>
		<pubDate>Wed, 02 May 2007 23:45:35 +0000</pubDate>
		<guid isPermaLink="false">http://sfdc.arrowpointe.com/2007/01/31/stopping-web-to-lead-spam-poor-mans-way/#comment-17998</guid>
		<description>Here's an additional idea:

Assuming these spammers are not submitting via your form really, but just capturing your orgId and submitting forms directly to SFDC, you can add a custom field to Lead (or Case in Web To Case) -- let's call the field NoSpam.  Then add the NoSpam field to your Web To X page as a hidden input field.  Add an OnClick to the submit button which triggers some Javascript that fills that field with a set value (like "nospam") (but come up with something else at random so spammers don't just figure it out).  Then you can easily detect if a human actually clicked the Submit button -- only humans will have the expected value in the NoSpam field!  So your validation rule would just be:

AND (ISPICKVAL ( Origin , "Web") , NoSpam__c"nospam")

This won't defeat the most dedicated spammers who actually automate clicks on your forms, but it will work against spambots that just blindly submit form data without respect to form contents and Javascript.  You could use this in concert with the validation rule described above to get a decent decrease in overall spam volume.</description>
		<content:encoded><![CDATA[<p>Here&#8217;s an additional idea:</p>
<p>Assuming these spammers are not submitting via your form really, but just capturing your orgId and submitting forms directly to SFDC, you can add a custom field to Lead (or Case in Web To Case) &#8212; let&#8217;s call the field NoSpam.  Then add the NoSpam field to your Web To X page as a hidden input field.  Add an OnClick to the submit button which triggers some Javascript that fills that field with a set value (like &#8220;nospam&#8221;) (but come up with something else at random so spammers don&#8217;t just figure it out).  Then you can easily detect if a human actually clicked the Submit button &#8212; only humans will have the expected value in the NoSpam field!  So your validation rule would just be:</p>
<p>AND (ISPICKVAL ( Origin , &#8220;Web&#8221;) , NoSpam__c&#8221;nospam&#8221;)</p>
<p>This won&#8217;t defeat the most dedicated spammers who actually automate clicks on your forms, but it will work against spambots that just blindly submit form data without respect to form contents and Javascript.  You could use this in concert with the validation rule described above to get a decent decrease in overall spam volume.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott Hemmeter</title>
		<link>http://sfdc.arrowpointe.com/2007/01/31/stopping-web-to-lead-spam-poor-mans-way/#comment-8832</link>
		<dc:creator>Scott Hemmeter</dc:creator>
		<pubDate>Tue, 20 Feb 2007 19:43:33 +0000</pubDate>
		<guid isPermaLink="false">http://sfdc.arrowpointe.com/2007/01/31/stopping-web-to-lead-spam-poor-mans-way/#comment-8832</guid>
		<description>JRoe:  
I forgot to put &lt; code &gt; tags around the code in the blog post.  Without it, Wordpress rendered the double-quote characters as a more readable double-quote character.  When you copied it into Salesforce, it saw an error because the double-quote characters were invalid.  

Try copying it again.  It should work.</description>
		<content:encoded><![CDATA[<p>JRoe:<br />
I forgot to put < code > tags around the code in the blog post.  Without it, Wordpress rendered the double-quote characters as a more readable double-quote character.  When you copied it into Salesforce, it saw an error because the double-quote characters were invalid.  </p>
<p>Try copying it again.  It should work.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JRoe</title>
		<link>http://sfdc.arrowpointe.com/2007/01/31/stopping-web-to-lead-spam-poor-mans-way/#comment-8829</link>
		<dc:creator>JRoe</dc:creator>
		<pubDate>Tue, 20 Feb 2007 19:09:13 +0000</pubDate>
		<guid isPermaLink="false">http://sfdc.arrowpointe.com/2007/01/31/stopping-web-to-lead-spam-poor-mans-way/#comment-8829</guid>
		<description>This is a great idea.  This type of spam nearly shut down one site on which I had salesforce deployed.  

I entered your validation script and for some reason I keep getting a syntax error in the first 2 lines.  Any thoughts as to why?</description>
		<content:encoded><![CDATA[<p>This is a great idea.  This type of spam nearly shut down one site on which I had salesforce deployed.  </p>
<p>I entered your validation script and for some reason I keep getting a syntax error in the first 2 lines.  Any thoughts as to why?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
