Changes at RoadRunner

I’ve been hearing rumors that some *.rr.com domains have been bouncing all mail sent to them. Those domains belong to customers that were moved to Comcast as part of the RoadRunner / Comcast / Adelphia purchase and customer swap. As a courtesy, RoadRunner forwarded mail to comcast for those former RoadRunner customers, but have ceased to do so.
Mail to any address in the following *.rr.com domains will no longer be delivered.
jam.rr.com
midsouth.rr.com
mn.rr.com
se.rr.com
sport.rr.com
swfla.rr.com
ucwphilly.rr.com
houston.rr.com
These addresses should be removed from your lists. These users now have Comcast addresses. You cannot just substitute the Comcast domain for the RoadRunner domain as users were required to choose new localparts. That means bobjones@houston.rr.com may not be, and probably is not, bobjones@comcast.

Related Posts

Changes at Comcast

I can usually tell when one of the ISPs makes some change to their incoming spam filtering just by my call volume. The past few weeks the ISP in most of my calls has been Comcast. And, what do you know, they have made changes to how they are filtering email.
According to their bounce message, Comcast is using ReturnPath’s proprietary SenderScore product to filter mail. Reports on thresholds vary, but IPs with SenderScores of 70 and below have been blocked with messages similar to:

Read More

Best practices and ISPs

A couple articles came out today talking about ISP requirements and how to find them.
EmailInsider talks about ISP best practices and how merely complying with CAN-SPAM is not enough to get good delivery at the ISPs.
Meanwhile, over at ClickZ, Stefan talks about what the ISPs want from you and how to find the information online.

Read More

Greylisting: that which Yahoo does not do

Over the last couple days multiple people have asserted to me that Yahoo is greylisting mail. The fact that Yahoo itself asserts it is not using greylisting as a technique to control mail seems to have no effect on the number of people who believe that Yahoo is greylisting.
Deeply held beliefs by many senders aside, Yahoo is not greylisting. Yahoo is using temporary failures (4xx) as a way to defer and control mail coming into their servers and their users.
I think much of the problem is that the definition of greylisting is not well understood by the people using the term. Greylisting generally refers to a process of refusing email with a 4xx response the first time delivery is attempted and accepting the email at the second delivery attempt. There are a number of ways to greylist, per message, per IP or per from address. The defining feature of greylisting is that the receiving MTA keeps track of the messages (IP or addresss) that it has rejected and allows the mail through the second time the mail is sent.
This technique for handling email is a direct response to some spamming software, particularly software that uses infected Windows machines to send email. The spam software will drop any email in response to a 4xx or 5xx response. Well designed software will retry any email receiving a 4xx response. By rejecting anything on the first attempt with a 4xx, the receiving ISPs can trivially block mail from spambots.
Where does this fit in with what Yahoo is doing? Yahoo is not keeping track of the mail it rejects and is not reliably allowing email through on the second attempt. There are a couple reasons why Yahoo is deferring mail.

Read More