undoing the DAMAGE that SPF has done
There's no "damage", if you don't like it just don't publish a sender
policy.
There is damage, even for a total non-adopter, like me.
First, it's drained off a nontrivial amount of effort that could have
gone towards developing something more effective.
Second, because it breaks bounces, and because some people feel that
the appropriate reaction to that is not "don't do that, then" but
rather to break bounces even more contrivedly, I've already had one
message produce a misfire from my automated filtering because its
envelope-from was mangled by SRS (itself a direct consequence of SPF).
/~\ The ASCII der Mouse
\ / Ribbon Campaign
X Against HTML
mouse(_at_)rodents(_dot_)montreal(_dot_)qc(_dot_)ca
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
_______________________________________________
Asrg mailing list
Asrg(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/asrg