On Fri, Jun 07, 2019 at 07:48:56AM -0700, John Hardin wrote: > On Fri, 7 Jun 2019, Henrik K wrote: > > >Just committed a simple log suppressor for these kinds of spam.. > > > >Jun 7 11:25:44.264 [1569] dbg: rules: ran body rule __LOWER_E ======> got > >hit: "e" > >Jun 7 11:25:44.264 [1569] dbg: rules: ran body rule __LOWER_E ======> got > >hit: "e" > >Jun 7 11:25:44.264 [1569] dbg: rules: ran body rule __LOWER_E ======> got > >hit: "e" > >Jun 7 11:25:44.264 [1569] dbg: rules: ran body rule __LOWER_E ======> got > >hit: "e" > >Jun 7 11:25:44.265 [1569] dbg: rules: ran body rule __LOWER_E ======> got > >hit: "e" > >Jun 7 11:25:44.265 [1569] dbg: rules: ran body rule __LOWER_E ======> got > >hit: "e" > >Jun 7 11:25:44.265 [1569] dbg: rules: ran body rule __LOWER_E ======> got > >hit: "e" > >Jun 7 11:25:44.265 [1569] dbg: rules: ran body rule __LOWER_E ======> got > >hit: "e" > >Jun 7 11:25:44.265 [1569] dbg: rules: ran body rule __LOWER_E ======> got > >hit: "e" > >Jun 7 11:25:44.265 [1569] dbg: rules: ran body rule __LOWER_E ======> got > >hit: "e" > >Jun 7 11:25:44.269 [1569] dbg: --- last message repeated 21 times --- > > Veto doing that. That information is very useful when debugging rules.
Well the information is there. In many places. You are saying you are consistently using things like spamassassin -t -D | grep __LOWER_E | wc -l to debug your rules?
