From the point of ISP, email addresses that are just wrong and where you
can tell the MTA to be off immediatly almost after the start of SMTP
tranmission, are not a big deal. Yes, it does consume some processing time
on the server, but its marginally very small compared to actually
receiving entire message, storing it on the serer, sending it through
filters, delivering it to mailbox, etc (logs do grow, unfortunetly, but
hard drive space is now inexpensive and cdburners and blank cds too).
Now the above is generally applicable to small ISP, large ISPs with
many 100,000 of email accounts may not see it this way...
But from "make spammer suffer" view - if spammer has to do 100 failed
attempts to get 1 successfull one and even there he does not know if
email will ever reach a recepient or if it may just go through alarm
making it harder for him to send even more messages, then its all working
in our favor.
On Thu, 6 Mar 2003, Kee Hinckley wrote:
At 1:59 PM -0500 3/6/03, Jim Youll wrote:
But if you had a proper client that hid all the work, you could
"give" a different e-mail address to every correspondent, and if it
leaked out, you need only cancel that one and give that particular
correspondent a freshly-generated address, no?
Read the thread on striker's spam problem. Hundreds of thousands of
messages a day, all bouncing due to a dictionary attack gone wrong.
Now consider what happens if everyone has hundreds of temporary
addresses that can get into spammers hands. Sure, you cancel it, but
that doesn't mean the spammer stops sending. You've made your life
more complicated, and you've made your ISPs life hell.
_______________________________________________
Asrg mailing list
Asrg(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/asrg