On 11/25/2014 01:05 PM, Barry Warsaw wrote:
>
> I think this does work differently in MM2.1, but that version's schema isn't
> really sophisticated enough to do anything different. There, members have a
> moderation flag which gets initialized from default_member_moderation. Then,
> if the membe
On Nov 25, 2014, at 11:46 AM, Aurelien Bompard wrote:
>As a result, unless I'm missing something changing, the list's
>default_moderation_action has no effect on existing members. Do I
>understand correctly?
That is correct. As Steve points out, the intent is that this setting is
initialization
On 11/25/14, 5:46 AM, Aurelien Bompard wrote:
Hi *,
I'd like to discuss the algorithm we use to enforce a list's default
moderation action. Here's what I understand:
- the list's default_moderation_action setting is stored in the database
and can be changed via the REST interface
- when a new me
Aurelien Bompard writes:
> I suggest we leave the member's moderation_action on None when it's
> created, and modify the moderation rules to go look for the list's default
> setting if the member's value is None.
I think this is a bad idea. From the subscriber's perspective, it
changes the li
Hi *,
I'd like to discuss the algorithm we use to enforce a list's default
moderation action. Here's what I understand:
- the list's default_moderation_action setting is stored in the database
and can be changed via the REST interface
- when a new member is created, its moderation_action is import
