Email Deliverability: The Complete Developer Guide (2026)
Deliverability is the difference between your emails reaching the inbox and landing in spam. This guide covers everything developers need to know — from authentication to reputation management to monitoring.
What is email deliverability?
Email deliverability is the ability of an email to reach the recipient's inbox. It's not just about whether the email is delivered (accepted by the receiving server) — it's about whether it lands in the inbox vs the spam folder.
Mailbox providers (Gmail, Outlook, Yahoo) use complex algorithms to decide where to place incoming emails. These algorithms consider: sender authentication, IP reputation, domain reputation, engagement history, and content signals.
Email authentication: DKIM, SPF, DMARC
Authentication is the foundation of deliverability. Without proper authentication, your emails will be rejected or marked as spam by major mailbox providers.
SPF (Sender Policy Framework)
SPF is a DNS record that specifies which IP addresses are authorized to send email for your domain. When a receiving server gets an email claiming to be from your domain, it checks your SPF record to verify the sending IP is authorized.
DKIM (DomainKeys Identified Mail)
DKIM adds a cryptographic signature to your emails. The receiving server verifies the signature against a public key published in your DNS. This proves the email was sent by an authorized server and hasn't been tampered with in transit.
Double DKIM signing (as offered by Emitlo) adds two signatures: your domain key and the sending platform's key. This provides an additional layer of authentication that improves inbox placement with strict receivers.
DMARC (Domain-based Message Authentication)
DMARC builds on SPF and DKIM. It tells receiving servers what to do when an email fails authentication: none (monitor only), quarantine (spam folder), or reject (block entirely). DMARC also enables reporting — you receive reports from mailbox providers about authentication failures.
IP reputation and shared vs dedicated IPs
Your sending IP's reputation is one of the most important deliverability factors. Mailbox providers track the history of every IP — bounce rates, complaint rates, spam trap hits, and engagement rates.
Shared IPs
Most email providers use shared IP pools — multiple senders share the same IP addresses. The advantage: the IP is already warmed up and has an established reputation. The risk: other senders on the same IP can damage your deliverability if they send spam or have high bounce rates. Good providers (like Emitlo) carefully manage their shared IP pools to prevent this.
Dedicated IPs
A dedicated IP is used exclusively by your account. You have full control over the reputation — but you're also fully responsible for it. Dedicated IPs require warmup (gradually increasing volume over 4–8 weeks) and are only beneficial for senders with consistent high volume (50,000+ emails/month).
Domain reputation and warmup
In addition to IP reputation, mailbox providers track the reputation of your sending domain. A new domain has no reputation — you need to build it gradually by sending to engaged recipients and maintaining low bounce and complaint rates.
For new domains, start with low volume (a few hundred emails/day) and increase gradually over 2–4 weeks. Monitor bounce rates and complaint rates at each stage. If rates spike, slow down.
Bounce handling
Bounces occur when an email cannot be delivered. There are two types:
- Hard bounces — permanent failures (invalid address, domain doesn't exist). These addresses must be immediately added to your suppression list and never emailed again. A hard bounce rate above 2% will damage your reputation.
- Soft bounces — temporary failures (mailbox full, server temporarily unavailable). These should be retried with exponential backoff. After multiple consecutive soft bounces, treat the address as a hard bounce.
Emitlo processes bounces automatically via DSN parsing with VERP-encoded Return-Path for precise attribution. Hard bounces are added to your suppression list immediately.
Complaint handling and feedback loops
A complaint occurs when a recipient marks your email as spam. Major ISPs (Gmail, Yahoo, Outlook) offer Feedback Loop (FBL) services that notify senders when this happens.
A complaint rate above 0.1% is a warning sign. Above 0.3% will trigger deliverability problems. Recipients who complain must be immediately added to your suppression list.
Emitlo processes FBL notifications automatically and adds complainers to your suppression list without any manual intervention.
Content and spam filters
Spam filters analyze email content for signals that indicate spam. Key factors:
- ⚠Spam trigger words in subject lines and body
- ⚠Excessive use of capital letters or exclamation marks
- ⚠Image-to-text ratio (too many images, too little text)
- ⚠Broken HTML or missing plain-text version
- ⚠Links to domains with poor reputation
- ⚠Missing unsubscribe link (required by CAN-SPAM and GDPR)
- ⚠Mismatched From name and email address
Monitoring your deliverability
Key metrics to monitor:
Percentage of emails accepted by receiving servers
Percentage of delivered emails that land in inbox (not spam)
Percentage of emails that permanently fail
Percentage of recipients who mark as spam
Engagement signal used by mailbox providers
SpamAssassin score (lower is better)
Emitlo's real-time deliverability dashboard shows all of these metrics in one place, updated in real time as emails are sent and processed.
Common deliverability mistakes
✗ Not setting up DKIM, SPF, and DMARC
Fix: Use a provider that automates DNS setup (like Emitlo). Verify authentication with tools like MXToolbox.
✗ Sending to old or purchased lists
Fix: Only send to recipients who have explicitly opted in. Clean your list regularly with an email validation service.
✗ Not processing bounces and complaints
Fix: Use a provider that handles bounces and FBL notifications automatically. Never email hard-bounced addresses again.
✗ Sending from a new domain without warmup
Fix: Start with low volume and increase gradually over 2–4 weeks. Monitor bounce and complaint rates at each stage.
✗ Mixing transactional and marketing email on the same domain
Fix: Use separate subdomains (e.g., mail.yourdomain.com for transactional, news.yourdomain.com for marketing). A marketing complaint won't affect your transactional reputation.
Monitor your deliverability in real time with Emitlo
12,000 emails/month free (400/day) · Real-time dashboard · Double DKIM · No credit card