Skip to Content.
Sympa Menu

en - Re: [sympa-users] Scenario for anti-spam, making sure it's right

Subject: The mailing list for listmasters using Sympa

List archive

Chronological Thread  
  • From: Aumont - Comite Reseaux des Universites <address@concealed>
  • To: address@concealed
  • Cc: address@concealed
  • Subject: Re: [sympa-users] Scenario for anti-spam, making sure it's right
  • Date: Wed, 16 Nov 2005 08:16:52 +0100

address@concealed wrote:
I want to create a send scenario that will allow members to post to a list and
non-members to be moderated, WITH THE EXCEPTION that any message the gateway
considers spam gets rejected outright. I based my new scenario off
send.privateoreditorkey. Here's what I've created so far:

title.gettext Private, moderated for non subscribers, rejects messages marked
{Spam?}

is_subscriber([listname],[sender]) smtp,smime,md5    -> do_it
is_editor([listname],[sender])	   smtp,smime,md5    -> do_it
match([header->X-nami-MailScanner-SpamCheck],/yes/) smtp -> reject
true()				   smtp,smime,md5    -> editorkey


Is this correct? 
It seems quite good but don't forget that rules are evaluated sequentially. So the rule that detect headers added by MailScanner should be the first one. Anoter remark : if headers look like "X-nami-MailScanner-SpamCheck: spam" the rule should no test "yes" but  "spam".
"match([header->X-nami-MailScanner-SpamCheck],/spam/) smtp -> reject"
At last remenber that scenario are loaded when the list configuration file are loaded. Sympa does NOT detect that a scenario file as changed so should have to restart Sympa when changing a scenario or just execute "touch config" where config is the configuration file are the related lists. Otherwise you will not test the scenario you have edited but a previous version ...

 Serge Aumont

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature




Archive powered by MHonArc 2.6.19+.

Top of Page