Blog

Shared mailbox vs distribution list

One forwards, one stores. Which to use for support@, billing@ and announcements, and why neither tracks who is answering.

A distribution list forwards one address to a group of people. A shared mailbox is a single mailbox that several people open and send from.

If a customer writes to the address and expects an answer, use a shared mailbox. If you are announcing something and do not want a reply, use a distribution list.

What a distribution list is

An address with members. Mail sent to it is delivered to every member’s own inbox. The list itself has no mailbox, so there is nothing to open and nothing kept in one place.

That is the whole design, and it is a good one for its purpose. A list is a fan-out mechanism.

What a shared mailbox is

One mailbox with its own address. Several people are granted access to it, so they all see the same Inbox, the same Sent folder and the same history. Replies can go out from the shared address rather than the individual’s.

The mailbox is the record. If you want to know what the team told a customer in March, there is one place to look.

The differences that matter

Distribution list Shared mailbox
Has its own mailbox No Yes
Where mail is kept Each member’s inbox The mailbox
Can send as the address Usually not Yes, with permission
Can you see a colleague’s reply No Yes
Access control List membership Mailbox permissions
Assignment and status No No
Fits a customer address Poorly Well

Two rows decide most cases. A distribution list cannot send as the address, so replies come from whoever answered, and it keeps no record, so nobody can see what a colleague already said.

When a distribution list is the right call

  • Announcements and internal notices where no reply is expected.
  • Alerts and notifications from a system.
  • A group you want people to receive in their own inbox because they will act on it personally.

The signal is that nobody needs to know what the others did with the message.

When a shared mailbox is the right call

  • support@, billing@, sales@, security@. Any address a customer writes to.
  • Anything where “what did we tell them” needs an answer later.
  • Anything where the reply should come from the company address rather than a person’s.

The signal is that the message needs an owner and a history.

Where both fall short for support

A shared mailbox solves the record. It does not solve the queue.

Open a shared mailbox with four people covering it and you get the failure everyone recognises: two people reply to the same message because neither can see that the other has started, and a message that nobody replies to because each of them assumed someone else had it.

That is not a configuration problem. A mailbox has no concept of a thread being claimed, so there is nothing to show who is on it.

Three things fix it, in rough order of effort:

  • A rule, written down. “Check the mailbox twice a day, reply to everything unread, mark it read when you are handling it.” This works until the volume makes it unreliable, and it depends on everyone being disciplined.
  • A saved view per person. Each person filters to their own assigned mail. This needs assignment to exist first.
  • A shared inbox in front of the mailbox. The mailbox stays the record, and the tool adds ownership, status and a view of who is on what.

Chirp is the third option: it connects to the mailbox, keeps the record where it is, and adds assignment, single-key triage and per-inbox access on top.

Setting each one up

A distribution list is minutes of work. Create the group, add members, decide whether people outside the organisation can post. There is nothing to configure on the receiving side.

A shared mailbox takes longer, because permissions are per person. You create the mailbox, grant access to the people who need to read it, grant send-as or send-on-behalf to the ones who should write from it, and then tell everyone how to add it to their mail client. The access model is the part worth getting right, since billing@ and support@ rarely want the same audience.

A shared inbox adds a third step: connecting the mailbox and agreeing the workflow. That is the step that produces the ownership and history a mailbox on its own does not have.

A worked example

A four-person software team runs support@ and wants to answer one question: who is replying today?

With a distribution list, all four get every message in their own inboxes. Whoever is fastest usually replies, and nobody can see who else already did. Looking up what was sent last month means asking around.

With a shared mailbox, all four see the same Inbox and the same Sent folder. The record problem is solved. The collision problem is not, because the mailbox still cannot show that someone has started a reply.

With a shared inbox in front of the mailbox, all four see the same queue, a thread shows who has it, and replies go out from support@. The mailbox still holds the history.

FAQ

What is the difference between a shared mailbox and a distribution list? A distribution list delivers copies to members’ own inboxes and keeps nothing central. A shared mailbox is one mailbox that several people open, with its own history.

Can you send from a distribution list? Usually not. The address forwards to members, so replies go out from the individual’s own address. A shared mailbox can send as the shared address when the member has permission.

Do distribution lists have a mailbox? No. That is the main practical difference. There is no Inbox or Sent folder for the list itself.

Which is better for a support address? A shared mailbox, and a shared inbox on top of it if more than one person is answering. A distribution list leaves you with no record and no way to tell what a colleague already sent.

Can I use both for the same address? You can, and some teams route a support address to a list for notifications while a shared mailbox handles replies. It usually creates more confusion than it saves.

Next step

If you are setting up the address rather than choosing the type, what a collaborative inbox is covers the four ways teams build one and how each fails. For the reply itself, CC and BCC explains what your team sees when a message arrives as a copy.