Opens in a new tab

Message rejected due to: SPF fail – not authorized (550 5.7.23)

The receiving server checked SPF (this wording is from pypolicyd-spf, common on Postfix servers) and the address that sent the message is not authorised by the SPF record of the envelope sender’s domain.

550 5.7.23 Message rejected due to: SPF fail - not authorized. Please see http://www.openspf.net/Why?s=mfrom;id=user@example.com;ip=203.0.113.5;r=recipient@example.org

Your bounce names your own domain and sending address where this one says example.com and 203.0.113.5.

Code550 5.7.23
Sent byAny mail server
TypePermanent — not retried
CauseSPF

Check your domain’s SPF, DKIM and DMARC

Enter the domain in your From address. We read its records the way Any mail server does.

What it means

“Fail” means the record ends in -all and the server is not in it. A record ending in ~all gives a softfail, which most servers accept.

The openspf.net link in the message has been offline for years; it is not something you can fix or visit.

Why it happens

  • A sending service or server missing from the SPF record.
  • Mail forwarded through a server that is not in your record.
  • A record over 10 DNS lookups, which fails for everyone.

How to fix it

  1. Check your SPF record below, then add the missing sender to the one record you have.
  2. Keep it within 10 lookups; flatten it if you cannot.

Follow every include in your SPF record →

Sources

Message text and meaning checked on 25 September 2026 against these official sources:

Catch it before the bounces start

Add your domain and we monitor what these bounces are about — SPF, DKIM, DMARC, your sending servers on the blocklists, Gmail’s spam rate — every day, and email you the day something changes. Free for your first domain.

Create a free account