Hi all,
The installation for spamassassin suggests to run sa-update from a cronjob regularly to update the spamd with new rules once in a while, however, the manual for sa-update says the following:
I've installed spamassassin version 3.3.1 using the spam.sh script as found in /usr/local/directadmin/scripts but this changes only /etc/init.d/exim startup script. I'm running debian 5.0.
As the exim reload command only reloads exim and not spamd this doesn't work either.
I think either the exim init script should be changed or a separate spamassassin script should be used which uses the --pidfile= option of spamd so we can do a kill -HUP to that pid on reload (spamd supports this).
What would be directadmin supported way of doing this?
The installation for spamassassin suggests to run sa-update from a cronjob regularly to update the spamd with new rules once in a while, however, the manual for sa-update says the following:
Note that "sa-update" will not restart "spamd" or otherwise cause a scanner to reload the now-updated ruleset automatically.
Instead, "sa-update" is typically used in something like the following manner:
sa-update && /etc/init.d/spamassassin reload
I've installed spamassassin version 3.3.1 using the spam.sh script as found in /usr/local/directadmin/scripts but this changes only /etc/init.d/exim startup script. I'm running debian 5.0.
As the exim reload command only reloads exim and not spamd this doesn't work either.
I think either the exim init script should be changed or a separate spamassassin script should be used which uses the --pidfile= option of spamd so we can do a kill -HUP to that pid on reload (spamd supports this).
What would be directadmin supported way of doing this?