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? 2) For every change in local.cf should I do now only "amavis restart" and no "spamd restart"? Regards, Leon -----Original Message----- From: Mark Martinec [mailto:[EMAIL PROTECTED] Sent: Sunday, November 26, 2006 10:54 PM To: users@spamassassin.apache.org Subject: Re: optional score in local.cf is not working On Sunday November 26 2006 20:25, Matt Kettler wrote: > >> Erm.. are you sure? I thought amavisd-new called SA directly at the API > >> layer, not via spamd... > I didn't even realize amavis *could* use spamd, every amavis person I've > talked to on the list isn't using it. amavisd-new can't call spamd, there is no configuration option to do so, and no code to support it. spamc/spamd could be used (if desired/needed) by implementing the usual SA standalone setup, and disabling spam checking in amavisd. Mark
