You want a separate address for club messages but do not want another inbox to monitor. An alias may suit that task. The important question is whether the address is simply another route into your existing account or a genuinely separate account with its own access.
Providers use aliases differently. For a personal Microsoft account, Microsoft explains that aliases share account resources and a password. That makes another address useful for organisation, but it does not create an independent security boundary.
Test the ordinary message journey
Before giving the address to a group, send a test message to it from another account you control. Check where it arrives, whether a rule can identify it and what address appears when you reply. An alias that receives neatly but replies from an unexpected address may not match your intended use.
Write down the provider’s actual behaviour instead of assuming it matches a tutorial for another service. Some systems support separate sending identities; some use forwarding addresses or address tags with different limitations.
Organisation is not anonymity
An alias can help separate categories of mail, but it should not be presented as a guarantee that recipients cannot connect identities. Display names, signatures, reply headers and the messages themselves can reveal the relationship.
Also distinguish deleting an inbox rule from removing the address. Before retiring an alias, check which services use it for sign-in, receipts or recovery. Read the provider’s removal instructions carefully; do not assume a removed address can always be recreated.
For a small personal system, keep a private list with three fields: address, purpose and linked services. Review it when a club role or project ends. That little record makes aliases easier to maintain and reduces the chance that tidying an inbox also cuts off an important account message.