We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Delivery Status Notification (Failure)

  • 1 cavab
  • 1 has this problem
  • 1 view
  • Last reply by Matt

more options

I am receiving this error message and have checked all the settings and have found nothing wrong with them.

Has anyone received this error and/or know how to fix it? Thanks.

Action: failed Status: 5.0.0 (permanent failure) Remote-MTA: dns; [104.47.65.110] Diagnostic-Code: smtp; 5.3.0 - Other mail system problem 554-'5.4.14 Hop count exceeded - possible mail loop ATTR34 [DM3GCC02FT017.eop-gcc02.prod.protection.outlook.com]' (delivery attempts: 0)

I am receiving this error message and have checked all the settings and have found nothing wrong with them. Has anyone received this error and/or know how to fix it? Thanks. Action: failed Status: 5.0.0 (permanent failure) Remote-MTA: dns; [104.47.65.110] Diagnostic-Code: smtp; 5.3.0 - Other mail system problem 554-'5.4.14 Hop count exceeded - possible mail loop ATTR34 [DM3GCC02FT017.eop-gcc02.prod.protection.outlook.com]' (delivery attempts: 0)

All Replies (1)

more options

The first Thing I need to ask is did you actually send the messages? These MTA failure messages often come back to genuine email accounts when the address has been used by spammers. In that scenario it is called backscatter. https://en.wikipedia.org/wiki/Backscatter_(email)

If it is genuine mail you are sending, there is a very high probability that misconfiguration of the network, probably on the recipient end is the problem. Perhaps misconfigured port forwarding on a firewall. But without knowing exactly where you are sending to. It is difficult to be at all precise.