One address that reaches the whole team

Some addresses should reach more than one person. Enquiries that two people answer, alerts a small team should all see, an announcement address for a set of site owners. Forwarding to three mailboxes works until the fourth person joins and nobody remembers where the rule lives.

A mailing list makes the membership the thing you edit, rather than a rule buried in one account's mail settings.

List or forwarder

• A forwarder sends copies onward. Good for one or two recipients who never change. There is no record of who is on it beyond the rule itself.
• A list has members you add and remove, an archive, and settings for who may post. Worth it once the recipients change or once more than a couple of people are involved.

Setting one up is a short form and the video above covers it. The only irreversible choice in there is the name, because it becomes the address and it also claims a family of control addresses alongside it.

Decide who may post before you tell anyone the address

This is the setting that decides whether the list is useful or a liability. A list that accepts mail from anyone will eventually be found and used to relay, and the messages go out with your domain on them.

Restrict posting to subscribed addresses and hold everything else for moderation. Do it when you create the list, not after the first incident.

Why this matters more on a network

Sending reputation is not per site. A list abused on one domain affects how mail from your addresses is treated generally, and on an estate where several sites send from the same infrastructure that reaches further than the one account.

The same applies to who you put on it. Adding addresses that never asked to be there produces complaints, and complaints are the fastest way to make ordinary transactional mail from your other sites start landing in spam folders.

Housekeeping that actually matters

• Remove hard bounces. Repeatedly sending to dead mailboxes is a negative signal, and it accumulates.
• Keep one owner. A list with no named owner is a list nobody prunes.
• Mind the reserved names. Creating a list also reserves control addresses such as -request and -owner on that name, so do not pick a name a person may later want as a mailbox.

Where a list stops being the right tool

Beyond a few hundred recipients you want a sending service with proper unsubscribe handling and delivery reporting. Lists also rewrite headers in ways that interact with authentication, and a setup that is misaligned is a common reason large providers reject list mail. The DMARC specification covers the mechanics if you are sending at that scale.