DKIM's purpose has been lost with the continued out of scope undefined
reputation modeling. A concern raised over and over again, Assessment |
Reputation - wink wink, same thing when it come to coding it. Word
smithing does not solve implementation issues.
I don't agree at all with these claims. An assessor module can make a complete
determination about what to do with a message using inputs from DKIM and
several other systems of its choosing (e.g. SPF) without consulting any
reputation system at all. Reputation is just another input to the assessor.
The total set and weighting of the assessor's inputs is both a matter of
software design and local policy.
They are certainly disjoint in my implementation.
_______________________________________________
NOTE WELL: This list operates according to
http://mipassoc.org/dkim/ietf-list-rules.html