Will Your Alias Strategy Scale? A Provider Checklist

Most alias strategies fail for reasons that have nothing to do with the alias itself. Teams pick a naming convention, hand out addresses, and six months later discover that half the aliases cannot reply from the right address, the other half broke during a domain move, and every mailbox is quietly burning through a shared sending cap. The fix is not a better convention. It is a provider checklist applied before you standardize anything. Three checks predict whether an alias plan scales: can the alias send outbound, does it survive a domain migration, and does it share the primary account’s quota? Run every provider through those three gates and the rest of the decisions get much easier.

Check one: outbound sending from the alias address

The most common myth in email identity management is that an alias is an alias is an alias. It is not. Receiving mail at an alias is nearly universal. Sending mail from that alias is a per-provider feature with per-provider limits, and the difference between the two is where most strategies quietly break. Gmail plus aliases, for example, deliver mail to the same inbox as the primary address, but outbound behavior depends on whether you have configured the address under Send mail as in Gmail settings. Without that step, replies go out from your primary address and your carefully planned identity collapses on first contact.

Gmail’s Send mail as feature supports up to 99 addresses per account, which sounds generous until you do the math on a shared team mailbox. Each send-as address also requires verification: Google sends a confirmation message, and for third-party domains you must supply SMTP credentials, typically through smtp.gmail.com with an app password or a Workspace SMTP relay. That verification email is a real operational step, not a formality. If the alias address cannot receive mail, you cannot complete verification, and you cannot send. Aliases that only forward inbound traffic are dead ends for outbound identity.

There is a deadline worth putting on the calendar. Gmail will discontinue Send as for third-party addresses starting January 2027, which means any strategy that relies on routing non-Google domains through a personal Gmail account needs a migration plan well before then. Google Workspace is the intended landing spot: it allows 30 aliases per user, and those aliases can send natively without SMTP workarounds. If your checklist item is “can this alias send outbound,” the honest answer for many personal-account setups is “yes, for now, with caveats.”

What to verify before you commit to a provider

Ask three concrete questions of any provider you are evaluating. First, does outbound sending work natively from the alias, or does it require a send-as configuration with SMTP credentials? Second, is there a documented cap on send-as addresses, and does it match your team size? Third, is the feature stable, or has the vendor announced changes? Google documents alias limits on its help pages, and reading those pages takes ten minutes versus the weeks you would spend untangling a broken reply chain. The same discipline applies to Yahoo and Outlook, which handle alias sending differently enough that a strategy copied from Gmail will not port cleanly.

Check two: survival across a domain migration

The second myth is that aliases are permanent. They are permanent only as long as the domain underneath them is. Changing your gmail.com address is allowed once every 12 months, which is a useful escape hatch but not a strategy. A second Gmail address means a second Google account, which provides a separate inbox, separate storage, and separate settings. That is sometimes exactly what you want and sometimes the worst possible outcome, because it splits your mail history and your filters across two places with no shared search.

Domain migration is the sharper test. If you move from a personal domain to a Workspace domain, or from one registrar to another, aliases defined at the domain level either follow you or they do not. Catch-all email configurations are especially fragile: a catch-all on the old domain does not automatically exist on the new one, and forwarded mail can break silently when DNS records change. Aliases defined inside a Google account, by contrast, travel with the account as long as the account itself is not renamed or deleted, a point explained further at https://allmail.one/blog/gmail-email-alias/. The distinction matters because it determines where you should define your aliases in the first place.

Plus aliases and dot aliases are the safest category here, because they require no domain configuration at all. Gmail treats john.smith@gmail.com and johnsmith@gmail.com as the same mailbox, and john.smith+newsletters@gmail.com routes to the same inbox as well. Gmail filters can be created on plus alias addresses, so a filter matching “to:john.smith+receipts@gmail.com” will sort those messages automatically. The catch is that dot aliases are a Gmail-specific quirk. Most other providers treat dots as significant characters, so a naming scheme built on dots will not survive a move to Yahoo or Outlook. Plus aliases are more portable, though not universally supported.

Check three: quota sharing and the hidden cost of one mailbox

The third myth is that aliases are free. They are free in the sense that you do not pay per address, but they are not free in the sense that they consume shared resources. Plus aliases deliver mail to the same inbox, which means they share the same 15 GB storage pool on a personal Google account, the same sending limits, and the same spam reputation. One alias that gets signed up for a high-volume mailing list can fill the quota that your primary address depends on. One alias that leaks to a spammer can drag down deliverability for every identity attached to that account.

Google Workspace changes the arithmetic without changing the principle. Aliases on a Workspace user still share that user’s mailbox and quota, so a 30-alias account is really one mailbox with 30 front doors. A second Google account, by contrast, provides a separate inbox and a separate quota, which is the right answer when you genuinely need isolation and the wrong answer when you just want a tidier address. The checklist question is simple: if this alias receives a flood of mail, does it damage the primary identity? If yes, the alias belongs on a separate account or a separate mailbox, not bolted onto your main one.

Quota sharing also affects sending. Gmail’s daily sending limits apply per account, not per alias, so a team that spreads ten identities across one mailbox is still constrained by one ceiling. That is fine for low-volume correspondence and disastrous for anything resembling transactional or marketing mail. If outbound volume matters, count the aliases against the account limit before you assign them, not after a message bounces back with a rate-limit notice.

Scale, in the end, is less about how many aliases you can create and more about whether each one behaves like a real address. Run the three checks before you standardize: confirm outbound sending works and understand the send-as cap, confirm the alias survives a domain move or define it somewhere that does, and confirm the alias shares quota with the primary account in a way you can live with. AllMail publishes Gmail alias guides that walk through the settings side of this, including the Accounts and Import panel where Send mail as lives, and they are worth reading before you hand out addresses to a team. The providers that pass all three checks are the ones your strategy can grow on. The ones that fail one are the ones that will cost you a migration later.