sieve vs amavis for spam filter rules

[Henning]

Sieve and Amavis are designed for different purposes: Filtering/sorting
and spam filtering.
Using amavis/spamassassin for spam filtering has the advantage that it
has some learning-features, so it gets better the longer you use it
(network checks (razor, pyzor, dcc), BayesDB).

Additionally you can write custom rules
http://wiki.apache.org/spamassassin/WritingRules

There is a nice spamassassin plugin for roundcube, which allows
user-level configuration.

My advice: sort with sieve, filter spam with amavis.

Henning

Am 20.03.2014 20:01, schrieb Sruli Saurymper:
> Hi,
> 
> I created a rule in Amavis for all emails with a score 6.308> should be
> posted in the users Spam folder witht eh Spam Score in the subject, this
> works correctly the downside is I need to set post permissions for each
> users Spam folder, I was wondering if using Sieve would be a better
> option however I can't any docs / howtos on using Sieve in Kolab (i
> found in wiki but that’s from 2.4 or something I guess) using Sieve I
> set a global filter without needing manually to set for each user? if
> yes can someone point me to some docs on how to add a sieve filter in
> Kolab?
> 
> 
> Thanks
> Sruli
> [Kolab 3.1]
> 
> _______________________________________________
> users mailing list
> users at lists.kolab.org
> https://lists.kolab.org/mailman/listinfo/users