k9axux00vgy6vfk001 Posted October 19, 2007 Share Posted October 19, 2007 I'm consistently getting the "couldn't parse head" error when I submit any and all spams through an email submit to my submit.XX...XX[at]spam.spamcop.net. What I see when I visit the processed spam message is: error: couldn't parse head Message body parser requires full, accurate copy of message More information on this error.. I've read the documentation and FAQ for this issue. In order to see the full email address with headers, under xemacs/gnus I use the "C-u g" sequence. And then I pipe the entire message, with headers, to a shell scri_pt that basically prepends a new set of headers (From, Return-Path, Reply-To, Sender, To, Bcc, Subject) so that I send out and forward the email to spamcop. The pipe is through the "|" key sequence. After these headers (to make the email go to spamcop), a newline is included, along with the original spam message with its headers. One of the submits that I made may be found at: http://www.spamcop.net/sc?id=z1482092140za...efe1de50d166b4z I've been submitting up to a dozen spam reports per day, sometimes with a turnaround time of several minutes from the receipt time of the spam message. It's vital that the reports are being forwarded on to all concerned parties, including the administrators of the domain names that appear in the body of the spam message. At the moment, that isn't happening. The scri_pt is quite simple, and I quote it below. When I see the copy of the report that I file, everything looks just fine, and includes the headers, so I'm at a loss to understand what might be going wrong. Can someone please advise how I might track and resolve this difficulty? #!/bin/sh ( cat <<EOF From: myemailaddress Return-Path: myemailaddress Reply-To: myemailaddress Sender: myemailaddress To: submit.XX...XX[at]spam.spamcop.net Bcc: myemailaddress Subject: Unsolicited email EOF sed 's,^From ,\\From ,' ) | sendmail -v -t Link to comment Share on other sites More sharing options...
This topic is now archived and is closed to further replies.