On Tue, 23 May 2006, David Saez Padros wrote:
There is no such charset restriction in the current DNS spec. There may be
some broken/obsolete DNS servers (e.g. M$), but yours doesn't need to be
one of
them. As long as your DNS server (the one hosting / responding to your SPF
records) works, there is no problem.
BTW, the broken M$ DNS affects RDNS delegation as well as verifying
BATV/SRS/SES via DNS.
But the problem could also be on the client side, the SPF check tool at
check-auth(_at_)verifier(_dot_)port25(_dot_)com just gives that results:
That is a broken implementation. A good reason to proceed post haste
with the updated test suite.
And in fact, your example is an excellent item for the new test suite!
--
Stuart D. Gathman <stuart(_at_)bmsi(_dot_)com>
Business Management Systems Inc. Phone: 703 591-0911 Fax: 703 591-6154
"Confutatis maledictis, flammis 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