X.6.0 · Message content or media
SMTP enhanced status code 5.6.0
Other or undefined media error
X.6.0 says something about the message content made it undeliverable, without a more specific code. Many providers use 5.6.0 for malformed messages.
| Registry code | X.6.0 |
|---|---|
| Forms in use | 5.6.0, 4.6.0 |
| Registry name | Other or undefined media error |
| Subject | 6: Message content or media |
| Permanent or temporary | 4.x.x persistent transient failure: retrying later may succeed; 5.x.x permanent failure: resending unchanged will not succeed |
| Associated basic codes | Not given |
| Defined in | [RFC 3463] |
What the registry says
Something about the content of a message caused it to be considered undeliverable and the problem cannot be well expressed with any of the other provided detail codes.
IANA SMTP Enhanced Status Codes registry, X.6.0
In practice
X.6.0 is the generic content code. Gmail returns 554 5.6.0 for a malformed message that is not accepted. Malformed MIME boundaries, broken encodings and invalid headers produced by template tools are common causes. Send the same message to a test inbox and inspect the raw source. Messages built by hand-written code are the usual source, especially when headers are joined without proper line folding or the multipart boundary appears inside the content.
What the sender should do
Check the message's MIME structure and headers for errors. Sending a plain, well-formed test message is a quick way to confirm.
Would verifying the list have prevented 5.6.0?
No
This reply is about your sending setup, the message or the receiving system, not about whether the address exists, so verifying the list will not prevent it.
How providers use X.6.0
Quoted from each provider’s own error reference.
- Gmail 554 5.6.0
Email message is malformed. Not accepted. For more information, go to Email sender guidelines and review RFC 5322 specifications.
Common questions
- What does 5.6.0 mean?
- X.6.0 says something about the message content made it undeliverable, without a more specific code. Many providers use 5.6.0 for malformed messages.
- What is the difference between 5.6.0 and 4.6.0?
- They share the subject and detail digits, so they report the same condition, "Other or undefined media error". The first digit is the class: 4.x.x persistent transient failure: retrying later may succeed; 5.x.x permanent failure: resending unchanged will not succeed.
- What should I do about 5.6.0?
- Check the message's MIME structure and headers for errors. Sending a plain, well-formed test message is a quick way to confirm.
- Would an email verifier have caught 5.6.0?
- No. This reply is about your sending setup, the message or the receiving system, not about whether the address exists, so verifying the list will not prevent it.
Full guides for this code
Sources
- IANA: SMTP Enhanced Status Codes registry (checked 2026-11-05)
- RFC 3463: Enhanced Mail System Status Codes (checked 2026-11-05)
- Google Workspace Admin Help: Gmail SMTP errors and codes (checked 2026-11-05)
Registry and provider wording is quoted exactly; guidance is written by the SimpleVerifier Team.
SimpleVerifier Team · Last checked against the sources 2026-11-05