On Wed, 29 Nov 2006 10:10:58 +0200, "Leon Kolchinsky" <[EMAIL PROTECTED]> 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? >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 As far as I am aware any setting changes in the local.cf need a restart of spamd. Whether or not amavis does this for you I don't know. I do recall someone recently mentioning that the Amavis doesn't give enough time and/or wait for the return from spamd. Though this may not be at all related to your issue. For a simple test. Make a change and manually restart spamassassin, then undo the change, restart just amavis and see if amavis picks it up? HTH Kind regards Nigel
