Custom domain email alias: how it works without another inbox

Quick answer for custom domain email alias

Verify the domain, create named aliases into the Gmail you already read, publish exclusive MailerZ MX, delete leftovers, probe. That is a custom domain email alias without another inbox.

The email forwarding alias is hop two. The role address is the public string. Neither is a new mailbox.

Free: ten aliases, hold unknowns, no send-as. Paid send-as still uses the same store.

If you need IMAP on the domain, buy a suite. This page will not grow a login.

MailerZ Free is one domain, ten aliases, one seat, a 14-day store, send-as disabled, SMTP and API disabled, and unrouted mail held or rejected only. Solo is $40 per year only. Starter is $8 monthly or $80 yearly. Business is $19 or $190. Agency is $39 or $390. Unlimited is $99/month or $990/year. Confirm numbers on MailerZ pricing. Limits are not an inbox-placement promise.

Google’s own Send mail as steps live in Google Gmail Help — Send mail from a different address. Workspace as a product is described on Google Workspace — product overview. Transport still follows IETF RFC 5321 — Simple Mail Transfer Protocol.

custom domain alias: the real decision

People skip MX because they already have Gmail.

They add send-as and think inbound exists.

They want a second inbox for finance and buy a seat instead of a second destination.

Criteria: one store unless you chose two destinations, exclusive MX, named map, external probe.

Technical mail flow for custom domain email alias

Lookup, accept named RCPT TO, second SMTP to the existing store, Header From intact.

No extra inbox is created at any hop.

Unknowns hold. A hosted mailbox would have accepted more names by habit.

Desktop IMAP to Gmail is still one inbox.

MailerZ is inbound MX plus authenticated SMTP from Secuno LLC. Envelope SRS only. Header From, Subject, Date, Message-ID, body, and MIME are never rewritten. Not Google Workspace, not IMAP or POP, not an open relay. Unauthorized send is SMTP 550 / 550 5.7.1. Leftover MX is a hard stop. Self-send from Gmail to the same Gmail account can hide routing errors. Not SOC 2, not ISO 27001, not HIPAA.

email forwarding alias

Map first. MX second. Probe third. No new login.

1. Pick the Gmail or Outlook you already use.
2. Verify the domain.
3. Create printed aliases to that store.
4. Publish MailerZ MX. Delete leftovers.
5. Probe from another mailbox.
6. Optional: second destination, not a second product.
7. Send-as only if a From must travel.
8. Document that the domain has no IMAP.

Failure modes and proof

Send-as only, no MX.

Thought Gmail was MX.

Left Workspace MX.

Expected MailerZ webmail.

Self-send.

MailerZ workflow and product boundary

MailerZ is the hop that keeps you at one inbox. Related: aliases and catch-all, email alias service, custom domain email alias, pricing.

Not IMAP or POP. Mail Box is portal webmail. Not an open relay.

Related pages: aliases and catch-all, email alias service, custom domain email alias, and pricing.

role address

Avoided seats are the point. Confirm pricing if send-as or more aliases matter.

A second personal Gmail as destination is still not a suite seat.

MailerZ Free is one domain, ten aliases, one seat, a 14-day store, send-as disabled, SMTP and API disabled, and unrouted mail held or rejected only. Solo is $40 per year only. Starter is $8 monthly or $80 yearly. Business is $19 or $190. Agency is $39 or $390. Unlimited is $99/month or $990/year. Confirm numbers on MailerZ pricing. Limits are not an inbox-placement promise.

Field notes you can reuse

Say store and hop out loud.

Finance can be a second destination.

Hold unknowns.

Agencies: one agency Gmail can be many client maps — still per-zone MX.

Review leftovers after NS moves.

Plus tags are not this alias.

Legal hold is not this design.

The definition article is the word. This article is the missing second inbox.

Deeper field notes for custom domain email alias

Without another inbox means one store, many names

A custom domain email alias works without another inbox because the store is Gmail or Outlook you already search. The domain never gets a second IMAP login. MX points at MailerZ. A named alias matches RCPT TO and opens a second SMTP session to that store. Header From stays the original author. Envelope SRS may change MAIL FROM. That is the hop. Workspace is the other design: another inbox on the domain, another seat, another Calendar.

People hear “without another inbox” and skip MX. A free Gmail account is not an MX target for yourdomain.com. You still verify TXT, publish one MX set, delete leftovers, and probe from another mailbox. No extra inbox is not no DNS.

What the map actually matches

The map matches a local-part you created. hello@ is not billing@. Catch-all is not a missing-name feature. Free holds unknowns. Creating three brochure names is the usual first inbox-saving move. A fourth printed string is a plan conversation. Confirm pricing.

Two destinations on one alias are a copy, not a second inbox product. Name who replies. Do not fan-out catch-all.

Send-as is still not another inbox

Paid SMTP lets the same Gmail send as hello@ without hosting IMAP on the domain. That is still one store. Free cannot finish that hop. Solo is $40 per year when the From must travel. Unauthorized send is 550 / 550 5.7.1. Catch-all does not mint a From.

Desktop clients do not create the extra inbox

Thunderbird talking to Gmail IMAP is still Gmail. The domain has no mailbox. People point at a client and claim they added an inbox. They added a password to a client. The alias still lives in the map.

When you do need another inbox

Admin legal hold, device management, Calendar as the system of record, or a person who must not share a Gmail. Then buy a suite or a second personal store and map the alias there. That is a destination choice, not a requirement of the alias itself.

A complete worked story

Finance wanted “their own inbox”

They were about to buy a Workspace user for billing@. They mapped billing@ to the bookkeeper’s existing Gmail instead. Same public string. No second product. They probed from a vendor. Copies landed. They paid Solo later so the bookkeeper could reply as billing@. Still one inbox per human. No extra seat.

Operator brief

A longer operator brief for custom domain email alias

Teams that bookmark Custom Domain Email Alias: How It Works Without Another Inbox usually arrive after a missed invoice, a form that never notified anyone, or a migration that looked clean in one resolver. The useful brief is still boring. Name the store. Name the printed local-parts. Name the nameservers that actually answer. Publish one MailerZ MX set. Delete leftover hosts. Probe from a mailbox that is not the destination. Only then talk about custom domain email alias as a send-as, catch-all, or comparison problem.

MailerZ remains inbound MX plus authenticated SMTP around Gmail or Outlook. Envelope SRS only. Header From, Subject, Date, Message-ID, body, and MIME stay intact. It is Mail Box portal webmail, not IMAP, not POP, and not an open relay. Unauthorized send is 550 / 550 5.7.1. Free cannot finish send-as: SMTP and API stay off. Solo is $40 per year when the domain From must travel. Starter is $8 or $80. Business is $19 or $190. Agency is $39 or $390. Unlimited is $99/month or $990/year. Confirm the live pricing page. Those numbers are ceilings, not an inbox-placement service-level agreement.

If leftover Google, Microsoft, Cloudflare routing, or registrar MX is still public, stop widening custom domain email alias. The map you built never saw that copy. Priority numbers are an order, not load balancing. A higher preference host is idle while a leftover host still accepts mail. Save the old MX set before you delete anything. Check more than one public view because TTL lies.

Catch-all forward is not a safety feature for custom domain email alias how it works without another inbox. Hold unknowns on everyday production. Review the store. Promote a leftover only when a real person used it. Paid forward belongs to a dated cutover. Fan-out of unknowns into two inboxes trains two spam buttons. Plus addressing on Gmail is not a custom-domain unknown policy. MailerZ will not strip plus tags on your domain the way Gmail does on @gmail.com.

Send-as is a second hop. Creating an inbound alias does not approve outbound. Catch-all does not mint a From. Copy the dashboard host, port, and TLS pair together. Set From to an identity you created. Do not paste a Gmail password into a CMS, a cron file, or a ticket. Do not mail SMTP secrets to support. Send a 550 line, a timestamp, and a Message-ID. Rotate if a secret already leaked.

Self-send from Gmail to the same Gmail account can short-circuit. That green result is why people swear custom domain email alias works while customers vanish. Use a second provider. Put a unique subject on the probe so delivery history is searchable. If Header From was rewritten by some other forwarder, authentication stories get noisier. MailerZ does not rewrite Header From on inbound.

Agencies should keep custom domain email alias per client zone. Separate SMTP credentials. Do not pour every client into one catch-all because the spreadsheet got long. Agency plan capacity exists so you can hold more domains and aliases. It does not replace a named list. Offboard means delete MX you own, revoke SMTP, and stop forwarding leftovers into the agency inbox.

Legal and security questions have published answers on the security, privacy, terms, DPA, and subprocessors pages. MailerZ is not SOC 2, not ISO 27001, and not HIPAA. The 14-day Free store, the 90-day Solo–Agency store, and the 180-day Unlimited store are recovery windows for hops this layer saw. They are not an archive and not legal hold. If counsel wants eDiscovery, buy eDiscovery.

Comparisons only help after the hop is honest. Cloudflare Email Routing is inbound routing. A privacy-mask product hides a destination on a provider domain. A suite hosts mailboxes, Calendar, and admin. Proton-class mailboxes encrypt a store. MailerZ is the delivery layer when you already have Gmail or Outlook and you need a domain route you can prove. Cite the other product’s documentation. Do not invent feature parity.

When Custom Domain Email Alias: How It Works Without Another Inbox is closed, the next physical action is a lookup and a probe, not another tab. Start free on one domain you can break. Sign in if the zone already lives here. Review quarterly, or sooner after a nameserver move, a plugin swap, or a staff departure. That is how custom domain email alias stays a runbook instead of an incident.

A second worked pass for custom domain email alias: write the last change on a sticky note before you open the dashboard. Nameserver move, leftover MX, new form plugin, contractor laptop, or a registrar forwarding toggle are the usual five. MailerZ history only shows hops that reached this layer. If the sticky note says leftover MX, you do not have a custom domain email alias mystery. You have a split. Delete the leftover. Wait for TTL. Probe again.

A third worked pass: print the public list. If you cannot print it, you are not ready for production unknowns and you are not ready for a bigger alias ceiling. Unlimited aliases as marketing will not save a missing list. Three named aliases on Free are enough to stop printing a personal Gmail on a homepage. Grow the list when a real person used a leftover, not when a harvest guessed admin@.

More working detail

Why “another inbox” is the expensive misunderstanding

People hear alias and picture a second pane in Gmail. A custom domain email alias does not add a pane. It adds a To: line that your filters can key on. Labels are enough for most three-person shops. A second Google account is another password and another place mail hides. Only split destinations when ownership is actually split — finance versus ops — not because the UI felt empty.

Without another inbox also means without another archive. Old Workspace mail stays in Workspace until you export it. MailerZ will not pull it. The 14-day and 90-day stores are hops this layer saw after the alias existed. They are not the missing second inbox.

Mobile apps signed into Gmail already show the alias mail. Apps signed into a dead Workspace user do not. Tell people which login to open. That sentence prevents “the alias is down” tickets that are the wrong app.

If two humans must see one alias without sharing a Gmail password, add a second destination or share the store on purpose. That is still not another domain inbox. It is a copy. Name who replies.

IMAP clients and the myth of the extra inbox

Thunderbird, Apple Mail, and Outlook desktop can download Gmail. They do not host hello@yourdomain. The alias still lives in the map. If a consultant wants “a real inbox” they can see in Thunderbird, give them Gmail IMAP, not a suite seat, unless they also need Calendar.

One more working distinction

A sentence for procurement

“The mailbox is Gmail. The alias is MailerZ. There is no second hosted inbox on the domain.” A custom domain email alias without another inbox is that split. Procurement can list two vendors. Security can read two pages. Nobody has to invent IMAP on yourdomain.com.

If they require a hosted login anyway, stop selling the hop as hosting. Sell the hop as the hop or walk. Enterprise wording that outruns the legal pages loses the next review.

Confirm live pricing before you put Solo in a SOW. Ceilings change on the page, not in this article.

A short operating rule

Filters that make one inbox feel like many

To: support@ yourdomain → Support label. To: billing@ → Finance. A custom domain email alias without another inbox is usable when those two filters exist. Without them, three roles drown in Primary and someone buys a seat to “see support.” The seat was a label.

Do not build twenty filters on day one. Build the three you print. Add a filter when you promote a leftover. That matches the hold policy.

Outlook rules are the same idea. Document which store has the rules. A remap to a new Gmail does not move them.

Field close

When the store is Outlook, not Gmail

A custom domain email alias without another inbox works the same: map hop two to Outlook.com or a Microsoft 365 personal mailbox you already have. Send-as is a manual SMTP identity, not Gmail’s wizard. Document it. Probe it. Do not assume Microsoft inherits a Gmail filter pack.

Shared Microsoft mailboxes are a suite object. Mapping to one is a destination choice. It is still not IMAP on your domain unless you bought hosting. Keep the sentence honest.

Last operating note

If someone still asks “where do I log in as hello@?”, the answer is you do not. A custom domain email alias without another inbox has no hello@ password. You log into Gmail. That is the product. Repeat it until the seat quote dies.

Start free on one domain you can break. Sign in if the store already works and leftover MX still steals hop one.

One last line

One more time: the domain has no hello@ password. A custom domain email alias without another inbox is Gmail plus a map. If leftover MX still answers, even that map is fiction. Look up twice. Then probe.

Ownership is the part founders skip after MX looks green. Write the owner next to each alias: who answers, who remaps, who can disable. A custom domain email alias without another inbox still needs a human. If support@ lands in three Gmails and nobody owns the spam button, you built a shared inbox without the suite controls. One destination per role. Filters in that store. A remap runbook when the person leaves. MailerZ seats operate the dashboard. They are not extra Gmail licenses. Confirm alias and seat ceilings on pricing before you print a dozen role names.

FAQ

What is the safest way to handle custom domain email alias?

Map a named alias to Gmail or Outlook you already have, publish exclusive MailerZ MX, delete leftover hosts, and probe from another mailbox. The domain does not get IMAP. That is an alias without another inbox.

Does this require a new mailbox?

No. MailerZ is Mail Box portal webmail (Inbox, Sent, New email). It is not IMAP or POP. Gmail or Outlook remains the store unless you separately buy a hosted mailbox product.

Will it work with Gmail or Outlook?

Yes for inbound when the destination is a verified mailbox. Branded replies need paid send-as plus Gmail Send mail as or a manual Outlook SMTP identity. Free has no send-as.

What DNS records are involved?

A verification TXT, one MailerZ MX set on the authoritative nameservers, leftover host MX removed, and SPF, DKIM, and DMARC if you also send as the domain.

What should I test before production?

Send a uniquely titled message from an unrelated provider into each named alias. Confirm Header From and delivery history. Do not email yourself from the same Gmail account.

Key takeaways

• One store: Gmail or Outlook stays the inbox.
• Named map: each printed local-part has an owner and a destination.
• Exclusive MX is still required. An alias without MX is a string on a website.
• No IMAP or webmail login on the custom domain.
• Free allows ten aliases, one domain, hold or reject unknowns, and no send-as.
• Paid send-as still uses the same store. It does not create a mailbox.
• Hold unknowns. Catch-all FORWARD is not a naming system.
• Buy a suite only if you need a hosted login, Calendar, or lockable store.

Conclusion and next action

A custom domain email alias does not require another inbox. It requires a map, exclusive MX, and a probe. MailerZ is that hop around Gmail or Outlook.

Start free. Sign in if the store is fine and leftover MX still owns hop one.

Review quarterly, or sooner if Gmail, Workspace, or MailerZ scope changes. Author: MailerZ editorial, Secuno LLC.