In your logs, you may see the following error message accompanying a deferral event:

1
Email was deferred due to the following reason(s): ["IPs reached ISP-suggested max connection limits: http://send.gd/1uKnEBh"]

What’s that about?

I’m glad you asked. We’ve recently updated the infrastructure that handles the actual sending of mail off to it’s intended recipients, specifically updated in regards to sending rate.

What’s wrong with my IPs?

Nothing! This is simply due to the fact that most of the time we are sending mail much faster than most ISPs can accept it. Rather than turning the fire hose on full-blast, we create one of these deferral events to control the rate of delivery by ISP to help prevent throttling and spam folder delivery. Sending too much mail too fast is a great way to get on an ISP’s naughty list.

We spend a lot of time tuning the rate of delivery on an ISP by ISP basis, and these deferral events are simply proof that this system is working for you to keep ISPs happy with your throughput, regardless of your sending habits.

What do I need to do?

You don’t need to take any further action.

We’ll continue to attempt delivery of Deferred messages for up to 72 hours, after which time we may drop the message if the ISP still isn’t able accept the messages. These deferrals may sometimes result in delays between an email’s Processed event and the eventual Delivery event, but again, this is simply us optimizing the rate at which email sends are attempted.