Blog

What is a distribution list

A distribution list delivers one message to many inboxes and keeps nothing in the middle. Where the mail goes, and why it suits an announcement but not support.

Send one message to a distribution list and it arrives in the personal inbox of every member. The list itself holds nothing, because there is no mailbox behind the address, so nothing collects in one place and a colleague’s reply does not show up anywhere you can look.

That shape is right for an announcement and wrong for an address a customer expects an answer from.

What a distribution list is

An address with a membership list and no mailbox of its own. Microsoft’s Exchange Online documentation describes it as a group that can be used only to distribute messages, with a member list you manage, as Create and manage distribution lists in Exchange Online describes.

The address is the whole object. There is no Inbox to open, no Sent folder and no queue. A list moves a message from one sender to many recipients, then stops.

A normal list holds the names you add; a dynamic distribution group recalculates its members each time a message is sent, from rules about department or location, as Compare types of groups in Microsoft 365 describes.

Delivery controls who may send to the list, and Exchange Online accepts mail only from inside your organization by default. Membership controls who may join or leave.

Where the mail goes

A copy of the message lands in every member’s own inbox, next to their personal mail. Each person can file, filter, forward or delete their copy without changing anyone else’s.

Nothing is kept at the address. Delete your copy and the message still sits in the other five inboxes, because there is no list copy behind it and no archive to search.

That is what teams miss when they point a customer address at a list. Finding out what the team told a customer in March means searching private inboxes you may not have access to.

What happens when someone replies

A member who presses Reply answers the person who sent the message. Reply all goes to everyone on the original message, which usually includes the list address, so every member gets a copy.

By default that reply leaves from the member’s own address; an admin can grant a delegate Send As or Send on Behalf for the list instead, as the same Exchange Online documentation sets out.

Either way the reply is not stored at the list, so the address keeps no copy of its own.

That is where a customer address gets awkward. Two members can answer the same question at once, because neither can see that the other has started, and nobody can tell from the address whether it was answered at all.

A distribution list, a group, an alias and a shared mailbox

Term What it is Where a message lands
Distribution list An address with a member list and no mailbox A copy in each member’s own inbox
Group A wider term. A Microsoft 365 group has a group email plus a shared workspace The group’s shared space, and the inbox of members who follow it
Alias A second address on a mailbox that already exists The mailbox that owns the alias
Shared mailbox One mailbox with its own address that several people open and send from The shared mailbox, where everyone with access can read it

A group is not one thing. A Microsoft 365 group gives its members a group email and a shared workspace for files and calendar events, while a shared mailbox is one mailbox several people open. An alias is a second name for a mailbox that already exists: mail sent to a proxy address is delivered to that mailbox’s primary address, per Add or remove email addresses for a mailbox in Exchange Online.

For the choice between two of those rows, shared mailbox vs distribution list works through the decision in full.

Why a distribution list suits an announcement

An announcement has one job: get the same information to a set of people, with no reply expected. Microsoft recommends distribution groups for broadcasting information to a set group of people.

Release notes, a change to the on-call rota, a maintenance window, a build alert. None of them needs a record of who replied, because no reply is part of the job, and each reader handles the message in their own inbox on their own time.

The test is whether the message ends with the people who receive it. If it does, a list is the right shape. If someone has to be named as the person handling it, the list is the wrong tool.

Why a distribution list fails a support address

A support address asks four things: replies come from the company, several people can answer, the team can see what has already been said, and one person owns each message.

A list provides none of them. The reply comes from an individual, the history sits in private inboxes, and there is no way to claim a message, so nothing prevents two people writing the same answer.

The usual first fix is a shared mailbox: one address, one Inbox, one Sent folder, and permissions that decide who can open it. That solves the record. It does not solve the queue, because a mailbox cannot show that someone has started a reply. Shared inbox vs help desk covers the next boundary, between ownership and a ticket system.

A list can still have a job beside a support address: teams route a copy of every new message to a list so everyone sees what came in, while the shared mailbox handles the answers.

Chirp and the shared support address

Chirp is a shared inbox for small software teams that track their work in Linear. It connects to your mailbox, which stays the record, and puts the queue in front of the team.

Press i in a thread to link it to a Linear issue, create one, or find the issue that already exists. When every linked issue is Done or Canceled, the thread comes back with a reply drafted for you that names the issue.

Every common action has a key: j and k to move, e to archive, and s, a, t and b to snooze, assign, tag and block. Each inbox carries its own access list, and the roles are Admin, Agent and Viewer. Chirp costs $9 per user per month.

FAQ

What is a distribution list in simple terms?

One email address that delivers a copy of every message to each person on it. Nobody shares a mailbox, and the address itself stores nothing.

Does a distribution list have a mailbox?

No. There is no Inbox, no Sent folder and no history for the list. Each member’s mailbox holds the copy they received.

Can you send email from a distribution list?

By default a member replies from their own address. An admin can grant a delegate Send As or Send on Behalf, so the reply appears to come from the list.

What is the difference between an email group and a distribution list?

Group is the broader word. A Microsoft 365 group includes a shared workspace for files and calendar events, while a distribution list only moves messages to its members.

How do I create a distribution list?

In Exchange Online, open the Exchange admin center, then Recipients, Groups and Distribution list. Add members, then set who may send to it.

Next step

Announcements are the easy case for a list. The hard case starts when the address belongs to customers, and what a shared inbox is covers what has to sit in front of the mailbox before four people can answer one address without colliding.