Distribution lists and mail-enabled groups turn one message into thousands, so a loose setting on a single group can hand an outsider a broadcast channel into the whole company or leak internal mail to the web. Most organisations have hundreds of groups created over many years, owned by people who have since left, with sender, membership and visibility settings nobody has reviewed. This guide covers the group mail settings that matter in Exchange Online and Google Workspace: who can send to a group, who can join it, who can read its archive and who can send as it. It is written for messaging administrators, identity teams and security engineers who need a repeatable review, not a one-off clean-up. Platforms are listed alphabetically by product name, and the order is not a ranking.
Key takeaways
- Sender restriction is the first control. Every large or sensitive list should accept mail only from internal, authenticated senders, and the biggest lists only from a named set of senders.
- Membership is an access grant. Open join settings let anyone add themselves to finance, HR or incident lists and read everything sent there from then on.
- Archives leak quietly. Group conversation archives that are readable by the whole organisation, or by anyone on the web, have exposed credentials and invoices to search engines.
- Send as and send on behalf are delegations. Treat them like mailbox permissions: few holders, a named owner and a periodic review.
- Owners must be current. A group whose owners have left cannot be governed, so ownership review comes before any other clean-up.
How group mail gets abused
Group mail abuse falls into four patterns, and each needs a different control. The settings below are the ones that close them.
| Abuse pattern | What happens | Primary control |
|---|---|---|
| External posting to internal lists | An outside sender, or a spoofed internal address arriving from the internet, mails an all-staff or department list directly, reaching everyone with one phishing message | Accept mail only from authenticated internal senders; restrict large lists to named senders |
| Internal broadcast misuse | A compromised internal account, or a careless user, mails the whole organisation; reply-all chains amplify it | Named-sender allow lists and moderation on the largest lists |
| Self-service joining | A user, or an attacker using a compromised account, joins a sensitive list and receives every future message | Closed or owner-approved membership on sensitive lists |
| Archive and visibility leakage | Group conversations are readable organisation-wide or publicly, so past mail, including attachments, is exposed | Private archives, restricted conversation viewing, organisation-level sharing defaults |
The all-staff list is the single most valuable target. A phishing email that arrives "from" the all-staff address, or that is posted to it by a sender the list should never have accepted, inherits the trust staff give to internal announcements. Spoofed internal sender addresses are a separate problem handled by DMARC enforcement on your own domain; see the DMARC, SPF and DKIM Guide and the Display Name and Exact Domain Spoofing Guide. The sender authentication setting on a group is the complementary control: it rejects unauthenticated mail at the group, whatever address it claims.
Exchange Online: distribution group settings
Exchange Online has three mail group types that matter here: distribution groups, mail-enabled security groups and Microsoft 365 Groups, plus dynamic distribution groups whose membership is calculated from a recipient filter. Microsoft documents the group settings in the Exchange admin centre and on the Set-DistributionGroup, Set-UnifiedGroup and Set-DynamicDistributionGroup cmdlet pages.
| Setting (cmdlet parameter) | What it controls | Documented default | Recommended for large or sensitive lists |
|---|---|---|---|
RequireSenderAuthenticationEnabled | $true accepts mail only from authenticated (internal) senders and rejects unauthenticated (external) senders | The admin centre's delivery management option "Only allow messages from people inside my organization" is the default for distribution groups | $true, confirmed by report rather than assumed |
AcceptMessagesOnlyFromSendersOrMembers | Only listed senders, or members of listed groups, can send; everyone else is rejected | Blank, which accepts mail from all senders | Set on all-staff and other organisation-wide lists to a small communications group |
RejectMessagesFromSendersOrMembers | Listed senders are rejected | Blank | Use sparingly; allow lists are easier to reason about than block lists |
ModerationEnabled, ModeratedBy, BypassModerationFromSendersOrMembers | Messages are held for a moderator; if no moderator is named on a distribution group, the owners approve | ModerationEnabled is $false | Moderate the largest lists, with a bypass list for the communications team |
MemberJoinRestriction | Open, Closed or ApprovalRequired | Closed for universal distribution and security groups | Closed or ApprovalRequired; never Open on sensitive lists |
MemberDepartRestriction | Whether members can leave without approval | Open for universal distribution groups | Closed only where leaving would break a legal or safety notification list |
ManagedBy | Owners, who can change properties, add and remove members, delete the group and approve moderated mail | The creating account, if none is specified | At least two current owners; no departed users |
GrantSendOnBehalfTo | Who can send on behalf of the group | Blank (nobody) | Named holders only, reviewed with mailbox delegations |
HiddenFromAddressListsEnabled | Hides the group from address lists; hidden groups still receive mail sent to their address | $false | Hide sensitive lists, but do not treat hiding as a sender control |
ReportToOriginatorEnabled, ReportToManagerEnabled | Whether delivery status notifications go to senders or to the owner | $true and $false | Keep sender notifications on internal lists so legitimate senders learn they were rejected |
Microsoft 365 Groups: Set-UnifiedGroup carries the same RequireSenderAuthenticationEnabled and AcceptMessagesOnlyFromSendersOrMembers parameters. Microsoft's documentation notes that anyone can send email to a private Microsoft 365 Group and receive replies from it, even though membership requires owner approval, so the AccessType of Private is not a sender control. HiddenFromExchangeClientsEnabled hides a group from Outlook and the global address list, but the group can still receive messages.
Dynamic distribution groups: membership comes from a precanned filter (IncludedRecipients with Conditional parameters such as ConditionalDepartment) or a custom OPATH RecipientFilter. The filter is the access decision, so it needs the same review as any rule-based access: an attribute that users or HR systems can set loosely, such as a free-text department, can quietly pull the wrong people into a sensitive list. Microsoft notes that conditional values are matched exactly, combined with OR within one property and AND across properties.
Specified senders and Reply-To: Microsoft warns that the sender check for a restricted group matches the Reply-To address rather than the From field, and that a group restricted to internal senders rejects a mail contact even if that contact is on the allowed list. Test any restriction with a real message from each sender type before relying on it. For the wider tenant baseline see the Exchange Online Security Guide, and for transport-level controls the Exchange Online Mail Flow Rules Security Guide.
Google Workspace: Groups for Business settings
Google Workspace controls group mail at two levels: organisation-wide sharing settings for Groups for Business set by an administrator, and per-group settings set by group owners within those limits. The organisation-level settings cap what owners can do, so they are the place to start.
| Organisation-wide setting | Options | Documented default | Recommended |
|---|---|---|---|
| Accessing groups from outside the organisation | Private (internal users only) or public (anyone on the web) | Private | Private, unless a specific public list has a business owner and review |
| Creating groups | Admins only, organisation users, or anyone on the web | Anyone in the organisation | Organisation users, with a naming convention and periodic review; admins only for regulated environments |
| Group owners can allow external members | Allowed or not allowed | Not allowed | Leave off; enable only with a documented need |
| Group owners can allow incoming email from outside the organisation | Allowed or not allowed | Not allowed | Leave off; route external contact through named support addresses |
| Default for permission to view conversations | Owners only, owners and managers, all members, all organisation users, or anyone on the web | All organisation users | All group members, so new groups do not expose archives organisation-wide |
| Hiding groups from non-members | Owners can or cannot hide groups from the directory | Both options unchecked | Allow hiding for sensitive groups |
Google notes that where a super administrator has turned on multi-party approval for Groups for Business sharing, changes to these settings need approval before they take effect, which is a useful guard on the most consequential switch, public access.
Per-group settings: owners set Who can join group (from "Invited users only" to "Anyone on the web can join"), Allow external members, Who can post, Who can view members, Who can contact group owners and Who can post as group. Posting policy adds Message moderation ("No moderation", "Moderate messages from non-members", "Moderate all messages") and Spam message handling, where "Reject all messages marked as spam" is the strictest option. Post replies to controls where replies go; for announcement lists, replies to the author only prevent reply-all floods. See the Gmail Security Settings Guide for Workspace Admins for inbound mail protection and the Google Workspace Security Guide for the tenant baseline.
The public archive lesson: in 2018 KrebsOnSecurity reported research by Kenna Security that found more than 9,600 organisations with public Google Groups settings, with roughly a third estimated to be exposing sensitive email such as credentials and financial details through indexed group archives. Google's advice at the time was to review which groups are public and to note that setting the domain-level option back to private blocks outside access to all groups. The organisation-level default above is the control that prevents a repeat.
Choosing a posture by list type
Not every group needs the same settings. Applying the strictest posture everywhere generates owner tickets and workarounds; applying the loosest everywhere leaves the all-staff list open. Tier groups and apply a profile per tier.
| List type | Who can send | Membership | Archive visibility |
|---|---|---|---|
| Organisation-wide (all staff, all managers, country lists) | Named communications senders only; moderation for anyone else | Dynamic or provisioned from HR; no self-join | Members only |
| Sensitive functions (finance, HR, legal, incident response, executives) | Internal authenticated senders; named senders for the most sensitive | Closed, owner-managed, reviewed quarterly | Members only, hidden from directory |
| Team and project lists | Internal authenticated senders | Owner approval | Members only |
| External-facing addresses (sales@, support@, security@) | External senders allowed by design | Closed, small and owner-managed | Members only; consider a shared mailbox or ticketing tool instead |
| Community or interest lists | Internal authenticated senders | Open join is acceptable | Organisation users |
Small versus large organisations: a company of a few hundred people can usually review every group by hand once a year and lock the all-staff list to two or three senders. A large enterprise with thousands of groups needs the tiering above, automation that reports drift from each tier's profile, and an expiry or attestation process for groups that nobody owns. Where an external address is really a team inbox, a shared mailbox with delegated access is often easier to govern than a distribution list; see the Mailbox Delegation Review Checklist.
Where identity fits: apps and service accounts that send to groups
Many messages to large lists are sent by applications, not people: HR systems, monitoring tools, ticketing platforms and marketing integrations. If such an application holds a credential that can send to the all-staff list, that credential is a broadcast capability and a phishing channel if stolen. Put application senders on the named-sender list explicitly rather than opening the list to all internal senders, give each application its own sending identity so its messages can be traced, and review those identities alongside other machine credentials. In Microsoft 365 this includes app registrations granted mail sending permissions; in Google Workspace it includes service accounts with domain-wide delegation. See the Google Workspace Domain-Wide Delegation Security Guide and the Consent Phishing and Illicit OAuth Grants Guide.
Implementation: a phased clean-up
- Inventory. Export every mail-enabled group with its type, member count, owners, sender restriction, join restriction, moderation state, send-on-behalf holders and, for Google, external member, external posting and conversation viewing settings. Exchange Online PowerShell (
Get-DistributionGroup,Get-UnifiedGroup,Get-DynamicDistributionGroup) and the Google Admin console or Directory and Groups Settings APIs both support this. - Fix ownership. Flag groups with no owner, a single owner or a departed owner. Assign current owners before changing anything else, because owners will field the questions the next phases create.
- Close the organisation-level defaults. In Google Workspace confirm groups are private to the organisation, external members and external incoming mail are off at the organisation level, and the default conversation viewing permission is members only. In Exchange Online confirm newly created groups default to internal senders only.
- Lock the top tier. Apply named-sender restrictions and moderation to organisation-wide lists. Announce the change, name the communications senders and give everyone else a route (a request form or the moderation queue).
- Pilot, then roll out by tier. Apply the sensitive-function profile to a pilot set of groups, test with real messages from internal, external, application and mail contact senders, then extend. Record the previous setting of every group changed so a rollback is a single scripted reversal.
- Handle exceptions. Groups that must accept external mail get a named business owner, a justification and a review date. Prefer moving them to a shared mailbox or ticketing tool.
- Make it continuous. Schedule a drift report against the tier profiles, include group ownership in joiner, mover and leaver processes, and attest sensitive group membership quarterly. See the Employee Offboarding Security Guide.
Detection and measurement
- Configuration changes: alert on changes that loosen a group: sender authentication turned off, a sender allow list cleared, join restriction set to open, external members or external posting allowed, or archive viewing widened to public. Exchange Online admin actions are captured in the Microsoft Purview audit log, and Google Workspace records group setting changes in the Groups audit log; see the Google Workspace Audit Log Detection Guide.
- Membership changes: alert on self-joins and new members on sensitive lists, especially from accounts that have recently signed in from new locations.
- Unusual sends: use message trace or email logs to spot first-time senders to organisation-wide lists, large lists receiving external mail, and bursts of replies.
- Rejected attempts: rejected external posts to internal lists show the restriction working and can show targeting.
Metrics to report:
- Percentage of groups above an agreed size (for example 100 members) that reject unauthenticated senders.
- Number of organisation-wide lists with a named-sender allow list (target: all).
- Percentage of groups with at least two current owners.
- Number of sensitive groups with open join or organisation-wide archive visibility (target: zero).
- Number of groups accepting external mail with an approved, unexpired exception, against the total accepting external mail.
- Time from a loosening configuration change to review.
Common failure patterns
- Assuming the default held. Groups created by scripts, migrations or older tools can carry settings that differ from today's admin centre default. Report on the actual value of every group.
- Treating hidden as protected. Hiding a group from the address list or directory does not stop mail sent to its address. Hidden groups still need sender restrictions.
- Private membership, open posting. A private Microsoft 365 Group or a closed Google group can still accept mail from anyone if the sender settings allow it.
- Allowing all internal senders on the all-staff list. One compromised account then reaches everyone. Organisation-wide lists need a named-sender list, not just internal-only.
- Orphaned groups. Groups whose owners left cannot approve moderated mail or membership requests, so someone eventually opens them up to stop the complaints.
- Organisation-wide archives by default. Leaving the default conversation viewing permission at all organisation users means every new HR or finance group exposes its history to the whole company until an owner notices.
Framework mapping
| Framework | Reference | How group mail controls apply |
|---|---|---|
| NIST SP 800-53 Rev 5 | AC-2 Account Management; AC-3 Access Enforcement; AC-6 Least Privilege | Group ownership and membership review; sender and join restrictions as enforced access decisions |
| NIST SP 800-53 Rev 5 | AC-21 Information Sharing; AC-22 Publicly Accessible Content | Archive visibility and public group settings |
| NIST SP 800-53 Rev 5 | AU-6 Audit Record Review, Analysis, and Reporting | Alerting on loosening configuration and membership changes |
| NIST CSF 2.0 | PR.AA-05; PR.PS-01 | Access permissions managed with least privilege; configuration management of group settings |
| CIS Controls v8.1 | Control 6 Access Control Management; Control 9 Email and Web Browser Protections | Membership governance and email channel protection |
| ISO/IEC 27001:2022 Annex A | 5.15 Access control; 5.18 Access rights; 8.9 Configuration management | Group access policy, periodic review and baseline settings |
| MITRE ATT&CK v20 | T1534 Internal Spearphishing | Named-sender restrictions limit the reach of a compromised internal account |
Practitioner checklist
- Export every mail-enabled group with owners, sender, join, moderation, delegation and visibility settings.
- Give every group at least two current owners and remove departed owners.
- Confirm organisation-level defaults: private groups, no external members or external mail by default, member-only archive viewing.
- Restrict every organisation-wide list to named senders and moderate everyone else.
- Set sensitive function lists to closed membership, internal senders only and member-only archives.
- Put application senders on allow lists by their own sending identities, and review those identities with other machine credentials.
- Review send-on-behalf and send-as holders on groups alongside mailbox delegations.
- Review dynamic group filters and the attributes they rely on.
- Alert on loosening changes and on self-joins to sensitive lists.
- Track exceptions for external posting with an owner and expiry date.
Standards and references
- Microsoft Learn: Set-DistributionGroup
- Microsoft Learn: Manage distribution groups in Exchange Online
- Microsoft Learn: Set-UnifiedGroup
- Microsoft Learn: Set-DynamicDistributionGroup
- Google Workspace Admin Help: Set organisation-wide policies for using groups
- Google Groups Help: Change group settings
- KrebsOnSecurity: Is Your Google Groups Leaking Data?
Related NHI Mgmt Group resources: Collaboration Tool Security Guide · Exchange Online Security Guide · Gmail Security Settings Guide for Workspace Admins · Mailbox Delegation Review Checklist