The mailing list for listmasters using Sympa

[Steven Peterson <address@concealed>]

Olivier,

Thanks!  I will work on setting up a test for next week. 

When you say that the search scenario now only takes one parameter, I am 
guessing that you mean we would add an authorization scenario entry like:
   search(myfilter.ldap)      smtp,smime,md5    -> do_it

Then create a filter that knows about the context variables, like:
   host       ...
   suffix       ...
   filter        (&(canonic_mail = [sender])(ListAllow = [listname]))
   scope        ...

Am I on the right track?

- Steve


Olivier Salaün - CRU wrote:

> Steven,
>
> The current restriction regarding available parameters does not make 
> sense ; in the end the full scenario context should be made available 
> to search filters. I did a quick hack in the MAIN CVS to allow use of 
> a few basic variables including [listname] but not all of them 
> ([env.xx], etc) because we need to factorize some code.
>
> We will make a tarball of sympa-5.3a.1à on monday ; if you can't wait, 
> then do a "cvs export".
>
> Note that the search() scenario rule now only take a single parameter.
>
> Steven Peterson wrote:
>
> > I am setting up Sympa to work with an external application so that 
> > the external application  decides whether someone is able to 
> > subscribe to a list.  My plan was to use an LDAP filter in an 
> > authorization scenario, but am finding that I can only pass the email 
> > address of the sender to the filter.  Is there anyway to send 
> > parameters other than the email address to the LDAP filter  (e.g. the 
> > list name)?  I am anticipating several hundred lists each with its 
> > own criteria for joining and my solution was to have the LDAP 
> > directory know about who can join which list.  If I cannot pass the 
> > list name to the filter, I am afraid I will have to have a different 
> > filter for each list.  Is there some solution that I am overlooking?