Gmail MX over IPv6
Wolfgang S. Rupprecht
wolfgang.rupprecht at gmail.com
Sun Jun 17 05:18:20 CEST 2012
Olivier MJ Crepin-Leblond <ocl at gih.com> writes:
> On 15/06/2012 23:30, Luca BRUNO wrote :
>> I'm not sure if it is a recent change or if I have just been
>> white-listed, but today in mailserver logs I've spotted that gmail.com
>> is already accepting mail over an IPv6 MX:
> Yes, but they appear to have "forgotten" googlemail.com which at some
> point used to call gmail.
> [root at waikiki log]# dig +short mx googlemail.com
> 10 alt1.gmail-smtp-in.l.google.com.
> 20 alt2.gmail-smtp-in.l.google.com.
> 30 alt3.gmail-smtp-in.l.google.com.
> 40 alt4.gmail-smtp-in.l.google.com.
> 5 gmail-smtp-in.l.google.com.
> [root at waikiki log]# dig +short gmail-smtp-in.l.google.com.
> Also -- did anyone check whether it breaks the SPF checking? It appears
> that when gmail received email by IPv6, it doesn't recognise the IPv6
> address which my mailer uses as a permitted sender, thus spf=softfail
I got a hardfail from gmail. Their SPF parsing for IPv6 is messed up.
Maybe the "::" notation scewed up a string compare to ":0:0:0:" or
Received-SPF: fail (google.com: domain of XXX at wsrcc.com does not designate 2001:5a8:4:7d1::1 as permitted sender) client-ip=2001:5a8:4:7d1::1;
Authentication-Results: mx.google.com; spf=hardfail (google.com: domain of XXX at wsrcc.com does not designate 2001:5a8:4:7d1::1 as permitted sender) smtp.mail=XXX at wsrcc.com
wsrcc.com. 3600 IN TXT "v=spf1 ip4:126.96.36.199/29 ip6:2002:408e:32e0::/48 ip6:2001:5a8:4:7d0::/60 -all"
More information about the ipv6-ops