This is a reply to your message from Newsgroup: list.yarn,
Concerning "Re: Automatic spam reporting"; Of Sun, 07 Jul 1996 08:43:24 -0400
~ > In article <70b_9607061426@sunshine.com>,
~ > Rich.Veraa@907.sunshine.com (Rich Veraa) wrote:
~ >
~ > >SPAM reads the header of each message in the configured
~ > >directory, determines where it came from, and creates a message
~ > >to "postmaster" at that address forwarding a copy of the
~ > >original message.
~ >
~ > Most of the spam I see has forged headers. Your program is going
~ > to generate a _lot_ of undeliverable mail in INBOX.
A thought for Mr. Veraa. All the USENET messages (SPAM and
others) include PATH info. A recent example I got "I'LL TELL YOUR
FUTURE, NOW!!!" included the following:
> From: M. WILKINS <mwilkins@earthlink.net>
>
> Path: clicnet!news.clic.net!rcogate.rco.qc.ca!n2ott.istar!ott.istar!
> istar.net!news.nstn.ca!newsflash.concordia.ca!newsfeed.pitt.edu!
> scramble.lm.com!news.math.psu.edu!news.cse.psu.edu!uwm.edu!
> vixen.cso.uiuc.edu!newsfeed.internetmci.com!in1.uu.net!
> nntp.earthlink.net!usenet
Perhaps your little program could be configured to allow a user to
automatically post messages as far up the path (from the root) as
necessary until s/he finally stopped getting a bounce. At that
point, you presumably have the postmaster you actually want (or at
least one who is very close to the action).
postmaster@nntp.earthlink.net root
postmaster@in1.uu.net 1 up
postmaster@newsfeed.internetmci.com 2 up
postmaster@vixen.cso.uiuc.edu 3 up etc
Thanks for your fine Broccolinarian work.
-- Friar Broccoli Robert Keith Elias (Quebec, Quebec, Canada) Address: kelias@clic.net OFFLINE Usenet & Email READER: www.vex.net/yarn/archive/YARN_091.zip--------- I consider ALL arguments in support of my views. ----------