One address that copies every message into every member’s personal inbox.
Distribution list. A distribution list is an email address that forwards every message it receives to each member’s individual mailbox. Unlike a shared mailbox, a distribution list stores nothing itself — every member gets a personal copy, and replies come from the member’s own address, not from the list.
An administrator creates the list — a distribution group in Microsoft 365, a Google Group in Workspace — and adds members. Mail sent to the list address fans out: the server delivers an independent copy to each member’s inbox, and the list itself keeps no archive. Membership changes only affect future mail; a new member sees nothing that arrived before they joined.
The defining mechanic is what happens after delivery: the copies diverge. One member archives their copy, another flags it, a third never opens it — and no copy knows about the others. Worse, replies default to the replier’s personal address, so the moment anyone answers a customer, the customer’s next email goes to that person’s private mailbox and leaves the group entirely. Threads privatize themselves — that quiet leakage, not the reply-all storm, is the failure that actually loses customers.
For one-way traffic, a distribution list is exactly right: announcements, alerts, “FYI everyone in sales” — cheap, simple, no shared state to manage. The damage starts when a list address is used for anything that expects an answer. Because everyone received the message, everyone can assume someone else will handle it — the classic diffusion of responsibility — and the two observable outcomes are silence (nobody replied) and embarrassment (three people replied, differently). There is no way to see which happened, because there is no shared record to look at.
Use the rule of expected replies. If the address only broadcasts — newsletters in, notifications out to the team — a distribution list is the correct, lowest-maintenance tool. If the address is expected to answer people — support@, sales@, billing@ — use a shared mailbox at minimum, because answering requires shared state the list cannot hold. The distinction has nothing to do with volume: a list receiving five answerable emails a week fails in exactly the same way as one receiving fifty, just more slowly.
Two practical checks: configure and test the reply-to behavior, so team discussion does not accidentally go to the customer or vice versa; and audit your lists yearly — almost every company has at least one distribution list that quietly became a de facto support address, with each member privately assuming someone else is answering it. Migrating that one address to a shared mailbox usually surfaces a small archaeology of unanswered mail — treat that discovery as the cost of the old setup, not a failure of the new one.
A distribution list is one of email’s two team primitives — these entries cover the other one and the systems built when neither is enough.
Give your customers faster answers and your team their evenings back.
Desktop and mobile. Free for solo.