# 554 5.6.0: email message is malformed, not accepted

URL: https://iblockspam.com/smtp-errors/554-5-6-0
Last updated: 2026-11-03

Code: 554 5.6.0 (permanent failure, the message bounced)
Provider: Gmail / Google Workspace

The receiving server refused the message because its content or structure is broken, for example bad MIME boundaries, invalid encoding or headers that don't follow the standard.

What the bounce says:

```
554 5.6.0 Email message is malformed. Not accepted.
```
Gmail's text for 554 5.6.0, as listed in Google's SMTP errors reference (the published line then points to the sender guidelines and RFC 5322).

RFC 3463 defines X.6.0 as "Other or undefined media error": something about the content of the message made it undeliverable, and no more specific code fits. RFC 5321 defines 554 as "Transaction failed". Together they mean the server read the message and refused it because of how it is built, not because of who sent it.

Gmail returns 554 5.6.0 "Email message is malformed. Not accepted." and points senders to its email sender guidelines and RFC 5322, the Internet Message Format. Typical faults are MIME parts with missing or mismatched boundaries, headers with invalid characters or broken line folding, wrong Content-Transfer-Encoding, and bare line feeds where the standard expects CRLF line endings. These almost always come from software that builds messages by hand, or from a gateway or footer tool that edits messages in transit.

Because the reply is 5xx, the message bounced. Rebuild it with a standard mail library, or send a test through a normal mail client to see if the same content goes through. If a relay sits between you and Gmail, send a test that bypasses it to find out whether it's breaking the message.

## Common causes

- Broken MIME structure, such as missing or mismatched boundaries between parts.
- Headers with invalid characters, bad folding or duplicates.
- Bare line feeds or inconsistent line endings from a script.
- A gateway, disclaimer or footer tool that damages the message while editing it.

## How to fix it (sender)

- Send the same content from a normal mail client; if it goes through, the problem is in the software that built the original.
- Use a maintained mail library instead of writing MIME by hand.
- Check any relay or footer tool in the path by sending one test that bypasses it.

## How to fix it (recipient or admin)

- No action needed at Gmail: the sending system has to produce a well-formed message.

**Q: What does 'media error' mean in 5.6.0?**
In enhanced status codes, the middle 6 covers message content or media. RFC 3463's X.6.0 is the catch-all for a content problem that no more specific code describes, such as a broken MIME structure.

**Q: Will resending fix a 554 5.6.0 malformed message?**
No. The same message will be refused again. Rebuild it with standard mail software, or find the relay or script that damages it, then send again.

Sources:
- Gmail SMTP errors and codes (Google Workspace Admin Help): https://knowledge.workspace.google.com/admin/support/troubleshooting/gmail-smtp-errors-and-codes
- RFC 3463: Enhanced Mail System Status Codes: https://www.rfc-editor.org/rfc/rfc3463
- RFC 5321: Simple Mail Transfer Protocol (reply codes, section 4.2): https://www.rfc-editor.org/rfc/rfc5321#section-4.2
- Email sender guidelines (Gmail Help): https://support.google.com/mail/answer/81126

---

Source: iBlockSpam, https://iblockspam.com/smtp-errors/554-5-6-0 (this is a Markdown copy; the HTML page is canonical). Quote with attribution and a link. Site index for AI assistants: https://iblockspam.com/llms.txt