<?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: Challenge/Response Email Verification</title>
	<atom:link href="http://ben.dechrau.com/2007/04/27/challengeresponse-email-verification/feed" rel="self" type="application/rss+xml" />
	<link>http://ben.dechrau.com/2007/04/27/challengeresponse-email-verification</link>
	<description>Programmer, Property Tycoon, Media Mogul</description>
	<lastBuildDate>Mon, 30 Aug 2010 16:18:52 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Ben Balbo</title>
		<link>http://ben.dechrau.com/2007/04/27/challengeresponse-email-verification/comment-page-1#comment-3957</link>
		<dc:creator>Ben Balbo</dc:creator>
		<pubDate>Sun, 29 Apr 2007 23:23:23 +0000</pubDate>
		<guid isPermaLink="false">http://benbalbo.com/2007/04/27/challengeresponse-email-verification/#comment-3957</guid>
		<description>Regarding the open relay, I&#039;m sure it won&#039;t be long until the open relay is added to the black-list, so I&#039;m not too worried about that scenario.

The fight against spam is an ever evolving one, and I&#039;m sure grey-listing will be rendered useless at some point, as the spammers keep circumventing current mechanisms. I&#039;m not sure what the next step is after grey-listing is. I hope it&#039;s not CREV, which also has its loopholes.

&lt;a href=&quot;http://en.wikipedia.org/wiki/Sender_Policy_Framework&quot; rel=&quot;nofollow&quot;&gt;SPF&lt;/a&gt; is another option, but requires adoption in all domain records to be truly effective. There is a firm plan for my hosting company to support SPF in all domains it hosts, but if your timeline is accurate, this might be happening sooner than expected :-)</description>
		<content:encoded><![CDATA[<p>Regarding the open relay, I&#8217;m sure it won&#8217;t be long until the open relay is added to the black-list, so I&#8217;m not too worried about that scenario.</p>
<p>The fight against spam is an ever evolving one, and I&#8217;m sure grey-listing will be rendered useless at some point, as the spammers keep circumventing current mechanisms. I&#8217;m not sure what the next step is after grey-listing is. I hope it&#8217;s not CREV, which also has its loopholes.</p>
<p><a href="http://en.wikipedia.org/wiki/Sender_Policy_Framework" rel="nofollow">SPF</a> is another option, but requires adoption in all domain records to be truly effective. There is a firm plan for my hosting company to support SPF in all domains it hosts, but if your timeline is accurate, this might be happening sooner than expected <img src='http://ben.dechrau.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: anonymous</title>
		<link>http://ben.dechrau.com/2007/04/27/challengeresponse-email-verification/comment-page-1#comment-3856</link>
		<dc:creator>anonymous</dc:creator>
		<pubDate>Fri, 27 Apr 2007 07:18:11 +0000</pubDate>
		<guid isPermaLink="false">http://benbalbo.com/2007/04/27/challengeresponse-email-verification/#comment-3856</guid>
		<description>Although I agree this is a cleaner solution I still have my reservations about the effectiveness.

Matti Aarnio is currently doing the same Post-greying technique within the Linux kernel mailing list and although it works to a degree, it still has its problems.

I&#039;ll explain one I can think of. Sam sends Bob an email. When he does this he uses an open relay (one of the most common spamming ways). Sam has now just broken the whole Post-greying because the open-relay will respond to the wait packet and resend when required (This is normally what happens anyway when a spammer hits an open relay because the quantity of emails exceeds the systems max throughput.

It will however work on a standard drone system (normally desktops that have been compromised and rigged to send mass emails), but only for a little while. Most spam bots now use a trigger method to reiterate through the list after all the email addresses have been posted.

It will (Matti says about another 50-100 days, I say about a month) soon be completely redundant.</description>
		<content:encoded><![CDATA[<p>Although I agree this is a cleaner solution I still have my reservations about the effectiveness.</p>
<p>Matti Aarnio is currently doing the same Post-greying technique within the Linux kernel mailing list and although it works to a degree, it still has its problems.</p>
<p>I&#8217;ll explain one I can think of. Sam sends Bob an email. When he does this he uses an open relay (one of the most common spamming ways). Sam has now just broken the whole Post-greying because the open-relay will respond to the wait packet and resend when required (This is normally what happens anyway when a spammer hits an open relay because the quantity of emails exceeds the systems max throughput.</p>
<p>It will however work on a standard drone system (normally desktops that have been compromised and rigged to send mass emails), but only for a little while. Most spam bots now use a trigger method to reiterate through the list after all the email addresses have been posted.</p>
<p>It will (Matti says about another 50-100 days, I say about a month) soon be completely redundant.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
