Kevin’s a senior guy in the transport section of the Exchange development team. I’d trust what he says.

I found this comment from MS here, see comment dated Feb 1 2024 10:53PM from Kevin.

https://techcommunity.microsoft.com/t5/exchange-team-blog/how-to-pause-throttling-and-blocking-of-out-of-date-on-premises/ba-p/4007169#comment-on-this

I ran it for MS on Apr 18, and again today (Apr 22) with no obvious change. I found a redditor had the same issue a few months ago but a solution was not posted. I guess I’ll have to wait for MS or uninstall E2013 (whichever comes first), I appreciate the quick feedback.

My impression is that the cmdlet updates the information shown in the report. This might take a little time as it’s likely that the data is cached.

MS requested I run the get-onpremserverreportinfo cmdlet to show the output (it only showed the E2013 server), but they didn’t give me any directions on how to ” update the information” their report depends upon.

If the Exchange 2013 server has been shut down since April 6, I think you’ve had enough time to discover if any problems are lurking in the environment and should be safe to remove it. Did you run the get-onpremserverreportinfo cmdlet to update the information that the Exchange server report depends on?

I don’t understand how the message headers could reference an offline E2013 server. Do you think if we uninstall E2013 from the environment that’ll cure our need to continue pausing the throttling?

My experience with MS products tells me that they will eventually apply the same rules to all incoming mail. After all its the same situation you are running an out of date and unsupported/insecure mail system.

Why not simply run the Get-ExchangeServer cmdlet to check the servers in your on-premises environment and the software versions they run? You know that Microsoft will block old servers that host the connectors to send email to Exchange Online, so simply make sure that these servers run an up-to-date and supported version and you’re fine.