Should each domain have its own inbox?

Usually no. One consolidated inbox is easier to actually read and search. Split only when a client or a sellable business genuinely requires isolation.

How do I stop catch-all spam from taking over?

Use a unique address per signup so you can trace and kill leaks, and add one filter that quietly files mail to addresses you never published.

What is the number-one cause of multi-domain email going to spam?

Missing or misconfigured SPF, DKIM, and DMARC on a domain. Every domain needs its own, and they need re-checking whenever you change how you send.

Can I manage a dozen domains from my phone?

Yes, if everything lives in one inbox. The hard part is never the device — it is having mail scattered across many accounts, which consolidation solves.

Workflow

Manage Email Across Multiple Domains with Rules You Can Paste

The twelfth domain does not break your email. The filter you half-remember writing, the catch-all you forgot you switched on, and the client reply that went out from your personal address — that is what breaks it. The fix is not more willpower. It is a small set of rules that run while you are not looking.

Treat a pile of domains the way you would treat a server: give it an operating system. Not a product, not a vibe — a handful of explicit rules, written in real syntax, that file mail, mute noise, kill leaks, and answer as the right identity without asking you first. Below are those rules, copy-paste ready, in both the vendor-neutral standard (Sieve) and Gmail's filter syntax. Steal them and change the domain names.

The rulebook, in Sieve

Sieve (RFC 5228) is the mail-filtering language most self-hosted and privacy-focused inboxes run natively, which makes it the portable way to write these down. Each rule keys on the envelope recipient — the real address a message was delivered to — not the cosmetic To: line, so it holds up against forged headers and BCCs.

# ===== SIEVE RULEBOOK  (RFC 5228 — portable mail rules) =====
require ["fileinto", "envelope", "imap4flags", "mailbox"];

# 1 - File each domain into its own folder
if envelope :domain "to" "studio.com"   { fileinto :create "Studio"; }
elsif envelope :domain "to" "mygame.io" { fileinto :create "Game"; }

# 2 - Quarantine catch-all mail to addresses you never published
if anyof (envelope :domain "to" "studio.com",
          envelope :domain "to" "mygame.io") {
  if not envelope :localpart :is "to"
        ["you", "billing", "support", "hello"] {
    fileinto :create "Catch-all/Unlisted";
  }
}

# 3 - Retire one leaked per-signup address
if envelope :is "to" "shop-xyz@studio.com" { discard; stop; }

# 4 - Flag anything that looks like it needs a human reply
if allof (not exists "Auto-Submitted",
          header :contains "subject" ["?", "quote", "invoice"]) {
  setflag "\\Flagged";
}
# ============================================================

The same four moves in Gmail

If your mail lives in Gmail or Google Workspace, you do not write Sieve — you paste a search string into a filter. The key operator is deliveredto:, which matches the Delivered-To header (the real recipient), so a catch-all typo still files correctly.

# ===== GMAIL FILTERS  (Settings > Filters > Create filter) =====
# Paste each line into "Has the words", then choose the action.

deliveredto:(*@studio.com)                   ->  Label: Studio
deliveredto:(shop-xyz@studio.com)            ->  Delete it
deliveredto:(*@studio.com) -deliveredto:(you@ OR billing@ OR hello@)
                                             ->  Label: Unlisted
subject:(quote OR invoice) -from:(no-reply)  ->  Star it
# ============================================================

What each recipe is doing, and why

Recipe 1 — per-domain folders. The backbone. One lane per domain where context actually matters (client work, anything you bill through). Leave personal and low-volume domains unfiltered; over-filing hides mail you meant to see. A few folders that earn their keep beat a filing cabinet you maintain more than you use.

Recipe 2 — the catch-all quarantine. A catch-all is the biggest time-saver in multi-domain email: anything@yourdomain arrives instead of bouncing, so you stop hand-creating addresses. Its one cost is that spammers eventually guess random names. This rule flips the logic — anything not sent to an address you actually published drops into a side folder, out of your main view, still searchable. Pair it with the habit of giving each signup its own address (shop-xyz@studio.com) so a leak is traceable to the exact service that sold you out.

Recipe 3 — the kill switch. When shop-xyz@ starts getting spam, you know precisely who leaked it, and you retire that one address in a single line without touching anything else. This is the per-use-address payoff made concrete.

Recipe 4 — flag by action, not by sender. "Needs a human reply" is more useful than "from this domain" when you are triaging fast. The rule skips auto-generated mail and flags messages whose subject smells like a real request.

The operating principle: every rule keys on the address a message was delivered to, never the visible To:. That one choice is what keeps a single inbox sorted into as many clean lanes as you have domains. (Why the envelope recipient is the trustworthy field is unpacked in the unified-inbox guide.)

The one rule that is not a filter: reply identity

Filters sort incoming mail; they do not fix the mistake that makes multi-domain email look amateurish — answering you@clientbrand.com and having it leave as you@gmail.com. The rule here is a setting, not a Sieve script: your client must read the address a message arrived on and default the reply's From to that same address, automatically. If your tool makes you pick the "from" by hand on every reply, treat that as a bug in your workflow, because sooner or later you will forget. Note the honest limit: that outbound reply still rides a sending provider, so deliverability of the answer depends on that provider being authenticated for the domain — which is the one piece of plumbing no filter can cover.

The recipient should always see the address they wrote to. If they see anything else, your setup is leaking.

The two-minute maintenance habit

Rules do the daily work; a tiny recurring check keeps the fleet healthy:

When you add a domain: run its authentication — the per-domain MX, SPF, DKIM, and DMARC sequence lives in the onboarding runbook — before you trust it with real mail. Missing or broken auth is the number-one reason multi-domain mail lands in spam.
Every so often: glance at which per-use addresses are getting hammered and fire Recipe 3 at the leaked ones.
Before anything important: campaign or invoice from a rarely used domain? Re-check its auth first with the email authentication checker and DNS tools.

Why self-hosting is the calm substrate for all of this

It sounds backwards, but running your own inbox can be the simplest way to manage many domains — one thing to maintain instead of a dozen accounts, and a mail stack that speaks Sieve natively so the rulebook above is yours to edit. Blue Folder Mail puts unlimited custom domains into a single inbox on your own Cloudflare account, with replies keyed to the right address and mail encrypted at rest with a key only you hold. That encryption is zero-access: the server stores ciphertext and the key derives from your passkey, so the host cannot read your messages. The honest caveats hold — mail arrives as plaintext at the edge and is sealed once it lands, and outbound rides a sending provider — so this is a strong privacy model, not a promise of invincibility. But it means a dozen domains' worth of mail is not handed to someone else to read.

Should each domain have its own inbox?: Usually no. One consolidated inbox is easier to actually read and search. Split only when a client or a sellable business genuinely requires isolation.
How do I stop catch-all spam from taking over?: Use a unique address per signup so you can trace and kill leaks, and add one filter that quietly files mail to addresses you never published.
What is the number-one cause of multi-domain email going to spam?: Missing or misconfigured SPF, DKIM, and DMARC on a domain. Every domain needs its own, and they need re-checking whenever you change how you send.
Can I manage a dozen domains from my phone?: Yes, if everything lives in one inbox. The hard part is never the device — it is having mail scattered across many accounts, which consolidation solves.

#EmailManagement#MultipleDomains#CustomDomainEmail#EmailDeliverability#CatchAllEmail#SelfHostedEmail#DomainManagement