Scott Kitterman wrote:
From the receiver's view, SPF is about deciding whether or
not to go on to DATA. Op DKIM is additional information to
help the receiver make the decision. Fail is still Fail,
the question is what to do with it.
Okay, now from the sender's POV: "v=spf1 op=dkim -all" won't
work as expected with all implementations and receivers which
don't have any clue what "op=dkim" might be, plus those who
don't care.
If you (as sender) want reliable results with all receivers
something like "v=spf1 op=dkim ~all" might make more sense,
or "v=spf1 op=dkim ?all".
Add some "..." before ?all / ~all / -all for more realistic
policies, but while we talk about semantics the simple cases
are clearer.
Are you really interested in some "reject if you don't know
or don't like or don't support DKIM" modifier ? It could
only have a technical purpose for receivers that do _all_ of
SPF, op=dkim, and DKIM.
It's obviously useless for all other receivers. So what is
it that a SPF + op=dkim + DKIM receiver would do differently
from a SPF + DKIM receiver ? And whatever that is, do you
still want what you'd get from a pure SPF or a SPF + DKIM
(without op=dkim support) receiver for a FAIL (i.e. reject) ?
Bye, Frank
-------
Sender Policy Framework: http://spf.pobox.com/
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/?listname=spf-discuss(_at_)v2(_dot_)listbox(_dot_)com