Mailing List Archive

Obsolete modifiers (was: Softfail when spf-checking mails from this list, max_dns_mx=5)
Stuart D. Gathman wrote:

> However, modifiers aren't allowed to change the SPF result

Objection :-) Of course modifiers can modify the result,
for implementations supporting the modifier in question.

> I'll have to add a test:

> testdefault.example.com: IN TXT "v=spf1 default=pass"

> which had better result in neutral.

Good idea, an extremely old (late 2003 ?) modifier that
didn't make it in the first "frozen" spec. Maybe add
also a test covering the old include_subdomains=yes idea:

foo.bar.example without policy
bar.example with "v=spf1 include_subdomains=yes a -all"
Client says HELO foo.bar.example with corresponding IP

Frank

P.S.: Of course that gets us near to a point where we
need a IANA registry of modifiers. At the moment it's
in theory possible to invent a new default= modifier
doing wild and wonderful things, and the test suite
"shouldn't" (in theory) preempt such horrible ideas.


-------
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