Quote:
|
Originally Posted by A.Serbinski
to track down the owner of the originating ip address.
|
Which are, with 99,9999% certainty, spambots and change at least daily, if not hourly. And end result: You may get couple ISPs to close the infected user's account and have wasted several hours to achieve practically nothing.
[add]
Here's a sample, same spam message, received and caught each time:
Code:
Delivery-Date: Thu, 17 Apr 2008 03:15:06 +0200
Received: from dti-host7.pickdti.com (dti-host7.pickdti.com [216.171.155.7])
From: ivagra cilais <mathias-matt@maumee.org>
Delivery-Date: Mon, 21 Apr 2008 14:35:27 +0200
Received: from mail.advokatkjallgren.se (mail2.advokatkjallgren.se [212.3.13.43])
From: vigara ciails <ftrain@mindspring.com>
Delivery-Date: Mon, 21 Apr 2008 21:51:23 +0200
Received: from geegee.lnk.telstra.net (geegee.lnk.telstra.net [165.228.201.116])
From: viagar icalis <jrhalo@peoplepc.com>
Delivery-Date: Wed, 23 Apr 2008 07:58:10 +0200
Received: from n11648136021.netvigator.com (n11648136021.netvigator.com [116.48.136.21])
From: viagar icalis <jbprecious@att.net>
Delivery-Date: Thu, 24 Apr 2008 15:55:31 +0200
Received: from host81-137-17-245.in-addr.btopenworld.com (host81-137-17-245.in-addr.btopenworld.com [81.137.17.245])
From: ivagra cilais <jeromy@bsite.net>
In effect, unless you want to try to report these spambots 24/7 and do nothing else in life, go ahead, but you are figthing a lost battle even then.
[/add]