<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/MU" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Sender ID: Tips for Creating Your SPF Record</title>
	<link>http://blogs.msexchange.org/silva/2007/09/11/sender-id-tips-for-creating-your-spf-record/</link>
	<description>Rui Silva's blog contains everything about Exchange and messaging in general, news, technical articles, and information about the new trends: mobility, unified messaging and PowerShell. With extensive Microsoft Exchange experience, since version 5.0, this blog contains his personal experiences and tips any email administrator should know in order to keep Exchange Server functioning as one of the best email messaging solutions on the market today.</description>
	<pubDate>Tue, 16 Mar 2010 05:56:42 +0000</pubDate>
	<generator>http://wordpress.org/?v=MU</generator>

	<item>
		<title>by: Rui J.M. Silva Blog &#187; Blog Archive &#187; The Sender ID Framework: Protecting Your Brand, Users &#38; Infrastructure</title>
		<link>http://blogs.msexchange.org/silva/2007/09/11/sender-id-tips-for-creating-your-spf-record/#comment-20705</link>
		<pubDate>Wed, 12 Sep 2007 09:47:51 +0000</pubDate>
		<guid>http://blogs.msexchange.org/silva/2007/09/11/sender-id-tips-for-creating-your-spf-record/#comment-20705</guid>
					<description>[...] After Microsoft refreshed the document Sender ID: Tips for Creating Your SPF Record, the guys from Redmond have just released a brand new one: The Sender ID Framework: Protecting Your Brand, Users &amp;#38; Infrastructure, which describes the benefits of implementing Sender ID. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] After Microsoft refreshed the document Sender ID: Tips for Creating Your SPF Record, the guys from Redmond have just released a brand new one: The Sender ID Framework: Protecting Your Brand, Users &amp; Infrastructure, which describes the benefits of implementing Sender ID. [&#8230;]
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
