Email started on UNIX, so obviously these days there is alot of code
available for processing/filtering/etc... email. I'd like to be able to
use some of this stuff with evolution. Take SpamAssassin for instance.
I'd like to write a perl script that uses the ::SpamAssassin module and
have it exit with a 1 or 0 depending on if the message is spam or not,
evolution could then file the message or delete it. 

That is a simple example of a rule that uses the output of a shell
command to determine whether a given email filter/rule is true or not.

I could also imagine a more complex interaction allowing more fine
grained 'procmail' like features. But if I just had the ability to
create a filtering rule in evolution that took the output of a shell
command to determine whether the rule was true or not, I think it would
greatly extend the usefulness of evolution without requiring people like
me to use a combination of fetchmail and procmail to filter our email
before delivering it to Evo (which is the point of having a powerful
pop3/ldap MUA anyway... right?)

I am not on this list so please insure that all replies include my 
address: [EMAIL PROTECTED]

-ryan
-- 
Humans are the unfortunate result of a local maximum in the
fitness landscape.

www.ryanmarsh.com


_______________________________________________
evolution-hackers maillist  -  [EMAIL PROTECTED]
http://lists.ximian.com/mailman/listinfo/evolution-hackers

Reply via email to