Tracing spamLet me start first by telling you how not to react to spam.
Here is a brief guide on how to find out where an e-mail message comes from. This applies to all e-mail, not just spam. The following case is a little devious (most instances of spam are easier to track), but you can learn a lot from this example. Below you can see the beginning of the message, as displayed by your mail program: Date: Wed, 22 Oct 97 13:55:24 EST Dear online friend, It does not say much about its origin, but we can be sure of one thing already: the address 81884948@aol.com is forged (do not try to send mail to this address). How can we tell? Because: Valid AOL addresses can not: To learn more, tell your mail reader to show all headers. In Eudora, this is done by clicking the "Blah Blah Blah" button: Received:
(from smap@localhost) by strix.its.uu.se (8.6.10/8.6.10) id GAA42920 for <pales@strix.its.uu.se.NOSPAM>; Thu, 23 Oct 1997 06:54:14 +0200 Date: Wed, 22 Oct 97 13:55:24 EST
Dear online friend, Now you have a little more information. Remember that you must send a complete copy of a spam message (including all headers) when you report spamming to the administrators of the domain of origin. The last "Received:" header is usually the one that matters. Normally, it contains the source of the message and the first host mail server which received it. However, in this case the last "Received:" header contains more than two host names, and this means the header has been forged. A valid "Received:" header has the following format: Received: from host1 (host2 [ww.xx.yy.zz]) by host3 (8.7.5/8.7.3) with SMTP id MAA04298; Thu, 18 Jul 1996 12:18:06 -0600. Reading from back to front in the forged header, we see the host which added the "Received:" header (host3); the IP address of the incoming SMTP connection (ww.xx.yy.zz); the reverse-DNS lookup of that IP address (host2); and the name the sender used in the SMTP HELO command when it connected (host1). In such a case, our best bet is the next-to-last "Received:" header. This indicates an IP address of origin within the net-block 208.136.0.0, which belongs to mci.net. We can learn this by doing: whois 208.136.10 MCI Internet Services (NETBLK-MCI-NETBLK10) With this information, we can forward our report to MCI. Remember to keep things simple, and do not address the administrator in less-than-polite terms. He is there to help you, and has nothing to do with the spammer. My favourite introduction is:
Dear Sirs, From the list of reporting addresses in http:\\www.abuse.com, we obtain the address spams@mci.net, and we send our report to this address. In most cases, you will receive an automated reply saying that your complaint has been received. Sometimes, you will receive a follow-up with specific information about your report. You should neither ask nor expect to receive any personal information on the spammer - remember that your identity is being kept confidential as well. Instead, a follow-up may contain valuable technical information (this is how I collected the information presented in this page). Even if you do not receive any reply, in most cases your report has been read, and the administrator has tried to find the source of the spam and acted against it. Just keep reporting all instances of spam, and you can be sure that several spammers will lose access to their mail servers. Here are, for instance, two messages I received yesterday:
Hello, Thank you very much for taking the time to inform us of this situation.
|
page hits during the last year |
Copyright (c) Enrico Savazzi, 1990 -
. This page was created
in 2002
, last updated
November 17, 2011
(last update refers to any change of contents, styling and/or web host)
This site is ad-free. If you see any ads here, they are added by your ISP, or by spyware on your computer, or you are visiting this site through frames of another site.