Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

My emails bounce because the SPF check fails

Short answer

SPF is a DNS record listing which services may send mail for your domain. It fails when a sender you use is missing from it, when it was never updated after a change, or when the record is malformed. Google says SPF changes can take up to 48 hours to start working, so change one thing at a time.

  • Written for business owners
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Does this sound like your situation?

  • Bounce messages mention SPF, or a mail check shows SPF fail or softfail.
  • Mail from my own domain works from one tool but bounces from another.
  • Newsletters, invoices or booking emails started failing after I added a new service.
  • Customers say my mail goes to spam while my colleagues receive it.
  • My web person says there are two SPF records, or none at all.

Why does this happen?

  1. A sender you use is not listed

    SPF is a DNS TXT record that starts with v=spf1 and lists every service allowed to send for the domain. Google says to update it whenever you add a mail sender, and to remove senders you no longer use. A shop system, a CRM or an invoicing tool that sends in your name each needs its own entry.

  2. The record was copied wrong or doubled

    A new email service often tells you to add its own SPF record. If you add it next to the old one instead of merging them, receivers can treat the result as an error. Quotes, stray spaces and a missing ending also break it.

  3. The record has grown too long

    Google's page says an SPF record can have up to 10 include tags. Every service you add uses one, so a business with a newsletter tool, a CRM, a shop and a helpdesk can run into the limit.

  4. Mail is sent for a subdomain or a different address

    Google states each domain and each subdomain needs its own SPF record. A tool that sends from a subdomain, or with its own return address, is checked against that name, not the one on your website.

  5. SPF is only one of the checks

    Google requires every sender to set up SPF or DKIM, and bulk senders must use SPF, DKIM and DMARC. Fixing SPF alone may not be enough if the other records are missing.

What can I do about it today?

  1. Write down every service that sends mail as youYour mail provider, website forms, newsletter tool, CRM, invoicing, shop and helpdesk. This list is what the record has to match.
  2. Ask whoever manages your domain to show the current SPF recordIt is a TXT record at the domain. Ask for a screenshot or a copy of the text, and keep it before any change.
  3. Do not delete records to see what happensRemoving a record you do not recognise can stop mail from a tool you forgot about. Copy it first and change one thing at a time.
  4. Send a test to a Gmail addressIn Gmail, open the message and choose Show original. It shows whether SPF passes or fails, and for which domain.
  5. Allow time after a changeGoogle says it can take up to 48 hours for SPF to start working, so do not keep editing every hour.

When should I bring someone in?

  • Invoices, orders or password resets are bouncing now.
  • Nobody knows which services send mail for your domain.
  • You already have more than one SPF record or a very long one and are afraid to touch it.

How do I handle it?

  1. Collect real evidence firstI read the headers of failing messages to see which sender, which domain and which check failed.
  2. Build the list of legitimate sendersI match the list from the owner against what the mail logs actually show, so no sender is cut off by mistake.
  3. Write one clean recordI merge the entries into a single record, keep it inside the lookup limit and keep a copy of the old text for rollback.
  4. Check DKIM and DMARC togetherSPF passing is not the goal; mail passing for the right domain is. I check all three and test with real messages.

The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.

What do owners ask about this?

What is the difference between SPF softfail and fail?

It comes from the ending of the record. Google recommends ending with ~all, which tells receivers to treat mail from unlisted servers as spam, instead of refusing it outright.

Can I have two SPF records?

Merge them into one. Google's guide describes one record per domain listing all senders, and a duplicate from a new service is a common cause of failures.

How long until it works?

Google says it can take up to 48 hours for SPF authentication to start working after a change.

Is SPF enough to stop spam folder problems?

No. Receivers also look at DKIM, DMARC and complaint rates, so a passing SPF check does not mean the mail will reach the inbox.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.

For your developer: the technical fixes

Next step

Want this off your desk?

Send me a few lines on where things stand. I reply within 24 hours.