I'm currently working on a small SPF patch/client for Exim. I have a
few questions regarding the test suite (1.991) and RFC Draft 02.9.5
that have been bugging me.
1. Tests #89 - #96 / RFC Draft Appendix A
The TXT record for 70.spf1-test.mailzone.com is "v=spf1
exists:%{lr+=}.lp._spf.spf1-test.mailzone.com -all". Appendix A lists
valid macro delimiters -- the equal sign is not included. Was this an
accidental omission in the RFC Draft, or should tests #89 through #96
return "unknown" (parse error)?
2. Semantics of "include" mechanism are no longer clear
Since the extra result values were added in 02.9.5, it's not clear how
"include" should behave. For example, Test #82 seems to indicate that
if a recursive query returns "none", then "include" should return
"unknown". Could text be added to Section 4.2 that covers all
possible recursive return values, much like the "include" section from
the November 02.7 RFC Draft (when softfail was last seen)?
3. Section 7.2 typo
The "%{p2}.trusted-domains.example.net" example is listed twice in the
RFC Draft.
The test suite has been very useful. Many thanks for that. However,
I'll throw in my vote that it's time to split out test.txt into
test-{must,should,mailspfqueryonly}.txt.
-------
To unsubscribe, change your address, or temporarily deactivate your subscription,
please go to http://v2.listbox.com/member/?listname@Ë`Ì{5¤¨wâÇSÓ°)h
few questions regarding the test suite (1.991) and RFC Draft 02.9.5
that have been bugging me.
1. Tests #89 - #96 / RFC Draft Appendix A
The TXT record for 70.spf1-test.mailzone.com is "v=spf1
exists:%{lr+=}.lp._spf.spf1-test.mailzone.com -all". Appendix A lists
valid macro delimiters -- the equal sign is not included. Was this an
accidental omission in the RFC Draft, or should tests #89 through #96
return "unknown" (parse error)?
2. Semantics of "include" mechanism are no longer clear
Since the extra result values were added in 02.9.5, it's not clear how
"include" should behave. For example, Test #82 seems to indicate that
if a recursive query returns "none", then "include" should return
"unknown". Could text be added to Section 4.2 that covers all
possible recursive return values, much like the "include" section from
the November 02.7 RFC Draft (when softfail was last seen)?
3. Section 7.2 typo
The "%{p2}.trusted-domains.example.net" example is listed twice in the
RFC Draft.
The test suite has been very useful. Many thanks for that. However,
I'll throw in my vote that it's time to split out test.txt into
test-{must,should,mailspfqueryonly}.txt.
-------
To unsubscribe, change your address, or temporarily deactivate your subscription,
please go to http://v2.listbox.com/member/?listname@Ë`Ì{5¤¨wâÇSÓ°)h