Kevin,
EBay is running into the same problem another user reported http://www.logsat.com/spamfilter/forums/showmessage.asp?messageID=4460" CLASS="ASPForums" TITLE="WARNING: URL created by poster. - here ( http://www.logsat.com/spamfilter/forums/showmessage.asp?messageID=4460" CLASS="ASPForums" TITLE="WARNING: URL created by poster. - http://www.logsat.com/spamfilter/forums/showmessage.asp?messageID=4460" CLASS="ASPForums" TITLE="WARNING: URL created by poster. - http://www.logsat.com/spamfilter/forums/showmessage.asp?messageID=4460 ).
ebay.ca SPF record contains include directives which tell the SPF filter to retrieve further information from ebay's subdomains:
"v=spf1 mx include:m._spf.ebay.com include:s._spf.ebay.com include:c._spf.ebay.com include:p._spf.ebay.com ~all"
The problem is that the subdomains specified are not really domains:
m._spf.ebay.com s._spf.ebay.com c._spf.ebay.com p._spf.ebay.com
but just entries under the _spf.ebay.com domain.
The RFC states that SPF records are to be retrieved from a "DOMAIN", not a host record. All the 4 entries above are *not* domains, so even though they have an SPF record, it's not supposed to be queried. This means that ebay.ca and ebay.com have an invalid spf confguration.
However I checked the domain using the tolls that http://spf.pobox.com" CLASS="ASPForums" TITLE="WARNING: URL created by poster. - http://spf.pobox.com" CLASS="ASPForums" TITLE="WARNING: URL created by poster. - http://spf.pobox.com provides, and they do say that the domain complies (against their own rules...)
We've been seing more and more domains that, while incorrectly configured, are marked as "good" by SPF checkers. We'll be doing research to see how we should proceed.
Roberto F. LogSat Software
|