Blog

SPF PermError after adding a second email provider

You added a second email service and now mail fails with "SPF PermError: multiple SPF records" or "too many DNS lookups". What each means, how to merge two SPF records into one, and how to check it.

Jonathan S.Updated 20 November 20266 min read

Your domain sent mail fine for years. Then you added a second service, a CRM, a newsletter tool, a new mail host, and suddenly replies land in spam or bounce with the word PermError in them. The cause is almost always one of three things in your SPF record, and each has a five-minute fix.

Where the error shows up

You rarely see a PermError in your own inbox. It appears in the bounce message a receiver sends back, in the Authentication-Results header of a message that did get through, or in a DMARC report. The header line looks like spf=permerror (sender SPF record is invalid) or names the cause outright. Open any message you sent to a Gmail or Outlook address, show the original, and search for spf=. The free header analyzer reads the same line and explains it.

PermError means permanent error: the receiver could not evaluate your record at all, so it treated your mail as unauthenticated. It is worse than a plain fail, because every message from the domain is affected, from every service, until the record is repaired.

If you see "multiple SPF records" or "more than one SPF record"

This is the one that follows adding a second provider. The new service's setup guide said "add this TXT record", you added it, and now the domain has two TXT records that both begin with v=spf1. The SPF standard, RFC 7208, is blunt about it: if the record set includes more than one SPF record, the check produces PermError (section 4.5, checked 6 October 2026). Two records do not add up; they cancel.

The fix is one record containing both services. Open your DNS editor, find the two TXT records at the root of the domain that start with v=spf1, and combine their mechanisms into a single record. Keep every include:, a, mx and ip4: term from both, list them once each, and end with one ~all or -all. Then delete the second record. Here is what a merge of a Google Workspace record and an Amazon SES record looks like:

One merged SPF record (TXT at the domain root)
v=spf1 include:_spf.google.com include:amazonses.com ~all
Both includes in one record, one all at the end. Replace the includes with the ones your two services gave you.

If you are moving to Faivelo, you do not have to do this by hand: its automatic DNS setup reads the SPF record that is already there and merges its own terms into it rather than adding a second one. If you are pasting records manually, the merge above is the step to get right.

If you see "too many DNS lookups"

Every include:, a, mx, ptr, exists and redirect in your record makes the receiver do a DNS query, and each include can contain more includes of its own. RFC 7208 section 4.6.4 limits the total to ten per evaluation and says implementations must return PermError when the limit is exceeded. A domain with Google, a CRM, a helpdesk, a newsletter tool and a web host can pass ten without anyone noticing, because the count is hidden inside the includes.

Count them. Resolve each include and add up every lookup it triggers, down the chain. The email checkup does the walk and prints the total. Then cut: remove services you no longer use, replace an include that only contributes a fixed address or two with ip4: terms (those do not count), and drop ptr entirely, which the RFC itself discourages. If you are still over ten with services you genuinely send from, that is the signal to consolidate who sends for the domain, not to split the record.

If the header just says "spf=permerror" with no reason

Then the record itself is malformed. The usual culprits: a stray space inside a term, include= instead of include:, two all mechanisms, a record longer than a single TXT string without being split correctly, or an include that points at a hostname with no SPF record of its own. Paste the record into a checker, read it term by term, and fix the one it stops on. A record that passes syntax and has one all at the end is almost always fine.

After the fix

  1. Wait for DNS. TXT changes usually show within minutes, sometimes up to the record's TTL. Do not re-edit in the meantime.
  2. Check the domain. Run it through the checkup. You want exactly one SPF record, fewer than ten lookups, and no syntax warning.
  3. Send a test. Send from each service to a Gmail address, open the original, and confirm spf=pass on every one.
  4. Read the DMARC reports. If you publish a DMARC record with a reporting address, the next day's reports will show every source passing. The free DMARC report analyzer turns the XML into a list.
SPF has one rule that catches nearly everyone: one domain, one record. Everything else is arithmetic.

FAQs

Can I just keep both SPF records and see what happens?

No. Two records are a PermError by definition, and receivers treat the mail as unauthenticated. Merge them into one today.

Does the order of includes matter?

Not for the result; a message passes if any term matches. Put the service you send most from first so the receiver finds it on the first lookup.

Should I end with ~all or -all?

Softfail (~all) asks receivers to be suspicious of unlisted senders; hardfail (-all) asks them to reject. Use ~all while you are still adding services, and -all once the list is stable and DMARC reports show nothing unexpected.

My provider added its own SPF record automatically. Is that the second one?

Often, yes. Hosts and registrars that pre-fill email records create one at setup, and a later service adds another. Keep one, fold the other in.

Will fixing SPF alone get my mail out of spam?

It fixes the PermError. Inbox placement also depends on DKIM signing and a DMARC policy. Check all three at once at /email-checkup.

Found this useful? Share it.

Let the records look after themselves

Faivelo writes SPF, DKIM and DMARC at your registrar and merges into an SPF record that already exists instead of adding a second one. Add your domain and check the result in the same five minutes.

Set up your domainFree 14-day trial. No card needed.

Keep reading