-----Original Message-----
From: owner-spf-discuss(_at_)v2(_dot_)listbox(_dot_)com
[mailto:owner-spf-discuss(_at_)v2(_dot_)listbox(_dot_)com]On Behalf Of Scott
Kitterman
Sent: Friday, August 05, 2005 9:08 AM
To: spf-discuss(_at_)v2(_dot_)listbox(_dot_)com
Subject: RE: [spf-discuss] Re: SPF test suite
-----Original Message-----
From: owner-spf-discuss(_at_)v2(_dot_)listbox(_dot_)com
[mailto:owner-spf-discuss(_at_)v2(_dot_)listbox(_dot_)com]On Behalf Of Frank
Ellermann
Sent: Friday, August 05, 2005 8:58 AM
To: spf-discuss(_at_)v2(_dot_)listbox(_dot_)com
Subject: [spf-discuss] Re: SPF test suite
Scott Kitterman wrote:
Among my favorite is an IP address after an a or mx
mechanism. It's not an error
Actually it is, <domain-spec> ends with either <toplabel>
or <macro-expand>.
In both cases there's more than only digits: A <toplabel>
starts with ALPHA, and a <macro-expand> starts with "%{".
there is no TLD for .123 (or whatever).
Hidden in domain-end = ( "." toplabel ) / macro-expand
John specified it in 3696 among others, and he's supposed
to know what follies ICANN plans, he was the IETF liaison
in (on ? at ? lang=en-DE ;-) the ICANN board.
I raise a warning on that kind of thing now.
Okay, but in that case it's also a real error. Bye, Frank
Cool. Then that's one that pySPF doesn't currently catch. More code to
write.
That's fixed and posted. RFC 3696 ends up having suprising useful
recommendations on how to validate the top level domain. Test and see if
it's all numeric, if not, just use DNS to discover if it's real.
Scott K