Personal email alias use cases are simple: one owned-domain string per shop, airline, or bill, landing in the Gmail you already search. When that vendor leaks, you disable that string. You do not disable lastname.com. HOLD unknown local-parts so guesses do not train the inbox. Exclusive MX so leftover registrar mail does not steal receipts. Free has ten aliases. Count before you print a wardrobe of names.
Quick answer for personal email alias use cases
Own a domain. Map shop-store@, fly-airline@, bills-power@ into one Gmail. HOLD the rest. Exclusive MailerZ MX. Product path: email forwarding, aliases and catch-all, use cases. Plus-addressing is in IETF RFC 5233 — Sieve Email Filtering: Subaddress Extension and Google Gmail Help — Using an address alias (plus addressing). MX is in IETF RFC 5321 — Simple Mail Transfer Protocol.
Confirm MailerZ pricing. Free is one domain, ten aliases, 14-day store, send-as disabled, SMTP and API disabled. Solo is $40 per year when you need more names or send-as. Starter is $8 or $80. Business is $19 or $190. Agency is $39 or $390. No inbox SLA. Not a mask network. Not SOC 2.
A Reddit thread about cheap forwarding is research, not proof; see the self-hosted discussion if you want the mood, and prefer RFCs for physics. Helpful content: Google’s people-first guidance.
The user problem and the decision criteria
People want receipts without giving every checkout their forever address. Plus tags help until a site rejects the plus. Disposable providers help until the site blocks the domain. An owned-domain alias is yours after you leave Apple or a mask app. The cost is alias count and MX discipline.
| Question | If yes | If no |
|---|---|---|
| Do you own the domain for years? | Aliases can be durable. | A mask may fit better for one checkout. |
| Is this a bank or government? | Use a durable name you will keep. | A killable shop alias is fine. |
| Will you exceed three names? | Quote Solo or Starter. | Free can prove the hop. |
| Catch-all FORWARD “for convenience”? | Guesses and spam join receipts. | HOLD unknown. |
| Leftover registrar MX? | Receipts split. Delete it. | You can probe the hop. |
Technical mail flow
The shop’s mailer resolves MX and offers the envelope to one owner. MailerZ maps the local-part and forwards into Gmail. Envelope SRS only. Header From stays the shop. If leftover builder MX is still published, some receipts never reach history. You conclude “they never sent the receipt.” They sent it to the old host.
Plus tags (you+shop@gmail) stay inside Gmail’s store. They do not give you a domain you own. Sites that block plus still accept you@yourdomain if MX works. Do not treat plus as leftover MX insurance.
Self-send from Gmail hides leftover MX. Foreign probes are the gate before you type the alias at checkout.
Step-by-step setup and decision path
Pick a domain you will renew
Auto-renew the zone. A lapsed domain turns every alias into someone else’s problem.
Cut exclusive MailerZ MX
Delete leftover registrar, builder, and parking email MX. Query two resolvers.
Name three aliases you will actually use
On Free, that is the whole list. Example: you@, shop-main@, bills@. HOLD the rest.
Foreign probe each name
Unique subject. History 250. Destination search. Then use the string at checkout.
Upgrade when the list grows
Solo or Starter for more aliases or send-as. Do not invent names on Free and wonder why the fourth bounced.
Disable after a leak
Turn off that vendor’s alias. Keep the domain. Update the merchant if you still need the account.
Failure modes and proof
| What you see | Likely cause | Proof |
|---|---|---|
| No receipt, history empty | Leftover MX or missing alias | Second resolver; envelope name |
| 250 empty Gmail | Filter or HOLD typo | Recovery |
| Fourth alias rejected | Free cap | Quote Solo or Starter |
| Spam to random names | Catch-all FORWARD | HOLD unknown |
| Site blocks the domain | They treat custom domains like masks | Use a durable you@ for that vendor |
| 550 when sending as shop@ | Free plan | Paid send-as or send from Gmail |
Proof is exclusive MX, a probed alias, and a receipt in Gmail. Families share a domain carefully: kids do not get catch-all. Agencies do not mix client shop aliases onto a personal zone.
MailerZ workflow and product boundary
MailerZ is inbound MX plus authenticated SMTP. Envelope SRS only. Header From never rewritten. It is not IMAP, not a mask network, not an open relay. Unhosted SMTP is 550 / 550 5.7.1.
HOLD or reject on Free. Ten aliases. 14-day store. Send-as, SMTP, and API disabled. Solo $40 per year. Starter $8 or $80. Business $19 or $190. Agency $39 or $390. Confirm pricing. Limits are not an inbox SLA. No SOC 2.
Features describe routing. They do not hide you from a shop that requires a “real” mailbox. Paid plans buy names and send-as, not anonymity.
Cost, alternatives, and trade-offs
| Choice | What you get | What you give up |
|---|---|---|
| Owned-domain aliases | Durable killable strings | One-tap masks |
| Gmail plus tags only | Zero DNS | Sites that reject plus |
| Hide My Email / masks | Convenience. Quote Apple live | The string if you leave the ecosystem |
| Catch-all FORWARD | Every guess | A quiet Gmail |
| Workspace for one human | A suite. Quote Google live | The Gmail you already search |
Time is a line item. Three well-chosen aliases beat twenty unused ones. Leftover MX costs more than Solo. A Free-plan send-as argument still costs more than the upgrade.
Shopping aliases
Use a pattern you can remember: shop-brand@ or brand.shop@. Write it down. If you cannot remember it at returns, you will give the forever address anyway. One alias per high-spam merchant. One shared shop@ for low-risk stores if you are on Free.
Loyalty programs and receipts belong on the alias, not on you@, if you will kill that merchant. Warranty and bank-linked shops may deserve the durable you@. The job is blast radius, not purity.
Checkout forms that reject “aliases” sometimes reject plus tags and disposable domains, not a real TLD you own. If they still reject you@yourdomain, use the durable name and accept the risk. Do not dual-publish MX to “look more real.”
Refunds and merchant replies must reach the same alias. If you typed shop-a@ and later used shop-b@, you created two maps. Probe both or pick one.
Travel and subscriptions
Airlines and hotels send boarding passes and changes. A travel@ you actually read is better than twenty airline-specific names you will miss at the gate. One travel@ plus one shop@ plus you@ fits Free. More airlines can wait for Solo.
Subscriptions—streaming, newspapers, SaaS—leak often. One alias per high-value bill (bank, power, phone) that you will never kill. One alias per disposable streaming trial. When the trial ends, disable the alias. HOLD will catch their leftover marketing to guessed names.
Calendar invites from travel brands still land in Gmail if the destination is Gmail. MailerZ is not a calendar. Do not buy IMAP for ICS files.
Families: do not give a child catch-all. Named aliases only. Shared household bills@ can map to two parents as destinations. That is one hop, two stores. Write who pays.
Passports and government logins get the durable you@. Do not put a joke local-part on a visa form. Researchers of your shopping habits are shops. Governments are not a “use case” for cute names.
After a leak
If shop-brand@ starts getting spam that is not from that brand, the merchant or a partner leaked. Disable the alias. Update the account if you still shop there. Keep lastname.com. Keep bills@. That is the point of personal email alias use cases.
Do not disable MX because one shop spilled. Do not catch-all FORWARD “to see what else leaks.” HOLD and review. Promote a name only if you will staff it.
Registrar republish after a website save steals receipts. Re-query MX after any panel click. Night operators who add Google MX “as backup” recreate leftover MX.
Send-as is a second job. You rarely need to send as shop-brand@. You need to receive. Free is enough for inbound if three names cover you. Upgrade for more names, not for theater SMTP.
Two-factor on Gmail. HOLD review. Foreign probe after each new alias. Legal hold is an export, not leftover MX. Open a held body for a typo receipt and expect an audit row. Not SOC 2.
IPv6 failures are host problems after exclusive names exist. Do not republish registrar mail. Fix the host. History shows whether we accepted the envelope.
If a second person needs the order, send this page plus leftover MX troubleshooting. Named aliases. HOLD. Exclusive MX. Probe. Kill the leaked string. That order prevents a forever address on every checkout.
Paid plans do not change the physics. Solo, Starter, Business, Agency still need one inbound owner. They buy more names. They do not buy a mask network or an inbox SLA.
The artifacts that close personal email alias use cases are a short written list, exclusive resolvers, probed names, and a kill step you have actually practiced. Everything else is a drawer of unused local-parts. Unused local-parts are how Free caps surprise you in November.
Named aliases on your domain, not a burner inbox
Shopping, travel, and subscription aliases on MailerZ are named local-parts on a domain you own, forwarded to Gmail or Outlook. They are not Temp-Mail. They are not provider masks on a famous shared domain. If a shop leaks shops@yourdomain, you disable that local-part and keep firstname@. The destination inbox does not change. Exclusive MX. HOLD unknowns on Free so random guesses do not land unless you pay for FORWARD and mean it.
Create the names you will give merchants: shops, airlines, news, maybe a travel-year tag if you created that exact string. MailerZ does not claim to strip plus tags on custom domains. founder+amazon@ is not an alias until you create it. Prefer shops@ and rotate when leaked.
Free is ten aliases. A shopping life with twelve merchants wants Solo (15) or Starter (50), or you drop museum names. Do not FORWARD the whole personal domain to “catch every shop.” That is how the personal Gmail becomes a landfill.
Banks and recoveries are not shopping aliases. Keep firstname@ or you@ as the main, proven, exclusive, probed. Move banks last. Shopping names are the ones you can burn. See the surname-as-main article for that bar. This page is the disposable-feeling names that are still yours.
When a merchant leaks, disable that alias. Create a replacement if you still use the merchant. Update the account. Probe the new name. Revoke send-as if that identity could send — most shopping aliases should never send. Free cannot send anyway.
Leftover MX on a personal domain makes some shop mail vanish into Google. Two resolvers. Delete aspmx. Calendar is not an excuse.
Self-send to shops@ is invalid. A friend or a second provider proves the hop. Empty history is leftovers. HOLD is a name you did not create.
Privacy apps (Relay, SimpleLogin, Addy.io) are better when you want a famous mask per site and no brand correlation. Your domain correlates. That can be what you want for travel receipts under a brand, or not. Quote those vendors if masks are the job. Do not leftover-MX them beside MailerZ.
Header From inbound stays the merchant. Envelope SRS. We do not rewrite From so the shop “looks like you.” Detection of a hop is public MX. We do not sell stealth.
Retention 14/90 is hop evidence, not a receipt archive. Gmail is the store. Export if a dispute outlives the window.
A three-alias Free map and when to pay
Free example: you@, shops@, news@. Travel stays on shops@ or you upgrade to Solo and add travel@. HOLD everything else. That is a complete personal hop. Print only those three.
Solo example: add airlines, insurance, civic. Still one domain, 90-day hops, 2,500 outgoing if you ever send, 20/hour. Most personal maps never send. Pay for names and retention, not for From, until you need From.
Travel week: leftover check before you fly. Hotel resolvers lie. Two public lookups. Do not restore Google from a phone.
Subscription cancel: disable the alias after the last receipt you need, or keep it if the vendor still mails tax documents. Disabling a live recovery is how you lock the shop. Sequence: update vendor, then disable.
Family: do not share shops@ with a partner without a written store. Two destinations means fan-out and privacy. Prefer two local-parts.
Agencies: this is a personal pattern. Do not put a client’s customers on shopping aliases on the client brand without a policy. Different job.
No inbox SLA when a shop files mail as promotions. No SOC 2. /security. /pricing.
Start free — one domain — and live on three names until a leak or a fourth print forces Solo. Sign in to disable a leaked alias without changing Gmail.
Monthly: leftover MX, hold list versus what you actually print, disable names you no longer use. The map stays small on purpose.
If you want a new mask per checkout forever, buy a privacy app. If you want three or fifteen names you own, this hop fits. Do not pretend they are the same SKU.
Name the job, then name the local-part
Shopping, travel, and subscriptions fail as alias schemes when every vendor gets a cute random string you cannot remember at a hotel desk. The scheme should encode the job: shops.brand, travel.brand, bills.brand, or vendor-plus-year if you like plus addressing on the destination. The inbound hop still needs a real alias or a paid catch-all policy you chose on purpose. Randomness without a map is how you HOLD a boarding-pass message and miss a flight notification.
A personal brand domain on MailerZ is exclusive MX plus named aliases. Free is ten aliases. That is enough for a tight map: one shopping, one travel, one bills. It is not enough for a unique string per merchant. If you want a unique string per merchant, you either upgrade for more aliases, enable paid FORWARD and accept the noise, or you use a privacy-alias product for merchants and keep the brand hop for humans who must reach you. Two tools, two jobs. One leftover MX is still wrong.
Travel is time-bounded. Create travel@ or air-2026@ before you book. Tell the airline that address. When the trip ends, you can stop reading it, or you can keep it for the airline’s refund cycle. Deleting the alias the day you land is how a delay SMS goes nowhere. HOLD will show you if they used a spelling you did not create. Create the spelling they used, or ask them to resend. Do not restore Google MX because a boarding pass is late.
Shopping leaks. When a merchant sells the list, you want to disable one alias, not your legal name. That is the privacy-class argument. On a brand hop, disabling shop@ also disables every other merchant you stuffed into shop@. Split high-risk merchants onto their own aliases if you have the cap. Stuff low-risk newsletters into one alias you are willing to mute. Muting in Gmail is not the same as deleting the alias. Muting hides. Deleting HOLDs or bounces the next receipt you needed.
Subscriptions are cancellation mail. The alias must live as long as the charge can surprise you. Keep bills@ for as long as cards are on file. When you cancel, keep the alias through the next two billing cycles. HOLD on a closed alias is a gift: you see they still have the address. Creating a new random alias every month without a register is how you lose the unsubscribe link.
Destination mailbox is still Gmail or Outlook. MailerZ is not IMAP. Filters belong on the destination. Prefix the local-part so filters are easy: shop-, travel-, bills-. Do not build a second mailbox culture in Vault. Vault is a store window, fourteen days on Free, ninety on paid. It is break-glass, not your travel inbox.
Send-as from a shopping alias is a paid choice and often a bad one. You do not need to send as shop@ to buy shoes. You need to receive receipts. Free cannot send. If a merchant requires a reply from the same address, reply from the destination or enable paid send-as for that one identity. Do not enable send-as on every burn alias. That is how you authenticate noise.
Self-send to test shop@ will lie the same way it lies for billing@. Use a stranger mailbox. If you only have one phone, use a web Proton. Unique subject. If history is empty, MX is leftover or the name never arrived. If HOLD, create the alias. If destination 5xx, fix Gmail. The personal case does not get a simpler physics.
Family domains need a written map. Partner@ and you@ are humans. shop@ might be shared. Shared destinations create shared leaks. Prefer one human destination per sensitive alias. Agency and family are not the same plan, but the map skill is the same: print the names, create the names, do not catch-all your way out of a conversation.
Start free if ten aliases match your life. Upgrade when the fourth merchant deserves its own name. /pricing for caps. Envelope SRS, Header From intact, no SOC 2, no inbox SLA. Sign in when the domain already receives. The scheme is a list you can read at a hotel desk, not a puzzle you invented in an airport.
If you already mixed leftover aspmx with a personal hop, delete leftovers before you invent more local-parts. New aliases on a split namespace train you to think the scheme failed. The scheme never got a fair hop. Exclusive MX, then the three names, then the stranger probe. Shopping can wait one evening. Leftover MX will not.
FAQ
What is the safest way to handle personal email alias use cases?
Give each shop, airline, or subscription a named alias on a domain you own, landing in the Gmail you already use. HOLD unknown local-parts. Disable the alias after a leak. Exclusive MX. Free has ten aliases—count before you print. Paid send-as only if you must leave as that From.
Does this require a new mailbox?
No. MailerZ is not IMAP. Gmail or Outlook stays the store. Disposable mask services are a different class. Buy hosting only if you want IMAP folders on the domain.
Will it work with Gmail or Outlook?
Inbound works when exclusive MX and the alias exist. Self-send can hide leftover registrar MX. Receipts from shops will not self-send. Free has no send-as.
What DNS records are involved?
One exclusive MailerZ MX set, verification TXT, leftover builder or registrar email MX deleted. SPF, DKIM, and DMARC when you send. Plus tags are not MX. See RFC 5321 and RFC 5233.
What should I test before production?
Two resolvers, a foreign probe to each named alias you will give a merchant, history 250, destination search. Then use that string at checkout. Do not print twenty names on Free.
Key takeaways
- Personal email alias use cases: one owned-domain string per vendor into Gmail.
- HOLD unknowns. Catch-all FORWARD trains spam.
- Kill the leaked alias. Keep the domain.
- Banks get durable names. Shops get killable ones.
- Free is ten aliases. Count before you print.
- Exclusive MX. Leftover registrar mail steals receipts.
- Plus tags are not a domain you own. Masks are another class.
- Solo $40/yr for more names or send-as. Confirm /pricing. Not SOC 2.
Conclusion and next action
If you want shopping, travel, and subscription aliases, own the domain, map a short list into Gmail, HOLD the rest, and practice killing a leaked string. MailerZ can show hops it accepted. It cannot hide you from a shop that demands you@. Start free, prove three names, upgrade when the list is real.
Ready to stop giving every checkout your forever address
Start free with one domain and three named aliases.
Inbound on Free. Solo when the list or send-as grows. Sign in if the domain is already there.
Review when a vendor leaks, and quarterly otherwise. Author: MailerZ editorial, Secuno LLC.