I was able to reproduce the behavior with the released intrepid version of logcheck, 1.2.66, and can confirm that logcheck 1.2.66ubuntu1 in intrepid-proposed fixes the issue, with logged messages being reported correctly.
I was able to reproduce the behavior with the released intrepid version of logcheck, 1.2.66, and can confirm that logcheck 1.2.66ubuntu1 in intrepid-proposed fixes the issue, with logged messages being reported correctly.