Re: non-ascii SPF policy

On Wed, 5 Oct 2011, Stuart D. Gathman wrote:

> how to code this in YAML.  The important thing is that non-ascii bytes in the 
> SPF policy are a syntax error.

Hmm.  What about USACII control chars?  These will trigger other syntax errors
if used anywhere outside domain-spec.  Macro-literal cannot represent
control chars, but they could be included verbatim and the policy
still be "usascii".  For instance, what should be the result of this
policy (using YAML 8-bit string escapes):

SPF: "v=spf1 a:\x01ctrl.example.com -all"

In this case, domain-spec is defined to consist of (in macro-literal) "visible
chars except %", and so the result is again PermError (whether
or not the domain actually exists).  I will add another test case when
we all agree on this result.

--
 	      Stuart D. Gathman <[email protected]>
     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.