Rotation Is the Whole Game When Your Prospects Run the Filters
Cold-emailing security companies means sending into inboxes protected by the very products your prospects build, deploy, or manage all day. The gateways guarding those inboxes don't just score individual messages — they profile sending patterns: how many emails a domain pushes per day, how similar the bodies look, how fast volume ramps. A pattern that sails into a normal B2B inbox gets a security company's gateway interested for all the wrong reasons.
That's why, for this audience more than any other, the deciding variable isn't your subject line — it's how thinly your volume is spread. Smartlead's campaign-level mailbox rotation is built for exactly that: you attach a pool of mailboxes to a campaign and Smartlead distributes every send across the pool automatically. ColdRelay supplies the pool itself — the secondary domains, mailboxes, and dedicated IPs that rotation distributes across. This guide covers how to size that pool for rotation depth, wire it into Smartlead, and keep per-campaign deliverability honest against the hardest filters in B2B.
Why Run Smartlead on ColdRelay Infrastructure
Smartlead's rotation engine is only as good as the pool it rotates across. Rotation spreads volume; it doesn't create reputation. If the mailboxes in the pool share an IP, sit on the same tenant, or carry sloppy DNS, a strict gateway treats the whole pool as one sender — and rotating across fifty mailboxes that look identical buys you nothing.
ColdRelay builds the pool rotation actually needs: dedicated mailboxes on isolated Azure tenants with dedicated IPs, each domain with SPF, DKIM, and DMARC pre-configured, provisioned in about an hour. Because every mailbox carries its own standing, Smartlead's rotation genuinely diversifies what the receiving gateway sees — many small, well-authenticated senders instead of one big suspicious one. ColdRelay supports 100-150 mailboxes per domain, so building a deep pool doesn't mean managing a sprawl of domains.
The pairing is additive, not competitive: ColdRelay is the infrastructure layer — domains, mailboxes, dedicated IPs — and Smartlead is the sending and sequencing layer that rotates across it. You keep Smartlead's campaign builder, spintax, and Master Inbox; you just give its rotation a pool worth rotating.
Visit Smartlead →Connecting ColdRelay Mailboxes to Smartlead
Provision a deeper pool than the volume math suggests
Work backwards from your daily target, then add headroom. At 2 outbound sends/day per mailbox (each mailbox sends 4/day total — 2 outbound + 2 warmup), 100 sends/day needs 50 mailboxes — but for security-buyer audiences, provision 30-50% more so rotation can rest mailboxes and you can swap out any that a gateway sours on. ColdRelay supports 100-150 mailboxes per domain, and the whole pool spins up on isolated Azure tenants with dedicated IPs in about an hour, DNS pre-configured.
Bulk-import the pool under Email Accounts
Export the mailbox list with SMTP/IMAP credentials from the ColdRelay dashboard, then in Smartlead go to Email Accounts and use the bulk CSV import. The full pool connects in one upload, so a 60-mailbox pool takes minutes to wire up rather than an afternoon of one-by-one connections.
Cap each account at 2 outbound/day and skip extra warmup
Set every account's daily campaign limit to 2 outbound emails — mirroring ColdRelay's per-mailbox budget of 4 sends/day total, split 2 outbound + 2 warmup. ColdRelay's warmup runs continuously as part of that budget, so there's no separate warmup period before launch; conservative per-mailbox volume is precisely what keeps you under the ramp-detection thresholds strict gateways watch.
Attach the full pool and let campaign-level rotation spread the load
In your Smartlead campaign settings, attach every mailbox in the pool to the campaign. Smartlead's campaign-level rotation then distributes each day's sends across the whole pool automatically — no single mailbox or domain ever shows a gateway more than a trickle. Add spintax to your templates here too, so rotated sends vary in body as well as in sender.
Monitor deliverability per campaign and triage replies in the Master Inbox
Watch each campaign's bounce and reply metrics in Smartlead as a per-campaign deliverability signal — a bounce uptick in one campaign usually means one list segment or one domain is in trouble, not the whole pool. Pause affected mailboxes, replace them from ColdRelay, and keep working replies in the Master Inbox, where the entire rotated pool's responses land in one view.
The Cybersecurity Smartlead Playbook
Spread thinner than the gateway can profile
Enterprise gateways flag senders on velocity and concentration — one domain pushing 40 emails into one company's mail flow is a pattern; six domains sending 2 each over three days is weather. Size your ColdRelay pool and your Smartlead rotation so that no single domain ever delivers more than a handful of messages to any one target organization per week.
Break the template fingerprint with spintax
Security filters hash message bodies and cluster near-duplicates across recipients — fifty identical pitches from rotating senders still look like one campaign. Use Smartlead's spintax support to vary openers, phrasing, and sign-offs per send, so rotation diversifies the content fingerprint along with the sending identity.
Treat mailboxes as rotating units, not permanent assets
Against this audience, some mailboxes will get flagged no matter how clean the setup — assume it and build for it. Review per-campaign bounce signals in Smartlead weekly, pull soured mailboxes out of rotation immediately, and backfill from ColdRelay; the headroom you provisioned in step one exists exactly for this swap-and-continue motion.
Quarantine list segments into separate campaigns so one bad list can't poison the pool
A scraped list with stale addresses will spike bounces and drag down every mailbox attached to its campaign. Run each data source as its own Smartlead campaign with its own slice of the ColdRelay pool — when a segment goes bad, its blast radius is the mailboxes assigned to it, not your entire sending operation.
Typical Cybersecurity Outbound Benchmarks (Smartlead + ColdRelay)
| Metric | Benchmark | Notes |
|---|---|---|
| Inbox placement rate | 95%+ | Dedicated IPs and isolated tenants per mailbox give rotation real diversity instead of one shared reputation |
| Reply rate | 1.5-3% | Security buyers are the most skeptical audience in B2B; thin, well-rotated volume keeps you at the top of the range |
| Outbound capacity per mailbox | 2/day | 4 sends/day total per mailbox — 2 outbound + 2 warmup |
| Pool headroom over raw volume math | 30-50% | Extra mailboxes let rotation rest senders and replace any a strict gateway flags, without pausing campaigns |
| Time to first campaign | Same day | ~60 minutes to provision on ColdRelay, plus bulk CSV import and campaign setup in Smartlead |
What It Costs: Smartlead + ColdRelay
You pay per mailbox per month for the infrastructure, with volume tiers that drop as you scale (see the table below). Dedicated IPs, isolated Azure tenants, and pre-configured DNS are included — so deepening the pool for rotation headroom gets cheaper per mailbox as it grows.
Smartlead is billed separately on its own subscription for the campaign builder, mailbox rotation, spintax, and Master Inbox — priced per its current plans.
Infrastructure cost scales with pool depth; Smartlead's cost scales with its plan tier. Since rotation strategy against security gateways favors more mailboxes at lower per-mailbox volume, the volume-tiered infrastructure pricing works in the same direction as the deliverability strategy.
| Mailboxes | ColdRelay price / mailbox / month |
|---|---|
| 1–199 | $1.00 |
| 200–999 | $0.85 |
| 1,000–4,999 | $0.70 |
| 5,000+ | $0.55 |
Each mailbox sends 4 emails per day — 2 outbound to prospects + 2 warmup. ColdRelay provisions mailboxes on isolated Azure tenants with dedicated IPs; Smartlead handles the sending, sequencing, and inbox rotation on top.
Frequently Asked Questions
Does ColdRelay replace Smartlead?
No — they're complementary layers and you use them together. Smartlead is the sending and sequencing layer: campaigns, mailbox rotation, spintax, the Master Inbox. ColdRelay is the infrastructure layer underneath: the secondary domains, mailboxes, and dedicated IPs that Smartlead's rotation distributes sends across. Neither does the other's job.
Isn't Smartlead's mailbox rotation enough on its own to get past security gateways?
Rotation spreads volume; it doesn't create reputation. If the pool's mailboxes share IPs or tenants, a strict gateway scores them as one sender and rotation changes nothing. Rotation works against security-company filters when each mailbox in the pool carries its own standing — dedicated IP, isolated Azure tenant, clean SPF/DKIM/DMARC — which is exactly what ColdRelay provisions.
Do ColdRelay mailboxes need a warmup period before we launch Smartlead campaigns?
No separate warmup period. Warmup runs continuously as part of each mailbox's 4 sends/day budget — 2 outbound + 2 warmup — so the pool is campaign-ready the day it provisions. Cap each account in Smartlead at 2 outbound/day and leave the warmup side to ColdRelay rather than double-warming inside Smartlead.
We're an agency running outbound for several security clients — how does this setup handle that?
Cleanly, on both layers. In Smartlead, give each client their own sub-account so campaigns, rotation pools, and the Master Inbox stay separated, and use the API and webhooks for white-label reporting. On ColdRelay, provision each client their own domains and mailbox pool — one client's flagged segment can never bleed into another client's deliverability, which matters doubly when the clients are security companies who will notice.