52.138.55.160 - "Using rdns to route to correct Microsoft" but reports go to the spammer

[Snowbat]

52.132.0.0 - 52.143.255.255 is Microsoft but Spamcop reports 52.138.55.160 directly to the spammer. I've seen similar misreporting for other Microsoft-hosted spammers.

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

Tracking message source: 52.138.55.160:

Routing details for 52.138.55.160
[refresh/show] Cached whois for 52.138.55.160 : abuse@microsoft.com
Using best contacts abuse@microsoft.com
Using rdns to route to correct Microsoft department
host 52.138.55.160 = user15.pj-santanderesfera.com. (cached)
abuse net pj-santanderesfera.com = postmaster@pj-santanderesfera.com

[petzl]

On 6/5/2020 at 10:01 PM, Snowbat said:

abuse net pj-santanderesfera.com = postmasterXpj-santanderesferaXcom

Abuse net often get their addresses wrong putting postmaster@domain, that used to be the default address where no abuse address can be found.

Doubt if it goes any where, pays to look-up abuse addresses yourself to check.
I use this windows APP from
http://www.nirsoft.net/utils/ipnetinfo.html

Edited June 6, 2020 by petzl

[Snowbat]

52.132.0.0 - 52.143.255.255 is a Microsoft netblock. Why is SpamCop not reporting this to abuse@microsoft?

> Using rdns to route to correct Microsoft department

Whatever SpamCop is trying to do here is clearly broken and likely to deliver reports directly to spammers hosted on Microsoft.

[gnarlymarley]

1 hour ago, Snowbat said:

52.132.0.0 - 52.143.255.255 is a Microsoft netblock. Why is SpamCop not reporting this to abuse@microsoft?

That is a good question. I would almost expect abuse@microsoft.com to be on the list as well in addition to the administrator's abuse address. I think this might be microsoft's cloud and it is going to the server admin, which may or may not be the spammer.