From my experience, you can modify the salocal.cf.in file directly and have your changes moved to the salocal.cf file after a Zimbra reboot.
However, note that some settings for spamassassin will be ignored b/c it is controlled by amavisd - for example, I found our that I cannot add new headers for DCC through salocal.cf. This took me quite a while to find out - so make sure read the sa and amavisd docs quite well when making changes, otherwise you might not get what you expect.
I know I've said this before, but if an sa, amavisd and Zimbra guru from the community could step forward and document things better, that would very greatly appreciated. |