Scott Kitterman wrote:
Hi Scott, your tool still hates mx::%%%_/.claranet.de/27 ;-)
It will parse that now.
Frank wrote:
LOL, maybe we need two SPF validators, "expert mode" for the
weird constructs, and "simple mode" for the real SPF records.
BTW, it does accept mx:invalid but that's _really_ invalid:
domain-spec = macro-string domain-end
domain-end = ( "." toplabel ) / macro-expand
There's no dot in invalid, and it's no <macro-expand>. For a
minimally "valid" invalid I'd need mx:.invalid with a dot.
Is that true, that we cannot use domain names without a dot in them?
I guess it's unlikely to ever come up, but domain "ws" has both an A and
MX, so if they wanted to use that with an a: or mx: mechanism I guess they
couldn't. (Easy enough to just define a subdomain).
I wonder if mx:ws. would pass the ABNF or various parsers? maybe the
trailing dot could be used to distinguish an actual TLD from a broken
short name or local reference.
--
Greg Connor <gconnor(_at_)nekodojo(_dot_)org>
on my squirrelmail right now