Catch-All Email for Personal Domains: A Practical Setup

Quick answer for catch all personal domain email

Start with the strings you will actually give people: me@, hello@, maybe a shop@ you use at checkouts. Create those aliases. Free allows three. Solo allows fifteen at $40 per year if you also need send-as. Starter is $8 or $80. Business is $19 or $190. Agency is $39 or $390. Unlimited is $99/month or $990/year. Confirm MailerZ pricing. Unknown recipients are held on Free. Paid FORWARD is optional. Product language lives on aliases and catch-all.

A personal domain is not a privacy mask. Shops and banks will still see your public name. Write-ups on addy.io’s blog discuss rotating aliases that hide a personal inbox. That is a different product. lastname.com is an identity you intend to keep. Catch-all FORWARD on that identity trains Gmail on every guess the internet tries.

Transport still follows IETF RFC 5321 — Simple Mail Transfer Protocol. Senders look up MX, offer a local-part, and transfer content. MailerZ accepts a named alias and forwards to your inbox. Envelope SRS may rewrite the return path. Header From, Subject, Date, Message-ID, body, and MIME stay as received. Leftovers follow HOLD or paid FORWARD. Leftover registrar MX still steals mail before either policy runs.

Google’s people-first guidance is about pages, not SMTP; see creating helpful, reliable, people-first content. A personal catch-all guide that only says “turn it on so you never miss a typo” is how shopping spam becomes the inbox.

Send-as is separate. Free has no send-as. If replies must leave as me@lastname, upgrade after inbound works. Catch-all leftovers never become From identities. Creating shop@ as a named alias is how a checkout address can later send. Enabling FORWARD is not how it sends.

The user problem and the decision criteria

People buy lastname.com because they want one durable name. Then they enable catch-all so they never create aliases. Convenience feels like owning the whole local-part space. The cost is dictionary first names, old partner guesses, and scraper lists landing in the same Gmail that holds the bank mail. A practical setup names the few strings you print and holds the rest.

Shopping aliases are named routes, not catch-all. If you want shop-amazon@, create it—or use a privacy tool if hiding is the job. Catch-all FORWARD of amazon@, paypal@, and every brand guess is how a personal domain becomes a promo folder. Name the two or three checkout addresses you will actually type.

Family members on the same lastname.com need their own aliases: alex@, sam@. Mapping both to one Gmail is a shared pile. Mapping each to their own Gmail is a routing rule. Catch-all FORWARD to dad’s inbox is how the kids’ leftover mail becomes your problem. Do not use leftovers as family IT.

Plus addressing on Gmail is not a personal-domain alias. you+store@gmail.com is a filter tag. Forms reject plus signs. me@lastname is ordinary SMTP. Do not skip domain aliases because plus tags felt cheaper. They fail the first form that validates email strictly.

Old registrar “email included” is leftover MX waiting to happen. If the registrar still publishes MX next to MailerZ, some aunt will reach the old webmail you forgot. Delete those records. Catch-all on MailerZ cannot recover the half that never arrived. History for the half that did lives on delivery and recovery.

Technical mail flow

A sending server looks up MX, connects, offers MAIL FROM, names a recipient, and transfers content. MailerZ accepts a verified domain. A matching alias forwards to the destination you verified. An unknown local-part is held on Free. Paid plans hold it unless you enabled catch-all FORWARD. Envelope SRS may rewrite the return path. Header From stays the author.

HOLD is the practical personal default. You can open a leftover in recovery for 14 days on Free or 90 days on paid. That store is hop evidence, not a second Gmail and not legal hold. If the leftover is a real person who used an old nickname, create that nickname as an alias. If it is a scraper, leave it held.

FOREVER FORWARD is how catch all personal domain email becomes a spam cannon. Directory guesses of your first name, middle initial, and role-like strings (admin@, office@) all arrive. Destination filters then get jumpy about the named aliases you actually use. Turn FORWARD off after a cutover week. Promote the leftovers that were real.

SPF, DKIM, and DMARC evaluate authorization. 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) are the documents. They do not decide leftover policy. They do not move mail into Primary. Publish them when you send as a named address.

Outbound SMTP is paid and named. Unauthorized or unhosted recipients get 550 / 550 5.7.1. MailerZ is not an open relay. Free cannot finish this hop. A personal domain that only receives can stay on Free forever. That is a valid setup.

Self-send from Gmail to the same Gmail account can short-circuit. Budget an external mailbox for me@ and for a made-up local-part. The second probe is how you confirm HOLD versus FORWARD without guessing.

Campaign mail is out of scope. Solo’s 100 outgoing and 5 send-as per hour are stop signs if you later send. Dictionary inbound is not a reason to raise those caps.

Simulate a personal alias versus an unknown string in the Email Routing Lab before you cut production MX. The lab is teaching, not a live zone.

Leftover MX is a hard stop. Old Google, Microsoft, or registrar records beside MailerZ MX split inbound. Some birthday invites reach the old host. Some reach Gmail. It looks random. Read the public set from two resolvers.

Operator seats do not matter on a one-person domain. Free and Solo have one seat. Do not buy Starter to “get catch-all.” Catch-all FORWARD is a paid policy bit, not a seat. Alias count is the card that grows if you invent twelve shopping names.

Wedding and RSVP addresses are named aliases with an expiry. Create rsvp@ for a season. Map it to your inbox. After the event, disable or leave it mapped if vendors still write. Do not leave catch-all FORWARD on because one vendor might invent party@ later. Create party@ if they do. HOLD will show you.

Job-search mail is another named route. Create jobs@ or yourname@ and give that to recruiters. Catch-all FORWARD will also collect hr@ and careers@ guesses from scrapers. Those guesses are not opportunities. They are load. Name the one string you put on the résumé.

Git commits and public profiles leak first.last@ guesses. If you published that string, create it. If you did not, HOLD is how you see whether it is worth promoting. Forever FORWARD turns every GitHub scrape into inbox mail next to the electric bill.

Newsletter signups should use a named alias you can burn, or a privacy tool. lastname.com catch-all is a poor burner. You will still own the domain in ten years. The leftover policy will still be there. Name news@ if you must, then disable it when the list goes bad.

Kids’ school portals often reject plus tags and demand a “real” looking address. A named parent@ or firstname@ on the family domain is the practical object. Catch-all FORWARD is how every teacher typo plus every scraped first name arrives. Create the school name. Hold the rest.

Travel bookings should use a named trip@ or your durable me@. Airlines send changes for years. A leftover you never created will not help when the flight moves if HOLD expired on Free after fourteen days. Create the name you give the airline. Do not rely on leftovers as a travel archive.

Step-by-step setup and decision path

1. Write the three names you will print

   Example: me@, hello@, shop@. If you cannot name three, you do not need catch-all. You need those names. Free allows three aliases. Do not start FORWARD because the fourth name is undecided.

2. Add the domain and map those aliases to your inbox

   Verify TXT. Do not loop. Use the Gmail or Outlook account you already read. Do not create a new mailbox “for the domain” unless you want hosting.

3. Publish one MX set and delete leftover host mail

   Copy the dashboard MX. Read the public set from two resolvers. Remove registrar “included email” MX. Catch-all cannot unify two owners.

4. Prove each printed name from another mailbox

   Unique subject, Header From intact, delivery history present. If history is empty, MX or the alias is wrong. If history says 250 and Gmail is empty, check spam. No inbox SLA.

5. Probe a made-up local-part

   Confirm HOLD on Free. On paid, confirm HOLD unless you enabled FORWARD for a dated window. Open recovery only if you need the body.

6. Promote real leftovers; keep FORWARD short

   If an old nickname appears in HOLD, create it. Then turn FORWARD off. Confirm pricing if you upgraded only for the window.

Failure modes and proof

Proof is a header block plus a MailerZ event. Do not send SMTP passwords. Do not publish verification tokens. A catch all personal domain email setup that cannot show HOLD for one made-up local-part is still a guess.

Bank recovery addresses should be named aliases you control, not leftovers. If the bank stored me@, keep me@. If it stored a typo, create the typo, then change the bank. Do not leave FORWARD on forever “in case a bank used something weird.”

Dating apps and throwaway signups are a poor fit for a lastname.com catch-all. Use a privacy tool or a dedicated cheap alias you can burn. Do not train the family domain on that traffic.

MailerZ workflow and product boundary

MailerZ is a custom-domain delivery layer operated by Secuno LLC. Point MX at MailerZ. Personal-domain aliases land in Gmail or Outlook. Unknowns are held on Free. Paid plans add optional FORWARD and SMTP. Site: mailerz.net. App: mail.mailerz.net.

• Free $0: 1 domain, 3 aliases, 14-day store, send-as disabled, SMTP and API disabled.
• Solo $40/yr: 1 domain, 15 aliases, 90-day, 100 outgoing, 5 send-as/hr.
• Starter $8/$80: 5 / 50 / 5 seats, 200 outgoing, 10/hr.
• Business $19/$190: 25 / 200 / 25, 400 outgoing, 15/hr.
• Agency $39/$390: 100 / 500 / 50, 800 outgoing, 25/hr.

MailerZ is not IMAP, not a suite, not an open relay, not an inbox SLA, not SOC 2 / ISO 27001 / HIPAA. Controls: Security and Trust Center. Unauthorized send returns 550 / 550 5.7.1. Annual Starter, Business, and Agency include two months free versus monthly. Solo has no monthly option. Dashboard seats are operators, not Gmail logins. A personal domain almost never needs Agency.

Cost, alternatives, and trade-offs

The cheap-looking choice is catch-all FORWARD so you never create aliases. The expensive choice is a personal Gmail trained on harvested names. Free is enough for three printed names and HOLD. Solo is $40 per year if me@ must send. Do not prepay Business for a lastname.com vanity.

Registrar cost sits next to the forwarder. A .com or .family renewal is often tens of dollars. Quote your registrar. That line does not change when you switch HOLD to FORWARD.

Time is a line item. Naming three aliases costs less than a month of leftover mail. Leftover MX costs more than Solo. Budget one external unknown-recipient probe as part of cutover.

Monthly versus yearly is cash flow. Solo is $40 per year only. Do not buy Agency because a privacy blog used a large integer. Alias count is the card that matches shopping-name sprawl. Catch-all is a policy bit.

If you want IMAP clients on lastname.com, a host is the honest product. A forwarder will look incomplete because it is incomplete for that job. If you already live in Gmail, keep Gmail.

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 SMTP passwords or verification tokens to support. The artifacts that close a catch all personal domain email argument are the three printed names, HOLD versus FORWARD, exclusive public MX, and one made-up-local-part probe.

Two-factor on the destination Gmail is the control that protects the pile. Catch-all policy does not replace 2FA. If leftovers ever FORWARD, they land in that same protected inbox—or they land in an unprotected one. Fix the inbox first.

Quote vendors the day you buy. This page can drift. Registrars change included-email MX. MailerZ limits can change. The tests do not: named prints, exclusive MX, inbound probe, HOLD for leftovers, short FORWARD only when you can watch it.

Moving countries or ISPs does not change leftover policy. MX still has one owner. Gmail still has one pile. If you change destination inboxes, remap the named aliases. Do not enable FORWARD “until I remember every old nickname.” Read HOLD for a week. Promote what is real. That is the practical personal-domain move.

Inheritance and death-of-inbox planning is grim and useful. A named me@ with a documented destination is something an executor can remap. A forever catch-all with no list of printed names is a pile nobody can explain. Write the three names down next to the domain registrar login.

Side-project domains are not personal lastname.com, but the same rule applies if you parked a hobby zone on the same MailerZ account later. Each zone needs its own printed names. Copying FORWARD from the family domain onto a hobby shop domain is how you inherit leftover spam twice. Free is one domain. Solo is three domains. Starter starts at five if you actually have five zones.

Phone auto-complete will invent local-parts from old threads. Those strings are leftovers unless you created them. HOLD shows the miss. FORWARD delivers it and trains Gmail that the miss is you. If a friend keeps using an old nickname, create that one alias. Do not keep the hose open for one friend.

Public WHOIS privacy does not replace leftover policy. Hiding the registrant email is a registrar setting. Catch-all FORWARD still accepts guesses at the domain. Those are different doors. Close leftover MX. Name what you print. Hold the rest.

Calendar invites from schools and clubs often go to whatever address they first stored. If that address was a leftover you never created, HOLD on Free may expire before you notice. Create the stored string. Then ask them to update if you want a cleaner name. Practical personal-domain email is boring: name the string the other party already has.

Open-source maintainers who print a domain on a repo should create that exact local-part. Security reports sent to a guessed security@ will sit in HOLD unless you created it. If you want security@, create it and map it. Catch-all FORWARD is a noisy way to run a disclosure address.

Photo-sharing and printer apps love to invent accounts from whatever address is on the phone. If the phone offers a leftover, HOLD will show the welcome mail. Create that leftover only if you want the account. Otherwise leave it held and fix the phone’s default to me@. Practical setup is half DNS and half teaching your own devices which name to use.

Two personal domains—one for the family, one for a pen name—need two MX owners and two alias lists. Do not dual-publish. Do not copy FORWARD across both because it felt consistent. Consistency is named prints and HOLD, not leftover hoses.

Holiday card lists and reunion mailers still use whatever address they typed a decade ago. HOLD for a month around those events if you expect old nicknames. Promote the ones that show up. Then return to named prints. That is a watched window with a calendar, not a reason to live on FORWARD until next December.

If you only remember one test, remember two messages: one to me@ from another provider, one to a nonsense local-part. The first must reach Gmail with Header From intact. The second must sit in HOLD unless you dated a FORWARD window. When those two proofs exist, catch all personal domain email is set up. Everything else is naming and leftover MX.

FAQ

Key takeaways

• Catch all personal domain email is leftover policy, not ownership of every string.
• Print three names. Free allows 3. Hold the rest.
• Paid FORWARD is a cutover window, not a forever default.
• A personal domain is not a privacy mask. Use a mask product if hiding is the job.
• Leftover registrar MX is a hard stop.
• Catch-all does not create send-as. Free has no send-as.
• Envelope SRS only. Header From untouched. Not an inbox SLA.
• Probe printed names and one made-up local-part from another mailbox.

Conclusion and next action

A personal domain stays readable when you name what you print and hold the rest. Catch-all FORWARD is how leftover guesses share a folder with the bank. Keep Gmail. Create the aliases. Delete leftover MX. Watch HOLD. MailerZ Free fits that sequence. Solo is there when me@ must send. It does not become a mask service or file Primary.

Review quarterly, or sooner if MailerZ leftover policy or registrar included-email MX changes. Author: MailerZ editorial, Secuno LLC.