[186360] in North American Network Operators' Group
Re: AOL emails bouncing back certain domains
daemon@ATHENA.MIT.EDU (John Peach)
Sat Dec 12 08:06:44 2015
X-Original-To: nanog@nanog.org
Date: Sat, 12 Dec 2015 08:06:22 -0500
From: John Peach <john-nanog@peachfamily.net>
To: nanog@nanog.org
In-reply-to: <566B4605.1030401@ispn.net>
Reply-To: nanog@nanog.org
Errors-To: nanog-bounces@nanog.org
--Sig_/YaNXKvA5dHe3FpZdOiX/6g3
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable
I too reported this issue here and an AOL postmaster contacted me
offlist and got our servers sorted.
On Fri, 11 Dec 2015 15:54:13 -0600
Blake Hudson <blake@ispn.net> wrote:
> Aaron, I reported an issue here almost a month ago (521 5.2.1 : AOL will=
=20
> not accept delivery of this message). AOL support did, eventually,=20
> acknowledge an issue and the failed deliveries did, eventually, clear up=
=20
> for us. AOL support never stated what the issue was nor did they provide=
=20
> any explanation. The responses that we received, much like the response=20
> you received, did not give me the impression that their support staff=20
> was provided any information to pass along.
>=20
> The only advice I can offer is to take care of your own stuff and keep=20
> following up with AOL occasionally regarding their issues. There's not=20
> much you can do, as a non AOL customer, to resolve their issue. We did=20
> have some AOL customers reach out to AOL and it seems as though they=20
> also had trouble getting any reasonable level of support.
>=20
> --Blake
>=20
> Hough, Aaron wrote on 12/11/2015 11:12 AM:
> > The following problem has been acknowledged and yet, has been persistin=
g for weeks unfortunately:
> >
> > "Apparently, email messages ( that with the @aol.com domain ) bounces t=
o and in some occasions, from multiple domains and comes up with Error 521.=
This has been escalated already. As of writing, we are still working towar=
ds a possible solution on this. We would like to apologize for the inconven=
ience this issue might have caused, but let us assure you that higher level=
technicians have been assigned to getting this resolved."
> >
>=20
--=20
John
PGP Public Key: 412934AC
--Sig_/YaNXKvA5dHe3FpZdOiX/6g3
Content-Type: application/pgp-signature; name=signature.asc
Content-Disposition: attachment; filename=signature.asc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
iQEcBAEBAgAGBQJWbBvPAAoJEFkW2a9BKTSsK3sIAJMmFSISazKDYg27NA2rwtxe
BDXpy1/Yyu98r+bEfRxTnflFnEz6qXodqHHxQ9IHhm4zWQp8ujHeDjelyynmmCiv
0EcmV/+6BbIoYIGgOfaF2EsRBN9Ohe7Naod9oM36erFh9DJJc2h5YIHzV4VMHmd6
IBZf7d21EjtPXINsRZEYikqoM+KNNPCDENpYLeNOu1aX09wPmnaIIxhDGe6Bgvt7
IZGlMLdhn3uQFxbSVY7MELPofeXPoOGvkentLKTJUy691unsljQPeYtM3j8qKTcK
UTGM7hHLuggiStsNEE/L8cibhNOdtrbAp3TEL8DJj/hSezp8Iq2k4n+m+lao9h8=
=OsFq
-----END PGP SIGNATURE-----
--Sig_/YaNXKvA5dHe3FpZdOiX/6g3--
