Surely you have considered this, but what is the rationale for pushing
to distributions SPF implementations that are not known, according to
<http://www.openspf.org/Implementations>, to fully comply with rfc
4408?
What exactly are the things that lead to non-compliance? Are they
listed somewhere?
Will the package documentation point out that it does or does not
comply fully with the specification or has or has not passed the
current test suite?
The output of this test suite maybe?
BTW don't we want to read "comply" where "conform" is written in
... there are currently two library implementations that are
known to _fully conform_ to the final SPFv1 specification (RFC
4408)
I'm trying to understand the difference between "comply" and "fully
conform"
in this context (my native language not being English), could you
please shed some light on that?
-------
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