Some emails not forwarding is the most honest ticket title in DNS. Total outage is rare. Splits are common. Leftover MX sends a random half to Google. A missing alias holds or rejects one local-part. One sender is blocked at the destination. The cause is findable if you stop treating “email” as one object.
Quick answer for some emails not forwarding
Write a matrix: which local-parts, which senders, which destinations, which times. A 2×2 beats a vibe.
If named aliases work and unknowns do not, you are on Free HOLD or you never created the name. That is policy, not a down MX.
If Stripe works and a registrar form does not, check leftover MX and the form’s own From. Different senders pick different MX when the set is mixed — actually they should all see the same MX set. If the set is mixed, different MTAs may order hosts differently. That is the coin flip.
If everything works except one destination mailbox, that destination is filtering or full. History will show the hop. The miss is after us.
Authoritative mail transport is still IETF RFC 5321 — Simple Mail Transfer Protocol. troubleshooting. delivery recovery. tools.
Build the matrix before you republish MX. Partial failure is information.
Start free — one domainThe real decision
People reset all DNS when one alias is missing. They create a second outage.
Decision: split by recipient, by sender, or by time (TTL). Those three splits have different fixes.
Agencies should attach the matrix to the ticket or refuse the ticket.
A suite will also split if you dual-MX with MailerZ. Buying seats does not unmix the coin flip.
When this path is enough
- You can list working and failing examples with timestamps.
- You can look up MX from two resolvers.
- You can open history for both classes.
When this is the wrong ticket
- You only know “clients are complaining.”
- You will add a backup MX while debugging.
- You will enable catch-all FORWARD to hide naming mistakes.
Technical mail flow
Every sender resolves the same MX set. If the set contains two products, some connections go left. Those messages never appear in MailerZ. The other half looks “fine.” That is the signature of mixed MX.
Same product, missing local-part: we see the inbound and HOLD or 550. Gmail never gets it. Users say “some forward.” History says hold.
Same product, destination refuse on one mailbox: we see 550 from that destination. Other mailboxes work.
TTL tails after a delete: some resolvers still have old MX. Time-split. Wait and prove from two resolvers.
Step-by-step decision path
- Build the matrix. Recipient, sender, destination, time.
- Lookup MX twice. Same hosts? Leftovers?
- Open history for a hit and a miss. Empty miss = not our hop.
- If empty miss, unmix MX. Wait TTL.
- If hold, create the alias or accept HOLD. Do not panic-FORWARD.
- If destination 550, take that text. Different admin.
- Re-probe each class. Unique subjects.
Worked examples
hello@ works, jobs@ does not. jobs@ never created. HOLD. Matrix was recipient.
Half of vendors missing. aspmx leftover. Matrix was sender only because of MX order. Unmix. All vendors appear.
All aliases work to founder Gmail, none to the accountant Outlook that is full. Destination 550 mailbox full. Matrix was destination.
Worked yesterday, fails for some ISPs today. TTL after a sloppy MX edit. Two resolvers disagreed. Waited. Agreed. Fixed.
Catch-all FORWARD “fixed” missing names and created a spam flood. Reverted to HOLD and created the three real names. Matrix stayed honest.
A miss with empty history is not a filter. It is a path you do not own yet.
Open troubleshootingFailure modes and proof
| Symptom | Likely cause | Proof |
|---|---|---|
| Some senders only | Mixed MX | Two resolvers + empty history |
| Some local-parts only | Missing alias / HOLD | History hold |
| Some destinations only | Their refuse or filter | SMTP after hop |
| Some hours only | TTL tail | Resolver disagreement |
| After dual MX “backup” | You created the split | Delete backup |
| Self-send always works | Short-circuit | Other mailbox |
| Unknowns only | Free HOLD | Policy |
| One ESP only | Their retry to old MX | Wait TTL or they cache |
MailerZ workflow and product boundary
Secuno LLC operates MailerZ. Site: mailerz.net. App: mail.mailerz.net. Envelope SRS only. Header From, Subject, Date, Message-ID, body, and MIME are never rewritten. Not IMAP. Not an open relay.
What MailerZ does
- Accept MX for verified domains.
- Rewrite envelope MAIL FROM with SRS on the forward.
- Leave Header From and MIME intact.
- Hold unknowns on Free. Optional paid FORWARD.
- Paid SMTP from approved identities. Dashboard SPF, DKIM, and DMARC instructions.
- 550 for unauthorized From. Not an open relay.
What MailerZ does not do
- Guarantee Gmail Primary or any inbox placement rate.
- Host IMAP, Calendar, or a Workspace suite.
- Send-as on Free.
- SOC 2, ISO 27001, HIPAA, review counts, or an uptime SLA. Controls: Security and Trust Center.
Plans: pricing. Free $0, 1 domain, 10 aliases, 1 seat, 14-day store, send-as disabled, SMTP and API disabled. Solo $40/year, 5 domains, 25 aliases, 90-day, 2,500 outgoing, 20/hour. Starter $8 or $80, 8/50/5, 5,000, 40/hour. Business $19 or $190, 25/200/25, 12,000, 60/hour. Agency $39 or $390, 100/500/50, 20,000, 60/hour. Unlimited is $99/month or $990/year. Annual Starter, Business, and Agency include two months free versus monthly. Solo is yearly only.
Cost, alternatives, and trade-offs
| Approach | You get | You give up |
|---|---|---|
| Matrix + exclusive MX | End of coin flip | Requires leftover delete |
| Catch-all FORWARD as cover | Names appear | Spam |
| Dual MX backup | Worse split | Never do |
| Suite plus MailerZ MX | Classic split | Unmix |
Field notes
ESPs cache MX. After you unmix, some platforms take hours. Say that in the customer email.
Plus-tags are not aliases on this product. Do not expect hello+x@ to exist as a created name.
Related: /troubleshooting, /delivery-recovery, /tools, /docs.
Document the matrix format so juniors do not file “email is down.”
14/90 day store: export the miss if you will need it after the window.
Null MX plus MailerZ is another split — actually a refuse-all plus a real MX if both exist. Remove the null.
Do not change SPF to fix a recipient split.
Agency: one matrix per domain. Do not blend clients.
Quarterly: leftover MX returns after a “helpful” host restore. Re-lookup.
Teaching phrase: “Some is a clue. All is a different ticket.”
Search demand for some emails not forwarding usually arrives as a screenshot, not a sentence. Ask for the received copy, the public MX set, and the plan name before you change a record. Some Emails Forward and Others Do Not: How to Find the Cause is a workflow, not a checkbox.
Write a one-paragraph policy the team can reuse for some emails not forwarding. Name the hop (inbound versus outbound), the proof artifact, and the thing you will not do (dual MX, From rewrite, second SPF record). Put the paragraph in the ticket template.
Change control matters more than a clever record. One person owns DNS for this domain. Adding an include, a selector, or a backup MX requires a ticket. Most regressions in some emails not forwarding are Friday edits without a probe.
Self-send remains invalid for some emails not forwarding. Gmail can short-circuit. Outlook can look local. Use a mailbox on another provider and a unique subject. If the customer refuses, the ticket stays open.
Leftover MX masquerades as every authentication and spam incident. If history is empty, some emails not forwarding is the wrong title until two resolvers agree on one product. Delete aspmx, Microsoft, and registrar MX. Wait TTL.
Free HOLD and missing aliases masquerade as outages. History shows the hold. Create the named local-part or accept that unknowns stay. Catch-all FORWARD is paid, optional, and a spam trade-off — not a debugger for some emails not forwarding.
Paid send-as is a different hop from inbound some emails not forwarding. Free cannot send. Unauthorized From is 550 / 550 5.7.1. Publishing prettier DNS will not authorize a From the product has not approved.
Destination filters still win after a clean hop. Some Emails Forward and Others Do Not: How to Find the Cause does not include an inbox placement SLA, review counts, or a Primary guarantee. Say that once, early, so the customer stops buying a story you cannot ship.
Proof packet for some emails not forwarding: public MX from two resolvers, inbound received copy with Header From, Authentication-Results, outbound received copy if they send, plan name, and the SMTP line if anything refused. That packet ends folklore.
Retention is 14 days on Free and 90 on paid. Export headers while they live. some emails not forwarding arguments without artifacts become myths. The destination inbox is the archive, not the hop store.
Agencies should not blend clients in one some emails not forwarding thread. One domain, one matrix, one MX screenshot. Agency plan limits are 100 domains, 500 aliases, 50 seats, 20,000 outgoing, 60/hour — still not unlimited, still not an SLA.
Security hygiene: no SMTP passwords in the some emails not forwarding ticket, no message bodies in chat, no invented SOC 2. Controls live on the Security and Trust Center. Secrets rotate if they leaked.
Related operations stay on real routes: forwarding, send-as, troubleshooting, tools, delivery recovery, docs, pricing. Do not invent a pillar. If some emails not forwarding is actually leftover MX, say leftover MX.
Refresh cadence is at least quarterly, sooner after a domain transfer, panel change, ESP trial, or dashboard host change. Some Emails Forward and Others Do Not: How to Find the Cause goes stale when the zone changes and the runbook does not.
If two products still share MX after you explained the coin flip, stop adding records. Exclusive MX is a hard stop. some emails not forwarding cannot be correct on a split path.
If Header From is already rewritten, stop tuning SPF for some emails not forwarding. Change the hop. MailerZ will not offer a From-replace control. Honest identity is the product.
If the customer wants a suite, sell the suite as Calendar and a hosted mailbox, not as a magic fix for some emails not forwarding. Workspace and Microsoft 365 are different architectures with their own filters and their own 550s.
Hourly and monthly send-as ceilings (disabled/2,500/5,000/12,000/20,000 outgoing; 20/40/60/60 per hour by plan) produce refuses that look like some emails not forwarding outages. Read counters before you republish DKIM.
Null MX plus a real MX is another lie. Remove the lone-dot refuse if you intend to receive. Empty inbound plus a pretty some emails not forwarding essay is still a refuse-all.
After you change anything, wait TTL, probe from another mailbox, and store the new received source next to the MX screenshot. Some Emails Forward and Others Do Not: How to Find the Cause is done when proof exists, not when the panel is green.
Field story 1 for some emails not forwarding: hello@ works, jobs@ does not. jobs@ never created. HOLD. Matrix was recipient. Keep that story in the runbook so the next person does not reopen Some Emails Forward and Others Do Not: How to Find the Cause from zero.
Field story 2 for some emails not forwarding: Half of vendors missing. aspmx leftover. Matrix was sender only because of MX order. Unmix. All vendors appear. Keep that story in the runbook so the next person does not reopen Some Emails Forward and Others Do Not: How to Find the Cause from zero.
Field story 3 for some emails not forwarding: All aliases work to founder Gmail, none to the accountant Outlook that is full. Destination 550 mailbox full. Matrix was destination. Keep that story in the runbook so the next person does not reopen Some Emails Forward and Others Do Not: How to Find the Cause from zero.
Field story 4 for some emails not forwarding: Worked yesterday, fails for some ISPs today. TTL after a sloppy MX edit. Two resolvers disagreed. Waited. Agreed. Fixed. Keep that story in the runbook so the next person does not reopen Some Emails Forward and Others Do Not: How to Find the Cause from zero.
Field story 5 for some emails not forwarding: Catch-all FORWARD “fixed” missing names and created a spam flood. Reverted to HOLD and created the three real names. Matrix stayed honest. Keep that story in the runbook so the next person does not reopen Some Emails Forward and Others Do Not: How to Find the Cause from zero.
For some emails not forwarding, symptom “Some senders only” usually means Mixed MX. Isolate it with Two resolvers + empty history. Do not stack a second change until that proof exists.
For some emails not forwarding, symptom “Some local-parts only” usually means Missing alias / HOLD. Isolate it with History hold. Do not stack a second change until that proof exists.
For some emails not forwarding, symptom “Some destinations only” usually means Their refuse or filter. Isolate it with SMTP after hop. Do not stack a second change until that proof exists.
For some emails not forwarding, symptom “Some hours only” usually means TTL tail. Isolate it with Resolver disagreement. Do not stack a second change until that proof exists.
For some emails not forwarding, symptom “After dual MX “backup”” usually means You created the split. Isolate it with Delete backup. Do not stack a second change until that proof exists.
For some emails not forwarding, symptom “Self-send always works” usually means Short-circuit. Isolate it with Other mailbox. Do not stack a second change until that proof exists.
For some emails not forwarding, symptom “Unknowns only” usually means Free HOLD. Isolate it with Policy. Do not stack a second change until that proof exists.
For some emails not forwarding, symptom “One ESP only” usually means Their retry to old MX. Isolate it with Wait TTL or they cache. Do not stack a second change until that proof exists.
Setup step “Build the matrix.” for some emails not forwarding: Recipient, sender, destination, time. Skip it and Some Emails Forward and Others Do Not: How to Find the Cause turns into a second ticket next week. Do the step, store the artifact, then continue.
Setup step “Lookup MX twice.” for some emails not forwarding: Same hosts? Leftovers? Skip it and Some Emails Forward and Others Do Not: How to Find the Cause turns into a second ticket next week. Do the step, store the artifact, then continue.
Setup step “Open history for a hit and a miss.” for some emails not forwarding: Empty miss = not our hop. Skip it and Some Emails Forward and Others Do Not: How to Find the Cause turns into a second ticket next week. Do the step, store the artifact, then continue.
Setup step “If empty miss, unmix MX.” for some emails not forwarding: Wait TTL. Skip it and Some Emails Forward and Others Do Not: How to Find the Cause turns into a second ticket next week. Do the step, store the artifact, then continue.
Setup step “If hold, create the alias or accept HOLD.” for some emails not forwarding: Do not panic-FORWARD. Skip it and Some Emails Forward and Others Do Not: How to Find the Cause turns into a second ticket next week. Do the step, store the artifact, then continue.
Setup step “If destination 550, take that text.” for some emails not forwarding: Different admin. Skip it and Some Emails Forward and Others Do Not: How to Find the Cause turns into a second ticket next week. Do the step, store the artifact, then continue.
Setup step “Re-probe each class.” for some emails not forwarding: Unique subjects. Skip it and Some Emails Forward and Others Do Not: How to Find the Cause turns into a second ticket next week. Do the step, store the artifact, then continue.
Trade-off on some emails not forwarding: choosing Matrix + exclusive MX gets you End of coin flip and gives up Requires leftover delete. Write that exchange on the quote so nobody pretends it is free.
Trade-off on some emails not forwarding: choosing Catch-all FORWARD as cover gets you Names appear and gives up Spam. Write that exchange on the quote so nobody pretends it is free.
Trade-off on some emails not forwarding: choosing Dual MX backup gets you Worse split and gives up Never do. Write that exchange on the quote so nobody pretends it is free.
Trade-off on some emails not forwarding: choosing Suite plus MailerZ MX gets you Classic split and gives up Unmix. Write that exchange on the quote so nobody pretends it is free.
Some Emails Forward and Others Do Not: How to Find the Cause is enough when You can list working and failing examples with timestamps. If that condition is false, stop implementing some emails not forwarding and reopen the decision.
Some Emails Forward and Others Do Not: How to Find the Cause is enough when You can look up MX from two resolvers. If that condition is false, stop implementing some emails not forwarding and reopen the decision.
Some Emails Forward and Others Do Not: How to Find the Cause is enough when You can open history for both classes. If that condition is false, stop implementing some emails not forwarding and reopen the decision.
Some Emails Forward and Others Do Not: How to Find the Cause is the wrong ticket when You only know “clients are complaining.”. Name the correct system instead of forcing some emails not forwarding to cover it.
Some Emails Forward and Others Do Not: How to Find the Cause is the wrong ticket when You will add a backup MX while debugging. Name the correct system instead of forcing some emails not forwarding to cover it.
Some Emails Forward and Others Do Not: How to Find the Cause is the wrong ticket when You will enable catch-all FORWARD to hide naming mistakes. Name the correct system instead of forcing some emails not forwarding to cover it.
Write some emails not forwarding in the subject line of the ticket and the layer in the first sentence. If the layer is leftover MX, say leftover MX. If the layer is HOLD, say HOLD. If the layer is a destination 550, paste the text. Some Emails Forward and Others Do Not: How to Find the Cause stays short when the first sentence is honest.
Keep a standing calendar note for some emails not forwarding: monthly external probe, leftover MX lookup, and a glance at send-as counters if you are paid. Five minutes. The outage you avoid is the Friday dual-MX restore.
When two vendors disagree about some emails not forwarding, believe artifacts: two resolvers, one received copy, one history row. Do not believe the prettier admin center. Registrar dots lie. Composer UIs lie. Self-send lies.
Teach the next hire the MailerZ split before they touch some emails not forwarding: envelope may change, Header From must not, Free cannot send, unknowns HOLD, leftover MX is a hard stop, no inbox SLA, no SOC 2 sticker. That speech prevents a class of tickets.
If some emails not forwarding appears in an RFP, answer with published caps and hop evidence. Decline inbox-rate clauses. Decline fake certifications. Point at pricing and the Security and Trust Center. Some Emails Forward and Others Do Not: How to Find the Cause is not a place to invent enterprise theater.
Export while the 14- or 90-day window still has the some emails not forwarding hop. Future-you will not remember the SMTP sentence. The destination mailbox remains the archive. We will not grow the store because a blog asked.
Do not bundle unrelated edits with some emails not forwarding. Rotating SMTP while republishing MX while enabling FORWARD is how you lose the ability to name the failure. One change, one probe, one stored copy.
If you need a suite, buy a suite for Calendar and a hosted mailbox. If you need a hop, buy a hop. Some Emails Forward and Others Do Not: How to Find the Cause does not become Exchange because a quote stacked seats next to aliases.
FAQ
What is the safest way to handle some emails not forwarding?
Build a matrix of sender, recipient, destination, and time. Empty history means leftover or cached MX. A hold means a missing name on Free. A hop plus destination 550 is their side. Do not add backup MX.
Does this require a new mailbox?
No. MailerZ is Mail Box portal webmail (Inbox, Sent, New email). It is not IMAP or POP. Gmail or Outlook stays the store. Buy a suite seat only if you need Calendar and a hosted mailbox, not because this workflow failed.
Will it work with Gmail or Outlook?
Yes as a destination inbox when MX is exclusive and the alias exists. Header From stays the original sender on inbound. Paid send-as is a separate hop. Free has no send-as. Self-send from the same Gmail can hide failures.
What DNS records are involved?
Inbound: verification TXT, one MailerZ MX set, leftover MX removed. Outbound send-as: one SPF TXT, DKIM, and DMARC as the dashboard states. Two MX products split mail. Two SPF records permerror.
What should I test before production?
Prove inbound from another mailbox with a unique subject. Confirm Header From and history. If you send, prove paid SMTP to a third-party mailbox. Wait TTL after DNS deletes. Composer UI is not proof.
Key takeaways
- Partial failure is a split. Matrix it.
- Mixed MX is the usual sender split.
- Missing names are HOLD or 550.
- Destination splits show a hop.
- TTL explains time splits.
- Do not dual-MX.
- Do not hide names with FORWARD.
- Self-send lies.
- History plus two resolvers.
- No inbox SLA.
Conclusion and next action
When some emails forward and others do not, the cause is a split you can name. Recipient, sender, destination, or time.
Next action: write four rows, look up MX twice, open two history items, and change only the system the matrix points at.
Ready to name the split
Start free, create the real names, keep MX exclusive.
Three aliases on Free. History will tell you which name never existed.
Review quarterly, or sooner if DNS hosts or dashboard instructions change. Author: MailerZ editorial, Secuno LLC.