Disallow clubs from using CSC email #111
Labels
No Label
priority
high
priority
low
priority
medium
priority
very high
BUG
Feature
High Priority
Low Priority
Medium Priority
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: public/pyceo#111
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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.
Bumping to high because #110 depends on this issue being fixed first.