In that case, what is the SSP result when a message does not contain a
valid Originator Signature, and the Originator Domain has a policy of "all"?
"not compliant"
The whole business about third-party signatures is a DKIM-based
mechanism to decide what to say in that case. If the verifier sees
another signature that they "like", the result is "not Suspicious".
If the recipient sees another signature it likes, it's not going to do
an SSP lookup at all, so I don't see any value in giving recipients
directions for a situation that won't happen.
R's,
John
_______________________________________________
NOTE WELL: This list operates according to
http://mipassoc.org/dkim/ietf-list-rules.html