EkriirkE

No. Read the posts.

This is a failed parse https://www.spamcop.net/sc?id=z6693341449z0778223c9998b219a4bda561ffbc4addz this version parsed https://www.spamcop.net/sc?id=z6693545149z7a985f0f94faa3a5d9a2fa784fd2555bz The only difference is I removed the Return-Path header

I forward as attachments, been doing so for over a decade. This is a bug which only affects about 1 spam a year. I doubt my methods of simply clicking the forward button are randomly "mis pasting" an email of thousands consistently

What are you going on about? You can't get a tracking link for a spam you haven't submitted yet. That's a catch 22. And I'm not trying to report spamcop report links

Occasionally I will get an email where the body is not parsed/ignored and I got another today that I did some poking around, and I found that if the Return-Path header exists and is empty (`Return-Path: <>`), the body is ignored. Removing or populating it resolve the issue.

Obviously, but I'd rather minimize confirmation of receipt

I've run into this as well, so I have a ScriptMonkey scri_pt that gives me an alert to scrutinise carefully if my email or hosting providers are one of the recipients

Spammers are tracking back who reports them by including the emails that get back to them via spamcop reports in the subject and body, example: encoded and segmented subject: https://www.spamcop.net/sc?id=z6641797254z619187ae372c6cec5509fadaf926d2baz segmented body: https://www.spamcop.net/sc?id=z6641801254z40077f70be652e542cfe9e7deb51e5faz My email is still visible. Note the first example is targeted at me directly for reporting them subject "You make compliant on Spamcorp my.visible.email erville?..." with a confusing body that pieces together a personalized message:

This report seems to crash the engine https://www.spamcop.net/sc?id=z6415313104z2c92b57960e7b2c931232479df8fc2efz