Skip to Content.
Sympa Menu

en - [sympa-users] Re: Re: Re: Re: Spam in suscribe and unsuscribe mail recipients

Subject: The mailing list for listmasters using Sympa

List archive

Chronological Thread  
  • From: Héctor Garcia Peris <address@concealed>
  • To: address@concealed
  • Cc: address@concealed
  • Subject: [sympa-users] Re: Re: Re: Re: Spam in suscribe and unsuscribe mail recipients
  • Date: Wed, 10 Jan 2007 10:46:28 +0100



address@concealed wrote:
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

Summarizing, I can add rules in subscribe and unsubscribe scenarios to prevent spam, but I can use this rules in list-request, list-editor, list-owner or address@concealed mail recipients. Is this ok?

But I think it's possible modify perl programs to prevent this. It could be in DoCommand or DoForward functions.

Another thing, is it possible that sympa doesn't answer to the sender if there isn't any command in a mail? This could solve this.

Thanks.

---------------------------------------------------------------------
Héctor Garcia Peris
Dpto. Informática
Instituto Valenciano de Investigaciones Económicas S.A. (Ivie)
C/ Guardia Civil, 22 esc-2 1º 46020 - Valencia (Spain)
Tfno.: +34 - 963190050 / +34 - 963930816
Fax.: +34 - 963190055 / +34 - 963930856
e-mail: address@concealed
Web: http://www.ivie.es
----------------------------------------------------------------------



Archive powered by MHonArc 2.6.19+.

Top of Page