Help | Site Map
| Text size: - +
(Answer) (Category) SpamCop FAQ : (Category) SpamCop Parsing and Reporting Service : (Category) Parsing and reporting spam with SpamCop - decisions, problems :
What do you mean by "full headers"?
Here's an example of the headers of an email:

Return-Path: <nospam@julianhaight.com>
Received: from julianhaight.com (usr25-dialup4.mix1.Sacramento.mci.net [166.55.9.4])
     by sam.julianhaight.com (8.8.7/8.8.7) with ESMTP id MAA14120;
     Sat, 7 Mar 1998 12:08:52 -0800
Message-ID: <3501A7D6.9C842904@julianhaight.com>
Date: Sat, 07 Mar 1998 12:02:30 -0800
From: Julian Haight <nospam@julianhaight.com>
X-Mailer: Mozilla 4.04 [en] (WinNT; I)
MIME-Version: 1.0
To: feedback@pfmicro.com
Subject: TWINSTOR TS210 Disk Mirroring Controller
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Notice the line marked in red. This is the most important part of the header that SpamCop cares about. This is called a received line. Some email messages have only one received line, some have more than one. Every time the email makes a "hop" from one server on the internet to another, one more received line is added. They can be used to track the email back along its path to the origin. Without this information, SpamCop can do nothing. All the other information in the header is suspect (it can be faked). The received line portion of the header always contains SOME kernel of truth. SpamCop separates the kernel from the chaff in order to find the true source of the spam.
[Append to This Answer]