How to run cold email without burning your domain.
Deliverability is not a setting. It is the sum of what you send, to whom, and what happens when it goes wrong. These are the seven mechanisms Rainmaker runs on every send, in order.
- 01
Verify every address before it is contacted
A bounced email is the fastest way to lose a sending reputation. Every recipient address goes through verification before a draft is even written, and addresses that fail are never contacted. A vouch from you cannot override a provider that has flagged a specific problem with an address.
- 02
Write only what can be sourced
Spam complaints follow emails that read as generated and get something wrong. Every factual sentence in a Rainmaker draft must link to a live source or the draft is blocked before it reaches you. Fewer invented claims means fewer recipients reaching for the spam button.
- 03
Hold the batch for a human
Nothing sends without your approval. The agent assembles a batch of sourced drafts and waits. You read them, edit or reject any, and approve the rest. Autopilot is an explicit opt-in with a daily budget cap, never the default.
- 04
Send from a managed address, under a budget
By default outreach goes out from a managed sending address Rainmaker operates for your workspace, not from the domain your company runs on. Daily send budgets cap volume per workspace, so a campaign cannot run away on a bad day.
- 05
Add the CAN-SPAM footer, every time
The gatekeeper adds clear sender identification, a physical postal address, a working unsubscribe link, and RFC 8058 List-Unsubscribe headers to every email. No email may leave without them; a send with a missing address is blocked, not patched.
- 06
Watch bounces and complaints, and stop
Bounce and complaint rates are monitored on the sending identity. When either crosses its threshold, active campaigns pause automatically and stay paused until a human has looked. The circuit breaker protects the account, not just one campaign.
- 07
Honor every opt-out, everywhere
An unsubscribe adds the address to a permanent opt-out registry shared across every Rainmaker account. Rights requests use double opt-in, so nobody can suppress or delete someone else's address, and Global Privacy Control signals are honored as opt-outs.
The legal side of the same question, CAN-SPAM, GDPR, opt-out and privacy mechanics, is on the compliance page. What it costs is on the pricing page.
Cold email without the damage.
The questions founders ask after their first burned domain, answered with the mechanisms that prevent the second one.
How do I run cold email without burning my domain?
Send fewer, better-targeted emails, verify every address before you send, keep bounce and complaint rates low, and stop the moment they rise. Rainmaker enforces each of those steps: every recipient address is verified first, campaigns pause automatically when bounce or complaint thresholds are breached, daily send budgets cap volume, and nothing sends without your approval.
Does Rainmaker send from my primary domain?
Only if you connect your own mailbox and choose to. By default Rainmaker sends from a managed sending address it operates for your workspace, so a bad day of outreach cannot damage the domain your company runs on. Replies still reach your inbox.
What is a safe bounce or complaint rate for cold email?
Mailbox providers start filtering aggressively when spam complaints pass roughly 0.1 percent of delivered mail, and high bounce rates signal a scraped or stale list. Rainmaker watches both on the sending identity and pauses active campaigns when a threshold is crossed, so the numbers are corrected before a reputation is lost rather than after.
Why does approving every email protect deliverability?
Because the emails that get marked as spam are the ones that read as generated and get a fact wrong. Rainmaker blocks any sentence it cannot source, then holds the whole batch for you to read before it sends. Recipients get fewer, more accurate emails, and fewer of them reach for the spam button.
What happens when someone unsubscribes?
Every email carries a one-click unsubscribe link and RFC 8058 List-Unsubscribe headers. When a recipient uses it, their address is added to a permanent opt-out registry shared across every Rainmaker account, so no other workspace can contact them either.
Is cold email spam?
Not when it is sent to a business address, is relevant to the recipient's role, identifies the sender honestly, includes a postal address, and honors unsubscribes immediately. That is the CAN-SPAM standard in the US and the legitimate-interest standard under GDPR. Rainmaker's gatekeeper adds the identification, address, and unsubscribe mechanics to every email; the relevance comes from the buyer persona and the source check.