Moderation of class and student lists

[pricem]

It is desired to require admin approval of e-mails sent to forwarding lists such as M100-students and M100-teachers. While this capability is allowed by Mailman, it may need to be added to the built-in existing e-mail forwarding system. (Requested by Stanford in spring 2014.)

See also #119 and #298.

[willgearty]

Stanford is having some problems with spam emails to class lists, in addition to some inappropriate material being shared from teachers to students. Any chance this or #1680 is getting any attention? @pricem @benjaminjkraft ?

[milescalabresi]

Other chapters have also requested that /admin/dbmail/textofemail/ get a copy of these messages.

[benjaminjkraft]

@willgearty I think as a workaround they do already cc the server archive address. That's currently a shared LU archive address, but if you want you could create a gmail and ask websupport to redirect it there. (It might be a good idea to also give web-team access to that archive for debugging, although it's not strictly necessary.) It gets a lot of email, so you won't want that to directly go to a bunch of people, but you could set up a filter to forward just the class mailing list traffic to another list or person.

[willgearty]

@benjaminjkraft Yeah, our gmail account already gets a copy of all of the emails. But I do think there is merit to having them archived on the website as well, as @milescalabresi suggested. However, our real problem is being able to moderate the emails BEFORE they are sent to the students/teachers/etc. Some way to approve or reject emails before the server then sends them to the recipients. As I said in my email to websupport, our chapter had a pretty severe incident this past Splash via these mailing lists and we had no control over what the teacher was able to send to his students.

[benjaminjkraft]

Ok, got it.