421 mtain-mk06.r1000.mx.aol.com Service unavailable - try again later

Hey All,

This one is killing me the past week.

Any ideas?

 

just adjust your retries - or let your IPs rest for a day. I ran a Y! list after getting that a lot; came back to AOL and I was good again.

 

THanks Pushsend.

am getting it on ranges that have not been mailed on even.
I have a few /24's resting now till monday.

new /24's i just took on, which have had zero mail in a week are throwing that, even while sending to 10 seeds!

is ADK integrated the issue? I think so!

 

that's why you're seeing it - you need to "warm up" the IP's - maybe look at backing off your rate per IP

I don't run ADKanything

 

warm up? only sending to 10 email address. can't warm up much slower! well i could send to 9!

just annoying me this week. am having a brain fart i guess.

 

It these are new ranges, are you sure you have your RDNS and such all set up properly?

I have seen this error before, normally during peek hours of the day. My best guess is that it's a 421 error, but you're not getting the 2nd half of the actual 421 error. As you know (I am assuming) there is multiple error codes. It could be lack of whitelisting, spike in unfavorable stats, DNS not set up, and so forth. You can find a list of them at the postmaster.

My point is, that there could be a 2nd part of the message your missing that would answer the riddle. Considering you are pushing so little volume on your warm up. I am going to say that, based on my experience, there could be another issue at had here beyond throttling. I would make sure to go back and check FBL's, RDNS, NS's and alike. I would also recommend you split test the offer you're sending and see if you get the same error code both time. That includes different subject lines, graphic, from address, and so forth.

Good luck.

:idea:

 

send rate less than 25 per IP per hour
retry 3 times
data - ONLY o/c for the 1st few days.

If you get this - pause for a few hours and restart drop. If it continues run some Y! or other domain out on the IPs then come back to your o/c sets and you should be fine.

 

DaMadHatter and PushSend,

thanks.

I'll take another look at this.

 

I've noticed over the past month or so they keep changing how they deal with new ranges.

I would see some of those wacky error codes you did, before that it was conb's, now I see a mix of different things going on. You send on a range, and it's going through at 99% but you see crazy scomps. You're not getting a lot of FBL's or anything which leads me to believe there is something else going on triggering a false negative, much the same way of the conb errors a few months back.

Whatever it is, seems that AOL keeps tinkering with these error codes and filtering in some way. The first 10-14 days with new ranges are crazy. You can send to a o/c file that you are running other inboxing ranges too all day long, and then these new ranges (also inboxing) will get crazy scomps. I think that it's a matter of their filters learning your system or something, but it's easily the most frustrating thing going on at present.

 

We lost (RYL:BL) our few ranges within matter of few days...when contacted AOL they say higher complaint ratio while we were sending only few thousand mails. We were wondering if there is any specific codes they through our way when this is happening....

 

You really have to pay attention to your scomps, especially on new ranges as they tend to inbox more times than not. You can't treat an inboxing range the same way you do a junk boxing one. You need to ease back on the threads and volume big time, especially for at least 14 days after going live, at least that is the pattern I am noticing anyway.

Additionally, you need to change up the offers you are running. Some trigger a lot of scomps while others not so much. You need to rotate them accordingly instead of swinging for a home run on every drop. In short, it takes a lot more intelligence when mailing to AOL and paying attention to the details. You can't just load up a spam cannon and hit send. You need to account for all of the other variables and know when to ease back.

Ultimately, your first priority should be managing your IP space, not revenue. That is your life blood.

 

Thanks DaMadHatter for your reply.

These ranges were mailing on Live payday feeds and we cant help sending other offers but payday.....but we do changes the creatives frequently.
we initially got CON:B1 then hammered with RYL:BL

 

Conb errors mean that you need to change the creative. It's either being mailed hard, or it's been ID'd in spam filters.

If you keep pounding away, as it sounds like happened here, then you are going to earn your RYL:BL unfortunately.

While I am sure there is a lot more to the story, based on what's presented above, I can easily see why you would be having errors or issues in regards to AOL. You simply must be a lot more creative and simply can't fire and forget if you want to make your ranges last, and get any forward progress.

 

We were rotating the creatives every day btw. So when we hi CON:B1 mailing should be halted through entire range or that particular IP and for how long? Someone says 24 hours is ideal though

 

Check the AOL postmaster blog.
http://postmaster-blog.aol.com

 

thnx bro - I gotta start watching that blog closer. I kinda freaked out as I saw my drops today hitting 90% deferrals...

 

Same thing happened to me.

 

Me Three!!

 

ditto.

Aol has been buggin me since May.

 

Tough AOL day for sure. Early morning 421's. Then a new range started with a bunch of ConB1's. Quit for the day early without much going out to AOL