Discussion in 'Mail Chat' started by DCamponi, Aug 6, 2014.
Anyone seeing a lot of this lately? Any suggestions?
Backoff for 48 hours if the error is 5xx and 24 hours if the error is 4xx, as long as it's a "non availability" related error. That should help you keep your IPs for more than just a few days before becoming a permanent block.
So you are saying any error 5XX or 4XX that follows with a "Service unavailable" or "Connection Time Out" pause for 24 or 48 hours.
What about errors like 421 4.2.1 : (DYN:T1) or 521 5.2.1 : AOL will not accept delivery of this message. Do you also pause these for 24 - 48 hours?
I've been pausing most errors for AOL around 12h, but it seems like the last 3 weeks have been killer regarding 554 errors.
The word is, any other than "service unavailable" or "connection timeout" bounce should be treated as you used to in the past. But these two are the ones giving the fair warning that you're about to get RTR. People following this practice are keeping their ranges, and that's proof enough that it's indeed working. Mail goes out slowly though, so it's necessary to spend a bit more on IP space.
Thanks DAgent, I was seeing the exact errors and lost a range to RLY:BL because I didn't heed the warning. I will adjust my pauses accordingly.
To be clear, this is what I am seeing, which I consider to be a sort of throttling... Connected to 220.127.116.11 but greeting failed. Remote host said: 421 mtaig-mad04.mx.aol.com Service unavailable - try again later
2 things can be done -
1. Skip MX of aol
2. Stop Sending for at-least 72Hours
what do you mean by skip MX of AOL?
MX = Mail Exchange = don't mail to aol is what he's saying
ah...thanks. I mail only to aol on that server so I'll go with option 2.