Die Funktionalität dieser Website ist durch Wartungsarbeiten eingeschränkt, die Ihr Erlebnis verbessern sollen. Wenn ein Artikel Ihr Problem nicht löst und Sie eine Frage stellen möchten, können Sie unsere Gemeinschaft über @FirefoxSupport auf Twitter, /r/firefox oder Reddit fragen.

Hilfe durchsuchen

Vorsicht vor Support-Betrug: Wir fordern Sie niemals auf, eine Telefonnummer anzurufen, eine SMS an eine Telefonnummer zu senden oder persönliche Daten preiszugeben. Bitte melden Sie verdächtige Aktivitäten über die Funktion „Missbrauch melden“.

Weitere Informationen

Delivery Status Notification (Failure)

  • 1 Antwort
  • 1 hat dieses Problem
  • 1 Aufruf
  • Letzte Antwort von 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)

Alle Antworten (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.