Skip to Content.
Sympa Menu

en - Re: [sympa-users] selective moderation

Subject: The mailing list for listmasters using Sympa

List archive

Chronological Thread  
  • From: Olivier Salaün <address@concealed>
  • To: Marc Meurrens {HMp} <address@concealed>
  • Cc: address@concealed
  • Subject: Re: [sympa-users] selective moderation
  • Date: Mon, 05 Oct 2009 11:52:10 +0200

Hi Marc,

That's an interresting topic you raise and it sounds like a usefull feature indeed, therefore I suggest that you submit a feature request to keep track of this in <http://sourcesup.cru.fr/tracker/?group_id=23>.
Please detail your use case, along with how Yahoo feature works. Maybe Roger can complete with a description of Mailman's 'postblock" option.

Now let's see how you can manage with a current Sympa version :
  1. split your list: your idea works well, except that you can manage to send messages to list Z only; lists M and A being used for subscription only. The advantage of sending messages to list Z is that you have messages in a single list; you just need to create a custom send.privatebutmoderatefromlistm authorization scenario, based on send.private scenario. The scenario will have one rule for list M members that looks like this : is_subscriber('listM',[sender]) smtp,dkim,smime,md5  -> editorkey. The mail drawback of this solution, is that having 3 lists instead of one may make usual operations like subscribing, sending, unsubscribing, more complex from the user's perspective.
  2. adding a custom "unmoderate" DB field to subscriber table: this would use the additional_subscriber_fields sympa.conf parameter, see <http://www.sympa.org/manual/conf-parameters/part3#db_additional_subscriber_fields>. This solution has a couple of drawbacks :
  1. standard Sympa DB needs to be extended;
  2. this automatically applies to all mailing list on your server;
  3. the new subscriber option is not used, untill you customize the authorization scenarios;
  4. the new "unmoderate" member option can be edited by listowner, from the user editsubscriber page, but it will be a text input, not a checkbox.
custom_attributes: Sympa provide so-called custom attributes that can be defined on a per-list basis, see <http://www.sympa.org/manual/customizing#custom_attribute>, but it lacks a way to allow provisioning to list owners only.

Marc Meurrens {HMp} a écrit :
address@concealed"> Hello all,

I am trying to solve the following problem using Sympa 5.3.4
(may be the problem is solved in version 6 and I just have to wait ?).

Suppose we have a private working group (no access to the public)
with a few owners, a few moderators (editors), 100 serious subscribers
(but not serious enough to become editors)
and 100 less serious subscribers that need to be moderated.

Is it possible to moderate some of the users but not all?
Obviously the current answer is "no".

This is however a request from people I convinced to leave
the Yahoo stuff (where selective moderation is possible)
as to reach a more respectuous service/software.

===

The only solution I found until now to satisfy them
is not really nice :

- a list M, moderated, with subscribers m1, m2, m3
- a list A, not moderated, with serious subscribers a1, a2, a3 + the list M
- a list Z, where no message may be posted, including M and C, thus m1,m2,m3,a1,a2,a3

when m1 posts to M, the message is moderated. If the message must
be accepted, the editor MUST TRANSFER MANUALLY the message to list A
and, btw, specify in some way (e.g. a CC) that the original author is m1.
the message will then also reach list M (but without a reference to
the original author m1)

when a1 posts to A, the message is sent to M automatically
BUT m1,m2,m3 will ignore that the original author is a1
and will thus not be able to reply directly to a1 if needed.
THIS IS A REAL PROBLEM.

hopefully, archives are nearly identical on A and M,
except of course the matter of the original author.

list Z is only devoted to hold the shared documents
assuming that both the serious and the less serious
subscribers have the same rights.

===

Any idea?
Any project to build a better solution?




Archive powered by MHonArc 2.6.19+.

Top of Page