Anti-spam Strategies: Difference between revisions
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
{{Article Infobox|{{admin}}|{{ZCS 8.0}}{{ZCS 7.0}}|||}} | |||
== For SpamAssassin and Anti-spam Updates == | |||
== '''This page is currently a draft and in the process of being developed.''' == | == '''This page is currently a draft and in the process of being developed.''' == | ||
=== Customizing SpamAssassin === | === Customizing SpamAssassin === | ||
Revision as of 20:58, 30 August 2013
 Article Information |
|---|
| This article applies to the following ZCS versions. |
For SpamAssassin and Anti-spam Updates
This page is currently a draft and in the process of being developed.
Customizing SpamAssassin
ZCS 8.0.5 and later
For ZCS 8.0.5 and later, SpamAssassin scans for all *.cf files in /opt/zimbra/conf/sa and loads them in alphabetical order. If you create a sausers.cf file, it will be loaded after salocal.cf is loaded. This is the supported method for doing customizations of SpamAssassin.
ZCS 7.2.5 and later
For ZCS 7.2.5 and later, SpamAssassin customizations go in /opt/zimbra/conf/sauser.cf. On upgrade from ZCS7 to ZCS8, that file gets moved to /opt/zimbra/conf/ca
amavisd.conf.in:$sa_userprefs_file = '/opt/zimbra/conf/sauser.cf'; </quote>'
Customizing Postfix
Customizing Postfix using the "zmprov ms ..." method survives upgrades. On plain (non-Zimbra) Postfix servers, it is helpful to use certain Postfix restrictions not configurable using the Zimbra administration console. It is both permissible and the recommended way now to perform such customizations, for example:
zmprov ms <server> +zimbraMtaRestriction reject_unknown_reverse_client_hostname
