Opens in a new tab

spf=softfail: the sending server is probably not allowed

The same finding as an SPF fail, stated more softly: the IP address the message came from is not in the envelope sender’s SPF record, and the record ends in ~all — “probably not authorised”. Receivers should not reject on this alone, but many count it against the message.

spf=softfail (google.com: domain of transitioning bounce@example.com does not designate 192.0.2.1 as permitted sender) smtp.mailfrom=bounce@example.com
How other mail servers write it

Microsoft 365 and Outlook.com

spf=softfail (sender IP is 192.0.2.1) smtp.mailfrom=example.com

Microsoft’s Received-SPF

Received-SPF: SoftFail (protection.outlook.com: domain of transitioning example.com discourages use of 192.0.2.1 as permitted sender)

Postfix (policyd-spf)

Received-SPF: Softfail (mailfrom) identity=mailfrom; client-ip=192.0.2.1; envelope-from="bounce@example.com"
Resultspf=softfail
Usually fixed byThe sender, or whoever forwarded it
Published as~all at the end of the SPF record
ReceiversShould not reject on this alone (RFC 7208 §8.5)

Check the sender’s SPF record

Enter the domain from smtp.mailfrom (the envelope sender): we read its SPF record, follow every include and count the lookups.

What it means

A softfail means the IP is not listed and the domain asks receivers to be suspicious rather than to refuse. Google recommends ~all for Google Workspace, so a softfail usually points at the same problem as a fail: a sender missing from the record. Gmail’s wording — “domain of transitioning …” — is its standard text for this result.

Why it happens

  • A service that sends as your domain is missing from the record.
  • The message was forwarded, so it arrived from the forwarder’s server.
  • Someone sending as your domain without permission.

How to fix it

  1. Find the IP address in the result and the service it belongs to.
  2. Add that service to the SPF record — with its include: or its IP ranges — staying within ten lookups.
  3. Make sure DKIM passes for your domain too: then DMARC passes even when SPF does not.

See it for yourself

dig TXT example.com +short

The record’s last term is ~all; the question is which sender is not listed before it.

Sources

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

See every receiver’s verdict on your mail

Add your domain and collect its DMARC reports: what Gmail, Microsoft, Yahoo and the rest decided about every message sent as you — SPF, DKIM and DMARC, pass or fail — and who is sending it. Free for your first domain.

Create a free account