<?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: What the heck is RFC Compliant?</title>
	<atom:link href="http://www.jeffwoelker.com/2006/11/26/what-the-heck-is-rfc-compliant/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.jeffwoelker.com/2006/11/26/what-the-heck-is-rfc-compliant/</link>
	<description>Jeff Woelker&#039;s Home for Search Marketing, Social Media, Chicago, and Life on the North Side</description>
	<lastBuildDate>Fri, 10 Sep 2010 19:46:35 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Taylor</title>
		<link>http://www.jeffwoelker.com/2006/11/26/what-the-heck-is-rfc-compliant/comment-page-1/#comment-11448</link>
		<dc:creator>Taylor</dc:creator>
		<pubDate>Thu, 01 Apr 2010 14:58:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.jeffwoelker.com/2006/11/26/what-the-heck-is-rfc-complaint/#comment-11448</guid>
		<description>Thanks,

That was very informative, concise, and enjoyable to read.</description>
		<content:encoded><![CDATA[<p>Thanks,</p>
<p>That was very informative, concise, and enjoyable to read.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Itelica</title>
		<link>http://www.jeffwoelker.com/2006/11/26/what-the-heck-is-rfc-compliant/comment-page-1/#comment-10974</link>
		<dc:creator>Itelica</dc:creator>
		<pubDate>Fri, 06 Mar 2009 13:02:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.jeffwoelker.com/2006/11/26/what-the-heck-is-rfc-complaint/#comment-10974</guid>
		<description>You&#039;re completely wrong. The vast majority of Spam sending machines are infected PCs (zombies) which are not RFC compliant. That’s precisely why mail servers are increasingly implementing RFC compliance when receiving mail. It helps reduce Spam. So if you “don’t care” whether you are RFC compliant or not there is good chance your mail will get lumped with all the other non-RFC compliant spam sending machines and rejected.

Done and done.</description>
		<content:encoded><![CDATA[<p>You&#8217;re completely wrong. The vast majority of Spam sending machines are infected PCs (zombies) which are not RFC compliant. That’s precisely why mail servers are increasingly implementing RFC compliance when receiving mail. It helps reduce Spam. So if you “don’t care” whether you are RFC compliant or not there is good chance your mail will get lumped with all the other non-RFC compliant spam sending machines and rejected.</p>
<p>Done and done.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: juand</title>
		<link>http://www.jeffwoelker.com/2006/11/26/what-the-heck-is-rfc-compliant/comment-page-1/#comment-20</link>
		<dc:creator>juand</dc:creator>
		<pubDate>Fri, 29 Dec 2006 20:49:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.jeffwoelker.com/2006/11/26/what-the-heck-is-rfc-complaint/#comment-20</guid>
		<description>I see your point, in the sense that complying with a standard does not necessarily determines whether something works or not. However, standards were created to guarantee that 2 applications can speak the same language and ensure data gets from side to side properly. 

On top of that, your points 2 and 3 are completely irrelevant to what the RFC is. I would rather qualify those are e-mail ethics or perhaps laws in some countries.

So the fact that scammers are trying to comply with the e-mail standard does not really diminish the importance of standard protocols. In addition, RFC compliance is only a small part of the set of rules most spam filters use; Things like word and sentence structure, network sources and black lists play a much larger role in the process.</description>
		<content:encoded><![CDATA[<p>I see your point, in the sense that complying with a standard does not necessarily determines whether something works or not. However, standards were created to guarantee that 2 applications can speak the same language and ensure data gets from side to side properly. </p>
<p>On top of that, your points 2 and 3 are completely irrelevant to what the RFC is. I would rather qualify those are e-mail ethics or perhaps laws in some countries.</p>
<p>So the fact that scammers are trying to comply with the e-mail standard does not really diminish the importance of standard protocols. In addition, RFC compliance is only a small part of the set of rules most spam filters use; Things like word and sentence structure, network sources and black lists play a much larger role in the process.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
