On Thu, 2005-04-28 at 14:57 -0400, Marc Sherman wrote: > Jamie L. Penman-Smithson wrote: > > Since there is an open bug about this filed against spamassassin, I'm > > not sure this should be included with logcheck. This is a temporary > > issue which will [hopefully] be fixed in the next release of SA, in the > > meantime this belongs in a local-foo file.. > > This bug has existed upstream since december[1], and there doesn't seem > to be any rush to get it fixed (it's currently put off to 3.1.1). I > think it's quite unlikely it will be fixed before sarge is released, > while the new logcheck rule could easily be added before sarge is released.
Whether it gets fixed before sarge or not, we're not going to start including rules for messages caused by transient problems in packages, sorry. You can either configure your favourite syslog variant to not log those messages, or you can add a regexp for it to a local- file in /etc/logcheck/ignore.d.* -j
signature.asc
Description: This is a digitally signed message part
