On Oct 19, 2013, at 00:13, Dominik George <n...@naturalnet.de> wrote:
>> if i would be you i would *not* use "v=spf1 mx ~all" > > If I were [...] ... > >> here you go for ipv6 >> >> http://www.openspf.org/SPF_Record_Syntax#ip6 > > Jeez, I don't believe it. The problem is that the mx mechanism simply > only enumerates A records of MXs. That's broken ... The only place I've seen this problem with the lookup of IPv6 addresses via the 'mx' construct in SPF records was Gmail, which was resolved, and recently some small local operator who kept insisting that the problem was on our side until the evidence was so overwhelmingly pointing to his own setup that he could no longer ignore it. He made the same claim, however, but never backed it up. How are you reaching your conclusion? Because this only mentions A records and IPv4 prefixes? http://www.openspf.org/SPF_Record_Syntax#mx Mvg, Joni
