nanog mailing list archives

Re: gmail.com - 550 error for ipv6/PTR ?


From: Blair Trosper <blair.trosper () gmail com>
Date: Tue, 14 Jan 2014 21:42:39 -0600

Possibly related, a lot of 503 errors are starting to show up in the
javascript served by Google inside Gmail...reminds me of the issue in the
early morning hours (US time)...very similar to what I'm starting to see on
the front end.  I've not had any IPv6 emails bounce, but I do have some
that are MIA from Google Apps.  They were sent from one GApps domain to
another, but they haven't materialized on the other end...but they also
haven't bounced back to me.

As a matter of curiosity, I also sent my personal Gmail account email over
v6, and it's doing the same thing...either it's delayed or it's going to
bounce.

The front-end of Gmail is starting to behave weirdly, as well, spitting out
bizarre errors like "technical code:  undefined", and saying it wasn't able
to send a message, but the message going through.  There's a fair amount of
chatter about this on Twitter, so I know it's not just me.

It also thinks it's offline in one tab, when an account in another is
perfectly fine.  Maybe a DC somewhere is having trouble again?


On Tue, Jan 14, 2014 at 8:10 PM, Christopher Morrow <morrowc.lists () gmail com
wrote:

On Tue, Jan 14, 2014 at 8:51 PM, Ted Cooper
<ml-nanog090304q () elcsplace com> wrote:
On 15/01/14 10:06, Brandon Applegate wrote:
Off-list replies are fine to minimize noise, and if there is an answer
or any meaningful correlation I will reply on-list.  Thanks in advance
for any info/feedback.


brandon, I didn't get your original... but could you ping me off-list
and maybe I can get some data about what it is you're seeing? :)

I have been running into these a lot also and have so far concluded that
it is an error within Google. The PTR/AAAA, SPF and DKIM are all matched
up and tested as working. It also occurring on domains using google apps
to handle their email so it is platform wide. All of the emails are
personal emails, but coming from multiple domains/senders.

The exact same email will be rejected when sent to any google IPv6
server for minutes/hours, but 3-4 hours later it will be accepted
without error.

The fact that it is being hard rejected is really quite annoying and
generating a lot more support work.

Unfortunately, my only fix at present is to turn off IPv6 delivery for
all google hosted domains as I encounter them. It would be really nice
if it was fixed.

My theory is that they are failing PTR lookups.







Current thread: