> LIVE PERSONAL PSYCHIC!    (as seen on T.V.)
> ...

Probably the easiest way to deal with most spam like this is to change
the list parameters so that only members of the list can send to the

This does create frustration for those of us who have different
addresses than we wish the list to be sent to, but it is usually
possible to allow each user to set a set of addresses they wish to
make available.

BTW, the From: address in SPAM is almost never the originator of the
SPAM.  Often it is the address of someone else who has complained
about spam.  Spammers often use this to seek vengeance.  Silvia Brown
probably had a real GTE account and then had to close it down because
of all of the hate mail received because people thought she sent the

Looking at the trail of the headers:

Received: from ACM.ORG by ACM.ORG (LISTSERV-TCP/IP release 1.8d) with spool id
          207195 for [log in to unmask]; Sun, 21 Mar 1999 23:25:22 -0500
Received: from mail.wa.freei.net (Mail1.Wa.FreeI.Net []) by
          mail.acm.org (8.8.5/8.7.5) with ESMTP id XAA23082; Sun, 21 Mar 1999
          23:15:20 -0500
Received: from (dial21.Block1.trm1.FreeI.Net [])
          by mail.wa.freei.net (8.9.1/8.9.1) with SMTP id UAA48786; Sun, 21 Mar
          1999 20:12:10 -0800 (PST) (envelope-from [log in to unmask])

The first place the message was received was by
dail21.block1.trm1.freei.net, a dialin port on a free internet
provider; a common source of spam.

The first mailer notited that that message was an envelope-from
Silvia_Brown1, meaning that the return address only occurred in the

GTE has nothing to do with the SPAM either.  Sending the lines above
to FreeI.Net should allow them to quickly identify the culprit.  A
good place to start would be [log in to unmask]  Be sure to include
the entire message (with all of these headers).  If you don't know how
show all headers in your mailer, you need to learn this before
complaining about spam.  Without the headers, the message is useless.

Dave Brown