The mailing list for listmasters using Sympa

["Ward, Michael" <address@concealed>]

I must admit I read further through the scenario doco after posting the last 
email and came across the implicit scenario inclusion - however I don't think 
it quite covers the scenario I outlined below.

As you've mentioned, the implicit inclusion would be ok if you want all lists 
on a virtual host to include the custom scenario, or all but a few (using the 
empty include file). However in my case, I want to use the custom scenario on 
a handful of lists (3-4), so it's much less work to create a standalone send 
scenario and configure these lists to use that.

So I've setup the list as first suggested, is working fine. Thanks for your 
help.

Regards,
Michael Ward


-----Original Message-----
From: David Verdin [mailto:address@concealed] 
Sent: Tuesday, 16 October 2007 9:02 p.m.
To: Ward, Michael
Cc: sympa-users
Subject: Re: [sympa-users] RE: Re: Re: Advanced nested lists

Michael,

Ward, Michael a écrit :
> Ok thanks - that sounds like what I'm looking for.
>
> So if I understand correctly, I'd have to create an additional scenario 
> file with the addition you've outlined below, for every different send 
> scenario that the lists I want our helpdesk staff to send to are using?
>
> e.g:
> I have a list using send.private, I'd create send.privatehelpdesk
> I have a list using send.privateandeditorkey, I'd create 
> send.privateandeditorkeyhelpdesk
>
> I can't tell a list to use a 'base' send scenario then apply other scenario 
> files? I'm already pretty sure the answer is no, if not then it would be a 
> useful feature to have :-).
>   
We will do it in the future, so I time-traveled there this morning and 
brought it back to present. ;-)
More seriously: you can use implicit scenario inclusion, as documented 
there:
http://www.sympa.org/wiki/manual/authorization-scenarios#scenario_implicit_inclusion

These are scenario that are applied to any scenario of the same action. 
Please note that precedence apply, and then if you put your scenario 
inclusion file in a ~sympa/etc/your.virtual.host/scenari directory, it 
will be applied to all lists in this virtual host for this action, 
whatever scenario they are using.

If you want to apply the inclusion to all your lists except a few of 
them, this is by far the least effort-spending solution. For the lists 
for which you don't want to apply the scenario, just add an empty 
include file to their own scenari directory.

Regards,
> In the end though this if my assumptions above are correct it shouldn't be 
> a big problem for us. So far the only lists we have that need to be setup 
> like this are using send.private, so at this stage I'd only need to create 
> one new scenario.
>
> Regards,
> Michael Ward
>
>
> -----Original Message-----
> From: David Verdin [mailto:address@concealed] 
> Sent: Monday, 15 October 2007 10:28 p.m.
> To: Ward, Michael
> Cc: sympa-users
> Subject: Re: [sympa-users] Re: Re: Advanced nested lists
>
> I highlighted informations about the distinction between list inclusion 
> and foreign list subscribers authorization in Sympa's FAQ.
> See:
> https://www.sympa.org/wiki/faq/sub-list
>
> David Verdin a écrit :
>   
>> Warning : the previous mail went away before I could finish it. It's 
>> getting cold, back here, my hands must be shaking. ;)
>> This is what it should have contained actually :
>>
>> Nesting is used to add subscribers to lists. Scenario can't control 
>> who receive a message, they control who send them.
>> There is another solution : if you just want people from list B to be 
>> able to post to list A, just modify the "send" scenario from list A to 
>> allow subscribers fom list B to send.
>> This can be done by adding this line to the "send" scenario of list A :
>>
>> is_subscriber ("address@concealed", [sender])             
>> smtp,smime,md5    -> do_it
>>
>> This way, you don't need nested lists. The subscribers of list A will 
>> receive the message and not those of list B.
>>
>> Regards,
>>
>> David Verdin a écrit :
>>     
>>> Hi,
>>>
>>> Ward, Michael a écrit :
>>>       
>>>> Hi,
>>>>
>>>> Sympa version 5.3.2 on RHEL 5
>>>>
>>>> I know you can nest lists in Sympa by using the include_list parameter.
>>>> However I've been asked if it's possible to configure the list so that
>>>> the members of the nested list do not receive the messages sent to the
>>>> parent list?
>>>>
>>>> Ie:
>>>> - List B is configured as a nested list for List A
>>>> - Members of List B can post to List A, but do not receive the messages
>>>>
>>>> The scenario in question is intended to be used by our helpdesk to pass
>>>> emails onto other groups within our organisation, so they have to be
>>>> able to send to the lists restricted to members only, but do not 
>>>> want to
>>>> receive any messages sent to those lists.
>>>>
>>>> Is this possible? Or is there a better way to do this?
>>>>   
>>>>         
>>> There is another solution : if you just want people from list B to be 
>>> able to post to liste A, just modify the "send" scenario from list A 
>>> to allow subscribers fom list B to send.
>>> This can be done by adding this line to the scenario :
>>>
>>> is_subscriber (<listname>, <var>)
>>>
>>>       
>>>> Thanks
>>>> Michael
>>>>
>>>>   
>>>>         
>
>   

-- 
David Verdin
Comité réseau des universités