mail.globalinkllc.com has no SPF record. However, their weird MX could
happen to a domain that does.
$ host -t mx mail.globalinkllc.com
mail.globalinkllc.com is an alias for redirect.mail.premiumservices.yahoo.com.
redirect.mail.premiumservices.yahoo.com is an alias for
ymb1.mail.vip.sc5.yahoo.com.
ymb1.mail.vip.sc5.yahoo.com mail is handled by 0 .
Currently, pyspf gets temperror for an MX mechanism and an MX record with
an empty name like the above.
What should the correct result be? Should the mechanism simply fail
to match? Or permerror?
--
Stuart D. Gathman <stuart(_at_)bmsi(_dot_)com>
Business Management Systems Inc. Phone: 703 591-0911 Fax: 703 591-6154
"Confutatis maledictis, flamis acribus addictis" - background song for
a Microsoft sponsored "Where do you want to go from here?" commercial.
-------
Sender Policy Framework: http://www.openspf.org/
Archives at http://archives.listbox.com/spf-discuss/current/
To unsubscribe, change your address, or temporarily deactivate your
subscription,
please go to
http://v2.listbox.com/member/?listname=spf-discuss(_at_)v2(_dot_)listbox(_dot_)com