550 5.7.1: Gmail IPv6 sending guidelines not met

Quick fix

Ask the provider of the sending IPv6 address to set a PTR record with the server's host name, publish an AAAA record for that name, and cover the address in SPF with ip6:.

How to fix it

  1. Find the sending IPv6 address in the bounce or in the Received headers.
  2. Ask the provider of that address to set a PTR record with the server's host name; most cloud consoles have a reverse DNS setting for IPv6 addresses too.
  3. Publish an AAAA record for that host name that points to the same IPv6 address.
  4. Add the IPv6 address or range to the SPF record with ip6:, or use the include your mail provider documents, and sign the mail with DKIM.
  5. If you cannot set reverse DNS for IPv6, send to Gmail over IPv4 only, for example with inet_protocols = ipv4 in Postfix, until you can.

Learn more: MX records explained: priority and null MX

How to check

The reverse DNS check looks up the PTR record of every IPv4 and IPv6 address of the domain's MX hosts and checks that the name resolves back. For the server in the bounce, look up the IPv6 address it names, for example with dig -x 2001:db8::25, and check SPF for the envelope sender domain.

The Reverse DNS check for mail servers opens with your domain filled in; it runs when you press Check.

Tools to check it

What the error means

Full error text: 550 5.7.1 This message does not meet IPv6 sending guidelines regarding PTR records and authentication.

This 550 5.7.1 is Gmail's rejection for mail that arrives over IPv6 without the reverse DNS and authentication Gmail requires. Google's list of Gmail SMTP errors gives the text as "This message does not meet IPv6 sending guidelines regarding PTR records and authentication." It often appears after a server or provider starts sending over IPv6, because IPv6 addresses rarely get a PTR record by default.

Google's sender guidelines explain it under "Fix IPv6 authorization errors": "An IPv6 authorization error could mean that the PTR record for the sending server isn’t using IPv6. If you use an email service provider, confirm they’re using an IPv6 PTR record." The general rule applies to IPv6 too: "The public IP address of a sending SMTP server must have a corresponding PTR record that resolves to a hostname. [...] The same hostname must also have an A (for IPv4) or AAAA (for IPv6) record that resolves to the same public IP address used by the sending server."

The authentication part is SPF or DKIM. An SPF record that lists only ip4: ranges does not cover the server's IPv6 address, so SPF fails as soon as the server sends over IPv6 (RFC 7208, section 5.6: ip6: matches IPv6 addresses). Microsoft has the same two rules for IPv6: its 5.7.25 reads "Access denied, the sending IPv6 address [...] must have a reverse DNS record" and its 4.7.26 reads "Access denied, a message sent over IPv6 [...] must pass either SPF or DKIM validation, this message is not signed". Missing reverse DNS on IPv4 gives 550 5.7.25 at Gmail.

Sources

All findings