<?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/"
	
xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#"

	>
<channel>
	<title>Comments on: Domain Return Address in a Spam Run</title>
	<atom:link href="/2007/08/20/domain-return-address-in-a-spam-run/feed/" rel="self" type="application/rss+xml" />
	<link>/2007/08/20/domain-return-address-in-a-spam-run/</link>
	<description>Tips and tricks to get technology to work for you, by Michael Boyd Clark</description>
	<lastBuildDate>Sat, 20 Feb 2016 14:14:51 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: Mike Cardwell</title>
		<link>/2007/08/20/domain-return-address-in-a-spam-run/comment-page-1/#comment-13792</link>
		<dc:creator><![CDATA[Mike Cardwell]]></dc:creator>
		<pubDate>Mon, 20 Aug 2007 13:43:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.planetmike.com/journal/2007/08/20/domain-return-address-in-a-spam-run/#comment-13792</guid>
		<description><![CDATA[I have a user on my system with a catchall. This happens fairly regularly to him. So I set up Bounce Address Tag Validation, then limited null senders to one recipient, and performed a BATV check after the client submits DATA, and before responding with a 354. Problem solved.]]></description>
		<content:encoded><![CDATA[<p>I have a user on my system with a catchall. This happens fairly regularly to him. So I set up Bounce Address Tag Validation, then limited null senders to one recipient, and performed a BATV check after the client submits DATA, and before responding with a 354. Problem solved.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
