The mailing list for listmasters using Sympa

[Liam Kirsher <address@concealed>]

David,

I actually already had implemented this, as it turned out.
In /home/sympa/etc/scenari/send.private --
> title.gettext restricted to subscribers
>
> match([header->X-Spam-Flag],/YES/) smtp -> reject,quiet
> is_subscriber([listname],[sender])             smtp,smime,md5    -> do_it
> is_editor([listname],[sender])                 smtp,smime,md5    -> do_it
> is_owner([listname],[sender])                  smtp,smime,md5    -> do_it
However, I still noticed a lot of messages in the spool directory that
were marked as spam, including the one referred to in the earlier email
that was apparently causing Sympa to crash.
http://address@concealed

Maybe that was all okay, after all -- Sympa was going to quietly reject
the spam messages, but had to parse the headers first, and that's the
point when it choked on the bad header chars.

I do still get some backscatter but on closer look, it's not spammers
sending messages to the lists (probably due to the scenario above) but
rather spammers sending messages to sympa-request that Sympa tries to
interpret as commands.  So... which are the other ones I should filter
spam for, if spammer sends mail to address@concealed?

Is there someplace to put it for all the requests, or do I need to do it
for each one:
subscribe.open
unsubscribe.open
etc.

Liam


David Verdin wrote:
>>  
> Don't be afraid. Scenarios are your friends. They are good to you and
> your users. ;)
> Anyway, you can use your scenarios to automatically and silently
> dismiss any mail marked as spam by yous spam filter. Just look at the
> syntax in the doc, it's all there.
>> It's the spammers that are sending the messages that crash Sympa, in
>> this case.  Also I don't feel like I want Sympa taking CPU cycles to
>> process spam when it really shouldn't have to.
>>   
> You can save some of Sympa energy by splitting it in two processes,
> one used to analyze any incoming message, and another to distribute
> message to lists.
> That way, charge has a better repartition.
> This can be done by setting the sympa.conf parameter named
> "distribution_mode" to the value "fork".
>
> Regards,
>

-- 
Liam Kirsher
PGP: http://liam.numenet.com/pgp/