<?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 5 - A bit more on RFC 3464</title><link>http://blogs.msdn.com/tzink/archive/2008/07/07/the-problem-of-backscatter-part-5-a-bit-more-on-rfc-3464.aspx</link><description>Continuing on from my previous post about the format of Delivery Status Notifications, a DSN must be addressed to the return address from the transport envelope which accompanied the original message for which the DSN was generated. (For a message that</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 5 - A bit more on RFC 3464</title><link>http://blogs.msdn.com/tzink/archive/2008/07/07/the-problem-of-backscatter-part-5-a-bit-more-on-rfc-3464.aspx#8704489</link><pubDate>Tue, 08 Jul 2008 01:12:36 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8704489</guid><dc:creator>a-foton &amp;raquo; The problem of backscatter, part 5 - A bit more on RFC 3464</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-5-a-bit-more-on-rfc-3464/"&gt;http://blog.a-foton.ru/2008/07/the-problem-of-backscatter-part-5-a-bit-more-on-rfc-3464/&lt;/a&gt;&lt;/p&gt;
</description></item></channel></rss>