<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>The problem of backscatter, part 9 - Block it with content analysis</title><link>http://blogs.msdn.com/tzink/archive/2008/07/13/the-problem-of-backscatter-part-9-block-it-with-content-analysis.aspx</link><description>We can see how backscatter is a problem, so how do we go about stopping it?&amp;#160; What are some of the techniques we can employ to keep it out of our inboxes? One such technique is to block all NDR messages, or at least tag phrases and characteristics</description><dc:language>en</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>a-foton &amp;raquo; The problem of backscatter, part 9 - Block it with content analysis</title><link>http://blogs.msdn.com/tzink/archive/2008/07/13/the-problem-of-backscatter-part-9-block-it-with-content-analysis.aspx#8730896</link><pubDate>Mon, 14 Jul 2008 08:34:51 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8730896</guid><dc:creator>a-foton &amp;raquo; The problem of backscatter, part 9 - Block it with content analysis</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://blog.a-foton.ru/2008/07/the-problem-of-backscatter-part-9-block-it-with-content-analysis/"&gt;http://blog.a-foton.ru/2008/07/the-problem-of-backscatter-part-9-block-it-with-content-analysis/&lt;/a&gt;&lt;/p&gt;
</description></item><item><title>re: The problem of backscatter, part 9 - Block it with content analysis</title><link>http://blogs.msdn.com/tzink/archive/2008/07/13/the-problem-of-backscatter-part-9-block-it-with-content-analysis.aspx#8731754</link><pubDate>Mon, 14 Jul 2008 20:05:36 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8731754</guid><dc:creator>Lee Maguire</dc:creator><description>&lt;p&gt;By far the most effective filter for DSN messages is&lt;/p&gt;
&lt;p&gt;going to be to match RFC3464 bounces:&lt;/p&gt;
&lt;p&gt; if sender is &amp;lt;&amp;gt; &lt;/p&gt;
&lt;p&gt; and Content-Type: contains &amp;quot;multipart/report&amp;quot;&lt;/p&gt;
&lt;p&gt;I have mailserver filters that identify and tag different DSN types. &amp;nbsp;For example, exim generated bounces can be identified by the inclusion of an &lt;/p&gt;
&lt;p&gt;&amp;quot;X-Failed-Recipients:&amp;quot; header.&lt;/p&gt;
&lt;p&gt;Based purely on the backscatter I've received so far this week:&lt;/p&gt;
&lt;p&gt;249 RFC3464&lt;/p&gt;
&lt;p&gt;43 nonstandard (exim)&lt;/p&gt;
&lt;p&gt;38 nonstandard (qmail)&lt;/p&gt;
&lt;p&gt;6 nonstandard (other)&lt;/p&gt;
&lt;p&gt;5 nonstandard (exchange)&lt;/p&gt;
&lt;p&gt;3 unknown&lt;/p&gt;
&lt;p&gt;2 nonstandard (smtp32)&lt;/p&gt;
&lt;p&gt;1 nonstandard (type1)&lt;/p&gt;
&lt;p&gt;1 nonstandard (old sendmail)&lt;/p&gt;
&lt;p&gt;+ 11 other responses (DSNs not using null senders, confirmation requests, googlegroups.com nonsense.)&lt;/p&gt;
</description></item><item><title>re: The problem of backscatter, part 9 - Block it with content analysis</title><link>http://blogs.msdn.com/tzink/archive/2008/07/13/the-problem-of-backscatter-part-9-block-it-with-content-analysis.aspx#8731782</link><pubDate>Mon, 14 Jul 2008 20:19:54 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8731782</guid><dc:creator>Lee Maguire</dc:creator><description>&lt;p&gt;Also, every time a null sender is used for connection, a check is made on the DNSBL &lt;a rel="nofollow" target="_new" href="http://www.backscatterer.org/?target=backscatter"&gt;http://www.backscatterer.org/?target=backscatter&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;and positive hits are tagged on the mail.&lt;/p&gt;
&lt;p&gt;Currently 133 hits out of 347 backscatter mails.&lt;/p&gt;
</description></item><item><title>re: The problem of backscatter, part 9 - Block it with content analysis</title><link>http://blogs.msdn.com/tzink/archive/2008/07/13/the-problem-of-backscatter-part-9-block-it-with-content-analysis.aspx#8733597</link><pubDate>Tue, 15 Jul 2008 18:27:50 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8733597</guid><dc:creator>Frank</dc:creator><description>&lt;p&gt;Other uses of empty reverse paths include auto-responders (RFC 3834), e.g., vacation mails (RFC 5230), and message disposition notifications (RFC 3798). Apart from being difficult blocking all bounces including good bounces is a dubious plan, mail reliability depends on error reports. Even black-listed &amp;quot;backscatterers&amp;quot; can send good (wanted) mails with an empty reverse path. Blocking known &amp;quot;backscatterers&amp;quot; might work for senders never sending mail to them. But where senders are organized enough to guarantee this they can likely also deploy BATV and/or SPF FAIL without losing good bounces.&lt;/p&gt;
</description></item></channel></rss>