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? On Feb 23, 2015 3:30 PM, "John Zettlemoyer" <john@west-canaan.net> wrote:
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
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 From: Bill Patterson [mailto:billpatterson84@gmail.com] Sent: Monday, February 23, 2015 3:46 PM To: John Zettlemoyer Cc: nanog@nanog.org Subject: Re: AOL Postmaster Did you suddenly start getting "AOL will not accept delivery of this message" bounce backs? On Feb 23, 2015 3:30 PM, "John Zettlemoyer" <john@west-canaan.net> wrote: 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
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. On Feb 23, 2015 3:56 PM, "John Zettlemoyer" <john@west-canaan.net> wrote:
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
*From:* Bill Patterson [mailto:billpatterson84@gmail.com] *Sent:* Monday, February 23, 2015 3:46 PM *To:* John Zettlemoyer *Cc:* nanog@nanog.org *Subject:* Re: AOL Postmaster
Did you suddenly start getting "AOL will not accept delivery of this message" bounce backs?
On Feb 23, 2015 3:30 PM, "John Zettlemoyer" <john@west-canaan.net> wrote:
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
Having exactly the same issue. Also never received any response from AOL. Quite annoying. John Zettlemoyer:
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
From: Bill Patterson [mailto:billpatterson84@gmail.com] Sent: Monday, February 23, 2015 3:46 PM To: John Zettlemoyer Cc: nanog@nanog.org Subject: Re: AOL Postmaster
Did you suddenly start getting "AOL will not accept delivery of this message" bounce backs? On Feb 23, 2015 3:30 PM, "John Zettlemoyer" <john@west-canaan.net> wrote: 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
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----- Van: NANOG [mailto:nanog-bounces@nanog.org] Namens Fred Verzonden: Tuesday, February 24, 2015 3:19 AM Aan: nanog@nanog.org Onderwerp: Re: AOL Postmaster Having exactly the same issue. Also never received any response from AOL. Quite annoying. John Zettlemoyer:
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
From: Bill Patterson [mailto:billpatterson84@gmail.com] Sent: Monday, February 23, 2015 3:46 PM To: John Zettlemoyer Cc: nanog@nanog.org Subject: Re: AOL Postmaster
Did you suddenly start getting "AOL will not accept delivery of this message" bounce backs? On Feb 23, 2015 3:30 PM, "John Zettlemoyer" <john@west-canaan.net> wrote: 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
On Tue, Feb 24, 2015 at 03:19:06AM +0100, Fred wrote:
Having exactly the same issue. Also never received any response from AOL. Quite annoying.
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 Sent from my iPhone
On 24 Feb 2015, at 12:36, Rich Kulawiec <rsk@gsp.org> wrote:
On Tue, Feb 24, 2015 at 03:19:06AM +0100, Fred wrote: Having exactly the same issue. Also never received any response from AOL. Quite annoying.
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
And how many users do you have, again? On Feb 24, 2015 6:29 PM, "Colin Johnston" <colinj@gt86car.org.uk> wrote:
block aol like china blocks with no engagement of comms as justification
colin
Sent from my iPhone
On 24 Feb 2015, at 12:36, Rich Kulawiec <rsk@gsp.org> wrote:
On Tue, Feb 24, 2015 at 03:19:06AM +0100, Fred wrote: Having exactly the same issue. Also never received any response from AOL. Quite annoying.
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
On Tue, 24 Feb 2015 08:45:15 -0500, Rich Kulawiec said:
On Tue, Feb 24, 2015 at 06:33:08PM +0530, Suresh Ramasubramanian wrote:
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.
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 - ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ vox: +1 202 459 9800 x.1300 // secure: +1 410 874 0050 (phone calls need to be arranged in advance) e: adrian@2600.COM // e: adrian.lamo@us.army.mil GPG/PGP public key: https://keybase.io/comsec/key.asc PGP Fingerprint (64 bit): 324B EE81 A275 E619 (COMSEC First! Verify fingerprint before using key.) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ El 2015-02-24 13:03, Suresh Ramasubramanian escribió:
And how many users do you have, again? On Feb 24, 2015 6:29 PM, "Colin Johnston" <colinj@gt86car.org.uk> wrote:
block aol like china blocks with no engagement of comms as justification
colin
Sent from my iPhone
On 24 Feb 2015, at 12:36, Rich Kulawiec <rsk@gsp.org> wrote:
On Tue, Feb 24, 2015 at 03:19:06AM +0100, Fred wrote: Having exactly the same issue. Also never received any response from AOL. Quite annoying.
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
Their own announcement: http://postmaster-blog.aol.com/2014/04/22/aol-mail-updates-dmarc-policy-to-r... says that DMARC issues should be referred here: dmarc-help@teamaol.com (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 On Wed, Feb 25, 2015 at 05:24:12AM -0500, Rich Kulawiec said:
Their own announcement:
http://postmaster-blog.aol.com/2014/04/22/aol-mail-updates-dmarc-policy-to-r...
says that DMARC issues should be referred here:
dmarc-help@teamaol.com
(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
-- Ken Chase - Toronto Canada
That was my first response as well. But that response was frowned upon by my customer service reps. On Feb 25, 2015 8:56 AM, "Ken Chase" <math@sizone.org> wrote:
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
On Wed, Feb 25, 2015 at 05:24:12AM -0500, Rich Kulawiec said:
Their own announcement:
http://postmaster-blog.aol.com/2014/04/22/aol-mail-updates-dmarc-policy-to-r...
says that DMARC issues should be referred here:
dmarc-help@teamaol.com
(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
-- Ken Chase - Toronto Canada
You think every accountant, realtor, coffee shop etc uses their own domain? On Feb 26, 2015 3:12 AM, "Bill Patterson" <billpatterson84@gmail.com> wrote:
That was my first response as well. But that response was frowned upon by my customer service reps. On Feb 25, 2015 8:56 AM, "Ken Chase" <math@sizone.org> wrote:
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
On Wed, Feb 25, 2015 at 05:24:12AM -0500, Rich Kulawiec said:
Their own announcement:
http://postmaster-blog.aol.com/2014/04/22/aol-mail-updates-dmarc-policy-to-r...
says that DMARC issues should be referred here:
dmarc-help@teamaol.com
(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
-- Ken Chase - Toronto Canada
they seem to use gmail and actually get their email. /kc On Thu, Feb 26, 2015 at 07:24:35AM +0530, Suresh Ramasubramanian said:
You think every accountant, realtor, coffee shop etc uses their own domain?
-- Ken Chase - ken@heavycomputing.ca skype:kenchase23 +1 416 897 6284 Toronto Canada Heavy Computing - Clued bandwidth, colocation and managed linux VPS @151 Front St. W.
On Feb 25, 2015, at 5:54 PM, Suresh Ramasubramanian <ops.lists@gmail.com> wrote:
You think every accountant, realtor, coffee shop etc uses their own domain?
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
participants (11)
-
Adrian Lamo -
Bill Patterson -
Colin Johnston -
David Hofstee -
Fred -
John Zettlemoyer -
Ken Chase -
Rich Kulawiec -
Steve Atkins -
Suresh Ramasubramanian -
Valdis.Kletnieks＠vt.edu