SC parser chokes on spam headers

[SuperMacro]

Hi there,

SC says that the following headers (straight from Thunderbird) are somehow unparsable:

Return-Path: <return@news.neofromotherside.club>
Received: from news.neofromotherside.club ([185.80.129.8]) by mx-ha.gmx.net
 (mxgmx014 [212.227.15.9]) with ESMTP (Nemesis) id 1MVtTT-1gMGpZ1Uf7-00RiCX
 for <x>; Mon, 03 Sep 2018 04:52:24 +0200
from:VIP Ticket 1200 Eur/200 SPIN !! <contact@news.neofromotherside.club>
subject:Der GROSSE PREIS ist nur Stunden entfernt
date:Mon, 03 Sep 2018 04:52:01 +0200
to:x
reply-to:<reply@vsrvi-news.neofromotherside.club>
Content-Type:text/plain/html; charset="utf-8"
Message-ID:<0.0.6A.3F6.1D43ADE13AB8FCC.7104@vmta-m-152.lstrk.net>
MIME-Version:1.0
Content-Type:multipart/alternative; boundary="----=_NextPart_000_1829_01D40337.86CACFB0"
Content-Type:text/plain; charset="us-ascii"
Content-Transfer-Encoding:7bit
X-Mailer-Reference:RPK44R14D890RE630V31QE1PG9B1RNR93KAK4RGDQ81
Errors-To:RPK44R14D890RE630V31QE1PG9B1RNR93KAK4RGDQ81@b.lt02.net
List-Unsubscribe:<mailto:6QT55645JSCQ6AT8QN8OVA4QGC1O936C8TET56GJVS4G@b.lt02.net>
Envelope-To: <x>

Other mails work fine, though. My personal mail address was removed, obviously.

Thanks.

 [edit] The report URL is https://www.spamcop.net/mcgi?action=gettrack&reportid=6848016328

[Lking]

Unfortunately you provided a "reportid" not a Tracking URL.  Only you can see the report.  On the submit past the tracking URL is near the top, or it is the link in the auto-respond email you received from SpamCop

Quote

SpamCop v 4.9.0 © 2018 Cisco Systems, Inc. All rights reserved.
Here is your TRACKING URL - it may be saved for future reference:
https://www.spamcop.net/sc?id=z6483188285ze9bc35b37251663da7aedd4e24275c5cz

 

Quote

SpamCop is now ready to process your spam.

Use links to finish spam reporting (members use cookie-login please!):
http://www.spamcop.net/sc?id=z6483188285ze9bc35b37251663da7aedd4e24275c5cz

Welcome to the forum.

[SuperMacro]

Uh, didn't know that. Here's the correct link

https://www.spamcop.net/sc?id=z6483371849zb1840febd22e4df5a0f6357e46bb1a48z

[SuperMacro]

Next UCE arrived today with unparsable headers

https://www.spamcop.net/sc?id=z6483930589z531db03c3000f0ee59c5fc2c685e9011z

[Lking]

Quote

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

Reports regarding this spam have already been sent:

Re: 54.38.135.123 (Administrator of network where email originates)
   Reportid: 6848948977 To: abuse@ovh.net
   Reportid: 6848948978 To: noc@ovh.net

If reported today, reports would be sent to:

Re: 54.38.135.123 (Administrator of network where email originates)

abuse@ovh.net
noc@ovh.net

Is you point that the message "error: couldn't parse head"  is incorrect?  Looking at the first part of the report, the header is processed. The error message follows the header "Finding links in message body"  Looking at the results spam reports are sent to admin where the message originated.

Processing the body of spam/sending spam reports to spamvertised links in the spam is a secondary priority for SpamCop. The error message is confusing and should be changed along with the link to "More information."  But I would not hold my breath.  Dealing with parsing of the header and related security issues have much higher priority.

[petzl]

7 hours ago, SuperMacro said:

Next UCE arrived today with unparsable headers

https://www.spamcop.net/sc?id=z6483930589z531db03c3000f0ee59c5fc2c685e9011z

Your email provider is putting adding to headers some "anti-spam" code to headers (which don't seem to work), however SpamCop is sending abuse report to a abuse desk where email/spam originates