[Logcheck-devel] Bug#353868: logcheck-database: no longer ignores "spamd: checking message ..."
Aaron M. Ucko
ucko at debian.org
Tue Feb 21 14:57:50 UTC 2006
Package: logcheck-database
Version: 1.2.43a
Severity: minor
Since last weekend's upgrade of logcheck-database from 1.2.42 to
1.2.43a, logcheck stopped ignoring routine SpamAssassin messages of
the form
Feb 20 21:36:16 tux64 spamd[4665]: spamd: checking message <20060220190721.0E0B41C5207 at llwb563.servidoresdns.net> for amu:7286
Could you please edit the second pattern in
/etc/logcheck/ignore.d.paranoid/spamassassin to allow "checking" as an
alternative to "processing"?
Thanks!
(Incidentally, in regard to #353793, which bit me as well, run-parts's
filtering, though perhaps stricter than some might like, is a
*feature* -- in particular, you should also ignore .dpkg-* files, if
nothing else. I'd actually suggest reverting the change altogether
and simply documenting run-parts's policy.)
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'sarge-unsupported')
Architecture: amd64 (x86_64)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Versions of packages logcheck-database depends on:
ii cdebconf [debconf-2.0] 0.97 Debian Configuration Management Sy
ii debconf [debconf-2.0] 1.4.70 Debian configuration management sy
logcheck-database recommends no packages.
-- debconf information excluded
More information about the Logcheck-devel
mailing list