Closing this bug from 2010 (14 years ago!) -- the then-maintainer
found that most of the suggestions were either already present or
should not actually be added, for various reasons.
A requested was made to resubmit as more independent bugs - if that
was done, we dont need this bug, and if not
Hi,
Like Gerfried said, please file different bug reports for different
packages the next time.
Some comments about your rule suggestions:
Radosław Antoniuk wrote:
#dkimproxy
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ dkimproxy.out\[[0-9]+\]: connect from .*$
^\w{3} [ :0-9]{11} [._[:alnum:]-]+
Package: logcheck-database
Version: 1.3.10
Severity: normal
Please add rules for some packages:
#dkimproxy
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ dkimproxy.out\[[0-9]+\]: connect from .*$
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ dkimproxy.out\[[0-9]+\]: DKIM signing -
signed; .*$
^\w{3} [ :0-9]{11}
tags 588312 + moreinfo
severity 588312 wishlist
thanks
Hello!
* Radek Antoniuk radek.anton...@gmail.com [2010-07-07 11:44:43 CEST]:
Please add rules for some packages:
It would be highly convenient if you could offer some sample log
entries so we can check if your usage of wildchar .*
#dkimproxy
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ dkimproxy.out\[[0-9]+\]: connect from .*$
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ dkimproxy.out\[[0-9]+\]: DKIM signing -
signed; .*$
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ dkimproxy.out\[[0-9]+\]: DKIM signing -
skipped; .*$
No rules at all.
Jul 7
5 matches
Mail list logo
