Bug#687149: cron.daily maintenance/upgrade script emit warnings...

2014-03-04 Thread Marco Gaiarin

 I will tag this ticket as squeeze since it seems to only apply to
 the Squeeze 6 version.

This is true.

Sorry but i'm a bit late in debian versions, so i've started in these
days the upgrate to wheezy, and still no one with a SA setup.

I've only do some test and noted that newer SA use a dedicated users,
not 'nobody'.


So, please, wait some time and i will comment this bug, and adding a
specific one for the 'SA_UPDATE_OPTS' variable to manage
plugin/external repository.

Thanks.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#687149: cron.daily maintenance/upgrade script emit warnings...

2014-03-03 Thread Bob Proulx
Bob Proulx (me) wrote:
 The original bug report was regarding sa-exim and greylisting.
 ...
 the bug should be reassigned to exim4 as an exim problem.

Adam D. Barratt wrote:
 sa-exim isn't exim4; it's a separate package from a different upstream.

Marco Gaiarin wrote:
 No, it is not exim4 trouble, better a sa-exim trouble, but i think it
 is generic, so robably other SA plugin (not only sa-exim) could trigger
 that...

Sorry.  I misspoke saying exim4 when I should have said sa-exim.  My
bad.  I had identified it correctly in an earlier message.

Bob


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#687149: cron.daily maintenance/upgrade script emit warnings...

2014-03-03 Thread Bob Proulx
Marco Gaiarin wrote:
 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.

Much of the code for spamassassin is completely different in recent
versions released with Debian Wheezy 7 and later.  I have not been
able to recreate any of the issues reported in this ticket on Wheezy.
I believe any issues here only apply to Squeeze 6 and not to any later
release.

I will tag this ticket as squeeze since it seems to only apply to
the Squeeze 6 version.

Bob


signature.asc
Description: Digital signature


Bug#687149: cron.daily maintenance/upgrade script emit warnings...

2014-02-28 Thread Marco Gaiarin

  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
 Is this still a problem for you?  There have been a number of package

Ahem, i'm still mostly on squeeze, and all of my spamassassin
installation ws not just migrated to wheezy.
So... i cannot reply. ;-)


 the bug should be reassigned to exim4 as an exim problem.

No, it is not exim4 trouble, better a sa-exim trouble, but i think it
is generic, so robably other SA plugin (not only sa-exim) could trigger
that...


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#687149: cron.daily maintenance/upgrade script emit warnings...

2014-02-24 Thread Adam D. Barratt

On 2014-02-24 4:55, Bob Proulx wrote:

Marco Gaiarin wrote:
	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


Is this still a problem for you?  There have been a number of package
version uploads since this report.  I cannot reproduce the above with
spamassassin and postfix.  If it is still active for you then I think
the bug should be reassigned to exim4 as an exim problem.


sa-exim isn't exim4; it's a separate package from a different upstream.

Regards,

Adam


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#687149: cron.daily maintenance/upgrade script emit warnings...

2014-02-23 Thread Bob Proulx
Marco Gaiarin wrote:
   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

Is this still a problem for you?  There have been a number of package
version uploads since this report.  I cannot reproduce the above with
spamassassin and postfix.  If it is still active for you then I think
the bug should be reassigned to exim4 as an exim problem.

Bob


signature.asc
Description: Digital signature


Bug#687149: cron.daily maintenance/upgrade script emit warnings...

2012-09-10 Thread Marco Gaiarin
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.0 +0200
@@ -43,9 +43,9 @@
 reload() {
 # Reload
 if which invoke-rc.d /dev/null 21; then
-	invoke-rc.d spamassassin reload  /dev/null
+	invoke-rc.d spamassassin reload  /dev/null 21
 else
-	/etc/init.d/spamassassin reload  /dev/null
+	/etc/init.d/spamassassin reload  /dev/null 21
 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 21 || die_with_lint
 do_compile
 	reload
 ;;