/etc/cron.daily/spamassassin should restart amavisd
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
spamassassin (Ubuntu) |
Triaged
|
Wishlist
|
Unassigned |
Bug Description
Binary package hint: spamassassin
/etc/cron.
I noticed this today after the sa-update run installed a new version of 72_active.cf to fix the notorious FH_DATE_PAST_20XX bug. Mails were still tagged like this:
X-Spam-Status: No, score=2.686 tagged_above=2 required=5
This happens when you run SpamAssassin through Amavis (package amavisd-new) because the amavisd processes seem to need a restart to use the updated rules.
Since the cron job knows if there are indeed updates, it is probably the best place to trigger this restart. Probably with something like this:
# Reload
if which invoke-rc.d >/dev/null 2>&1; then
invoke-rc.d spamassassin reload > /dev/null 2>&1
if [ -f /var/run/
invoke-rc.d amavis restart > /dev/null 2>&1
fi
else
/etc/
if [ -f /var/run/
fi
fi
I'm using /var/run/
Changed in spamassassin (Ubuntu): | |
importance: | Undecided → Wishlist |
status: | New → Triaged |
Maybe a restart isn't such a good idea for amavis, to kill off every child and restart at every change (could be a problem on systems under heavy load), maybe a reload would be enough (if it supports reload).