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.
Richard Draves wrote:
> One way would be to make the "posters' a totally restricted (for
> posting) list of itself, with an owner (the same) etc.
> Then the 'owner of posters' could remotely update the 'posters' list.
>
> Allan P. Magmanlac wrote:
>
>> One more thing that I forgot to ask. How can I configure the list so
>> that the list owner (not the majordomo admin) can add members to the
>> "posters" file.
>>
>> Allan P. Magmanlac wrote:
>>
>>> Thanks guys, actually this is my setup however during the test, i
>>> have 2 similar entries configured (1 in member list and 1 in the
>>> posters list) and so it messed up my testing.
>>> All is ok now.
>>>
>>> Dean Mail wrote:
>>>
>>>> " ... Is is possible for a list be modified to allow
>>>> "user@example.com" to send to the list but not be on the list of
>>>> recipients, or be returned if a "Who" command is done on the list?
>>>> ..."
>>>>
>>>> In your Majordomo lists directory, add a file (or create a list)
>>>> called "posters" (or call it whatever you'd like).
>>>>
>>>> Put user@example.com in that file.
>>>>
>>>> In your config file for the list to which you want user@example.com
>>>> to be able to post, add "posters" (or whatever you've named it) to
>>>> the "restrict_post" variable.
>>>>
>>>> -- Dean
>>>>
>>>>
>>>
>>
>
--
--
Allan P. Magmanlac
allan.magmanlac@nrns.ca
NRNS Incorporated
DREnet Network Coordination Centre (NCC)
Tel: (613) 599-7860 ext 107
Follow-Ups:
References:
|
|
