Pillar 03 · Auto-pause spam

Pull burning accounts off the line.

Eight codified rules with severity tiers from warn to pause to replace. When bounce velocity climbs or a DNSBL hits, Mailnurse stops the sends before the campaign goes wider.

Start free → Book a demo
The painful status quo

A bad domain keeps sending until someone notices.

When a sending account starts misfiring — bounce rate climbs, a DNSBL listing lands, complaint rates spike — most agencies discover it after the campaign has already run for hours. By then, the new spam signal has been broadcast wider than necessary, and the recovery curve is longer.

  • Triage rules live in Notion docs, Slack threads, and the founder's memory — not in the system actually monitoring accounts.

  • Two operators on the same fleet apply "when do we pause?" differently. The fleet drifts in ways the dashboard cannot explain.

  • By the time the morning standup catches a burning account, it has been sending for twelve hours.

What Mailnurse does

Eight rules. Three severity tiers. One audit log.

  1. 01

    Codify.

    Mailnurse ships with eight default rules covering the most common deliverability failure modes. Each has a tunable threshold per workspace.

  2. 02

    Evaluate.

    Rules run nightly against every account in your fleet — and continuously for fast-moving signals like bounce velocity. Each evaluation produces an automation-log entry.

  3. 03

    Act.

    Rules emit one of three severity actions: warn (notification only), pause (sending halted, account preserved), or replace (rotation triggered). The action is logged with the rule that fired.

Inside the rules engine

The minimum playbook to run cold email without daily intervention.

Eight default rules.

Bounce velocity, placement drop, blacklist hits, authentication regression, warmup drift, engagement collapse, age mismatch, and fleet anomaly. The minimum playbook to run cold email without a human in the loop every day.

Three severity tiers.

Warn, pause, replace. Each rule resolves to one action; you decide which threshold maps to which tier per workspace.

Automation log.

Every rule evaluation is recorded — when it fired, against which account, with what observation, leading to what action. Audit-trail-grade history; queryable, exportable.

Per-workspace tuning.

Rule thresholds adjust per workspace. The aggressive thresholds appropriate to a fast-burn agency client are not the thresholds for a slow-burn enterprise client. Same rules, different dials.

Auto-pause FAQ

What the rules do, and what you can tune.

What are the eight default rules?
Bounce velocity (sustained climb in hard bounces vs. seven-day baseline), placement drop (inbox-placement percentile falling below threshold), blacklist hits (DNSBL listing count exceeding the workspace tolerance), authentication regression (SPF / DKIM / DMARC failures over a 24-hour window), warmup drift (engagement curve falling below the expected slope), engagement collapse (sustained open-rate or reply-rate decline), age mismatch (send volume exceeding age-banded thresholds), and fleet anomaly (cross-account signal suggesting a workspace-level problem).
Can I add my own rules?
Custom rules are on the roadmap for the Agency tier — not in the initial release. The eight defaults cover the majority of incident types we've seen at the Lanello agency; tunable thresholds give most workspaces enough flexibility.
What does replace actually do?
Triggers the auto-rotation pipeline — the same end-to-end provisioning described on the Auto-rotate page. The burned account is paused; the next pool domain is provisioned, warmed, and handed off; the automation log records the transition.
How are rule evaluations logged?
Every nightly evaluation produces a log entry per account-per-rule — timestamp, account ID, rule ID, the observed value, the threshold, and the action taken. Logs are queryable, exportable, and retained for the workspace's data-retention window.
Pairs well with

Two disciplines that compound this one.

01

Health monitoring

Continuous placement testing, 11-DNSBL probes, warmup vitals every four hours. A composite risk score per account so decay is visible before deliverability collapses.

Read more 02

Auto-rotate domains

When a domain burns, replace it end-to-end: Spaceship → Cloudflare → Workspace → Instantly → warmup. The ten-hour playbook, run while you sleep.

Read more

Care, expressed as precision.

Cold-email infrastructure that watches itself — so you can focus on the campaign, not the chassis.

Start free trial → Book a demo

14-day free trial · No credit card · Instant setup