<?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: The secret to dealing with ISPs</title>
	<atom:link href="http://blog.wordtothewise.com/2009/09/the-secret-to-dealing-with-isps/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.wordtothewise.com/2009/09/the-secret-to-dealing-with-isps/</link>
	<description>Email, Delivery, Spam and more</description>
	<lastBuildDate>Thu, 18 Mar 2010 13:53:27 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Peter Blair</title>
		<link>http://blog.wordtothewise.com/2009/09/the-secret-to-dealing-with-isps/comment-page-1/#comment-2620</link>
		<dc:creator>Peter Blair</dc:creator>
		<pubDate>Wed, 21 Oct 2009 15:28:45 +0000</pubDate>
		<guid isPermaLink="false">http://blog.wordtothewise.com/?p=664#comment-2620</guid>
		<description>Remember that many ISPs leave the abuse desk emails/tickets to tier 1 support, who may not have the required training to fully understand your problem and why it&#039;s impacting you.

Please, have patience with us (Receivers). And, if you do navigate the gauntlet to contact abuse people higher up the escalation chain, I&#039;m sure that they&#039;re aware of their own problems withing their organization, but helpful criticism is always helpful -- just don&#039;t be a jerk about it.

Thanks for the great blog entry!  I&#039;ll be passing it around $WORK ( opensrs.com )</description>
		<content:encoded><![CDATA[<p>Remember that many ISPs leave the abuse desk emails/tickets to tier 1 support, who may not have the required training to fully understand your problem and why it&#8217;s impacting you.</p>
<p>Please, have patience with us (Receivers). And, if you do navigate the gauntlet to contact abuse people higher up the escalation chain, I&#8217;m sure that they&#8217;re aware of their own problems withing their organization, but helpful criticism is always helpful &#8212; just don&#8217;t be a jerk about it.</p>
<p>Thanks for the great blog entry!  I&#8217;ll be passing it around $WORK ( opensrs.com )</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John</title>
		<link>http://blog.wordtothewise.com/2009/09/the-secret-to-dealing-with-isps/comment-page-1/#comment-2621</link>
		<dc:creator>John</dc:creator>
		<pubDate>Wed, 14 Oct 2009 21:37:02 +0000</pubDate>
		<guid isPermaLink="false">http://blog.wordtothewise.com/?p=664#comment-2621</guid>
		<description>Great list. I would just add: Do not assume there is a problem on the ISP&#039;s side and do not assume that there are no problems on your own side. Going in with the attitude that you &quot;need&quot; the ISP to fix something is never a good idea.</description>
		<content:encoded><![CDATA[<p>Great list. I would just add: Do not assume there is a problem on the ISP&#8217;s side and do not assume that there are no problems on your own side. Going in with the attitude that you &#8220;need&#8221; the ISP to fix something is never a good idea.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Overusing ISP contacts at Word to the Wise</title>
		<link>http://blog.wordtothewise.com/2009/09/the-secret-to-dealing-with-isps/comment-page-1/#comment-2614</link>
		<dc:creator>Overusing ISP contacts at Word to the Wise</dc:creator>
		<pubDate>Wed, 07 Oct 2009 21:49:59 +0000</pubDate>
		<guid isPermaLink="false">http://blog.wordtothewise.com/?p=664#comment-2614</guid>
		<description>[...] I said in my The Secret To Dealing with ISPs post, the vast majority of issues can be handled on the sender side without involvement of anyone [...]</description>
		<content:encoded><![CDATA[<p>[...] I said in my The Secret To Dealing with ISPs post, the vast majority of issues can be handled on the sender side without involvement of anyone [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike</title>
		<link>http://blog.wordtothewise.com/2009/09/the-secret-to-dealing-with-isps/comment-page-1/#comment-2615</link>
		<dc:creator>Mike</dc:creator>
		<pubDate>Wed, 30 Sep 2009 19:45:52 +0000</pubDate>
		<guid isPermaLink="false">http://blog.wordtothewise.com/?p=664#comment-2615</guid>
		<description>Your reputation problem is that you&#039;re SPAMMERS.
This cannot be reapired.
Welcome to my blocklist.

[&lt;em&gt;&lt;strong&gt;Editor&#039;s note&lt;/strong&gt;: I normally wouldn&#039;t approve a comment like this because of the obviously forged email address and lack of useful content. But I can&#039;t figure out who this guy thinks is a spammer with an un-reapirable reputation. Me? Return Path? The irony of such a poorly written comment on a post about how to communicate more clearly is not lost on me, though.&lt;/em&gt;]</description>
		<content:encoded><![CDATA[<p>Your reputation problem is that you&#8217;re SPAMMERS.<br />
This cannot be reapired.<br />
Welcome to my blocklist.</p>
<p>[<em><strong>Editor's note</strong>: I normally wouldn't approve a comment like this because of the obviously forged email address and lack of useful content. But I can't figure out who this guy thinks is a spammer with an un-reapirable reputation. Me? Return Path? The irony of such a poorly written comment on a post about how to communicate more clearly is not lost on me, though.</em>]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: George Bilbrey</title>
		<link>http://blog.wordtothewise.com/2009/09/the-secret-to-dealing-with-isps/comment-page-1/#comment-2617</link>
		<dc:creator>George Bilbrey</dc:creator>
		<pubDate>Tue, 29 Sep 2009 23:48:44 +0000</pubDate>
		<guid isPermaLink="false">http://blog.wordtothewise.com/?p=664#comment-2617</guid>
		<description>This is a great guide.  If you are talking to ISPs, these are definitely the right steps to take.

In Return Path&#039;s experience, there are really only two types of good conversations when there is a deliverability problem:

1) &quot;I think I&#039;ve got a [complaint&#124;spam trap&#124;whatever] problem.  Can you confirm?&quot; This requires having a pretty good feel for IP/domain reputation and where the ISP generally starts blocking or filtering.  Once you&#039;ve fixed the problem, let them know what you&#039;ve done and the results you&#039;re seeing.  This tends to speed up resolution (if the problem doesn&#039;t resolve itself because of your improved reputation).

2) Less common is the &quot;We&#039;ve looked at every reputation metric for this mailer and: (1)They look good relative to all other mailers; (2) They are at reputation levels where you rarely block; (3) BTW, no one else is blocking them&quot; conversation.   Requires a lot of data as well, but tends to drive better results as well.  From time to time the answer is - &quot;yep, this doesn&#039;t make sense.&quot;

In the end, your first point is the best - fix your reputation problems and you don&#039;t need to talk to the ISP.</description>
		<content:encoded><![CDATA[<p>This is a great guide.  If you are talking to ISPs, these are definitely the right steps to take.</p>
<p>In Return Path&#8217;s experience, there are really only two types of good conversations when there is a deliverability problem:</p>
<p>1) &#8220;I think I&#8217;ve got a [complaint|spam trap|whatever] problem.  Can you confirm?&#8221; This requires having a pretty good feel for IP/domain reputation and where the ISP generally starts blocking or filtering.  Once you&#8217;ve fixed the problem, let them know what you&#8217;ve done and the results you&#8217;re seeing.  This tends to speed up resolution (if the problem doesn&#8217;t resolve itself because of your improved reputation).</p>
<p>2) Less common is the &#8220;We&#8217;ve looked at every reputation metric for this mailer and: (1)They look good relative to all other mailers; (2) They are at reputation levels where you rarely block; (3) BTW, no one else is blocking them&#8221; conversation.   Requires a lot of data as well, but tends to drive better results as well.  From time to time the answer is &#8211; &#8220;yep, this doesn&#8217;t make sense.&#8221;</p>
<p>In the end, your first point is the best &#8211; fix your reputation problems and you don&#8217;t need to talk to the ISP.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymouse</title>
		<link>http://blog.wordtothewise.com/2009/09/the-secret-to-dealing-with-isps/comment-page-1/#comment-2618</link>
		<dc:creator>Anonymouse</dc:creator>
		<pubDate>Tue, 29 Sep 2009 11:01:30 +0000</pubDate>
		<guid isPermaLink="false">http://blog.wordtothewise.com/?p=664#comment-2618</guid>
		<description>Actually, briefly telling what kind of mail you&#039;re sending can be helpful (eg, &quot;bulk mail&quot;, &quot;my internal employee email server&quot;, &quot;shared web hosting server&quot;, etc.). I know that several ISPs request it now, and I have my suspicions why.</description>
		<content:encoded><![CDATA[<p>Actually, briefly telling what kind of mail you&#8217;re sending can be helpful (eg, &#8220;bulk mail&#8221;, &#8220;my internal employee email server&#8221;, &#8220;shared web hosting server&#8221;, etc.). I know that several ISPs request it now, and I have my suspicions why.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Trout</title>
		<link>http://blog.wordtothewise.com/2009/09/the-secret-to-dealing-with-isps/comment-page-1/#comment-2616</link>
		<dc:creator>Trout</dc:creator>
		<pubDate>Mon, 28 Sep 2009 15:38:48 +0000</pubDate>
		<guid isPermaLink="false">http://blog.wordtothewise.com/?p=664#comment-2616</guid>
		<description>Yes. This. Lots and lots and lots of this.</description>
		<content:encoded><![CDATA[<p>Yes. This. Lots and lots and lots of this.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
