<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>MailChimp Email Marketing Blog &#187; isp</title>
	<atom:link href="http://www.mailchimp.com/blog/tag/isp/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.mailchimp.com/blog</link>
	<description>MailChimp, email marketing, and monkeys!</description>
	<lastBuildDate>Fri, 13 Nov 2009 21:09:20 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Comcast Delivery Tips</title>
		<link>http://www.mailchimp.com/blog/comcast-delivery-tips/</link>
		<comments>http://www.mailchimp.com/blog/comcast-delivery-tips/#comments</comments>
		<pubDate>Thu, 06 Nov 2008 21:41:25 +0000</pubDate>
		<dc:creator>Ben</dc:creator>
				<category><![CDATA[Abuse Desk Stories]]></category>
		<category><![CDATA[Deliverability]]></category>
		<category><![CDATA[Spam Topics]]></category>
		<category><![CDATA[Tips, Tricks, Best Practices]]></category>
		<category><![CDATA[comcast]]></category>
		<category><![CDATA[fbl]]></category>
		<category><![CDATA[feedback loops]]></category>
		<category><![CDATA[isp]]></category>

		<guid isPermaLink="false">http://www.mailchimp.com/blog/?p=1430</guid>
		<description><![CDATA[A couple days ago, Comcast sent an email asking for feedback about their feedback loop. Rare to see an ISP genuinely asking email senders what they think. Anyway, this meant I got to speak with one of their senior spam analysts on the phone today. Now I&#8217;ve spoken with a lot of ISPs, and I [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://postmaster.comcast.net"><img class="alignright" style="border: 0pt none; margin: 5px;" src="http://www.mailchimp.com/blog/wp-content/uploads/2007/12/comcastic.png" rel="facebox" alt="" width="191" height="67" /></a>A couple days ago, Comcast sent an email asking for feedback about their <a href="http://www.clickz.com/showPage.html?page=3623337">feedback loop</a>. Rare to see an ISP genuinely asking email senders what they think. Anyway, this meant I got to speak with one of their senior spam analysts on the phone today. Now I&#8217;ve spoken with a lot of ISPs, and I can tell you this was unlike any other conversation I&#8217;ve ever had. Comcast was human. Friendly, even. It was refreshingly <em>Comcastic</em>.</p>
<p>He gave me some tips that I could pass on to our readers. So here you go:</p>
<p><span id="more-1430"></span></p>
<ul>
<li>Comcast really, really hates it when you send to an old list (with lots of undeliverable email addresses). If you&#8217;ve got too many emails on your list that no longer exist, Comcast will block your IP address. This is a very strong argument for cleaning old, inactive members from your lists. Yes, I know it feels safer to keep old members on the list, because the number of recipients looks so much bigger. Yes, I know your boss keeps telling you not to clean your list, because they don&#8217;t want to lose any prospects. But those bad addresses are just holding back your overall deliverability and keeping the <strong><em>good</em></strong> addresses on your list from getting your message. Yes, I have numbers to prove it. In a later post.</li>
<li>Comcast doesn&#8217;t like it if you send too many emails all at once to them (this one&#8217;s kind of a no-brainer). Here&#8217;s what makes them different: t<a title="Comcast rate limiting chart" href="http://help.comcast.net/content/faq/RL001" target="_blank">hey&#8217;ll actually TELL you how many you&#8217;re allowed to send at once</a>.</li>
<li>As you can see from <a title="Comcast Rate limiting chart" href="http://help.comcast.net/content/faq/RL001" target="_blank">this chart</a>, the rate of emails you&#8217;re allowed to send to Comcast at once depends on your IP&#8217;s &#8220;reputation.&#8221;</li>
<li>Your IP reputation is based on at least two factors: <a href="http://www.mailchimp.com/authentication">Authentication</a> (a technology standard that&#8217;s used to prove an email is not a forgery), and the IP&#8217;s &#8220;<a title="ReturnPath Senderscore" href="https://www.senderscore.org/" target="_blank">Sender Score</a>&#8221; (Your IP&#8217;s Sender Score is kind of like a credit rating, and it&#8217;s the folks at <a href="https://www.senderscore.org/" target="_blank">ReturnPath</a> who issue the score). <em>MailChimp customers &#8211; Authentication is free with every MailChimp account, and through our relationship with ReturnPath we monitor our senderscore closely.</em></li>
</ul>
<p>For those of you familiar with ISPs and abuse desks in general, none of this is all that new. The interesting stuff is how forthcoming and helpful Comcast is with their error codes and rate limiting charts. Overall, their new Postmaster site is one of the best I&#8217;ve ever seen (look at all the handy RSS feeds):</p>
<p><a title="Comcast Postmaster Site" href="http://postmaster.comcast.net/" target="_blank">http://postmaster.comcast.net/</a></p>
<p>If you&#8217;re new to all this, and wonder how this applies to you:</p>
<ul>
<li>Don&#8217;t send to old email addresses. You&#8217;ll get yourself (and other innocent senders) blocked.</li>
<li>At some ISPs, old email addresses get turned into spam traps. You send an email to a spamtrap, and you are instantly blocked. We had a case of a MailChimp user who sent to a 10-yr old email list (totally opt-in, and the guy luckily had IP/timestamps on all subscribers) and one of the addresses had been turned into a spam trap. The impact on his deliverability from a spamtrap hit was instantaneous and dramatic. Keeping his proof of opt-in for so long saved his behind.</li>
<li>If you&#8217;re sending your emails from an ESP (like MailChimp, Constant Contact, etc) that has shared IP ranges, then one bad apple can truly spoil the whole IP range. So it&#8217;s important to go with an ESP that closely monitors their deliverability, and punishes bad senders (it&#8217;s for the greater good). Quality over quantity.</li>
<li>Don&#8217;t export your entire email address book and assume they all want to receive email newsletters from you. <a href="http://www.mailchimp.com/blog/email-marketing-mistake-the-old-address-book-dump/">Address book dumps </a>are full of old email addresses, and are one of the most common reasons I see senders get blocked. <a href="http://www.mailchimp.com/blog/how-tradeshow-email-lists-can-get-you-blacklisted/">Other reasons</a> include: Fish bowls, sharing lists, and buying lists.</li>
<li>If you have an old list of people who opted-in to receive emails from you, but you haven&#8217;t sent them an email in a really long time (or ever), then you need to delete any emails older than 1yr, <em><strong>then</strong></em> send the remaining subscribers a &#8220;remember me?&#8221; welcome email. <a href="http://www.mailchimp.com/blog/reclaim-old-customer-emails-example/">Here&#8217;s a good example</a>.</li>
<li>If you send emails on a regular basis, and you think your system is cleaning the list for you, you still might want to <a href="http://www.mailchimp.com/blog/3-quick-email-list-segmentation-examples/">segment your list by actives vs. inactives.</a></li>
</ul>
<p>Comcast isn&#8217;t the only ISP that hates it when you send to old/dead lists.  <a title="AOL Postmaster - don't send to old email addresses" href="http://postmaster-blog.aol.com/2008/10/24/ip-reputation-the-whitelist-and-inbox-delivery-at-aol/" target="_blank">AOL&#8217;s postmaster talks about IP reputation and undeliverables </a>here. ReturnPath, the experts on email deliverability, <a href="http://www.returnpath.net/blog/2008/11/why-your-email-wont-get-delive.php">mentions undeliverables here</a> and offers some tips. Laura Atkins from <a href="http://blog.wordtothewise.com/2008/08/letting-go/">WordtotheWise</a> talks about &#8220;<a href="http://blog.wordtothewise.com/2008/08/letting-go/">Letting Go</a>&#8221; of old members.</p>
<p>In general, there&#8217;s a shift (again) in the way ISPs and email receivers judge emails as spam or not. Instead of relying on blacklists or focusing on bad content, they&#8217;re looking at your overall reputation as a sender. And list cleanliness (undeliverables, hard bounces, spam complaints) are huge factors in determining how clean your list is.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.mailchimp.com/blog/comcast-delivery-tips/feed/</wfw:commentRss>
		<slash:comments>11</slash:comments>
		</item>
		<item>
		<title>Email Authentication by ISP</title>
		<link>http://www.mailchimp.com/blog/email-authentication-by-isp/</link>
		<comments>http://www.mailchimp.com/blog/email-authentication-by-isp/#comments</comments>
		<pubDate>Thu, 07 Feb 2008 12:20:32 +0000</pubDate>
		<dc:creator>Ben</dc:creator>
				<category><![CDATA[Deliverability]]></category>
		<category><![CDATA[MailChimp News]]></category>
		<category><![CDATA[Spam Topics]]></category>
		<category><![CDATA[Using MailChimp]]></category>
		<category><![CDATA[aol whitelist]]></category>
		<category><![CDATA[authentication]]></category>
		<category><![CDATA[isp]]></category>
		<category><![CDATA[returnpath]]></category>

		<guid isPermaLink="false">http://www.mailchimp.com/blog/email-authentication-by-isp/</guid>
		<description><![CDATA[A few of our customers have been asking us about this bit of news from ReturnPath: AOL Changes Authentication and Whitelist Standards.
According to George Bilbrey, AOL, Gmail, and Yahoo have implemented DKIM email authentication.
For those of you who don&#8217;t know, authentication is a way to prevent email forgeries, and it can improve your deliverability. The [...]]]></description>
			<content:encoded><![CDATA[<p>A few of our customers have been asking us about this bit of news from ReturnPath: <a href="http://www.returnpath.net/blog/2008/01/changes-to-aol.php" title="AOL Implements DKIM" target="_blank">AOL Changes Authentication and Whitelist Standards.</a></p>
<p>According to George Bilbrey, AOL, Gmail, and Yahoo have implemented DKIM email authentication.</p>
<p>For those of you who don&#8217;t know, authentication is a way to <a href="http://www.mailchimp.com/blog/can-your-email-newsletter-be-stolen/" title="Can your email be stolen?">prevent email forgeries</a>, and it can <a href="http://www.mailchimp.com/blog/authentication-helping-with-corporate-firewalls/" title="authentication improving deliverability">improve your deliverability</a>. The AOTA says <a href="http://www.mailchimp.com/blog/email-authentication-hits-tipping-point/" title="Authentication hits tipping point">Authentication has hit its &#8220;tipping point.&#8221;</a></p>
<p>Since 2004, when email authentication started to really pick up steam, ISPs have been testing (and changing) their support for authentication. Some use one method for inbound, and another for outbound. Some support all methods of authentication. Some have abandoned it, or are in limbo. It can be confusing.</p>
<p>So we compiled a <a href="/authentication/" title="Email authentication guide">chart of which ISPs are using which authentication methods over here</a>.  <a href="http://www.mailchimp.com/authentication/" title="Email authentication by ISP"><img src="http://www.mailchimp.com/blog/wp-content/uploads/2008/02/chart-authentication.gif" rel="facebox" alt="Email Authentication by ISP chart" border="0" hspace="0" vspace="5" /></a></p>
<p>Of course, we&#8217;ve also made authentication &#8220;MailChimp Easy:&#8221; Our customers can <a href="/resources/authentication-in-mailchimp.phtml" title="MailChimp email authentication">authenticate their email campaigns with one simple click</a>, and we cover <strong><em>all</em></strong> the major authentication standards (DKIM, Domain Keys, SenderID, and SPF).</p>
]]></content:encoded>
			<wfw:commentRss>http://www.mailchimp.com/blog/email-authentication-by-isp/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
