What should I do
The change that matches each bounce: the record, the PTR, the TLS session, or the From header the error list actually names.
The matching fix for each error-code page: what Google or the RFC actually asks you to change, without inventing a DNS record when the bounce is rate limits or STARTTLS.
Gmail's sender guidelines still require SPF or DKIM for all senders and SPF, DKIM, and DMARC for bulk mail over TLS. RFC 7208 permerror is not temperror; duplicate `v=spf1` TXT records or more than ten DNS-querying SPF terms need a DNS edit, not a retry.
/
Fix 550 5.7.26Fix 550 5.7.26 by authenticating the sending server with SPF or DKIM. On direct mail, Google also requires that domain to align with the From header. Fix SPF PermErrorA receiver cannot interpret the SPF record. Fix the DNS. RFC 7208 says a later retry will not clear a permerror the way it can clear a temperror. Fix DMARC alignmentMake a passing SPF or DKIM check use a domain that aligns with the header From. RFC 7489 says passing SPF on a different domain does not satisfy DMARC. Fix too many SPF lookupsGet the DNS-querying terms down to 10. RFC 7208 says ip4 and ip6 do not query DNS at evaluation time, so an address does not spend one of the 10. Fix 550 5.7.27Make SPF pass for the host that sent the message. Gmail's bulk-sender rule on 550 5.7.27 is SPF, not SPF or DKIM. List dated 18 September 2026 UTC. Fix 550 5.7.30Make DKIM pass for the message. Gmail's bulk-sender rule on 550 5.7.30 is DKIM. Publish the key the provider gives you. List dated 18 September 2026 UTC.