reassign 567205 spamassassin thanks *snip*
> xmail:/etc# find ./cron* -type f | xargs grep -li 'sa-update' > ./cron.daily/spamassassin > > ================================== > > xmail:/etc# cat ./cron.daily/spamassassin > #!/bin/sh > > # Duncan Findlay > # du...@debian.org > > # Daily cronjob for SpamAssassin updates. This isn't pretty but it > # should do the job. > > set -e > > CRON=0 > > test -f /etc/default/spamassassin && . /etc/default/spamassassin > > test -x /usr/bin/sa-update || exit 0 > test -x /etc/init.d/spamassassin || exit 0 > > if [ "$CRON" = "0" ] ; then > exit 0 > fi > > # Sleep for up to 3600 seconds > # Taken from apticron's cron.daily > RANGE=3600 > number=`od -vAn -N2 -tu4 < /dev/urandom` > number=`expr $number "%" $RANGE` > sleep $number > > > # Update > umask 022 > sa-update || exit 0 > > # Compile, if rules have previously been compiled, and it's possible > if [ -x /usr/bin/re2c -a -x /usr/bin/sa-compile -a -d > /var/lib/spamassassin/compiled ]; then > sa-compile > /dev/null 2>&1 > fi > > # Fixup perms -- group and other should be able to read and execute, > # but never write. Works around sa-compile's failure to obey umask. > if [ -d /var/lib/spamassassin ]; then > chmod -R go-w,go+rX /var/lib/spamassassin/ > fi > > # Reload > if which invoke-rc.d >/dev/null 2>&1; then > invoke-rc.d spamassassin reload > /dev/null 2>&1 > else > /etc/init.d/spamassassin reload > /dev/null 2>&1 > fi > > ================================== > > xmail:/etc# etc/init.d/spamassassin reload > bash: etc/init.d/spamassassin: No such file or directory > > ================================== > > what this seems to tell me is that sa-update is being called every day by > cron, but spamassassin and amavisd-new are not being reloaded in order to > utilize the update. > > what brings me to notice this issue is the recent spamassassin bug 6269 > (see https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6269) > > for spamhaters this bug causes dataloss as legitimate mail had an extra 3 > points added to the spam score. > > from what i understand, this bug was noticed and rectified on 2010/01/01, but > due to /cron.daily/spamassassin calling /etc/init.d/spamassassin reload > instead of /etc/init.d/amavisd-new force-reload, the sa-update updates were > never picked up by the running amavisd-new daemon. > > should i change the code in /cron.daily/spamassassin to call > /etc/init.d/amavisd-new force-reload, or is there a better way to accomplish > this? I don't think there is anything we (amavisd-new) can do there. So I reassign that back to spamassassin. They should initiate a restart. Maybe /etc/default/spamassassin should contain a list of services to restart. What do you think? Alex -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
