Back to Details

sales-deliverability

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Email Deliverability for Outbound Sales

外呼销售邮件送达率

Help the user set up, diagnose, and optimize email deliverability — from domain authentication and warmup through inbox placement, reputation monitoring, and platform-specific configuration. This skill is tool-agnostic and covers Apollo, Mailshake, Salesloft, Lemlist, Yesware, Mixmax, Reply.io, Woodpecker, and standalone tools.
帮助用户搭建、诊断并优化邮件送达率——从域名认证、邮箱预热，到收件箱投递率、信誉监控及平台专属配置。本Skill与工具无关，覆盖Apollo、Mailshake、Salesloft、Lemlist、Yesware、Mixmax、Reply.io、Woodpecker及独立工具。

Step 1 — Gather context

步骤1 — 收集上下文

Ask the user:
  1. What's your situation?
    • A) Setting up a new domain for cold outbound
    • B) Warming up a new mailbox / sender account
    • C) Emails going to spam — need to diagnose
    • D) Open rates dropped significantly
    • E) High bounce rates
    • F) Blacklisted — need to recover
    • G) Scaling sending volume (increasing daily sends)
    • H) Switching platforms (migrating senders)
    • I) Something else — describe it
  2. What's your current sending setup?
    • Primary domain or dedicated outbound domain?
    • How many mailboxes / sender accounts?
    • Daily sending volume (current or target)?
    • How long have you been sending from this domain/mailbox?
  3. What tools are you using?
    • A) Apollo.io
    • B) Mailshake
    • C) Salesloft
    • D) Lemlist
    • E) Yesware
    • F) Instantly / Smartlead
    • G) Mixmax
    • H) Reply.io
    • I) Woodpecker
    • J) HubSpot / Salesforce (direct sending)
    • K) Custom SMTP / other
    • L) Multiple tools — describe
  4. Domain authentication status?
    • A) SPF/DKIM/DMARC all configured
    • B) Some configured, not sure which
    • C) Not configured / don't know
    • D) Using a new domain with nothing set up
If the user's request already provides most of this context, skip directly to the relevant step. Lead with your best-effort answer using reasonable assumptions (stated explicitly), then ask only the most critical 1-2 clarifying questions at the end — don't gate your response behind gathering complete context.
询问用户：
  1. 你的具体场景是什么？
    • A) 为冷外呼搭建新域名
    • B) 预热新邮箱/发件人账户
    • C) 邮件进入垃圾邮件箱——需要诊断
    • D) 打开率大幅下降
    • E) 退信率过高
    • F) 被列入黑名单——需要恢复
    • G) 扩容发送量（增加每日发送数）
    • H) 切换平台（迁移发件人）
    • I) 其他情况——请描述
  2. 你当前的发送配置是怎样的？
    • 使用主域名还是专用外呼域名？
    • 有多少个邮箱/发件人账户？
    • 每日发送量（当前或目标值）？
    • 你使用该域名/邮箱发送邮件已有多久？
  3. 你正在使用哪些工具？
    • A) Apollo.io
    • B) Mailshake
    • C) Salesloft
    • D) Lemlist
    • E) Yesware
    • F) Instantly / Smartlead
    • G) Mixmax
    • H) Reply.io
    • I) Woodpecker
    • J) HubSpot / Salesforce（直接发送）
    • K) 自定义SMTP / 其他
    • L) 多种工具——请描述
  4. 域名认证状态如何？
    • A) SPF/DKIM/DMARC已全部配置
    • B) 部分配置，不确定具体是哪些
    • C) 未配置 / 不清楚
    • D) 使用全新域名，未进行任何设置
如果用户的请求已提供大部分此类上下文，可直接跳至相关步骤。 先基于合理假设（需明确说明）给出最佳答案，最后仅询问1-2个最关键的澄清问题——不要要求用户提供完整上下文后才给出回复。

Step 2 — Domain authentication framework

步骤2 — 域名认证框架

Domain authentication is the foundation of deliverability. All three records must be properly configured.
域名认证是送达率的基础。必须正确配置全部三项记录。

SPF (Sender Policy Framework)

SPF（发件人策略框架）

  • What it does: Tells receiving servers which mail servers are authorized to send on behalf of your domain
  • DNS record: TXT record on your domain
  • Format: 
    v=spf1 include:_spf.google.com include:mailshake.com ~all
  • Key rules: Only one SPF record per domain. Use 
    include:
    for each authorized sender. Max 10 DNS lookups.
  • Common mistake: Multiple SPF records (only the first is read), too many includes (exceeds lookup limit)
  • 作用：告知收件服务器哪些邮件服务器被授权代表你的域名发送邮件
  • DNS记录：域名下的TXT记录
  • 格式：
    v=spf1 include:_spf.google.com include:mailshake.com ~all
  • 关键规则：每个域名只能有一条SPF记录。对每个授权发件人使用
    include:
    。最多允许10次DNS查询。
  • 常见错误：多条SPF记录（仅第一条会被读取），包含过多授权方（超出查询限制）

DKIM (DomainKeys Identified Mail)

DKIM（域名密钥识别邮件）

  • What it does: Adds a cryptographic signature to outgoing emails proving they haven't been tampered with
  • DNS record: TXT or CNAME record (format varies by provider)
  • Setup: Each sending platform provides its own DKIM key. Add the record they give you to your DNS.
  • Common mistake: Not adding DKIM for every sending platform. Each service needs its own DKIM record.
  • 作用：为 outgoing邮件添加加密签名，证明邮件未被篡改
  • DNS记录：TXT或CNAME记录（格式因服务商而异）
  • 配置方法：每个发送平台都会提供专属DKIM密钥。将其添加到你的DNS记录中。
  • 常见错误：未为每个发送平台配置DKIM。每个服务都需要独立的DKIM记录。

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

DMARC（基于域名的邮件认证、报告与一致性）

  • What it does: Tells receiving servers what to do with emails that fail SPF/DKIM checks
  • DNS record: TXT record at 
    _dmarc.yourdomain.com
  • Recommended start: 
    v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com
    (monitor mode)
  • Progression: none → quarantine → reject (move to reject after 2-4 weeks of clean monitoring)
  • Common mistake: Jumping straight to 
    p=reject
    before monitoring — this blocks legitimate emails
  • 作用：告知收件服务器如何处理未通过SPF/DKIM校验的邮件
  • DNS记录：
    _dmarc.yourdomain.com
    下的TXT记录
  • 推荐初始配置：
    v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com
    （监控模式）
  • 进阶配置：none → quarantine → reject（在2-4周的干净监控后再切换为reject）
  • 常见错误：未进行监控就直接设置
    p=reject
    ——这会拦截合法邮件

Custom tracking domain

自定义跟踪域名

  • What it is: A subdomain (e.g., 
    track.yourdomain.com
    ) for open/click tracking instead of shared tracking domains
  • Why it matters: Shared tracking domains get flagged by spam filters. Custom domains protect your reputation.
  • Setup: CNAME record pointing to your platform's tracking server
  • 定义：用于打开/点击跟踪的子域名（例如
    track.yourdomain.com
    ），替代共享跟踪域名
  • 重要性：共享跟踪域名会被垃圾邮件过滤器标记。自定义域名可保护你的信誉。
  • 配置方法：CNAME记录指向平台的跟踪服务器

Verification checklist

验证清单

  • SPF record includes all sending services
  • DKIM configured for each sending platform
  • DMARC record exists (start with p=none)
  • Custom tracking domain configured
  • Test with mail-tester.com (aim for 9+/10)
  • Test with MXToolbox for DNS record validation
  • SPF记录包含所有发送服务
  • 已为每个发送平台配置DKIM
  • 存在DMARC记录（初始设置为p=none）
  • 已配置自定义跟踪域名
  • 使用mail-tester.com进行测试（目标得分9+/10）
  • 使用MXToolbox验证DNS记录

Step 3 — Warmup strategy

步骤3 — 预热策略

New mailboxes and domains must be warmed up before sending at volume. Skipping warmup is the #1 cause of deliverability problems.
新邮箱和域名在批量发送前必须进行预热。跳过预热是送达率问题的头号原因。

Warmup schedule (new mailbox)

新邮箱预热时间表

WeekDaily sendsNotes
15-10Manual sends to engaged contacts, internal test sends
215-25Mix of warm contacts and small cold batches
330-40Gradual increase, monitor bounce/spam rates
440-50Standard cold outbound volume
5+50-75Scale cautiously, never exceed provider limits
For new domains: Add 2 extra weeks at the beginning (weeks 1-2 at 3-5 sends/day). New domains have zero reputation.
周数每日发送量说明
15-10手动发送给活跃联系人，内部测试发送
215-25混合发送给熟客和少量冷接触批次
330-40逐步增加发送量，监控退信/垃圾邮件率
440-50标准冷外呼发送量
5+50-75谨慎扩容，切勿超出服务商限制
针对新域名：在最开始增加2周的预热时间（第1-2周每日发送3-5封）。新域名没有任何初始信誉。

Warmup tools

预热工具

  • Smartlead Ultra Premium Warmup — AI-driven warmup built into the Smartlead platform with exclusive warmup network. Unlike standalone tools, it's fully integrated with sender management and campaign scheduling.
  • Instantly — automated warmup with real engagement (opens, replies, moves from spam)
  • Warmbox — AI-powered warmup network
  • Lemwarm — Lemlist's built-in warmup (included free with every seat, 10,000+ user network, deliverability scoring)
  • Mailwarm — Standalone warmup service
These tools simulate real email conversations to build sender reputation. Run warmup for at least 2-3 weeks before adding cold outbound.
  • Smartlead Ultra Premium Warmup —— 集成在Smartlead平台中的AI驱动预热工具，拥有专属预热网络。与独立工具不同，它与发件人管理和活动调度完全集成。
  • Instantly —— 自动化预热，模拟真实互动（打开、回复、从垃圾邮件箱移至收件箱）
  • Warmbox —— AI驱动的预热网络
  • Lemwarm —— Lemlist内置的预热工具（每个席位免费包含，拥有10,000+用户网络，提供送达率评分）
  • Mailwarm —— 独立预热服务
这些工具模拟真实邮件对话以建立发件人信誉。在启动冷外呼前，至少运行预热2-3周。

Mailbox rotation

邮箱轮换

  • Why: Distributing sends across multiple mailboxes protects each one's reputation and increases total volume
  • Rule of thumb: 1 mailbox per 50-75 cold emails/day
  • Setup: Connect multiple sender accounts in your platform and enable rotation/round-robin
  • Naming: Use real names (jane@company.com), not generic addresses (sales@, outreach@)
  • 原因：在多个邮箱间分配发送量可保护每个邮箱的信誉，并提升总发送量
  • 经验法则：每50-75封冷邮件/天使用1个邮箱
  • 配置方法：在平台中连接多个发件人账户，启用轮换/循环发送
  • 命名规范：使用真实姓名（如jane@company.com），而非通用地址（如sales@、outreach@）

Step 4 — Platform-specific implementation

步骤4 — 平台专属配置

In Mailshake

Mailshake平台

  • Sending limits: Configure per-sender daily limits in Settings > Senders
  • Sender rotation: Add multiple senders to a campaign — Mailshake rotates automatically
  • Custom tracking domain: Settings > Tracking Domain — add CNAME record
  • Warmup: Mailshake doesn't have built-in warmup. Use Instantly or Warmbox alongside.
  • Bounce handling: Auto-pauses recipients on hard bounce. Monitor in Activity > Bounces.
  • 发送限制：在设置>发件人中配置每个发件人的每日限制
  • 发件人轮换：为活动添加多个发件人——Mailshake会自动轮换
  • 自定义跟踪域名：设置>跟踪域名——添加CNAME记录
  • 预热：Mailshake无内置预热工具。需搭配Instantly或Warmbox使用。
  • 退信处理：遇到硬退信时自动暂停收件人。在活动>退信中监控。

In Apollo

Apollo平台

  • Inbox Ramp Up: Settings > Email > Inbox Ramp Up — Apollo's built-in warmup feature
  • Command Center: Settings > Email > Deliverability — monitors sender health, SPF/DKIM status
  • Sending limits: Settings > Email > Sending Limits — per-mailbox daily caps
  • Mailbox rotation: Assign multiple mailboxes to a sequence — Apollo rotates sends
  • Custom tracking domain: Settings > Email > Custom Tracking Domain
  • 收件箱扩容：设置>邮件>收件箱扩容——Apollo内置的预热功能
  • 指挥中心：设置>邮件>送达率——监控发件人健康状态、SPF/DKIM状态
  • 发送限制：设置>邮件>发送限制——每个邮箱的每日上限
  • 邮箱轮换：为序列分配多个邮箱——Apollo会轮换发送
  • 自定义跟踪域名：设置>邮件>自定义跟踪域名

In Salesloft

Salesloft平台

  • Email settings: Settings > Email — configure sending windows, throttling, daily limits
  • Throttling: Salesloft auto-throttles to prevent spikes. Configure max emails per hour.
  • Sender management: Cadence settings > Sender — assign specific senders per cadence
  • Custom tracking domain: Admin > Email > Custom Tracking Domain
  • 邮件设置：设置>邮件——配置发送窗口、流量控制、每日限制
  • 流量控制：Salesloft会自动进行流量控制以避免发送量突增。配置每小时最大发送数。
  • 发件人管理：节奏设置>发件人——为每个节奏分配特定发件人
  • 自定义跟踪域名：管理员>邮件>自定义跟踪域名

In Lemlist

Lemlist平台

  • Lemwarm: Built-in warmup included with every seat at no extra cost. Enable per email account — set warmup to 30 emails/day for accounts <6 months, 40/day for older. Minimum 3-5 weeks before adding cold outbound. Monitor deliverability score (target 90+).
  • Inbox rotation: Connect multiple email accounts to a sequence — Lemlist rotates sends automatically. Each account limited to plan allowance (5 per user on Multichannel Expert, $9 per additional inbox).
  • Domain auth: Configure SPF/DKIM/DMARC and custom tracking domain before launching sequences. Lemlist Help Center has DNS configuration guides.
  • Sending limits: Configure per-account daily limits. Recommended 30-50 cold emails/day per mailbox.
  • Lemwarm：每个席位免费包含的内置预热工具。为每个邮箱账户启用——对于使用时长<6个月的账户，设置为每日30封预热邮件；对于老账户，设置为每日40封。在启动冷外呼前至少运行3-5周。监控送达率评分（目标90+）。
  • 邮箱轮换：为序列连接多个邮箱账户——Lemlist会自动轮换发送。每个账户受限于计划配额（Multichannel Expert计划每个用户最多5个邮箱，额外邮箱每个9美元）。
  • 域名认证：在启动序列前配置SPF/DKIM/DMARC和自定义跟踪域名。Lemlist帮助中心提供DNS配置指南。
  • 发送限制：配置每个账户的每日限制。推荐每个邮箱每日发送30-50封冷邮件。

In Yesware

Yesware平台

  • Sends from your inbox: Yesware campaigns send directly from Gmail/Outlook — no third-party server. This improves deliverability because emails appear as genuine 1:1 messages, not bulk sends.
  • No built-in warmup: Since Yesware sends from your existing inbox, traditional warmup is less critical. However, if you're sending high-volume campaigns from a new email account, ramp up gradually (20/day → 50/day over 2-3 weeks).
  • Domain auth: SPF/DKIM/DMARC should still be configured for your domain. Yesware inherits your inbox's auth settings.
  • Custom tracking domain: Yesware uses its own tracking domain for open/click tracking. This is a shared domain — no custom tracking domain option.
  • Sending limits: Governed by your email provider (Gmail ~400-500/day, Outlook ~1,000/day) plus Yesware plan limits on campaign recipients.
  • Key advantage: Inbox-native sending means no separate IP reputation to manage and no relay server that could get blacklisted.
  • Key limitation: No deliverability dashboard — Yesware doesn't report inbox placement rate, so you won't know how many emails landed in spam vs inbox.
  • 从收件箱发送：Yesware活动直接从Gmail/Outlook发送——无需第三方服务器。这可提升送达率，因为邮件看起来是真实的1:1消息，而非批量发送。
  • 无内置预热：由于Yesware从现有收件箱发送，传统预热的重要性较低。但如果你从新邮箱账户发送高容量活动，需逐步增加发送量（20/天 → 50/天，耗时2-3周）。
  • 域名认证：仍需为你的域名配置SPF/DKIM/DMARC。Yesware会继承收件箱的认证设置。
  • 自定义跟踪域名：Yesware使用自身的跟踪域名进行打开/点击跟踪。这是一个共享域名——无自定义跟踪域名选项。
  • 发送限制：受限于你的邮件服务商（Gmail约400-500/天，Outlook约1,000/天）以及Yesware计划对活动收件人的限制。
  • 核心优势：收件箱原生发送意味着无需管理独立的IP信誉，也不存在中继服务器被列入黑名单的风险。
  • 核心局限：无送达率仪表盘——Yesware不报告收件箱投递率，因此你无法得知有多少邮件进入垃圾邮件箱，多少进入收件箱。

In Smartlead

Smartlead平台

  • SmartSenders: Auto-provision mailboxes via Gmail/Outlook OAuth. Configure per-sender daily limits (recommend 30-50/day per mailbox for cold outbound).
  • SmartInfra: Dedicated IPs with auto DNS/DKIM/DMARC configuration for high-volume senders. Evaluate when sending 1,000+ emails/day or managing multiple clients.
  • Ultra Premium Warmup: Built-in warmup — enable per mailbox, minimum 2-3 weeks before campaign sends. Monitor warmup reputation score (target 80+ before activating).
  • SmartDelivery: Inbox placement testing — send test emails to seed accounts and measure inbox vs spam placement. Run before launching campaigns and periodically during active sends.
  • Custom tracking domain: Settings > Tracking Domain — add CNAME record for branded link tracking.
  • SmartSenders：通过Gmail/Outlook OAuth自动配置邮箱。为每个发件人配置每日限制（推荐冷外呼每个邮箱每日30-50封）。
  • SmartInfra：为高容量发件人提供专属IP，自动配置DNS/DKIM/DMARC。当每日发送1,000+封邮件或管理多个客户时可考虑使用。
  • Ultra Premium Warmup：内置预热工具——为每个邮箱启用，在活动发送前至少运行2-3周。监控预热信誉评分（激活前目标80+）。
  • SmartDelivery：收件箱投递测试——向种子账户发送测试邮件，统计收件箱与垃圾邮件箱的投递情况。在活动启动前及活动期间定期运行。
  • 自定义跟踪域名：设置>跟踪域名——添加CNAME记录以实现品牌化链接跟踪。

In Mixmax

Mixmax平台

  • Sending method: Gmail-native — emails send through the user's actual Gmail account (Google Workspace), not through Mixmax's servers. This means deliverability is tied to your Google Workspace domain reputation, not Mixmax's infrastructure.
  • SPF/DKIM/DMARC: Managed at the Google Workspace level, not in Mixmax. Ensure your domain has SPF, DKIM, and DMARC configured in Google Workspace Admin > Apps > Google Workspace > Gmail > Authentication.
  • Custom tracking domains: Available to reduce spam filtering on tracked links — configure in Mixmax settings. Uses CNAME record pointing to Mixmax's tracking servers.
  • No built-in warmup: Mixmax does not have a warmup tool. Since it sends through Gmail, use a third-party warmup service (Lemwarm, Warmbox, Instantly) connected to your Google Workspace account if needed.
  • Sending limits: Subject to Gmail/Google Workspace sending limits (2,000 emails/day for Workspace, 500/day for free Gmail). Mixmax sequences respect these limits automatically.
  • No deliverability dashboard: Mixmax doesn't have a dedicated deliverability dashboard. Monitor bounce rates in sequence reporting; check Google Postmaster Tools for domain reputation.
  • Best practice: Since Mixmax is Gmail-native, your Google Workspace domain health IS your Mixmax deliverability. Focus on Google Postmaster Tools, proper authentication, and keeping bounce rates under 2%.
  • 发送方式：Gmail原生——邮件通过用户的真实Gmail账户（Google Workspace）发送，而非Mixmax的服务器。这意味着送达率与你的Google Workspace域名信誉绑定，而非Mixmax的基础设施。
  • SPF/DKIM/DMARC：在Google Workspace层面管理，而非Mixmax中。确保你的域名已在Google Workspace管理员>应用>Google Workspace>Gmail>认证中配置SPF、DKIM和DMARC。
  • 自定义跟踪域名：可配置以降低跟踪链接被垃圾邮件过滤器标记的风险——在Mixmax设置中配置。使用CNAME记录指向Mixmax的跟踪服务器。
  • 无内置预热：Mixmax无预热工具。由于它通过Gmail发送，若需预热，可使用第三方预热服务（Lemwarm、Warmbox、Instantly）连接到你的Google Workspace账户。
  • 发送限制：受Gmail/Google Workspace发送限制（Workspace账户2,000封/天，免费Gmail账户500封/天）。Mixmax序列会自动遵守这些限制。
  • 无送达率仪表盘：Mixmax无专门的送达率仪表盘。在序列报告中监控退信率；通过Google Postmaster Tools查看域名信誉。
  • 最佳实践：由于Mixmax是Gmail原生工具，你的Google Workspace域名健康状况就是Mixmax的送达率。重点关注Google Postmaster Tools、正确的认证配置，并将退信率控制在2%以下。

In Reply.io

Reply.io平台

  • Built-in warmup: Peer-to-peer warmup service — uses real Reply.io user accounts (no free/temporary emails). The system opens, replies, marks as important, and removes from spam realistically. Enable in Settings > Email Accounts > Warmup.
  • Warmup timeline: 2-3 weeks for new domains/mailboxes. Leave warmup running even after starting sequences to maintain reputation.
  • Domain health checker: Dedicated tab in Reply.io that checks SPF, DKIM, DMARC, and MX records. Provides actionable fix suggestions for each issue.
  • Google Postmaster integration: Reply.io pulls spam rate data directly from Google Postmaster Tools — monitor your spam rate without leaving the platform.
  • Branded links: Custom tracking domains to replace Reply.io's default tracking domain — reduces spam filtering on tracked links. Configure in Settings > Branded Links.
  • Sending limits: Respects Gmail/Outlook provider limits; configure per-mailbox daily caps. Use multiple mailboxes (up to 10/user on Multichannel plan) to increase volume safely.
  • Bounce handling: Automatic bounce detection; bounced contacts are paused in sequences. Monitor bounce rate in sequence analytics — keep under 3%.
  • Best practice: Enable warmup on every new mailbox before adding it to sequences. Use the domain health checker weekly. If spam rate exceeds 0.3% in Google Postmaster, pause sequences and investigate.
  • 内置预热：点对点预热服务——使用真实的Reply.io用户账户（无免费/临时邮箱）。系统会真实地打开、回复、标记为重要、从垃圾邮件箱移至收件箱。在设置>邮箱账户>预热中启用。
  • 预热时间线：新域名/邮箱需2-3周。即使启动序列后，也要继续运行预热以维护信誉。
  • 域名健康检查器：Reply.io中的专用标签页，检查SPF、DKIM、DMARC和MX记录。针对每个问题提供可操作的修复建议。
  • Google Postmaster集成：Reply.io直接从Google Postmaster Tools拉取垃圾邮件率数据——无需离开平台即可监控垃圾邮件率。
  • 品牌化链接：自定义跟踪域名以替代Reply.io的默认跟踪域名——降低跟踪链接被垃圾邮件过滤器标记的风险。在设置>品牌化链接中配置。
  • 发送限制：遵守Gmail/Outlook服务商限制；配置每个邮箱的每日上限。使用多个邮箱（Multichannel计划每个用户最多10个）安全提升发送量。
  • 退信处理：自动检测退信；退信的联系人会在序列中被暂停。在序列分析中监控退信率——控制在3%以下。
  • 最佳实践：在将新邮箱添加到序列前，为其启用预热。每周使用域名健康检查器。如果Google Postmaster中的垃圾邮件率超过0.3%，暂停序列并进行调查。

In Woodpecker

Woodpecker平台

  • Built-in warmup: Free warmup powered by Mailivery — AI-driven interactions (opens, replies, marks as important, removes from spam). Starts with a few emails/day, ramps to max 50/day. Included in all plans (free plan: 4 warmup slots). Additional slots available at €5/account.
  • Bounce Shield: Proactive protection that prevents sending to risky or invalid addresses before they bounce. Reduces bounce rate and protects sender reputation automatically.
  • Adaptive Sending: Automatically adjusts sending volume and pace based on email provider limits and engagement signals. Prevents overloading mailboxes and triggering spam filters.
  • ESP Matching: Matches your sending patterns to what email service providers expect from legitimate senders — improves inbox placement.
  • Email verification: Free catch-all verification powered by Bouncer. Real-time list cleaning validates prospect emails when added to campaigns. Catches invalid addresses before sending.
  • Domain audit: In-app tool that checks SPF, DKIM, DMARC configuration with actionable fix suggestions. Run before launching any campaign.
  • Spam checker: Pre-send analysis that highlights spammy words, broken links, and authentication issues in your email content.
  • Deliverability monitor: Ongoing monitoring of inbox placement and sender reputation. Alerts when metrics degrade.
  • Inbox rotation: Distributes sends across multiple mailboxes to stay within per-account limits while maintaining volume. Unlimited email accounts on all plans.
  • Best practice: Woodpecker has the most comprehensive built-in deliverability toolkit of any cold email tool. Enable warmup + Bounce Shield + Adaptive Sending on every account. Run domain audit before first campaign. Use the spam checker on every new email template.
  • 内置预热：由Mailivery提供支持的免费预热工具——AI驱动的互动（打开、回复、标记为重要、从垃圾邮件箱移至收件箱）。从每日几封邮件开始，逐步增加至最多50封/天。所有计划均包含（免费计划：4个预热席位）。额外席位每个5欧元/账户。
  • 退信防护：主动防护，在发送前避免向高风险或无效地址发送邮件。自动降低退信率并保护发件人信誉。
  • 自适应发送：根据邮件服务商限制和互动信号自动调整发送量和节奏。避免邮箱过载并触发垃圾邮件过滤器。
  • ESP匹配：使你的发送模式符合邮件服务商对合法发件人的预期——提升收件箱投递率。
  • 邮件验证：由Bouncer提供支持的免费全域验证。在添加到活动时实时验证潜在客户邮箱。在发送前捕获无效地址。
  • 域名审计：内置工具，检查SPF、DKIM、DMARC配置并提供可操作的修复建议。在启动任何活动前运行。
  • 垃圾邮件检查器：发送前分析，突出显示邮件内容中的垃圾邮件敏感词、无效链接和认证问题。
  • 送达率监控：持续监控收件箱投递率和发件人信誉。当指标下降时发出警报。
  • 邮箱轮换：在多个邮箱间分配发送量，以在遵守每个账户限制的同时维持发送量。所有计划均支持无限邮箱账户。
  • 最佳实践：Woodpecker拥有所有冷邮件工具中最全面的内置送达率工具包。为每个账户启用预热+退信防护+自适应发送。在首次活动前运行域名审计。为每个新邮件模板使用垃圾邮件检查器。

Standalone tools (any platform)

独立工具（适用于任何平台）

  • MXToolbox: DNS lookup, blacklist check, SPF/DKIM/DMARC validation
  • mail-tester.com: Send a test email, get a deliverability score (aim for 9+/10)
  • SmartDelivery (Smartlead): Inbox placement testing by provider (Gmail, Outlook, Yahoo)
  • GlockApps: Inbox placement testing and spam filter analysis
  • Google Postmaster Tools: Monitor Gmail-specific reputation (if targeting Gmail recipients)
  • Microsoft SNDS: Monitor Outlook/Microsoft reputation
  • MXToolbox：DNS查询、黑名单检查、SPF/DKIM/DMARC验证
  • mail-tester.com：发送测试邮件，获取送达率评分（目标9+/10）
  • SmartDelivery（Smartlead）：按服务商（Gmail、Outlook、Yahoo）进行收件箱投递测试
  • GlockApps：收件箱投递测试和垃圾邮件过滤器分析
  • Google Postmaster Tools：监控针对Gmail收件人的域名信誉
  • Microsoft SNDS：监控Outlook/Microsoft域名信誉

Step 5 — Monitoring and recovery

步骤5 — 监控与恢复

Key metrics to track

需跟踪的关键指标

MetricTargetAction if exceeded
Bounce rate<3%Pause sending, clean list, verify emails before next send
Spam complaint rate<0.1%Reduce volume, review content, check targeting
Open rate>40%Check deliverability (inbox vs spam), test subject lines
Unsubscribe rate<1%Review frequency, improve relevance
指标目标值超出后的行动
退信率<3%暂停发送，清理列表，下次发送前验证邮箱
垃圾邮件投诉率<0.1%降低发送量，检查内容，优化目标受众
打开率>40%检查送达率（收件箱vs垃圾邮件箱），测试主题行
退订率<1%调整发送频率，提升内容相关性

Blacklist check and delisting

黑名单检查与移除

  1. Check: Use MXToolbox blacklist check or multirbl.valli.org to check your domain/IP
  2. Common blacklists: Spamhaus, Barracuda, SORBS, SpamCop, CBL
  3. Delisting process: Each blacklist has its own removal request form. Fix the root cause first (high bounces, spam complaints), then request removal.
  4. Timeline: Most blacklists delist within 24-48 hours after request. Spamhaus can take longer.
  1. 检查：使用MXToolbox黑名单检查或multirbl.valli.org检查你的域名/IP
  2. 常见黑名单：Spamhaus、Barracuda、SORBS、SpamCop、CBL
  3. 移除流程：每个黑名单都有自己的移除请求表单。先修复根本原因（高退信率、垃圾邮件投诉），再提交移除请求。
  4. 时间线：大多数黑名单会在请求提交后24-48小时内完成移除。Spamhaus可能需要更长时间。

Reputation recovery

信誉恢复

If your domain reputation is damaged:
  1. Stop all outbound from the affected domain/mailbox immediately
  2. Diagnose: Check bounce rate, spam complaints, blacklist status
  3. Fix root cause: Clean list, fix auth, reduce volume
  4. Warmup again: Treat the mailbox as new — follow the warmup schedule from Week 1
  5. Consider a new domain: If reputation is severely damaged (blacklisted on 3+ lists), it may be faster to start a new outbound domain
如果你的域名信誉受损：
  1. 立即停止受影响域名/邮箱的所有外呼发送
  2. 诊断：检查退信率、垃圾邮件投诉、黑名单状态
  3. 修复根本原因：清理列表，修复认证问题，降低发送量
  4. 重新预热：将该邮箱视为新邮箱——遵循第1周的预热时间表
  5. 考虑更换域名：如果信誉严重受损（被3+个黑名单列入），更换新的外呼域名可能更快恢复

List hygiene

列表卫生管理

  • Verify before sending: Use NeverBounce, ZeroBounce, or BriteVerify before importing lists
  • Remove on bounce: Hard bounces should be permanently removed, not just paused
  • Re-verify periodically: Email addresses decay at ~25% per year. Re-verify lists older than 3 months.
  • Never use purchased lists: Purchased lists have high bounce/spam rates and will destroy your reputation
  • 发送前验证：在导入列表前使用NeverBounce、ZeroBounce或BriteVerify进行验证
  • 退信即移除：硬退信地址应永久移除，而非仅暂停
  • 定期重新验证：邮箱地址每年约有25%的失效率。对超过3个月的列表重新验证。
  • 切勿使用购买的列表：购买的列表退信/垃圾邮件率极高，会彻底摧毁你的信誉

Gotchas

注意事项

  • Don't skip warmup. Every new mailbox needs 2-4 weeks of warmup before cold outbound. Sending 100 cold emails from a brand-new mailbox will land in spam immediately. Claude often generates "connect mailbox → start sending" workflows that skip this critical step.
  • Don't send from your primary domain. Use a dedicated outbound domain (e.g., 
    outbound.yourcompany.com
    or 
    yourcompanymail.com
    ). If your outbound domain gets blacklisted, your primary domain (and all company email) is protected.
  • Don't ignore bounces. A bounce rate above 3% signals to email providers that you're sending to bad addresses. This damages reputation quickly. Pause the campaign, clean the list, and re-verify before resuming.
  • Don't use purchased or scraped lists. These lists have high bounce rates, spam traps, and unengaged recipients. They will destroy your sender reputation within days. Always build lists from legitimate data providers and verify emails before sending.
  • 请勿跳过预热。每个新邮箱在冷外呼前都需要2-4周的预热。从全新邮箱发送100封冷邮件会立即进入垃圾邮件箱。Claude生成的“连接邮箱→开始发送”流程通常会跳过这一关键步骤。
  • 请勿使用主域名发送。使用专用外呼域名（例如
    outbound.yourcompany.com
    或
    yourcompanymail.com
    ）。如果外呼域名被列入黑名单，主域名（及所有公司邮件）仍会受到保护。
  • 请勿忽视退信。退信率超过3%会向邮件服务商发出信号，表明你在向无效地址发送邮件。这会迅速损害信誉。暂停活动，清理列表，重新验证后再恢复发送。
  • 请勿使用购买或抓取的列表。这些列表退信率高，包含垃圾邮件陷阱和不活跃收件人。它们会在数天内摧毁你的发件人信誉。始终从合法数据供应商处构建列表，并在发送前验证邮箱。

Related skills

相关Skill

  • /sales-cadence
    — Design outbound cadence strategy and content
  • /sales-smartlead
    — Smartlead platform help (SmartSenders, SmartInfra, SmartDelivery, campaigns)
  • /sales-lemlist
    — Lemlist platform help (sequences, Lemwarm, enrichment, LinkedIn automation)
  • /sales-mailshake
    — Mailshake platform help (campaigns, Lead Catcher, settings)
  • /sales-apollo-sequences
    — Apollo sequence mechanics and configuration
  • /sales-salesloft
    — Salesloft platform help
  • /sales-agency-outbound
    — Multi-client agency outbound — infrastructure, client isolation, warmup at scale
  • /sales-yesware
    — Yesware platform help (inbox-native sending, campaigns, tracking)
  • /sales-mixmax
    — Mixmax platform help (for Mixmax-specific setup)
  • /sales-reply
    — Reply.io platform help (for Reply.io-specific setup)
  • /sales-woodpecker
    — Woodpecker platform help (for Woodpecker-specific setup)
  • /sales-email-tracking
    — Email engagement tracking — understand open/click accuracy and privacy limitations
  • /sales-enrich
    — Verify and enrich contact emails before sending
  • /sales-prospect-list
    — Build prospect lists with verified contacts
  • /sales-do
    — Not sure which skill to use? The router matches any sales objective to the right skill.
  • /sales-cadence
    — 设计外呼节奏策略与内容
  • /sales-smartlead
    — Smartlead平台帮助（SmartSenders、SmartInfra、SmartDelivery、活动）
  • /sales-lemlist
    — Lemlist平台帮助（序列、Lemwarm、数据 enrichment、LinkedIn自动化）
  • /sales-mailshake
    — Mailshake平台帮助（活动、Lead Catcher、设置）
  • /sales-apollo-sequences
    — Apollo序列机制与配置
  • /sales-salesloft
    — Salesloft平台帮助
  • /sales-agency-outbound
    — 多客户代理外呼——基础设施、客户隔离、规模化预热
  • /sales-yesware
    — Yesware平台帮助（收件箱原生发送、活动、跟踪）
  • /sales-mixmax
    — Mixmax平台帮助（Mixmax专属配置）
  • /sales-reply
    — Reply.io平台帮助（Reply.io专属配置）
  • /sales-woodpecker
    — Woodpecker平台帮助（Woodpecker专属配置）
  • /sales-email-tracking
    — 邮件互动跟踪——了解打开/点击数据的准确性与隐私限制
  • /sales-enrich
    — 发送前验证与丰富联系人邮箱
  • /sales-prospect-list
    — 构建包含已验证联系人的潜在客户列表
  • /sales-do
    — 不确定使用哪个Skill？该路由会将任何销售目标匹配到合适的Skill。

Examples

示例

Example 1: New domain setup

示例1：新域名搭建

User says: "I'm setting up a new domain for cold outbound. What do I need to do?" Skill does:
  1. Recommends a dedicated outbound domain (separate from primary)
  2. Provides SPF/DKIM/DMARC setup instructions with example DNS records
  3. Outlines the warmup schedule (weeks 1-5)
  4. Recommends warmup tools and verification steps Result: User has a complete domain setup and warmup plan
用户提问：“我正在为冷外呼搭建新域名。需要做什么？” Skill操作：
  1. 推荐使用专用外呼域名（与主域名分离）
  2. 提供SPF/DKIM/DMARC配置说明及示例DNS记录
  3. 列出预热时间表（第1-5周）
  4. 推荐预热工具和验证步骤 结果：用户获得完整的域名搭建和预热计划

Example 2: Diagnosing a deliverability drop

示例2：送达率下降诊断

User says: "My open rates dropped from 45% to 15%. I'm using 3 Apollo mailboxes at 50 emails/day each." Skill does:
  1. Identifies likely causes: reputation damage, blacklisting, or auth issues
  2. Provides a diagnosis checklist: check blacklists, verify SPF/DKIM/DMARC, review bounce rate
  3. Recommends volume reduction and mailbox-by-mailbox reputation check
  4. Creates a recovery plan with timeline Result: User has a diagnosis framework and recovery plan
用户提问：“我的打开率从45%下降到15%。我使用3个Apollo邮箱，每个每日发送50封邮件。” Skill操作：
  1. 识别可能的原因：信誉受损、被列入黑名单或认证问题
  2. 提供诊断清单：检查黑名单、验证SPF/DKIM/DMARC、查看退信率
  3. 建议降低发送量并逐个检查邮箱信誉
  4. 制定包含时间线的恢复计划 结果：用户获得诊断框架和恢复计划

Example 3: Platform migration

示例3：平台迁移

User says: "Switching from Apollo to Mailshake. What do I need to do for deliverability?" Skill does:
  1. Verifies domain auth is platform-independent (SPF/DKIM may need updating for Mailshake)
  2. Recommends adding Mailshake to SPF and configuring Mailshake-specific DKIM
  3. Advises warmup for new platform connection even if mailbox is established
  4. Compares sending limit configuration between platforms Result: User has a migration checklist covering auth, warmup, and platform config
用户提问：“从Apollo切换到Mailshake。送达率方面需要做什么？” Skill操作：
  1. 确认域名认证与平台无关（SPF/DKIM可能需要更新以适配Mailshake）
  2. 建议将Mailshake添加到SPF中，并配置Mailshake专属的DKIM
  3. 建议即使邮箱已成熟，连接新平台后仍需进行预热
  4. 对比两个平台的发送限制配置 结果：用户获得涵盖认证、预热和平台配置的迁移清单

Troubleshooting

故障排除

Emails landing in spam

邮件进入垃圾邮件箱

Symptom: Recipients report emails in spam, or open rates are very low (<15%) Cause: Missing/broken domain auth, poor sender reputation, content triggers, or shared tracking domain Solution: Run full auth check (SPF/DKIM/DMARC). Test with mail-tester.com. Set up custom tracking domain. Check blacklists. If reputation is damaged, reduce volume and re-warmup.
症状：收件人反馈邮件在垃圾邮件箱，或打开率极低（<15%） 原因：域名认证缺失/损坏、发件人信誉不佳、内容触发垃圾邮件规则或使用共享跟踪域名 解决方案：运行完整的认证检查（SPF/DKIM/DMARC）。使用mail-tester.com测试。配置自定义跟踪域名。检查黑名单。如果信誉受损，降低发送量并重新预热。

High bounce rate

退信率过高

Symptom: Bounce rate above 3% Cause: Unverified email list, stale data, or sending to catch-all domains Solution: Immediately pause affected campaigns. Run remaining list through email verification (NeverBounce, ZeroBounce). Remove all invalid addresses. Only resume with verified addresses.
症状：退信率超过3% 原因：未验证的邮件列表、过期数据或发送到全域域名 解决方案：立即暂停受影响的活动。使用邮件验证工具（NeverBounce、ZeroBounce）检查剩余列表。移除所有无效地址。仅使用已验证的地址恢复发送。

Blacklisted domain

域名被列入黑名单

Symptom: Widespread delivery failures, MXToolbox shows blacklist hits Cause: High bounce rate, spam complaints, or sending to spam traps Solution: Stop all sending. Identify and fix root cause. Submit delisting requests to each blacklist. Wait 24-48 hours. Re-warmup before resuming. If severely blacklisted, consider a new outbound domain.
症状：大范围送达失败，MXToolbox显示被列入黑名单 原因：退信率过高、垃圾邮件投诉或发送到垃圾邮件陷阱 解决方案：停止所有发送。识别并修复根本原因。向每个黑名单提交移除请求。等待24-48小时。重新预热后再恢复发送。如果严重被列入黑名单，考虑更换新的外呼域名。