Assuming that this is the entire RFC 822 content of this email...
There is no routing information in the message that you sent. There is only the envelope information, which is useless for spam tracing.
If this is the only information that you have access to, it would certainly explain your problem with SpamCop, and Purify.
FYI, an RFC 822 header that DOES contain routing information looks something like this:
QUOTE
Return-Path: <snipped@macmaniacs.com>
Delivered-To: snipped@hendricom.com
Received: (qmail 16797 invoked from network); 21 Mar 2008 09:55:46 -0400
Received: from data.xzibition.com (64.18.131.146)
by 70-88-129-121-bsr01-howard01-md.hfc.comcastbusiness.net with (DHE-RSA-AES256-SHA encrypted) SMTP; 21 Mar 2008 09:55:46 -0400
Received: from c-71-224-171-163.hsd1.pa.comcast.net ([71.224.171.163] helo=[10.0.0.198])
by data.xzibition.com with esmtpa (Exim 4.68)
(envelope-from <snipped@macmaniacs.com>)
id 1JchsM-0002zc-Da
for snipped@HendriCOM.COM; Fri, 21 Mar 2008 10:05:45 -0400
User-Agent: Microsoft-Entourage/12.1.0.080305
Date: Fri, 21 Mar 2008 10:05:40 -0400
X-PURIFY-RATING: HAM
X-PURIFY-REASON: macmaniacs.com is a friend
Subject: Re: Taste the Difference: Saucy Inspirations
From: Mike McWhirter <snipped@macmaniacs.com>
To: Jeff Hendrickson <snipped@HendriCOM.COM>
Message-ID: <C40938F6.7E7C%macmikey@macmaniacs.com>
Thread-Topic: Taste the Difference: Saucy Inspirations
Thread-Index: AciLXKToe7zMLRAAbU+ESlyXUBvssQ==
In-Reply-To: <7490B1F1-F228-4756-A829-28D9DFD81089@HendriCOM.COM>
Mime-version: 1.0
Content-type: multipart/mixed;
boundary="B_3288938743_4531609"
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - data.xzibition.com
X-AntiAbuse: Original Domain - hendricom.com
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - macmaniacs.com
Please note the IP addresses in the Received: lines...