Zimbra Forums

Hello.

We got a web based server and almost 400 web-client mailboxes running. The spam kill/tag rate is ok and all... but, we have one user - coincidentally the company owner - that wants to do his own sorting of spam.

I wonder if there is a way we can customize spam filter only for his mailbox, so he doesn't have to obey the kill/tag rule?

Thanks a lot!

anyone? please...

Zimbra doesn't support this directly, though they did add support for per-user white/blacklists in 6.0.
We added a customized spam filter (per-user whitelist/blacklist, kill threshold, tag threshold) using Amavis's built-in support for storing user preferences in MySQL. You can store site-wide defaults, domain defaults, and individual user settings in MySQL. It just takes a simple addition to /opt/zimbra/conf/amavisd.conf.in to enable it (@lookup_sql_dsn directive), but you also need to write an interface so users can change their preferences. We did it with a Zimlet, but could be an external web site too.
These links have more information on Amavis's MySQL support:
http://www.ijs.si/software/amavisd/README.sql.txt

http://www.ijs.si/software/amavisd/README.sql-mysql.txt
Ron

It's interesting you implemented this in Mysql and even wrote a zimlet to manage it. All of the amavis attributes are supported on a per account limit (ZCS 5/6) and domain (ZCS 6) levels.
ZCS 6.0 added webclient preferences to manage the per user white/black lists directly but the admins can modify any of the attributes.
krag_maga: you can set kill/tag levels per user via zmprov


zmprov ma account@domain.tld amavisSpamKillLevel 3.5

or to bypass completely

zmprov ma account@domain.tld amavisBypassSpamChecks TRUE

[QUOTE]

zmprov ma account@domain.tld amavisSpamKillLevel 3.5

or to bypass completely

zmprov ma account@domain.tld amavisBypassSpamChecks TRUE[/QUOTE]
This would have been nice to know last year when we first started hosting Zimbra!
krav_maga, you might find this particular thread helpful:
http://www.zimbra.com/forums/administra ... ering.html
Specifically, the list of available amavis attributes is in:
/opt/zimbra/conf/attrs/amavisd-new-attrs.xml
In any case, it isn't accessible to the end user, except for the whitelist/blacklist in 6.0, so writing the Zimlet and replacing the line in amavisd.conf.in after upgrades was well worth it. Now that I know these attributes are available via SOAP we may have to consider moving away from the MySQL version.