Mailing Lists: Difference between revisions
(contest committee no longer exists (at least its mailing list doesn't)) |
No edit summary |
||
| Line 18: | Line 18: | ||
Most of our mailing lists are handled through [http://www.gnu.org/software/mailman/index.html Mailman], including the lists for the [[Executive]] (<tt>exec@csclub.uwaterloo.ca</tt>), the Program Committee (<tt>progcom@csclub.uwaterloo.ca</tt>), and the [[Systems Committee]] (<tt>syscom@csclub.uwaterloo.ca</tt>). |
Most of our mailing lists are handled through [http://www.gnu.org/software/mailman/index.html Mailman], including the lists for the [[Executive]] (<tt>exec@csclub.uwaterloo.ca</tt>), the Program Committee (<tt>progcom@csclub.uwaterloo.ca</tt>), and the [[Systems Committee]] (<tt>syscom@csclub.uwaterloo.ca</tt>). |
||
== Mailman 3 == |
|||
Starting from April 2021, we now use [https://docs.mailman3.org/ Mailman 3] for managing our mailing lists. Mailman 3 is split into three |
|||
independent components: |
|||
* Mailman 3 Core is responsible for sending and receiving emails. |
|||
* Postorius is the web admin UI for creating and managing mailing lists. |
|||
* HyperKitty is the archiver, where past messages can be viewed and searched. |
|||
=== Day-to-Day Operations === |
|||
The Django admin site for Mailman 3 is accessible from [https://mailman.csclub.uwaterloo.ca/admin/ here]. Generally, you'll only need to use |
|||
this to see the list of accounts, and to assign/remove permissions from them. |
|||
If you are logged in as a superuser, you should be able to see a list of all the mailing lists from |
|||
[https://mailman.csclub.uwaterloo.ca/postorius/lists here]. After clicking on a list, you should be able to access and modify all of its |
|||
settings, including subscription policy and message acceptance. Most of the setting names should be self-explanatory. For example, under |
|||
'Held Messages', you can see a list of all held messages, and take an action on each one (discard, reject, accept, etc.). |
|||
=== Installation === |
|||
The steps below describe how Mailman 3 was installed on the mail container and how we migrated the lists from Mailman 2. Note that some lists |
|||
were not migrated due to inactivity. See <code>/var/lib/mailman/data/aliases</code> in the mail container to see which lists were not |
|||
migrated. |
|||
[[Category:Systems]] |
[[Category:Systems]] |
||
Revision as of 18:15, 17 April 2021
Systems Mailing Lists
The following mailing lists are the targets of various automated notifications. Subscribe to them to receive these notifications.
git@csclub.uwaterloo.ca
Commits to club git repositories are sent to this list in patch form.
packages@csclub.uwaterloo.ca
Changes to our debian repository are sent to this list.
ceo@csclub.uwaterloo.ca
CEO sends a note to this list every time a new member or club is added.
Technical Details
Most of our mailing lists are handled through Mailman, including the lists for the Executive (exec@csclub.uwaterloo.ca), the Program Committee (progcom@csclub.uwaterloo.ca), and the Systems Committee (syscom@csclub.uwaterloo.ca).
Mailman 3
Starting from April 2021, we now use Mailman 3 for managing our mailing lists. Mailman 3 is split into three independent components:
- Mailman 3 Core is responsible for sending and receiving emails.
- Postorius is the web admin UI for creating and managing mailing lists.
- HyperKitty is the archiver, where past messages can be viewed and searched.
Day-to-Day Operations
The Django admin site for Mailman 3 is accessible from here. Generally, you'll only need to use this to see the list of accounts, and to assign/remove permissions from them.
If you are logged in as a superuser, you should be able to see a list of all the mailing lists from here. After clicking on a list, you should be able to access and modify all of its settings, including subscription policy and message acceptance. Most of the setting names should be self-explanatory. For example, under 'Held Messages', you can see a list of all held messages, and take an action on each one (discard, reject, accept, etc.).
Installation
The steps below describe how Mailman 3 was installed on the mail container and how we migrated the lists from Mailman 2. Note that some lists
were not migrated due to inactivity. See /var/lib/mailman/data/aliases in the mail container to see which lists were not
migrated.