Leon Kolchinsky wrote: > Hi, > > I thought I was wrong and "amavis restart" didn't really helped there, but > there is an update for this problem I had with configuration in local.cf not > catching. > > It seems that only when I do /etc/init.d/amavis restart, all configs in > local.cf are coming intact. > > I've used to an old version of amavis and SA on Suse, where you would only do > changes to local.cf and "spamd restart". > > 1) So, my question is - Is this a normal behavior? > Yes. Because amavisd-new uses the API, restarting spamd should have no affect on it. I don't know why your old version ever used spamd, as it's highly inefficient for a perl application to do so instead of calling Mail::SpamAssassin. > 2) For every change in local.cf should I do now only "amavis restart" and no > "spamd restart"? > Yes.. and you should also change your system to not run spamd anymore.
Amavisd-new does not use spamd, so running it is a waste of memory.
