Outlook Error Code 5.4.6
for error code 5.4.6 through 5.4.20 in Office 365 Applies To: Office 365 Admin, Less Applies To: Office 365 Admin , More... Which version do I have? More... Here’s what to do if you get delivery status notification (DSN) error code 5.4.6 or Exchange NDR 5.4.6 through 5.4.20 in a non-delivery report (NDR). There can be several causes for dsn error code 5.4.6, but this might happen if the message hop count is exceeded or the route through which the message gets delivered is broken. Some causes and solutions for hop count being exceeded are provided later in this topic. The information here applies to a range of error codes 5.4.6 through 5.4.20. Finding information about Exchange NDR 5.4.x that will help you solve the problem Use the information in the Exchange NDR to decide how to fix the problem. Tips for fixing the problem that is causing Exchange NDR 5.4.6 Here are some procedures that you can try that may allow you to resend the message successfully. Message delivery from server-to-server can be complicated or require special access to settings, so most of these steps are designed for an Office 365 email administrator and not the average email sender. If the steps here don’t help, contact your email administrator and refer them to this information so they can try to resolve the issue for you. Accepted domain issues Verify that the recipient's domain is configured as an authoritative accepted domain in Exchange Online. For more information, see Manage Accepted Domains in Exchange Online. Hybrid configuration issues If your domain is part of a hybrid deployment between Exchange and Exchange Online, check the following items based on your configuration: You route all incoming mail for your hybrid domain through Exchange Online. This error can happen when the MX record for your hybrid domain points to Exchange Online, and the Outbound connector that's used to route mail to your on-premises Exchange organization is configured to use DNS routing. To fix the problem, configure a dedicated Outbound connector that uses smart host routing and that has your on-premises hybrid server configured as a smart host. The easiest way to fix the problem is to re-run the Hybrid Configuration Wizard in the on-premises Exchange organization. Or, you can verify the configuration of the Outbound connector that's used for hybrid by following these steps: Open the Office 365 portal at https://portal.office.com, and then click Admin > Exchange. In the Exchange admin cen
range? Exclaimer 3,206 Followers - Follow 43 Mentions12 Products Neal (Exclaimer) Sales & Marketing Manager GROUP SPONSORED BY EXCLAIMER TECHNOLOGY IN THIS DISCUSSION Microsoft Exchange Server 2010 Join the Community! Creating your account only takes a few minutes. Join Now We have a single Exchange 2010 server in our small organization. It has Mailbox, Client Access and Hub Transport roles installed. A user gets a NDR after around 30 https://support.office.com/en-us/article/Fix-email-delivery-issues-for-error-code-5-4-6-through-5-4-20-in-Office-365-81212ae4-4c36-4e8f-9546-e58b70cfd74b minutes after sending an email to an external domain. I have posted the NDR after the jump. These are the results of Get-AcceptedDomain and get-sendconnector PowerShell commands. Powershell[PS] C:\Windows\system32>Get-AcceptedDomain Name DomainName DomainType Default ---- ---------- ---------- ------- abc.com abc.com Authoritative True [PS] C:\Windows\system32>get-sendconnector Identity AddressSpaces Enabled -------- ------------- ------- Internal {SMTP:*;1} True External {SMTP:*;1} True I tried a lot https://community.spiceworks.com/topic/590879-exchange-server-2010-ndr-554-5-4-6-hop-count-exceeded-possible-mail-loop of searching however I couldn't pin-point the root of this problem. Any help will be highly appreciated. This is the NDR: TextDiagnostic information for administrators: Generating server: server-mail.abc.com johndoe@domain.uk server-mail.abc.com #554 5.4.6 Hop count exceeded - possible mail loop ## greensoldier@domain.uk server-mail.abc.com #554 5.4.6 Hop count exceeded - possible mail loop ## Original message headers: Received: from server-mail.abc.com (10.1.1.3) by server-mail.abc.com (10.1.1.3) with Microsoft SMTP Server (TLS) id 14.1.438.0; Mon, 22 Sep 2014 13:08:18 +0300 Received: from server-mail.abc.com (10.1.1.3) by server-mail.abc.com (10.1.1.3) with Microsoft SMTP Server (TLS) id 14.1.438.0; Mon, 22 Sep 2014 12:53:13 +0300 Received: from server-mail.abc.com (10.1.1.3) by server-mail.abc.com (10.1.1.3) with Microsoft SMTP Server (TLS) id 14.1.438.0; Mon, 22 Sep 2014 12:38:08 +0300 Received: from server-mail.abc.com (10.1.1.3) by server-mail.abc.com (10.1.1.3) with Microsoft SMTP Server (TLS) id 14.1.438.0; Mon, 22 Sep 2014 12:23:02 +0300 Received: from server-mail.abc.com (10.1.1.3) by server-mail.abc.com (10.1.1.3) with Microsoft SMTP Server (TLS) id 14.1.438.0; Mon, 22 Sep 2014 12:07:57 +0300 Received: from server-mail.abc.com (10.1.1.3) by server-mail.abc.com (10.1.1.3) with Microsoft SMTP Server (TLS) id 14.1.438
your account only takes a few minutes. Join Now Our Office 365 ( hybrid ) has recently been upgraded, and we have a couple of mailboxes https://community.spiceworks.com/topic/377408-5-4-6-hop-count-exceeded-possible-mail-loop on our on-premises exchange server, that now cannot send/receive email with the error Diagnostic code = LoopDetected; Reason code = TransferFailed; Status code = 546