One Inbox for Multiple Domains: Three Working Setups Compared (2026)

Yes — you can run email for every domain you own (acme.app, northwind.io, vela.studio) from a single inbox, and there are three setups that actually work: forward everything into Gmail and add "Send mail as" for each domain, hold all domains in one provider account where aliases deliver into one mailbox, or use a host built for portfolios where every address on every connected domain lands in one real inbox and replies go out from the right address automatically. What separates them is not receiving mail — that part is easy — but reply identity, deliverability, and what the second and third domain cost you.

Disclosure up front: we make SuperMailOS, a multi-domain email host built around exactly this. The mechanics below apply no matter which route you take. For the provider-and-pricing side of the decision (per-user suites vs. flat-rate hosts, and the DNS records involved), see our guide to email hosting for multiple domains.

The two jobs a one-inbox setup has to do

Most people asking this question only picture the first job:

1. Receive everything in one place. Mail to hello@acme.app, support@northwind.io, and press@vela.studio arrives in one inbox you check once.
2. Reply from the right address. When you answer an email that came to support@northwind.io, the reply has to go out From support@northwind.io — not from a gmail.com address, and not from the wrong brand.

Job 1 is trivial; forwarding solves it. Job 2 is where setups diverge. Support threads from Zoho and HubSpot communities are full of teams that consolidated receiving but then fight with reply identity — agents answering from the wrong brand, or the "sent via" marker appearing next to their address. Judge every option below on both jobs.

Setup 1: Forward into Gmail with "Send mail as"

The free route, and the one most people try first. You forward each domain's addresses to one Gmail account, then configure Gmail's Send mail as for each domain so you can reply as hello@acme.app from inside Gmail. Google's own support threads walk through this: add the domain to your account, set the addresses up as aliases, and connect via SMTP or POP3 fetching.

What works: one inbox, zero new subscriptions, Gmail's search and filtering on top of everything.

Where it breaks:

• The "via" line. When Gmail sends on behalf of a domain it doesn't control well, recipients can see "hello@acme.app via gmail.com" next to your address. It signals to clients that the mail took a detour.
• Deliverability drift. For send-as to authenticate cleanly, each domain needs SPF and DKIM set up to include the sending path. Multi-domain G Suite walkthroughs exist for a reason — they are pages of DNS surgery, and a missed record means your reply lands in the client's spam folder. Forwarded inbound mail has its own problem: forwarding routinely breaks DMARC alignment for the forwarded copy.
• You still need mail hosting somewhere. Gmail doesn't host your domain's mail; it only fetches or receives forwards. Something has to run MX for every domain.

Verdict: fine for personal mail and low-stakes side projects. Risky for anything customer-facing, because the failure mode is invisible — you find out when a reply never gets answered.

Setup 2: One provider account, aliases into one mailbox

The established route. Most business email providers — Zoho Mail, Fastmail, Migadu, Google Workspace — let a single account hold multiple custom domains, with each extra address configured as an alias that delivers into one real mailbox. Mail from every domain arrives together, and replies go out From the address the message was sent to, with that domain's SPF and DKIM behind them.

The economics differ sharply by provider, because the pricing unit differs:

• Zoho Mail bills per user, not per domain — one paid account can host many domains, and adding domains costs nothing extra; only adding people multiplies the bill.
• Fastmail includes multiple custom domains on paid plans (from $60/year for one person) with alias support.
• Migadu prices the account flat, with domains and aliases treated as volume rather than line items.

This route does both jobs: receive-all and correct reply identity, with real per-domain authentication. The trade-offs are the ones operators know from suite products — storage and feature limits per tier, admin consoles designed around a single company rather than a portfolio of brands, and per-user pricing that starts to add up the moment a second person needs to read the same mail across several domains.

Setup 3: A native multi-domain workspace

The newest category: hosts designed for people running several products, where the domain portfolio is the product's core unit rather than an add-on. Folio, Shipmail, and SuperMailOS all sit here. Since we make SuperMailOS, here is concretely how ours works — treat it as a spec for the category:

• Every address on every domain lands in one inbox. You connect a domain, tap the addresses you want on it (hello@, support@, billing@), and each one delivers into a single real inbox with threads, search, labels, and signatures — not a forwarding arrangement.
• Reply as any address on any domain. The From address follows the conversation, which is job 2 solved by default.
• Aliases are free, on every plan. The billing unit is people, not addresses — a pricing model where Pro covers up to 3 domains at $3/mailbox/month and Business takes unlimited domains at $5/mailbox/month (annual billing, 14-day trial without a card). Four products on one Business plan cost the same as one.
• Per-domain verification and deliverability work is included. DNS records come from the mail server's own zone and are verified live before a domain can send; DKIM signs every message, DMARC is parsed and reported per domain, and new domains get a warm-up period. The homepage reports a 99% DMARC pass rate measured continuously across the mail server.

The honest trade-off versus Setup 2: a newer category means fewer years of maturity and smaller ecosystems of integrations and migration tooling than Zoho or Google. If you need a full office suite attached to the mailbox, the big providers are the right answer — the use-cases overview is candid about which portfolios fit.

Keep the brands separate even while you share the inbox

One objection that comes up in operator threads — sometimes for legal reasons — is that some businesses genuinely need separate, isolated inboxes per domain, not one merged view. That is a different requirement than convenience, and no consolidation setup should override it. If you do consolidate:

• Keep authentication per-domain. Each domain needs its own SPF, DKIM key, and DMARC record, so one brand's reputation problem doesn't bleed into the others. Our SPF/DKIM/DMARC explainer covers the mechanics.
• Mirror your address pattern. If hello@ and billing@ exist on one domain, create the same pair on the others; predictability makes a merged inbox navigable.
• Use labels, not memory. A label per domain (or per product) keeps the merged view scannable.
• Migrate one domain at a time. Keep the old provider live until inbound and outbound both verify on the new host, then move the next.

Frequently asked questions

Can I receive email from multiple domains in one Gmail inbox?

Yes — forward each address, or fetch via POP3. Receiving is the easy half. The hard half is replying with correct authentication: Gmail's send-as needs careful SPF/DKIM setup per domain, and poorly configured send-as is a common cause of replies landing in spam, with the "via gmail.com" marker as the visible symptom.

Do I need a separate mailbox for each domain?

No. On multi-domain providers, one person can hold addresses on every connected domain, with aliases delivering into a single mailbox. Microsoft 365 is the exception in practice: its licensing model assigns one license per mailbox, which is why multi-domain operators there often end up consolidating via groups or forwarding instead.

When I reply, does the From address match the domain the email was sent to?

On provider aliases and multi-domain workspaces, yes — the reply goes out From the address that received the message. On forwarded-into-Gmail setups, only if send-as is configured and authenticated for every address; otherwise you end up replying from the wrong address, which is the classic failure that pushes people off the free route.

Is forwarding all my domains to Gmail bad for deliverability?

For inbound mail, forwarding can break DMARC alignment for the forwarded copy. For outbound, Gmail send-as without correct SPF/DKIM on each domain risks the "via" line and spam-foldering. Occasional personal mail survives it; customer-facing addresses deserve a host that sends with proper authentication on every domain.

---

Running several products and want the two jobs done by default? SuperMailOS puts every domain's addresses in one inbox, replies from the right address, and bills per person — aliases free, 14 days free, no credit card. This is the same setup we run across our own portfolio, alongside tools like our PNG to SVG converter guide and Splitwise alternatives comparison.