Mailing Lists - Revision history

Merenber: /* Moderation */

2022-08-27T18:14:14Z

Moderation

← Older revision		Revision as of 13:14, 27 August 2022
Line 23:		Line 23:

	# When you become an exec, you are automatically subscribed to the <code>exec-moderators</code> mailing list.		# When you become an exec, you are automatically subscribed to the <code>exec-moderators</code> mailing list.
	# <del>You should now [https://mailman.csclub.uwaterloo.ca/accounts/signup/?next=/postorius/lists/ create a mailman account] '''with your CSC email''', and sign up for a weekly shift to mod the <code>exec</code> mailing list.</del> <br> Use the shared exec account for accessing Mailman. Ask an existing exec for the location.		# <del>You should now [https://mailman.csclub.uwaterloo.ca/accounts/signup/?next=/postorius/lists/ create a mailman account] '''with your CSC email''', and sign up for a weekly shift to mod the <code>exec</code> mailing list.</del> <br> Use the shared exec account for accessing Mailman. Ask an existing exec for the location. <br>If you are a syscom member, use the sysadmin account instead (password is stored in the usual place).
	# You can then remove yourself from the <code>exec-moderators</code> mailing list. To do this, go to [https://mailman.csclub.uwaterloo.ca/postorius/lists/exec-moderators.csclub.uwaterloo.ca/members/member/ this page] and unsubscribe yourself.		# You can then remove yourself from the <code>exec-moderators</code> mailing list. To do this, go to [https://mailman.csclub.uwaterloo.ca/postorius/lists/exec-moderators.csclub.uwaterloo.ca/members/member/ this page] and unsubscribe yourself.
	# When it's your turn to mod the list, go to [https://mailman.csclub.uwaterloo.ca/postorius/lists/exec.csclub.uwaterloo.ca/held_messages held messages] and read through each email before clicking '''Accept''' if it is not spam.		# When it's your turn to mod the list, go to [https://mailman.csclub.uwaterloo.ca/postorius/lists/exec.csclub.uwaterloo.ca/held_messages held messages] and read through each email before clicking '''Accept''' if it is not spam.

Merenber: /* Moderation */

2022-06-05T17:02:21Z

Moderation

← Older revision		Revision as of 12:02, 5 June 2022
Line 23:		Line 23:

	# When you become an exec, you are automatically subscribed to the <code>exec-moderators</code> mailing list.		# When you become an exec, you are automatically subscribed to the <code>exec-moderators</code> mailing list.
	# You should now [https://mailman.csclub.uwaterloo.ca/accounts/signup/?next=/postorius/lists/ create a mailman account] '''with your CSC email''', and sign up for a weekly shift to mod the <code>exec</code> mailing list.		# <del>You should now [https://mailman.csclub.uwaterloo.ca/accounts/signup/?next=/postorius/lists/ create a mailman account] '''with your CSC email''', and sign up for a weekly shift to mod the <code>exec</code> mailing list.</del> <br> Use the shared exec account for accessing Mailman. Ask an existing exec for the location.
	# You can then remove yourself from the <code>exec-moderators</code> mailing list. To do this, go to [https://mailman.csclub.uwaterloo.ca/postorius/lists/exec-moderators.csclub.uwaterloo.ca/ this page] and ~~click~~ ~~'''Unsubscribe''' (in red)~~.		# You can then remove yourself from the <code>exec-moderators</code> mailing list. To do this, go to [https://mailman.csclub.uwaterloo.ca/postorius/lists/exec-moderators.csclub.uwaterloo.ca/members/member/ this page] and unsubscribe yourself.
	# When it's your turn to mod the list, go to [https://mailman.csclub.uwaterloo.ca/postorius/lists/exec.csclub.uwaterloo.ca/held_messages held messages] and read through each email before clicking '''Accept''' if it is not spam.		# When it's your turn to mod the list, go to [https://mailman.csclub.uwaterloo.ca/postorius/lists/exec.csclub.uwaterloo.ca/held_messages held messages] and read through each email before clicking '''Accept''' if it is not spam.
	# If it IS spam, copy the email address it is from, and click '''Discard.''' '''DO NOT CLICK REJECT'''.		# If it IS spam, copy the email address it is from, and click '''Discard.''' '''DO NOT CLICK REJECT'''.

R389li: Add Moderation instructions

2022-05-31T23:15:02Z

Add Moderation instructions

← Older revision		Revision as of 18:15, 31 May 2022
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>).

			== Moderation ==
			Our mailing lists need to be moderated. The process for that is this:

			# When you become an exec, you are automatically subscribed to the <code>exec-moderators</code> mailing list.
			# You should now [https://mailman.csclub.uwaterloo.ca/accounts/signup/?next=/postorius/lists/ create a mailman account] '''with your CSC email''', and sign up for a weekly shift to mod the <code>exec</code> mailing list.
			# You can then remove yourself from the <code>exec-moderators</code> mailing list. To do this, go to [https://mailman.csclub.uwaterloo.ca/postorius/lists/exec-moderators.csclub.uwaterloo.ca/ this page] and click '''Unsubscribe''' (in red).
			# When it's your turn to mod the list, go to [https://mailman.csclub.uwaterloo.ca/postorius/lists/exec.csclub.uwaterloo.ca/held_messages held messages] and read through each email before clicking '''Accept''' if it is not spam.
			# If it IS spam, copy the email address it is from, and click '''Discard.''' '''DO NOT CLICK REJECT'''.
			# Go to [https://mailman.csclub.uwaterloo.ca/postorius/lists/exec.csclub.uwaterloo.ca/settings/message_acceptance#id_discard_these_nonmembers message acceptance] and add the address to the '''Discard These Non-Members''' box. Don't forget to click '''Save Changes'''.

	== Mailman 3 ==		== Mailman 3 ==

Merenber: /* Mailman 3 */

2022-05-24T02:28:24Z

Mailman 3

← Older revision		Revision as of 21:28, 23 May 2022
Line 79:		Line 79:
	<pre>		<pre>
	EMAIL_HOST = 've-mail'		EMAIL_HOST = 've-mail'
	EMAIL_PORT = '10025		EMAIL_PORT = 10025
	</pre>		</pre>
	See [https://docs.djangoproject.com/en/4.0/topics/email/#smtp-backend here] for more details. "ve-mail" is an alias set in /etc/hosts.		See [https://docs.djangoproject.com/en/4.0/topics/email/#smtp-backend here] for more details. "ve-mail" is an alias set in /etc/hosts.

Merenber: /* Installation */

2022-05-24T02:22:06Z

Installation

← Older revision		Revision as of 21:22, 23 May 2022
Line 75:		Line 75:

	<b>Update 2</b>: Mailman has been moved into its own [[systemd-nspawn]] container. It communicates with the mail container via a dedicated veth pair. Some relevant changes include: apply [https://gitlab.com/mailman/hyperkitty/-/merge_requests/379 this] patch; edit /opt/mailman3/lib/python3.9/site-packages/mailman/database/alembic/versions/bc0c49c6dda2_use_utf8mb4_in_mysql.py so that the type of autoresponse_postings_text is SAUnicodeLarge instead of SAUnicode4Byte; update main.cf and master.cf (and postfix_lmtp and postfix_lmtp.db in /opt/mailman3/data) to account for the new veth pair IP address of the mailman container.		<b>Update 2</b>: Mailman has been moved into its own [[systemd-nspawn]] container. It communicates with the mail container via a dedicated veth pair. Some relevant changes include: apply [https://gitlab.com/mailman/hyperkitty/-/merge_requests/379 this] patch; edit /opt/mailman3/lib/python3.9/site-packages/mailman/database/alembic/versions/bc0c49c6dda2_use_utf8mb4_in_mysql.py so that the type of autoresponse_postings_text is SAUnicodeLarge instead of SAUnicode4Byte; update main.cf and master.cf (and postfix_lmtp and postfix_lmtp.db in /opt/mailman3/data) to account for the new veth pair IP address of the mailman container.

			<b>Update 3</b>: So apparently Django tries to send emails over localhost by default, which doesn't work for us because the mail and mailman containers are now separate. Add the following params to /etc/mailman3/settings.py:
			<pre>
			EMAIL_HOST = 've-mail'
			EMAIL_PORT = '10025
			</pre>
			See [https://docs.djangoproject.com/en/4.0/topics/email/#smtp-backend here] for more details. "ve-mail" is an alias set in /etc/hosts.

			-------------------------------------------------------------

	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		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

Merenber: /* Day-to-Day Operations */

2022-05-06T18:08:35Z

Day-to-Day Operations

← Older revision		Revision as of 13:08, 6 May 2022
Line 61:		Line 61:

	<b>Make sure you disable the Pipermail archiver</b> (go to Settings -> Archiving and uncheck the Pipermail box). That archiver only works for lists which were migrated from Mailman 2.		<b>Make sure you disable the Pipermail archiver</b> (go to Settings -> Archiving and uncheck the Pipermail box). That archiver only works for lists which were migrated from Mailman 2.

			==== User gets subscribed to the same list twice ====
			Sometimes a user gets subscribed to a list twice and it becomes impossible to unsubscribe them. This actually happened to us before, and as of this writing, it is still [https://gitlab.com/mailman/mailman/-/issues/826 an open issue]. If this happens again, just run the following:
			<pre>
			su -s /bin/bash list
			cd /opt/mailman3
			. bin/activate
			mailman shell -r delete_dup_sub Yes
			</pre>

	=== Installation ===		=== Installation ===

Merenber: /* Creating a new list */

2022-05-06T17:27:52Z

Creating a new list

← Older revision		Revision as of 12:27, 6 May 2022
Line 59:		Line 59:
	</pre>		</pre>
	I have never actually attempted this before, so I am not certain that it will work.		I have never actually attempted this before, so I am not certain that it will work.

			<b>Make sure you disable the Pipermail archiver</b> (go to Settings -> Archiving and uncheck the Pipermail box). That archiver only works for lists which were migrated from Mailman 2.

	=== Installation ===		=== Installation ===

Merenber: /* Day-to-Day Operations */

2022-05-01T07:27:26Z

Day-to-Day Operations

@@ Line 48: / Line 48: @@
 </pre>
 You need to press Ctrl-D (EOF) after entering the list of new members.
 === Installation ===

Merenber: /* Installation */

2022-05-01T07:21:45Z

Installation

← Older revision		Revision as of 02:21, 1 May 2022
Line 51:		Line 51:
	=== Installation ===		=== Installation ===
	<b>Update</b>: We now use the pip package of mailman (from PyPI) instead of the Debian package, since the Debian package was giving us too many issues. All of the configs are now in /etc/mailman3, and the data files are in /opt/mailman3. A virtualenv was created in /opt/mailman3.		<b>Update</b>: We now use the pip package of mailman (from PyPI) instead of the Debian package, since the Debian package was giving us too many issues. All of the configs are now in /etc/mailman3, and the data files are in /opt/mailman3. A virtualenv was created in /opt/mailman3.

			<b>Update 2</b>: Mailman has been moved into its own [[systemd-nspawn]] container. It communicates with the mail container via a dedicated veth pair. Some relevant changes include: apply [https://gitlab.com/mailman/hyperkitty/-/merge_requests/379 this] patch; edit /opt/mailman3/lib/python3.9/site-packages/mailman/database/alembic/versions/bc0c49c6dda2_use_utf8mb4_in_mysql.py so that the type of autoresponse_postings_text is SAUnicodeLarge instead of SAUnicode4Byte; update main.cf and master.cf (and postfix_lmtp and postfix_lmtp.db in /opt/mailman3/data) to account for the new veth pair IP address of the mailman container.

	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		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

Merenber: /* Day-to-Day Operations */

2021-12-25T00:47:54Z

Day-to-Day Operations

← Older revision		Revision as of 19:47, 24 December 2021
Line 36:		Line 36:
	'Held Messages', you can see a list of all held messages, and take an action on each one (discard, reject, accept, etc.).		'Held Messages', you can see a list of all held messages, and take an action on each one (discard, reject, accept, etc.).

	Unfortunately it is not possible to subscribe a new member from the web UI (although you can unsubscribe them). You can do this from the command line in the mail container. For example, to add people to the exec list:		Unfortunately it is not possible to subscribe a new member from the web UI, although you can unsubscribe them (open issue [https://gitlab.com/mailman/postorius/-/issues/189 here]). You can do this from the command line in the mail container. For example, to add people to the exec list:
	<pre>		<pre>
	sudo		sudo