How to use catch-all email for typo recovery without accepting everything

Quick answer for catch all email typo recovery

The safest recovery is a second named alias. If people misspell support@yourdomain.com as suport@, create suport and point it at the same destination. SMTP still delivers by MX as IETF RFC 5321 — Simple Mail Transfer Protocol describes. The alias table matches the exact local-part. Nothing else has to be accepted.

Catch-all FORWARD recovers typos you have not listed yet. It also accepts harvested names. That is the trade-off. MailerZ Free holds unknowns instead of forwarding them. Paid plans can enable FORWARD. Use FORWARD for a week when you cannot guess the misspellings, copy the real strings into named aliases, then turn FORWARD off.

Do not use Gmail plus tags as public typo recovery. Plus addressing is a destination-provider feature, not a domain policy. Google documents it for Gmail accounts in Google Gmail Help — Using an address alias (plus addressing). Forms and vendors drop the plus. MailerZ does not strip plus tags on custom domains. If you need support+vip@, create that string as its own alias.

Prove three paths from another mailbox: printed name arrives, typo alias arrives, invented name stays held. If leftover MX still points at Google or an old host, both the printed name and the typo will look random. Delete leftover MX before you add recovery rows. See aliases and catch-all routing for the product split between named rows and unknown policy.

The real decision behind typo recovery

Operators search this topic after a lost invoice or a missed sales reply. The customer swears they emailed the domain. History is empty. The founder enables catch-all and calls it fixed. A week later the destination is a spam folder with no owner. The original typo is still unnamed.

Separate three problems. A repeated misspelling of a printed role is a named alias. A forgotten printed string from an old PDF is a migration inventory. A desire to never think about local-parts again is accepting everything. Only the first problem belongs in this article. The second belongs in the migrate-catch-all guide. The third is a policy you should refuse.

Decision criteria stay boring on purpose. Can you write the misspelling? Add it. Can you not write it, but you know mail is dying on one public page? Run a short paid FORWARD audit and promote what appears. Is the domain new and you control every stamp? Skip FORWARD entirely. Three named aliases on Free cover a one-person company.

When a typo alias is enough

• Support tickets already show the same wrong local-part twice.
• The printed name is on the site, invoices, or a store listing.
• The destination inbox is one the company keeps after a person leaves.
• You can spare one alias slot. Free has three. Solo has fifteen.

When a short FORWARD audit is justified

• You inherited a domain that used catch-all for years and nobody kept a list.
• A campaign used a QR code or a spoken address that people hear wrong.
• You can assign a human to review unknowns daily for seven days.
• You will turn FORWARD off after the real strings are named.

When neither list fits, keep hold. Lost mail that was never printed is not a typo. It is a sender guessing. Guessing should fail or sit in history, not land next to billing.

Agencies managing client domains see this weekly. The client says “just catch-all it.” The safer script is: name the footer addresses, add the two misspellings from last month’s tickets, hold everything else, review history on Friday. That script scales. Permanent FORWARD does not, because nobody staffs an infinite local-part.

Security-minded teams worry that a typo alias teaches attackers the real name. The real name is already public. The typo is already being typed. Naming it does not publish a new role. Accepting every string does. Hold plus one extra row is the smaller surface.

Technical mail flow for typo recovery

Delivery does not “fuzzy match” local-parts. The sending server looks up MX, connects, and issues RCPT TO for the exact address the human typed. Your system either has that local-part or it does not. Catch-all is only the default after a miss. A typo alias is an exact hit. Prefer the exact hit.

What the forwarder rewrites

MailerZ rewrites envelope MAIL FROM with SRS so the hop does not fail SPF at Gmail or Outlook. Header From, Subject, Date, Message-ID, body, and MIME stay as the sender wrote them. That is true for a named typo and for paid FORWARD. Destination spam filters still score the original sender. Inbox placement is not an SLA.

SPF, DKIM, and DMARC remain outbound problems. Typo recovery does not sign mail. If you reply as support@, that is paid send-as from an approved identity. Free has no send-as. Do not enable catch-all hoping replies will show the domain. Inbound recovery and outbound identity are different switches. Specs: IETF RFC 7208 — Sender Policy Framework (SPF), IETF RFC 6376 — DomainKeys Identified Mail (DKIM), IETF RFC 7489 — Domain-based Message Authentication, Reporting, and Conformance (DMARC).

Hold versus FORWARD versus 550

Hold keeps the hop without delivering it to a human inbox. Free uses hold for unknowns. You can see the attempted local-part in history. The window is 14 days on Free and 90 on paid. That store is hop recovery, not a finance archive.

FORWARD delivers the unknown to the catch-all destination. Use it when you are hunting unnamed typos and can sort the queue. Turn it off when the hunt ends. Leaving it on trains you to ignore the inbox.

A 550 unknown-user tells honest senders the address does not exist. MailerZ also returns 550 / 550 5.7.1 for unhosted or unauthorized recipients because it is not an open relay. Catch-all FORWARD still applies only to a verified domain you control.

Plus tags are not typo recovery

support+urgent@gmail.com is a subaddress on Gmail’s store. IETF RFC 5233 — Sieve Email Filtering: Subaddress Extension describes Sieve subaddressing. Your custom domain does not inherit that behavior unless you create the full local-part. Customers who type suport@yourdomain.com never include a plus. Do not design recovery around plus tags.

Case folding is a separate trap. SMTP local-parts can be case-sensitive in the protocol and case-insensitive in practice. Treat Support@ and support@ as the same operational name. Do not create duplicate rows for case. Create rows for real misspellings: missing letters, swapped vowels, plural forms, and old product names.

Step-by-step setup for typo recovery

Work from evidence. If you do not have a misspelling in tickets, logs, or a spoken script, you do not have a typo problem yet. You have a naming problem or an MX problem.

1. Collect the printed name. Copy the exact string from the site, invoice, or store listing. Create that named alias first if it does not exist. Destination must be an inbox the company keeps.
2. Collect the misspelling. Pull it from support tickets, bounce reports, or a sales call recording. Write only strings you have seen twice, or once with money attached.
3. Add the typo as a named alias. Same destination as the printed name. Do not invent a second owner. One queue. Two public strings.
4. Fix MX before more rows. One MX set. Delete leftover Google, Microsoft, or registrar MX. Confirm with two public resolvers. Mixed MX looks like “typos never arrive.”
5. Prove three messages. From an unrelated mailbox: printed name, typo alias, invented local-part. Unique titles. Confirm Header From and history. Self-send inside Gmail can lie.
6. Optional audit week. If you still see lost mail you cannot name, enable paid catch-all FORWARD. Review daily. Promote real strings. Disable FORWARD on day seven.
7. Write the decision. Note which typos you accepted and why FORWARD is off. The next operator will otherwise re-open the dump.

Setup clicks live in docs. Use the email routing lab if you want to walk named versus unknown before you touch production MX.

Alias budget

Free allows three aliases. A typical first set is hello, billing, and the operator. If the typo is on support, you may need to promote a plan or drop a low-value name. Solo allows fifteen aliases for $40/year. That is enough for printed roles plus a handful of misspellings. Do not spend the budget on speculative guesses like infoo@ and infor@ unless you have seen them.

If a spoken brand is routinely heard wrong, add those two or three variants and stop. You will not win every accent. You will win the ones that already appear in the ticket queue.

Worked examples you can copy

A one-person studio prints hello@studio.test on the site and billing@studio.test on invoices. Customers type hallo@ after a phone call. Add hallo as a named alias to the same inbox as hello. Do not enable FORWARD. Free still has one alias slot left for a later role. Invented names stay held. That is typo recovery without accepting everything.

A five-person shop prints support@shop.test on the help center. Tickets show suport@ and supports@. Add both. Destination is the shared operations Gmail, not a contractor account. If Free is full, Solo’s fifteen aliases cover the printed roles plus those two misspellings. Still no FORWARD.

An agency inherits client.test that used host catch-all for six years. Nobody has a list. After MX cutover, named aliases cover the footer. Lost mail continues. Enable paid FORWARD for seven days. Each morning, copy local-parts that are real people or real invoices into named aliases. Ignore dictionary hits. On day seven, disable FORWARD. Keep the promoted rows. That audit is the only time “catch-all” should stay on.

A founder wants info@, contact@, team@, and every guess “just in case.” Refuse. Print one public name. Map it. Add evidenced typos only. Extra public names create extra misspellings. The recovery table grows because the printed surface grew, not because catch-all was wise.

Spoken brands need a short variant list, then a stop rule. If the company is called “Kite”, people type hello@kite correctly and sometimes hello@kyte on the wrong domain entirely. A typo alias on your domain cannot fix a wrong domain. Recover local-part errors on the domain you host. Domain-level typos are a DNS and trademark problem, not catch-all.

QR codes and conference badges are high-typo surfaces. If the badge prints a short local-part, add the two misreads you hear at the booth that afternoon. Do not leave FORWARD on after the event. Event spam arrives for months. Named rows from the booth stay useful. The open door does not.

Failure modes and proof

Typo recovery fails in predictable ways. Most of them are not “catch-all is off.”

Delivery recovery shows held and failed hops. Use it to read the local-part the sender actually used. Guessing misspellings from memory wastes alias slots. Copy the string from history, promote it, and leave the rest held.

Destination junk folders hide successful recovery. The typo arrived. Gmail scored the sender. Check spam before you add more aliases. Header From is still the original sender, so filters behave like a direct send to the destination, not like a rewritten newsletter.

Loops happen when the typo destination is another alias on the same domain. Destinations must be external mailboxes. Do not point suport@ at support@ if support@ is only an alias with no mailbox behind it unless the chain ends in Gmail or Outlook.

Leftover MX remains a hard stop. If Workspace still publishes MX, some senders never hit your typo row. Enabling FORWARD does not merge MX. Delete the leftover records. Recheck from two resolvers, not only the registrar UI.

MailerZ workflow and product boundary

Secuno LLC operates MailerZ. Site: mailerz.net. App: mail.mailerz.net. Typo recovery is named aliases plus an optional unknown policy. It is not a mailbox product and not fuzzy matching.

What MailerZ does

• Accept exact named aliases on verified domains, including misspellings you add.
• Hold unknown local-parts on Free.
• Optionally FORWARD unknowns on paid plans for a deliberate audit.
• Preserve Header From. Envelope SRS only.
• Keep hop history 14 days on Free, 90 on paid.
• Refuse open relay with SMTP 550 for unhosted or unauthorized recipients.

What MailerZ does not do

• Auto-generate typo variants or fuzzy local-parts.
• Strip plus tags on your custom domain.
• Rewrite Header From or MIME.
• Offer catch-all FORWARD or send-as on Free.
• Host IMAP, Calendar, or a shared mailbox for the typo.
• Promise inbox placement, uptime SLAs, review counts, SOC 2, ISO 27001, or HIPAA. Controls: Security and Trust Center.

Capacity is on pricing. Free: $0, one domain, three aliases, one seat, 14-day store, send-as disabled, SMTP and API disabled. Solo: $40/year, 15 aliases, 90-day store, 1,000 outgoing/month, 5 send-as/hour. Starter: $8 or $80, five domains, 50 aliases, five seats, 2,000 outgoing, 10/hour. Business: $19 or $190, 25 / 200 / 25, 4,000 outgoing, 15/hour. Agency: $39 or $390, 100 / 500 / 50, 8,000 outgoing, 25/hour. Annual Starter, Business, and Agency include two months free versus monthly. Solo is yearly only. Limits are capacity, not an inbox SLA.

Seats are dashboard operators. They do not create extra typo inboxes. If two people must edit routes, you need seats. If two people only read Gmail, one destination is enough. Forwarding model: email forwarding.

Cost, alternatives, and trade-offs

A typo alias costs one row. Permanent catch-all costs attention every day. A suite seat costs a monthly user for a name nobody logs into. Pick the smallest tool that recovers the mail you can name.

Google’s suite overview: Google Workspace — product overview. Buy it when you need Calendar and a hosted mailbox. Do not buy it to recover suport@. Do not score either path with invented reviews.

Best practice: print fewer names, map them, add only evidenced misspellings, hold the rest, audit with FORWARD only when the list is unknowable. That is catch all email typo recovery without accepting everything.

“Accepting everything” has a concrete shape. The destination inbox shows local-parts you never printed: first names of strangers, product codes from scrapers, role words you do not staff, and random strings. A human cannot own that queue. Filters hide the one real typo inside the noise. The feature that was meant to recover a sale now hides the sale. Hold plus named rows keeps the real typo visible because the inbox only contains names you chose.

Time cost matters more than plan price. Ten minutes to add suport@ is cheaper than an hour a week sorting FORWARD. Solo at $40/year is cheaper than a Workspace seat bought only to host a catch-all mailbox. Agency at $39/month is for many domains and many named rows, not for one lazy toggle. Confirm current cards on pricing before you quote a customer. Do not invent discounts or inbox guarantees.

If legal or finance requires every historical recipient to remain deliverable, you are in migration territory, not typo territory. Inventory the old prints, promote them to named aliases, then decide whether a temporary FORWARD window is still required. Do not leave permanent FORWARD in place as a substitute for that inventory. The migrate article in this cluster covers cutover order. This page stays on recovering a misspelling without opening the domain.

FAQ

Key takeaways

• Typo recovery is an exact extra alias, not fuzzy matching.
• Add misspellings you have seen. Do not invent a dictionary.
• Free holds unknowns. That is the safe default.
• Paid FORWARD is a timed audit, then it goes off.
• Plus tags are not domain typo recovery.
• Leftover MX wastes every recovery row you add.
• Prove printed, typo, and invented-held from another mailbox.
• Header From stays original. Envelope SRS is the allowed rewrite.
• Held hops last 14 days on Free and 90 on paid.
• MailerZ is not IMAP, not a suite, and not SOC 2.

Conclusion and next action

If you came here for catch all email typo recovery, name the misspelling and keep the dump closed. Accepting everything recovers the typo and a thousand guesses. A second alias recovers the typo and leaves ownership intact.

MailerZ fits that order: named rows, Free hold, optional paid FORWARD for a week you actually staff. It does not auto-correct local-parts, host a mailbox, or promise inbox placement. Start on Free if three names plus hold are enough. Pay when you need more alias slots, a 90-day hop window, or a short FORWARD audit.

Next action: copy the misspelling from a real ticket, add it next to the printed name, and send three unique tests from another mailbox. Register path is one domain.

Review quarterly, or sooner if hold windows or catch-all defaults change. Author: MailerZ editorial, Secuno LLC.