The following has been going on for a couple months, but I've just now become annoyed and curious enough to track down what is going on. I usually paste my spam into SpamCop's reporting form to report spam, but for several months now I've been getting the following in the report when doing so:
>Finding links in message body >Parsing text part >error: couldn't parse head >Message body parser requires full, accurate copy of message >More information on this error.. >no links found I then receive one possible spammer listed, usually, and I know there should be more. The "More information on the error" is a link leading to <http://www.spamcop.net/fom-serve/cache/368.html>. It lists a problem with Outlook and Eudora, but I've tried that special form to no avail. It also says: >One common pitfall that still seems to be prevalent is erroneous wrapping >of long email header lines being submitted to SpamCop. If this type of >problem is present in submitted spam, SpamCop will refuse to scan the >message body for links, instead producing an error. Now, I've checked my headers according to their samples and I honestly see no erroneous wrapping. Indents seem to be where they are supposed to be. The page also says the best way to report is to forward as an attachment, but PowerMail doesn't have that function, and forwarding otherwise has always worked before. I have tried using the SpamCop reporting script posted here long ago, but the reports show the same unable to parse error. Can someone provide some ideas on what is going on and what I might be able to do to get this stuff reportable? I'd get rid of SpamCop, but it really cuts down on the massive amounts I receive -- I don't want to download this crap first to sort it by local scripts. But, if I don't do my part in reporting, then SpamCop is less useful since its main flags arebase don how many people report a particular piece of spam...
