william(at)elan.net wrote:
I see no clear answer in RFCs if "MX 0 ." is valid or not.
Depends, somebody mentioned on the general IETF list that one
of those "alternate DNS roots" managed to have an IP for their
root, and then "dot" could be a "valid" MX (in their parallel
universe).
Yahoo obviously says it is
Mark is the author of draft-delany-nullmx, eating his own dog
food is only consequent, and Yahoo! won't use "v=spf1 -all" for
a similar effect without call-back-verification at the moment.
not at all clear to me that you can use just "." as valid
host name for target of MX.
Try `nslookup -q=any .`, if you get no IP it's a "bogusmx" ;-)
-------
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