Marco Fioretti:
> <marco.fiore...@gmail.com>: host
> gmail-smtp-in.l.google.com[2a00:1450:400c:c0c::1b] said: 550-5.7.1
> [XXXXXXXXXXXX] Our system has detected that this message does
> 550-5.7.1 not meet IPv6 sending guidelines regarding PTR records and
> 550-5.7.1 authentication. Please review 550-5.7.1
> https://support.google.com/mail/?p=IPv6AuthError for more information 550
> 5.7.1 . t6si9122052wrw.74 - gsmtp (in reply to end of DATA command)
>
> Fact is, "XXXXXXXXXXXX" is the ipv6 address of the server for which I
> *did* add a reverse entry some hours ago (and I had done the same for
> the ipv4 dns record yesterday). In other words, I don't know what else
> I could / should do at this point on the DNS side.
Hours may not be enough to propagate the change to all DNS servers.
What do 'dig' or 'host' have to say about that PTR record? For my
primary server, it looks like this:
$ host 2604:8d00:189::2
2.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.9.8.1.0.0.0.d.8.4.0.6.2.ip6.arpa domain
name pointer spike.porcupine.org.
$ dig +short ptr
2.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.9.8.1.0.0.0.d.8.4.0.6.2.ip6.arpa
spike.porcupine.org.
I also have configured my server not to use IPv6 with gmail. Years
ago they did not distinguish between DNS lookup timeout or 'record
does not exist'. That configuration is still in effect so I don't
know if the problem has been fixed.
Wietse
