If you're the recipient of a message that's failing to deliver because of this error, see:
Unable to receive message, due to "Hop Count Exceeded" error
This article explains how to fix one of the most common causes of the following Microsoft 365 mail loop / bounce error:
554 5.4.14
Hop count exceeded - possible mail loopATTR34 [SY3AUS99FT999.eop-AUS01.prod.protection.outlook.com]
There are multiple circumstances in which this error can occur, each with its own solution. Regardless, this article is usually the best place to start.
If you're getting this "mail loop" error and your situation matches, it most likely indicates that your service was configured before December 2022, using incorrect Microsoft 365 setup instructions. Our old instructions for configuring Office 365 to "always accept clean mail" were based on widely accepted practices. As of this writing, there are still other prominent anti-spam service providers that are using the same faulty approach.
The underlying problem is that Microsoft 365 sometimes accepts an inbound message and then instead of delivering to the local recipient, treats it as an outbound message. As a result, the message is relayed back to SpamHero, where it is processed and re-delivered to Microsoft (causing a loop until the message bounces).
While it is optional, you may wish to start by following our updated instructions for configuring Microsoft 365 for fast, reliable deliveries.
208.53.48.64
,208.53.48.71
,208.53.48.191
,208.53.48.218
,108.60.195.222
,108.60.195.213
,108.60.195.218
Here's an example of what to look for:
To avoid major mail flow disruptions, do not delete the connector. Instead, disable it for at least a few days to confirm that you have identified the right connector. Just in case it gets permanently left behind, it might be smart to prefix the connector name with: DO NOT ENABLE