Yakov Shafranovich <research(_at_)solidmatrix(_dot_)com> wrote:
If the entire purpose of these proposals is to make sure that the sender
is who he claims to be according to DNS information,
I would say "has permission to claim association with a domain"
than what we could
do is create an ESMTP extension to pass sender's information to the
server MTA which will be verified via DNS. Since we need to change MTA
software to support sender rewriting schemes, we might as well add a new
extension instead, to pass that information explicitly.
Sounds fine to me. Can we have a show of hands from people in the
IETF who are *not* opposed to modifying SMTP?
Of course this is just devil's advocate speaking :)
Yes, and there are standard arguments against it:
- it will take too long to deploy
- it won't stop spam.
My responses are:
- it will take less time to deploy than waiting forever for a perfect
solution
- it's not intended to stop spam. It's intended to allow the
recipient to better deal with the spam he does get.
99.99% of the spam I get is forged. Call me naive, but this says to
me that spammers believe that forgery is an important part of the
spamming process.
This addition would also get rid of the forged viruses & worms. If
nothing else, it would make it plainly obvious who's stupid enough to
run a system which gets viruses. Right now, I don't get viruses, but
I get tons of spam from software by antivirus companies, claiming to
have found a virus in a message I sent. The fact that the viruses are
forged, and that their "notifications" are spam, is something the
virus companies apparently don't get.
Alan DeKok.
_______________________________________________
Asrg mailing list
Asrg(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/asrg