Package: logcheck Version: 1.2.43a Severity: normal
-- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (900, 'testing'), (800, 'unstable') Architecture: i386 (i586) Kernel: Linux 2.6.10 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 Versions of packages logcheck depends on: ii adduser 3.77 Add and remove users and groups ii cron 3.0pl1-91 management of regular background p ii debconf [debconf 1.4.58 Debian configuration management sy ii debianutils 2.15 Miscellaneous utilities specific t ii exim4 4.54-1 metapackage to ease exim MTA (v4) ii exim4-daemon-hea 4.54-1 exim MTA (v4) daemon with extended ii grep 2.5.1.ds2-1 GNU grep, egrep and fgrep ii lockfile-progs 0.1.10 Programs for locking and unlocking ii logcheck-databas 1.2.43a database of system log rules for t ii logtail 1.2.43a Print log file lines that have not ii mailx 1:8.1.2-0.20050715cvs-1 A simple mail user agent ii sysklogd [system 1.4.1-17 System Logging Daemon -- debconf information excluded We need to cope with messages of the form 2006-03-28 09:26:34 1FO9X2-0003UQ-Gp -> ... destination ... These are logged when a single message ends up having multiple recipients - the first destination is logged with =>, and the rest have ->. I suggest that, for each rule with a "=>", we replace this with "[=-]>". Cheers, Richard -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]