Stuart D. Gathman wrote:
I am now even more commited to the interpretation that museum needs
a trailing dot to be a FQDN.
Won't fly, we get into the same trouble with a:%{l} for a local part
"museum" (without dot, but actually it doesn't matter). There are
also SPF constructs to select a single label out of several labels,
and eventually you've to check if it (whatever it is) has an address.
The only place to fix this would be the definition of <target-name>,
we could demand that it must have a trailing dot if it has only one
label, independent of the used macro(s), %{h}, %{l}, or what else.
And by "demand" I mean a very shaky "erratum", RFC 4408 obviously
doesn't do what Scott and you propose. At least "protecting the
DNS root servers" is a good excuse. I hope.
Add it anyway to the test suite, and let implementations do what
they like for the moment until that's resolved. One thing they
shouldn't do is crash.
Frank
-------
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/?list_id=735