The mailing list for listmasters using Sympa

[address@concealed]

Héctor Garcia Peris wrote:
> address@concealed wrote:
> > Héctor Garcia Peris wrote:
> > > Hello,
> > >
> > > I noticed that arrives a lot of spam messages to suscribe and 
> > > unsuscribe mail recipients. I saw in the list a message that says a 
> > > way to remove lots of messages using:
> > >
> > > match([header->X-Spam-Level],/\*\*\*\*\*\*\*+/) smtp -> reject,quiet
> > >
> > > in the send.private scenari. This reject lots of spam messages 
> > > directed to mail list recipients, but not for suscribe, unsuscribe 
> > > or request mail recipients. How can I do something similar to this 
> > > kind of recipients?
> > I think you can allready do it for message to list-subscribe and 
> > list-unsubscribe : thoses messages are commands aand are performed 
> > exactly in the same way as command in message body. So you can test 
> > headers added by your filter server in the scenario subscribe and 
> > unsubscribe.
> >
> > This can't be done for message to list-request and list-editor.  The 
> > way we will do it is introducing a new scenario for message 
> > forwarded. This is already in the feature request.
>
> I don't understand it. I have various scenario files with the name 
> send.<something> that I don't understand what they do really. Must I 
> create scenario files with name forward.<something> or 
> request.<something> or editor.<something>? What must I write instead 
> of <something>?
Currently, scenario are not used for message to <list>-request and 
<list>-editor. Will introduce this feature in a futur Sympa version, but 
you can add rules such as  
"match([header->X-Spam-Level],/\*\*\*\*\*\*\*+/) smtp -> reject,quiet" 
in the scenario subscribe.XXX (where XXX is the value of the parameter 
subscribe in list config).

I have improved scenario documentation, check :  
http://www.sympa.org/wiki/manual/authorization-scenarios#scenario_implicit_inclusion
http://www.sympa.org/wiki/manual/authorization-scenarios#location_of_scenario_file