Skip to Content.
Sympa Menu

en - [sympa-users] RE: FERPA, witness protection and toatl non disclosure users

Subject: The mailing list for listmasters using Sympa

List archive

Chronological Thread  
  • From: "Chris Andrews" <address@concealed>
  • To: "Serge Aumont" <address@concealed>
  • Cc: "address@concealed" <address@concealed>
  • Subject: [sympa-users] RE: FERPA, witness protection and toatl non disclosure users
  • Date: Thu, 8 Feb 2007 10:53:41 -0500

Ahh... I never thought of that - the simplest way is to only allow owners to
see the subscription lists. After adding this include scenario I would then
make all the non-owner only review scenarios to invisible and set the
default to equal the owner only one. Thanks for the info.

---
Chris Andrews
Boston College
Collaboration Team


-----Original Message-----
From: Serge Aumont [mailto:address@concealed]
Sent: Wednesday, February 07, 2007 3:18 PM
To: Chris Andrews
Cc: address@concealed
Subject: Re: [sympa-users] FERPA, witness protection and toatl non
disclosure users

Chris Andrews a écrit :
> We have a number of users that are marked as total non-disclosure users
here
> at Boston College. It would be nice to be able to flag a user globally as
> only visible to list owners. I know a user can go in on a list by list
> basis and set this flag, but that could be time consuming and in the mean
> time we violate FERPA.
>
> I could write a script that would look those users up and then using a SQL
> command change all the non-disclosure people to visibility_subscriber =
> "conceal", but that would leave the email address visible for a short
time.
>
> I could create a database trigger, but I am not that l33t in SQL and I
would
> rather not do that.
>
> I could add something to the add a subscribe routines in Sympa to make the
> change if the user was non-disclosure, does any one know where in the
Sympa
> code I should look to add this functionality?
You can block anyone except the list owners to review subscribers by
adding a new scenario rule to any review scenario. Just create a file
named include.review.header with the following rule :

!is_owner([listname],[sender]) smtp,md5,smime -> reject

This rule will be applied first to any scenario.

Where to locate this file ? This is described here :
http://www.sympa.org/wiki/manual/authorization-scenarios#location_of_scenari
o_file

Serge Aumont

Attachment: smime.p7s
Description: S/MIME cryptographic signature




Archive powered by MHonArc 2.6.19+.

Top of Page