Jump to content

Error in the report page


rob
 Share

Recommended Posts

I paste here the error I read when I click on a spam reporting link:

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

In more info I read this:

I cannot emphasize enough that this is not a trick by spammers to "fool spamcop". It is an error introduced by the recipient (you) when copying or submitting email to spamcop. If you encounter this problem, please review how you submit spam to SpamCop and take corrective action. Please don't just "fix up" the headers, but actually find a way to submit them unaltered in the first place. Fixing headers by hand only introduces even more fatal errors, not to mention being a big pain.

I always did what I always have done. Forward mail with full header to the address I got when subscribed.

Here it is the tracking url

http://www.spamcop.net/sc?id=z3974760216z3...92309a90cefd0ez

EDIT there is also a From: not obfuscated.......

Edited by rob
Link to comment
Share on other sites

I always did what I always have done. Forward mail with full header to the address I got when subscribed.

Here it is the tracking url

http://www.spamcop.net/sc?id=z3974760216z3...92309a90cefd0ez

Just tell us what email program you use

http://www.spamcop.net/fom-serve/cache/19.html

Your link does parse and is unreported?

Link to comment
Share on other sites

...Yes I stil not have reported that spam.
You should report or cancel now. I can see no problem with reporting it. From: is not usually obfuscated. Sometimes you might see To: unobfuscated - it is only you who can see that in most such cases.

The problem with the parse as posted is there are a heap of badly wrapped lines, that gives the error "Couldn't parse head". It gives that error after it has parsed the head. What it really means is it is not sure where the body is.

Here is that spam, re-parsed with the continuation lines fixed (and no mail hosting):

http://www.spamcop.net/sc?id=z3974967601z7...4f9a45dd7b2c25z

You will see this doesn't attempt to to resolve the 'spamvertized' URL either (I don't know why) - so reporting what you have already parsed is no loss.

FWIW http://bit.ly/d2WHfx is hosted on 128.121.254.201 and ARIN whois says report address is abuse[at]ntt.net

Maybe something has changed your line wrapping on TB? On this occasion it has not affected the reporting.

Link to comment
Share on other sites

You should report or cancel now. I can see no problem with reporting it.

Reported.

I just felt a bit accused when I read

"It is an error introduced by the recipient (you) when copying or submitting email to spamcop"

I did what I always did, not different.

Link to comment
Share on other sites

Reported.

I just felt a bit accused when I read

"It is an error introduced by the recipient (you) when copying or submitting email to spamcop"

I did what I always did, not different.

Well, looking at it, I think most or all of the 'problem' is caused by fake, malformed lines inserted by the spammer - so nothing changed 'your end' at all.
Link to comment
Share on other sites

The three top-most received lines appear to have a hard return after the word 'by' while the origination Received line does not. The hard returns (which can be an Esc/control character) look to be added by your machine(s). More than one hard return between headers confuses the parser.

I paste here the error I read when I click on a spam reporting link:

Finding links in message body

Parsing text part

error: couldn't parse head

Message body parser requires full, accurate copy of message

Again, that looks like a hard return inserted after "(UTC)" for what should be the uninterrupted header "X-OriginalArrivalTime." If that's the case, sc doesn't recognize "FILETIME=[26664A30:01CAEA33]" as a header field and therefore cannot determine where the body actually begins.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...