Discussion in 'Mail Chat' started by DaMadHatter, Jun 4, 2013.
That's a new one.
It's probably a transient error. I have seen that before and it seems to go away.
I normally do not do any drops during the middle of the day as filters turned up full blast, but today I had this little diddy pop up and I can't recall seeing it before. Although during the middle of the day I have seen all kinds of weird things with AOL that disappear later in the day.
It was gone by the time of afternoon drop and haven't seen it since. I guess it was just some middle of the day weirdness.
I personally think AOL's systems suffer from a bit of application rot.
554 become RTR:BL after some hours with AOL generally
We did see that on a couple of ranges, however the rest returned to normal by later in the day.
Makes me wonder if it's a flag of some sort that they investigate. Would explain why some go back to normal and some get perm blocks.
Yep I think same. It could be interesting to see how many times exactly they remain in 554. if its varies a lot there is chance thats a manual review.
I saw the same thing yesterday and the day before. It does go away. Back a few months ago, it indicated the IP was shot. Don't think that's the same now.
i saw this whole day yesterday " 554 mtain-md03.r1000.mx.aol.com ESMTP not accepting connections - 421 4.7.0 mtain-md03.r1000.mx.aol.com Error: too many errors"
After this error, i saw RLY:B2 (Hard Blocked), for how long this block be there? or Last time when i asked them for lift the block they said, you have too much number of complaints. Any suggestion?
Thats a permanent block, and they most likely won't lift it.
So is there a consensus on this? I started getting the same error today. First I got 554 mtain-dl05.r1000.mx.aol.com , then it turned to RYL-B2.
Anyone have experience with IP coming back after this?
Is anyone else here noticing that this is happening mostly with integrated mailings (RLY:B2 and RTR)?
AOL seems to have a "Tuesday-Tuesday" period for which they gauge complaint ratio among other variables. On Tuesday's, during the day, i have encountered these types of deferral's before and they either go away because you stayed under the threshold or they hard block your space.
I guess the most widely used integrated systems might be suffering from excessive footprint?
I had this error for one day.. took a two day breather and AOL is taking it like a s#ut once again.
Following up: this happened to me 8 days ago.. 2 days while I reworked my data.. then pounding town again.
I hope this works for me!
ADK integerated is the cause of this. My machines NOT running it are fine still.
anyone have any luck just requesting each block get unlisted in 1 shot?
ADK reps are denying this of course. Busy sending out press statements about record months!