icloud.com email now reports "Mailhost configuration problem, identified internal IP as source"

[styncer]

I've been reporting spam using spamcop.net for years.  A few weeks ago, all of the spam that I receive through my @icloud.com address is no longer able to be processed by spamcop.  I receive the error, "Mailhost configuration problem, identified internal IP as source" and cannot proceed.  I typically post the email source into the online form.  I've tried using the email submission as well ... no change.

Here are the top headers of the email I just received (with my account removed)

Return-path: <bounce@sansat.online>
Original-recipient: rfc822;*******@icloud.com
Received: from st42p59im-ztdg12250601 by st42p59ic-ztdg12240101 (mailgateway 1922B206)
	with SMTP id 183f8e09-ae71-4b00-baa3-458a228427ab 
	for <*******@icloud.com>; Wed, 4 Dec 2019 22:57:59 GMT
Received: from 17.36.65.61 by 17.36.65.25 (mailnotify 1916B19:12:18:22:57:59:60); Wed, 4 Dec 2019 22:57:59 GMT
X-Apple-MoveToFolder: Junk (36) uid 12 user ******* modseq 0
X-Apple-Action: JUNK/Junk
X-Apple-UUID: 183f8e09-ae71-4b00-baa3-458a228427ab
Received: from ip21.ip-178-32-48.eu (ip21.ip-178-32-48.eu [178.32.48.21])
	by pv33p00im-smtpin029.me.com (Postfix) with ESMTPS id 4845BAA00C2
	for <*******@icloud.com>; Wed,  4 Dec 2019 22:57:56 +0000 (UTC)

Would someone please offer a suggestion for how I can get this to work again?

[Lking]

It is possible that your email host (icloud.com) had changed their configuration, witch will affect your mailhost configuration on record with spamcop.  Ask your ISP. If ISP servers have been reconfigured then you need to update your mailhost configuration. by logging into your spamcop account, clicking on the <Mailhosts> tab and follow the instructions.

How you submit your spam, email attachment or web form, the parsing of the header will be the same an uses the same mailhost configuration.

[gnarlymarley]

Without the tracking URL, I would guess this is the line that it is stopping at right above the "identified internal IP as source" message:

14 hours ago, styncer said:

Received: from 17.36.65.61 by 17.36.65.25 (mailnotify 1916B19:12:18:22:57:59:60); Wed, 4 Dec 2019 22:57:59 GMT

It would appear that you need to update your mailhost configuration but resending a message to your account.  Then you should be able to return to the spam report page and it should work.

[styncer]

I apologize for the delay in my response.  I've tried to follow the Add Mailhost for my address (*****@mac.com) again.  I receive the test email, and when I paste the headers and body into the form, it returns the following error:

Quote

Host 17.36.65.23 (checking ip) IP not found ; 17.36.65.23 discarded as fake.

Sorry, SpamCop has encountered errors:

The email sample you submitted for *****@mac.com
appears to traverse more than one domain.  
Please ensure that you configure each mailhost individually and in order.

Proceed here:

<link removed>

When I try to follow the "Proceed Here" URL, I receive an error, "500 Internal Server Error".

[RobiBue]

1 hour ago, styncer said:

I apologize for the delay in my response.  I've tried to follow the Add Mailhost for my address (*****@mac.com) again.  I receive the test email, and when I paste the headers and body into the form, it returns the following error:

When I try to follow the "Proceed Here" URL, I receive an error, "500 Internal Server Error".

As gnarlymarley mentioned previously, a tracking URL would be helpful to figure out what’s going on.

the tracking URL can be found at the top of the spam processing screen after clicking the button [process spam] below the entry text box.

Quote

SpamCop v 5.1.0 © 2020 Cisco Systems, Inc. All rights reserved.
Here is your TRACKING URL - it may be saved for future reference:
https://www.spamcop.net/sc?id=z6606108219z9c172865e7cf0232ed44faff1e248b8bz
Skip to Reports

Delivered-To: x

[gnarlymarley]

On 1/5/2020 at 9:10 AM, styncer said:

The email sample you submitted for *****@mac.com
appears to traverse more than one domain.  
Please ensure that you configure each mailhost individually and in order.

Apparently @mac.com emails could be forwarded to another account.  If you can read the headers, then a part such as "for user@example.com;".  You might want to remove some of the "Received:" lines to split up the email if it is being forwarded.