>We use this for our customers all the time. We create a file in the
>lists directory called "listname.mod" (with "listname" being the name
>of the list), then we put listname.mod on the restrict_post line of
>the list's config file. Then the addresses in the mod file can post
>without approval while all others are bounced.
>
>However, this can only be set up by someone who has majordomo admin
>privs and can create and edit files in the lists directory. If you
>don't have those privs, you'll have to ask those who do to set up the
>mod file for you.
>
>And the actual file name is up to you. We chose listname.mod to
>signify it was sort of a list of 'moderator' addresses.
>From a post earlier (sorry lost the author address):
==================================================================
Q. I'm runninng my lists with restrict_post and have a list.config entry
like:
restrict_post: list list-digest list-posters
where list-posters is a list of alternate IDs for list subscribers.
I'd like to be able to maintain the list-posters file via EMail. How can
I do
that?
A. Create another list for list-posters. Make the list closed and not
advertised. Set up your list-posters aliases like:
list-posters:nobody
list-posters-approval:nobody
owner-list-posters:nobody
(where nobody is /dev/null)
Then you can do
approve list.passwd subscribe list-posters someone@somewhere.com
to maintain the alternate subscriber information.
==================================================================
Follow-Ups:
References:
|
|
