How Ripe Leads runs cold email: domains, warm-up, authentication and send caps

Why cold email runs on its own domain, never the client's main one

Every client we run cold email for gets sending domains that are separate from their main website domain. A standard setup at full volume is 20 mailboxes spread across 10 sending domains, reaching up to 400 emails a day once the ramp is finished. Those domains never carry the client's website, their main inbox or anything else the business depends on.

The reason is simple: cold email carries risk that a main domain should never absorb. A spam complaint, a bad list segment, a mailbox provider having an off week, any of these can knock a sending domain's reputation down, and that reputation problem stays contained to the sending domain itself. The client's main domain, the one their invoices, their real customer emails and their website sit on, is never in the blast radius. If a sending domain ever needed to be retired and replaced, that happens without touching anything the client's own team relies on.

This is also why we set up multiple domains per client rather than one. Spreading volume across ten domains means no single domain carries the full daily load, which keeps every domain's per-mailbox sending pattern looking like a real person's inbox rather than a mail server.

Warm-up: what it actually is, and why the ramp is slow

A brand new mailbox has no sending history. Mailbox providers such as Gmail and Outlook use that history, how many emails a mailbox sends, how many get opened, how many get marked as spam, how many bounce, to decide whether the next batch from that mailbox lands in the inbox or the spam folder. Warm-up is the process of building that history deliberately and slowly, before the mailbox ever touches a real prospect list.

The ramp has to be slow because mailbox providers are explicitly watching for the opposite pattern: a mailbox that goes from zero emails to hundreds overnight. That jump is the single clearest signal of a spam operation, and it gets a domain's reputation flagged fast. A mailbox that instead starts at a handful of emails a day and rises gradually looks like what it is supposed to look like, a person's account settling into normal use.

We run every mailbox through this ramp before it goes anywhere near a client's actual prospect list. Nothing skips the queue, regardless of how quickly a client wants volume up.

The ramp, in numbers

The drop from a second-month peak down to a steady one to six a day is deliberate, not a slowdown in effort. A mailbox does not need to send at its highest ramp volume forever to produce results. Once a domain has enough warmed mailboxes running in parallel, the total daily volume across all of them, up to 400 emails a day at full setup, comes from breadth across mailboxes rather than pushing any single one past a sustainable rate.

SPF, DKIM and DMARC: three records, in plain words

Every sending domain we use gets all three authentication records in place before it ever sends a cold email. None of the three is optional, and skipping any one of them undermines the other two.

SPF is a published list of which mail servers are allowed to send email on behalf of a domain. When a receiving mail server gets a message, it checks the sending server against that list. A message from a server not on the list looks forged, whether or not it actually is.

DKIM attaches a cryptographic signature to each outgoing message, generated from a private key that only the sending domain holds. The receiving server checks that signature against a matching public key published in the domain's DNS. A valid signature proves the message was not altered in transit and really did originate from that domain.

DMARC sits on top of the other two. It tells receiving mail servers what to do with a message that fails SPF or DKIM, and it gives the domain owner a way to see reports on messages sent using their domain, including any that were not authorized. Without a DMARC record, a domain has no visibility into whether someone else is sending mail pretending to be them.

Ripe Leads runs BIMI on its own domain, ripeleads.eu, which displays our logo next to our own emails in inboxes that support it. BIMI depends on a strict DMARC policy already being in place, so it is a downstream benefit of correct authentication rather than a separate step. This is stated as our own example, not a service applied to every client domain.

Anyone can check whether a domain has these three records set up correctly using the free deliverability checker at ripeleads.eu/#tools. It reads a domain's public DNS and reports its MX, SPF, DKIM and DMARC status. No signup is required.

Why daily caps stay low, even at steady volume

A single mailbox at steady state sends one to six emails a day, not because more capacity does not exist, but because mailbox providers read volume as a behavioral signal, not just a technical limit. A human being sending business email rarely sends more than a handful of first-contact messages to strangers in a single day. A mailbox that consistently sends far more than that, day after day, looks like automated mail regardless of content, and mailbox providers throttle or flag it accordingly.

Keeping each mailbox's daily cap low is what keeps its reputation, and by extension the sending domain's reputation, stable over months rather than degrading after a few weeks. It also limits how much damage a single bad list segment or a wrong subject line can do before it is caught: a mistake made by a mailbox sending six emails a day surfaces and gets corrected fast, long before it becomes a domain-wide problem.

How many mailboxes it takes to reach a given volume

Because each mailbox is capped low, reaching real outbound volume is a function of how many mailboxes are running in parallel, not how hard any single mailbox is pushed. A standard full setup, 20 mailboxes across 10 sending domains, two mailboxes per domain, reaches up to 400 emails a day once every mailbox has completed its ramp and settled into steady state.

That structure is also why the sending domain count matters on its own, separately from the mailbox count. Ten domains means no domain is carrying the reputation risk of the full daily volume by itself, and if one domain needs attention, the other nine keep sending without interruption.

What a bounce or a spam complaint triggers

Every mailbox is monitored for bounces and spam complaints as sending continues. A bounce means the message could not be delivered, often because the address is no longer valid, and a pattern of bounces from one mailbox is treated as a signal to slow that mailbox down or pause it while the underlying list segment is reviewed. A spam complaint means a recipient actively marked the message as spam rather than simply ignoring it, which mailbox providers weight far more heavily than a bounce.

Either signal, past a normal background rate, triggers a response on that specific mailbox: sending is reduced or paused, the triggering list segment is checked, and the mailbox only resumes normal volume once the underlying cause is addressed. This is handled at the mailbox and domain level, so a problem on one domain does not carry over into how the other nine domains in a client's setup are sending.

How a reply gets back to the client

When a prospect replies to a cold email, that reply arrives in the sending mailbox it was sent from, and it is routed through to the client so a real conversation can continue from there. The client sees the reply and can respond directly, or hand it back for us to continue, depending on how that client's workflow is set up. LinkedIn runs the same way alongside email, up to 1,000 actions or messages a month per client, inside LinkedIn's own platform limits, giving a second channel into the same conversation without either channel competing with the other for volume.

What the client does, and what we do

On our side: the sending domains, the mailboxes, the warm-up ramp, the SPF, DKIM and DMARC records on every domain, the daily caps, the bounce and complaint monitoring, and the list itself. Lists are built from public business data, never purchased, on a GDPR legitimate-interest basis with Article 14 disclosure to every contact and every opt-out honored permanently. Pricing for the full setup is EUR 3,750 for the first month, which includes setup, then EUR 2,850 a month after that, cancel anytime, with sending infrastructure, tools and data all included in that price.

On the client's side: almost nothing. A client does not manage mailboxes, does not touch DNS records, and does not need to understand warm-up schedules to get value from the setup. What we ask for is a short onboarding conversation to confirm who the target buyer is and how replies should be routed, and after that, reviewing the replies that come in. We never promise a fixed number of meetings. What we control is the infrastructure and the execution; what a given list and message combination produces is not guaranteed in advance.