9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: lucio@proxima.alt.za
To: 9fans@cse.psu.edu
Subject: Re: Re[2]: [9fans] Returned mail: Service unavailable
Date: Fri, 22 Aug 2003 08:59:53 +0200	[thread overview]
Message-ID: <38d0dc3fee3ae322fbaa23c548ffc355@proxima.alt.za> (raw)
In-Reply-To: <007001c3687b$a5e1a340$b9844051@insultant.net>

> i know how to do it, but i have bad carpal tunnel.  anyway, the basic
> idea is to parse the Received: headers and bitch to every site;
> backpressure works.  you could even plumb it out of faces; punch
> the message up and say "kill 'em".
>
That's perfectly reasonable, it's something SPAMCOP (spamcop.org?)
could have thought of.  I haven't used SPAMCOP in a long time, so I
can't recall exactly what they actually do, maybe their approach is as
close to that as needed.  Can't say it's had any effect, but the swell
of indignation is certainly growing.  Perhaps a certain critical
mass needs to be reached first and we may be close to it.

Unfortunately, spoofing Received: headers has long been a weapon in
the hands of spammers, so one has to be prepared to negotiate.  On the
other hand, as mentioned before, SMTP authentication may well become
the norm, in which case the relay agent can be compelled to accept
legal liability for the resources consumed by unsolicited mail.  This
is close in practice to implementing postage stamps at the sender's
expense.

++L

PS: SPAMCOP requires one to confirm, at some bother, all
notifications, which is far too demanding for the average user, hence
a spectacular lack of success.



  reply	other threads:[~2003-08-22  6:59 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-22  4:46 Mail Delivery Subsystem
2003-08-22  6:28 ` northern snowfall
2003-08-22  5:15   ` lucio
2003-08-22  6:37     ` northern snowfall
2003-08-22  5:22       ` lucio
2003-08-22  5:55       ` boyd, rounin
2003-08-21  9:38         ` okamoto
2003-08-22  6:23           ` boyd, rounin
2003-08-22  6:15       ` Rob Ristroph
2003-08-22  7:16         ` northern snowfall
2003-08-22  6:27       ` Re[2]: " Martin Althoff
2003-08-22  6:35         ` boyd, rounin
2003-08-22  6:33           ` lucio
2003-08-22  7:04             ` boyd, rounin
2003-08-22  6:59               ` lucio [this message]
2003-08-22  7:33                 ` boyd, rounin
2003-08-22  6:33           ` lucio
2003-08-22  6:35             ` lucio
2003-08-22  7:08             ` boyd, rounin
2003-08-22  7:10             ` Re[4]: " Martin Althoff
2003-08-22  7:03               ` lucio

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=38d0dc3fee3ae322fbaa23c548ffc355@proxima.alt.za \
    --to=lucio@proxima.alt.za \
    --cc=9fans@cse.psu.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).