In <1de(_dot_)2dae7719(_dot_)2ebbe170(_at_)aol(_dot_)com> "Brian Barrios"
<brianantispam(_at_)aol(_dot_)com> writes:
and now paypal, publishing incorrect spf2.0 format?
paypal.com. 3374 IN TXT "v=spf1 mx
a:outbound1.den.paypal.com a:outbound2.den.paypal.com
a:smtp-outbound.nix.paypal.com include:c._spf.ebay.com
include:s._spf.ebay.com include:m._spf.ebay.com
include:p._spf.ebay.com
~all"
paypal.com. 3374 IN TXT "v=spf2.0/pra mx
a:outbound1.den.paypal.com a:outbound2.den.paypal.com
a:smtp-outbound.nix.paypal.com include:c._sid.ebay.com
include:s._sid.ebay.com include:m._sid.ebay.com
include:p._sid.ebay.com
~all"
Paypal (and ebay) have had (incorrect) SPF records in for about a month now.
Do you spot anything wrong with the record other than the "v="? I just want
to be sure I catch everything before I let the know.
Paypal's records don't fit into a 512 byte UDP DNS packet and cause a
fallback to DNS over TCP. This can cause problems for MTAs that
either use resolvers don't support DNS over TCP, or site behind
firewalls that (incorrectly) block TCP/53.
I can't check the SenderID records, just the SPF records, but they
seem to parse fine for me. (Both ebay and paypal.)
-wayne