Our code should handle that correctly, and testing it seems fine. It will only do an A query if it's looking at an ip4 address.
I think the problem is dns errors, there are several things in our logs which imply that we were unable to get a txt record in the last couple days, though not today. Our caches all look to have the correct data now, so I don't know what was going on then. Brandon On Wed, Jan 18, 2017 at 5:33 AM, Vick Khera <[email protected]> wrote: > > On Wed, Jan 18, 2017 at 7:41 AM, Steve Freegard <[email protected]> > wrote: > >> I've had a report from a customer this morning regarding one of their >> customers messages being flagged as "Gmail couldn't verify that >> baerdijk.nl actually sent this message (and not a spammer)." despite >> having a correct SPF record at the time: >> >> v=spf1 mx ~all >> >> The received headers show: >> >> Received-SPF: softfail (google.com: domain of transitioning >> [email protected] does not designate 93.157.136.114 as permitted sender) >> client-ip=93.157.136.114; >> Authentication-Results: mx.google.com; >> spf=softfail (google.com: domain of transitioning [email protected] >> does not designate 93.157.136.114 as permitted sender) >> [email protected] >> >> > You didn't show the actual received headers showing its entry into gmail... > > Anyhow, you've changed your SPF records already, so I'm assuming you've > fixed it. > > > _______________________________________________ > mailop mailing list > [email protected] > https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop > >
_______________________________________________ mailop mailing list [email protected] https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
