[Licq-devel] Re: Antispam plugin

Hi,

Jon Keating schrieb:
> On Wednesday 05 September 2007 23:05, Florian Doersch wrote:
>> Currently I have some problems:
>> 1. SpamAssassin is not very useful as content filter, does somebody has
>> or can create one?
> 
> Not sure about this, but some user specified keywords might work? For example, 
> any Russian word will save lots of spam for me.
> 
I currently changed it to use a simple "special character counter" - 
works for most russian message ;) but a custom wordfilter would be 
simple to implement, I'll look at it. Also I have to filter the 
Auth-Request-Messages too

>> 2. The plugin likes to crash licq on fast messaging, perhaps someone has
>> an idea of changing the design.
> 
> Not quite sure what the current design is, but if the spam detection takes a 
> lot of time and blocks the plugin (if that is what you mean). You will most 
> likely need a new thread to handle the spam detection. This sounds like a 
> simple consumer-producer example.

The "new" solution does not need an extra program, and blocks the plugin 
  at maximum only for a second

> 
>> 3. I already get it to "ignoring message" in the console, but the
>> message appears to be sent to the gui before it reaches my plugin?
> 
> With the current plugin API, this is not really doable. Just curious, how do 
> you get the console to ignore the message? What happens is that the daemon 
> pushes the message to all registered plugins in an unspecified order. So they 
> all end up getting their own pointer, which means one plugin can not alter 
> the event for another plugin.
> 
> What all this means is that the current API was not meant for this kind of 
> plugins. Fortunately, a new API version is being worked on that will be able 
> to support the spam plugin. The bad news, is that development is going 
> slowly. Things will pick up once I finish a paying project that is eating up 
> all my spare time at the moment...

I know - you have to change the plugin-order, so that the antispam 
plugin is "Number One". Then it gets the Event first and can delete it 
before the other plugins get them from the daemon.

> 
>> (P.S you can write to me on german too ;) )
> 
> aber, Ich spreche nicht Deutsch. :)
> 
Schade :)

Florian