Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

SpamCop FAQ : SpamCop Parsing and Reporting Service : Parsing and reporting spam with SpamCop – decisions, problems : What do you mean by “full headers”?

April 26, 2017decisions full headers mean parsing problems service spam SpamCop

0

Posted

SpamCop FAQ : SpamCop Parsing and Reporting Service : Parsing and reporting spam with SpamCop – decisions, problems : What do you mean by “full headers”?

1 Answer

0

Posted

Here’s an example of the headers of an email: Return-Path: 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 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. Witho