"Roedy Green" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > On Tue, 11 Oct 2005 11:45:03 -0400, Mike Meyer <[EMAIL PROTECTED]> wrote > or quoted : > >>Jeff Poskanzer, now *he* has a spam problem. He gets a few million >>spams a day: <URL: http://www.acme.com/mail_filtering/ >. > > It is a bit like termites. If we don't do something drastic to deal > with spam, the ruddy things will eventually make the entire Internet > unusable. > > the three keys to me are: > > 1. flipping to a digital id based email system so that the sender of > any piece of mail can be legally identified and prosecuted. > If every piece of anonymous email disappeared that would go a long way > to clearing up spam. Let those sending ransom notes, death threats > and hate mail use snail mail. As a second best, correspondents are > identified by permission/identity/encryption keys given to them by > their recipients.
Too complicated. > > 2. flipping to a sender pays system so that the Internet does not > subsidise spam. This would turn cost of sending mail to ordinary people. Spammers pay for bandwith as much as receivers (except in case when they hijack server). > > 3. Mail is not transported without prior permission. The receiver can > turn that permission on and off any time he chooses. This is > basically an automated version of what Zaep does where the sender is > not consciously aware of the permission-getting step. That is the solution. rcpt from:<[EMAIL PROTECTED]> rcpt to:[EMAIL PROTECTED] not authorized Then simply users have to maintain list of domains/users that can send mail which need just one more smtp command. mail from:<[EMAIL PROTECTED]> auth req:<[EMAIL PROTECTED]> ok auth req:<[EMAIL PROTECTED]> request already in queue rcpt to:<[EMAIL PROTECTED]> not authorized user authorization: helo victims.org ok user:[EMAIL PROTECTED] ok password:victim ok auth list req ... ... ... auth add:<[EMAIL PROTECTED],org> error no such user at slam org auth add:<[EMAIL PROTECTED],org> ok auth add:<[EMAIL PROTECTED]> ok auth remove:<[EMAIL PROTECTED]> ok auth add:<[EMAIL PROTECTED]> ok quit and there it is, spam free solution. User can maintain two email addresses one for general public and one spam free. Of course smtp should be really extended to support user authorization. Greetings, Bane. -- http://mail.python.org/mailman/listinfo/python-list
