Self-check
Is Gmail's "Send mail as" Removal About to Hit You? A Five-Minute Self-Check
There is no email, no banner, no countdown. The first sign that Gmail has stopped letting your free account send as your custom domain is a reply that quietly goes out as yourname@gmail.com — and by then a client has already seen it. This page is one thing: a diagnostic to find out whether you are exposed.
Most writing about Gmail "Send as" being removed jumps straight to what to do instead. Skip that. First answer a narrower question: does this change actually touch your setup, or are you bracing for something that was never going to reach you? The feature ran invisibly for years, so many people genuinely don't know. The three checks below settle it — no guessing, no "I think so."
Step 1 — Are you even a candidate?
Only one kind of account sits squarely in the blast radius. Find your row before you spend another minute worrying:
| Your setup | Do you rely on the feature? | Exposure | First symptom you'd see |
|---|---|---|---|
| Free Gmail, custom address under "Send mail as" routed through your own SMTP server | Yes — this is the exact path being retired | High | A reply silently leaves as @gmail.com, or the send errors outright |
| Free Gmail, custom "Send mail as" set to send "through Gmail" (no external SMTP) | Yes — still a consumer send-as identity | High | Mail arrives stamped "via gmail.com," then stops sending as your domain |
| Gmail that "checks mail from other accounts" over POP and replies through their SMTP | Partly — the reply identity rides the same stored password | Medium | The saved SMTP password starts failing and won't re-save |
Custom domain that only forwards into Gmail; you reply from @gmail.com | No — you never actually sent as the domain | Low | Nothing new breaks; recipients already see @gmail.com |
Free Gmail, you only ever send from @gmail.com | No custom-domain sending at all | None | Nothing changes |
| Paid Google Workspace on your own domain | Identity comes from domain/MX setup, not the personal trick | Different — not this change | Unaffected; your sending is already native |
If you landed in the "None," "Low," or "Different" rows, this change won't break anything for you — though "Low" means your mail already goes out as @gmail.com. If you are in a "High" or "Medium" row, keep going: the next two steps confirm whether it is already reaching you, or merely will.
Step 2 — Find the feature in your settings
Open Gmail in a web browser — not the phone app, which hides this — and go to Settings → See all settings → Accounts and Import. In the block titled "Send mail as," check three things:
- Is there an entry on your own domain? An address like
you@yourdomain.comhere means you use the feature; a bare@gmail.comentry does not count. - Does it route through an external server? Click "edit info" on the custom entry; an SMTP host, a port, and a username and password mean your sending rides exactly the credential path Google is retiring.
- Is it the default, or does "reply from the same address the message was sent to" apply? That decides whether a break fails loudly — every reply wrong — or only on some threads.
Step 3 — Run the confirmation send-test
Settings tell you what is configured; a test tells you what actually happens on the wire. From the custom address, send a message to a different inbox you control — ideally on another provider (Proton, Outlook), so you see your mail as a stranger's server does. When it lands, open the raw headers — "Show original" in Gmail, "View source" or "Show headers" elsewhere — because three fields there decide your result: the From: line, any "via" note beside your name, and the Authentication-Results block that records whether SPF, DKIM, and DMARC passed and, crucially, which domain signed the message.
Match what you find against these three outcomes:
- Pass. The
From:readsyou@yourdomain.com, there is no "via gmail.com" beside your name, andAuthentication-Resultsshows the DKIM signature asd=yourdomain.comwith SPF and DMARC aligned to it. The feature works and your mail authenticates as genuinely yours — the only outcome you can leave alone, and only for now. - Soft fail. It arrives, but tagged "via gmail.com," or the DKIM signature reads
d=gmail.cominstead of your domain, or it slipped into spam. The address shows, so nothing feels broken — but the authentication underneath is Google's, not your domain's, and that seam is exactly what strict receivers key on. This is the stage nearly everyone misses, because to you the sent mail looks perfect. - Hard fail. The send errors out, bounces, or the reply simply departs as your
@gmail.comaddress. The feature is already gone for you; there is nothing left to pre-empt, only to replace.
Run it twice if you can — once to a strict provider, once to another Gmail — because the soft fail usually surfaces on the strict side first while Gmail-to-Gmail looks clean. That gap is the breakdown, caught in the act.
Confirm the authentication underneath while you are in there — a shaky foundation is its own warning sign. Our email authentication checker reports SPF, DKIM, and DMARC for your domain, and the DNS tools show exactly what it publishes, so you can tell a healthy record from a missing one.
The key takeaway: you are exposed if — and only if — you send from a custom address through free Gmail's "Send mail as." Step 3 is the clearest test. Watch for the soft fail: the mail still sends, so nothing feels broken, while every recipient quietly sees the seams.
What's actually confirmed, and what isn't
Be precise about this, because it changes how urgently to act on your results. Google has publicly deprecated the plumbing this trick runs on: app passwords, "less secure app" access, and basic username-and-password SMTP auth are all being wound down across Google accounts. A blanket removal of consumer "Send mail as" is the widely expected next step — where every one of those deprecations points — but not a dated shutoff Google itself has published. Those deprecations leave marks in your own account, and our companion walkthrough of the credential changes is the account-by-account checklist for spotting them. So read this self-check as measuring your exposure to a change already in motion. If Step 3 came back a soft or hard fail, the motion has already reached you, announced or not.
Confirmed you're affected? The first move
A self-check pays off only if it turns into action, and you can start today while "Send mail as" still works as a safety net. From the Step 2 "edit info" screen, inventory every custom address and the SMTP host behind it, then pick an inbox that sends and receives as your domain natively. Publish its SPF include, DKIM key, and DMARC record beside the live setup — without touching your current MX — so both coexist. The moment a test from the new home lands with SPF and DKIM aligned, the Step 3 soft fail is gone: your domain authenticates its own mail, and what remains is a controlled switch, not a scramble.
Finishing the move means making that home permanent: an inbox you run, where no toggle can switch it off. The migration runbook walks the cutover, and the options comparison ranks where to land. Blue Folder Mail is one such home: one encrypted inbox for every domain you own, on your own Cloudflare account. Mail arrives in the clear and is sealed the moment it lands, encrypted at rest under a key derived from your passkey that the host never holds — zero-access, so the server stores ciphertext it cannot open. That is a strong, specific guarantee, not a claim that anything is unhackable, and the sending half still rides a provider to relay your outbound mail — which, unlike the Gmail trick, now authenticates as genuinely yours.
- Will I stop receiving mail when Send as is removed?
- Usually not. Forwarding keeps delivering mail to you. The loss is on the sending side — replying as your custom address — which is the part other people see.
- Does this affect paid Google Workspace accounts?
- Paid business accounts handle custom-domain identities through domain setup rather than the personal "Send mail as" feature, so they are affected differently. This change centers on free, personal Gmail with a custom address attached.
- How do I check if I use the feature?
- Look in Gmail's settings under accounts for a "Send mail as" entry on your own domain, then send a test and confirm the "From" address. If it shows your custom domain, you depend on the feature being removed.
- Can I keep my custom address?
- Yes. The address belongs to your domain, not to Gmail. Move it to an inbox that sends and receives as it natively and the address keeps working exactly as before.