Mailbox, alias or forwarding address: what does your business need?

Business email hosting

The short answer

A mailbox stores messages and supports sending and receiving through an account. An alias is an additional address routed to an existing destination, usually without independent storage or login. Forwarding passes incoming mail to another address and does not by itself establish sending from the original address. Choose based on who needs access, where history belongs and how replies must appear. Specific alias, forwarding and shared-inbox features depend on the service and must be confirmed.

Several addresses can look identical on a business card while behaving very differently behind the scenes. Start with the conversation you need to manage, then choose the address arrangement.

Compare storage, access and replies separately

General differences between common email arrangements
ArrangementWhere mail livesWhat to verify
MailboxIn the hosted account's message store.Storage, access, sending settings and responsibility.
AliasAt the destination configured for the extra address.Allowed destinations and whether sending as the alias is supported.
ForwardingAt the receiving destination; source-copy behavior varies.Delivery, copy retention, reply identity and error handling.

Services use these labels differently. The SMTP specification describes alias expansion as replacing one recipient address with its configured destinations. Ask how the selected service implements that routing and which access and sending options accompany it.

Choose a mailbox when the history needs its own home

A mailbox is useful when one person or function needs a distinct message history, sending identity and storage allowance. For example, an owner may want work correspondence separate from personal mail. A dedicated enquiry mailbox may also be appropriate when conversations should remain attached to a business role.

However, a role-named address does not automatically make the account a multi-user shared inbox. If several people need access, describe their tasks: reading, replying, seeing sent messages, assigning work and removing access when responsibilities change. Check what the selected service supports. Do not solve team access by assuming everyone should share one password.

Consider an alias when another name reaches the same destination

An alias can be useful when a person handles more than one public address but wants conversations in one place. For instance, hello@yourbusiness.example and enquiries@yourbusiness.example might be intended for the same responsible person. Whether that routing is available, and how it is configured, depends on the service.

An alias does not normally provide its own storage, independent login or separate access policy. It also does not automatically allow replies from that address. Check the sending behavior in webmail and each app you plan to use. If future staff changes require a separate history, a convenient alias today may not match that longer-term requirement.

Treat forwarding as a route, not a complete mailbox setup

Forwarding may help direct incoming messages to an inbox already monitored. It does not, by itself, configure authenticated outgoing mail from the original business address. Without a suitable sending arrangement, replies may expose a different address or fail checks.

Also verify whether the original service keeps a copy and what happens if the destination rejects mail or becomes full. A forwarding chain can hide where a failure occurs. IETF guidance describes authentication issues in indirect mail flows, including forwarding. Test the actual route rather than relying on a direct-delivery test. Avoid circular rules in which two addresses forward messages back to each other.

Illustrative example: three public addresses, two different needs

In this illustrative example, a business wants owner@, enquiries@ and billing@ on its domain. The owner handles general questions, while billing conversations need to remain in a separate history.

  1. Write the responsible person and desired history for each address.
  2. Ask whether enquiries can route to the owner's destination under the selected service.
  3. Keep billing's independent-history requirement explicit when discussing mailbox options.
  4. If more than one person handles billing, assess supported team access separately.
  5. Test the sender shown on replies from every public address.

The number of addresses is not enough to determine mailbox count. Storage, access and reply requirements determine the setup.

Plan for absence and staff changes before publishing an address

Ask what happens when the responsible person is away or leaves. Can the business retain the necessary history? Who changes the destination? Which accounts and devices should lose access? Keep the authorized administrator and recovery process documented.

A shared inbox is a separate category of requirement: several people may need coordinated access and visibility into replies. A distribution arrangement instead may give several people their own copies, which does not inherently prevent duplicate responses. Describe the task in ordinary language before selecting a feature name. For a small team, a clear responsibility rule may solve the problem without adding another tool.

Discuss the address arrangement with us

Our business email hosting provides real mailboxes from $5 per mailbox per month with 5 GB each, webmail and compatible email apps. It is optional alongside a website or other business services. If you need aliases, forwarding or coordinated team access, include those requirements so we can confirm the right setup.

Tell us the addresses you want, who should use them, whether replies need a particular identity and where existing mail lives. We can check the appropriate arrangement before setup. That is more useful than choosing by address count alone. You can keep your website in place while discussing email, and existing-message transfer is considered separately from address routing.

A few follow-up questions

Can an alias have its own password?

An alias generally routes to another destination rather than creating an independent account. If you need separate login and access control, describe that as a mailbox requirement and confirm the service's terminology.

Does forwarding preserve a separate business sent folder?

Not by itself. Forwarding handles incoming routing. Where outgoing messages are stored depends on the account and app used to send them, so check the actual reply arrangement.

Can you help us choose how several addresses should work?

Tell us who needs access, whether histories should be separate and how replies should appear. We can check the supported mailbox and routing arrangements before agreeing the setup.

Sources and further reading

Choose addresses around the work

List the addresses you want, who answers them, where history should live and how replies should appear. We can check a suitable business email arrangement.

Discuss your mailbox needs See what our business email hosting service includes
Website by TelosOps