parse page failing to load?

[anyone8]

I've been using SpamCop for years, but either something has gone wrong or the last spam I received is stalling it somehow. My first thought was reload, but it stopped at the exact same point. So I went back to the reporting box and tried pasting in the spam again, thinking maybe it would go through this time. Neither of my ideas made any difference. It's been so long since I've ran into any issue like this, I'm not sure how to troubleshoot beyond this, so anything I haven't already tried would be appreciated.

It always stops at the same point:

Quote

Parsing header:
host 2a01:111:e400:fc11:0:0:0:42 (getting name) no name
host 2603:10b6:300:c2:0:0:0:27 (getting name) no name

Here's one of the tracking URLs: https://www.spamcop.net/sc?id=z6702233527zbcd30846d6b3149bd78570af38518361z

Thanks!

[gnarlymarley]

1 hour ago, anyone8 said:

Here's one of the tracking URLs: https://www.spamcop.net/sc?id=z6702233527zbcd30846d6b3149bd78570af38518361z

Last time I had seen this it was a double period in a hostname, but I have yet to find one in this tracking URL.

 

[gnarlymarley]

I think I found it.

Received: from beactive.it (5.149.249.179) by xHRZDMoSZQtTgIAffdczjrWWwatOgPNzFmircaawrvITFdBVQxutRnEWUepKPlOSwGJOqJfGFYyixSZjQnQWiQxqdPmvWeFgxrYmbRuJHWQgniKgFaMzPNMarqJOpuDIqmBFzSYld.mail.protection.outlook.com id pDAvY7enim86 for <x>; Tue, 09 Feb 2021 01:00:58 +0100 (envelope-from <return@nvse2fv2dfx.work>

The hostname appears to be too long on the above line.

C:\>dig any xHRZDMoSZQtTgIAffdczjrWWwatOgPNzFmircaawrvITFdBVQxutRnEWUepKPlOSwGJOqJfGFYyixSZjQnQWiQxqdPmvWeFgxrYmbRuJHWQgniKgFaMzPNMarqJOpuDIqmBFzSYld.mail.protection.outlook.com
dig: 'xHRZDMoSZQtTgIAffdczjrWWwatOgPNzFmircaawrvITFdBVQxutRnEWUepKPlOSwGJOqJfGFYyixSZjQnQWiQxqdPmvWeFgxrYmbRuJHWQgniKgFaMzPNMarqJOpuDIqmBFzSYld.mail.protection.outlook.com' is not a legal name (label too long)

C:\>

 

[anyone8]

Thanks for pointing me in the right direction. I wasn't sure whether to look at the message, or maybe there was an issue with my computer or SpamCop's parser.

Although there are no double periods in the whole email, that got me to looking at the message. I tired removing things that looked strange. The one that seemed to be the problem was a hostname that began with "xHRZDMoSZQtTgIAffdczjrWWwatOgPNzFmircaawrvITFdBVQxutRnEWUepKPlOSwGJOqJfGFYyixSZjQnQWiQxqdPmvWeFgxrYmbRuJHWQgniKgFaMzPNMarqJOpuDIqmBFzSYld" as it started working when I changed that portion to "removed."

If I recall correctly (it's been years), we shouldn't report things with material changes, so I cancelled. But at least we know what was tripping up the parser.

[anyone8]

5 minutes ago, gnarlymarley said:

I think I found it.

....

The hostname appears to be too long on the above line.

 

Well, if we both reached the same conclusion at the same time, we can't both be wrong, right?  Thanks!

[gnarlymarley]

On 2/8/2021 at 7:34 PM, anyone8 said:

Well, if we both reached the same conclusion at the same time, we can't both be wrong, right?  Thanks!

✔️