Folio vs. Gmail aliases

'Send as' is a setting.
Multi-identity is a premise.

Gmail's 'Send mail as' aliases route every outbound message through Gmail's servers under one shared sending reputation, and recipients often see a 'via gmail.com' line in the From header. Folio treats each domain as a first-class sending identity with its own DKIM key, its own SES sending principal, and no via-line — so client mail looks like client mail, not a forwarded alias.

Gmail aliases let you send from several addresses. That's a useful escape hatch — it is not the same thing as an inbox built around multiple identities.

Here's the feature-by-feature read, plus the reading-surface, reputation, and price trade-offs that matter once you're running more than one business from one head.

Updated 11 May 2026 (2026-05-11)

Start free — no cardSee the price

I · The verdict

In one sentence.

Gmail aliases are fine if you run one company and occasionally send from a vanity address. The moment you run two or more businesses, the abstraction cracks: replies come from the wrong address, threading collapses, DKIM doesn't match the domain on the envelope, and deliverability becomes a Googleable problem.

II · Feature by feature

Feature by feature.

CAPABILITYGmail · Send asFolio
  1. How many identities, practicallyUp to ~30 'Send as' addresses, but managed in Settings → AccountsUnlimited. Each bound domain is a first-class identity in the sidebar.
  2. Reply From auto-selected from received addressYes, when the reply-to is configured — fragile across edge casesAlways. Derived from the original envelope, not a setting
  3. Margin colour per identityNone — all mail is visually identicalDeterministic colour per domain, on every row, every letter
  4. DKIM signed by the sending domain's keyOnly if you've set up SMTP relay with your own serverAlways. Per-domain RSA-2048 key, encrypted at rest
  5. Separate sending reputationsShared — a bounce on one 'Send as' can affect othersIsolated — each domain has its own reputation and suppression list
  6. Keyboard shortcutsMature, decades-refinedAdequate, not the product's focus
  7. SearchIndustry-leadingBasic today; OpenSearch Serverless planned
  8. Host 3 custom domains, 1 person$0 on consumer Gmail can 'Send as' those addresses but can't host the domains (no MX/mailbox); Workspace hosts all 3 on one ~$7/mo seat (shared identity & reputation)$2.99/month — one flat subscription, every domain a first-class identity
  9. Sign-inPassword + 2FA, recovery via phone or backup codeMagic-link or passkey — no password, no SMS recovery

III · A deeper look

The reply-From problem, specifically.

Gmail's Send as relies on a server-side match between the recipient address and a configured alias. When it works, replies go out from the expected From. When it doesn't — which happens whenever the original message's Reply-To header disagrees with the To header, or the address is a forward from another provider — replies go out from your canonical Gmail address.

That misfire is harmless for a vanity alias. It is catastrophic for a consultancy replying to procurement from what looks like a personal Gmail address. Folio's reply-From derives from the envelope recorded at ingest, not a setting at send time.

In short: Gmail's model is opt-in substitution. Folio's is opt-out override. The default matters.

IV · A deeper look

Why DKIM per domain isn't optional.

Gmail aliases send through smtp.gmail.com. The DKIM signature on that outbound is signed with gmail.com's key, not your domain's. Most mail servers are polite about the mismatch; a handful (and an increasing number of enterprise SMTP gateways in the DMARC era) are not.

The workaround is to configure Gmail's SMTP relay with your own server, at which point you're running a sending server anyway. At that point the question becomes: why was Gmail the abstraction in the first place?

Folio signs every outbound with the sending domain's own DKIM key — generated at bind, encrypted at rest, rotated via the admin flow. No relay, no mismatch, no enterprise-gateway rejects.

V · A deeper look

Threading collapses when the From is wrong.

A reply that goes out with the wrong From breaks threading at every downstream client. Gmail folds the response into the wrong thread (or opens a new one). Outlook opens a new thread. Apple Mail opens a new thread. Your counterpart sees two emails from you when there should have been one continuous exchange.

Folio sets In-Reply-To and References on every outbound, with the sender derived from the received envelope. The thread folds. Your counterpart sees the exchange as a single conversation.

Common questions

Questions readers ask.

What is the 'via gmail.com' line, and why does it appear on alias mail?

When Gmail sends on behalf of a non-Gmail address using 'Send mail as,' the message passes through gmail.com SMTP and many mail clients display 'from you@yourbrand.com via gmail.com' to make the routing visible. RFC 5322 plus modern client conventions surface this whenever the envelope sender domain differs from the From-header domain.

Can Gmail aliases be DKIM-signed by my own domain?

Only if you configure SMTP relay through your own outbound server — which most alias users never do. The default 'Send mail as' path signs with Gmail's keys, not your domain's, so DMARC alignment falls back to relaxed SPF rather than strict DKIM-by-the-sending-domain.

How is Folio different from Gmail aliases?

Folio is built around multiple sending identities from day one. Each bound domain gets its own RSA-2048 DKIM key, its own SES sending identity, its own bounce reputation, and its own color stripe in the inbox. Reply From is auto-selected per inbound recipient — no toggle, no manual override.

Will my recipients notice the difference?

Yes — header inspection shows messages from Folio are DKIM-signed by your domain (d=yourbrand.com) and pass DMARC strictly. Most Gmail-alias outbound is DKIM-signed by d=gmail.com instead, which is what trips the 'via' display in clients like Apple Mail and Outlook.

Can I keep using Gmail for personal mail while using Folio for business domains?

Yes. Many users run Gmail for their @gmail.com address and Folio for every owned business domain. The two services don't conflict — DNS for your business domains points at Folio; the @gmail.com account stays with Google.

Sources & further reading

Where the claims come from.

Adjacent comparisons

Other head-to-heads.

Open the first letter

Try it as an actual inbox.

Start free, no card. Bind one domain you currently alias on Gmail. Send a test from it. Watch the From land correctly, the DKIM signature match the domain, and the colour stripe confirm the identity before you've even read the subject. Upgrade when you want to bring the rest of your aliases in.

Start free — no cardRead the FAQ

Updated 11 May 2026 (2026-05-11)