[SpamCop-Geeks] need procmail debugging help

[Socks the Whitehouse Cat]

I have a couple of spamtrap addresses on my server.  I want to auto 
forward mail sent to those addresses to my spamcop reporting address.  
Spamcop says that it couldn't find the spam.  A fix would be appreciated.

tia

= = = =

(munges manually inserted ex post facto as appropriate)

Here's what my procmail recipe looks like

# munged was NS registration acct - now spam trap only 
:0
* ^Received.*munged|\
  ^To.*munged|\
  ^Cc.*munged
{
    EXITCODE=77
    LOG = "spamtrap - "
    :0
    !munged at spam.spamcop.net
}

= = = =

procmail log file shows it was picked up and forwarded. I also got the 
bounce back in the sending mailbox from the exitcode=77

spamtrap - From munged  Sun Jul 20 14:56:08 2003
 Subject: test msg
  Folder: /usr/lib/sendmail -oi submit.munged at spam.spamcop.net	    836

= = = =

error message back from spamcop 

To: munged
Subject: SpamCop encountered errors


SpamCop encountered errors while saving spam for processing:
SpamCop could not find your spam message in this email:

Received: (qmail 1701 invoked from network); 20 Jul 2003 20:55:36 -0000
Received: from munged.com (munge)
  by shagrat.julianhaight.com with SMTP; 20 Jul 2003 20:55:36 -0000
Received: from munged.com (localhost [127.0.0.1])
	by munged.com (8.12.1/8.12.1/04202002-01) with ESMTP id 
h6KKu81r001241
	for <munged at spam.spamcop.net>; Sun, 20 Jul 2003 14:56:09 -0600 
(MDT)
Received: (from munged at localhost)
	by munged.com (8.12.1/8.12.1/Submit) id h6KKu8Ke001238
	for munged at spam.spamcop.net; Sun, 20 Jul 2003 14:56:08 -0600 (MDT)
Received: from munged (ppp36.den.munged.net [munged])
	by munged.com (8.12.1/8.12.1/04202002-01) with ESMTP id 
h6KKu21u001224
	for <munged>; Sun, 20 Jul 2003 14:56:06 -0600 (MDT)
X-Organization: Lumber Cartel
Message-Id: <5.2.1.0.0.20030720145748.00ae2a30 at mail.munged.com>
X-Sender: munged at mail.munged.com (Unverified)
X-Mailer: QUALCOMM Windows Eudora Version 5.2.1.0 (Beta)
Date: Sun, 20 Jul 2003 14:58:11 -0600
To: munged
From: munged
Subject: test msg
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed

should forward. make sure I dont get it


The email which triggered this auto-response had the following headers:
 Received: (qmail 1701 invoked from network); 20 Jul 2003 20:55:36 -0000
Received: from munged.com (munged)
  by shagrat.julianhaight.com with SMTP; 20 Jul 2003 20:55:36 -0000
Received: from ra.munged.com (localhost [127.0.0.1])
	by ra.munged.com (8.12.1/8.12.1/04202002-01) with ESMTP id 
h6KKu81r001241
	for <munged at spam.spamcop.net>; Sun, 20 Jul 2003 14:56:09 -0600 
(MDT)
Received: (from munged at localhost)
	by ra.munged.com (8.12.1/8.12.1/Submit) id h6KKu8Ke001238
	for munged; Sun, 20 Jul 2003 14:56:08 -0600 (MDT)
Received: from munged (ppp36.den.munged.net [207.174.254.36])
	by ra.munged.com (8.12.1/8.12.1/04202002-01) with ESMTP id 
h6KKu21u001224
	for <munged>; Sun, 20 Jul 2003 14:56:06 -0600 (MDT)
X-Organization: Lumber Cartel
Message-Id: <5.2.1.0.0.20030720145748.00ae2a30 at mail.munged.com>
X-Sender: munged (Unverified)
X-Mailer: QUALCOMM Windows Eudora Version 5.2.1.0 (Beta)
Date: Sun, 20 Jul 2003 14:58:11 -0600
To: munged
From: munged
Subject: test msg
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed





-- 
In either case, the Court cautions Plaintiff's counsel not to run with a
sharpened writing utensil in hand--he could put his eye out. (147 
F.Supp.2d 668)