Email Deliverability Tips

Your inbox warm-up is training providers to distrust you. (I'm talking about warming up new sending domains / inboxes for cold or outbound email — not newsletters.) Agency owners tell me this weekly: → "We warmed it up for 3 weeks" → "Open rates still tanked" → "Outlook keeps flagging us" Their warm-up did exactly what it was designed to do. The problem? It was designed without real deliverability infrastructure. This is where tools like Warmy.io - Email channel. Reliable. come in — not as a growth hack, but as the control layer between your domains and inbox providers. Reality #1: Volume ramp ≠ reputation engineering → Day 1: Send 10 → Day 7: Send 25 → Day 14: Send 50 → Day 21: Still flagged That's not warm-up. That's guessing with your domain. Reality #2: Generic warm-up creates generic signals Most inbox warm-up fails because it produces: → Shallow engagement patterns providers learn to discount → Repetitive behavior that looks automated at scale → No provider-specific logic (Gmail ≠ Outlook ≠ Yahoo) → No monitoring. No alerts. No guardrails. Inbox providers don't reward activity. They reward believable, consistent behavior over time. Reality #3: Authentication ≠ inbox placement I've audited sending domains with: → SPF / DKIM / DMARC valid ✓ → Domain health marked "high" ✓ → Inbox placement above 90% ✓ Still landing in spam. The difference between inboxes that recover and inboxes that burn? Controls. Monitoring. Observability. Not copy. Not timing. Not subject lines. What real inbox warm-up infrastructure looks like (how I use Warmy): → Provider-weighted logic (Gmail tolerance ≠ Outlook tolerance) → Continuous domain + inbox reputation monitoring (catches drift before damage) → Inbox placement testing by provider (not averages) → Dynamic warm-up control (auto slow-down when signals dip) → Real-time alerts (before domains get burned) → Seed lists designed for realistic engagement Cold email doesn't fail at send time. It fails weeks earlier — during warm-up. The fix isn't "write better emails." The fix is treating deliverability like infrastructure. 🔗 Try it yourself 👉 Explore Warmy here: https://lnkd.in/gGZzMhv6 Free 7-day trial — see inbox placement by provider before you scale outbound.

I’ve talked to 4-5 SDR Leaders that have gotten their email domains TORCHED in the last 2 months. Here’s the thing all outbound teams need to understand about deliverability: Email deliverability is a “death by a thousands paper cuts” type of situation. Stop stacking paper cuts and do these 9 things: 1️⃣ Set up secondary domains If you are still cold emailing off your primary email domain you may be in big trouble. This is crucial. Using something like Maildoso makes getting these domains and the whole technical setup super fast... more on that below. The last thing you want, especially if you DONT have a reputable domain like Salesforce(.)com is to burn your orgs primary domain. This doesn’t just affect your sales team. You don’t need your CSMS and CEO landing in SPAM. 2️⃣ Set up your DNS (DMARC, SPF & DKIM) records for ALL of your domains To skip the manual DNS headache... Maildoso automates this setup. I just set up 2 new domains in literally 1 minute with them last week. Right now we can only set up 2 mailboxes per rep in Outreach. Going to be adding a Smartlead integration soon in Common Room to run higher volume experiments based on various intent signals and double down on the ones that work with human SDRs. 3️⃣ Secondary domains should link to your primary You want to make sure your prospects are being directed to your actual company domain if they are curious and click. 4️⃣ Email Warmup - Domains should be “warmed up” for ~14 days before cold emailing Send at least 20-30 warm up emails per day per email account, with a 40% reply rate. This builds your domain reputation. 5️⃣ Email Volume - Build this over time. Start with 5-10 emails a day per account and do NOT send more than 30 emails per day per email account 6️⃣ Keep your email signature plain text. No Links. No images. No calendar links…at all Add your address in your signature and make sure you put a picture in your Outlook or Gmail profile. 7️⃣ Vary your cold email copy (i.e. SPINTAX). Sending the same template to every prospect signals that you are a spammer. Customize your first step email. For emails further in your sequence, use Spintax. Use alternate phrases “Hi, Hey, Hello”. New age sequencers do this automatically. 8️⃣ Understand that your domain gets TORCHED when people mark your email as spam. Good and relevant copy matter. 9️⃣ Constantly monitor your email deliverability. Deliverability varies across Outlook and Google servers. Get a platform that helps you land in ALL inboxes. Again, Maildoso makes this super easy...  they have daily reputation monitoring built right in so you catch issues fast. They average 98%+ inbox placement - wild. Maintaining good deliverability over time is key in the success of outbound. What would the email deliverability experts add here? #outbound #coldemail #deliverability

Myth: “Your deliverability is a one-time setup.” I learned that late. It cost us pipeline. We had SPF, DKIM, and DMARC in place. The copy was solid. The leads were qualified. But replies were silent. We tweaked subject lines.  Rewrote the CTA. Changed the offer.  Still nothing. The real issue? The emails were landing in Promotions. Some went to Spam. And we had no visibility. That’s when we realized deliverability isn't a checkbox. It's something you monitor consistently. Inbox placement changes. Domain reputation shifts. Even one bad step can tank performance. That’s why we now use Inbox Radar by Saleshandy. → Recurring Tests  Automatically track inbox placement over time. → Manual Tests  Run quick checks before sending a sequence. → External Tests  Check emails sent from Gmail or Outlook with a test ID. It shows where your emails land: Primary, Promotions, or Spam. And what needs fixing if they don’t land right. We don’t guess anymore. We check. We fix. Then we send. If you're running cold outreach, test before you launch. It’s one small habit that protects your entire pipeline. Using anything to monitor your deliverability yet?

How to setup the Domain Authentication in Marketing Cloud Next Want to keep your emails out of the spam folder and build trust with your brand? Domain authentication is non-negotiable. This guide walks through the complete process of setting up an authenticated domain in Marketing Cloud Next - from understanding why we use subdomains (like e. apple . com) to protect your main domain's reputation, to the practical steps of configuring your subdomain in Salesforce and updating DNS records in your domain registrar like GoDaddy. I break down SPF, DKIM, and DMARC records with screenshots showing exactly what needs to go where. Email deliverability starts here. https://lnkd.in/gu54iij2

I thought great copy was the secret to cold email. Then I realized 80% of my emails were landing in spam. Here’s what we found: 1️⃣ Domain protection is the #1 lever for deliverability → Most teams burn their main domain without realising it. Once a domain is flagged, everything gets filtered (even normal emails). We run 100+ secondary domains to protect our brand and reduce risk. Tool stack: Google Workspace, Namecheap, Warmup tools Next step: Move every outbound sequence off your primary domain. 2️⃣ Safe volume beats high volume → Sending 500 emails/day from one domain is the fastest path to spam. Deliverability collapses instantly. We spread volume across hundreds of mailboxes and stay under 40/day for each. Impact: Fewer red flags, higher trust, better inbox placement. Next step: Audit how many sends each domain is doing right now. 3️⃣ Authentication is non-negotiable → SPF, DKIM, and DMARC are the foundation ESPs check before letting anything through. Without proper authentication, you look suspicious by default. Tools: dmarcian, Google Admin, Cloudflare Next step: Run a deliverability test and fix whatever shows up in red. 4️⃣ Warm-up → Most domains get burned because people start sending too early. ESPs need time to trust you. We warm each domain for two full weeks before sending anything. Why it works: Slow ramp-up = better deliverability. If you just bought a domain, don’t touch it for 14 days. 5️⃣ Natural variation reduces spam triggers → Sending the same message repeatedly creates patterns that ESPs flag. You need micro-variation to look human. We use subtle spintax + a few message versions per campaign. Tools: Instantly.ai, Smartlead Next step: Add small variations to your first lines and CTAs. 6️⃣ Clean tracking protects your domain reputation → Tracking links are an instant red flag. Most agencies don’t realize this. We use custom tracking domains or disable tracking entirely for key campaigns. Next step: Replace all generic tracking links. The results: → 500,000+ emails/month reaching real decision-makers → Higher inbox placement across every ESP → Predictable revenue for ColdIQ clients → Stable domain health across all mailboxes Deliverability isn’t the flashy part of outbound, but it’s the part everything else depends on. If you want our 7-day GTM deliverability setup (domains, warm-up, templates, monitoring tools)... drop me a message, happy to help.

 “Just send an email.” It looks like a one-liner: await sendEmail(to, subject, body); But in production, that line explodes into a full subsystem. Here’s what you actually end up building 👇 1. Reliability - never send inline Sending directly inside a request works… until latency spikes or the provider times out. You decouple it using a queue (Kafka, SQS, or RabbitMQ) -> a background worker processes sends. Each message gets a unique message_id for idempotency, retries use exponential backoff, and you persist status = pending/sent/failed. 2. Deliverability - “sent” != “delivered” Your API logs “200 OK,” but user didn't get it. You need webhooks from SES/SendGrid to capture delivered, bounced, or spam events. Those callbacks update your DB, mark bad addresses inactive, and feed a delivery analytics dashboard so you actually know what happened. 3 Spam filters & domain reputation You can write the best emails, and still end up in spam if you skip the basics: Set up SPF, DKIM, and DMARC. Warm up new domains gradually (start with low send volume). Use a dedicated sending domain (e.g., mailer.myapp.com) and separate IPs for transactional vs marketing. Without this, your whole app’s communication pipeline can get blacklisted overnight. 4 Personalization at scale You’re not just sending static HTML. Each email has dynamic placeholders ({{user.name}}, {{order.id}}), localized text, and sometimes attachments. You pre-render templates (Liquid/MJML), cache HTML in Redis, and bulk fetch user data to avoid DB thrash. At high volume, even template rendering becomes a performance bottleneck. 5 Observability & throttling At scale, email providers rate-limit you. You’ll need token-bucket throttling, multiple provider fallbacks, and metrics (Prometheus/Grafana) for latency and bounce trends. When one region hits its SES quota, your system should automatically failover to another provider without losing events. That “forgot password” email that lands in 2 seconds? It’s backed by queues, workers, webhooks, templates, cryptographic signatures, and deliverability tuning.

Most people want to enjoy a finished dish. They’re not thinking about where the ingredients came from or how much work went into it. That used to be my relationship with cold email. I didn’t want to understand all the behind-the-scenes mechanics. I didn’t want to learn about DNS records, domain health, spam signals, or verification logic. I didn’t want to think about inputs. I just wanted outcomes. Write good emails. Send them. Get replies. Book meetings. But after sending 12,487 cold emails in 12 months… Switching between 4 different infrastructures… Losing access to my domain 5 times… I realized something uncomfortable but true: If cold email puts food on your table, you eventually have to understand the kitchen. Because most of the problems I blamed on messaging weren't actually messaging issues. Some data problems were crippling my progress. I had to educate myself on the reality of bad inputs: - Bounces: Emails sent to addresses that don’t exist. - Spam-trap hits: Emails sent to fake addresses that flag you as a spammer. - Deliverability dips: More of your emails land in spam, not in inboxes. - Sequences that die before a human ever sees them: Your message never gets delivered or opened. - “Unresponsive leads” that were never valid to begin with: You're chasing ghosts, not prospects. And when the data is weak, the writing gets distorted. You over-personalize. You lean on AI too heavily. You force relevance that isn’t real. It makes your emails feel automated, not human. But when the inputs are strong (accurate contacts, verified addresses, healthy domains), the whole system stabilizes. Messaging becomes clearer. Sequences get simpler. Outreach feels human again. That’s something I noticed firsthand when I decided to move and work closely with Prospeo (https://prospeo.io/). Not as a pitch. Just as a practitioner who was tired of unnecessary firefighting. And making sense of my frustration with cold emailing in general. I learned this: High-quality data doesn’t make you better at cold email. It simply removes the noise so you can focus on what matters. And that changed the way I work. My takeaway after 12,487 sends: ✔ Strong inputs ✔ Stable infrastructure ✔ Simple, relevant writing Everything else is optional. If your cold outreach is underperforming, start with the parts no one sees. I’m not an email infra expert. I’m a business owner trying to get ROI, make payroll, and keep momentum. When I see something working? I’m going to share it. #prospeo Cole Boyce Matthew Putnam 🔵

Nonprofits are making a big mistake with their email sending volume. It's a significant reason why revenue via email is down 10% year over year, according to the fine folks at M&R. Their 2024 Benchmarks Survey is out and chock full of nuggets (link in comments). Non-profits are averaging less than 5 emails/mo in months other than December, when their volume spikes up to 12. 5 emails/mo is barely more than one a week. Email service providers like Google/Yahoo care a ton about recency of interaction to decide about inbox placement. They need lots of signals that people care about your content to get it into their inbox, not the spam box. You have to send frequently enough to know which of your list members are active or not, or else you'll risk sending to too many people and then seeing a lower overall open rate. You need to send frequently enough to have a solid recent actives screen. Sending less frequently will result in something of a doom spiral. You get a poor result, so you don't try again for a bit. Then you know even less about your list and send it to the wrong people and then get an even worse result. Usually, I shoot for a 90-day actives targeting (90-day NTL, 90-day action takers, 90-day openers, and 6-mo donors) for most lists. Not infrequently, you'll need to drop that down to 30-days or less when deliverability hits a snag. High volume political lists can look something like 14-day openers, 60-day clickers, 6-mo donors, 21-day subscribers, 60-day action takers. Nonprofits are capable of scaling up volume, and their lists will tolerate it in December. 40% of all digital revenue comes in that month as their send volume spikes. If organizations sent to their lists more frequently, they likely could level out that imbalance. There are folks out there who will recommend sending no fewer than 4x/week to maximize deliverability. That's a big leap for a lot of programs. I'd recommend getting to 2-3/week. You also should scale up your sending in advance of a spike in activity, ie, your sending in November should scale up so by the time you are really cranking it up in December, ESPs aren't surprised and reactive. I'm currently designing a new email program for a new nonprofit. I am concerned about having things to say at a high volume, and I know how much time goes into creating quality content. However, I know if my email volume is too low, I am going to have huge problems with deliverability when I scale up sends during rapid response moments. Honestly, one of the biggest problems orgs have with their email programs is their lengthy approvals process. As a former consultant in this space, the amount of revisions/handwringing over every little thing meant that I would need to charge significantly more money to manage nonprofit email programs than a political one doing similar volume. Make it easier to get newsy content out the door at a higher volume and you'll see overall performance (including fundraising) improve.

I tested every major email validator with the same 2,451-email list. The results? Most validators are leaving 30-50% of your B2B prospects on the table. Here's what I found... The Catch-All Problem: ~30% of B2B email addresses are catch-alls (domains that accept mail to any address). Most validators can't verify them, so they mark them "risky" or "unverifiable." You're stuck with two bad options: → Send to them anyway and risk hard bounces (destroys sender reputation) → Skip them entirely and lose 30% of your reach Head-to-Head Comparison: I ran the same list through MillionVerifier, ZeroBounce, NeverBounce, and OrbiSearch. MillionVerifier: 4% validated (102 emails) 95% marked "Risky" (2,336 unverified) ZeroBounce: 30.72% validated (753 emails) 58.51% catch-alls they couldn't verify (1,434) NeverBounce: 26.3% validated (646 emails) 56.9% marked unverifiable (1,395) OrbiSearch: 53.8% validated (1,319 emails) 46.2% risky (1,132) That's 11.5× more catch-alls validated than MillionVerifier. Why This Matters... On a 10,000-email list with 30% catch-alls (3,000 prospects): MillionVerifier validates ~120, you lose 2,880 ZeroBounce/NeverBounce validate ~900, you lose 2,100 OrbiSearch validates ~1,600, you lose 1,400 That's not a rounding error. That's the difference between hitting your pipeline goals and leaving qualified prospects on the table. How It Works: Most validators check if a domain is catch-all, then give up. OrbiSearch uses dual-layer verification: Standard SMTP validation identifies catch-alls Proprietary detection verifies if the specific mailbox exists Result: Instant validation (under 10 minutes for 10K emails) with zero false positives. No waiting 48-72 hours like email-sending validators. Get results immediately while your leads are hot. The Bottom Line: If you're running cold email and want to maximize reach without destroying sender reputation, catch-all resolution is the game. I built OrbiSearch because I needed this for my own agency campaigns. Now I'm using it exclusively. You can test it yourself—100 free credits (500 validations) when you sign up. No credit card required. Run your own comparison. See the difference.

It’s official: email best practices are no longer best — they’re required. Here’s why... Microsoft recently announced new bulk sender requirements that mirror the ones Google and Yahoo rolled out last year. And they aren’t just doing this for fun, promise. They’re doing it because too many senders ignored best practices when they were optional. So, now they’re mandatory. ¯\_(ツ)_/¯ Starting May 5th, if you’re sending more than 5,000 emails a day and not following the rules, Microsoft’s going to start rejecting your mail. Not junking it. Rejecting it. And I wanna be clear here: this isn’t coming out of nowhere. The writing’s been on the wall for a while... and mail has been silently filtered away from the inbox all this time. Now it's just that the rules aren't written in invisible ink! So, what are these rules I speak of? 💌 Authentication (SPF, DKIM, DMARC) Yes, we’re still talkin’ about this… get used to it. Microsoft wants the same setup Google and Yahoo asked for. If your domains aren’t properly authenticated and aligned, your deliverability will suffer. 💌 Valid “From” and “Reply-To” Addresses Microsoft wants to make sure that when someone replies to your message, there’s someone on the other end. No more sending from a “noreply@brand.com” black hole. 💌 One-Click Unsubscribe (RFC 8058) They’re cracking down on bad unsubscribe flows. Make it easy. No weird hoops or loops or “oops, we need 10 days to process your request.” Just a simple unsubscribe option that actually works. If you’re already sending it right (ahem, compliant with Google and Yahoo’s requirements), this is mostly a “cool, cool, carry on” moment. But you’ll need a whole lotta margaritas and tacos to overcome your sorrow if you’ve been dragging your feet. May 5th (ahem, cinco de mayo!) is not the day to find out Microsoft doesn’t play. What happens if you’re not ready? If you need help figuring out where you stand, here are a few fast checks: ✅ SPF, DKIM, and DMARC passing in headers? ✅ “Reply-To” address monitored and functioning? ✅ One-click unsubscribe live and working? ✅ Lists clean and bounce/spam complaint rates under control? If not, now’s the time to fix it. Not next week. Not next quarter. Now. TLDR: if you’re not sending responsibly, you’re not sending at all. Because come Monday — yes, THIS Monday — non-compliant mail will be rejected at the door. No inbox. No spam folder. Just blocked. So, get it together, you (not so) filthy animals! LinkedIn says I’m outta characters, but if you need tool recommendations or a second set of eyes on your setup, I'm happy to help. Reach out, email scout. 💌