An agency reselling email eventually meets a client who won't send through anyone else's servers. Sometimes it's a compliance requirement, sometimes it's an existing relay they've spent years warming, sometimes it's a policy nobody wants to relitigate. White label SMTP is the arrangement that satisfies them without costing you the relationship: the interface carries your brand, and their mail leaves through their infrastructure.
This page covers how the two settings combine, why the separation is worth having even when no client demands it, and the authentication work that decides whether any of it arrives.
Two Settings That Happen to Compose
White label SMTP isn't a feature with a switch. It's two independent per-domain settings that compose, which is why the combination goes unnoticed.
Branding is configured per domain. Each domain inherits the account default, carries its own brand, or has none. One account can therefore present a different company on every domain it holds — the mechanics are in domain branding.
Sending is also configured per domain. A domain points at managed platform SMTP, at a profile you supply, or at nothing. Profiles are credentials for a relay — hostname, port, username, password — and each domain can point at a different one, covered in custom SMTP per domain.
Set both per domain and you get white label SMTP: forty client domains, forty brands if you want them, and forty distinct sending paths, administered from one login on one subscription.
Why a Client Asks for This
Clients ask for white label SMTP for four reasons, and they're worth distinguishing because only two are negotiable.
Warm IPs they already own. Established sending reputation is genuinely hard to rebuild and easy to lose. A client whose mail currently arrives reliably has an asset, and asking them to abandon it is asking them to take a risk for your convenience.
A contract that names the sending path. Some agreements specify where mail originates. That isn't a preference and you won't argue them out of it.
Existing transactional volume. If the client's application already sends through a provider, routing their correspondence the same way keeps one relationship instead of two.
Institutional caution. The vaguest reason and the most common — somebody senior is uncomfortable with mail leaving through a supplier they haven't vetted. White label SMTP resolves it without a procurement exercise.
The Separation Is Worth Having Anyway
Even where no client insists, white label SMTP protects you from a failure mode that gets expensive at scale.
On one shared path, every client's behavior becomes every other client's reputation. One client's compromised mailbox, one badly judged bulk send, one bounce-heavy campaign — and delivery degrades for the whole book. You then have a problem you can't explain to the clients it's affecting, because the cause belongs to someone else.
Per-domain routing contains that. A problem on one domain stays on that domain, which turns a portfolio-wide incident into a single awkward conversation. For an agency holding forty client domains, that containment is worth more than the configuration costs.
Where the Authentication Work Lands
This is where white label SMTP setups fail, and they fail quietly — mail sends successfully and lands in spam folders.
Sending through the client's relay means the client's DNS has to authorize that relay. Their SPF record must include it, and DKIM signing has to produce a signature that aligns with the From domain. Neither is your DNS to change, so both require the client to act, which is the real project-management cost of this arrangement.
Run a real message through before declaring it done. Send to two major providers and read the headers: SPF pass, DKIM pass, DMARC alignment. All three visible means finished. Any one failing means you've built something that appears to work and doesn't. Our guides to SPF and DMARC alignment cover what needs to be true.
Budget for this per client rather than per project. Forty domains is forty DNS conversations with forty different people who control those records at forty different registrars, and it's the part that takes weeks rather than minutes.
What Stays Yours
Under white label SMTP the client supplies the sending path, and everything their staff actually touch remains branded as you.
Their people log into webmail carrying your logo, your colors and your support address. Mailboxes, aliases, routing and storage are administered from your dashboard. When something breaks, they contact you, because the interface tells them to — which is the point of reselling rather than referring.
The honest limit is that message headers still show where mail was handled, so anyone technical inspecting a message can see the underlying platform. That's true of every white-label email arrangement including ones that don't mention it, and it has never mattered to a client's staff. It occasionally matters to a client's own IT department, and that's a conversation to have early rather than to be surprised by.
What It Costs and Who Pays
White Label Lite is $39 a month or $389 a year, on any mail plan including the free one, and it isn't priced per client. Forty client domains cost the same as four.
The relay is the client's cost, which is a commercial advantage worth naming — you're reselling administration and interface, not sending capacity, so a client with expensive transactional volume doesn't inflate your bill. Your mail plan covers the domain and mailbox counts, so an agency at this scale is usually on Agency at $29 a month for a thousand domains.
That's the whole recurring cost: $68 a month for a branded, multi-tenant mail operation where each client sends through their own infrastructure.
When Not to Do It
Three cases where white label SMTP is the wrong call, and pretending otherwise would cost you.
The client has no relay and you'd be building one. Standing up sending infrastructure for a client who doesn't have it is weeks of warm-up and an ongoing liability. Managed sending exists precisely so nobody has to, and a fresh relay is a downgrade dressed as flexibility.
You'd be supporting infrastructure you can't see. When their relay stops accepting mail, their sending stops and they call you. If you have no visibility into it, you're the accountable party for something you can't diagnose. Agree in advance who investigates.
The client is small and the arrangement is ceremonial. A two-person client asking for their own sending path because it sounds more professional is asking for complexity that will produce a support ticket within a quarter. Managed sending serves them better, and saying so is better business than agreeing.
The pattern earns its place with clients who already own sending and know why they do. For everyone else, the simpler arrangement is also the more reliable one.
