Disallow clubs from using CSC email #111

Open
opened 2023-10-26 04:08:21 -04:00 by merenber · 1 comment
Owner

Most club reps are not aware that the Unix user for their club has a CSC email address. As a result, if e.g. a cron job starts failing, the CSC email address gets spammed with messages, and nobody ever looks at them. We should require new clubs to have a non-CSC email address when they are created, and paste this into the ~/.forward of their Unix user.

At some point we should do this for existing clubs too, if we can determine their email address.

Most club reps are not aware that the Unix user for their club has a CSC email address. As a result, if e.g. a cron job starts failing, the CSC email address gets spammed with messages, and nobody ever looks at them. We should require new clubs to have a non-CSC email address when they are created, and paste this into the `~/.forward` of their Unix user. At some point we should do this for existing clubs too, if we can determine their email address.
merenber added the
priority
low
label 2023-10-26 04:08:21 -04:00
merenber added
priority
high
and removed
priority
low
labels 2024-03-01 18:00:48 -05:00
Author
Owner

Bumping to high because #110 depends on this issue being fixed first.

Bumping to high because #110 depends on this issue being fixed first.
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: public/pyceo#111
No description provided.