Gnus development mailing list
 help / color / mirror / Atom feed
From: Chris Shenton <cshenton@Outbounder.com>
Subject: Stopping spam by attracting it?
Date: 10 Jul 2001 11:05:15 -0400	[thread overview]
Message-ID: <lfy9pwygd0.fsf_-_@Samizdat.outbounder.com> (raw)
In-Reply-To: Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "Tue, 10 Jul 2001 13:05:16 +0200"

Perhaps this is painfully obvious and folks are doing it already; if
so, does it work? If not, here's what I'm thinking. 

Insert a bogus, spam-attracting email address into all the email I
send, like victim@mydomain.com; this address should never send mail,
so any mail it receives will be from address-harvesting spammers.
Alias that address to a small program which examines the headers and
extracts source IPs, From: lines, Subject: lines, etc and installs
these into some filter config. When your MTA receives mail, it
consults the filter looking for match and rejects any messages
matching the filter; alternatively, have the MUA do this and put it in
a folder/group for suspicious mail.

The trick would be building the program to find "significant" headers,
avoiding generation of overly loose matches which would filter too
much legitimate mail.

Anyone doing anything like this? Any thoughts how I might do something
like this with Gnus? 

Not quite Gnus-related, but if one collected lots of spammer/relay
host addresses, they could automatically be added to an RBL-like DNS
server, operating for an individual, an enterprise, or the public at
large. Would also be nifty if such fingerprints could be shared to
automatically build a list of suspicious senders.



                 reply	other threads:[~2001-07-10 15:05 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=lfy9pwygd0.fsf_-_@Samizdat.outbounder.com \
    --to=cshenton@outbounder.com \
    /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).