-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
David Brodbeck wrote:
Matthew(_dot_)van(_dot_)Eerde(_at_)hbinc(_dot_)com wrote:
I think most domains will run black/white SPF domains where
the authoritative constants are all 1, with a final 0all.
But it's still a good idea to build flexibility into SPF to
encourage adoption.
Hmm...I guess the question is, is the added flexibility worthwhile
enough to justify a significant increase in complexity? I
see a few issues:
- SPF checking libraries will no longer be returning a nice, simple,
multiple-choice response. They'll be returning a probability. This
changes and complicates the interface with other programs.
I could see libraries with functions like
spf_get_probability_of_authorization(...)
which will return the raw probability (or ERROR)
and
spf_get_simple_result(...)
which will round probabilities over 50% up to a PASS
or if the user specifies a different percent, that percent
or if the user wants 40-60% to be an ERROR, fine
or if... (etc.)
and
- Currently, the way the MTA is supposed to react to each of the
possible SPF returns is pretty cut and dried. When you throw in
probabilities, it becomes much hazier. At what point do I bounce
the
mail? 95%? 90%? 50%? Everyone will make their own
choices, and we no
longer really have a standardized, predictable response. The whole
thing becomes much more non-deterministic. Different sites will be
treating the same SPF record completely differently.
This is a good thing. Different people have differing levels of
paranoia.
- This would be enough of a change to the syntax to require a new
version string and new versions of all the libraries. Is it worth
it?
Sure. At least run it up the flagpole and see who salutes.
Matthew(_dot_)van(_dot_)Eerde(_at_)hbinc(_dot_)com
805.964.4554 x902
Hispanic Business Inc./HireDiversity.com Software Engineer
perl -e"map{y/a-z/l-za-k/;print}shift" "Jjhi pcdiwtg Ptga wprztg,"
-----BEGIN PGP SIGNATURE-----
Comment: pub key http://matthew.vaneerde.com/pgp-public-key.asc
iD8DBQFBLRPNUQQr0VWaglwRAh9FAKC/NftKtOM30gPTwGUW+RXkdVIJ2wCgnNOi
qimhofuEReM3IpbLGKN/yw4=
=LFsW
-----END PGP SIGNATURE-----