Developers of Sympa

[address@concealed]

Maurice Massar a écrit :
> > Not true : this is not hardcoded but configured in a scenario named invite.xxx where xxx is what 
> > you apply to the list configuration. You may change it going to the list admin menu > privileges 
> > then eit the invite section. Remeber that if you modify or create a scenario, you must restart 
> > sympa or touch (change the date) of the list config file.
> >     
>
> not quite..
>
> consider a list to:
> add closed
> invite owner
> subscribe auth_owner
>
> Now, an listowner loggs in to the web-interface and invites some user
> (hmm.. ignoring the fact that there is no invite button in the
> web-interface, and the forbidden "add" button is still there):
>
> 1) authenticated owner tells sympa to invite address@concealed
> 2) sympa sends a mail to address@concealed containing:
>      $command = "auth $keyauth sub $which $comment";
> 3) address@concealed replies to sympa with this token
> 4) sympa sees the list is configured to auth_owner and send to owner:
>      'keyauth' => $list->compute_auth($sender,'add')
> 5) owner issues add with corresponding token
> 6) sympa sees the list is configured add.closed and denies the request.
>
>   
Ok, now I understand your need : you want add command to configured in a 
way that allways respect OPT-IN (ie a chalenge is sent to the person who 
is added to the list).

I added a feature request in sympa web system