Package: logcheck Version: 1.2.39 Severity: normal Hello,
Due to the incorrect group ownership bug (which has already been fixed) I ended up with logcheck not being able to read any files in /etc/logcheck/ignore.d.paranoid. However, instead of complaining that some files were unreadable, logcheck just sent the *complete* logfiles by mail, without any filtering. If logcheck cannot read some of its rule files, it should mention that in its mail. Additionally, it may be worth considering to not include any logfile contents in this case, since for me this generated a 10 MB mail. Best, Nikolaus -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.6.9-023stab039.1-smp Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages logcheck depends on: ii adduser 3.63 Add and remove users and groups ii cron 3.0pl1-86 management of regular background p ii debconf [debconf 1.4.30.13 Debian configuration management sy ii debianutils 2.8.4 Miscellaneous utilities specific t ii exim4 4.50-8sarge2 metapackage to ease exim MTA (v4) ii exim4-daemon-hea 4.50-8sarge2 exim MTA (v4) daemon with extended ii lockfile-progs 0.1.10 Programs for locking and unlocking ii logcheck-databas 1.2.39 A database of system log rules for ii logtail 1.2.39 Print log file lines that have not ii mailx 1:8.1.2-0.20040524cvs-4 A simple mail user agent ii sysklogd [system 1.4.1-17 System Logging Daemon -- debconf information excluded -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
