Launching a perl process that does alot of searching and evaluating for
every message that comes in could get expensive.
It should be possible to embed a perl interpreter into the code.
You could enter an expression into a field, like the scheme expression
in 1.08 that I've seen, that is to be evaluated for every message that
comes in. The expression is evaluated into an 'anonymous subroutine'
(perlism) that is executed on every message.
An internal perl function could be provided that would 'get' the
message text, or the headers, or whatever is available in the Evolution
internals.
A startup file in the evolution directory could load any Perl libs
(such as Mail::Audit and Spam Assassin) that might be desired for
processing incoming messages.
On Fri, 2002-08-30 at 10:31, Johannes Berg wrote:
> > Has anyone added a perl interpreter into Evolution? I would like to use
> > perls "Spam Assassin" module to filter spam.
> >
> > If no one is currently taking this on, I'd like to get a CVS snapshot of
> > the code and see about embedding the perl interpreter myself.
>
> Maybe the "filter to external program" could be extended to allow for
> return values that trigger other actions (*) (unless, of course, it
> already does, I'm not familiar with the current CVS)
>
> (*) I could envision that the program sets a return value other than 0,
> and outputs something like this on stdout/stderr:
> MOVE TO <folder>
> DELETE
> COPY TO <folder>
> COLOR <color>
> STATUS <status>
> SCORE <score>
> etc for the current filter actions
>
> johannes
>
>
_______________________________________________
evolution-hackers maillist - [EMAIL PROTECTED]
http://lists.ximian.com/mailman/listinfo/evolution-hackers
