The server reached Gmail over IPv6, and Gmail’s stricter rules for IPv6 senders were not met: the IPv6 address has no matching reverse DNS, or the message did not authenticate.
550 5.7.1 This message does not meet IPv6 sending guidelines regarding PTR records and authentication. For more information, go to Email sender guidelines. - gsmtp
| Code | 550 5.7.1 |
| Sent by | Gmail |
| Type | Permanent — not retried |
| Cause | Reverse DNS |
See what receivers see
Send one email to our test address and get back the sending server’s reverse DNS, TLS, authentication and blocklist results — the things this bounce is about.
What it means
Many servers are set up and tested over IPv4, then start using IPv6 on their own once the host enables it. The IPv4 address has reverse DNS and is in SPF; the IPv6 one has neither.
Why it happens
- No PTR record for the server’s IPv6 address, or one that does not resolve back.
- The IPv6 address is not in the SPF record (an ip6: term, or an include that covers it).
- The message is not DKIM-signed, so nothing else authenticates it.
How to fix it
- Set reverse DNS for the IPv6 address with your provider, to a name with an AAAA record pointing back.
- Add the IPv6 address to SPF, and sign with DKIM.
- Or make the server send over IPv4 only until both are in place (Postfix: inet_protocols = ipv4).
Sources
Message text and meaning checked on 25 September 2026 against these official sources:
- Gmail SMTP errors and codes — knowledge.workspace.google.com
- Email sender guidelines — support.google.com