1997-03-28 - Re: spam

Header Data

From: Paul Foley <mycroft@actrix.gen.nz>
To: dlv@bwalk.dm.com
Message Hash: 9d673168f5ebe88a2a092d2dd79980385c276b92440779950edf76576f524a3f
Message ID: <199703281745.FAA08525@mycroft.actrix.gen.nz>
Reply To: <V5H74D19w165w@bwalk.dm.com>
UTC Datetime: 1997-03-28 17:46:27 UTC
Raw Date: Fri, 28 Mar 1997 09:46:27 -0800 (PST)

Raw message

From: Paul Foley <mycroft@actrix.gen.nz>
Date: Fri, 28 Mar 1997 09:46:27 -0800 (PST)
To: dlv@bwalk.dm.com
Subject: Re: spam
In-Reply-To: <V5H74D19w165w@bwalk.dm.com>
Message-ID: <199703281745.FAA08525@mycroft.actrix.gen.nz>
MIME-Version: 1.0
Content-Type: text/plain


On Wed, 26 Mar 97 09:58:54 EST, Dimitri Vulis KOTM wrote:

    > A while back we discussed on the cp mailing list a spec for a system that
    > provide junk e-mailers for free with a list of (hashed) addresses that
    > should be removed from any mass e-mail lists. Is anyone interested in
    > talking about the technical aspects of such a system?

Is there really anything to talk about?

I just implemented such a thing using SHA1 hashes.  Source code, a
database consisting of my address, and a Linux binary are available
(volunteers to compile other binaries, provide an FTP server, or add
their address(es) are welcome!)

It can add and delete addresses, check whether addresses are blocked,
and filter a list of addresses from stdin.  The database is stored as
a text file with the hexadecimal representation of the hashes written
one per line [actually, the first 0<=n<=5 digits of the hash are
appended to the file name, using multiple files to improve search
speed.]

-- 
Paul Foley <mycroft@actrix.gen.nz>       ---         PGPmail preferred

	   PGP key ID 0x1CA3386D available from keyservers
    fingerprint = 4A 76 83 D8 99 BC ED 33  C5 02 81 C9 BF 7A 91 E8
----------------------------------------------------------------------
A father doesn't destroy his children.
		-- Lt. Carolyn Palamas, "Who Mourns for Adonais?",
		   stardate 3468.1.





Thread