Gmail forwarding test works real mail fails is usually a path mismatch, not a curse. Your test stayed inside Google or used an alias you created this morning. The bank used public MX, a leftover Google host, or a local-part you never mapped. MailerZ can show the hop that arrived. It cannot invent a hop that went to ASPMX or to HOLD.
Quick answer for gmail forwarding test works real mail fails
Split the evidence. If MailerZ history is empty for the customer and present for you, they never reached you. Query two resolvers. Delete leftover ASPMX, outlook, and registrar MX. If history is 250 for them and your inbox is empty, search spam and HOLD. Product path: troubleshooting and delivery recovery.
MX selection is in IETF RFC 5321 — Simple Mail Transfer Protocol. Domain names are in IETF RFC 1035 — Domain names. A Gmail-to-Gmail send can short-circuit that lookup. Real senders will not. Competitor writeups such as the ImprovMX blog (nofollow) repeat the same leftover-MX story. Quote them live. Dual-publishing their MX beside MailerZ is leftover MX with extra branding.
Confirm MailerZ pricing if the failure is send-as on Free. Free receives. Solo is $40 per year. Starter is $8 or $80. Business is $19 or $190. Agency is $39 or $390. No plan merges two MX owners. No plan is an inbox SLA.
Google’s people-first guidance is about pages; see creating helpful, reliable, people-first content. A post that says “just email yourself” as the only test is how this ticket is born.
The user problem and the decision criteria
The founder emailed hello@ from the same Gmail that receives hello@. It landed. A customer invoice did not. Support asked if they checked spam. Both can be true and both can be incomplete. The decision is whether the customer’s envelope hit MailerZ. History answers that. A green self-send does not.
| Question | If yes | If no |
|---|---|---|
| Was the test Gmail to the same Gmail? | Invalid for public MX. Probe elsewhere. | Better. Still read history. |
| Does public MX list leftovers? | Real senders can hit the old host. | MX may be exclusive. Check alias next. |
| Is customer history empty? | They missed MailerZ. MX or envelope name. | If 250, search the store and HOLD. |
| Did they write sales@ and you created hello@? | HOLD or refuse. Create the printed name. | Good. Still match the envelope, not the header. |
| Is Send mail as the failing test? | Different job. Paid SMTP plus leftover MX can eat the confirm. | Stay on inbound. |
Technical mail flow
Real senders resolve MX, connect, and offer the envelope recipient. If the first willing host is leftover Google MX, MailerZ never runs. Alias policy, HOLD, and SRS do not apply to a hop you did not receive. Your Gmail-to-Gmail test may never have performed that lookup. That is why the test is green and the bank is missing.
Forms often envelope-send to webmaster@ or the address in a hidden field while the template Header To says hello@. You tested hello@. They offered webmaster@. HOLD on Free stores the unknown name. You never opened HOLD. You called it a Gmail forwarding failure.
Destination filters can 250 a customer copy into spam after a perfect hop. Your self-send is trusted. Their invoice is not. That is reputation and content, not MX. See the reputation article after MX is exclusive and history is 250.
TTL and corporate resolvers keep old MX after you deleted it. Your laptop used 1.1.1.1. The bank used a cache. Wait the old TTL. Re-query two resolvers. Do not add the leftover back as backup.
Step-by-step setup and decision path
Ban self-send as the gate
Keep it as a smoke demo if you must. Production proof is another provider.
Query two public resolvers
Only MailerZ hosts. Delete ASPMX, outlook, registrar, old Cloudflare routing MX.
Print the envelope the customer used
Create that local-part. Do not guess from the pretty To line.
Probe from Outlook, iCloud, or work mail
Unique subject. Match history. Header From intact.
If 250 and empty, search spam and HOLD
Then delivery recovery. Do not republish MX.
Re-query after the next registrar save
Website DNS and “email included” republish leftovers. The green test will lie again.
Failure modes and proof
| What you see | Likely cause | Proof |
|---|---|---|
| You land, they do not, history empty | Leftover MX or their envelope name | Public MX list plus their message-id missing |
| You land, they 250 into spam | Author reputation or filter | History 250, folder search |
| Send mail as confirm missing | Leftover Google MX ate it | ASPMX still published |
| Form missing, you present | Hidden envelope recipient | Form logs versus alias list |
| Works on LTE, fails in office | Split-horizon or pinned DNS | Office resolver still lists leftovers |
| Works for one customer | Their cache already updated | Wait TTL. Do not declare done |
Proof is two listings, one foreign probe, and the customer’s history row or its absence. “It worked when I emailed myself” is the bug report, not the diagnosis. Agencies run this per zone. Client A can be exclusive while Client B still has ASPMX.
MailerZ workflow and product boundary
MailerZ is inbound MX plus authenticated SMTP. Envelope SRS only. Header From never rewritten. History shows hops MailerZ accepted. It cannot show a Workspace 250. It is not IMAP, not Workspace, not an open relay. Unhosted SMTP is 550 / 550 5.7.1.
HOLD stores unknown local-parts on Free. That is why a real sender’s typo never reaches Gmail while your exact hello@ test does. Free is one domain, three aliases, 14-day store, send-as disabled, SMTP and API disabled. Solo is $40 per year: 3 domains, 15 aliases, 90-day store, 1,000 outgoing, five outgoing per hour, unknowns forwarded. Starter is $8 or $80. Business is $19 or $190. Agency is $39 or $390. Unlimited is $99/month or $990/year. Confirm pricing. Limits are not an inbox SLA. No SOC 2 claim lives here.
Features describe routing. They do not make self-send a valid gate. Paid plans do not merge leftover MX.
Cost, alternatives, and trade-offs
| Choice | What you get | What you give up |
|---|---|---|
| Third-mailbox probe plus history | A real split between leftover and filter | The comfort of emailing yourself |
| Keep ASPMX as backup | A quiet second inbox | Customer copies in Gmail |
| Catch-all FORWARD to hide names | Typos plus harvested noise | A readable inbox |
| Buy a suite to “match tests” | A store. Quote live | The Gmail archive you already have |
Time is a line item. One Outlook.com probe costs less than another week of self-send. Leftover MX costs more than Solo. A Free-plan send-as argument still costs more than the upgrade. If every teammate needs IMAP on the domain, a suite is the honest product.
Why Gmail-to-Gmail tests lie
Google can keep a message inside its own system when both sides are Gmail. Public MX may never run. That is convenient and fatal as a cutover gate. The same is true of some “Send mail as” confirmation paths when leftover Google MX still answers.
Thunderbird or Apple Mail sending through Gmail SMTP to the same destination can inherit the same short-circuit. The client is not the variable. The providers are. Use a mailbox whose MX is not Google when the destination is Gmail.
Plus-addressing in a test (hello+test@) proves nothing if customers write hello@ or sales@. Test the printed name. Then test the form’s hidden name. Two probes. Two history rows.
IETF RFC 7208 — Sender Policy Framework (SPF) and IETF RFC 7489 — Domain-based Message Authentication, Reporting, and Conformance (DMARC) on a self-send copy can look perfect because the hop was local. Do not screenshot those tokens as production proof. Tokens on a third-mailbox copy are the ones that matter.
The name real senders actually use
Contact forms, payment providers, and CRMs pick an envelope recipient from configuration, not from your business card. If the field still says support@oldhost.com or info@, they never offered hello@. Your test of hello@ cannot fail in the same way.
Display names lie. “Support Team <help@example.com>” is still help@ on the envelope. If you only created support@, HOLD or refuse. Read raw headers or MailerZ history, not the inbox preview.
Subdomains are separate names. billing@pay.example.com is not cleaned by an apex hello@ test. Query MX on the printed hostname. Give it exclusive MailerZ MX if it should arrive.
Lists and BCC send one envelope per recipient. A customer who BCCs hello@ while To is their lawyer still needs the hello alias. Your To-line test missed that path.
When the hop worked and Gmail hid it
History 250 plus an empty Primary is not leftover MX. Search Updates, Promotions, spam, and filters. User marks on a vendor train the store. Shared inboxes multiply that. Ask who clicked Report spam before you rotate DNS.
Helpdesks that ingest the alias are another store. If they reject after MailerZ 250 to Gmail, you may still have the Gmail copy. If they are the only destination and they 5xx, history will show it. Remap. Do not tell the sender the test proved production.
If a second operator needs the same order without a call, send this page plus leftover MX and the delivered-meaning article. Exclusive hosts. Foreign probe. History class. Folder last. That order prevents the most expensive wrong fix: keeping ASPMX because self-send worked.
Paid plans do not validate a self-send. Solo, Starter, Business, and Agency still need exclusive MX and a named alias. The upgrade changes send-as and limits. It does not make Gmail-to-Gmail a public MX test.
Legal hold is not the 14-day Free store. Two-factor on the destination Gmail is still required after the real probe lands. Registrar email toggles republish leftovers after a website save. Re-query. The green test will not notice.
Night operators close tickets on a founder self-send at 11pm. Morning the bank is still missing. Leave the ticket open until a foreign probe and a customer message-id both exist in history or are explained by HOLD or a leftover host.
Open a held body for break-glass recovery and expect an audit row. That is a control, not a SOC 2 badge. Do not send zone passwords to support. The artifacts that close this ticket are two resolver listings, a foreign probe, and either a customer history row, a HOLD body, or a leftover host you then delete.
IPv6-only senders and odd resolvers still read the same MX set. If they fail after your IPv4 probe worked, resolve the MX hostnames for AAAA. Dead family is a host problem, not a Gmail filter. Do not mix it with self-send folklore.
Send mail as is not an inbound test
Founders paste SMTP, send a confirmation to the alias, and call the whole stack proven when the confirm appears. That confirm is one message from Google to your domain. If leftover ASPMX still answers, Gmail may accept a path that never used MailerZ inbound—or the confirm dies on the old host while a later self-send looks fine. Delete leftovers before you treat send-as as green.
Free has no send-as. A failed confirm on Free is not leftover MX and not a real-sender inbound miss. It is the plan. Upgrade to Solo when the printed From must go out. Do not mix that ticket with a bank invoice that never arrived.
Outbound 550 5.7.1 is authorization. It does not explain a missing inbound invoice. Keep send-as and inbound in separate threads so nobody “fixes” the bank by rotating SMTP passwords.
Gmail’s send-as UI can show a checkmark after a short-circuit confirm. Repeat the inbound probe from Outlook after send-as is saved. Two jobs. Two proofs. IETF RFC 6376 — DomainKeys Identified Mail (DKIM) on your outbound copy is send-as homework. It is not proof customers hit your MX.
How to stop closing on a founder demo
Write the gate into the runbook: foreign mailbox, unique subject, history row, two resolvers. A demo from the founder’s phone is allowed as theater for a board meeting. It is not allowed as the close reason.
Support macros should ask which provider sent the successful test. If the answer is “the same Gmail,” bounce the ticket back with this page. If the answer is Outlook and history is empty, you are in leftover MX or envelope name. If history is 250, you are in folder or HOLD.
Agencies: require the foreign probe in the handoff checklist per zone. A screenshot of the founder’s sent folder does not certify Client B. Client B may still publish outlook.com.
Status updates during cutover should say “self-send works, public MX still dirty” when that is true. Customers will keep failing until leftovers die. Honesty keeps the next invoice from becoming a refund fight.
Legal hold is not the 14-day Free store. Two-factor on the destination Gmail is still required after the foreign probe lands. Quote live prices the day you debug. Gmail short-circuit behavior can change. The ban on self-send as a gate should not.
Night operators love a green demo. Leave a written next step: delete ASPMX, wait the old TTL, foreign probe at 09:00. Closing at 23:00 on a self-send is how this article keeps getting traffic.
Registrar included email and parking MX republish after A-record edits. Schedule a second public query the day after launch, not only at the cutover hour. The founder will self-send again and call it healthy. The bank will not.
If a second operator needs the same order without a call, send this page, leftover MX, and what delivered means. Exclusive hosts. Foreign probe. History class. Folder last. That order prevents keeping ASPMX because Gmail emailed Gmail.
Why leftovers survive after you deleted them
Deleting ASPMX in the panel is not the same as every sender seeing exclusive MailerZ MX. Old TTL, corporate resolvers, and registrar “email included” republish are the usual reasons a founder’s laptop looks clean while a bank still hits Google. Your 1.1.1.1 query can list only MailerZ. Their office resolver can still answer with the leftover set. That split is why gmail forwarding test works real mail fails after a “successful” cutover. Re-query two public resolvers and, if you can, the resolver the failing sender actually uses. Do not add the leftover back as backup while you wait.
Website DNS saves republish parking MX and registrar mail hosts. The A-record change you made for the marketing site can quietly restore ASPMX. Schedule a second public query the morning after launch, not only at the cutover hour. The founder will self-send again and call it healthy. The processor will not. Put the second query in the runbook next to leftover MX. Leftover MX is the tool. Dual-publishing Cloudflare routing MX or outlook.com beside MailerZ is the same class of bug with different branding.
Split-horizon and pinned office DNS look like a flaky product. LTE works. The office fails. Proof is the office resolver still listing leftovers or an internal view that never leaves the building. Fix that LAN. Do not dual-publish to “cover” it. Sticky caches after a low TTL still need the old TTL to expire. Waiting is cheaper than a second MX owner. MX priority is not load balancing. If you need the priority explainer, use the existing MX priority article. This page owns the test-versus-real split.
Google Groups, secondary Google MX (ASPMX2, ALT hosts), and leftover Workspace records are still leftovers. Consumer Gmail leftover and Workspace leftover fail the same way for a bank: the first willing host is not MailerZ. History stays empty. Your Gmail-to-Gmail test can still land because it never performed the public lookup. Ban that test as the gate. Keep it as theater if a board wants a demo. Close only on a foreign probe plus exclusive listings.
IPv6-only senders read the same MX set. If your IPv4 probe worked and they fail, resolve the MX hostnames for AAAA. A dead family is a host problem, not a Gmail filter and not a reason to restore ASPMX. Do not mix it with self-send folklore. MailerZ is not IMAP. Buying a suite seat does not expire a corporate cache.
Banks, processors, and CRMs as the real test
Payment processors, banks, and CRMs pick an envelope recipient from configuration. They do not read your business card. Stripe-style receipts, loan portals, and helpdesks often offer webmaster@, info@, or a leftover support@oldhost.com while you tested hello@. HOLD on Free stores the unknown name. You never opened HOLD. You called it a Gmail forwarding failure. Create the printed local-part the form actually offers. Then test that name from Outlook, iCloud, or a work mailbox that is not Google.
Calendar invites and ticket watchers are real senders too. They BCC or list-send. A customer who BCCs hello@ while To is their lawyer still needs the hello alias. Your To-line self-send missed that path. Subdomains are separate names. billing@pay.example.com is not cleaned by an apex hello@ test. Query MX on the printed hostname. Give it exclusive MailerZ MX if that name should arrive. Envelope SRS still applies on hop two. Header From stays intact. Do not rewrite From to “make tests match.”
Plus-addressing in a demo (hello+test@) proves nothing if customers write hello@ or sales@. Test the printed name. Then test the hidden form field. Two probes. Two history rows. Display names lie. “Support Team <help@example.com>” is still help@ on the envelope. If you only created support@, HOLD or refuse. Read history or raw headers, not the inbox preview.
When history is 250 and Primary is empty, you left leftover MX. You are in folder, filter, or HOLD. Search Updates, Promotions, spam, and the helpdesk that also ingests the alias. User marks on a vendor train the store. Shared inboxes multiply that. Ask who clicked Report spam before you rotate DNS. Reputation work comes after exclusive MX and a customer history row. It does not come first. No inbox percentage lives on this page.
Send mail as is still a different job. Free has no send-as. A missing Gmail confirm on Free is the plan, not leftover MX and not a missing bank invoice. Solo is $40 per year when the printed From must go out. Starter is $8 or $80. Business is $19 or $190. Agency is $39 or $390. Unlimited is $99/month or $990/year. Confirm pricing. Unauthorized send is 550 / 550 5.7.1. Do not “fix” an inbound miss by rotating SMTP passwords. Two tickets. Two proofs.
What to ask the missing sender for
Customers cannot paste MX. They can paste a sent-folder screenshot, a bounce, or nothing. Ask for three artifacts in plain language: the exact address they typed, the time in their timezone, and any bounce text. If they can open sent mail, ask for the Message-ID header. Match that id in MailerZ history. Present is hop two or hop one. Absent plus leftover MX is the usual miss. Absent plus exclusive MX is a different envelope name or a cache that still has leftovers.
Do not ask a bank to “check SPF.” They will not. You query two resolvers. You create the alias they used. You search HOLD. You search spam. That is the operator side. If they have a bounce that says 550, you are not on a leftover-MX-only ticket anymore. Read the permanent text. If they have no bounce and you have no history, they likely hit another host. Leftover Google accepted a Workspace 250 you will never see. MailerZ cannot invent that hop.
Support macros should ask which provider sent the successful test. If the answer is “the same Gmail,” bounce the ticket with this page. If the answer is Outlook and history is empty, leftover MX or envelope name. If history is 250, folder or HOLD. Agencies require the foreign probe per zone. A screenshot of Client A’s sent folder does not certify Client B. Client B may still publish outlook.com.
Night close on a founder demo is how this article earns traffic. Leave the ticket open until a foreign probe and a customer Message-ID both exist in history or are explained by HOLD or a leftover host you then delete. Write the next step: delete ASPMX, wait the old TTL, foreign probe at 09:00. Status during cutover should say “self-send works, public MX still dirty” when that is true. Honesty keeps the next invoice from becoming a refund fight.
Legal hold is not the 14-day Free store. Two-factor on the destination Gmail is still required after the real probe lands. Opening a held body for break-glass recovery should leave an audit row. That is a control, not a SOC 2 badge. Do not send zone passwords to support. The close packet is two resolver listings, a foreign probe, and either a customer history row, a HOLD body, or a leftover host you deleted. Paid plans do not validate a self-send. They change send-as and store length. They do not make Gmail-to-Gmail a public MX test.
If a second operator needs the same order without a call, send this page plus leftover MX and what delivered means. Exclusive hosts. Foreign probe. History class. Folder last. That order prevents the expensive wrong fix: keeping ASPMX because Gmail emailed Gmail. Start free on one domain when the job is inbound proof. Sign in if the domain is already there. Then run the probe from a mailbox that is not Gmail.
FAQ
What is the safest way to handle gmail forwarding test works real mail fails?
Throw out self-send. Query two public resolvers for exclusive MailerZ MX. Probe from a mailbox that is not Gmail. Match history. If history is empty, leftovers or alias. If history is 250, search spam and HOLD. Do not treat a green Gmail test as production.
Does this require a new mailbox?
No. You need a second mailbox only as a probe, not a new store. Gmail can stay the destination. MailerZ is not IMAP. Buy hosting only if you need folders on the domain instead of Gmail.
Will it work with Gmail or Outlook?
Inbound works for senders who hit exclusive MailerZ MX and a mapped alias. Same-Google tests can skip that path. Outlook and banks will not. Free has no send-as. Gmail Send mail as confirmation can vanish into leftover Google MX.
What DNS records are involved?
Exclusive MX on the printed name. NS that tells you which panel is live. Verification TXT. SPF, DKIM, and DMARC when you send. Leftover ASPMX is the usual reason real senders diverge from a Gmail-to-Gmail test.
What should I test before production?
Two-resolver MX listing, a uniquely titled message from Outlook, iCloud, or a work mailbox, Header From intact, history 250, then Primary and spam. Repeat after the next registrar save. Self-send is a demo, not a gate.
Key takeaways
- Gmail forwarding test works real mail fails: your path is not their path.
- Self-send and same-Google hops can skip public MX. Ban them as the gate.
- Empty customer history is leftover MX or a different envelope name.
- History 250 plus empty Primary is spam, filter, or HOLD.
- Create the name the form actually offers, not the name on the card.
- Re-query MX after registrar website saves.
- Free receives. Solo $40/yr starts send-as. Confirm /pricing.
- Envelope SRS only. Not IMAP, not an inbox SLA, not SOC 2.
Conclusion and next action
If tests work and customers do not, stop emailing yourself. List public MX twice. Probe from another provider. Match history to the envelope they used. MailerZ can show the hop. It cannot retrieve mail leftover Google accepted or an alias you never created. Start free on one domain and run a foreign probe before you call it done.
Ready to prove the public path
Start free with one domain and a non-Gmail probe.
Inbound on Free. Solo when send-as is the job. Sign in if the domain is already there.
Review quarterly, or sooner if Gmail short-circuit behavior or MailerZ history labels change. Author: MailerZ editorial, Secuno LLC.