On Monday 22 August 2005 23:20, wayne wrote:
In
<20050822175736(_dot_)9cea77b9ab63029d53d9cced8db53358(_dot_)6e02374947(_dot_)wbe(_at_)email(_dot_)email(_dot_)secureserver(_dot_)net>
Brad Owen <bowen(_at_)godaddy(_dot_)com> writes:
This may not be the appropriate place to post this but if there is someone
from amazon lurking on the list please check your SPF record.
I think this is an appropriate place for this kind of thing, thanks
for posting about it.
We used to have someone from amazon.com who hung around here (Jonathan
Gardner), but he hasn't posted recently. I'll email him anyway.
$ host -t txt amazon.com
amazon.com text "\"v=spf1 ip4:207.171.160.32/28 ip4:207.171.180.176/28
ip4:207.171.164.32/28 ip4:207.171.190.0/28 ?all\" "
amazon.com text "spf2.0/pra ip4:207.171.160.0/19 ?all"
When I last ran a survey of all .com domains around the beginning of
July, their record did not have this problem. So, it is a realatively
recent change.
The " in the DNS record is causing checks to fail.
Others have correctly pointed out that their records won't cause an
SPF FAIL, but I think you mean that "fail" as in "doesn't do what they
intend".
Thanks all for letting me (us) know about this. We're looking into it.
--
Jonathan Gardner
jonagard(_at_)amazon(_dot_)com