Personal domain catch all is usually a bad default. HOLD unknown on Free for a reason: the internet will guess your name, your dog, and your old employers. FORWARD turns that into a Gmail firehose and trains junk. Create named aliases for the strings you actually give out. Enable paid FORWARD only with a written reason and an expiry date.
Quick answer for personal domain catch all
Most personal domains do not need catch-all. They need two or three named aliases.
RFC 5321 will happily deliver garbage if you ask it to.
MailerZ Free holds unknown. That is the safe personal default.
Paid FORWARD is optional. It is not a virtue.
If you gave out random local-parts for years, inventory them and create the real ones. Do not FORWARD forever as a memory substitute.
Start free and send a fake local-part. Confirm it stays held.
Authoritative mail transport is defined in IETF RFC 5321 — Simple Mail Transfer Protocol. Product path: aliases and catch-all, email forwarding, and custom-domain email alias.
User problem and decision criteria
Decision criteria: how many strings you actually published, junk tolerance, whether you can review held mail.
Founders who used catch-all at a host think it is normal. It is normal noise.
Privacy is worse with FORWARD: every guess arrives.
Agencies should not enable FORWARD on personal domains by default.
Plus-addressing is not catch-all on your zone.
If you need one throwaway, create a named alias you can disable.
Do not invent an inboxing benefit for catch-all. It is the opposite.
If you are a public figure, HOLD plus named aliases is the professional setup.
Technical mail flow
Named hit: forward. Unknown: HOLD on Free or configured paid behavior.
FORWARD dumps guesses into Gmail. Filters learn the wrong lesson.
Disabling an abused named alias is cleaner than turning off a firehose late.
Exclusive MX so you see the whole held list.
History distinguishes hold from destination reject.
Step-by-step setup / decision path
- List every address you have ever published.
- Create those as named aliases.
- Leave unknown on HOLD.
- Exclusive MX. Probe names. Probe a fake—should hold.
- Review held weekly at first.
- Create a new named alias when a real miss appears.
- If you enable FORWARD, write an expiry.
- Disable abused names. Do not FORWARD to hide abuse.
Classify the next failure before a second DNS edit.
HOLD unknown unless you wrote a FORWARD reason.
Quote live pricing before promising alias counts.
Failure modes and proof
FORWARD to be clever: junk.
Catch-all as memory: you never inventory.
Leftover MX: incomplete holds.
Public figure + FORWARD: harassment inbox.
Free FORWARD: not on Free.
Self-send: lie.
Header rewrite: no.
Inboxing win claimed: false.
Disabled HOLD without a sheet: missed real mail later.
Kids plus FORWARD: safety issue.
Open relay fantasy: 550.
Expired store plus no review: lost real typos.
MailerZ workflow and product boundary
MailerZ is custom-domain aliasing and forwarding with optional paid send-as. Secuno LLC operates mailerz.net. The app is mail.mailerz.net. Not Workspace, not IMAP, not an open relay, not a campaign ESP.
Envelope SRS only. Header From, Subject, Date, Message-ID, body, and MIME stay intact. Exclusive MX. Hold unknown on Free. Copy SMTP host, port, and TLS or STARTTLS from the dashboard when you send.
Free: one domain, three aliases, one seat, fourteen-day store, fifty outgoing a month, no send-as. Solo forty dollars a year, fifteen aliases, ninety-day store, one hundred outgoing, five send-as per hour. Starter eight or eighty. Business nineteen or one hundred ninety. Agency thirty-nine or three hundred ninety. Quote pricing. No SOC 2, ISO, HIPAA, SLA, or inboxing percentage.
Cost, alternatives, and trade-offs
HOLD is cheaper than a burned personal Gmail.
Named aliases are cheaper than archaeology later.
FORWARD looks convenient and costs attention.
Host catch-all plus leftover MX costs incidents.
Solo for more names beats FORWARD for memory.
Agencies: default HOLD in the SOW.
Time in junk is a real cost.
No inbox KPI.
Operational depth
Treat held mail like voicemail. Short scheduled reviews beat living in it.
When a conference printed a typo of your alias, create the typo as a named alias if you will keep using that card. Otherwise tell people the real string.
Scanners will try admin@ and office@ on a personal zone. HOLD is correct.
If you used catch-all for ten years, export what you can and build the named list. Then turn FORWARD off.
Exclusive MX after leaving a host that defaulted catch-all on.
Do not publish a blog that invites people to invent local-parts. You are asking for FORWARD.
Quote paid plans only if you truly want FORWARD. Most personal domains want Solo for more named aliases, not for FORWARD.
Disable leaked shop aliases. That is another article’s move and still true here.
Keep send-as off catch-all thinking. You send as named identities.
No HIPAA story on a personal domain.
Probe the fake local-part after any policy change.
Write the decision in one sentence so future you does not “improve” it at midnight.
How personal zones get harvested
A personal domain is a short dictionary. First name, last name, first-last, last-first, the dog, the street, the old employer, admin, office, info, hello, contact. Scrapers do not need imagination. They concatenate tokens they already have from WHOIS history, GitHub, conference badges, and the about page you published in 2019. Catch-all FORWARD turns that dictionary into a delivery guarantee. Every guess becomes a message in the Gmail you actually read.
HOLD does not stop the guesses. It stops the guarantee. That is the whole product decision on a personal zone. You still have a store window. Free is fourteen days. Paid is ninety. If you never open HOLD, the guesses expire and you lose the one typo that was a real human. That is why HOLD is a review job, not a set-and-forget trophy.
Harvest also arrives as lookalike local-parts with plus tags and hyphens. Plus addressing is a Gmail filter, not a MailerZ alias. IETF RFC 5233 — Sieve Email Filtering: Subaddress Extension describes subaddressing. Do not enable FORWARD so that hello+stripe@ and hello_stripe@ and hell0@ all land. Create the one string you printed. Kill the rest.
Old host catch-all is a leftover policy, not a branding asset. If the registrar or cPanel still forwards unknown on a leftover MX row, you have two firehoses. Exclusive MailerZ MX is the first cut. HOLD is the second. Named aliases are the third. In that order.
Agencies who copy a personal catch-all onto a client zone inherit that client’s harvested dictionary plus the agency’s. Do not do that. Client zones use a short noun list and HOLD. Personal zones use a short you@ list and HOLD. The policies rhyme. The strings do not.
Named aliases that actually earn a slot
Free gives you three aliases. That is enough for a durable you@, a killable shop- prefix, and a staffed bills@ if you pay people from that domain. It is not enough for a museum of every vendor. Solo is forty dollars a year and fifteen aliases. Confirm pricing. Count before you invent a fourth public string on Free.
A named alias earns a slot when you will give it out on purpose, search it later, and disable it without taking down the domain. Conference one-offs can be a dated prefix. Bank and tax mail should be a stable bills@ that you will not rotate for fun. Dating and throwaway shops should be killable. The naming system article covers the pattern. This page is the catch-all question: do not use FORWARD as a substitute for that pattern.
If a real human mailed a typo once, you have two honest options. Create the typo as a named alias if you will keep the relationship. Or reply from the real string and ask them to update the card. The dishonest option is FORWARD forever so every future typo also arrives. That trains the next printer.
Role nouns on a personal domain—support@, careers@—are usually wrong. You are not a support desk. You are a person. If you freelance, hello@ or work@ is enough. Do not staff five roles you will not open on Saturday.
Send-as is a named identity. Free has no send-as. Do not enable FORWARD because you wanted to send as a random local-part. Map the From you will actually use. 550 5.7.1 on an unmapped From is authorization, not a reason to catch-all.
How to run HOLD without ignoring mail
Put HOLD review on a calendar. Fifteen minutes on Monday is enough for most personal zones. Search for the few strings you care about: a bank, a government form, a family member’s typo. Everything else can expire. If Monday is always a flood, you already have a harvest problem and FORWARD would have been worse.
Filename the review note with the zone and the date. “Looked at hold” in your head is not a review. Write whether you promoted a string to a named alias. That is how the named list grows without becoming a dump.
Two-factor on the destination Gmail. HOLD is not a second inbox product. MailerZ is not IMAP. The destination still needs a password you would not paste into a ticket.
After you promote a typo to an alias, foreign-probe it. Unique subject. History 250. Destination search. Self-send from the same Gmail can lie. Use a third mailbox. Exclusive MX must already be true or you are probing leftover registrar mail.
If HOLD is empty for months, that is success, not a missing feature. Do not enable FORWARD to “make sure it works.” Probe a fake local-part and confirm it does not arrive. That is the test that HOLD is doing its job.
When paid FORWARD is honest
Paid FORWARD is honest when you have a written reason, an expiry date, and a person who will audit junk weekly. Examples that can qualify: a one-month move off a host that already published a hundred random strings you cannot list; a family domain where elders will invent local-parts and you accepted the noise for a quarter; a legal hold you discussed with counsel—not a vibe, and not something MailerZ calls HIPAA.
FORWARD is not honest as “I might forget a vendor.” That is what named aliases and a password manager are for. FORWARD is not honest as “I want to see who guesses.” That is curiosity billed as operations. FORWARD is not honest on Free. Free holds unknown. Quote a paid card if you truly want FORWARD. Confirm live pricing. Solo forwards unknown. That is a trade, not a default speech.
Write the expiry. When the date hits, switch back to HOLD and keep the named aliases you learned. If you cannot name the expiry, you do not have a reason. You have a habit.
Catch-all FORWARD plus leftover MX is two owners and a firehose. Delete leftovers first. See leftover MX troubleshooting. Do not troubleshoot spam volume while Google and MailerZ both accept.
Family domains and shared guesses
A family zone with kids, parents, and a shared bills@ is still a personal domain for harvest purposes. Kids will invent names. Parents will invent names. Scrapers will invent names. HOLD plus a short printed list beats FORWARD “so Grandma’s typo works.” Teach Grandma the one string. Create a second named alias if her phone already stored a typo. Do not open the dictionary.
Shared destinations are a map, not a catch-all. Two Gmails on hello@ is dual destination. Dual MX is leftover. Do not confuse them. Write who replies.
When a child leaves for college, remap or delete their named alias. Do not leave FORWARD on so their old guesses keep arriving in a parent Gmail. That is someone else’s mail with extra steps.
Retiring a decade of catch-all
If you have run host catch-all since the domain was new, you cannot list every string that ever worked. You can still stop the firehose. Exclusive MX to MailerZ. HOLD unknown. Create the strings you still print: you@, bills@, maybe one shop- vendor you have not killed. Tell frequent senders once. Keep HOLD review for a quarter. Promote the rare real typo. Let the rest expire.
Export what the old host will give you if you need nostalgia. MailerZ is not an archive. Fourteen or ninety days is a recovery window, not a museum. We do not claim SOC 2. We do not claim an inbox SLA. We do not host IMAP folders of your 2014 guesses.
Night-you will want to turn FORWARD back on after one missed message. Write the decision on the zone sheet: HOLD, named list, review Monday. If the missed message was leftover MX, fix MX. If it was a filter, search all mail. If it was a real new string, add the alias. Those are three tickets. Catch-all is not the fourth ticket.
Probe a fake local-part after the cut and after any policy change. Confirm it does not land in Gmail. Confirm HOLD or bounce according to the plan you bought. Confirm exclusive listings on two resolvers. Filename the screenshots with the zone.
If a second operator or your future self needs the order, send this page plus the personal naming article and leftover MX troubleshooting. Named first. HOLD default. FORWARD only with expiry. Exclusive MX. Fake local-part must not arrive.
The artifacts that close personal domain catch all are a short named list, a HOLD review date, and a probe that a guess does not inbox. Everything else is a firehose you called convenience.
Shopping, travel, and why FORWARD still loses
Personal shop- and travel- prefixes are killable named aliases. When a vendor leaks, you disable that string. Catch-all FORWARD cannot disable a leak because every new guess still arrives. The shopping-alias article is the pattern. This page is the policy: do not replace that pattern with FORWARD because you might invent a prefix at the airport.
If you already printed a prefix on a boarding pass, create it as a named alias before the trip if you can. If you forgot, HOLD review after landing will show whether anyone mailed it. Promote if real. Do not flip FORWARD for a weekend and forget to flip back.
Bills and government mail should be a stable named string you will not rotate for fun. Do not put those on a catch-all hope. Searchable, staffed, exclusive MX. Two-factor on the destination.
The fake local-part probe
After HOLD is on and MX is exclusive, mail a nonsense local-part from a third mailbox. It must not appear in Gmail. History should show HOLD or the plan’s unknown policy, not a 250 into the inbox. If it inboxes, you still have leftover host catch-all or leftover MX. Fix that before you discuss FORWARD.
After you enable paid FORWARD on purpose, the same nonsense string will inbox. That is the trade you wrote an expiry for. Put the expiry on the calendar the same day. Filename the probe subjects.
Self-send is not this probe. Foreign mailbox. Unique subject. Two resolvers exclusive first.
A one-sentence decision you can keep
Write: “This personal zone uses named aliases and HOLD; FORWARD is off unless dated reason X.” Stick it in the password manager note for the domain. Future you at midnight is the threat model.
Free: one domain, three aliases, fourteen-day store, HOLD, no send-as. Solo forty dollars a year if you need more names. Confirm /pricing. No SOC 2. No inbox SLA. Not IMAP. Envelope SRS. Header From intact.
Agencies: do not copy personal FORWARD onto client zones. Clients get a noun list and HOLD. Offboard deletes maps. Leftover MX is still leftover MX.
If a second person needs the order, send this page plus personal naming and leftover MX. Named first. HOLD default. Fake local-part must not arrive. Exclusive MX.
The artifacts that close should you use catch-all on a personal domain are the sentence, the named list, and the fake-part probe. MailerZ can HOLD unknowns. It cannot unteach the internet your dictionary if you FORWARD it.
A week in the life of HOLD versus FORWARD
Monday you review HOLD. Two guesses: admin and your last name backwards. You ignore them. One typo from a cousin who reversed two letters. You create that named alias, probe it from a third mailbox, and write the date. Tuesday a shop leak hits shop-oldvendor. You disable that alias. Wednesday a scraper hits office, info, and hello. HOLD keeps Gmail quiet. Thursday you almost enable FORWARD because a conference form rejected your usual you@ and you invented a new string on the fly. You create the new named alias instead if you will keep using it. Friday you re-query MX after a registrar website save. Exclusive still. Saturday you do not live in junk. Sunday you do not flip FORWARD because you are bored.
The FORWARD week is the opposite. Monday junk is already the inbox. Tuesday you cannot tell a leak from a guess. Wednesday you miss a real bill under a pile of admin@. Thursday you create filters that hide the bill. Friday you blame Gmail. The hop was doing what you asked.
Solo at forty dollars a year buys more named aliases if three is tight. It does not require FORWARD. Quote live pricing. Do not buy FORWARD as a personality. Buy names you will stand behind. If you already have fifteen public strings, you are past Free and you still should not FORWARD. You should prune. Every public string is a future disable decision. Catch-all removes the decision and that is why it feels easy and why it fails.
A personal domain that prints you@ on a resume and also FORWARDs every guess will train recruiters to invent local-parts. Then you cannot disable a leak without disabling the resume string. Named aliases keep the resume string stable and the leak killable. That is the entire argument in one hiring cycle.
If you share the domain with a partner, write who reviews HOLD. A review that nobody owns is not a review. Two-factor on the destination. Filename the Monday note with the zone. That is enough process for a personal domain.
FAQ
- What is the safest way to handle personal domain catch all?
- Prefer named aliases and HOLD. If you enable FORWARD on paid, audit junk weekly and set an expiry. Exclusive MX so the firehose is at least only one hop. Never FORWARD to “see what people send.” That is how personal inboxes die.
- Does this require a new mailbox?
- No. MailerZ is not IMAP. Keep Gmail or Outlook unless you need a suite for other reasons.
- Will it work with Gmail or Outlook?
- Yes as destinations. Self-send is not proof. Use a third mailbox and open original.
- What DNS records are involved?
- Exclusive MX, verification TXT, one SPF if you send-as. Leftover MX is a hard stop. Dashboard values only for sending.
- What should I test before production?
- A uniquely titled probe from an unrelated provider to each public alias. Confirm Header From and hop history.
Key takeaways
- Named aliases first.
- HOLD is the personal default.
- FORWARD needs a written reason.
- Fake local-part should not arrive.
- Exclusive MX.
- Review held mail on a schedule.
- Disable leaks. Do not FORWARD them.
- Free holds unknown.
Conclusion
You probably do not need catch-all on a personal domain. You need a short list of names you will stand behind. HOLD keeps guesses out of the Gmail you actually read. Named aliases keep the strings you printed searchable and killable. Exclusive MX keeps leftover host catch-all from undoing the policy. A fake local-part probe proves the policy after every change.
Start free, hold the guesses, and create aliases only when a string becomes real. Pay Solo when you need more names, not when you want a firehose. Confirm pricing. Sign in if the domain is already there.