[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: Remailer Abuse Solutions
Sounds like another attempt to raise the cost of using the Net, nothing more.
Sure, paying postage (Is $1 really necessary? Why email when snailmail's
cheaper??) may reduce general spamming done by local punks, but it does
nothing
against corporations which already spend millions on snailmail spamming.
Also,
what happens when your long-lost friend comes across your addy and tries to
email you? Surely you don't want to charge postage for an otherwise free
service to him/er. Maintaining a list of "accepted sources" would be a hassle
not many people would accept.
Slight variation is to generate a list of "toll these entities." A smaller
list
(hopefully :-), and generally easier because then it defaults to no-bill. Or,
to accomodate superstars/actors/etc, generate files like rhosts.accept
rhosts.deny in UNIX. That way, the user may use either/both types of
filtering.
Again, the average user wouldn't want to deal with this hassle, everyone's
mail
software would have to be rewritten, and I basically oppose any ideas that
cost me money for something I already get for free... :-)
PM
_______________________________________________________________________________
From: Peter Hendrickson on Wed, Nov 13, 1996 4:10
Subject: Remailer Abuse Solutions
To: [email protected]
What do you do if you are operating a remailer and somebody complains
they are getting spammed? That's easy, you keep a list of people that
you don't send mail to. What's hard is if that person wants to receive
other anonymous mail.
The solution is easy: charge e-cash to send mail to certain addresses
and send the money to the owner of the account. Never put an address
on a kill list, just raise the price of sending mail to it. This
generates lots of positive publicity for your remailer. People will
beg to be spammed!
And, since the remailer operator handles the financial parts of the
deal, the technically naive "victim" does not have to have specialized
knowledge or even an e-cash account.
This also eliminates the spam problem generally. If you are plagued
by spam, create a list of names you will accept mail from. When a
message comes in that is not on the list, return a message directing
them to send you the mail through a paying remailer.
This solves a problem for famous people, too. They get lots of
mail but they don't have time to read it all. How to sort it? Raise
the price of sending a message. (I heard that Arnold Schwarzeneggar
was once paid $1 million just to read a script and look at the set
of a movie with no obligation to act in it.)
Okay, now lets go to mailing lists. We like to read anonymous mail
on this list, but we don't like getting spammed. It's hard to filter
anonymous mail for obvious reasons.
The solution: don't accept anonymous mail. Only people on the "approved"
list would be allowed to post. People who wish to post anonymously
could then send mail through the paying remailer to people on the
"approved" list and request that their message be relayed. Most people
on the list would be happy to accept a dollar or two to provide this
service. This would eliminate inappropriate mail while allowing anybody
to post.
For that matter, postings to the list itself could be priced at, say,
a dollar to cut down on the noise levels.
Payments, and addresses which complicate payment, make it harder to
rely on the remailer network. When you send a message through a
few remailers and make a faux pax on the last one, you won't know
what happened. Did one of the remailers go down? Did you make a
mistake?
I think I know a solution to this one, too. If somebody wants to
get error messages, they include a random 128 bit number with their
message. This is a different number for each remailer in the chain.
When an error occurs, the remailer distributes an error message
with the number attached.
Error message distribution is pretty easy. The remailer operator
could publish a web page with the errors. Or, the messages could
be bundled and made available through anonymous ftp, or mailed to
an error message mailing list, or posted to a newsgroup.
Peter Hendrickson
[email protected]
------------------ RFC822 Header Follows ------------------
Received: by mail.ndhm.gtegsc.com with SMTP;13 Nov 1996 04:10:17 -0400
Received: from toad.com by delphi.ndhm.gtegsc.com with SMTP;
Wed, 13 Nov 1996 9:06:01 GMT
Received: (from majordom@localhost) by toad.com (8.7.5/8.7.3) id RAA13602 for
cypherpunks-outgoing; Tue, 12 Nov 1996 17:07:45 -0800 (PST)
Received: from netcom19.netcom.com ([email protected] [192.100.81.132])
by toad.com (8.7.5/8.7.3) with SMTP id RAA13594 for <[email protected]>;
Tue, 12 Nov 1996 17:07:36 -0800 (PST)
Received: from [192.0.2.1] ([email protected] [192.100.81.135]) by
netcom19.netcom.com (8.6.13/Netcom)
id RAA03014; Tue, 12 Nov 1996 17:07:31 -0800
X-Sender: [email protected]
Message-Id: <v02140b04aeaec9f1fa9b@[192.0.2.1]>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Tue, 12 Nov 1996 17:07:41 -0800
To: [email protected]
From: [email protected] (Peter Hendrickson)
Subject: Remailer Abuse Solutions
Sender: [email protected]
Precedence: bulk