Migrate catch all domain work goes badly when the old host forwarded every guess into Gmail and you copy that policy on day one. You inherit a spam cannon. HOLD unknowns on MailerZ, especially on Free where HOLD is the only unknown policy. Create the real names. Audit what people actually use. Paid FORWARD is a later, optional trade-off.
Quick answer for migrate catch all domain
Old catch-all accepted typos and harvested names. New HOLD shows you the list. That list is the migration gift.
Free cannot FORWARD unknowns. If you need FORWARD, you are on paid and you still should wait.
Directory harvesting becomes your problem the minute you FORWARD. Attackers guess ceo@, accounts@, plus first names.
Leftover MX plus catch-all on the old host means some spam still lands at Google. Unmix so your audit is complete.
Authoritative mail transport is still IETF RFC 5321 — Simple Mail Transfer Protocol. migration planner. docs. troubleshooting.
Prove the hop with a received copy before you treat migrate catch all domain as a DNS edit.
Start free — one domainThe real decision
Founders fear missing a human typo more than they fear a flooded inbox. Write the trade-off down.
Decision: which local-parts are contractual (billing, legal, support) versus guesses.
Agencies should not FORWARD client catch-alls by default. Bill for the audit.
A suite catch-all is also a spam magnet. Seats do not sanitize guesses.
When this path is enough
- You can staff exclusive MX and named aliases.
- You will keep Header From intact.
- You can probe from another mailbox.
When this is the wrong ticket
- History is empty and leftovers remain.
- You want an inbox placement SLA.
- You plan to rewrite visible From.
Technical mail flow
Cut MX exclusive. Unknowns HOLD. You read holds. You promote names. You leave the rest held or rejected later if you add that policy.
Named aliases forward immediately. That is the safe path for invoices@.
Send-as is unrelated. Do not delay MX because SMTP is unconfigured.
Self-send will not reveal harvester volume. Real internet will.
Step-by-step decision path
- Inventory leftovers. Screenshot current MX, SPF, DKIM, NS.
- Verify the domain. TXT as the dashboard states.
- Create named aliases first. Do not cut MX onto empty maps.
- Publish one MX set. Delete Google, Microsoft, registrar leftovers.
- Prove from another mailbox. Unique subject. Header From intact.
- Only then send-as if paid. Dashboard SPF/DKIM. Outbound probe.
- Store the proof packet. MX, hop, headers, plan name.
Worked examples
A shop copied FORWARD from the registrar. Gmail died in two days. Reverted to HOLD, created eight real names, survived.
Inventory from Stripe, Apple, Google Workspace old users, and the footer of the website covered 90% of humans.
ceo@ was only ever spam. They did not create it. Holds proved it.
Agency inherited 40 client catch-alls. They HOLD-migrated one per day. The ones they FORWARDED first created emergency tickets.
Typo helloo@ was real for one vendor. They created it after a hold. That is what HOLD is for.
If history and public MX disagree, believe MX first.
Open the matching guideFailure modes and proof
| Symptom | Likely cause | Proof |
|---|---|---|
| Empty history | Leftover or cached MX | Two resolvers |
| Unknowns missing | Free HOLD | History hold |
| Header From rewritten | Wrong hop | Received From |
| SMTP 550 send-as | Free or unauthorized From | History line |
| spf=fail hop two | Naive envelope | Return-Path |
| Still spam after clean hop | Destination filters | Not an SLA |
| Self-send clean | Short-circuit | Other mailbox |
| Wrong DNS panel | NS ≠ registrar UI | NS lookup |
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 |
|---|---|---|
| Exclusive MX + named aliases | Debuggable path | You must delete leftovers |
| Dual MX backup | Feels safe | Coin-flip misses |
| From rewrite | Cosmetic SPF | Trust and DKIM |
| Suite seats | Hosted mailbox | Per-user price |
Field notes
Related: /aliases-catch-all, /migration-planner, /troubleshooting, /delivery-recovery.
Do not claim MailerZ strips plus tags on custom domains.
Audit weekly during the first month. Then monthly.
If you FORWARD, name an owner who will watch junk.
Search demand for migrate catch all domain 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. How to Migrate a Catch-All Domain Without Creating a Spam Problem is a workflow, not a checkbox.
Write a one-paragraph policy the team can reuse for migrate catch all domain. 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 migrate catch all domain are Friday edits without a probe.
Self-send remains invalid for migrate catch all domain. 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, migrate catch all domain 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 migrate catch all domain.
Paid send-as is a different hop from inbound migrate catch all domain. 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. How to Migrate a Catch-All Domain Without Creating a Spam Problem 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 migrate catch all domain: 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. migrate catch all domain arguments without artifacts become myths. The destination inbox is the archive, not the hop store.
Agencies should not blend clients in one migrate catch all domain 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 migrate catch all domain 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 migrate catch all domain 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. How to Migrate a Catch-All Domain Without Creating a Spam Problem 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. migrate catch all domain cannot be correct on a split path.
If Header From is already rewritten, stop tuning SPF for migrate catch all domain. 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 migrate catch all domain. 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 migrate catch all domain 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 migrate catch all domain 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. How to Migrate a Catch-All Domain Without Creating a Spam Problem is done when proof exists, not when the panel is green.
Field story 1 for migrate catch all domain: A shop copied FORWARD from the registrar. Gmail died in two days. Reverted to HOLD, created eight real names, survived. Keep that story in the runbook so the next person does not reopen How to Migrate a Catch-All Domain Without Creating a Spam Problem from zero.
Field story 2 for migrate catch all domain: Inventory from Stripe, Apple, Google Workspace old users, and the footer of the website covered 90% of humans. Keep that story in the runbook so the next person does not reopen How to Migrate a Catch-All Domain Without Creating a Spam Problem from zero.
Field story 3 for migrate catch all domain: ceo@ was only ever spam. They did not create it. Holds proved it. Keep that story in the runbook so the next person does not reopen How to Migrate a Catch-All Domain Without Creating a Spam Problem from zero.
Field story 4 for migrate catch all domain: Agency inherited 40 client catch-alls. They HOLD-migrated one per day. The ones they FORWARDED first created emergency tickets. Keep that story in the runbook so the next person does not reopen How to Migrate a Catch-All Domain Without Creating a Spam Problem from zero.
Field story 5 for migrate catch all domain: Typo helloo@ was real for one vendor. They created it after a hold. That is what HOLD is for. Keep that story in the runbook so the next person does not reopen How to Migrate a Catch-All Domain Without Creating a Spam Problem from zero.
For migrate catch all domain, symptom “Empty history” usually means Leftover or cached MX. Isolate it with Two resolvers. Do not stack a second change until that proof exists.
For migrate catch all domain, symptom “Unknowns missing” usually means Free HOLD. Isolate it with History hold. Do not stack a second change until that proof exists.
For migrate catch all domain, symptom “Header From rewritten” usually means Wrong hop. Isolate it with Received From. Do not stack a second change until that proof exists.
For migrate catch all domain, symptom “SMTP 550 send-as” usually means Free or unauthorized From. Isolate it with History line. Do not stack a second change until that proof exists.
For migrate catch all domain, symptom “spf=fail hop two” usually means Naive envelope. Isolate it with Return-Path. Do not stack a second change until that proof exists.
For migrate catch all domain, symptom “Still spam after clean hop” usually means Destination filters. Isolate it with Not an SLA. Do not stack a second change until that proof exists.
For migrate catch all domain, symptom “Self-send clean” usually means Short-circuit. Isolate it with Other mailbox. Do not stack a second change until that proof exists.
For migrate catch all domain, symptom “Wrong DNS panel” usually means NS ≠ registrar UI. Isolate it with NS lookup. Do not stack a second change until that proof exists.
Setup step “Inventory leftovers.” for migrate catch all domain: Screenshot current MX, SPF, DKIM, NS. Skip it and How to Migrate a Catch-All Domain Without Creating a Spam Problem turns into a second ticket next week. Do the step, store the artifact, then continue.
Setup step “Verify the domain.” for migrate catch all domain: TXT as the dashboard states. Skip it and How to Migrate a Catch-All Domain Without Creating a Spam Problem turns into a second ticket next week. Do the step, store the artifact, then continue.
Setup step “Create named aliases first.” for migrate catch all domain: Do not cut MX onto empty maps. Skip it and How to Migrate a Catch-All Domain Without Creating a Spam Problem turns into a second ticket next week. Do the step, store the artifact, then continue.
Setup step “Publish one MX set.” for migrate catch all domain: Delete Google, Microsoft, registrar leftovers. Skip it and How to Migrate a Catch-All Domain Without Creating a Spam Problem turns into a second ticket next week. Do the step, store the artifact, then continue.
Setup step “Prove from another mailbox.” for migrate catch all domain: Unique subject. Header From intact. Skip it and How to Migrate a Catch-All Domain Without Creating a Spam Problem turns into a second ticket next week. Do the step, store the artifact, then continue.
Setup step “Only then send-as if paid.” for migrate catch all domain: Dashboard SPF/DKIM. Outbound probe. Skip it and How to Migrate a Catch-All Domain Without Creating a Spam Problem turns into a second ticket next week. Do the step, store the artifact, then continue.
Setup step “Store the proof packet.” for migrate catch all domain: MX, hop, headers, plan name. Skip it and How to Migrate a Catch-All Domain Without Creating a Spam Problem turns into a second ticket next week. Do the step, store the artifact, then continue.
Trade-off on migrate catch all domain: choosing Exclusive MX + named aliases gets you Debuggable path and gives up You must delete leftovers. Write that exchange on the quote so nobody pretends it is free.
Trade-off on migrate catch all domain: choosing Dual MX backup gets you Feels safe and gives up Coin-flip misses. Write that exchange on the quote so nobody pretends it is free.
Trade-off on migrate catch all domain: choosing From rewrite gets you Cosmetic SPF and gives up Trust and DKIM. Write that exchange on the quote so nobody pretends it is free.
Trade-off on migrate catch all domain: choosing Suite seats gets you Hosted mailbox and gives up Per-user price. Write that exchange on the quote so nobody pretends it is free.
How to Migrate a Catch-All Domain Without Creating a Spam Problem is enough when You can staff exclusive MX and named aliases. If that condition is false, stop implementing migrate catch all domain and reopen the decision.
How to Migrate a Catch-All Domain Without Creating a Spam Problem is enough when You will keep Header From intact. If that condition is false, stop implementing migrate catch all domain and reopen the decision.
How to Migrate a Catch-All Domain Without Creating a Spam Problem is enough when You can probe from another mailbox. If that condition is false, stop implementing migrate catch all domain and reopen the decision.
How to Migrate a Catch-All Domain Without Creating a Spam Problem is the wrong ticket when History is empty and leftovers remain. Name the correct system instead of forcing migrate catch all domain to cover it.
How to Migrate a Catch-All Domain Without Creating a Spam Problem is the wrong ticket when You want an inbox placement SLA. Name the correct system instead of forcing migrate catch all domain to cover it.
How to Migrate a Catch-All Domain Without Creating a Spam Problem is the wrong ticket when You plan to rewrite visible From. Name the correct system instead of forcing migrate catch all domain to cover it.
Write migrate catch all domain 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. How to Migrate a Catch-All Domain Without Creating a Spam Problem stays short when the first sentence is honest.
Keep a standing calendar note for migrate catch all domain: 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 migrate catch all domain, 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 migrate catch all domain: 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 migrate catch all domain 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. How to Migrate a Catch-All Domain Without Creating a Spam Problem is not a place to invent enterprise theater.
Export while the 14- or 90-day window still has the migrate catch all domain 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 migrate catch all domain. 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. How to Migrate a Catch-All Domain Without Creating a Spam Problem does not become Exchange because a quote stacked seats next to aliases.
FAQ
What is the safest way to handle migrate catch all domain?
Do not enable catch-all FORWARD during cutover. Create named aliases from an inventory. Exclusive MX. Probe those names. Audit holds. FORWARD only if a paid plan and a written owner exist.
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
- Exclusive MX is a hard stop.
- Header From stays the original sender.
- SRS is envelope-only.
- Free holds unknowns and cannot send-as.
- 550 means read the text.
- Self-send lies.
- No inbox SLA.
- 14- or 90-day store is not an archive.
- MailerZ is not IMAP.
- No SOC 2, ISO, or HIPAA claims.
Conclusion and next action
Migrate a catch-all without a spam problem by refusing to copy FORWARD on day one.
Next action: inventory contractual names, HOLD the rest, cut MX, promote holds that are human.
Ready to HOLD first
Start free with HOLD and the names you can prove.
Free holds unknowns. That is the safer migration default.
Review quarterly, or sooner if DNS hosts or dashboard instructions change. Author: MailerZ editorial, Secuno LLC.