TL;DR
- An industrial supplier's automated quote system had a 20–30% spam rate — prospective buyers weren't receiving responses, and nobody knew
- Root cause: no SPF, DKIM, or DMARC configured; outbound email sent from the same IP used for hosting, with a poor reputation from prior tenant activity
- We implemented DNS authentication, created a dedicated sending subdomain, and set up Google Postmaster Tools monitoring
- Deliverability reached 98.4%; lead response rate increased 18%; estimated $50,000+ in annual sales recovered
Quote Emails Landing in Spam, Leads Going Cold
An industrial supplier's sales process depended on their automated quote system: prospect submits a request through the website, system generates and sends a quote by email. The process had been running for years. What they didn't know was that a significant portion of those quote emails were being filtered as spam by Gmail and Outlook before the prospect ever saw them.
The symptom they noticed: longer-than-expected response times from prospects, some deals going quiet. When they dug in, they found prospects who had submitted quote requests, never received a response, and moved on. The quote had gone out. It had just never arrived.
What the audit found:
- No SPF (Sender Policy Framework) record configured on the domain
- No DKIM (DomainKeys Identified Mail) signing on outbound email
- No DMARC policy — receiving servers had no instruction on what to do with unauthenticated messages
- Outbound email sending from the same shared IP used for website hosting — an IP with prior spam history from previous tenants on the same server
- No monitoring of any kind on email deliverability or bounce rates
The combination was damaging. Without SPF and DKIM, the supplier's email had no authentication signal — it looked, to Gmail and Outlook's filters, exactly like a spoofed message. The shared IP's reputation made it worse. Google and Yahoo's 2024 sender requirements formalized what had been best practice for years: DKIM is required, SPF is expected, DMARC is the tie-breaker. The supplier had none of them.
DNS Authentication and a Dedicated Sending Domain
We approached the fix in layers: authentication first, then reputation isolation, then monitoring.
DNS authentication: Configured a proper SPF record authorizing the supplier's sending infrastructure. Implemented DKIM signing with a 2048-bit key at the domain level. Set DMARC to monitoring mode initially to capture baseline data, then moved to a quarantine policy once authentication was confirmed working across all sending sources.
Dedicated sending subdomain: Created a separate subdomain (mail.domain.com) for transactional email. Transactional email — quotes, order confirmations, shipping notices — now sends from a clean IP with its own reputation history, isolated from any issues with the primary domain or website hosting IP.
Reverse DNS and reputation: Configured correct PTR records (reverse DNS) for the sending IP, which receiving mail servers check as a basic trust signal. Submitted the IP to major blocklist removal processes where it appeared.
Monitoring: Set up Google Postmaster Tools monitoring for domain reputation and spam rate. Configured bounce and complaint rate tracking. Ran test sends through Gmail, Outlook, and Yahoo before going live.
Testing: Ran comprehensive email authentication testing using MXToolbox and mail-tester.com to verify SPF, DKIM, and DMARC pass rates across major providers before treating the fix as complete.
98.4% Email Deliverability, 18% More Lead Responses
Results measured over the 90 days following implementation:
- Email deliverability improved to 98.4% — from a 20–30% spam rate to consistent inbox placement
- Lead response rate increased 18% — prospects were now actually receiving and responding to quotes
- Inbox placement above 95% consistently across Gmail, Outlook, and Yahoo
- Zero spam complaints to major email providers in the 90 days following implementation
- Estimated $50,000+ in recovered annual sales — based on the prior lead loss rate, average deal size, and close rate
The $50,000 estimate is conservative. It represents the recoverable portion of the leads that were being silently filtered — not counting the deals that may have been lost before the problem was identified.
Frequently Asked Questions
What is email deliverability? Email deliverability measures whether your outbound email actually reaches the recipient's inbox — as opposed to being filtered to spam, deferred, or rejected entirely. A deliverability rate of 98.4% means 98.4% of sent messages reached the inbox. A 20–30% spam rate means 20–30% were filtered before the recipient saw them.
How do SPF, DKIM, and DMARC work together? SPF declares which servers are authorized to send email from your domain. DKIM adds a cryptographic signature to each message so the recipient's server can verify it came from you. DMARC ties them together: it tells receiving servers what to do when a message fails SPF or DKIM (monitor, quarantine, or reject), and it reports back to you when failures occur. All three working together are the standard authentication stack for commercial email in 2024–2026.
How long does it take to fix email deliverability? DNS changes like SPF and DKIM propagate within 24–48 hours. Reputation recovery — improving a domain or IP's standing with receiving mail servers — takes longer: typically 2–4 weeks of clean sending history before Gmail and Outlook's filters fully trust a previously flagged sender. In this case, using a new dedicated sending subdomain bypassed the reputation recovery timeline almost entirely.
How do I know if my business email is being filtered as spam? Google Postmaster Tools is free and shows your domain's spam rate and reputation as seen by Gmail. MXToolbox checks your SPF, DKIM, and DMARC configuration and reports on common blacklists. If your domain has no DKIM record configured, that's a strong signal that deliverability is worse than you think.
What is a dedicated sending domain and why does it help?
A dedicated sending subdomain (like mail.yourdomain.com) lets transactional email build its own sending reputation separate from your primary domain and website hosting IP. If your website's hosting IP has a poor reputation from previous tenants, moving transactional email to a clean IP with its own history insulates your quote and order emails from that history.