<?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: Any help for an odd qmail spam exploit?</title>
	<atom:link href="http://www.seo-theory.com/2008/03/16/any-help-for-an-odd-qmail-spam-exploit/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.seo-theory.com/2008/03/16/any-help-for-an-odd-qmail-spam-exploit/</link>
	<description>Algorithm analysis, Web community relationship analysis, SEO practices and techniques, industry news, etc.</description>
	<lastBuildDate>Sat, 04 Sep 2010 04:55:11 -0400</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Michael Martinez</title>
		<link>http://www.seo-theory.com/2008/03/16/any-help-for-an-odd-qmail-spam-exploit/comment-page-1/#comment-690</link>
		<dc:creator>Michael Martinez</dc:creator>
		<pubDate>Mon, 17 Mar 2008 21:24:24 +0000</pubDate>
		<guid isPermaLink="false">http://seo-theory.com/wordpress/2008/03/16/any-help-for-an-odd-qmail-spam-exploit/#comment-690</guid>
		<description>Well, researching Daniel Bernstein&#039;s brain child is no fun.  He&#039;s apparently won some hearts and lost a few.

Not being versed in Qmail&#039;s intricacies, I have no idea of whether the answer I am seeking is buried in it but someone went to a lot of trouble up until a couple of years ago to track down all reported issues with Qmail. &lt;a href=&quot;http://www-dt.e-technik.uni-dortmund.de/~ma/qmail-bugs.html&quot; target=&quot;_blank&quot; rel=&quot;nofollow&quot;&gt;Qmail bugs&lt;/a&gt; is an interesting read.

If you are curious about what the exploit looks like, I did finally find someone who reported it last month.  To date, no one has replied in that forum with any information.

&lt;a href=&quot;http://www.webhostingtalk.com/showthread.php?t=674813&quot; target=&quot;_blank&quot; rel=&quot;nofollow&quot;&gt;What a Qmail spam exploit looks like&lt;/a&gt;

It ain&#039;t pretty.

But the most widely known (and criticized) exploit appears to be based on bouncing messages off a Qmail server.  I THINK I have now blocked that one too with the white listing through hosts.deny and hosts.allow but this is such a pain to keep up with.  I&#039;ve already added more than 150 domains to the list and I am sure a large percentage of people who could once reach me via email will no longer be able to unless they use the Xenite contact form.</description>
		<content:encoded><![CDATA[<p>Well, researching Daniel Bernstein&#8217;s brain child is no fun.  He&#8217;s apparently won some hearts and lost a few.</p>
<p>Not being versed in Qmail&#8217;s intricacies, I have no idea of whether the answer I am seeking is buried in it but someone went to a lot of trouble up until a couple of years ago to track down all reported issues with Qmail. <a href="http://www-dt.e-technik.uni-dortmund.de/~ma/qmail-bugs.html" target="_blank" rel="nofollow">Qmail bugs</a> is an interesting read.</p>
<p>If you are curious about what the exploit looks like, I did finally find someone who reported it last month.  To date, no one has replied in that forum with any information.</p>
<p><a href="http://www.webhostingtalk.com/showthread.php?t=674813" target="_blank" rel="nofollow">What a Qmail spam exploit looks like</a></p>
<p>It ain&#8217;t pretty.</p>
<p>But the most widely known (and criticized) exploit appears to be based on bouncing messages off a Qmail server.  I THINK I have now blocked that one too with the white listing through hosts.deny and hosts.allow but this is such a pain to keep up with.  I&#8217;ve already added more than 150 domains to the list and I am sure a large percentage of people who could once reach me via email will no longer be able to unless they use the Xenite contact form.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
