On Jan 19, 8:39am, Dave Wolfe wrote:
}
} [ Bill Houle writes: ]
} > ! and restrict_post authorizations. If the moderator address
} > ! is not set, it will default to the 'sender' in the config
} > ! file. If 'sender' is not defined, the mail will be sent to
} > ! the list-request address (usually the owner).
}
} While this is exactly what the code does, I think it's rather
} dangerous given that the -request address is usually set to either the
} request-answer script or majordomo with the -l option. Shouldn't it
} resort to list-owner instead?
Yeah, I was scratching my head when I saw that. What if the path was
instead: moderator, else -approval, else owner?
This would allow for:
list owner does all
-approval alias to owner
moderator unset
list owner gets bounces, approver does subs & posts
-approval alias goes to user X
moderator unset
list owner gets bounces, approver does subs, moderator does posts
-approval alias to user X
moderator set to user Y
The latter would support three levels of admin (owner, approver,
moderator) and still default to the owner when not used.
--bill
|
|
