In
<200401290920(_dot_)08245(_dot_)dan(_at_)boresjo(_dot_)demon(_dot_)co(_dot_)uk>
Dan Boresjo <dan(_at_)boresjo(_dot_)demon(_dot_)co(_dot_)uk> writes:
There is no need to cater for 'unrecognised mechanisms', and I feel that the
best change that could be made to the current spec is to say that any
mechanism or modifier not defined in the spec is an error.
The current spf1 spec says that unknown mechanisms are an error, but
unknown modifiers are ignored. This lets SPF be a reasonable place to
advertise other email related policies. If you add something like
"gpg=<where/how to locate keys>", this will be ignored by all spf1
implementations, but allows those that want to locate gpg keys an easy
way to do it.
Please don't destroy SPF with feature creep and misplaced 'extensibility'.
Agreed.
Let's please freeze it and concentrate on evangelism and adoption rather than
creating new opportinities for confusion and incompatibility.
s/evangelism/writing code/
-wayne
-------
Sender Permitted From: http://spf.pobox.com/
Archives at http://archives.listbox.com/spf-discuss/current/
Latest draft at http://spf.pobox.com/draft-mengwong-spf-02.9.4.txt
Wiki:
http://spfwiki.infinitepenguins.net/pmwiki.php/SenderPermittedFrom/HomePage
To unsubscribe, change your address, or temporarily deactivate your
subscription,
please go to
http://v2.listbox.com/member/?listname(_at_)©#«Mo\¯HÝÜîU;±¤Ö¤Íµø?¡