PS, this is Spamcop's explanation of what it needs, from their example page.
That's what's missing and needs to be included in the graymail item, to let the spam be reported to Spamcop.
EXAMPLE:
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
"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."
That's what's missing and needs to be included in the graymail item, to let the spam be reported to Spamcop.
EXAMPLE:
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
"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."