One of our senior ministry leaders is replying to e-mails from a hundred or so people who e-mailed her. Many of these people are on Road Runner e-mail addresses. (Road Runner is the Internet service from Time Warner Cable.) She started getting bounce-backs from Road Runner that look like this:
The e-mail system was unable to deliver the message, but did not report a specific reason. Check the address and try again. If it still fails, contact your system administrator. exchange01.church.cor.org #4.0.0 smtp;452 Too many recipients received this hour. Please see our rate limit policy at http://security.rr.com/spam.htm#ratelimit
So I clicked the link and read about Road Runner’s rate limit policy. Turns out that we didn’t have forward DNS for our mail server, exchange01.church.cor.org, which caused us to fall under the category of “Systems With Incorrectly Configured DNS Entries”. Accordingly, we are limited to sending e-mails to 10 Road Runner customers per hour. Since we have literally thousands of people in our congregation with Road Runner addresses, this is a problem.
Needless to say, we corrected the DNS issue right away, but how long will it be before Road Runner’s system checks again and realizes we fixed it?
Later in the same Road Runner page about their rate limit policy we read:
The SenderBase Reputation Score that Road Runner uses as part of its inbound email rate limiting decision cannot be looked up on the SenderBase site as a direct query.
Woo hoo. So Road Runner is going to base its rate limitation partly on the SenderBase Reputation Score, but there’s no obvious way for me to find out our score. Road Runner, this is not serving your customers well. How are we supposed to explain to our congregants that we can’t get e-mail through to them due to a policy of their ISP that’s so complicated, even us IT guys can’t figure it out or do anything about it?