Forwarded email goes to Gmail spam even when DNS looks correct because a pretty MX and SPF screenshot is not dest classify. Accepted and forwarded are hops this layer saw. Spam is Gmail’s folder. Prove exclusive MX, intact Header From, and an external probe. Then search All Mail. Do not rewrite From. MailerZ does not promise Primary. Limits are not an inbox SLA.
Quick answer
Separate three facts. Your MX can be exclusive and still leave Gmail free to junk a copy. Your SPF, DKIM, and DMARC can be tidy for send-as and still say nothing about a customer’s author domain. History can show dest 250 while the tab you opened is empty. Search the unique subject in All Mail, spam, and Promotions. Train Gmail if you want. Do not rebuild aliases because a folder is empty.
First prove hop one. Leftover Google or registrar MX means some senders never reach this layer. Empty history is not Gmail spam. It is a split. Print public MX from two views. Delete leftovers. Probe from another mailbox. Self-send from Gmail to the same Gmail account can hide the path.
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. Starter is $8 or $80. Business is $19 or $190. Agency is $39 or $390. Unlimited is $99 or $990. Confirm MailerZ pricing. Those numbers are capacity, not placement.
Transport follows IETF RFC 5321 — Simple Mail Transfer Protocol. SPF, DKIM, and DMARC are 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). They authorize sending. They do not move Gmail tabs.
The real decision
People paste a DNS screenshot into a ticket and ask why spam happened. The screenshot shows their records. The message is from someone else. Gmail judged the author, the content, the dest user’s filters, and a hundred other signals. Your MX being right is necessary for the copy to exist. It is not sufficient for Primary.
| You checked | Still broken | Proof |
|---|---|---|
| SPF on your domain | Stranger’s author domain | Original Header From |
| One resolver’s MX | Leftover host on another view | Two public lookups |
| History 250 | Gmail classify | All Mail + spam search |
| Self-send green | Real customers on the forward hop | Unrelated provider |
| Rewrote From “to authenticate” | Noisier DKIM/DMARC story | MailerZ does not rewrite From |
Prove exclusive MX and a unique-subject dest search before you change aliases.
Start free — one domainWhat Gmail is actually judging
A sender looks up MX, offers RCPT TO, and transfers content. MailerZ accepts a named alias, may SRS the envelope, and opens SMTP to Gmail. Gmail returns 250 and then classifies. That last step is dest policy. Envelope SRS is the allowed rewrite so the next hop can pass SPF on the return path. Header From stays the author.
If another forwarder rewrote Header From, Gmail sees a broken author story. Do not add a third vendor to compensate. Cut leftover hosts. Open original. If From is already intact and history shows forwarded, you are in dest classify. Search. Train. Do not remap.
User filters, blocked senders, and “report spam” history live on the dest account. A founder who trained Gmail to junk a vendor will keep junking that vendor after MX is perfect. That is dest memory, not your zone file.
Promotions is not spam and not a bounce. Conversation view can hide a message under another thread. Search the unique subject. Primary is a folder, not a promise.
Step-by-step diagnosis
Print public MX from two views
Exclusive MailerZ. No leftover Google, Microsoft, Cloudflare routing, or registrar host. If views disagree, wait for TTL. Help on troubleshooting.
Send a unique subject from another provider
Not the dest Gmail. Confirm history accepted and forwarded. Empty history is hop one, not spam.
Open original on the dest
Header From should be the test sender. Return-Path may show SRS. If From was rewritten, you are on the wrong hop.
Search All Mail, spam, and Promotions
Exact subject. If it is there, dest classify happened. Train Gmail if you want. Do not rebuild the alias.
Check dest filters and blocked senders
A filter that files or deletes hello@ will look like “forwarding failed.” It did not.
Leave send-as out of this ticket
Outbound 550 is hop five. Free has no send-as. Split that from inbound spam.
Related: delivery recovery, email forwarding. RFC links above beat a competitor blog about “inboxing.”
Failure modes and proof
| Symptom | Likely cause | What to check |
|---|---|---|
| Empty Gmail, empty history | Leftover MX. | Two public lookups. |
| Empty Primary, full spam | Dest classify. | Search. Train. Do not remap. |
| Self-send never hits spam | Short-circuit. | Foreign probe. |
| Via / rewritten From | Another forwarder. | Original headers. MailerZ keeps From. |
| Only one sender junks | That author’s reputation or a dest block. | Not your MX screenshot. |
| Everything junks after a filter | User rule. | Gmail filters. Disable the rule. |
If history is empty, you do not have a spam problem yet. You have a hop-one problem.
Open leftover MX troubleshootingMailerZ workflow and product boundary
MailerZ can show accepted and forwarded. It cannot move a message to Primary. It cannot promise inbox placement. It does not rewrite Header From to “look local.” That rewrite is how other tools create the authentication mess people then blame on forwarding.
The 14-day Free store, 90-day paid store, and 180-day Unlimited store keep hop evidence. They are not Vault. MailerZ is not IMAP, not Workspace, not an inbox SLA, not SOC 2. Unauthorized send is 550 — a different ticket.
Cost and alternatives
Paying for a bigger plan does not file Primary. Solo at $40 per year buys send-as and a longer store, not a Gmail tab. Confirm pricing for ceilings only. Buying Workspace to “fix spam” on forwarded copies is a suite purchase. Quote Google live. It still classifies.
A bulk ESP is for mail you send as yourself at list volume. It does not decide how Gmail files a stranger’s inbound copy. Registrar forwarding with a From rewrite can make spam worse. Prefer intact Header From. Cite RFCs, not a competitor inboxing claim.
Worked examples
The SPF screenshot
They pasted a green SPF for their domain. The customer wrote from a university account Gmail already disliked. History showed forwarded. Spam had the unique subject. They trained Gmail. They left MX alone. The screenshot was the wrong object.
Leftover aspmx plus a clean MailerZ panel
One resolver showed MailerZ. Another still had Google. Some senders never arrived. They called it spam. History was empty for those copies. They deleted the leftover, waited, probed. Then the remaining copies that did arrive were a dest-search job.
They rewrote From at the old host
The old forwarder made every inbound look like the relay. Gmail junked the lot. They moved to MailerZ, kept Header From intact, probed, and still searched spam the first week. Intact From is necessary. It is not a placement contract.
A filter named “hello”
A founder filed hello@ to trash during a noisy week. After MX was perfect, everything still vanished. The filter was the dest. They deleted the rule, searched trash, and left the alias.
Write the last change on a sticky note: leftover MX, new filter, From rewrite, or a sender Gmail already hated. If the sticky note says leftover MX, stop talking about spam. If it says filter, open Gmail settings. If it says From rewrite, open original. If it says that sender, train or block at the dest. Do not remap as a mood.
Two dests multiply classify. Founder A can see Primary while founder B sees spam. Probe both. Mixed folders are two facts. Do not delete hello@ because one dest junked.
Self-send from the dest Gmail to hello@ that lands in Primary proves almost nothing about customers. Use another provider. Put a unique subject on the probe so search works. Conversation view lies. Search anyway.
Plus addressing on Gmail is dest-side. It will not explain why shop@yourdomain junked. Create named aliases. Hold unknowns. A harvest into catch-all trains the spam button faster than any DNS slide.
Send-as 550 is not inbound spam. Free cannot finish outbound. Split those tickets. Copy the dashboard pair only after inbound search works. Gmail Send mail as labels live in Google Gmail Help — Send mail from a different address.
Quarterly leftover MX review still applies after you feel done. A helpful person will reintroduce Google MX “for Calendar.” Calendar does not need customer MX. Review sooner after a nameserver move. When this page is closed, the next physical action is a lookup and a dest search, not another inboxing blog.
Agencies: per-client dest Gmails have per-client filters. A house story that “forwarding always junks” is usually leftover MX on half the book and dest filters on the other half. Print MX per zone. Search per dest. Do not invent an SLA because a client yelled.
What a green SPF check actually proved
SPF on your domain answers who may send as you. A customer writing to hello@ is a different author. Their SPF, DKIM, and reputation travel with their domain. Your tidy records help send-as later. They do not file that customer’s inbound copy in Primary. A screenshot of _spf on your zone is the wrong object for this ticket. Open original. Read Header From. If From is the university, Gmail judged the university. MailerZ forwarded a copy. Dest 250 plus spam can both be true.
DKIM and DMARC on your domain are the same category of mistake when the ticket is inbound. They describe mail you send. They do not move a stranger’s message. If another forwarder rewrote Header From so every inbound looked like the relay, Gmail sees a broken author story. MailerZ does not rewrite Header From on inbound. Envelope SRS only. If original shows a rewritten From, you are debugging the old hop, not this one. Do not add a third vendor to “authenticate” a rewrite.
Content, training, and dest memory
Gmail classifies after it accepts. Links, attachments, lookalike brands, and the dest user’s own Report spam history all weigh more than your MX screenshot. A founder who junked a vendor last year will keep junking that vendor after DNS is perfect. That is dest memory. Train or unblock at the dest. Do not remap hello@. Do not buy a larger MailerZ plan to file a tab. Solo at $40 per year buys send-as and a longer store, not Primary. Confirm pricing for ceilings only.
Promotions is not spam and not a bounce. Social and Updates are the same idea. Conversation view can hide a unique subject under another thread. Search All Mail with the exact subject before you rebuild aliases. If the copy is there, hop four happened. If All Mail is empty and history is empty, print MX from two views. If All Mail is empty and history shows dest 250, search again, then spam, then trash, then filters. A filter that files hello@ to trash looks like “forwarding failed.” It did not.
Self-send, plus tags, and leftover suite MX
Self-send from the dest Gmail to hello@ that lands in Primary proves almost nothing about customers. Gmail can short-circuit. Use another provider. Put a unique subject on the probe so history and dest search agree. Plus addressing on Gmail is dest-side. you+billing@gmail.com will not explain why shop@yourdomain junked. Create named aliases. Hold unknowns. A harvest into catch-all trains the spam button faster than any DNS slide.
Leftover aspmx, Microsoft, Cloudflare routing, or a registrar host means some senders never reach this layer. Those copies have no history row. Calling that spam is the wrong name. Delete leftovers. Wait for TTL. Probe again. Calendar does not need customer MX. A helpful person will reintroduce Google MX “for Calendar.” Review leftover MX quarterly, and sooner after a nameserver move. Related: troubleshooting, email forwarding, delivery recovery.
Two dests, agencies, and what this page is not
Two dests multiply classify. Founder A can see Primary while founder B sees spam. Probe both. Mixed folders are two facts. Do not delete hello@ because one dest junked. Agencies should treat per-client dest Gmails as per-client junk models. A house story that forwarding always fails is usually leftover MX on half the book and dest filters on the other half. Print MX per zone. Search per dest. Do not invent an inbox SLA because a client yelled.
This page is dest classify after a forward hop. It is not “does forwarding hurt deliverability” as a general reputation essay, and it is not an outbound 550 ticket. Free has no send-as. Split those. MailerZ is not IMAP, not Workspace, not SOC 2, not an inbox SLA. The store — 14 days on Free, 90 on paid, 180 on Unlimited — keeps hop evidence. It is not Vault. Buying Workspace to fix spam on forwarded copies is a suite purchase. Quote Google live. It still classifies. When this page is closed, the next physical action is a lookup and a dest search, not another inboxing blog.
A diagnosis you can paste into a ticket
Write four lines before you remap. One: public MX from two views, leftover hosts named or “none.” Two: history for the unique subject — accepted, forwarded, dest code, or empty. Three: Header From on original — stranger, or rewritten. Four: dest search — All Mail, spam, Promotions, trash, filters. If line one is leftover MX, stop talking about spam. If line two is empty and MX is exclusive, the alias may be unnamed or the probe never left. If line three is rewritten, you are on the old hop. If line four found the subject, dest classify happened. Train Gmail if you want. Leave the alias.
BIMI, a pretty logo, and a green lock in a DNS tool do not file Primary. Neither does a larger alias cap. Neither does catch-all. Hold unknowns so harvest does not train the spam button. Self-send last, if at all. If you must demonstrate the path to a colleague, use another provider and a unique subject they can search without opening your laptop. Two dests need two searches. Mixed 250 and junk is two facts, not a broken map.
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). Those documents authorize sending. They do not move Gmail tabs. Gmail Send mail as is a different hop and lives in Google Gmail Help — Send mail from a different address. Do not open that wizard because inbound spam scared you. Inbound first. Search first. Then decide whether send-as is even the question. If the unique subject is already in spam, training the dest is cheaper than another DNS screenshot. Remapping hello@ will not untrain a junk button. Search the unique subject again after you train, then stop.
When two dests disagree on the same sender
hello@ can fan out to two Gmail accounts and produce two folders. Founder A marks a vendor as important. Founder B reported that vendor last year. After dest 250, one copy sits in Primary and the other sits in spam. That is not a broken alias and not leftover MX. It is two junk models on two stores. Probe both dests with the same unique subject. Open original on both. If Header From matches and history shows two forwarded hops, leave the map. Train the dest that junked. Do not delete hello@ because one human is noisier.
A Workspace admin quarantine is a third folder. If the dest is a Workspace user, ask whether admin routing or a compliance hold ate the copy before the user tab. MailerZ history showing dest 250 only proves Gmail accepted the SMTP session. It does not prove the user mailbox was the final file. Search the admin quarantine before you remap. Confirm MailerZ pricing only if you needed a longer store to keep that hop row — not because one dest junked.
FAQ
- Why does forwarded email go to Gmail spam when DNS looks correct?
- Because “DNS looks correct” is usually your SPF, DKIM, and MX screenshot, not the stranger’s reputation or Gmail’s classify hop. Prove exclusive MX, intact Header From, and an external probe. Then search spam and filters. MailerZ does not promise Primary.
- Does a green SPF check on my domain place inbound mail?
- No. SPF on your domain describes who may send as you. A customer writing to hello@ is a different author. Their authentication is their problem. Your pretty records do not move their copy out of spam.
- Does this require a new mailbox?
- No. MailerZ is not IMAP. Gmail stays the store. Buying Workspace does not turn dest classify into an inbox SLA.
- What should I check first?
- Public MX from two views, leftover hosts, Header From on original, a unique subject from another provider, then Gmail All Mail, spam, Promotions, and user filters. Self-send last, if at all.
- Will rewriting Header From fix spam?
- It usually makes authentication noisier. MailerZ does not rewrite Header From on inbound. Envelope SRS only. If another forwarder rewrote From, you are debugging that hop, not this one.
- Is this an inbox-placement guarantee?
- No. History 250 plus dest classify in spam can both be true. Limits and DNS are not an inbox SLA. Confirm pricing only for plan ceilings, not for Primary.
Key takeaways
- Your DNS screenshot is not Gmail classify.
- Empty history is leftover MX or unnamed alias, not spam.
- Dest 250 plus spam is hop four. Search All Mail.
- MailerZ does not rewrite Header From. Do not “fix” spam by rewriting it.
- Self-send lies. Probe from another mailbox.
- User filters and blocked senders live on Gmail, not on MX.
- SPF on your domain does not place a stranger’s mail.
- Plans are capacity. Confirm /pricing. Not an inbox SLA.
Conclusion and next action
Forwarded mail lands in Gmail spam when Gmail classifies it there, when leftover MX hid the hop, when From was rewritten, or when a dest filter ate it. A correct-looking zone file does not pick the tab. Prove MX. Probe. Open original. Search. Then stop remapping.
Name the hop, then the folder
Start free, cut leftovers, prove a unique subject in All Mail.
Do not call Promotions a bounce. Do not promise Primary.
Review quarterly, or sooner if Gmail or MailerZ hop behavior changes. Author: MailerZ editorial, Secuno LLC.