Package: spamassassin
Version: 3.3.1-1

Really, i don't know if this is a SA bug or a sa-exim bug, so feel free
to move de bug where appropriate.

Indeed, i don't know if this is a real bug... ;)
sa-exim plugin, at every spamassassin restart, print a row like:

        Sep 10 11:34:23.133 [15754] warn: Couldn't get Connecting IP header 
X-SA-Exim-Connect-IP for message <1347269660@lint_rules>, skipping greylisting 
call

AFAI've understood, this is a side effect of how the sa-exim module are
initialized, not a bug.

Anyway, migrating from lenny to squeeze, /etc/cron.daily/spamassassin
script start to complain every day about that; looking at lenny script,
seems to me that all restart command to SA are redirected to /dev/null
(STDOUT and STDERR).
Squeeze version have one more, SA call, with --lint.

Anyway, this little patch solve all the trouble.

Hope this help, thanks.

--- /tmp/spamassassin	2012-09-10 11:46:09.597794514 +0200
+++ /etc/cron.daily/spamassassin	2012-09-10 11:36:22.000000000 +0200
@@ -43,9 +43,9 @@
 reload() {
     # Reload
     if which invoke-rc.d >/dev/null 2>&1; then
-	invoke-rc.d spamassassin reload > /dev/null
+	invoke-rc.d spamassassin reload > /dev/null 2>&1
     else
-	/etc/init.d/spamassassin reload > /dev/null
+	/etc/init.d/spamassassin reload > /dev/null 2>&1
     fi
     if [ -d /etc/spamassassin/sa-update-hooks.d ]; then
         run-parts --lsbsysinit /etc/spamassassin/sa-update-hooks.d
@@ -66,7 +66,7 @@
 case $? in
     0)
         # got updates!
-        spamassassin --lint || die_with_lint
+        spamassassin --lint > /dev/null 2>&1 || die_with_lint
         do_compile
 	reload
         ;;

Reply via email to