Updating spamassassin rules

(Has no effect unless SINGLE_EMAIL_ONLY is set) SA_LINT="/usr/bin/spamassassin --lint"; # Command used to lint the rules SA_RESTART="/etc/init.d/amavisd restart"; # Command used to restart spamd # May be /etc/rc.d/init.d/spamassassin restart # For amavisd, may be /etc/init.d/amavisd restart # For minedefang, may be /etc/init.d/mimedefang restart CURL_PROG="/usr/bin/curl"; # Location of the curl program CURL_OPTS="-w % --compressed -O -R -s -S -z"; # Parameters of the curl program CURL="$ $"; # Curl program with parameters WGET_PROG="/usr/bin/wget"; # Location of the wget program WGET_OPTS="-N" # Parameters of the wget program WGET="$ $"; # Wget program with parameters PERL="/usr/bin/perl"; # Location of the perl program GREP="/bin/grep"; # Location of the grep program TAIL="/usr/bin/tail -n 1"; # Location (and parameters) for 'tail -n 1' HEAD="/usr/bin/head -n 1"; # Location (and parameters) for 'head -n 1' MAILCMD="/bin/mail"; # Location of the mail program # that takes and understand the -s flag # DEBUG="true"; # Uncomment this to force debug mode on (or use -D), e.g.

/bin/sh # schaal @it # # Simple script to update Spam Assassin SYSLOG_TAG=sa-update compile=0 logger -d -t $SYSLOG_TAG "Start SA-Update" sa-update --nogpg retval="$?

" if [ $retval -eq 0 ]; then compile=1; fi sa-update --nogpg --channel updates.retval="$?

" if [ $retval -eq 0 ]; then compile=1; fi sa-update --nogpg --channel sa.retval="$?

Date: Tue, UTC Severity: normal Tags: fixed-upstream Found in versions spamassassin/3.4.1-8, spamassassin/3.4.1-6 deb9u1, spamassassin/3.4.0-6 Forwarded to https://bz.apache.org/Spam Assassin/show_bug.cgi?

id=7540 Package: spamassassin Version: 3.4.1-6 deb9u1 Severity: grave Justification: renders package unusable Dear Maintainer, I enabled CRON=1 in /etc/default/spamassassin, to enable the cron job to automatically update spamassassin's rules.

This does hilight a need to be a little more thorough in our cleanup of failed updates, though.Most of the rulesets that Rules Du Jour supports can be found on the SA Rules Emporium web site.I do not issue any guarantee that this will work for you!We currently detect the case where the update results in an invalid ruleset, and in that case we skip the spamd reload. Or better yet, we need to stage the ruleset and validate it before we ever expose it to the runtime environment.The theory is that we'll naturally pick up the fix when it's published via the update channel. noah The quickest work-around if to add check_for_forged_gmail_received_headers() to source code.

Leave a Reply