Or to get to the original (I think) plan to allow posters ONLY and not
have the list members able to send:
restrict_post: LISTNAME-posters
Now ONLY those on the LISTNAME-posters list can send (post) to the
LISTNAME list. And the LISTNAME-posters is remotely managable.
Roger B.A. Klorese wrote:
> Allan P. Magmanlac wrote:
>
>> It would create then a totally different list and this is not what is
>> intended as there should only be one list with other people who can
>> only post to the same and one list.
>>
>
> You're thinking too narrowly. You're thinking "list == a set of
> addresses to which mail can be sent." We're telling you that "list ==
> a set of addresses that can be managed using the Majordomo software,
> and, if proper aliases are set up, to which mail can be sent." Note
> the "if" portion. Don't set up the aliases (other than the -owner and
> owner- aliases), and no mail can be sent to this list -- it just
> becomes a file that can be managed remotely using the Majordomo
> software so you don't need shell access to the server. Than you list
> that "list" name in the restrict-post line of your real list.
>
> restrict_post = LISTNAME:LISTNAME-posters
>
> You're being incredibly resistant to this, and yet, it's how it's been
> done for years.
--
Have a good day!
Dick Draves
Systems Administrator
Bard College
(845) 758-7119
Follow-Ups:
References:
|
|
