Gnus development mailing list
 help / color / mirror / Atom feed
From: Steven L Baur <steve@miranova.com>
Cc: David Worenklein <dcw@gcm.com>,
	(ding) GNUS Mailing List <ding@ifi.uio.no>
Subject: Re: Unsolicited ads
Date: 10 Jun 1996 10:13:50 -0700	[thread overview]
Message-ID: <m2n32binu9.fsf@deanna.miranova.com> (raw)
In-Reply-To: Ketil Z Malde's message of 10 Jun 1996 08:07:44 -0700

>>>>> "Ketil" == Ketil Z Malde <ketil@ii.uib.no> writes:

>> David Worenklein <dcw@gcm.com> writes:
>> Some how, I've gotten onto an e-junk-mail list.  Has anyone thought
>> about ways of dealing with this?  For instance, maintaining a list
>> of all people who have sent me mail in the past and lowering the
>> score of an article if it's from someone not on the list?

The problem with this is that the worse offenders use throw-away
accounts, so the first message from that mailbox may well be the
last ...

Ketil> I maintain a list of all domains that have repeatedly sent me
Ketil> spam in the past, and use procmail to automatically discard
Ketil> mail from these domains.  Some magic ensures that messages that
Ketil> are replies to my own messages won't be affected.

Ketil> Of course, the list of rotten domains should perhaps be
Ketil> globally maintained, so that when enough spams have originated
Ketil> from some domain, it could be automatically blocked by all who
Ketil> wanted.

Yup.  There is a maintained black list.  Brian Edmonds
<edmonds@cs.ubc.ca> has a reference to it in a Gnus/antispam page:
	http://www.cs.ubc.ca/spider/edmonds/usenet/gnus/
(there's a reference to this in the Gnus FAQ).

Ketil> For my particular spam filtering, look at:
Ketil> http://www.ii.uib.no/~ketil/mailsorting.html 
(Also referenced by the Gnus FAQ, BTW).

The problem with any solution of this form is that it is reactive, and
ineffective against many spams.  A better long-term solution is going
to be maintaining a ``white list'', and filtering non-white list
e-mail to a lower priority mailbox.

I like the idea of only accepting personal e-mail that contains ecash
postage of some sort, and then only cashing in on the postage if you
deem the mail message not worth the time to read it.  The technology
for implementing this kind of a solution is well within the current
capabilities of Gnus all by itself, though it won't be of much use
until ecash (of whatever form) is more prevalent.

A wild idea off the top of my head:
How effective would a closed mailing list be that distributed the
equivalent of NoCEM information about spammers?  The messages would be
of the same form, and could be automatically processed by Gnus ...

-- 
steve@miranova.com baur
Unsolicited commercial e-mail will be proofread for $250/hour.
Andrea Seastrand: For your vote on the Telecom bill, I will vote for anyone
except you in November.


  reply	other threads:[~1996-06-10 17:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-06-10 13:30 David Worenklein
1996-06-10 13:53 ` Per Abrahamsen
1996-06-10 17:26   ` Steven L Baur
1996-06-10 15:07 ` Ketil Z Malde
1996-06-10 17:13   ` Steven L Baur [this message]
1996-06-10 20:30     ` Lars Magne Ingebrigtsen
1996-06-10 22:12       ` Steven L Baur
1996-06-11  1:47         ` Lars Magne Ingebrigtsen
1996-06-16  0:45         ` Clarification (was Re: Unsolicited ads) Steven L Baur

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=m2n32binu9.fsf@deanna.miranova.com \
    --to=steve@miranova.com \
    --cc=dcw@gcm.com \
    --cc=ding@ifi.uio.no \
    /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).