554: more than one address in the From header
GMX refused the message because its From header lists more than one email address. GMX accepts only one address in From.
- GMX, WEB.DE
- Provider
- Permanent (5xx)
- Class
- Sources checked
- Author
At a glance
- Code
- 554
- Provider
- GMX, WEB.DE and mail.com
- Temporary or permanent
- PermanentRefused for good: the message comes back to the sender, and resending it gets the same answer.
- Who has to act
- The sender. The fix is on the sending side: your domain, your server or your list.
- What the server says
554 Transaction failed
What it means
RFC 5322 technically allows several authors in the From header, provided a Sender header names the one who sent it, but GMX does not accept that. Case r0741 means the From field of your message holds more than one address, and GMX refuses it with 554. Several From addresses also make DMARC checks ambiguous, since there is no single domain to align with. Put one address in From; if others should get replies, use Reply-To.
Common causes
- An application puts several addresses in the From field.
- A form or script joins the sender and a contact address into From.
- A misconfigured template lists a group address and a personal one together.
How to fix it
- 01Change the From header to a single address.
- 02Put any other addresses that should receive replies in Reply-To.
- 03Send the message again.
Sources
What this page rests on, checked on 20 Oct 2026. The explanation is ours; the reply text is the server's.
Related codes
- 554A header field has invalid syntax.GMX refused the message because a header, such as Date, From, Sender, Subject or To, is not written the way RFC 5322 and RFC 2047 require.
- 554Transaction failed.The server permanently refused the transaction, often after receiving the message data or straight away when the connection opened.
554 at other providers
- 554Permanent rejection (554).Yahoo or AOL rejected the message for good with a 554. Yahoo uses this code for several problems, from failed authentication to unacceptable content, so the wording of the reply tells you which.
- 554Failed authentication.Yahoo or AOL refused the message because it failed the checks that confirm the sending domain, such as DKIM against the domain's policy. Yahoo lists this among its permanent 553 and 554 errors.
- 554Recipient does not exist.The Yahoo or AOL account you wrote to does not exist. The failure is permanent: check the address with the recipient, and remove it from any list.
- 554No reverse DNS (PTR) record.Xfinity refused the connection because your sending IP has no PTR record. Every server sending to Xfinity needs valid reverse DNS, so the owner of the IP must add one.
- 554No reverse DNS for your IP.IONOS refused your mail because the IP address of your mail server has no domain name assigned to it in DNS (no PTR record).
- 554Reverse DNS does not meet IONOS policy.IONOS refused your mail because the PTR record of your IP does not meet its policy, typically a generic or dynamic-looking provider name.
All 57 GMX, WEB.DE codesEvery code in the wikiPaste your own bounce