Email Deliverability: The Technical Setup Most Firms Get Wrong

The Unsexy Foundation of Outbound Success

You can write the best cold email in the world, but if it lands in spam, nobody will ever read it. Email deliverability is the unsexy, technical foundation of outbound sales success, and most B2B service firms get it completely wrong.

The consequences of poor deliverability are severe and often invisible. Your emails silently disappear into spam folders. Your reply rates plummet for reasons you cannot diagnose. Your domain reputation degrades over time. And worst of all, you blame your messaging or your targeting when the real problem is that your emails are not being seen at all.

At MAVEN, email infrastructure setup is the first thing we install for every client. Before a single sequence launches, before a single email is written, the deliverability foundation must be solid. This guide covers the complete technical setup — domain strategy, DNS authentication, warming protocols, sending limits, and ongoing monitoring — so your emails actually reach the inbox.

Why Deliverability Matters More Than Ever in 2026

The email landscape has shifted dramatically. Google and Yahoo introduced strict sender authentication requirements in early 2024. Microsoft followed. Email service providers (ESPs) have become increasingly aggressive about filtering unsolicited email.

What has changed:

• Authentication is mandatory: Emails without proper SPF, DKIM, and DMARC are flagged or rejected
• Sending volume limits are lower: The era of sending 500 cold emails per day from a single domain is over
• Engagement signals matter more: ESPs now track whether recipients open, reply to, or delete your emails — and use this data to determine inbox placement
• Spam complaints have higher impact: A few spam complaints can now tank your domain reputation for weeks

The bottom line: Technical setup is no longer optional. It is a prerequisite for any B2B sales outbound programme.

The Domain Strategy: Protecting Your Primary Domain

Rule Number One: Never Send Cold Emails From Your Primary Business Domain

This is the most important rule in email deliverability, and the one most firms violate. If you send cold email from yourcompany.com, you risk damaging the domain reputation that your entire business depends on — client communications, proposals, invoices, and internal email all flow through this domain.

A damaged domain reputation means your legitimate business emails start landing in spam. Clients do not receive your proposals. Invoices go unseen. Internal communications break down. The cost of recovering a primary domain from a poor reputation far exceeds the cost of setting up proper sending infrastructure.

Buying Sending Domains

Purchase 2-3 domain variations for cold outreach:

Option 1: Same name, different TLD

• Primary: yourcompany.com
• Sending: yourcompany.co.uk, yourcompany.io

Option 2: Variations

• Primary: yourcompany.com
• Sending: getyourcompany.com, yourcompanyteam.com, tryyourcompany.com

Option 3: Descriptive variations

• Primary: yourcompany.com
• Sending: yourcompany-consulting.com, yourcompany-group.com

Domain Selection Best Practices

• Keep them recognisable: The prospect should be able to connect the sending domain to your company
• Avoid cheap or suspicious TLDs: Stick with .com, .co.uk, .io, or your country code
• Register for at least 1 year: Domains registered for short periods are flagged as potentially spam
• Set up a basic website: Even a simple redirect page on each sending domain adds legitimacy

DNS Authentication: The Big Three

SPF (Sender Policy Framework)

What it does: Tells receiving email servers which IP addresses are authorised to send email on behalf of your domain.

How it works: You add a TXT record to your domain's DNS that lists the authorised sending services. When a receiving server gets an email from your domain, it checks the SPF record to verify the sender is authorised.

Setup steps:

1. Identify all services that send email from your domain (Apollo.io, Google Workspace, etc.)
2. Create a TXT record with the appropriate includes
3. Example: v=spf1 include:_spf.google.com include:servers.mcsv.net ~all
4. Verify with an SPF checker tool

Common mistakes:

• Too many lookups: SPF allows a maximum of 10 DNS lookups. Exceeding this causes SPF to fail silently.
• Missing services: Forgetting to include a sending service means its emails fail SPF checks
• Using +all: Never end your SPF record with +all (allows any server to send). Use ~all or -all.

DKIM (DomainKeys Identified Mail)

What it does: Adds a digital signature to your emails proving they have not been tampered with in transit. This is like a wax seal on a letter — it proves the email came from your domain and has not been altered.

How it works: Your email service generates a public/private key pair. The private key signs each outgoing email. The public key is published in your DNS records. Receiving servers use the public key to verify the signature.

Setup steps:

1. In your email service (Google Workspace, Apollo.io, etc.), find the DKIM settings
2. Generate the DKIM key pair
3. Add the public key as a CNAME or TXT record in your DNS
4. Enable DKIM signing in your email service
5. Verify with a DKIM checker tool

Common mistakes:

• Not enabling DKIM for all sending services: Each service needs its own DKIM key
• Incorrect DNS record format: Copy the record exactly as provided — extra spaces or missing characters break it
• Not waiting for DNS propagation: Allow 24-48 hours for DNS changes to propagate before testing

DMARC (Domain-based Message Authentication, Reporting & Conformance)

What it does: Tells receiving servers what to do with emails that fail SPF or DKIM checks. It also provides reporting so you can monitor authentication failures.

How it works: You add a TXT record specifying your DMARC policy. Receiving servers check this policy after evaluating SPF and DKIM results.

Setup steps:

1. Start with a monitoring policy: v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com
2. Monitor reports for 2-4 weeks to identify legitimate senders that might fail authentication
3. Move to quarantine: v=DMARC1; p=quarantine; rua=mailto:dmarc@yourdomain.com
4. Eventually move to reject: v=DMARC1; p=reject; rua=mailto:dmarc@yourdomain.com

Common mistakes:

• Going straight to p=reject: This can block legitimate emails from services you forgot to authenticate
• Not monitoring reports: DMARC reports reveal authentication failures you might not otherwise discover
• Skipping DMARC entirely: Without DMARC, there is no policy telling servers how to handle failed authentication

Domain Warming: Building Reputation From Zero

New domains have zero sending reputation. Sending 100 cold emails from a brand-new domain on day one is a guaranteed ticket to the spam folder. Domain warming is the process of gradually building a positive sending reputation.

The Warming Schedule

Week 1-2: Send 5-10 emails per day to engaged contacts. These should be people who will open and reply — colleagues, friends, existing clients. The goal is to generate positive engagement signals.

Week 3: Increase to 15-20 emails per day. Begin mixing in warm prospects alongside your engaged contacts. Continue generating opens and replies.

Week 4: Increase to 30-40 per day. You can begin adding cold prospects in small batches alongside warm contacts.

Week 5+: Gradually scale to your target volume. Maximum 50-75 cold emails per domain per day. Do not exceed this threshold.

Warm-Up Tools and Techniques

Automated warm-up services: Tools like Instantly, Warmbox, or Mailreach send automated emails between warming accounts, generating opens and replies that build your domain reputation.

Manual warm-up: Send genuine emails to colleagues, partners, and existing contacts from your new domains. Ask them to reply. This is slower but creates more authentic engagement signals.

Apollo.io warm-up: Apollo.io includes built-in warm-up features that gradually increase sending volume and generate engagement automatically.

Monitoring Warm-Up Progress

Track these indicators during warming:

• Inbox placement rate: Use a seed test (send to test accounts across Gmail, Outlook, Yahoo) to verify emails land in the inbox, not spam
• Open rates: During warm-up, open rates should be 70%+ (since you are emailing engaged contacts)
• Bounce rate: Should be 0% during warm-up (you are emailing known-good addresses)
• Blacklist checks: Run weekly blacklist checks to ensure your domains and IPs are not listed

Sending Limits and Best Practices

Volume Limits

• Maximum 50-75 emails per domain per day for cold outbound
• Use multiple sending domains to distribute volume (3 domains × 50 emails = 150 emails/day)
• Use multiple email accounts per domain if needed (2 accounts × 25 emails each)

Sending Patterns

• Spread sends throughout the day: Do not blast 50 emails at 9:00 AM. Use Apollo.io's send scheduling to distribute emails between 8 AM and 5 PM.
• Send during business hours in the recipient's time zone
• Vary send times slightly: Perfectly regular sending patterns (exactly every 3 minutes) look automated. Add some natural variation.
• Avoid weekends: B2B emails sent on Saturday and Sunday have lower open rates and can trigger spam filters.

List Hygiene

• Verify all email addresses before adding to sequences. Apollo.io includes built-in email verification that checks addresses before sending.
• Remove hard bounces immediately: Hard bounces (invalid addresses) damage your sender reputation. Remove them from all lists.
• Monitor soft bounces: Soft bounces (temporary issues) should be retried but removed after 3 consecutive failures.
• Stay below 3% bounce rate: If your bounce rate exceeds 3%, pause sending and clean your list before resuming.
• Remove unsubscribes instantly: This is not just best practice — it is a legal requirement under GDPR and the Privacy and Electronic Communications Regulations.

The Apollo.io Advantage for Deliverability

One key reason we recommend Apollo.io for outbound sales is its built-in deliverability features:

Email verification: Before you add a prospect to a sequence, Apollo checks whether the email address is valid. This pre-send verification reduces bounce rates and protects your sender reputation.

Sending limits: Apollo enforces daily sending limits per account, preventing accidental over-sending.

Built-in warm-up: Apollo's warm-up feature automates the domain warming process.

Tracking and analytics: Real-time monitoring of open rates, bounce rates, and engagement signals helps you catch deliverability issues early.

Multiple mailbox support: Connect multiple sending accounts and Apollo distributes sends across them automatically.

Visit our Apollo.io partner page for preferred pricing and expert configuration support.

Monitoring and Maintenance

Weekly Monitoring Checklist

Email deliverability is not a one-time setup. It requires ongoing attention:

• Check open rates: A sudden drop (below 30%) suggests a deliverability issue
• Check bounce rates: Must stay below 3%
• Check spam complaint rates: Must stay below 0.1% (1 complaint per 1,000 emails)
• Run inbox placement tests: Send to seed accounts weekly
• Check blacklists: Use a monitoring service to check your domains and IPs

Monthly Maintenance

• Review DMARC reports: Look for authentication failures from legitimate services
• Audit sending domains: Ensure all DNS records are still correct
• Review and clean contact lists: Remove stale addresses and hard bounces
• Assess domain reputation: Use Google Postmaster Tools and similar services

Recovery: What to Do If You Are Already in Trouble

If your emails are consistently landing in spam, follow this recovery protocol:

Step 1: Stop All Cold Sending Immediately

Do not try to "send through" a deliverability problem. Every email you send with poor deliverability makes the problem worse.

Step 2: Diagnose the Problem

• Check DNS records: Verify SPF, DKIM, and DMARC are correctly configured using online checkers
• Check blacklists: Search your domains and sending IPs on major blacklist databases
• Check engagement metrics: Review open rates, bounce rates, and spam complaint rates for patterns
• Check content: Run your emails through spam scoring tools to identify trigger words or formatting issues

Step 3: Fix What You Find

• DNS issues: Correct misconfigurations and wait 24-48 hours for propagation
• Blacklisted: Submit removal requests to each blacklist. Most process requests within 24-72 hours
• Poor engagement: Your list quality or targeting needs improvement
• Content triggers: Rewrite emails to avoid spam trigger patterns

Step 4: Re-Warm Your Domains

After fixing the underlying issues, restart the warming process from the beginning. Send only to engaged contacts for 2 weeks before gradually reintroducing cold outreach.

Step 5: Consider New Domains

If your domain reputation is severely damaged (consistently landing in spam despite fixes), it may be faster to register new sending domains and start fresh. This is a last resort, but sometimes the fastest path to recovery.

The Complete Deliverability Checklist

Use this checklist when setting up email infrastructure for outbound sales:

• [ ] Primary domain never used for cold outbound
• [ ] 2-3 sending domains purchased and registered
• [ ] SPF records configured for all sending domains
• [ ] DKIM enabled for all email accounts on sending domains
• [ ] DMARC policy set (starting with p=none)
• [ ] Domain warm-up completed (minimum 2-4 weeks)
• [ ] Sending limits set (50-75 per domain per day)
• [ ] Email verification enabled in Apollo.io
• [ ] Send scheduling configured for business hours
• [ ] Weekly monitoring process established
• [ ] Bounce handling automated (remove hard bounces)
• [ ] Unsubscribe handling automated (immediate removal)

Build Your Email Infrastructure With MAVEN

Email deliverability setup is the first phase of every sales operating system we build. We handle the complete technical configuration — domains, DNS records, warming, and monitoring — so you can focus on messaging and strategy.

• Book a Virtual Coffee: Discuss your email infrastructure setup
• Apollo.io Partner Page: Access preferred pricing with built-in deliverability tools
• Cold Email Playbook: Download our complete outbound playbook
• Our Services: Explore our sales consultancy UK offerings
• ROI Calculator: Model the revenue impact of improved deliverability

---

MAVEN LB is a London sales consultancy helping B2B service firms build email infrastructure that reaches inboxes. Book a virtual coffee to set up your deliverability foundation.