<?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: FreshBooks now supports SPF</title>
	<atom:link href="http://www.freshbooks.com/blog/2008/09/09/freshbooks-now-supports-spf/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.freshbooks.com/blog/2008/09/09/freshbooks-now-supports-spf/</link>
	<description>A blog about our thoughts on entrepreneurship, teamwork, our services, the Web and anything we find interesting.</description>
	<lastBuildDate>Sat, 21 Nov 2009 07:27:46 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Henning Geiler</title>
		<link>http://www.freshbooks.com/blog/2008/09/09/freshbooks-now-supports-spf/comment-page-1/#comment-64551</link>
		<dc:creator>Henning Geiler</dc:creator>
		<pubDate>Sat, 04 Oct 2008 14:26:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.freshbooks.com/?p=1716#comment-64551</guid>
		<description>Hello Kevin and Scott. Thank you very much for your help. I did as per Scott&#039;s suggestion, ran a 3rd party validation tool, and it seems to be working very well.</description>
		<content:encoded><![CDATA[<p>Hello Kevin and Scott. Thank you very much for your help. I did as per Scott&#8217;s suggestion, ran a 3rd party validation tool, and it seems to be working very well.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott Girard</title>
		<link>http://www.freshbooks.com/blog/2008/09/09/freshbooks-now-supports-spf/comment-page-1/#comment-64533</link>
		<dc:creator>Scott Girard</dc:creator>
		<pubDate>Wed, 01 Oct 2008 03:38:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.freshbooks.com/?p=1716#comment-64533</guid>
		<description>Here&#039;s another helpful page that discusses using multiple include: mechanisms.

http://www.schlitt.net/spf/spf_classic/draft-schlitt-spf-classic-02.html#mech-include</description>
		<content:encoded><![CDATA[<p>Here&#8217;s another helpful page that discusses using multiple include: mechanisms.</p>
<p><a href="http://www.schlitt.net/spf/spf_classic/draft-schlitt-spf-classic-02.html#mech-include" rel="nofollow">http://www.schlitt.net/spf/spf_classic/draft-schlitt-spf-classic-02.html#mech-include</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott Girard</title>
		<link>http://www.freshbooks.com/blog/2008/09/09/freshbooks-now-supports-spf/comment-page-1/#comment-64532</link>
		<dc:creator>Scott Girard</dc:creator>
		<pubDate>Wed, 01 Oct 2008 03:23:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.freshbooks.com/?p=1716#comment-64532</guid>
		<description>Um, I think Henning&#039;s record should look like this:

v=spf1 include:72smtp.whatever.com include:_spf.freshbooks.com ~all

The ~all should go at the end of the record and multiple include: statements are valid.

See here: 
http://old.openspf.org/mechanisms.html and here: 
http://www.spamresource.com/2006/09/sender-policy-framework-spf-trick-of.html and here:
http://www.kitterman.com/spf/validate.html</description>
		<content:encoded><![CDATA[<p>Um, I think Henning&#8217;s record should look like this:</p>
<p>v=spf1 include:72smtp.whatever.com include:_spf.freshbooks.com ~all</p>
<p>The ~all should go at the end of the record and multiple include: statements are valid.</p>
<p>See here:<br />
<a href="http://old.openspf.org/mechanisms.html" rel="nofollow">http://old.openspf.org/mechanisms.html</a> and here:<br />
<a href="http://www.spamresource.com/2006/09/sender-policy-framework-spf-trick-of.html" rel="nofollow">http://www.spamresource.com/2006/09/sender-policy-framework-spf-trick-of.html</a> and here:<br />
<a href="http://www.kitterman.com/spf/validate.html" rel="nofollow">http://www.kitterman.com/spf/validate.html</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kevin</title>
		<link>http://www.freshbooks.com/blog/2008/09/09/freshbooks-now-supports-spf/comment-page-1/#comment-64524</link>
		<dc:creator>Kevin</dc:creator>
		<pubDate>Tue, 30 Sep 2008 15:56:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.freshbooks.com/?p=1716#comment-64524</guid>
		<description>Hi Henning,

You can add the snippet Rich provided to the end of your existing txt record.  So, if your current record said:

&lt;code&gt;v=spf1 include72smtp.whatever.com ~all&lt;/code&gt;

You should update it to say:

&lt;code&gt;v=spf1 include72smtp.whatever.com ~all include:_spf.freshbooks.com&lt;/code&gt;

Below is a link to the documentation from the SPF project, which explains what each of these directives means.

http://www.openspf.org/SPF_Record_Syntax</description>
		<content:encoded><![CDATA[<p>Hi Henning,</p>
<p>You can add the snippet Rich provided to the end of your existing txt record.  So, if your current record said:</p>
<p><code>v=spf1 include72smtp.whatever.com ~all</code></p>
<p>You should update it to say:</p>
<p><code>v=spf1 include72smtp.whatever.com ~all include:_spf.freshbooks.com</code></p>
<p>Below is a link to the documentation from the SPF project, which explains what each of these directives means.</p>
<p><a href="http://www.openspf.org/SPF_Record_Syntax" rel="nofollow">http://www.openspf.org/SPF_Record_Syntax</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Henning Geiler</title>
		<link>http://www.freshbooks.com/blog/2008/09/09/freshbooks-now-supports-spf/comment-page-1/#comment-64519</link>
		<dc:creator>Henning Geiler</dc:creator>
		<pubDate>Tue, 30 Sep 2008 03:24:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.freshbooks.com/?p=1716#comment-64519</guid>
		<description>I don&#039;t understand the working of this. How is the DNS record supposed to look like. I have set up SPF records for two other external mail servers and in both instances I was instructed to create DNS record or the type TXT and then add the following line: v=spf1 include72smtp.whatever.com ~all. How does this go together with the snippet of code you posted in your blog? Would it be possible to create the TXT record and then add the following for freshbooks.com? 
v=spf1 include72spf.freshbooks.com ~all</description>
		<content:encoded><![CDATA[<p>I don&#8217;t understand the working of this. How is the DNS record supposed to look like. I have set up SPF records for two other external mail servers and in both instances I was instructed to create DNS record or the type TXT and then add the following line: v=spf1 include72smtp.whatever.com ~all. How does this go together with the snippet of code you posted in your blog? Would it be possible to create the TXT record and then add the following for freshbooks.com?<br />
v=spf1 include72spf.freshbooks.com ~all</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rich Lafferty</title>
		<link>http://www.freshbooks.com/blog/2008/09/09/freshbooks-now-supports-spf/comment-page-1/#comment-64459</link>
		<dc:creator>Rich Lafferty</dc:creator>
		<pubDate>Sun, 14 Sep 2008 17:03:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.freshbooks.com/?p=1716#comment-64459</guid>
		<description>Fixed, thanks!</description>
		<content:encoded><![CDATA[<p>Fixed, thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: bri</title>
		<link>http://www.freshbooks.com/blog/2008/09/09/freshbooks-now-supports-spf/comment-page-1/#comment-64457</link>
		<dc:creator>bri</dc:creator>
		<pubDate>Sun, 14 Sep 2008 06:04:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.freshbooks.com/?p=1716#comment-64457</guid>
		<description>It&#039;s &quot;sender policy framework&quot;.</description>
		<content:encoded><![CDATA[<p>It&#8217;s &#8220;sender policy framework&#8221;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe</title>
		<link>http://www.freshbooks.com/blog/2008/09/09/freshbooks-now-supports-spf/comment-page-1/#comment-64426</link>
		<dc:creator>Joe</dc:creator>
		<pubDate>Wed, 10 Sep 2008 05:14:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.freshbooks.com/?p=1716#comment-64426</guid>
		<description>Good info to know!  I appreciate the extra effort to explain it, rather than just &quot;yes that&#039;s correct&quot;.</description>
		<content:encoded><![CDATA[<p>Good info to know!  I appreciate the extra effort to explain it, rather than just &#8220;yes that&#8217;s correct&#8221;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rich Lafferty</title>
		<link>http://www.freshbooks.com/blog/2008/09/09/freshbooks-now-supports-spf/comment-page-1/#comment-64425</link>
		<dc:creator>Rich Lafferty</dc:creator>
		<pubDate>Wed, 10 Sep 2008 02:18:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.freshbooks.com/?p=1716#comment-64425</guid>
		<description>Joe: Yep! That&#039;s the standard for &quot;this DNS record only exists as an SPF record for other domains to include&quot;. 

The underscore prevents the possibility of colliding with a hostname (since hostnames can&#039;t contain underscores). That&#039;s why they&#039;re used in SRV records, too.</description>
		<content:encoded><![CDATA[<p>Joe: Yep! That&#8217;s the standard for &#8220;this DNS record only exists as an SPF record for other domains to include&#8221;. </p>
<p>The underscore prevents the possibility of colliding with a hostname (since hostnames can&#8217;t contain underscores). That&#8217;s why they&#8217;re used in SRV records, too.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe</title>
		<link>http://www.freshbooks.com/blog/2008/09/09/freshbooks-now-supports-spf/comment-page-1/#comment-64424</link>
		<dc:creator>Joe</dc:creator>
		<pubDate>Wed, 10 Sep 2008 02:07:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.freshbooks.com/?p=1716#comment-64424</guid>
		<description>Just wanted to make sure that the underscrore in _spf was supposed to be there.</description>
		<content:encoded><![CDATA[<p>Just wanted to make sure that the underscrore in _spf was supposed to be there.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
