Meet the build
Our own sending tenant, bought on September 4, 2026, to run cold outreach inboxes we control end to end, instead of renting inboxes from resellers whose tenants we cannot see inside.
The challenge
Most teams either buy reseller inboxes and never see the tenant, or set up a tenant quickly and leave the DNS at the weakest settings: SPF soft, DMARC at p=none, DKIM half-configured. Those settings pass a casual glance and quietly cap deliverability for months, and nobody notices until campaigns underperform and the domain's reputation is already spent.
The solution
Shared mailboxes, one spare license
Nine inboxes were built as unlicensed shared mailboxes across 3 domains, 3 per domain, with roles and profile photos set properly, so the estate carries no per-inbox license cost. The provisioning trick is worth writing down: the tenant holds 2 Business Basic licenses. One runs the admin user. The second was assigned to provision a mailbox, pulled back, and reused for the next one, nine times over, at 1 to 5 minutes per mailbox, and it sits spare in the pool today. When the build finished, the tenant held 25 mailboxes in total, 24 shared and 1 user mailbox, across 9 domains.
The strict version of the DNS spec, on every domain
MX at priority 0. SPF ending in -all, the hard fail, not the soft one. DMARC at p=quarantine with pct=100 from day one, not the usual p=none placeholder. Autodiscover in place. Both DKIM CNAMEs published per domain, with DKIM signing enabled and showing Valid in Microsoft Defender for all 3 domains.
Verified on public DNS, not on hope
Every record was checked live through public DNS lookups the same day, and only then were the inboxes connected to the sending tool over OAuth.
The results
The tenant was bought on September 4, 2026. Three domains were added and ownership-verified, accounts were created on October 14, and the full DNS set was verified live the same day. All 9 inboxes were connected to the sending tool and warmup started on October 15.
The detail that matters most: DMARC enforcement at quarantine from day one. Almost every inbox setup we audit starts at p=none and stays there. This estate never had a p=none day.
The return: nine sending inboxes with no per-inbox license cost at all, running on infrastructure we own outright. The reseller version of this same estate rents by the month, forever, as the teardown study on this page shows. This one was a one-time build with a one-time cost.
FAQ
Shared mailboxes or licensed users?
For sending infrastructure, unlicensed shared mailboxes do the job and remove the per-inbox license cost entirely. We proved they connect and send from real sending tools in the teardown study on this page.
Why DMARC at quarantine from day one?
p=none only watches; it stops nothing. Quarantine tells receivers to treat spoofed mail as suspicious from the start. Setting it at build time, before any sending, means the domain never spends a day unprotected.
How many domains should one tenant hold?
Our working structure is about twelve domains with three inboxes each per tenant, scaling by adding tenants rather than stuffing more domains into one. It keeps any single tenant's blast radius small.
