In the 111.spf1-test.mailzone.com policy record, there is an unsupported mechanism "gpg", which the tests seem to indicate only triggers a problem when it gets to processing the mechanism, however in the 112.spf1-test.mailzone.com policy, there is a mechanism "mp3" which seems to cause the tests to fail regardless of position of the mechanism.
My question; Should clients parse the entire record for syntax errors before policy processing commences, or should they do it as they process the record.
There was a conversation thread in the archives about complete processing of the policy (which seemed to be in reference to when to get redirect/exp modifiers out).
Wayne postulated that an SPF syntax error should be caught regardless of the position in the record (which makes sense and I agree with), but this does not seem possible with the records & tests for the subdomains 111 & 112.
Comments?
-Gary
-------
To unsubscribe, change your address, or temporarily deactivate your subscription,
please go to http://v2.listbox.com/member/?listname=spf-devel@v2.listbox.com
My question; Should clients parse the entire record for syntax errors before policy processing commences, or should they do it as they process the record.
There was a conversation thread in the archives about complete processing of the policy (which seemed to be in reference to when to get redirect/exp modifiers out).
Wayne postulated that an SPF syntax error should be caught regardless of the position in the record (which makes sense and I agree with), but this does not seem possible with the records & tests for the subdomains 111 & 112.
Comments?
-Gary
-------
To unsubscribe, change your address, or temporarily deactivate your subscription,
please go to http://v2.listbox.com/member/?listname=spf-devel@v2.listbox.com