Mailbox or Forwarder: Which Do You Need? Print

The question worth getting right

When you set up an email address on your domain, you have two ways to handle it, a mailbox or a forwarder, and choosing the right one saves you clutter, confusion, and the occasional lost message. They sound similar and are often confused, but they do genuinely different jobs. This article makes the choice obvious.

The plain difference

• A mailbox is a real email account. It stores mail on the server, you log in to it, and you can both receive and send from the address. It has its own password and its own storage space. This is a full email address in every sense.
• A forwarder stores nothing and cannot send. It simply passes mail arriving at one address on to another address, as our article on setting up forwarders describes. It has no login, no password, and no storage of its own.

So the real question is two smaller questions: does this address need to store its own mail, and does it need to send mail? If yes to either, you want a mailbox. If it only needs to receive and pass mail on to somewhere you already check, a forwarder is enough.

When a mailbox is the right choice

• The address needs to send mail. If you reply, send, or start conversations from this address, you need a mailbox, a forwarder cannot send, which is the single most common reason people end up needing one.
• The address belongs to a person who wants their own separate inbox, their own login, and their own mail kept apart from everyone else's.
• You want the mail stored on the server, accessible from several devices and from webmail, and kept as a record.
• It is a primary working address, the one you live in day to day.

When a forwarder is the right choice

• You only need mail to reach you somewhere you already check. A forwarder sends it straight to your existing inbox, no extra account to log into.
• Role or department addresses like info@, sales@, or accounts@ that you want landing in a mailbox you already have, rather than as separate inboxes to check.
• You want to keep things tidy and free, forwarders cost no storage and add no inbox to manage.
• You need one address to reach several people, which a forwarder does by sending to multiple destinations at once.

The common trap: needing to reply as the address

Here is where people most often choose wrong. You set up sales@ as a forwarder into your personal inbox, which works beautifully for receiving. Then a customer emails sales@, you reply, and your reply goes out from your personal address, because a forwarder cannot send. The customer now has your personal address and sees the mismatch.

If an address ever needs to reply as itself, that is a mailbox, not a forwarder. This one point resolves most mailbox-versus-forwarder mistakes: receiving-only can be a forwarder, but sending-or-replying means a mailbox.

You can have both patterns at once

The best setups often mix the two. A typical small business has a real mailbox or two for the people who send mail, with a handful of role addresses forwarding into them. So you might have a mailbox for yourself, and info@, sales@, and support@ all forwarding to it, real accounts where sending matters, forwarders where it does not. You are not choosing one approach for your whole domain, you are choosing per address, based on what each one needs to do.

Good to know

A helpful rule of thumb: start with a forwarder, because it is free, simple, and adds nothing to manage, and upgrade an address to a full mailbox only when you find it genuinely needs to send or store its own mail. That way you never run more inboxes than you actually use, which keeps your email tidy and your storage clear. Setting up either takes a minute, our articles on forwarders and on managing email accounts in cPanel cover both, and converting from one to the other later is easy, so this is not a decision you can get badly wrong, only one worth understanding.