Could someone from AOL who deals with the email systems please contact me off-list.
Thank you.
John Zettlemoyer
WCiT LLC
856.310.1375 x221
john@wcit.net
Did you suddenly start getting "AOL will not accept delivery of this
message" bounce backs?
No, started using an IP address that hasn’t been used since we got the range from Arin, and got this - 554- (RTR:BL)
Tried to contact AOL through normal channels, and no response in over a week. Feedback loop has been in place for years, and we check it every day (its clean).
John Zettlemoyer
Ok, it took 21 days from the time I opened a ticket with them last month
for them to respond to me. I ended up having to have our ISP update our
rDNS. Not sure if it's something similar for you but I felt the same way
after a week of waiting for a response from them.
Having exactly the same issue. Also never received any response from AOL. Quite annoying.
John Zettlemoyer:
Same here. I want to solve things that they seem to have issues with. But when I ask what is wrong they either don't respond (in any meaningful manner) or say that they 'solved it', without me ever knowing what 'it' was.
I prefer swimming in seaweed instead of contacting Yahoo (or MS for that matter). And the seaweed here is quite gross.
David Hofstee
Deliverability Management
MailPlus B.V. Netherlands (ESP)
-----Oorspronkelijk bericht-----
I've been waiting since January 26th for a response from dmarc-help@teamaol.com,
which is their stipulated contact point for DMARC issues.
Of course I wouldn't *need* a response about that if they hadn't implemented
DMARC so foolishly.
It seems that the days when Carl Hutzler ran the place -- and ran it well --
are now well behind them. I didn't always agree with their decisions,
but it was obvious that they were working hard and trying to make AOL a
good network neighbor, so even when I disagreed I could at least acknowledge
their good intentions. It seems now that AOL is determined to permit
unlimited abuse directed at the entire rest of the Internet while
simultaneously making life as difficult as possible for everyone who
*doesn't* abuse...and is counting on their size to make them immune from
the consequences of that decision.
---rsk
block aol like china blocks with no engagement of comms as justification
colin
And how many users do you have, again?
So professionalism, competence, diligence, etc. are reserved for
only the operations considered large enough? Good to know.
---rsk
No, but being able to ignore 800 pound gorillas *is* reserved for
only the operations considered small enough....
The quickest way of contacting the AOL Mail Team I'm aware of is through their Twitter account at @AOLMail (https://twitter.com/AOLMail). Tell them @6 sent you. 
Cordially,
A
Their own announcement:
http://postmaster-blog.aol.com/2014/04/22/aol-mail-updates-dmarc-policy-to-reject/
says that DMARC issues should be referred here:
(And before anyone asks, yes, the headers on mailing list traffic
have been modified precisely as that page stipulates.)
Perhaps it's too much to expect that in 2015 system and network admins
will actually demonstrate baseline professionalism and competence by
reading and answering role account email.
---rsk
Simple, one simply does not conduct business email over an AOL account.
This is what I've been telling several of my customers about their contacts for a while now.
/kc
That was my first response as well. But that response was frowned upon by
my customer service reps.
You think every accountant, realtor, coffee shop etc uses their own domain?
they seem to use gmail and actually get their email.
/kc
No.
But they should not, and in many cases *cannot*, rely on aol or yahoo addresses.
It would suck for them to have to change all their contact information, business cards,
and so on - but a) they chose their email provider unwisely and that's the cost of
relying on an inappropriate vendor and b) they don't really need to - inbound mail to
those addresses is mostly fine, so they just need to get a second email address
and gradually migrate their outbound usage to that.
Because the root cause of this issue is a long series of security mistakes by those
providers, allowing 3rd parties to have access to user's (supposedly private) account
information, the issue is specific to those providers, and there's no strong argument that
other email providers are likely to make the same business choices.
Cheers,
Steve