<?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>Word to the Wise &#187; 4xx</title>
	<atom:link href="http://blog.wordtothewise.com/tag/4xx/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.wordtothewise.com</link>
	<description>Email, Delivery, Spam and more</description>
	<lastBuildDate>Sat, 04 Feb 2012 17:01:54 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.3</generator>
		<item>
		<title>Changes at Gmail</title>
		<link>http://blog.wordtothewise.com/2011/05/changes-at-gmail/</link>
		<comments>http://blog.wordtothewise.com/2011/05/changes-at-gmail/#comments</comments>
		<pubDate>Wed, 11 May 2011 00:55:57 +0000</pubDate>
		<dc:creator>laura</dc:creator>
				<category><![CDATA[Industry]]></category>
		<category><![CDATA[4xx]]></category>
		<category><![CDATA[delays]]></category>
		<category><![CDATA[filtering]]></category>
		<category><![CDATA[gmail]]></category>
		<category><![CDATA[google]]></category>
		<category><![CDATA[ISPs]]></category>
		<category><![CDATA[spam filters]]></category>

		<guid isPermaLink="false">http://blog.wordtothewise.com/?p=2915</guid>
		<description><![CDATA[As I&#8217;ve said before, I can usually tell when some ISP changes their filtering algorithm because I start getting tons and tons of calls about delivery problems at that ISP. This past month it&#8217;s been Gmail. There have been two symptoms I&#8217;ve been hearing about. One is an increase in bulk folder delivery for mail [...]]]></description>
			<content:encoded><![CDATA[<p>As I&#8217;ve said before, I can usually tell when some ISP changes their filtering algorithm because I start getting tons and tons of calls about delivery problems at that ISP. This past month it&#8217;s been Gmail.</p>
<p>There have been two symptoms I&#8217;ve been hearing about. One is an increase in bulk folder delivery for mail that previously was reliably hitting the inbox. The other is a bit more interesting. I&#8217;ve heard of 3 different mailers, with good reputations and very clean lists, that are seeing 4xx delays on some of their mail. The only consistency I, and my colleagues at some ESPs, have identified is that the mail is &#8220;bursty.&#8221;</p>
<p>The senders affected by this do send out mail daily, but the daily mail is primarily order confirmations or receipts or other transactional mails. They send bi-weekly newsletters, though, exploding their volume from a few tens of thousands up to hundreds of thousands. This seems to trigger Gmail to defer mail. It does get delivered eventually. It&#8217;s frustrating to try and deal with because neither side is really doing anything wrong, but good senders are seeing delivery delays.</p>
<p>For the bulk foldering, Bronto has a <a href="http://brontoversity.com/2011/05/05/gmail-deliverability-and-3-ways-to-improve-it/">good blog post talking about the changes</a> and offering some solid suggestions for how to deal with them. I&#8217;m also hearing from some folks who are reliable that Gmail may be rolling back some of the bulk foldering changes based on feedback from their users.</p>
<p>So if you&#8217;re seeing changes at Gmail, it&#8217;s not just you.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.wordtothewise.com/2011/05/changes-at-gmail/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>AOL transmitting 4xx error for user unknown</title>
		<link>http://blog.wordtothewise.com/2010/02/aol-transmitting-4xx-error-for-user-unknown/</link>
		<comments>http://blog.wordtothewise.com/2010/02/aol-transmitting-4xx-error-for-user-unknown/#comments</comments>
		<pubDate>Tue, 09 Feb 2010 00:40:47 +0000</pubDate>
		<dc:creator>laura</dc:creator>
				<category><![CDATA[Industry]]></category>
		<category><![CDATA[4xx]]></category>
		<category><![CDATA[5xx]]></category>
		<category><![CDATA[AOL]]></category>
		<category><![CDATA[bounce handling]]></category>
		<category><![CDATA[bounces]]></category>

		<guid isPermaLink="false">http://blog.wordtothewise.com/?p=1236</guid>
		<description><![CDATA[AOL is currently returning &#8220;451 4.3.0 &#60;invaliduser@aol.com&#62;: Temporary lookup failure&#8221; in some cases when they really mean &#8220;550 user unknown.&#8221; This message from AOL should be treated as 5xx failure and the message should not be retried (if at all possible) and the failure should be counted as a hard bounce for list management purposes. [...]]]></description>
			<content:encoded><![CDATA[<p>AOL is currently returning &#8220;451 4.3.0 &lt;invaliduser@aol.com&gt;: Temporary lookup failure&#8221; in some cases when they really mean &#8220;550 user unknown.&#8221; This message from AOL should be treated as 5xx failure and the message should not be retried (if at all possible) and the failure should be counted as a hard bounce for list management purposes.</p>
<p>This is something broken at AOL&#8217;s end, and the guys with the magic fingers that keep the system running are working to fix it. Right now there doesn&#8217;t seem to be an ETA on a fix, though.</p>
<p>Even if you are a sender who is able to stop the retries, you may see some congestion and delays when sending to AOL for the time being. Senders who don&#8217;t get the message, or who are unable to stop their MTAs from retrying 4xx mail will continue to attempt delivery of these messages until their servers time out. This may cause congestion for everyone and a noticeable  slowdown on the AOL MTAs.</p>
<p><a href="http://postmaster-blog.aol.com/2010/02/08/error-code-update/">AOL blog post on the issue</a></p>
<p>HT: <a href="http://www.annaliviaford.com/2010/02/error-code-updates.html">Annalivia</a></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.wordtothewise.com/2010/02/aol-transmitting-4xx-error-for-user-unknown/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Soft bounces and rate limiting</title>
		<link>http://blog.wordtothewise.com/2009/02/soft-bounces-and-rate-limiting/</link>
		<comments>http://blog.wordtothewise.com/2009/02/soft-bounces-and-rate-limiting/#comments</comments>
		<pubDate>Tue, 24 Feb 2009 01:33:09 +0000</pubDate>
		<dc:creator>laura</dc:creator>
				<category><![CDATA[Delivery Improvement]]></category>
		<category><![CDATA[4xx]]></category>
		<category><![CDATA[bounce]]></category>
		<category><![CDATA[rate limiting]]></category>

		<guid isPermaLink="false">http://blog.wordtothewise.com/?p=364</guid>
		<description><![CDATA[What is your policy for handling soft bounces? What do you consider a soft bounce? What is the right thing to do about soft bounces? The first step in talking about soft bounces is to define them. When I talk about soft bounces, I mean mail that has been rejected with a 4xx response during [...]]]></description>
			<content:encoded><![CDATA[<p>What is your policy for handling soft bounces? What do you consider a soft bounce? What is the right thing to do about soft bounces?</p>
<p>The first step in talking about soft bounces is to define them. When I talk about soft bounces, I mean mail that has been rejected with a 4xx response during the SMTP transaction. As described by <a href="http://www.faqs.org/rfcs/rfc5321.html">RFC5321</a>, when a recipient <a href="http://isp.webopedia.com/TERM/M/MTA.html">MTA</a> responds with a 4xx it is telling the sending MTA &#8220;Wait! I can&#8217;t take this mail right now. Come back a little later and try again.&#8221; The sending MTA will then continue to attempt to deliver the message until either it is delivered or until it hits the max delivery time, usually 3 &#8211; 5 days.</p>
<p>In a well behaved and RFC compliant MTA, messages that have reached the maximum time without delivery due to 4xx rejections will be converted to permanent rejections (5xx). With a correct MTA, this means too many emails in a row timing out shoud result in an email address being removed from future mailings.</p>
<p>For a number of reasons some ISPs, notably Yahoo, are using 4xx responses to slow down mail from some senders. Many senders treat this as a inconvenience and a frustration and try to figure out how to get around the rate limiting. The UK DMA published an article on soft bounces with the following <a href="http://email.dma.org.uk/_attachments/Resources/4780_S4.html">words of wisdom</a>.</p>
<blockquote><p>Emails blocked in this way are recorded as soft bounces, so your soft bounces are important indicators of how &#8216;Spammy&#8217; ISP’s think you are at a given point in time. They are an indication of a drop in reputation for the IP address you are using, uneven mailing patterns and/or an increase in the level of SPAM complaints your email is generating.  All of these things are things that you and your ESP can do something about!</p></blockquote>
<p>This, in a nutshell, is why senders should not just grump about transient failures, but instead should look at their mailing practices. The ISPs using this technique to slow down senders typically are doing this on-the-fly, in that their limits are being put on mail that they see as problematic at that moment. In addition to the reasons given by the UK DMA, they are also monitoring complaints in real time and looking at the content of the message. If the ISP is seeing an increase in complaints about mail with a URL that is also in your mail, you may see rate limiting as a result. If the ISP is seeing an increase in complaints about mail from your IP, then you may see rate limiting as a result.</p>
<p>These are issues senders can address. You have the power and the technology to address the issue. Addressing the issue will improve your overall delivery.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.wordtothewise.com/2009/02/soft-bounces-and-rate-limiting/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

