Knowledgebase
554 5.4.6 Hop Count Exceeded: Possible Mail Loop
Posted by Carlos Rios on 15 November 2017 02:40 PM

This issue may occur if one of the following conditions is true:

  • The domain is not added as an accepted domain (that is, the domain is not verified) in Office 365
  • Domain propagation to the Microsoft Forefront Online Protection for Exchange (FOPE) Edge Transport servers requires up to 45 minutes after an Office 365-accepted domain is added, moved, or deleted in FOPE; or the domain is propagated, but it is configured as outbound-only
  • In FOPE, the Exchange on-premises organization is not defined as being enabled to relay email messages
  • Mail delivery settings in the FOPE Administration Center are not set correctly for the expected email flow

  To resolve this issue, use one of the methods in the following table, as appropriate for your situation:

Cause Resolution
The domain is not added as an accepted domain (that is, the domain is not verified) in Office 365. Make sure that the domain has a status of "Verified" in the Office 365 domains section.

For more information about how to troubleshoot adding and verifying domains in Office 365, click the following article number to view the article in the Microsoft Knowledge Base:2515404
Domain propagation to the FOPE Edge Transport servers requires up to 45 minutes after an Office 365 accepted domain is added, moved, or deleted in FOPE; or the domain is propagated but is configured as outbound-only.

Populate your domain in FOPE. To do this, use the following Windows PowerShell commands to force FOPE to recognize your Office 365 domain. This creates the necessary records:

Set-AcceptedDomain <domain> -OutboundOnly $true Set-AcceptedDomain <domain> -OutboundOnly $false

Notethat the placeholder <domain> represents the vanity domain that you want to use.

It will take 30 to 45 minutes for propagation to all Edge servers. During this time, you may receive an NDR message that states that the hop count is exceeded.

Hybrid coexistence scenarios only: In FOPE, the on-premises Exchange organization is not defined as being enabled to relay email messages. In the FOPE Administration Center, add the IP address of the on-premises server or servers to the IP addresses list on the outgoing (also known as "outbound") mail server. To do this, follow these steps:
  1. In the FOPE Administration Center, clickAdministration >Domains >and then click the domain that is experiencing the issue
  2. UnderOutbound Mail Server IP Addresses, clickAddand then enter the IP address of the on-premises server or servers
  3. ClickSave
It will take 30 to 45 minutes for propagation to all Edge servers. During this time, you may receive an NDR message that states that the hop count was exceeded.
Mail delivery settings in the FOPE Administration Center are not set correctly for the expected email flow. If FOPE delivers mail directly to Exchange Online for the domain, make sure that the FOPE admin mail delivery settings or the mail server address are set to useinbound multi-SMTP profileinboundsmtpprofile. If FOPE delivers mail to the on-premises Exchange organization, verify that the on-premises IP address is set as the address for delivery.

 


ERROR: This domain name does not match domain registered in the license key file (cms.orlinpilot.com), allowed domains: support.excelmicro.com,localhost, please change the product path to match the domain under Admin CP > Settings > General Settings
This product will not work properly unless untill that value is changed.

For more information please contact Kayako support at https://my.kayako.com