Possible with workaround (see last comment).

workaround



file: ingo/config/prefs.php

line 66



i've it's the first installation you can add a anti-spam here

example:

     'value' => 
'a:5:{i:0;a:2:{s:4:"name";s:9:"Whitelist";s:6:"action";i:9;}i:1;a:3:{s:4:"name";s:8:"Vacation";s:6:"action";i:8;s:7:"disable";b:1;}i:2;a:2:{s:4:"name";s:9:"Blacklist";s:6:"action";i:7;}i:3;a:2:{s:4:"name";s:7:"Forward";s:6:"action";i:10;}i:4;a:8:{s:4:"name";s:8:"Antispam";s:7:"combine";s:1:"2";s:10:"conditions";a:1:{i:0;a:4:{s:5:"field";s:7:"Subject";s:4:"type";i:1;s:5:"match";s:8:"contains";s:5:"value";s:10:"+++SPAM+++";}}s:6:"action";s:1:"1";s:12:"action-value";N;s:4:"stop";s:1:"1";s:5:"flags";i:10;s:7:"disable";b:0;}}',



just get this out of the dbase after creating it with ingo on a testaccount



this one will filter all +++SPAM+++ titles and make them read&deleted 
(but visible on imap)

This would only be possible with a justifiable effort when we have a 
SQL backend for Ingo's filter rules.

Similar to how Whitelist and Blacklist are created for all users, 
there should be a way for the administrator to create other global 
filters for all users.  Any rule created by the administrator could be 
assigned a "locked" value which if set, would prevent the user from 
disabling the rule.    This would be a good way for an administrator 
to change spam filtering rules to the benefit of all users.