Setting Up Shared Email Addresses for Associations

Here's how to set up shared email addresses like vorstand@ and kasse@ on Virtualmin. Mailbox, alias, or mailing list? Permissions, spam, and handover during board changes.

The board changes, and suddenly association communication grinds to a halt because all inquiries went to the former chairperson's private address. To prevent this, it's worth setting up functional email addresses like vorstand@, kasse@, or presse@. On a Virtualmin server, this is done in just a few clicks once you know the differences between a mailbox, an alias, and a mailing list.

Mailbox, alias, or mailing list: Which fits which address?

A real mailbox has a password and storage space. The user logs in and manages their emails themselves. An alias only forwards and has no mailbox of its own. A mailing list sends every email to multiple recipients at once.

For most association addresses, an alias is the best choice. The vorstand@ address stays in place, and you can adjust the forwarding with each change. You only need a mailbox if someone actually needs to send and archive emails from this address. A mailing list is suitable for round-robin emails to the entire board.

Typical assignment for associations

  • vorstand@ – Alias to the current chairperson, often additionally to the deputy.
  • kasse@ – Alias to the treasurer, sometimes with forwarding to the auditor.
  • presse@ – Alias to the person who writes press releases, or a mailing list to several media officers.
  • info@ – Alias to a shared mailbox that several board members read.

Step by step: Creating shared addresses on Virtualmin

Log in to Virtualmin as administrator and select the appropriate virtual server. Under "Email" you'll find the items "Users and Aliases" as well as "Mail Mailing Lists". There you create the addresses.

  1. Open "Users and Aliases" and click "Add Alias".
  2. Enter, for example, vorstand as the alias name and select the chairperson's private address as the target.
  3. Add further targets if needed, such as the deputy.
  4. Save the settings. Test the forwarding with an email from your own account.
  5. For a mailing list, switch to "Mail Mailing Lists" and create a new list with the desired members.

Don't forget to create clear documentation for each address. A short text document in the association folder is enough: which address forwards where, who has access, when it was last changed.

Managing permissions and representation rules cleanly

An alias is only as good as the person who manages it. Determine who in the association is authorized to change forwardings. This is often the administrator or a technically savvy board member. Avoid having multiple people make changes at the same time without coordinating.

For representation cases, you can enter multiple target addresses for an alias. This way the deputy automatically receives all emails if the chairperson is unavailable. Alternatively, you set up a mailing list containing both recipients. Important: Every change should be noted in the association minutes or a handover file.

Keeping spam and data protection in view

Shared addresses like info@ or presse@ are often targets of spam. Activate a spam filter on the server and determine whether suspicious emails are marked or rejected outright. An alias without its own mailbox cannot manage spam folders, so filtering at the entry point is important.

Data protection: Only forward association emails to people who consent to it. Private addresses of board members should not be publicly listed in the imprint. Use an internal association list for forwarding and inform all parties involved about the forwarding. If you have questions about legal permissibility, a data protection officer or a lawyer can help; this is not legal advice.

Board change: How to hand over the addresses smoothly

An orderly transition begins with a checklist. You should work through these points with every change:

  • Collect the new target addresses of the officeholders and enter them in the alias.
  • Remove old private addresses from the forwarding once the new person is trained.
  • Send a test email to all shared addresses and have receipt confirmed.
  • Change the passwords for the Virtualmin panel if the previous administrator leaves.
  • Update the documentation and store it in the association folder.

A realistic example: The previous chairperson leaves. Until now, vorstand@ went to max@privat.de. You change the alias to the new chairperson Erika Muster and add her deputy as a second target. After the test, both confirm receipt. The old address is removed, and the handover record states who made which change and when.

If you're unsure whether your association needs its own server for such tasks, you'll find the necessary flexibility on virtual servers. For smaller associations, a web hosting package with email functions is often enough. What matters is that the addresses work independently of individuals and that the transition is documented.