Hello,
I'm new here, so not sure if this is appropriate:
In regards to FAQ 3.27:
Am I the only one who would find it extremely helpful if duties could be better split? Certainly for large lists. That is:
Owners = who can determine the list's configuration Admins = who handle subscriptions and bounces Moderators = who handle list messages
If needed admin/mod could be combined as one.
Or alternatively, that you can specify an email address for each Notification?
The current problem is that in academic lists, the owner/sponsor of a forum often needs to be an University staff member, who however would delegate daily running to students etc (mods). But with Mailman, on a bad day, the poor Prof would get 70 messages per day (bounces, subscription, approvals, etc). It's not workable IMHO (I'm a mod BTW).
AFAICT in the present system, reducing mail to an owner can only be done by setting admin_immed_notify, bounce_unrecognized_goes_to_list_owner, bounce_notify_owner_on_disable, and bounce_notify_owner_on_removal, (and a few more) to NO, which is clearly not an ideal solution...well, no solution at all, really.
Any thoughts? Any chance of this duties seperation [i.e. owners are nót automatically mods], being implemented in future versions?
Best regards, Aayko
Since the messages have set forms, it should be "easy" to filter the various bounce and membership requests and route accordingly.
Not ideal, but as long as the ownership password(s) are not the professor's usual passwords, he should be able to delegate to an appropriate grad student (even if the professor insists on using his own email account...having all administration go to a delegated email account ... or a special forwarding account with filtered forwarding) is what I'd do in your situation.
Keith Bierman khbkhb@gmail.com kbiermank AIM 303 997 2749
On Tue, Sep 9, 2014 at 7:47 AM, A.K. Eyma ayma@tip.nl wrote:
Hello,
I'm new here, so not sure if this is appropriate:
In regards to FAQ 3.27:
Am I the only one who would find it extremely helpful if duties could be better split? Certainly for large lists. That is:
Owners = who can determine the list's configuration Admins = who handle subscriptions and bounces Moderators = who handle list messages
If needed admin/mod could be combined as one.
Or alternatively, that you can specify an email address for each Notification?
The current problem is that in academic lists, the owner/sponsor of a forum often needs to be an University staff member, who however would delegate daily running to students etc (mods). But with Mailman, on a bad day, the poor Prof would get 70 messages per day (bounces, subscription, approvals, etc). It's not workable IMHO (I'm a mod BTW).
AFAICT in the present system, reducing mail to an owner can only be done by setting admin_immed_notify, bounce_unrecognized_goes_to_ list_owner, bounce_notify_owner_on_disable, and bounce_notify_owner_on_removal, (and a few more) to NO, which is clearly not an ideal solution...well, no solution at all, really.
Any thoughts? Any chance of this duties seperation [i.e. owners are nót automatically mods], being implemented in future versions?
Best regards, Aayko
Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/ mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/ khbkhb%40gmail.com
On 09/09/2014 06:47 AM, A.K. Eyma wrote:
Any chance of this duties seperation [i.e. owners are nót automatically mods], being implemented in future versions?
I don't think this will happen in Mailman 2.1, but it is something we could consider for Mailman 3. It might get more attention if you post a proposal to mailman-developers@python.org.
-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mark Sapiro writes:
it is something we could consider for Mailman 3. It might get more attention if you post a proposal to mailman-developers@python.org.
"ACLs" or "capabilities" (cf. Linux kernel, origin maybe Plan 9?) for Mailman admin might be an interesting GSoC.
Note that at present our web interface (Postorius) for Mailman 3 is done in Django. It might be as simple as cooking up an ACL table in the database, and a permissions decorator with a bit of introspection to find the ACL for the view.
Steve
participants (4)
-
A.K. Eyma -
Keith Bierman -
Mark Sapiro -
Stephen J. Turnbull