惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
U
Unit 42
Google DeepMind News
Google DeepMind News
博客园 - 司徒正美
Y
Y Combinator Blog
F
Fortinet All Blogs
云风的 BLOG
云风的 BLOG
T
Tailwind CSS Blog
G
Google Developers Blog
酷 壳 – CoolShell
酷 壳 – CoolShell
罗磊的独立博客
D
DataBreaches.Net
T
The Blog of Author Tim Ferriss
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
MyScale Blog
MyScale Blog
N
Netflix TechBlog - Medium
Microsoft Security Blog
Microsoft Security Blog
GbyAI
GbyAI
P
Proofpoint News Feed
Jina AI
Jina AI
B
Blog RSS Feed
腾讯CDC
阮一峰的网络日志
阮一峰的网络日志
D
Docker

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
Cold email in 2026: what indie hackers got wrong (with a ...
孫昊 · 2026-05-06 · via DEV Community

If you've been sending B2B cold emails the same way for 18 months, your reply rate just dropped to ~0% and you don't know why.

I rebuilt my outreach this week after my reply rate tanked from 4% to <1%. Pulled fresh data from 5+ deliverability blogs (Autobound, MarketingProfs, HyperGen, Instantly), built a Python validator to enforce the new rules across 70+ template files in my repo, and shipped 10 trimmed emails that comply.

Here's what changed and the SOP for fixing your stack.


What changed in 2026

1. DMARC is now hard-rejected.

In Feb 2024, Google started requiring DMARC for bulk senders. In Nov 2025, they escalated to hard rejection. As of March 2026, emails from domains without properly configured DMARC + DKIM + SPF are rejected by major providers — not sent to spam. Rejected.

If you send from a custom domain (not gmail.com / hotmail.com), check yours:

dig TXT _dmarc.yourdomain.com
# Should return: v=DMARC1; p=quarantine; rua=mailto:dmarc@yourdomain.com

Enter fullscreen mode Exit fullscreen mode

If it returns nothing, you're invisible. Period.

2. Word count is now a ranking signal.

Multiple deliverability tests in 2026 show emails over 150 words have a measurable reply drop. The current sweet spot:

  • Initial email: 75-125 words
  • Followup: 50-75 words

I went through my outreach folder. Every email I'd written in 2024-2025 was 200-300 words. Trimmed all to 75-125. Reply rate started recovering within a week.

Why this changed: mobile preview. 60-80% of B2B emails are first scanned on mobile, where 150-word emails fill 2 screens. Recipients tap delete before they finish.

3. Personalization slot is required, not optional.

Generic "Hi {{name}}, I see you do {{industry}}" gets <1% reply in 2026. Recipients can detect template structure within 3 seconds. The new rule:

Each email needs a {{detail}} slot that references a specific recent action the prospect took (post / launch / hire / press release). Mass-merged templates with no specific detail = 0% reply.

Campaigns with signal-specific personalization hit 18% reply rate vs 3% for generic. 5x.

4. Daily volume cap dropped.

The safe limit per mailbox is now 50-100 emails/day. Total per SDR (across 3-4 mailboxes) sweet spot is 200-375/day. Above this triggers spam classifiers within a week, even with perfect content.

I was sending 250/day from 1 mailbox. Burned the domain reputation in 3 weeks. Lesson: split across multiple mailboxes (sales@ / hello@ / firstname@) and rotate.


The Python validator I built

I have 70+ paste-ready outreach templates in my repo. Going through each by hand to check word count + slots + spam triggers + CTA = 6 hours.

Built cold_email_validator.py instead. Run it on any email:

from orchestrator.lib.cold_email_validator import validate_email

result = validate_email(
    subject="30 min audit your AI workflow",
    body="""Hi {{name}},
    looked at {{company}}'s recent {{detail}}.
    [...75-125 words...]
    Reply with a time? cal.com/foo/30min""",
    is_followup=False,
)

print(result.score)  # 0-100
print(result.issues)  # list of structured issues with severity + fix hints

Enter fullscreen mode Exit fullscreen mode

It checks:

  • Subject: < 60 chars, no ALL CAPS, no excessive punctuation
  • Word count: in 75-125 (initial) or 50-75 (followup) range
  • Personalization: required {{name}}, {{company}}, {{detail}} slots
  • Spam triggers: 200+ word blacklist (guarantee, act now, 100%, etc)
  • CTA: must have URL or specific question or time word
  • Unfilled brackets: no [BRACKETS] left in template

Returns a 0-100 score with issue codes and fix suggestions. Run before every send. Run as CI check on your outreach repo.

36 tests, runs in 0.1 sec. MIT-licensed at github.com/jiejuefuyou/autoapp-toolkit/blob/main/orchestrator/lib/cold_email_validator.py.


A real example: trimming a 200-word email to 100

Here's an actual email I had in my repo. Before (200 words, sent in 2024):

Hi {{name}}, hope this finds you well.

I noticed your team at {{company}} has been doing some really impressive work in the {{industry}} space. I particularly liked your recent {{detail}}. The way you approached {{specific_aspect}} was insightful.

I'm reaching out because I work with B2B teams like yours to help them get more value from their AI workflows. We've helped companies like X, Y, and Z achieve 30-40% productivity gains by streamlining their AI tool stack. Specifically, we look at:

  • Tool sprawl reduction (most teams use 5-10 redundant tools)
  • Prompt library consolidation
  • Workflow handoff optimization
  • Measurement infrastructure

Our process is a 30-min discovery call followed by a 1-week audit followed by a 2-month implementation. Pricing starts at $99 for the audit and goes up to $25k for full implementation.

Would you be open to a 30-min call next week to explore if there's a fit? I'd love to learn more about what you're working on.

Looking forward to hearing from you.

Best,
Sun

Validator output:

  • Score: 35/100
  • ❌ Body 200 words > 150 hard cap
  • ⚠️ Subject too generic
  • ⚠️ Spam trigger: "I'd love to"
  • ⚠️ CTA buried in last paragraph

After (100 words, 2026 best practice):

Hi {{name}},

Just looked at {{company}}'s {{detail}} — sharp positioning.

Question: most {{industry}} teams I work with use 5-10 AI tools with 0 shared prompts library. The result is 8 hours/week wasted per person on duplicated work.

30 min audit gives you (1) tool sprawl map (2) 3 quick-win prompts you can deploy this week. Free. If we click after, $99 starter package.

Reply with Wednesday or Thursday afternoon? Or book direct: cal.com/foo/30min

Validator output:

  • Score: 92/100
  • ✅ Word count in target
  • ✅ Specific personalization slot
  • ✅ Concrete CTA with URL fallback

Same value proposition. Half the words. 5x reply rate (in my 1-week test, n=24 sends).


What I'd skip in 2026

A few practices that worked in 2023-2024 but stop working now:

1. Multi-paragraph "value-first" intros. Lost. Recipients don't read past sentence 2 before deciding. Lead with the specific detail or skip.

2. "Just following up" without new info. Auto-classified as spam by major providers in 2026. Every followup needs a NEW angle (new data, new resource, new ask).

3. Long signature blocks with social links. Hurts deliverability score. Use 2-line signature: name + 1 link.

4. PS sections with secondary CTA. Used to boost replies; now seen as template marker. Remove.

5. Hardcoded company info. "I see you're at {{company}}, a leading {{industry}} firm" is dead. You need {{detail}} (specific recent action) instead.


My current outreach stack (2026)

For full transparency:

  • 10 emails organized by ICP, each 75-125 words (repo)
  • 2 mailbox rotation: hello@jiejuefuyou.com (primary) + sun@ (backup)
  • DMARC p=quarantine with rua reporting to dmarc@
  • Cal.com 30 min slot as primary CTA
  • Reply rate target: 5% (3% acceptable, 8%+ exceptional)
  • Sending volume: 30/day per mailbox (well under 100 cap)

Sending Mon-Wed 9-11 AM JST (US Sun-Tue evening = best B2B reach for my audience).


Action items

If your reply rate dropped recently:

  1. Run a deliverability check: mail-tester.com (free) — score 8+/10 needed
  2. Verify DMARC: dig TXT _dmarc.yourdomain.com — must return policy
  3. Run validator on every template in your outreach folder
  4. Rewrite anything > 150 words to 75-125 (cut, don't shorten)
  5. Add {{detail}} slot to every template; fill with specific recent action
  6. Rotate mailboxes if sending > 100/day total

This took me ~4 hours to do across my 70 templates. Reply rate started recovering inside a week.


Summary

Practice 2024 2026
Initial email words 200-400 75-125
Followup words 100-200 50-75
DMARC required Optional Hard-rejected
Personalization Token slots Specific recent action
Daily volume/mailbox 200-300 50-100
Reply rate target 1-3% 3-5% (signal: 18%)

If you've been ignoring these changes, your domain reputation is degrading silently. The first sign isn't always "spam folder" — it's rejected at SMTP with no notification. By the time you notice, you need a fresh domain.

Run the validator. Check your DMARC. Rewrite the templates. Don't lose your channel.


Open source toolkit at github.com/jiejuefuyou/autoapp-toolkit. Validator + 10 trimmed templates included. If this helped, give me a star — I read every issue.