Why Email Address Limits Aren’t Comparable Across Providers

Ask three email admins how many addresses a mailbox can have and you will get three answers that sound like they describe the same thing: 10, 30, 400. They are not the same thing. Gmail’s 10 counts verified outbound identities you can send from, Google Workspace’s 30 counts user aliases on a business mailbox, and Microsoft 365’s 400 counts proxy addresses attached to a single mailbox object. Comparing those numbers directly is like comparing the number of doors on a house to the number of keys on a ring. The limits measure different objects, so any “which provider gives you more addresses” comparison has to start by matching the object type first.

What each provider is actually counting when it quotes a limit

Gmail’s well-known number is about send mail as addresses. A free Gmail account can verify and send from up to 99 other addresses, but the number that matters for most people is the limit on changing the gmail.com address itself: Google caps that at three changes. The 10 figure that circulates in comparisons usually refers to verified sending identities in tighter configurations or to the practical alias count on a consumer account. The point is that what you are counting is outbound identities, not inboxes. Each one has to be verified, and each one routes replies back to whichever address you designate.

Google Workspace changes the object entirely. A business mailbox allows up to 30 aliases per user, and those aliases are inbound addresses that land in the same inbox. Groups are a separate object with no comparable cap, which is why a Workspace admin can effectively hand out hundreds of addresses by creating groups rather than aliases. Microsoft 365 documents a proxy address limit of roughly 300 to 400 per mailbox depending on the service and configuration, and Exchange Online is enabled by default to accept plus addressing, so a single mailbox can generate an unbounded number of plus-tagged variants on top of its proxy addresses. Same mailbox, different counters.

Then there is the catch-all domain, which accepts mail for every address on the domain whether or not a mailbox exists for it. That is the only genuinely unlimited option in the sense most people mean when they ask for unlimited email addresses. It does not create mailboxes; it routes everything into one. Providers do not advertise it as a limit because it is not a limit at all. It is a routing rule with a blast radius.

Why plus addressing confuses the comparison further

Plus addressing delivers mail to the base Gmail address no matter what tag follows the plus sign, and the same pattern works in Exchange Online by default. So a user with one mailbox and one alias can register for a hundred websites using name+site1@, name+site2@, and so on, and every message lands in the same inbox. None of those plus tags count against any provider’s alias limit because they are not aliases. They are tags on the local part of an existing address. If you count plus tags as addresses, gmail unlimited email addresses becomes the result, and the comparison collapses.

This is where most “how many email addresses does X allow” articles go wrong. They mix plus tags, aliases, proxy addresses, and send-as identities into one bucket and then rank providers by the biggest number they found. The honest approach is to define the object you need. If you need separate outbound identities for a support desk, you are counting send mail as slots. If you need separate inbound addresses that all land in one inbox for an email registration strategy, you are counting aliases or proxy addresses. If you need an address per website with no setup at all, plus addressing or a catch-all domain is the tool.

How to compare providers without fooling yourself

Start with the object type, not the number. Write down what the address has to do: receive only, send and receive, route to a different person, or hide the real mailbox from a vendor. Only then look at the provider’s documented limit for that object. Gmail’s send mail as cap answers a different question than Google Workspace’s Workspace alias limit of 30, and neither tells you anything about Microsoft’s proxy address ceiling. Microsoft’s number is generous precisely because proxy addresses are cheap routing labels, not identities you can send from independently in every case.

Watch for the objects that are uncapped. Groups in Google Workspace, distribution lists in Exchange Online, and forwarding rules all multiply addresses without touching the published per-user limits. A catch-all mailbox is the extreme version of this: one mailbox, infinite addresses, zero per-address management. AllMail publishes the unlimited email addresses guide that walks through these distinctions, and the core lesson is that the only genuinely unlimited option is the catch-all domain, with everything else being a finite allowance on a specific object. The domain email hosting layer is what determines whether a catch-all is even available to you, so check that before you plan around it.

A practical test for any provider comparison: ask whether the address can receive mail, whether it can send mail as itself, and whether it survives a mailbox migration. Aliases and proxy addresses usually survive; plus tags and catch-all routes often do not. A role address like billing@ or support@ is another object again, usually a group or shared mailbox, and its limits follow group rules rather than user rules. Once you separate these into receive-only, send-as, and routing labels, the numbers stop competing and start describing what each provider is actually good at.

Pick the object your workflow needs, then read the provider’s documentation for that object specifically. If you need outbound identities, count send-as slots and verify each one. If you need inbound addresses that all land in one inbox, aliases or proxy addresses will do, and a catch-all domain covers the long tail without per-address setup. If you just want to know which site leaked your address, plus addressing costs nothing and needs no configuration. Match the object first, and the limits finally mean something.

Author: zeusyash

LindaFam