sieve vs amavis for spam filter rules

[Christian Hügel]

As far as I know you cannot set a global sieve rule for ex. spam mails.
Either you use a shared spam folder [1] or have a spam folder per user.
I have chosen to use a spam folder for each user like:

INBOX
-->SPAM
-->SPAM/Ham
-->SAM/UnknownSPAM

This folders can easily (auto)created from /etc/kolab/kolab.conf

Thus, I can train spammassin with this script [2]

To automatically create a sieve rule for each user I have written a
script which
extracts all valid mailboxes from kolab and if there's no sieve spam
rule it will create it.
The script needs a little more tweaking so I'll share it in a couple of
days.

Kind regards,

Christian

[1] http://docs.kolab.org/administrator-guide/combating-spam.html
[2] http://www.pollux.franken.de/en/mail-server-tools/sa-learn-cyrus/

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

-------------- n?chster Teil --------------
Ein Dateianhang mit Bin?rdaten wurde abgetrennt...
Dateiname   : signature.asc
Dateityp    : application/pgp-signature
Dateigr??e  : 901 bytes
Beschreibung: OpenPGP digital signature
URL         : <http://lists.kolab.org/pipermail/users/attachments/20140320/754af523/attachment.sig>