After you connect an email address to Dubsado, Dubsado automatically checks your SPF record. If something is wrong with that record, you'll see an error message in your email deliverability settings. This article walks through what each one means and how to fix it.
Where to find your SPF status
Navigate to Settings ➔ Emails, or Messages ➔ Settings ➔ Emails, then scroll to the Email Deliverability section. The SPF subsection shows your current status once you've connected an email account.
For SMTP connections, Dubsado shows the exact DNS record fields you need (Type, Host / Name, and Value) with copy buttons directly in the SPF section, so you can see what to add or update without leaving Dubsado.
For every error below, the fix starts in the same place: open your domain host's DNS (domain name server) settings page and look at the SPF record listed there. Once you update it, come back to Dubsado and click Verify to re-check your status. DNS changes can take up to 48 hours to propagate, so give it time before checking again if verification doesn't succeed right away.
If you've worked through the troubleshooting below and an error still won't resolve, reach out to your email or domain host for further assistance.
Dubsado checks your SPF record automatically as soon as you connect an email address, so you don't need to trigger the check yourself.
No valid TXT record found for one of the domains listed in your SPF record
This error means you have an SPF record listed with your domain host, but Dubsado couldn't verify that it's valid. Here are the most common reasons why.
The SPF value is incorrect
Your SPF value is provided by your email host, so make sure you're using their most current value. To find it, reach out to your email host directly or search their help center for "SPF record."
For your convenience, here are common email host SPF values. Enter these as a TXT record, with Host (sometimes called Name) set to an @ symbol:
Google:
v=spf1 include:_spf.google.com ~allMicrosoft:
v=spf1 include:spf.protection.outlook.com ~allGoDaddy:
v=spf1 include:secureserver.net ~allZoho:
v=spf1 include:zoho.com ~allorv=spf1 include:one.zoho.com ~allAny other SMTP connection:
v=spf1 a:spf.dubsado.com ~all
If you're connected through SMTP, Dubsado suggests the exact value to add. It inserts a:spf.dubsado.com into your existing record, or offers v=spf1 a:spf.dubsado.com ~all if you don't already have one. Copy it into your DNS settings.
You selected SPF type instead of TXT type
When you add your SPF record with your domain host, make sure you're entering it as a TXT type, not an SPF type. Some domain hosts, like Wix, show separate sections for TXT and SPF records, so you'll want to create your SPF record in the TXT section.
At one point, SPF records were their own record type, separate from TXT. Most people are more familiar with TXT records, so SPF-specific records never fully replaced them, but many domain hosts still show SPF as its own option alongside TXT. Enter your record as TXT.
The SPF record hasn't yet been updated
If you recently added or fixed your SPF record with your domain host, there's a waiting period called propagation, where it can take up to 48 hours for the new record to update across the internet.
We found multiple SPF records on your domain
A domain can only have one SPF record. You can identify an SPF record by looking for v=spf1 as a value in your DNS settings. If you see v=spf1 listed more than once, all of those values cancel each other out, and none will be seen as valid.
To fix this, merge your records so you only have one SPF record in your domain settings. For a walkthrough, see merging multiple SPF records.
We could not find any domains on your SPF record
This error means Dubsado couldn't find a domain associated with your SPF record. The most likely cause is that your domain host doesn't have an SPF record at all. To fix this, you'll need to add an SPF record with your domain host.
We found an error in your SPF record
This error most often shows up because of a typo, or because merged SPF records weren't combined correctly.
A valid SPF record always starts with v=spf1 and ends with ~all or -all, and you can only have one of each in a single record. For example:
v=spf1 include:_spf.google.com ~all
Check your record against this pattern to spot what might be off.
There was an error with your SPF record
This is a catch-all error, meaning Dubsado couldn't verify your SPF record for a reason other than the ones above. Work through the causes below. If the error still won't clear, contact your email or domain host to determine the cause.
The SPF record hasn't yet been updated
If you recently added or fixed your SPF record, there's a waiting period called propagation, where it can take up to 48 hours for the new record to update across the internet.
Too many merged SPF records
If you've merged a large number of SPF records, you might have reached the maximum number of allowed DNS lookups. Per RFC 7208, an SPF record can have a maximum of 10 DNS lookups.
Each instance of the following terms counts as one lookup:
redirectincludeamxptrexists
These terms are not counted against the 10 DNS lookup limit:
allip4ip6exp
If you have more than 10 DNS lookups, use an SPF flattening tool to reduce them. See merged SPF records for more on combining records correctly.
The SPF record has too many characters
Your SPF record must be under 255 characters, per RFC 7208. You're unlikely to run into this unless you have many merged SPF records.
To fix a record that's over 255 characters, break it up into multiple strings of 255 characters or less, using quotation marks around each string. For example:
Valid (two strings, each under 255 characters):
"v=spf1 ip4:192.168.0.1 ip4:192.168.0.2 ip4:192.168.0.3 ip4:192.168.0.4 ip4:192.168.0.5 include:_spf.google.com" "ip4:192.168.0.6 ip4:192.168.0.7 ip4:192.168.0.8 ip4:192.168.0.9 ip4:192.168.1.0 ip4:192.168.1.1 include:zoho.com ~all"Not valid (one string over 255 characters):
"v=spf1 ip4:192.168.0.1 ip4:192.168.0.2 ip4:192.168.0.3 ip4:192.168.0.4 ip4:192.168.0.5 include:_spf.google.com ip4:192.168.0.6 ip4:192.168.0.7 ip4:192.168.0.8 ip4:192.168.0.9 ip4:192.168.1.0 ip4:192.168.1.1 ip4:192.168.1.2 ip4:192.168.1.3 include:zoho.com ~all"
The maximum length of a value in a TXT record is 4,000 characters. The 255-character limit applies per string, not to the record as a whole.
Your SPF record is valid but does not include Dubsado
If you're connected through SMTP, you might see a message that your SPF record is valid but doesn't include Dubsado. This means your record is otherwise fine, but it needs to authorize Dubsado's mail servers so emails sent through Dubsado are recognized as legitimate.
To fix this, update your existing record using the suggested Value Dubsado shows in the SPF section, then click Verify. This warning only applies to SMTP connections. If you're connected through Google or Microsoft, you won't see it.
FAQ
Where do I see my SPF status in Dubsado?
Go to Settings ➔ Emails and scroll to the Email Deliverability section. The SPF subsection shows your current status. You can also get there through Messages ➔ Settings ➔ Emails.
I fixed my SPF record but Dubsado still shows an error. What now?
DNS changes can take up to 48 hours to propagate. Click Verify to re-check your status. If you see a message that no changes were detected, your record hasn't propagated yet, so wait and try verifying again later.
Do I need to set up SPF again if I change domain hosts?
Yes. If you move to a new domain host, you'll need to set up and verify your SPF record with that host.
Should I enter my SPF record as a TXT type or an SPF type?
Always TXT. Some domain hosts show a separate SPF type, but don't use it. Create your SPF record in the TXT section instead.
