[jira] [Commented] (WHIMSY-233) New workbench to support mail moderation

["Sebb (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/WHIMSY-233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16735985#comment-16735985 ] 

Sebb commented on WHIMSY-233:
-----------------------------

Authorisation:
The existing moderator lists are maintained in ezmlm; all moderators get a copy of each request.
This is no longer wanted (only Whimsy should get the mails), so some other way must be found to do the auth.

I don't know if there is any formal process for determining who can moderate a specific list.
I assume that prospective moderators must be allowed to read the list. For most private lists this means PMC membership (or ASF membership).
This could perhaps be relaxed for public lists.
However moderators may need knowledge of the list topics to determine if a posting is on-topic or should be rejected.
It might be sufficient to restrict users to (P)PMC members and ASF members.

If further authorisation is needed, this would have to be decided and implemented somehow.


> New workbench to support mail moderation
> ----------------------------------------
>
>                 Key: WHIMSY-233
>                 URL: https://issues.apache.org/jira/browse/WHIMSY-233
>             Project: Whimsy
>          Issue Type: New Feature
>            Reporter: Sebb
>            Priority: Major
>
> Mail moderation sends the same email to each of the moderators, so they all have to scan all the mails. It would be a lot more efficient if each mail could be dealt with once.
> The suggestion is to implement this in Whimsy.
> The code could be derived from the Secretary workbench.
> This issue is to keep track of requirements etc.
> Functionality needs to include:
> - store mails for posts, subscriptions and reponses
> - show only unprocessed mails (and dynamically update the list)
> - Flag a mail as accepted (and/or allowed)
> - Reject a mail with a suitable message (templates would be useful here)
> - Flag a mail as spam (don't reject)
> - Accept a subscription request (check that the email address is in LDAP so can validate it)
> - authorise the moderator so they only process mails for lists they are allowed to see.
> Optionally:
> - detect mails that look like spam, e.g. they are very similar to ones already flagged



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)