wayne wrote:
The choice of defining modifiers as accepting <macro-string> rather
than <domain-spec> was very intentional.
For exp= and redirect= it's <domain-spec>, that's a proper subset of
<macro-string>.
For include-subdomains=yes the "yes" was also a kind of <macro-string>
subset, the string "yes". For options it's similar, it's just a list
of named properties. Using the SPF syntax element <name> for the
individual properties. How they are sparated is mostly a matter of
taste, for dots I was sure that lousy implementations will eat it.
I would recommend not using a semicolon and other characters that
bind seems to like to escape since I think they cause confusion.
Yes, that was also my concern. With the dots I was sure that this
can't go wrong in better than hopeless implementations, or in Web
forms allowing to create at least simple v=spf1 TXT records.
Of course any modifier syntax must match <macro-string>, it can't
have say quoted strings with spaces. But a specific modifier can
use a proper subset of <macro-string> like "yes", or a list of dot
separated <name>, or the syntax of an IP, or a <domain-spec>, etc.
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