How to use a custom domain email in Gmail without Google Workspace

Quick answer

Use a custom domain in Gmail without Workspace when the job is identity plus an inbox you already trust. Add the domain on MailerZ. Publish a verification TXT. Create named aliases such as hello@. Publish only the MailerZ MX set. Delete leftover Google, Microsoft, Cloudflare routing, or registrar MX. Send a uniquely titled message from an unrelated provider. Confirm Header From and delivery history in Gmail, including spam and Promotions.

Do not buy Workspace because a homepage needs hello@. Workspace is a hosted mailbox, Calendar, Drive admin, and a per-user invoice. MailerZ is not that product. Compare pages exist. This article is the keep-Gmail path.

Send-as is optional. Email forwarding to Gmail is the inbound half. If you only need to receive, Free is enough: one domain, ten aliases, unknown recipients held, send-as Off. If customers must see the domain on replies, upgrade and attach Send mail as using the dashboard SMTP pair. Google’s own steps live in Google Gmail Help — Send mail from a different address.

MailerZ Free is one domain, ten aliases, one seat, a 14-day store, send-as Off, SMTP Off, API Off. 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 monthly or $990 yearly. Confirm live numbers on MailerZ pricing. Those ceilings are capacity, not an inbox-placement promise.

Workspace as a product is described on Google Workspace — product overview. Transport still follows IETF RFC 5321 — Simple Mail Transfer Protocol. Authentication still follows IETF RFC 7208 — Sender Policy Framework (SPF), IETF RFC 6376 — DomainKeys Identified Mail (DKIM), and IETF RFC 7489 — Domain-based Message Authentication, Reporting, and Conformance (DMARC).

The real decision

Founders treat Workspace as the only way to look like a company. They pay per seat for people who only needed a printed role. Custom-domain Gmail is calmer when Calendar already lives on personal Gmail and nobody needs an admin console. The expensive wrong turn is a mailbox seat per printed name. The quiet wrong turn is leftover Workspace MX after a trial. The public wrong turn is printing hello@ before the probe.

Technical mail flow

A sender looks up MX for your domain, offers RCPT TO hello@yourdomain, and transfers content. MailerZ accepts a named alias and forwards a copy to the Gmail address you verified. Gmail stores and classifies the message. Header From stays the original author so DKIM still describes that author.

SRS may rewrite the envelope return path so bounces can travel. That is not a From rewrite. If a forwarder rewrites Header From, Gmail’s filters see a broken authentication story. MailerZ does not do that rewrite on inbound.

Gmail does not need MX on your custom domain for this split. If Google MX remains, Google is still the inbound operator. Custom domain Gmail without Workspace fails quietly that way. Priority numbers are an order, not load balancing. A leftover aspmx host will keep accepting mail this layer never sees.

Outbound: Gmail Send mail as uses authenticated SMTP on a paid plan. Free cannot finish that hop. Unauthorized send is 550 / 550 5.7.1. Creating the inbound alias does not approve outbound. Catch-all does not mint a From.

MailerZ is inbound MX plus authenticated SMTP from Secuno LLC. Not Workspace, not IMAP or POP, not an open relay. Self-send from Gmail to the same Gmail account can hide routing errors. Promotions is not a bounce. Primary is not promised.

Step-by-step setup

1. Name the Gmail you already search

   That dest is the archive. If it does not exist, you are not skipping Workspace. You are missing a store.

2. Add and verify the domain

   Verification TXT first. Create printed aliases. Map them to that Gmail. Hold unknowns. Do not start with catch-all.

3. Publish one MailerZ MX set

   Delete leftover Workspace, Microsoft, Cloudflare routing, and registrar MX. Save the old set. Check two public views. Help lives on troubleshooting.

4. Probe from another mailbox

   Unique subject. Confirm Header From and a history row. Search Gmail including spam and Promotions. Self-send lies.

5. Leave send-as off until From must travel

   Inbound-only is a valid production setup. When replies must show the domain, upgrade, copy host, port, and TLS together, and follow Google Gmail Help — Send mail from a different address. Treat as an alias. Prove outward on a second external inbox.

6. Write that the domain has no Workspace login

   The next contractor will ask for the mailbox password. The answer is the Gmail dest, the MailerZ operator seat, and the SMTP secret as three objects.

Related: email forwarding, send and reply, docs. The Gmail SMTP wizard article is the outbound sibling. This page stays inbound first.

Failure modes and proof

MailerZ workflow and product boundary

MailerZ is a delivery layer around Gmail. It does not become Workspace because this title mentioned Gmail. It does not host Calendar. It does not replace Gmail. Compare Workspace when every person needs a hosted login. Cite Google’s product page. Do not invent feature parity.

The 14-day Free store, 90-day paid store, and 180-day Unlimited store are hop windows, not Gmail Vault. If counsel wants eDiscovery, buy that from the store vendor. MailerZ does not claim SOC 2, ISO, HIPAA, or an inbox SLA.

Agencies should keep per-client dest Gmails and per-client SMTP. Do not pour every client hello@ into one founder Gmail plus catch-all. Offboard means delete MX you own and revoke secrets. The client keeps the printed names if they take the zone.

Cost and alternatives

Stay on Free while inbound is the question. Solo at $40 per year is the smallest send-as plan. Starter through Agency add seats and volume. Unlimited adds a 180-day store and a 100,000 outgoing monthly cap. Confirm pricing. Two months free on annual Starter, Business, and Agency is arithmetic versus monthly. Solo is yearly only.

Workspace is the honest buy when you need hosted humans, admin, and Calendar as the system of record. Quote Google live. A privacy-mask product is the wrong buy when customers must write hello@ on a domain you own. Registrar forwarding is a thin hop with no history. Cloudflare Email Routing is inbound routing. Compare live docs.

Time is still a line item. Leftover Workspace MX costs more than Solo. A Free-plan branded-reply promise costs more than the upgrade. Budget one external inbound test before the homepage goes live.

Worked examples

They bought Workspace for a footer

They needed hello@ and billing@. They already lived in Gmail. They bought seats, never used Calendar, and forwarded everything to personal Gmail anyway. The hop would have been enough. They kept Drive on Workspace if they wanted Drive. Domain mail became MailerZ aliases.

The trial ended and MX stayed

The invoice was gone. aspmx still answered. Customers never hit the new map. They deleted leftover Google MX, waited for two views, probed from another mailbox, and left send-as off until inbound was boring.

They printed hello@ on Friday

Marketing went live. The probe happened Monday. Weekend mail sat at the registrar. They learned to probe first. The unique subject is cheaper than a reprint.

Promotions was “not delivered”

History said 250. They remapped twice. The unique subject was in Promotions. They searched, trained Gmail, and left the alias alone. Classify is hop four. We do not move it to Primary.

Write the last change on a sticky note: leftover MX, new plugin, Workspace trial, or a contractor who added Google MX “for Calendar.” If the sticky note says leftover MX, you do not have a Gmail mystery. You have a split. Delete the leftover. Wait. Probe again.

Print the alias 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@. 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.

Self-send from you@gmail.com to hello@yourdomain that lands in the same Gmail can skip the forward hop. That green result is why people swear the path works while customers vanish. Use a second provider. Put a unique subject on the probe so history is searchable.

If you later need send-as, do not paste smtp.gmail.com into MailerZ or a MailerZ password into a Google “less secure apps” story. Two hops, two credentials. Treat as an alias in Gmail so replies stay on the domain identity. Prove outward on a mailbox that is not this Gmail.

Conversation view lies. Open original. Confirm Header From on inbound is the stranger. Confirm outbound Header From is the alias if you paid. Do not debug “Gmail rewrote the domain” until you opened original.

Filters are dest policy. A filter that files hello@ to a label is fine. A filter that auto-forwards back at the domain can loop. Break dest forwards that point at the alias. That is a Gmail setting, not an MX setting.

Quarterly leftover MX review still applies after you feel done. A plugin or a helpful IT person will reintroduce Google MX. Review sooner after a nameserver move. When this page is closed, the next physical action is a lookup and a probe, not another Workspace comparison tab.

What Gmail still owns after MX moves

Gmail still stores the copy, still applies spam and Promotions, still offers conversation view, and still defaults the composer to you@gmail.com until you attach send-as. Moving MX does not move those behaviors. A green MailerZ history row and an empty Primary tab can both be true. Search the unique subject. Train the dest. Do not rebuild aliases because a tab is empty.

Gmail plus addressing is dest-side. you+billing@gmail.com is a filter tag on Google’s domain. hello+billing@yourdomain is a different local-part on your zone. MailerZ will not strip plus tags the way Gmail does on @gmail.com. If you need billing@, create billing@. Do not invent plus-tag magic as the custom-domain plan.

Google Groups and collaborative inboxes are suite or dest objects. They can be a dest for a MailerZ alias. They do not become MailerZ. If a Group still follows Google MX on a different domain, that is fine. If you publish Google MX on this domain beside MailerZ, you are split again.

Workspace leftovers people forget

After a Workspace trial you may still have Google MX, a verification TXT that looks important and is not MailerZ’s, SPF that includes _spf.google.com, and a habit of adding users in an admin console that no longer receives. Clean MX first. Then rewrite SPF for send-as if you will send. Do not leave Google MX “for Calendar.” Calendar does not need your customer MX.

If someone still needs a Workspace seat for Drive, keep Drive on that seat and keep this domain’s MX on MailerZ. Two products, two jobs. Mixing them on one MX set is how Drive IT reintroduces aspmx and customers vanish again.

Agencies handing a client a Gmail dest

Write the dest Gmail in the runbook. The client will forget. Offboard means they can take the zone and remap dest to their own Gmail without a reprint if the public string is on their domain. If you printed the agency Gmail on their homepage, you locked them. That is the opposite of the keep-Gmail, own-the-domain design.

Separate SMTP per client if they send as the domain. One agency pair across ten client From identities is how one laptop becomes every brand. Solo through Agency ceilings are on the live pricing page. They are not a reason to share a secret.

A last inbound checklist you can paste: dest Gmail named, domain verified, aliases created, public MX is MailerZ only from two views, unique subject from another provider landed in All Mail, Header From is the stranger, history shows accepted and forwarded. If any line fails, do not print the homepage and do not open Send mail as. Fix the line. Probe again.

If All Mail has the message and Primary does not, you are done with hop four. Train Gmail if you want. Do not remap. If All Mail is empty and history is empty, print MX. If All Mail is empty and history shows dest 250, search again with the exact subject, then spam, then Promotions. Conversation view can hide a message under another thread. Search is the proof, not the tab you happened to have open.

Send mail as after inbound is boring

Gmail’s Send mail as wizard wants an SMTP host, port, username, and password. Those values come from the MailerZ dashboard on a paid plan, not from smtp.gmail.com and not from a guessed hostname. Treat as an alias so replies stay on hello@. Prove the first outbound message on a mailbox that is not this Gmail. If AUTH fails, recopy the live pair. If you get 550, you are still on Free, the From identity does not exist, or you hit a cap. Those are outbound tickets. They do not mean inbound MX is wrong.

A personal Gmail dest can still reject or junk a stranger after MX is exclusive. That is dest classify, not a missing Workspace seat. Buying Workspace to “look more official” while you keep forwarding to the same personal Gmail does not move Gmail’s junk model. Quote Google live if you actually need hosted humans, Calendar, and an admin console. This page is the other design: keep the store you already search, own the printed names, and pay MailerZ only when send-as must travel.

When a Google wizard tries to reclaim MX

Search Console, a cancelled Workspace admin, and “add this domain to Google” flows often offer to publish aspmx again. That is not required for Gmail as a dest. Cancel the mail-hosting step. A TXT for Search Console or a site verification record can stay. Google MX cannot. If a contractor finishes that wizard, leftover MX is back and customers split. Print public MX the same week anyone touches a Google admin screen.

Drive, Calendar, and Ads do not need your customer MX. Keep those products on the Google account you already have. Keep this domain’s MX on MailerZ. Confirm MailerZ pricing only if send-as is the next hop. A wizard that reintroduced aspmx is a DNS ticket, not a reason to buy Workspace seats you already decided against.

FAQ

Can I use a custom domain in Gmail without Google Workspace?

Yes for receive: keep Gmail as the store, verify one domain, publish one MailerZ MX set, delete leftover Workspace or host MX, and prove inbound from another mailbox. Add paid Send mail as only if replies must show the domain. This is not a Gmail replacement and not a Workspace trial.

Does this require a new mailbox?

No. MailerZ is not IMAP. Gmail remains the archive. Buy Workspace only if you need hosted logins, Calendar admin, and Drive as the system of record.

Why is leftover Google MX a hard stop?

If aspmx.l.google.com still answers, Google is still the inbound operator. Your new aliases never run for those senders. The suite invoice can be gone and the MX still answers. Print public MX from two views before you blame Gmail filters.

What DNS records are involved?

Verification TXT, one MailerZ MX set, leftover MX removed. SPF, DKIM, and DMARC if you also send as the domain. Gmail MX should not remain on the custom domain for this design.

What should I test before production?

A uniquely titled message from an unrelated provider into hello@. Confirm Header From and history. Search Gmail including spam and Promotions. Do not email yourself from the same Gmail account.

Is this the same as the Send mail as article?

No. This page’s first success is a stranger’s message arriving in Gmail. Outbound Send mail as is a second, paid hop after that proof. A sibling article covers the Gmail wizard field by field.

Key takeaways

• Keep Gmail as the store. Point exclusive MX at MailerZ.
• Leftover Workspace MX is a hard stop. The invoice can be gone and the host still answers.
• Prove inbound from another mailbox. Self-send lies.
• Promotions is not a bounce. Primary is not promised.
• Free receives. Solo $40/year starts send-as. Confirm /pricing.
• MailerZ is not IMAP and not a Gmail replacement.
• Buy Workspace when you need hosted humans, Calendar, and admin.
• Inbound first. Send mail as second. Two hops, two credentials.

Conclusion and next action

You can use a custom domain in Gmail without Workspace. Keep the inbox. Publish one MX set. Delete leftovers. Probe from somewhere else. Pay for send-as only if From must travel. Do not buy seats to print a footer. Do not treat this hop as a suite.

Review quarterly, or sooner after a Workspace trial or nameserver move. Author: MailerZ editorial, Secuno LLC.