DEV Community: Nilesh M

Why Your First Cold Email Through Amazon SES Didn't Send

Nilesh M — Wed, 15 Jul 2026 11:24:36 +0000

If you just set up Amazon SES to send cold email and your first test message never showed up, you didn't break anything. This happens to almost everyone. It's called the sandbox, and every new SES account starts inside it.

What the sandbox actually is

When you create a new Amazon SES account, AWS doesn't let you send freely right away. You're placed in a sandbox with three rules:

You can only send to email addresses you've manually verified in the SES console. You're capped at 200 messages in a 24 hour period. You can send at most 1 message per second.

For cold email, the verified addresses rule is the one that trips people up. Cold email means reaching people who haven't given you their address ahead of time. But the sandbox only lets you send to addresses you've already added and confirmed yourself. So your first real cold email, to a prospect who never verified anything with AWS, just won't go out. No dramatic error, it simply won't deliver.

Why AWS does this

This isn't AWS being difficult. New accounts with no sending history are the most common source of spam on any email platform. The sandbox is AWS's way of making sure new accounts prove they send legitimate mail with real bounce and complaint handling before they're allowed to send widely. It protects their own sending reputation, which in turn protects everyone using SES.

How to get out of it

You request production access from the SES console. Go to your Account Dashboard, then "Get set up," then "Request production access." AWS asks for a few specific things:

Your mail type, marketing or transactional. For cold email, marketing is usually the right answer. A website URL, so AWS can see that what you're describing matches what your site actually does. Up to four additional contact emails. Your preferred contact language. A checkbox confirming you only send to people who've asked to hear from you, and that you have a process for handling bounces and complaints.

AWS says they typically respond within 24 hours. Sometimes they'll ask a follow up question before approving, which adds time.

One thing worth doing before you even request access: verify a full domain, not just a single email address. AWS calls this out directly as something that helps your request move faster.

What changes once you're approved

The verified recipients restriction goes away, so you can send to anyone. The 200 message and 1 per second caps lift too, though your new limits start modest and rise automatically as you build a clean sending history with low bounces and complaints. You can request a higher limit directly once you need it.

One thing that doesn't change: you still have to verify whatever address or domain you're sending from. Production access removes the restriction on who you can send to, not the requirement to prove you own what you're sending from.

If you want the full walkthrough, from creating the AWS account through your first real campaign, EmailQo has a step by step guide for setting up cold email on Amazon SES.

Your Warmup Finished. Your Emails Still Went to Spam. Here's Why.

Nilesh M — Fri, 03 Jul 2026 07:42:20 +0000

You did everything right.

You set up a new sending domain. You ran warmup for three weeks. Green scores across the board. Then you launched your campaign and half your emails landed in spam.

This is the most common cold email story in 2026. And the platforms you're using don't want to talk about it.

Warmup is not deliverability. It's a starting point.

Warmup builds reputation before you send. It tells inbox providers that your domain has been around, sends reasonable volumes, and gets replies. That is genuinely useful.

But warmup ends when your campaign starts. After that, you're on your own.

Nobody checks whether your DMARC record is still valid before send number 47. Nobody flags that your tracking domain quietly got blacklisted while you were building your sequence. Nobody scans your new template for the spam trigger words that Outlook's enterprise filters reject at scale.

That is what most cold email tools skip. They warm up your domain, hand you a green badge, and walk away.

The gap between "warmup complete" and "emails landing in inbox" is where most cold email campaigns go to die.

What actually causes cold emails to go to spam in 2026

Here are the real reasons, not the vague ones:

1. **Broken authentication records
**
SPF, DKIM, and DMARC must be configured correctly before you send a single cold email. If your SPF record has too many DNS lookups, it fails silently. If your DKIM selector doesn't match what your email provider set up, every email fails authentication. If your DMARC policy is missing or set to p=none, Gmail and Outlook apply their own judgment to your mail, and that judgment is not kind to cold outreach.

These records break mid-campaign. A DNS change for something completely unrelated can break your SPF without you noticing. Warmup does not catch this because it happened before warmup started, or it happens while your campaign is already running.

Check your SPF, DKIM, and DMARC records free here

2. Shared IP contamination

Most cold email platforms send through shared infrastructure. Your emails leave from the same IP addresses as other users on that platform. When a different user runs a bad campaign, generates spam complaints, or hits spam traps, the IP reputation drops for everyone on that pool.

You did nothing wrong. Another sender did. Your emails still land in spam.

This is not a hypothetical. The majority of deliverability complaints from cold email senders trace back to shared IP problems they had no part in causing. The only real fix is sending through infrastructure you control, not infrastructure you share with strangers.

3. Spam trigger words in your copy

Enterprise email filters at companies running Microsoft 365 and Google Workspace use content-based filtering. Certain words and phrases trigger these filters regardless of your sender reputation. "Free," "guaranteed," "limited time," "act now," and specific financial language get flagged.

Most senders find out by watching open rates drop. By then, some portion of your reputation is already spent on emails that never should have gone out.

4. Blacklisted tracking domains

If you use a custom tracking domain to monitor opens and clicks, that domain has its own reputation. Tracking domains get blacklisted. When yours does, every email containing your tracking link becomes a deliverability problem, regardless of how clean your sending domain is.

Most cold email tools do not check your tracking domain health. They assume it's fine.

5. Domain age and sending pattern inconsistency

Even after warmup, sudden changes in sending volume or target audience signal unusual behavior to inbox providers. A domain that sent 50 emails per day during warmup and then jumps to 500 on day one of a live campaign looks suspicious. Inbox providers notice this.

Cold email inbox placement rate drops most often not at launch, but 3 to 6 weeks in, when warmup stops being the active variable and actual sending behavior takes over.

Why founders get hit hardest

Solo founders doing outbound face a specific trap. They set up sending, run warmup, and launch. Two things go wrong fast.

First, the authentication is usually 80% correct. The 20% that's wrong is silent until it causes problems.

Second, when the first campaign tanks, they assume it's the copy. They rewrite subject lines, change the offer, try different CTAs. The problem is never the copy when your cold emails are going to spam. The problem is infrastructure.

Copy changes don't fix infrastructure problems. Every week spent optimizing subject lines around a broken foundation is a week of pipeline lost.

If you're a founder running cold email through your own Gmail or Outlook account, you already have a head start. Your reputation is yours alone. Nobody else's bad campaign can contaminate it. But that only helps if authentication is correct and you're checking what happens before each send, not just at setup.

Why SDR teams see deliverability work and then stop working

The pattern is consistent. An SDR team sets up correctly, runs warmup, and the first month performs well. By month three, inbox placement has dropped without anything obvious changing.

What happened: warmup stopped being the active variable. Sender reputation is now determined by actual sending behavior. List quality, bounce rates, spam complaint rates, and content patterns take over. If the list has stale contacts, complaint rates creep up. If templates have gotten lazier, content filters catch them more. If sending volume increased without adding inboxes, per-inbox volume gets too high.

Most sales engagement tools show open rates and reply rates. They don't show inbox placement rate.

You can have a 30% open rate from 50% of your emails and have zero visibility into the 50% that went straight to spam. The numbers look okay. The pipeline doesn't add up. That's the cold email deliverability black hole.

The fix is not more warmup. It's knowing what happens to each send before you send it.

Why agencies have a compounding problem

Agencies running cold email for multiple clients have all the same infrastructure problems, multiplied by client count.

The specific agency risk: one client's bad list contaminates shared infrastructure. One client's sloppy template triggers content filters for campaigns running on the same pool. One client's complaint rate affects sending reputation that other clients depend on.

The correct architecture for agencies is client isolation. Each client should send through their own account, with their own reputation, and their own monitoring. Problems in one account stay in that account. They don't spread to other clients.

Most platforms don't work this way. They pool infrastructure and call it managed deliverability.

If you run cold email campaigns for clients and each client connects their own Gmail, Outlook, or AWS SES account, you have true isolation. The only way to protect client A from client B's mistakes is to keep their sending infrastructure completely separate.

What pre-send checks actually do

The fix for all of this is not more warmup. It's validating what's actually wrong before each send, not once during setup.

Pre-send checks are what most cold email platforms skip. Before a campaign goes out, a real deliverability check should:

Validate that SPF, DKIM, and DMARC are correctly configured and passing, not just present
Check blacklist status for both the sending domain and any tracking domains in the email
Scan email body for spam trigger words against content filters used by major enterprise inbox providers
Simulate how the email would be treated by Outlook, Gmail, and other providers before a real user sees it

If any of these fail, you fix before sending. Not after watching your open rate drop for two weeks.

This is different from warmup. Warmup happens once. Pre-send checks happen every time. They catch things warmup never could: a DNS change that broke SPF mid-campaign, a spam trigger word that appeared in a new template variant, a tracking domain that got listed overnight.

See how EmailQo runs pre-send checks before every campaign

The infrastructure problem explained simply

Think of your email sender reputation as a bank account.

Warmup deposits money into that account before you start spending. Good sending behavior adds to it. Bad sending behavior withdraws from it. Bounces, spam complaints, low engagement, and authentication failures are all withdrawals.

Most tools help you make the initial deposit. Nobody watches the ongoing balance. Nobody alerts you when a transaction is about to overdraft the account.

Pre-send checks are the alert system. They flag the transaction before it goes through, not after the account is in deficit.

The shared infrastructure problem is separate but related. With shared infrastructure, your bank account is connected to hundreds of other accounts. When they overdraft, it affects yours. Sending through your own infrastructure, whether that's your own Gmail, Outlook, Zoho, or AWS SES account, keeps your account separate. Your balance reflects only your own sending behavior.

This is why sending through your own accounts is not just a pricing or control preference. It is a fundamental deliverability decision.

How to actually fix cold email deliverability: the honest order of operations

Step 1: Fix authentication before anything else

Check that SPF, DKIM, and DMARC are all configured correctly for your sending domain. Use a free DMARC checker to verify each record is passing, not just present. If DMARC is set to p=none, it is doing nothing. Move toward quarantine once you've confirmed SPF and DKIM are passing consistently.

Step 2: Separate your sending from your primary domain

Never send cold outreach from the domain your company email runs on. Set up a separate sending domain, configure authentication on it, warm it up, and keep campaign traffic isolated. If it gets damaged, your main business email is untouched.

Step 3: Check your tracking domain

Verify that your tracking domain is not on any major blocklist. This is easy to miss and consistently causes deliverability problems that look impossible to diagnose.

Step 4: Run pre-send checks before every campaign

Before any campaign goes live, validate that authentication is passing, check blacklist status, and scan content against spam filters. Catch problems before they affect real sends.

Step 5: Monitor ongoing, not just at setup

Cold email deliverability is not a one-time setup task. DNS records break. Tracking domains get listed. Sending patterns change. The tools that show you what's happening between campaigns are the ones that keep you out of trouble.

Step 6: Send through infrastructure you control

Connect your actual Gmail, Outlook, Zoho, or AWS SES account for sending. Your reputation stays yours. Another sender's problems don't become your problems. If something goes wrong, you can diagnose it because the only variable is your own behavior.

If you're running cold email through AWS SES, the setup is more involved than Gmail but the reputation isolation is the strongest available. See the full AWS SES cold email setup guide here.

The bottom line

Warmup is table stakes in 2026. Every serious cold email platform offers it. That means warmup alone is no longer a differentiator. It's just the minimum to not be immediately filtered.

The tools that actually improve results go further: they check what's wrong before each send, they let you send through your own accounts, and they give you visibility into what's happening to your reputation between campaigns.

The reason most cold email campaigns underperform in 2026 has nothing to do with subject lines or offer quality. The emails are not reaching the inbox in the first place.

Fixing the infrastructure fixes the results. Rewriting copy around a broken foundation just wastes more time and more domain reputation.

If your warmup finished and your emails are still going to spam, the problem is not your copy.

EmailQo runs pre-send checks on every campaign including SPF, DKIM, DMARC validation, blacklist monitoring, spam trigger scanning, and enterprise filter simulation before anything goes out. It connects to your own Gmail, Outlook, Zoho, or AWS SES account so your reputation is isolated from every other sender. Start a free trial, no credit card required

The Deliverability Black Box: Why Your Warmup Score Says "Healthy" While Your Emails Sit in Spam

Nilesh M — Fri, 19 Jun 2026 07:18:26 +0000

If you run outbound for a living, you've lived this exact moment.

Your warmup dashboard shows green. Your sender score looks fine. Whatever platform you're using tells you everything is healthy. Then you check a seed inbox or a friend's Gmail and your email is sitting in the spam folder anyway.

Nobody tells you why. There's no alert. No root cause. Just a healthy looking dashboard and a campaign that quietly failed.

This is one of the most common frustrations among SDRs, founders, and agencies running cold outreach today, regardless of which tool sits behind their sequences. It shows up so often in practitioner communities that it has a name now: the deliverability black box.

Why this keeps happening

It's not that the popular platforms are badly built. Tools like Instantly, Smartlead, Lemlist, and dozens of others have genuinely useful sequencing, warmup, and reporting features, and plenty of teams run them successfully. The issue is structural, not a flaw in any one product.

Warmup and pre-send verification are two different jobs, and most platforms only do one of them well.

Warmup is a slow, background process. It sends low volume engagement emails over weeks to build a sending history with Gmail, Outlook, and other providers. That's genuinely valuable, but it's a lagging indicator. It tells you about your reputation over time. It says nothing about whether the specific email you're about to send right now has a broken DKIM record, a DMARC policy that will reject it, or a subject line that trips a spam filter today.

Those are two separate problems, and conflating them is where the black box comes from. A dashboard showing "warmup: healthy" is answering a different question than "will this exact campaign land in the inbox."

This is true whether you're sending through a dedicated sequencing platform, connecting your own Gmail and Outlook accounts directly, or running campaigns through Amazon SES. The infrastructure changes. The blind spot doesn't, unless something is specifically built to check for it.

The checklist that actually closes the gap

Whatever tool you're using, here's what separates teams who consistently land in the inbox from teams stuck guessing.

Authentication, checked live, not just set once

SPF, DKIM, and DMARC need to be verified before every meaningful send, not just configured once at setup. DNS records change, TTLs expire, and a record that passed verification three months ago can silently break.

A real pre-send scan on content

Spam trigger words, excessive punctuation, image to text ratio, and link count all get scored by enterprise filters before a human ever opens the email. Catching this before sending costs nothing. Catching it after a 2,000 contact send has already gone out costs you the whole list.

Blacklist status checked within 24 hours of sending, not once at setup

A clean domain can land on Spamhaus or Barracuda overnight. Checking once when you configure a sending domain and never again is how teams get blindsided.

Bounce and complaint thresholds tracked per campaign, not just in aggregate

Most platforms show an overall bounce rate. The number that actually predicts trouble is the rate on your most recent campaign specifically. A clean 90-day average can hide a single bad send that's already damaging your reputation right now.

Reply detection that pauses follow-ups instantly

Sending a scheduled follow-up to someone who already replied is one of the fastest ways to generate a spam complaint. If your sequence doesn't pause the moment a reply lands, that's a deliverability risk hiding inside your own automation.

Warmup that runs continuously, not just at launch

Reputation isn't something you build once. Background warmup that continues quietly between active campaigns keeps your sending history positive during the gaps, which matters more than most people realize.

Where the category is heading

The honest pattern across the cold email space right now is that sequencing and infrastructure verification are slowly converging. Some teams run a dedicated warmup or verification layer alongside whatever sequencing tool they already use, specifically because a warmup score alone wasn't giving them the full picture of what was actually happening in the inbox.

That convergence is also what a newer set of deliverability-first tools is built around, treating pre-send verification as the core feature rather than something bolted on after the fact. EmailQo is one example, built around checking a campaign against live DNS, blacklist, and content signals immediately before it sends, on top of your own Gmail, Outlook, or Amazon SES account.

Whatever tool you land on, you don't need to take any dashboard's word for whether your setup is actually working. A few free checks take less than five minutes and tell you more than a warmup score ever will.

Run your domain through a free infrastructure grader to see your SPF, DKIM, DMARC, and MX status scored out of 100.

Check your actual DMARC alignment and confirm whether you're still sitting on monitoring mode without realizing it.

Run a draft subject line and body through a spam score checker before your next send, not after.

None of these require switching tools or signing up for anything. They just answer the one question every dashboard seems to dance around: is this email actually going to reach the inbox, right now, as written.

That's the question worth answering before you hit send, not after your reply rate quietly drops and you start rewriting subject lines that were never the problem in the first place.

Your Emails Are Not Landing in Enterprise Inboxes. Here’s Why (And What to Actually Do About It)

Nilesh M — Wed, 03 Jun 2026 05:09:46 +0000

Let’s skip the fluff.

You set up SPF, DKIM, and DMARC. You kept your complaint rate clean. You ran warmup for three weeks. You checked the boxes. And your emails are still showing up in spam for half your prospects.

Welcome to email deliverability in 2026, where the rules changed faster than most people noticed and doing the basics right is no longer enough.

This is not a guide for beginners. This is for people already doing outreach who are watching their inbox placement slowly die and can’t figure out why.

What Actually Changed in the Last 12 Months
Two things happened that broke a lot of sending setups that used to work fine.

Gmail got serious about enforcement.

February 2024 was the warning. Google told senders to get their authentication in order or face consequences. Most people updated their records, ticked the compliance box, and moved on. What they didn’t notice was that in November 2025, Google quietly escalated from soft deferrals to hard rejections. That means your emails don’t just land in spam anymore. They don’t land at all. A 5xx rejection from Gmail is permanent. The message is gone.

The gap between senders who sailed through and senders who got wrecked wasn’t just authentication. It was engagement history. Google’s AI-driven filtering now weighs how recipients have historically interacted with your domain. A clean SPF record means nothing if your last three campaigns generated low opens and zero replies.

Microsoft Outlook became a nightmare.

Outlook’s inbox placement dropped from 77.43% in early 2024 to 50.70% on Exchange and 26.77% on consumer Outlook by Q1 2025. Those are brutal numbers. One in four emails reaching consumer Outlook addresses is landing in junk even from senders with perfect authentication.

Why? Microsoft rolled out Exchange Online Protection updates that added tenant-level admin controls on top of their SmartScreen filter. Every enterprise IT department running Microsoft 365 can configure custom blocklists and content rules. The same email can land in the inbox at one company and get quarantined as “mass messaging” at another, from the same sending IP.

There is no single fix for M365. Every inbox is configured differently. What you can control is how you look going in.

The Thing Most People Still Get Wrong
The most common deliverability mistake in 2026 is treating authentication as a destination rather than a starting point.

You set up DMARC, you move on. But DMARC adoption has jumped massively over the last two years. Domains with valid DMARC records went from 523,000 in 2023 to nearly 938,000 by early 2026. The thing is, only about 412,000 of those records actually enforce anything. More than half are sitting on p=none, which is monitoring mode. You're watching the problem, not stopping it.

Enterprise spam filters know this. A p=none record tells their system you're still figuring it out. A p=quarantine or p=reject tells them you're serious about your domain. It's a trust signal, not just a technical setting.

The other thing people get wrong is thinking shared infrastructure is fine as long as their own campaigns are clean. It’s not.

When you send through a shared IP pool, your deliverability depends partly on what every other sender on that pool is doing. One neighbor with a dirty list or a spammy campaign raises complaint rates for everyone on the same IP range. You absorb that penalty even if your own setup is immaculate. Enterprise filters that query Spamhaus or Barracuda don’t care that you personally followed the rules. They see the IP.

What Enterprise Filters Are Actually Evaluating
Here’s a practical breakdown of how your email gets scored when it hits an enterprise inbox in 2026.

Authentication alignment, not just authentication passing. Your SPF needs to pass on the envelope-from domain, not just on Amazon’s domain. Your DKIM signature needs to be from your domain, not your ESP’s. DMARC alignment fails when those don’t match. This is the most common silent deliverability killer for people using sending tools without proper MAIL FROM configuration.

Sending behavior patterns. Consistent daily sends beat sporadic bursts every time. Microsoft’s filters flag domains that send 500 emails one day and nothing for a week. Enterprise filters learn the normal sending pattern for a domain over time. Deviations read as suspicious activity.

Content against enterprise filter models. Gmail’s consumer filters and Microsoft Defender use different scoring models. Something that passes Gmail’s content check can get quarantined by Defender. There’s no single spam word list you can avoid and be safe. Enterprise filters run ML models trained on behavior and sender history, not just word matching.

Engagement signals from prior sends. Your last 30–90 days of sending behavior with each provider affects how your next campaign gets scored. Low opens, high deletions without reading, and spam clicks build a negative prior that takes months to clear.

Recipient-level signals. Individual Outlook recipients who previously marked your domain as junk will not receive your mail regardless of your domain’s overall reputation. This is invisible to you. You can have a Sender Score of 90 and still hit junk for specific contacts at specific companies.

How to Actually Navigate Enterprise Inboxes
None of this is magic. It’s operational hygiene treated with the same seriousness as conversion rate optimization.

Stop sending before you’ve checked your authentication stack. Not “I set it up six months ago,” but actually run your domain through a live check right now. DMARC records can break silently. A SPF record can accumulate too many DNS lookups over time as you add new sending tools. A DKIM selector can expire or get misconfigured during an account migration. These things fail quietly while your campaign stats show normal bounce rates.

Before your next send, run a free check on your domain’s SPF record, DKIM signature, and DMARC alignment. Tools like EmailQo’s DMARC checker will show you exactly what enterprise filters see when they look up your domain. Not what you think is configured. What’s actually live in DNS right now.

Get off p=none. If your DMARC is still in monitoring mode, move it. The process is: check your aggregate reports for two weeks and confirm all legitimate sending sources are passing. Then move to p=quarantine. Two more weeks of reports confirming nothing legitimate is being caught. Then p=reject. This is a four-week process that most people never finish.

Build sending history on providers you own. If you’re sending cold outreach through shared pools, you’re building reputation on infrastructure you don’t control. When you leave the platform or the platform has a problem, that history is gone. Sending through your own Gmail, Outlook, or AWS SES account means the reputation you build belongs to your domain, not to whoever owns the sending pool.

Treat Outlook differently from Gmail. They use different scoring systems. An email that passes Gmail’s content filter can fail Defender’s ML model. The single most useful thing you can do for Outlook placement is end your outreach emails with a question. Getting a reply is one of the strongest positive signals you can send to Microsoft’s filters. A conversation is happening. That’s what they’re looking for.

Enroll in Microsoft’s SNDS and JMRP. Most people have never done this. SNDS shows you sending data for your IP addresses including spam trap hits and complaint rates as Microsoft sees them. JMRP sends you copies of emails Outlook.com users marked as junk. If you’re not enrolled, you’re flying blind on a provider that controls 25–30% of enterprise inboxes worldwide.

Watch your volume consistency. A domain that sends 40–50 emails per day, consistently, will outperform one that sends 500 on campaign launch day and nothing for the next two weeks. This is not intuition. Enterprise filters build expectation models for domain sending patterns. Consistency is a trust signal.

The Infrastructure Question Nobody Wants to Answer
Here’s the uncomfortable reality of 2026 deliverability.

The B2B SaaS sector sits at 92% median inbox placement. That’s 6 points above the overall average. The difference isn’t better copy or smarter subject lines. It’s structural. B2B SaaS senders tend to use opt-in friction, which means cleaner lists. They tend to run on dedicated or owned infrastructure. And they monitor deliverability as a first-class metric.

Most outreach teams don’t. They watch open rates. By the time open rates drop, the reputation damage is usually 2–4 weeks old.

The metric that tells you the problem is coming is complaint rate. AWS SES enforces a 0.1% complaint threshold. Google publicly flags domains generating elevated complaints. Microsoft’s filters respond faster than either. If your complaint rate is climbing, you have a week or two before it shows up in your inbox placement numbers.

You cannot watch this metric if you don’t have access to it. Most shared sending platforms don’t surface complaint rate per campaign. They show you the aggregate. That’s too late.

Owning your sending infrastructure, even at Gmail or Outlook level, gives you visibility into your own reputation signals. Sending through AWS SES and processing bounce and complaint SNS notifications gives you real-time complaint rate data per campaign. You know something is wrong on day one, not week three.

The Checklist Before Your Next Campaign
Here’s what a technically sound send looks like in 2026:

Authentication: SPF passes on your sending domain (not your ESP’s). DKIM signed with your domain. DMARC at p=quarantine minimum, with rua= set to an inbox you actually read. Run a live check before sending, not once at setup. EmailQo's free email infrastructure grader gives you a 100-point score across all four authentication signals in one place, no signup needed.

Domain health: Your sending domain is not listed on Spamhaus ZEN, Barracuda, or SURBL. Check this within 24 hours of sending, not once at setup. IP and domain reputation can change overnight.

Content: No spam trigger stacking in the subject line. One link maximum in cold outreach. Text-heavy over HTML-heavy. Specific CTA with a yes or no answer, not a vague “let me know your thoughts.”

List quality: Verified within 30 days. Suppression list applied from all previous campaigns. Hard bounces from prior sends excluded. Catch-all domains treated separately.

Volume: Daily send count per account within the established pattern for that account’s age and history. No burst sending.

Post-send monitoring: Bounce and complaint data processed within 24 hours. Hard bounces suppressed globally immediately.

One More Thing
The deliverability gap in 2026 is not closing. It’s widening.

Senders above Sender Score 90 are pulling further ahead every quarter. Senders below a certain threshold are staying there for 18 months or more. Reputation has become durable in both directions.

The teams that are winning inbox placement in enterprise accounts right now are not doing anything exotic. They’re doing the basics consistently and they’re treating deliverability as a metric they check before every campaign, not a problem they fix after something breaks.

That’s the whole game.

Nilesh M has 15+ years in B2B SaaS marketing. He built EmailQo to give senders pre-send deliverability checks on every campaign, free tools to diagnose authentication problems, and sending infrastructure they actually own.

Deliverability-First Email Marketing: Why Your Strategy is Backwards

Nilesh M — Sat, 18 Apr 2026 12:26:15 +0000

Your email marketing strategy is built on a lie.

Most businesses focus on crafting perfect subject lines, A/B testing send times, and optimizing open rates. But none of that matters if your emails never reach inboxes.

Here's the uncomfortable truth: 20% of permission-based emails never make it to the recipient. Your beautifully designed campaigns are sitting in spam folders, invisible to your audience.

What Deliverability-First Actually Means

Traditional email marketing asks: "How do we get more opens and clicks?"
Deliverability-first marketing asks: "How do we ensure every email reaches its destination first?"
This fundamental shift changes everything about how you approach email marketing. Instead of optimizing for engagement after delivery, you optimize for delivery before engagement.

Why Most Email Marketing Fails at Deliverability

The biggest mistake businesses make is treating deliverability as an afterthought. They design campaigns, write copy, segment lists, and then hope emails get delivered.

This backwards approach creates predictable problems:

Shared IP reputation issues. When you send through platforms like Mailchimp or Constant Contact, you share IP addresses with thousands of other senders. One bad sender can damage everyone's reputation.

Poor authentication setup. Most businesses never properly configure SPF, DKIM, and DMARC records. This makes their emails look suspicious to inbox providers.

No warmup process. Sending large volumes immediately from a new domain or IP triggers spam filters. Proper warmup takes weeks, not hours.

Generic content triggers. Certain words, phrases, and formatting patterns automatically flag emails as promotional content.

The Deliverability-First Framework

Here's how to restructure your email marketing around deliverability:

Step 1: Infrastructure First
Set up dedicated sending domains separate from your main business domain. Configure all authentication records properly. Use your own sending infrastructure instead of shared platforms when possible.

Step 2: Reputation Building
Start with small volumes and gradually increase. Send to your most engaged subscribers first. Monitor bounce rates and spam complaints religiously.

Step 3: Content Optimization
Write emails that pass spam filters before optimizing for human readers. Test every campaign through spam checkers. Avoid promotional language patterns.

Step 4: List Hygiene
Remove inactive subscribers regularly. Verify email addresses before adding them to lists. Track engagement patterns and segment accordingly.

Real Impact of Deliverability-First Thinking
Companies that prioritize deliverability see dramatic improvements:
TechCorp switched from Mailchimp to dedicated infrastructure and saw inbox placement jump from 68% to 94%. Same content, same audience, better delivery.
SaaS startup CloudBase implemented proper warmup and authentication. Their trial signup emails went from 40% spam rate to 2% spam rate in 30 days.

Tools for Deliverability-First Marketing

Email authentication checkers. Verify your SPF, DKIM, and DMARC setup is correct. Tools like EmailQo's free email grader can identify configuration issues before they hurt deliverability.

Spam testing tools. Check every campaign before sending to identify potential issues. EmailQo includes built-in spam scoring that catches problems other platforms miss.
Deliverability monitoring. Track where your emails land across different inbox providers.
Dedicated sending platforms. Use infrastructure designed for deliverability, not just ease of use. Platforms like EmailQo that offer AWS SES integration with automatic warmup give you dedicated infrastructure without the complexity.

The Bottom Line
Perfect subject lines mean nothing in spam folders. Brilliant copy is worthless if nobody sees it.

Deliverability-first email marketing flips the script. Ensure delivery first, optimize engagement second.

Tools that prioritize deliverability over flashy features help businesses focus on what actually moves the needle: getting emails into inboxes.

I built a free email infrastructure grader that scores any domain out of 100

Nilesh M — Fri, 10 Apr 2026 06:39:33 +0000

I kept running into the same problem. Every time I needed to check a domain's email setup, I had to use 4 different tools. One for SPF. One for DKIM. One for DMARC. One for spam risk.

So I built a tool that does all four checks at once and gives you a single score out of 100.

Try it here: emailqo.com/email-grader

Enter any domain. It checks:

SPF record (is it valid, does it use hard fail)
DKIM (checks common selectors and AWS SES CNAME records)
DMARC (policy level, reporting setup)
Mail server (MX records present and responding)

Each check is worth 25 points. You get a color coded score: green for 80+, amber for 50 to 79, red for below 50.

Why I built it:

Gmail started rejecting unauthenticated email in November 2025. Microsoft followed in April 2026. Domains without proper SPF, DKIM, and DMARC are not just going to spam anymore. They are getting rejected entirely.

Most people do not realize their setup is broken until their campaigns fail. This tool catches the problems before that happens.

Stack: Next.js, Vercel, dns.google API for lookups. No backend database needed for the checks. Everything runs from DNS queries.

It is part of EmailQo, a cold email platform I am building that routes through the user's own AWS SES instead of shared sending pools. But the grader is completely free, no signup needed.

Would love feedback on what other checks to add. Thinking about adding blacklist checks and reverse DNS lookup next.