Problems at Cox: Resolved

People mailing to Cox in the wee hours of this morning may have received a rejection message citing the Invaluement DNSBL.
554 IMP a.b.c.d blocked.  IPBL100 – Refer to Error Codes section at http://postmaster.cox.net for more information.
I spoke with one of the folks at Cox and they said there was an error in the implementation causing non-listed IPs to be rejected erroneously between about 4am to 8am (Eastern) this morning.  The problem has been resolved as of 8am, and all traffic is flowing  normally.  The also stated that attempts to resend any blocked messages will succeed. They do apologize for any problems this may have caused.
For those of you with aggressive bounce handling, removing addresses after a single 550 bounce, you will also want to re-enable any cox.net subscribers that bounced off during this configuration problem.

Why do you need so many IP addresses (part 2)?
A blast from the past

Related Posts

Apparent changes at mail.com

I was poking around at some DNS this weekend and happened to do a MX lookup for mail.com and noticed something changed. Previously mail.com mail was handled by Outblaze (now owned by IBM). It seems, though, that mail.com is now outsourcing their mail delivery to AOL.

Read More

AOL changes bounce behaviour

A couple other bloggers have commented on the recent AOL blog post talking about changes to the MAILER-DAEMON string on bounce messages.

Read More

They are all Barry. Listen to Barry

Al has a guest post up from an ISP rep (now universally referred to as Barry) about senders contacting ISPs. It lists things senders do that Barry Don’t Like.
Listen to Barry.
There are also comments from various other Barrys in the comments. Those are worth reading, too.

Read More