A 60,000-contact client newsletter can go out on five domains, each one carrying 12,000 messages, each one clearly the client's brand, each one authenticated and warmed. If one mailbox provider throttles one of those domains on send day, you lose part of one fifth of the campaign. The client's invoices, password resets and replies from their main domain keep landing as normal. That's what multi domain email campaign distribution gets you when you set it up properly.
Be clear on what it doesn't do. Spreading volume doesn't trick spam filters, and it won't hide a bad list or a send nobody asked for. Mailbox providers see through that fast. What it does is limit how far the damage from one bad send spreads. That only works if every extra domain is a real extension of the client's brand, not a disposable lookalike registered to soak up complaints.
This guide sets it up in the order that matters. Brand first, authentication second, warmup third, volume last. It's written for agencies running large client sends in the week of 11 March 2024, a month after the new bulk sender rules started being enforced. Each step gives you the action, what you should see and the mistake to avoid.
By the end you will have one large client send split safely across several sending domains
You'll finish with a client campaign of tens of thousands of contacts spread over 3 to 5 brand-matched domains. Each domain will pass authentication, have its own warmup history and send at a pace set per mailbox provider. The client's root domain stays out of the bulk pool entirely.
Get these in place before you start, because the steps stall without them.
- Access to the client's DNS, or a named person on their side who can add records the same day you send them.
- The client's written sign-off on the domain names. They're the client's brand, so the client approves them.
- A list you're ready to clean. You'll verify it in Step 5, but know where every segment came from now.
- A SendTo partner account with the client set up under your brand.
- Two to four weeks before the big send. New domains need that long to warm, and nothing speeds it up safely.
Why one domain carrying the whole send is a single point of failure
Mailbox providers keep score per sending domain. Every bounce, complaint, open and deletion gets tied to the domain in the From address and the domain that signed the message. Put 60,000 messages through one domain in an afternoon and you've staked all of that score on one send.
When that send goes wrong, say a stale segment complains more than usual, the provider throttles or defers mail from the domain. Deferral means the receiving server says "try later", and the messages queue. If the bulk send shares a domain with the client's everyday mail, those invoices and password resets sit in the same queue. A newsletter problem turns into a customer service problem by Tuesday morning.
The stakes went up in February 2024. Large mailbox providers began enforcing rules for bulk senders. You now need SPF and DKIM authentication plus a DMARC record, one-click unsubscribe on marketing mail, and a spam complaint rate kept well under 0.3%. A domain that drifts over that line sees its mail filtered or rejected. That's why it pays to spread the risk across several domains.
So, will providers read extra domains as an attempt to dodge filters? Not when each one is plainly the client's brand, fully authenticated and warmed with real engagement. Providers punish domains that hide who's sending, rotate away from complaints or appear from nowhere at full volume. Brand-matched domains with clean histories look like what they are, a business separating its mail streams.
Step 1: Size the send and decide how many domains it actually needs
Start with three numbers. The total list size after cleaning, the share of recipients at each major mailbox provider, and how often the client sends. A client mailing 50,000 people once a month needs a different setup from one mailing 50,000 people twice a week.
Here's a rule of thumb we work from. Once warmed, keep each domain's daily load modest, roughly 10,000 to 15,000 messages, and add a domain only when the volume needs it. Then check the provider mix. If 70% of the list sits at one provider, that provider sees most of each domain's traffic, so a smaller share per domain matters more.
| Clean list size | Sends per week | Domains in the bulk pool | Volume per domain per send |
|---|---|---|---|
| Up to 15,000 | 1 | 1 | Up to 15,000 |
| 15,000 to 40,000 | 1 to 2 | 2 to 3 | About 10,000 to 13,000 |
| 40,000 to 80,000 | 1 to 2 | 3 to 4 | About 12,000 to 20,000 |
| 80,000 to 150,000 | 1 to 2 | 4 to 5 | About 16,000 to 30,000, split over two days |
For a client asking how to send 3,000 emails at once, the answer is one warmed, authenticated domain and a normal send. Distribution doesn't earn its keep at that size.
What you should see is a simple table like the one above for this client. It shows the clean list total, the number of domains and the volume each one carries per send.
The mistake is adding ten domains to a 15,000-contact list. Each one ends up sending 1,500 messages a month. That's too little traffic to build any reputation, so every domain stays a stranger to the providers. Every domain is also a DNS job and a warmup commitment you'll have to keep up. Add them when the volume asks for them, not before.
Step 2: Choose domains a recipient will recognise as the client's brand
Picture the From line. Pick names a customer of the client would trust at a glance, such as clientname-mail.com, getclientname.com, clientnamehq.com, or a subdomain like news.clientname.com. Our guide to using secondary domains for high-volume client outbound covers the strategy behind these. Here we only need the choice.
A subdomain sits under the client's root, so news.clientname.com is part of clientname.com. A separate registered domain, such as getclientname.com, is its own name with its own reputation. The trade-off looks like this.
| Subdomain (news.clientname.com) | Separate domain (getclientname.com) | |
|---|---|---|
| Recipient trust | Highest, it's visibly the real brand | High if the name is clearly the brand |
| Link to root reputation | Partly shared, trouble can rub off on the root | Kept apart from the root |
| Setup | DNS records on the existing domain | Register, then add a full set of records |
| Best for | Clients with clean history and modest volume | Large or frequent sends where root mail must stay protected |
Our view is to use separate registered domains for the bulk pool on large sends and keep subdomains for smaller, steady programmes. A subdomain reads best in the inbox, but it gives the root less protection.
What you should see is a short list of names the client has approved in writing, each one you'd happily read in a From line yourself. Redirect each new domain's homepage to the client's main site, so anyone who checks finds the real business.
The mistake is choosing random or keyword-stuffed lookalikes, like best-deals-clientnme.com. They read as phishing, recipients report them, and the brand loses its consistent look. A name a customer hesitates over is a name that gets complaints.
Step 3: Authenticate every domain before it sends a single message
Every domain in the pool needs the full set of records, and none of them borrows from the root. Here's what goes on each one.
- SPF, a DNS record listing the servers allowed to send for the domain.
- DKIM, a signature on each message that proves it wasn't altered and ties it to the domain.
- DMARC, a record that tells providers what to do when SPF or DKIM fails. Start at p=none with reporting switched on, read the reports for two weeks, then tighten to quarantine.
- A From address on the same domain that signs the mail, so the checks align.
- A working reply address that a person reads.
- A custom tracking domain, so links point to a branded address instead of a shared one.
- One-click unsubscribe headers on every marketing message.
Alignment is the bit that trips people up. A message can pass SPF and DKIM and still fail DMARC if those checks pass for a different domain from the one in the From line. Match them on every domain.
Can a client have two email providers on the same domain? Yes. Their office mail and their marketing platform can both send for clientname.com, as long as SPF includes both and each signs with its own DKIM key. Keep that root for the office, invoices and password resets, though, and leave it out of the bulk pool. Transactional mail is mail people expect and need, so don't let a newsletter's complaint rate decide whether it arrives.
What you should see is a test message to a mailbox you control from each domain. In the message headers, SPF, DKIM and DMARC all show pass, and they're aligned to the From domain.
The mistake is authenticating the root, forgetting the new domains, and finding out on send day. The second mistake is leaving DMARC off because nothing has broken yet. Since February it's a requirement, so without the record a domain doesn't qualify as a bulk sender at all.
Step 4: Warm each new domain on its own schedule
Warmup is the period when a new domain sends small, growing volumes so mailbox providers learn what normal looks like for it. In SendTo, automated warmup starts on each new sending domain, so you don't build the ramp by hand. Our guide to automated domain warmup for new clients covers how it works. This step only covers what changes when you warm several domains at once.
Domains warm in parallel, but they never share a ramp. Providers score each domain separately, so three weeks of good history on one domain counts for nothing on the domain you added last Tuesday. Start four domains on the same day and they climb together. Add a fifth a fortnight later and it starts from the bottom.
Send the first warmup volume to the client's most engaged contacts, the people who opened or clicked in the last 60 to 90 days. Their opens and replies are what build the domain's reputation. Put a cold segment through a domain in its first week and providers learn that it sends mail nobody wants.
How long before a new domain can carry real campaign volume? Plan on two to four weeks to reach its full share. Allow longer if one provider holds most of the list or the client's engagement runs low.
What you should see is each domain's daily volume climbing steadily, with bounces under about 2%, complaints close to zero and very few deferrals.
Step 5: Clean and suppress the list once, platform-wide, before you split it
Clean the list once, at the top, before you divide it. Import it into SendTo and the spreadsheet columns map automatically. If the upload drops halfway, it picks up where it stopped instead of creating duplicates. Then SendTo verifies every address before anything sends, so dead mailboxes and typos come off before they turn into hard bounces. We cover why that check matters in automated email list verification before agency campaigns.
Suppression is the part that makes multi domain email campaign distribution safe. SendTo applies suppression across the whole platform. When a contact unsubscribes from a message sent on getclientname.com, or hard bounces there, they're blocked on every domain in the pool. That's how you stop an unsubscribed contact getting the next email from a sister domain.
What you should see is a smaller list than the one the client handed over, every address verified, and suppressions applied to all domains, not just one. On a list that hasn't been mailed for a year, losing 10% to 20% is normal. That loss is the point of cleaning.
Step 6: Configure distribution and per-provider pacing in SendTo
With a clean list and warm domains, SendTo spreads the campaign's volume across the client's brand-matched domains. It also sets dispatch speed per mailbox provider and per domain, so no single provider gets a flood from any one domain in a short burst. You don't hand-split the list or schedule the batches.
You still make three decisions. First, which domains go into the pool, and only the ones that have finished warmup. Second, the From name. Keep it identical on every domain, such as "Clientname", so the recipient sees one familiar sender whatever domain carries the message. Third, what stays out. Invoices, password resets, receipts and one-to-one replies stay on the client's root domain and never join the bulk pool.
What you should see is a send plan showing each domain's share and pace. For the 60,000-contact newsletter, it looks something like this.
| Domain | Role | Messages | Pacing |
|---|---|---|---|
| getclientname.com | Bulk pool | 12,000 | Set per provider |
| clientname-mail.com | Bulk pool | 12,000 | Set per provider |
| clientnamehq.com | Bulk pool | 12,000 | Set per provider |
| clientname-news.com | Bulk pool | 12,000 | Set per provider |
| clientnameupdates.com | Bulk pool | 12,000 | Set per provider |
| clientname.com | Root, transactional only | None from this send | Normal daily mail |
The mistake is sending the full load in one burst because the client wants everything out by 9am. Pacing spreads the send over hours so providers see steady traffic. A campaign that takes until mid-afternoon to finish and lands in the inbox beats one that goes out by 9.05 and sits in a deferral queue.
Step 7: Run the large dispatch and read results per domain, not in aggregate
Before launch, SendTo's built-in AI reviewer checks the campaign's subject line, structure, language, links, alignment and basic compliance. That catches the broken link or missing unsubscribe before 60,000 people see it. Fix whatever it flags, then send.

Then watch each domain on its own. Track bounces, deferrals, complaints, and real human opens and clicks. A blended average hides one sick domain. Say four domains sit at a 0.05% complaint rate and one sits at 0.4%. The combined figure is 0.12%, which looks comfortable, while that fifth domain is already over the 0.3% line.
SendTo's reports leave out opens triggered by security scanners, so the open figures you see are people. Our piece on how security scanners skew email open metrics explains where those false opens come from. When opens drop, check where the drop is. If it's on one domain, with deferrals or bounces rising there, that's a deliverability problem. If it's spread evenly across every domain and clicks hold steady, look at the subject line or the segment first.
What you should see is five similar rows, each domain close to the others on bounces, complaints and clicks.
How to tell it worked, and what to do when one domain slips
A successful send leaves five dull, similar rows in the report and a client who never mentions deliverability. Check these after every large dispatch.
- SPF, DKIM and DMARC still pass and align on every domain.
- Inbox placement holds steady from one send to the next.
- Complaints sit well under 0.3% on each domain, not just on average.
- No domain shows a spike in deferrals.
- Root domain mail, such as invoices and password resets, arrives as normal.
If one domain slips, the setup has done its job, because the damage stops at that domain's share. Here's how to recover it.
- Pull the domain from the bulk pool so the next send runs on the healthy ones.
- Cut its volume back to warmup levels.
- Send it only to recent engagers, contacts who clicked or opened without clicking in recent campaigns. Our guide to audience segments built on campaign interaction history shows how to build them.
- Find the cause. Check which list source fed that domain's share, what the content said and how often those contacts were mailed.
- Fix the cause first, then let the domain climb back into the pool over a week or two.
If every domain slips at once, the domains aren't the problem. Extra domains limit how far damage from one bad send spreads, but they don't hide bad sending. When the whole pool drops together, the cause is the list, the content or the frequency. Stop the bulk sends, re-clean the list, mail only your engaged contacts, and fix what's driving the complaints before adding volume back.
If you set up client sends this way, other agencies will want the same platform. SendTo's affiliate programme pays you 20% of the partner subscription each agency you refer pays SendTo, every month they pay it. You never earn a share of what that agency's own clients pay them. Attribution lasts 90 days from the first click, the first touch wins, and commission is paid monthly by PayPal. For what agencies pay, point them to the pricing page.
Refer agencies to SendTo and earn 20% of their partner subscription every month they pay it.
Join the SendTo affiliate programme

