Gmail Send mail as: custom domain setup with authenticated SMTP

Quick answer for gmail send mail as custom domain

Gmail send as custom domain requires a paid MailerZ plan, an approved From such as hello@, and the host/port/TLS/username/password the dashboard shows. Follow Google’s help article for the clicks. Treat that page as source for the UI.

Custom domain Gmail inbound is a separate MX cut. Email forwarding to Gmail must already work. Otherwise you send as hello@ and never receive the replies.

Do not paste the Gmail account password into Send mail as. That is mailbox SMTP at Google, not domain SMTP at MailerZ.

Treat send-as as identity match. Unauthorized is 550 5.7.1. Not an outage.

MailerZ Free is one domain, three 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 gmail: the real decision

People open Send mail as on day one while leftover MX still owns inbound. Outbound looks branded. Inbound is dead. Customers who reply vanish.

Tutorials say “use your email and password.” Operators type hello@ and the website admin password.

Two browsers store two pairs. One still has an old improvised relay. Gmail silently picks the broken one.

Criteria: inbound proven, plan paid, From created, one pair pasted, outward probe done.

Technical mail flow for gmail send mail as custom domain

Gmail connects to MailerZ SMTP, authenticates, offers From. Policy checks the identity. DKIM signs per published selectors. The recipient’s MX accepts or rejects.

Gmail may still show the Gmail address if the user did not choose the From on compose. Train the habit.

A revert to Gmail on compose is a client setting issue. There is a separate article if that slug exists. Here: pick the From every time until the default is set.

Rate limits are on /pricing. Bursting a form through the same identity can hit hourly send-as caps.

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, not webmail, 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.

gmail send as

Inbound cut first. Then money. Then paste. Then outward probe.

1. Prove hello@ inbound from another mailbox.
2. Upgrade to Solo or higher.
3. Create the From identity.
4. Create SMTP credential. Store in a manager.
5. In Gmail, add Send mail as with the MailerZ pair.
6. Send to an external inbox. Confirm From.
7. Set Gmail to reply from the same address if the UI offers it.
8. Revoke if a laptop is lost.

Failure modes and proof

Free plan.

Gmail password in the form.

Uncreated From.

Inbound leftover MX.

Self-send as the only test.

MailerZ workflow and product boundary

Paid SMTP for verified domains. Not an open relay. Not IMAP. Not SOC 2. Failed hops can sit in the recovery window.

Google owns the Send mail as UI. We own the credential and the 550.

Related pages: email forwarding, send and reply, compare Google Workspace, and docs.

email forwarding to gmail

Solo $40/year is the usual Gmail send-as budget. Workspace native send is the alternative if you already bought the suite and still publish their MX — that is a different architecture.

MailerZ Free is one domain, three 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

Name the From in the runbook. When you rename hello@ to founders@, update Gmail the same day.

A contractor with Send mail as still configured after offboard is an identity leak. Remove the account in Gmail and revoke SMTP.

App passwords at Google are for Google. Do not mix vocabularies in a ticket.

If Gmail asks to verify the address, complete that loop. Do not skip into “treat as alias” folklore.

Multiple domains need multiple identities and usually multiple credentials. Do not reuse one password across client brands.

Outlook users on the same domain use a manual SMTP identity. Do not force them through Gmail’s dialog.

Campaign tools should not share this credential. Buy a transactional vendor for bursts.

Log the 550, not the password, when it fails.

STARTTLS versus implicit TLS is a pair with the port. Copy both.

If compose still defaults to Gmail, that is training and settings, not MX.

Longer operator notes

The Gmail dialog, in human order

Google’s help page owns the clicks. This page owns the match rule. Open Settings, Accounts and Import, Send mail as. Add the From you created. Paste the MailerZ host, port, username, and password. Use the TLS mode the dashboard pairs with that port. Do not invent 587 versus 465 from memory. Do not type the Gmail account password. Complete any verification loop Gmail demands.

Then send to a mailbox you do not own. If From is hello@ and history shows the hop, you are done. If Gmail still composes as the Gmail address, change the default From if the UI offers it, and train the habit. A revert is not leftover MX. It is a client setting.

If AUTH fails, the secret or the TLS pair is wrong. If AUTH works and you get 550 5.7.1, the From is not approved or you are still on Free. Those are different tickets. Do not rotate a good password because From was never created.

Inbound still owns the reply

Branded outbound with dead inbound is how companies look professional on the first message and silent on the second. Prove hello@ receive before you celebrate Send mail as. Leftover Google MX will swallow replies even while outbound DKIM looks pretty.

Two identities on one Gmail — personal and hello@ — need two mental modes. Calendar invites from the Gmail address will still leak the store. That is not SMTP’s fault. Decide which identities are public.

Contractors with Send mail as still configured after they leave are an outbound leak. Remove the account in Gmail. Revoke the SMTP credential. Do both.

Forms, cron, and Gmail

Send mail as is for humans in Gmail. A contact form should not impersonate the human dialog. Give the form its own credential on a paid plan, or a transactional vendor if volume is the product. Sharing one password across Gmail, WordPress, and cron is how you hit hourly send-as ceilings and then paste the secret into a ticket.

Campaign tools do not belong on this identity. MailerZ is not a bulk sender. Limits live on pricing. 550 on unauthorized is success for everyone else on the internet.

Outlook users need a manual SMTP identity, not this Gmail dialog. Do not force a mixed shop through one UI.

STARTTLS versus implicit TLS is a pair. Mixing them fails before a body exists. Copy the dashboard.

App password language at Google is for Google. MailerZ passwords are for MailerZ. A plugin that says “app password” does not merge the vendors.

If you rename hello@ to founders@, update Gmail the same day. Orphans look like “SMTP is down.”

More operational detail

Verification loops and aliases

Gmail may send a confirmation to hello@. That confirmation must arrive, which is why inbound MX has to work first. If leftover Google still owns inbound, the confirmation dies and Send mail as never finishes. People then paste a Gmail password to “just send.” Do not.

Treat as alias versus send through SMTP: follow Google’s current help. This page requires authenticated SMTP through MailerZ for the domain From. We are not documenting a deprecated Google-internal relay.

Defaults: set reply-from-same-address if the UI offers it. Otherwise every reply leaks Gmail. That leak is not leftover MX. It is compose habit.

Two-factor on the Gmail account is still required hygiene. SMTP credentials do not replace account security at Google.

If Gmail disables the Send mail as entry after a password change, you rotated the wrong secret or Gmail invalidated the stored pair. Recreate from the dashboard. Do not reuse an old screenshot.

Hourly send-as limits are on pricing. A burst of “test” emails during onboarding can look like a block. Wait. Do not switch to an open relay.

Multiple Gmail accounts as destinations do not each need SMTP. Only the accounts that send as the domain need the pair.

Write the From string in the MX runbook so a rename is a checklist, not an incident.

MailerZ Free remains one domain, three 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 or $80. Business is $19 or $190. Agency is $39 or $390. Unlimited is $99/month or $990/year. Confirm MailerZ pricing. Unauthorized send is 550 / 550 5.7.1. Leftover MX is a hard stop. Envelope SRS only. Header From, Subject, Date, Message-ID, body, and MIME are never rewritten. Not Google Workspace, not IMAP, not webmail, not SOC 2, not ISO 27001, not HIPAA, not an inbox-placement promise.

A complete worked story

A Send mail as afternoon that does not skip inbound

Morning: leftover MX is gone, hello@ receives from a colleague, history is clean. Afternoon: upgrade to Solo, create the credential, open Gmail Send mail as, paste the MailerZ pair, finish Google’s verification because inbound now works so the confirmation arrives. Evening: send outward to the colleague. From is hello@. They set reply-from-same-address if the UI offers it.

The afternoon that skips morning is the failure. Confirmation mail dies at leftover Google. They paste a Gmail password. Google locks the account later. hello@ inbound was never proven. Do not do that afternoon.

A form plugin on the same identity needs its own rate limit and preferably its own credential. Sharing the Gmail-dialog password with WordPress is how hourly send-as ceilings look like an outage. Campaign tools do not belong here. MailerZ is not a bulk sender. Confirm pricing limits.

When the contractor leaves, they remove Send mail as in Gmail and revoke SMTP. Doing only one half leaves an outbound leak. Write both steps in the offboard checklist next to leftover MX.

If compose still defaults to Gmail, that is training. It is not MX. If AUTH fails, TLS pair or secret. If 550, From or Free plan. Do not rotate a good secret because From was never created. Catch-all does not approve outbound identities.

Outlook users in the same company use a manual SMTP identity. Do not force them through this dialog. The match rule is the same: issued pair, approved From, paid plan.

Operator brief

A longer operator brief for gmail send mail as custom domain

Teams that bookmark Gmail Send Mail As: Custom Domain Setup With Authenticated SMTP 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 gmail send mail as custom domain 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 not a hosted mailbox, not IMAP, not webmail, 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 gmail send mail as custom domain. 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 gmail send mail as custom domain setup with authenticated smtp. 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 gmail send mail as custom domain 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 gmail send mail as custom domain 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 Gmail Send Mail As: Custom Domain Setup With Authenticated SMTP 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 gmail send mail as custom domain stays a runbook instead of an incident.

A second worked pass for gmail send mail as custom domain: 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 gmail send mail as custom domain 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@.

FAQ

What is the safest way to handle gmail send mail as custom domain?

Prove inbound, upgrade, create the From identity, paste the MailerZ SMTP pair into Gmail Send mail as, and send outward to another mailbox. Do not use the Gmail password.

Does this require a new mailbox?

No. Gmail stays the client and the store.

Will it work with Gmail or Outlook?

This page is Gmail. Outlook uses a manual SMTP identity with the same MailerZ pair.

What DNS records are involved?

Inbound MX plus SPF, DKIM, and DMARC for the sending domain. Leftover MX does not fix AUTH.

What should I test before production?

Outward message to an external inbox. Confirm From. Confirm a wrong password fails closed.

Key takeaways

• Paid plan first.
• Dashboard pair only.
• From must exist.
• Inbound first.
• Google’s UI, MailerZ’s AUTH.
• 550 means unauthorized.
• No Gmail password.
• No inbox SLA.

Conclusion and next action

Attach Send mail as only after inbound is honest and the plan includes send-as. Copy the pair. Probe outward.

Start free for the receive half. Upgrade when the From must travel.

Sign in if the credential already exists and Gmail still refuses — check From and TLS before you rotate blindly.

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