By the registry, 5.7.27 means the sender’s own domain takes no mail (a null MX), so a bounce could not be returned. Gmail uses it for a bulk sender whose mail failed SPF.
| Code | 5.7.27 |
| Meaning | Sender address has null MX |
| Kind | Permanent failure — the sender gives up |
| Sent in reply to | With 550 |
| What the sender does | Returns the message — where it can |
| Defined in | RFC 7505 |
Paste your bounce
Paste the line with the code — or the whole bounce: we explain each code in it, say whether the sender will try again, and link the service’s own page where it has one. It is read in your browser; nothing is sent.
What to do
- From Gmail: make the sending server pass SPF for the Return-Path domain.
- Elsewhere: do not send from a domain that publishes a null MX.
What each provider means by it
| Who | What they say |
|---|---|
| Gmail | 550 5.7.27 This message was blocked because it didn’t pass SPF authentication — for bulk senders; temporary form 421 4.7.27. |
| Yahoo | Refuses mail whose sender domain has a null MX, as the registry intends. |
Bounces with this code
Sources
Checked on 27 September 2026 against these official sources:
- Simple Mail Transfer Protocol (SMTP) Enhanced Status Codes Registry — iana.org
- RFC 7505: A “Null MX” No Service Resource Record for Domains That Accept No Mail — rfc-editor.org
- Gmail SMTP errors and codes — knowledge.workspace.google.com
- Email sender guidelines FAQ — support.google.com
- SMTP Error Codes — senders.yahooinc.com