Why Your Quotes Keep Disappearing: A Plain-English Email Authentication Tune-Up for 2026
Photo: JoachimKohler-HB, CC BY-SA 4.0, via Wikimedia Commons
A small business owner we worked with had a simple complaint: clients kept saying they never received quotes. The sent folder showed every message went out. The follow-up calls happened anyway. What looked like forgetful customers was actually a deliverability problem—and it had been quietly costing the company work for months.
That is the frustrating part about email. Your outbox says delivered. Your customer says nothing arrived. Somewhere between those two truths is a settings menu most owners never open.
The leak you cannot see from your sent folder
When you send an invoice, a quote, or a follow-up, your email provider hands the message to the internet. The receiving side—Gmail, Outlook, Yahoo, a corporate mail server—decides whether to trust it. That decision is not personal. It is based on records attached to your domain name.
If those records are missing, incomplete, or contradictory, legitimate mail gets treated like junk. Not every time. Not loudly. Just often enough to hurt. A quote lands in spam. An invoice gets filtered. A follow-up disappears. Nobody files a ticket because nobody knows it happened.
For a small business, that is a revenue problem hiding in a DNS control panel.
Three records, one goal: prove you are who you say you are
You do not need to become a mail administrator to fix this. You need to understand what three records do.
SPF is a list of servers allowed to send email for your domain. Think of it as a guest list. If a sending server is not on the list, receivers get suspicious.
DKIM adds a cryptographic signature to your messages. It lets the receiving side verify that the message really came from your domain and was not altered in transit.
DMARC tells receivers what to do when SPF or DKIM fails, and it can send you reports about who is sending as your domain. It is the policy layer.
When all three are set up correctly, your legitimate email has a much better chance of reaching the inbox. When they are missing or misconfigured, even honest messages look sketchy.
Before you touch DNS: gather three facts
You can run this checkup in under an hour, but do not start editing records until you know three things.
- Who hosts your DNS? That is usually your domain registrar or a separate DNS provider. You need login access.
- Who sends email as your domain? This includes your main email provider, your website contact form, your invoicing tool, your CRM, your scheduling app, and any newsletter platform.
- Who can edit DNS records? If it is a web developer or an IT vendor, get them on the phone or in a shared document. You do not want two people making conflicting changes.
Write the answers down. This inventory is the part most people skip, and it is the part that causes the most trouble later.
Step 1: Inventory every service that sends as your domain
Open your email admin console and your DNS dashboard. Then list every tool that might send email using your domain name. Common culprits include invoice and accounting software, customer relationship management tools, appointment reminders, website forms, and email marketing platforms.
This matters because SPF and DKIM are not just about your inbox provider. If your invoicing app sends as your domain but is not included in your SPF record or signed with DKIM, those invoices are more likely to be filtered.
A simple spreadsheet works fine: service name, purpose, sender address, and whether it is included in SPF or DKIM. If you cannot answer the last two columns, that is your first fix.
Step 2: Read your SPF record without panic
Look up the TXT record at your root domain. It will usually start with v=spf1. A basic record might look like v=spf1 include:yourprovider.com -all.
You want one SPF record, not two. Multiple SPF records confuse receivers. You also want to stay within the lookup limit—SPF allows a maximum of 10 DNS lookups, and each include counts. If your record is a long chain of includes, it may be failing silently.
Do not just add another include and hope for the best. If the record is messy, ask your email provider or DNS host for help consolidating it. The goal is a clean list of authorized senders with a clear ending policy.
Step 3: Confirm DKIM is actually signing your mail
DKIM setup depends on your provider. Microsoft 365, Google Workspace, and most mainstream providers give you a selector and a DNS record to publish. Your job is to confirm the record exists and that mail is being signed.
Use a free DKIM checker or send a test message to a Gmail account and inspect the headers. Look for a passing DKIM result. If it fails, go back to your provider's admin console and enable DKIM signing. For third-party tools, follow their documentation—they usually provide the exact DNS record to add.
A common mistake is assuming DKIM is on because the provider offers it. It is often available but not enabled.
Step 4: Add DMARC in monitoring mode
DMARC lives at _dmarc.yourdomain.com as a TXT record. Start simple: v=DMARC1; p=none; rua=mailto:[email protected]; pct=100.
The p=none policy tells receivers to take no action but still send reports. That gives you visibility before you tighten the rules. Do not jump straight to reject unless you have a clean inventory and someone reviewing the reports.
After a few weeks, look at the reports. If legitimate senders are passing and you see no surprises, move to p=quarantine and eventually p=reject. That progression is how you protect your domain without blocking your own invoices.
Step 5: Send real tests, not guesses
Send a message from your main address to a Gmail account, an Outlook account, and a Yahoo account. Check the inbox and the spam folder. Then inspect the authentication results in the headers. You want SPF, DKIM, and DMARC all passing.
Do the same for your invoicing tool and any other service that sends as your domain. A test from your main inbox does not prove that your billing system is authenticated.
The quarterly habit
Email authentication is not a one-time project. Every time you add a scheduling tool, change your website host, or switch email providers, the records may need updating. Put a reminder on the calendar once a quarter. Open the spreadsheet, check the records, and send a test.
That small habit prevents the slow, invisible leak of quotes, invoices, and follow-ups that never reach the inbox. It also gives you something better than hope: evidence that your email is set up correctly.
Deliverability is not glamorous. But when a client says they never got the invoice, you will be glad you spent the afternoon in the settings menu.