Twenty role addresses with three real inboxes means twenty named aliases and three Gmail or Outlook stores, not twenty seats. Free allows three aliases. Solo allows fifteen. Twenty printed names need Starter at $8 or $80 (50 aliases) or a higher card. Catch-all is not a list of twenty. Exclusive MX. Probe every name. Paid send-as if those roles must reply as themselves.
Quick answer for role addresses few inboxes
A role address is a local-part customers already use: sales, jobs, press, billing, legal, support, partners, security. It is not a mailbox product. IETF RFC 5321 — Simple Mail Transfer Protocol delivers to your MX. MailerZ maps the name to a destination you already read. Three humans can own three stores. Twenty names can land in those three. That is how you run 20 role addresses with 3 real inboxes.
Confirm MailerZ pricing. Free: 1 domain, 3 aliases, 14-day store, hold unknown, no send-as. Solo: $40 per year, 1 domain, 15 aliases, 90-day store, 100 outgoing, 5 send-as per hour, unknown forwarded. Starter: $8 or $80, 5 domains, 50 aliases, 200 outgoing, 10 per hour. Business: $19 or $190, 25 domains, 200 aliases. Agency: $39 or $390, 100 domains, 500 aliases. Twenty names on one domain fit Starter. They do not fit Free or Solo.
Related: alias naming, support sales billing without extra Gmail, aliases and catch-all, catch-all vs spam. This page is the fan-in math.
Do not buy twenty Google Workspace — product overview seats to print twenty From lines. Buy a suite when those three people need Calendar, Drive, and lockable IMAP. MailerZ is not that suite.
The user problem and the decision criteria
Founders think each printed address is a user. They quote Workspace times twenty. The job was invoices, jobs, and press landing where three people already live. Role addresses few inboxes is a routing design. Seats are a collaboration design. Mixing them is how payroll grows and inboxes stay empty.
| Question | If yes | If no |
|---|---|---|
| Are all twenty names already printed? | Count them. Buy enough aliases. | Do not create twenty “just in case.” |
| Do three people already read mail all day? | Fan in to those three stores. | You may be shopping for seats, not aliases. |
| Must each role send as itself? | Paid send-as. Named From only. | Inbound-only is enough for some roles. |
| Is catch-all tempting? | Audit first. It is not twenty names. | Safer. Create the printed set. |
| Is leftover MX still up? | Stop. Fan-in will split. | Continue the maps. |
| Is this Free or Solo? | You cannot fit twenty names. | Starter or higher. |
Plus addressing on Gmail is not twenty domain roles. hello+jobs@gmail.com is a destination trick. jobs@yourdomain is the public name. Do not confuse them on the website footer.
Technical mail flow for fan-in
One MX set. Twenty RCPT TO values. Each named alias forwards to one of three destinations. Envelope SRS. Header From stays the customer. The store sees twenty identities in From and one IMAP login. Filters and labels do the rest. Email forwarding.
Send-as is a second conversation. The human whose client has paid SMTP attached can offer a named From. The other two cannot invent From in Gmail without the pair. Train who replies to sales@ versus who only reads it. MailerZ does not log into Gmail and rewrite the composer.
Unknown names on Starter may forward if you enabled that path. That is not a substitute for creating the twenty you printed. Guessed local-parts will flood the three stores. Audit before you forward unknown. Catch-all audit.
Recovery 90 days on paid helps when hop two fails. It is not twenty archives. MailerZ is not IMAP.
How to group twenty names onto three stores
Example only. Your footer wins. Store A (founder): hello, billing, invoices, legal, security, privacy, officers. Store B (ops): support, jobs, careers, partners, vendors, status. Store C (growth): sales, press, media, community, events, sponsors. That is twenty if you count carefully. Write the real twenty from invoices, app stores, WHOIS, and social bios. Naming strategy already exists. Do not invent a parallel taxonomy here.
Do not map every name to all three people unless you accept triple noise. Fan-in to one owner with a backup human who has Gmail delegation or a shared label. MailerZ can map one alias to multiple destinations when you choose that; it is a volume decision. Start with one destination per name. Add a second only when a role is truly shared.
Legal and security often need a quieter store than sales. Putting press and legal in the same Gmail is how a reporter thread buries a subpoena. The “three” in this title is a constraint, not a dare to dump everything on the founder.
Step-by-step: twenty names, three stores
Export the printed list
Footer, Stripe, calendars, job boards. Those strings must exist as rows.
Pick a card that fits the count
Twenty > 15. Starter or higher. Confirm pricing.
Create named aliases and map destinations
Three verified Gmail or Outlook addresses. Not catch-all as the list.
Exclusive MX, leftovers gone
One operator. Leftover MX.
Probe all twenty
Unique subjects. Third mailbox. Confirm the right store and Header From.
Attach send-as only for roles that reply
Dashboard pair. Named From. Not every name needs outbound on day one.
Filters in Gmail: one filter per role or a header match on To. That is destination work. MailerZ already delivered.
When someone leaves, reassign the destination on those aliases. Do not delete twenty MX records. There is only one MX set. A later article covers employee exit. Do not invent a disable-all here.
Failure modes
Free or Solo alias cap. Proof: you cannot create name 16 or 20. Fix: Starter. Do not use catch-all to fake the rest.
Leftover MX. Proof: some roles arrive, some sit on Google. Fix: exclusive MX.
One name never created. Proof: hold or 550. Fix: create it. The other nineteen working do not prove the twentieth.
All twenty into one inbox by accident. Proof: destination field identical. Fix: remap. Fan-in is a design, not a default dump.
Replies as @gmail.com. Proof: received From. Fix: paid SMTP on the people who reply. Free cannot.
Catch-all flood. Proof: guessed local-parts. Fix: hold or audit. Twenty names does not mean accept everything.
Self-send. Proof: Gmail short-circuit. Fix: third mailbox per name, or at least per destination group.
Shared secret SMTP in Slack. Proof: 535 after a rotation. Fix: vault rows per client. Seats operate the dashboard; they are not extra SMTP users unless issued that way.
Suite purchase to “get twenty users.” Proof: calendar empty, invoices still missing. Fix: you bought the wrong object.
MailerZ workflow and the product boundary
Verify domain, create named aliases, exclusive MX, probe. Not Workspace, not IMAP, not webmail, not an open relay, not SOC 2. Security. Docs. Unauthorized From 550.
Header From intact on inbound. Envelope SRS only. Seats are operators. Three inboxes are Gmail accounts you map, not three MailerZ mailboxes.
Store 90 days on paid. Failed hops, not twenty archives.
Compare a suite if every human needs Drive: Workspace. Compare routing vendors if you are leaving them: ImprovMX.
Cost versus twenty seats
Starter at $8 or $80 holds 50 aliases. That is the usual card for twenty roles on a few domains. Business and Agency if you have many domains. Solo at $40 per year is the wrong card for twenty names. Free is a three-name proof. Confirm pricing. Annual Starter, Business, and Agency include two months free versus monthly.
Twenty Workspace seats are a different product and a different invoice. Buy them if those twenty people exist. They do not exist in this title. Three people exist.
Time: a spreadsheet of twenty probes is cheaper than a week of “jobs@ is down” when jobs@ was never created.
Send-as ceilings: Starter 10/hour, 200/month. Twenty roles do not each get a blast quota. Operational replies only. Not lists.
Field notes
Put the twenty names and the three destinations in the same note as the MX screenshot. The next hire will otherwise create a twenty-first “info” and miss leftover MX.
Press@ and sales@ in the same inbox need labels the week you cut, not the week a reporter thread buries a deal. Fan-in without filters is how people demand a fourth Gmail.
If a role is a legal obligation, keep delivery evidence in hop history and the destination store. MailerZ is not a seven-year archive. Say that before counsel asks.
Do not print roles you will not staff. Twenty empty names train the internet to guess. Create what you will answer.
Agencies: twenty roles per client domain still need that client’s Starter-or-higher alias cap. Agency 500 aliases is a fleet ceiling, not a reason to skip the printed list.
When you add name 21, check the plan cap first. Do not enable catch-all because you are tired of the form.
If two of the three humans never open Gmail, you do not have three inboxes. You have one inbox and two unused destinations. Remap or replace the humans. Fan-in to a store nobody reads is how legal@ dies quietly.
Night-shift support should not create alias 21 from a phone without the printed list. The next morning you will have typos and a leftover “infoo.” The map is a file. The dashboard is the copy of the file.
Send-as hourly caps apply to the domain, not per role. Ten sales replies and ten billing replies in one hour on Starter can 550. Stagger or upgrade. Do not treat twenty roles as twenty quotas.
International job boards will keep mailing careers@ after you remap to jobs@. Keep both names for a quarter or publish a redirect sentence on the board. The alias is cheap. The missed candidate is not.
Twenty names, three dests, no shared passwords
How to run 20 role addresses with 3 real inboxes is named aliases mapped onto three company-owned dests — not twenty Workspace seats and not plus tags. Group roles by who will staff them. Sales and partnerships to dest A. Support and billing to dest B. Hello, careers, and vendors to dest C. Print the map. Exclusive MailerZ MX. Delete leftovers. Probe every public role from another mailbox. Self-send lies.
Free has three named aliases. Twenty roles need Starter or higher. Solo has fifteen. Starter has fifty. Confirm /pricing. Catch-all is not the other seventeen. Hold unknowns. Promote leftovers from the store when a real person used them. Fan-out of one role into two dests trains two spam buttons. Prefer one dest per role unless you will staff both.
People leave. Change dest, not the public string, unless the string leaked. Disable a leaked role. Keep exclusive MX and neighbor roles. Rotate SMTP if that From could send. Free cannot finish send-as. Paid send-as uses identities you created. Copy the pair. Do not share one SMTP secret across three dests’ WordPress plugins. Unauthorized send is 550.
Envelope SRS only. Header From stays so dests see who wrote support@. Dest must not forward back to the public alias. That loop looks like a spike. MailerZ is not IMAP. Plus addressing on Gmail is not a custom-domain role. We will not strip plus tags on your domain.
A twenty-role homepage and a three-alias card
A shop printed twenty roles on Free. Seventeen hit hold. They thought MailerZ was down. They upgraded to Starter, named the real roles, left harvest names held, probed the twenty they printed. History matched the map. Related: features, aliases and catch-all, send and reply. Not SOC 2. Not HIPAA.
Map sign-off
Twenty strings, three dests named, card fits, MX exclusive, leftovers gone, each role probed, send-as only where paid. If a dest is a personal Gmail, remap before vacation. Start free to prove three roles first. Sign in if the zone already lives here. That is how to run 20 role addresses with 3 real inboxes.
Quarterly reprint the map after HR changes. Offboard rotates SMTP and dests. Do not enable catch-all to cover a role you forgot to name.
Dest labels versus public strings
The public internet sees twenty strings. The dest sees labels or filters you create. Do not print the dest Gmail. Do not share dest passwords to “cover” a role. Change dest when staff changes. Probe the role the same day. Unique subject. Other mailbox. If two roles share a dest, both threads land together — staff must search. That is cheaper than twenty seats. Confirm /pricing for twenty named aliases. Starter or Business, not Free.
Loops: dest rule “forward domain mail back to support@.” Disable it. Hold unknowns. Related: aliases and catch-all, features, send and reply. Envelope SRS only. Header From stays.
Close
Map printed, card fits, MX exclusive, twenty probes, three dests company-owned, catch-all off. Start free with three roles first. Sign in if the zone already lives here. That is how to run 20 role addresses with 3 real inboxes.
If a role leaked, disable that string only. Do not delete the domain. Rotate SMTP if it could send. Not SOC 2. Not HIPAA.
Send-as per role without twenty secrets
You can have twenty inbound roles and three dests, and still only two or three SMTP identities if only hello@ and billing@ send. Do not mint twenty From identities you will not staff. Free cannot finish send-as. Confirm /pricing. Copy pairs only for roles that send. Shared dest does not require shared SMTP. Related: send and reply, features, aliases and catch-all.
Probe inbound all twenty. Probe outbound only the sending roles. Unique subjects. Other mailbox. Start free with three roles. Sign in if the zone already lives here. That is how to run 20 role addresses with 3 real inboxes without twenty secrets.
Vacation week
Before vacation, remap any dest that is a personal Gmail to a company inbox. Probe those roles the same day. Unique subjects. Other mailbox. Do not enable catch-all because someone is out. Hold. Confirm /pricing if you add a named backup role. That is how to run 20 role addresses with 3 real inboxes through a week off.
Homepage versus footer drift
If the homepage lists twenty roles and the footer still lists a personal Gmail, customers will use both. Update every public string in the same window as the dashboard map. Probe the strings you print, not the strings you wish you printed. Exclusive MX still. Leftovers gone. Confirm /pricing. That extra fact is how to run 20 role addresses with 3 real inboxes without a quiet second inbox on the footer.
Contact-form From fields that still say the personal Gmail are the same drift. Fix the form identity on a paid plan. Free cannot finish send-as. Probe the form to a third mailbox after the footer change. Neighbor role aliases still need their own unique subjects the same day.
FAQ
How do you run 20 role addresses with 3 real inboxes?
Create twenty named aliases and map them onto three Gmail or Outlook destinations. Do not buy twenty seats. Free has three aliases. Solo has fifteen. Twenty names need Starter (50 aliases) or higher. Exclusive MX. Probe every name. Catch-all is not twenty names.
Does this require a new mailbox?
No. The three stores are inboxes you already read. MailerZ is not IMAP. Role addresses are routes, not Workspace users.
Will it work with Gmail or Outlook?
Yes as destinations. Filters and labels sort the fan-in. Paid send-as lets the person who replies use the named From. Free has no send-as. Self-send is a bad test.
What DNS records are involved?
One exclusive MailerZ MX set for the domain, verification TXT, leftover host MX deleted. You do not publish twenty MX records. SPF, DKIM, and DMARC matter if those roles send.
What should I test before production?
Unique inbound to all twenty names from a mailbox you do not own. Confirm the right one of the three stores. Confirm Header From. If send-as matters, upgrade and prove each From you will print.
Key takeaways
- Twenty roles are twenty named aliases, not twenty seats.
- Free has 3 aliases. Solo has 15. Twenty needs Starter or higher.
- Three real inboxes are three Gmail or Outlook destinations.
- Catch-all is not the list of twenty.
- One exclusive MX set. Not twenty MX records.
- Probe every printed name.
- Send-as is optional per role and needs a paid pair.
- Free has no send-as.
- Do not dump every role on one founder by accident.
- Leftover MX splits the fan-in.
- MailerZ is not IMAP, not a suite, not SOC 2.
- Workspace seats are for people who exist.
Conclusion and next action
You run twenty role addresses with three inboxes when the printed names exist as aliases and the destinations are the three stores people already open. The plan must fit the count. Catch-all is not a shortcut.
Next action: write the twenty strings, pick Starter or higher, map three destinations, exclusive MX, leftover delete, unique probe per name. Attach SMTP only for roles that reply. Do not buy twenty seats.
Keep the map next to the MX screenshot. The next role should be a row, not a mailbox purchase.
Ready to map roles instead of buying seats
Start free with three names, then upgrade for twenty.
Free proves inbound. Starter fits twenty aliases. Sign in if the domain is there.
Review quarterly, or sooner if plan alias caps change. Author: MailerZ editorial, Secuno LLC.