
<?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: Secure Contact Forms</title>
	<atom:link href="http://kennsarah.net/2005/09/14/secure-contact-forms/feed/" rel="self" type="application/rss+xml" />
	<link>http://kennsarah.net/2005/09/14/secure-contact-forms/</link>
	<description>“...and every time she sneezes, I believe it&#039;s love... ”</description>
	<lastBuildDate>Mon, 26 Sep 2011 04:37:50 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Ken</title>
		<link>http://kennsarah.net/2005/09/14/secure-contact-forms/comment-page-1/#comment-1134</link>
		<dc:creator>Ken</dc:creator>
		<pubDate>Thu, 15 Sep 2005 16:56:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.kennsarah.net/?p=875#comment-1134</guid>
		<description>Mike, the main issue with this is that these attempts to spam are clogging our Church Administrator&#039;s inbox with emails from an address that would normally get a good amount of attention (say from people actually interested in our church or connecting with our staff).  

A captcha plugin would be an interesting idea.  They do have accessibility issues (they exclude blind people), but a lot of online companies use them.  Once we&#039;re done migrating to WordPress -- hopefully sometime this week -- I can see if that WordPress Contact Form plugin can help.</description>
		<content:encoded><![CDATA[<p>Mike, the main issue with this is that these attempts to spam are clogging our Church Administrator&#8217;s inbox with emails from an address that would normally get a good amount of attention (say from people actually interested in our church or connecting with our staff).  </p>
<p>A captcha plugin would be an interesting idea.  They do have accessibility issues (they exclude blind people), but a lot of online companies use them.  Once we&#8217;re done migrating to WordPress &#8212; hopefully sometime this week &#8212; I can see if that WordPress Contact Form plugin can help.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Bond</title>
		<link>http://kennsarah.net/2005/09/14/secure-contact-forms/comment-page-1/#comment-1133</link>
		<dc:creator>Mike Bond</dc:creator>
		<pubDate>Thu, 15 Sep 2005 12:23:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.kennsarah.net/?p=875#comment-1133</guid>
		<description>The contact form sends an email? And you&#039;re worried about spam email to people on your site?

Stop worrying about it. Let the users deal with their own spam. Spam happens and there are many ways to deal with it now.

Just make sure you are running the newest version and that you have any patches for that may address the bug that is being exploited. 

Alternatively you can use the wordpress plugin (i forget its name, sorry) that adds a field to forms that requires the user to type in the randomly generated image letters. Using things like that lead to various accessibility problems though, it also requires imagemagick (or compairable software) to be installed.</description>
		<content:encoded><![CDATA[<p>The contact form sends an email? And you&#8217;re worried about spam email to people on your site?</p>
<p>Stop worrying about it. Let the users deal with their own spam. Spam happens and there are many ways to deal with it now.</p>
<p>Just make sure you are running the newest version and that you have any patches for that may address the bug that is being exploited. </p>
<p>Alternatively you can use the wordpress plugin (i forget its name, sorry) that adds a field to forms that requires the user to type in the randomly generated image letters. Using things like that lead to various accessibility problems though, it also requires imagemagick (or compairable software) to be installed.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

