Eric Siegerman wrote:
On Thu, Aug 07, 2003 at 09:20:09AM -0600, Michael Kopach wrote:

I'm not sure this will help or not. Anyway, here is the header  I get
from that annoying message.


FWIW, they've come from at least three different ISP's (the
leading numbers are message counts):
    1   Received: from localhost (pcp02515402pcs.arlngt01.va.comcast.net 
[68.84.139.19])
    5   Received: from localhost (pool-138-89-183-57.mad.east.verizon.net 
[138.89.183.57])
    2   Received: from localhost (rrcs-nys-24-97-179-130.biz.rr.com [24.97.179.130])


FWIW, I send all spam I get (most are filtered by Spam Assassin into a folder I have named "Crap") to the FTC ([EMAIL PROTECTED]) - including all 3 of those I received under this subject. On occasion when I find a repeat offender - spam about the same subject by either the same person or different people (i.e. - spam sent from a compromised system or with forged headers) with the same message - I seek and destroy the offending spammer by:


1. Tracking down the ISP/web host of the web site refered to in the spam message.
2. Reporting the domain registrant for ISP EULA violations. Most of these people use 
incorrect contact information which is agains most every ISP/domain registrant/web 
host EULA.
3. Reporting the person(s) sending the spam for fraud (the FTC takes fraud cases 
*VERY* seriously).
4. Any other legal recourse I can find.

It usually only takes a matter of minutes to track the originator down. To date I have verified that I have personally been responsible for a dozen web sites being shut down, accounts disabled, and the domain names locked.

Now if more people took such steps, how much spam do you think there'd be?

PGA
--
Paul G. Allen
Owner, Sr. Engineer, Security Specialist
Random Logic/Dream Park
www.randomlogic.com




Reply via email to