I understand. But "end to end" issues are very different
from network abuse issues. Preventing network abuse isn't
censorship. Preventing forgery of my domain in spam isn't
censorship (and yes, it happens a fair bit.)
The RMX-style solutions allow recipients to make ISP's
accountable for their network traffic. They don't affect
end-user accountability, privacy, or authentication.
I agree. RMX would merely allow for me to protect my domain from
getting spoofed. By no means is it an anti-spam method. I can not
simply implement a force-RMX-check implementation in my mail server
anymore that I can perform a force-reverse-DNS check or
force-HELO-check. There is simply too much email from valid senders
with pathetic mail administrators. However, I can perform an RMX check
and if the domain is protected by RMX..I can ensure that the sending
source is from a listed IP.
_______________________________________________
Asrg mailing list
Asrg(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/asrg