Email alias explained: several addresses, one inbox

An alias gives the company tidy, role-shaped addresses without multiplying inboxes: the customer sees a department, the team sees one queue.

A company wants the tidy addresses: info@ for the front door, sales@ for the commercial side, a short address for the founder. The common assumption is that every address needs its own mailbox, so the inboxes multiply, and soon somebody owns a password to a box that gets opened twice a year. The confusion sits in a small word: an alias is not a second mailbox. It is a second name for the same mailbox, and the difference changes how a company's mail behaves.

An alias is one real mailbox receiving mail sent to several addresses. Mail to info@ and mail to sales@ and mail to the founder's short address all land in one place, and the customer sees a department while the team sees a single queue. That is what separates an alias from its two neighbors. A second mailbox is another box to log into, another password, another place to check and forget. Forwarding is mail sent onward to a personal address, which works until replies start leaving from that personal identity, and the customer finds themselves corresponding with a person's private account while believing they are writing to the company.

The failures are quiet and expensive. The address created as a full second mailbox, checked once a quarter, with customer mail sleeping inside it, some of it urgent, some of it a quotation request that aged out. The alias pointing at one person who then left the company: the alias survives, the person does not, and mail pools in a departed employee's box that nobody has the credentials to open. Both failures come from the same root: the address was attached to a container or a person instead of to a role.

The slowest failure is the least visible: address decay. The company that was five people created ten aliases in its first year, and nobody has inventoried them since; some point to people who moved on, some answer mail for campaigns that ended, and one or two probably point nowhere at all. Nothing breaks loudly. The domain simply answers on more doors than the company knows it has, and each forgotten door is a place where a customer's message can go in and never come out.

The practice has four habits. Aliases for roles and campaigns, so the address describes a function rather than a person. Real mailboxes, shared or single, where conversation history must live, because an alias cannot hold a history; it only delivers to where one does. An inventory of every address the domain answers on, reviewed when people join and when they leave. And aliases owned by roles rather than persons, so offboarding is a reroute that takes minutes, not an archaeology of who was really receiving sales@ this year.

We run our own mail this way, and the inventory habit reached us through a missed message, not through a manual. Guidance, not guarantees: what your provider calls an alias, and how many addresses one mailbox may receive, lives in the provider's documentation, and the details differ between them. But the structure holds everywhere: the customer sees a department, the team sees one queue, and the list of doors your domain answers on belongs to the company, written down somewhere, not to whoever set them up and later left.