On Thursday 15 March 2007 13:46, Thomas Jacob wrote:
It seems to support some modifiers not in the RFC (default= is one).
Bottom line though this shouldn't affect libspf2's interoperability
with other fully RFC compliant SPF implementations (apart
from maybe the limits issue), or am I mistaken here?
That is correct. This is not even a 'violation' of the RFC as RFC 4408 has
explicit allowance for addition of unknown modifiers later.
The result names are only problematic for programs calling libspf2 within a
system. This is an integration issue that is minor (libspf2 is well
documented and so as long as an integrator RTFM, the shouldn't be a problem).
It is not an interoperability concern.
Processing limits are, as you said, the core interoperablity issue here. BTW,
I've submitted your patch to Ubuntu.
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
please go to http://v2.listbox.com/member/?list_id=735