Hi,
OK.
I did some manual tests and indeed changes in local.cf only catching then I
restart amavis.
# /etc/init.d/amavis restart
Shutting down virus-scanner (amavisd-new):Daemon [9905] terminated by SIGTERM
done
Starting virus-scanner (amavisd-new):
done
When I restart only spamd no change in local.cf is catching.
I don’t really understand why?
Mark Martinec said that "amavisd-new can't call spamd"
So, let me get this straight:
-----------------------------
This is how I see the work of amavis+spamd+clamd:
1. As I see it amavis talk to spamd (spamassassin) and clamd (ClamAV) via
appropriate sockets or TCP ports.
In my case -
To clamd via /var/lib/clamav/clamd-socket (I can see it in amavisd.conf)
To spamd ? (I don't know how to check it)
2. Any configuration change I make to clamd and spamd take power only when I
restart the deamons themselves.
3. But according to Matt Kettler response and my testings, any change to
local.cf require amavis restart.
# /etc/init.d/amavis restart
Shutting down virus-scanner (amavisd-new):Daemon [9905] terminated by SIGTERM
done
Starting virus-scanner (amavisd-new):
done
What is going on?
Where I can validate config options of amavis to make sure the way it works?
P.S.:
This is taken from /etc/init.d/amavis:
--------------------------------------
AMAVISD_BIN=/usr/sbin/amavisd
AMAVIS_MILTER_BIN=/usr/sbin/amavis-milter
echo -n "Starting virus-scanner (amavisd-new):"
$AMAVISD_BIN start
if ! checkproc amavisd; then
rc_failed 7
fi
rc_status -v
if [ "$AMAVIS_SENDMAIL_MILTER" == "yes" ]; then
rc_reset
echo -n "Starting amavis-milter:"
startproc -u vscan $AMAVIS_MILTER_BIN -p
local:/var/run/amavis/amavis-milter.sock > /dev/null 2>&1
rc_status -v
This is taken from /etc/init.d/spamd:
-------------------------------------
# Short-Description: Start the spamassassin daemon
SPAMD_BIN=/usr/sbin/spamd
PIDFILE=/var/run/spamd.pid
startproc -p $PIDFILE $SPAMD_BIN $SPAMD_ARGS -r $PIDFILE
This is taken from /etc/amavisd.conf:
-------------------------------------
@av_scanners = (
### http://www.clamav.net/
['ClamAV-clamd',
\&ask_daemon, ["CONTSCAN {}\n", "/var/lib/clamav/clamd-socket"],
qr/\bOK$/, qr/\bFOUND$/,
qr/^.*?: (?!Infected Archive)(.*) FOUND$/ ],
-----Original Message-----
From: Nigel Frankcom [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 29, 2006 10:21 AM
To: users@spamassassin.apache.org
Subject: Re: optional score in local.cf is not working
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
