Currently if you enable anvil in postfix you get maillog entries such as the below. Unfortunately logwatch doesn't seem to handle the scache entries and generated lots of messages about "Unmatched entries". postfix/scache[24755]: statistics: start interval Jul 30 04:01:41 postfix/scache[24755]: statistics: domain lookup hits=1 miss=10 success=9% postfix/scache[24755]: statistics: address lookup hits=0 miss=10 success=0% postfix/scache[24755]: statistics: max simultaneous domains=1 addresses=1 connection=10 postfix/scache[25590]: statistics: start interval Jul 30 04:18:21 postfix/scache[25590]: statistics: domain lookup hits=37 miss=20 success=64% postfix/scache[25590]: statistics: address lookup hits=0 miss=20 success=0% postfix/scache[25590]: statistics: max simultaneous domains=1 addresses=1 connection=20 postfix/scache[31466]: statistics: start interval Jul 30 04:35:01 postfix/scache[31466]: statistics: domain lookup hits=14 miss=10 success=58% postfix/scache[31466]: statistics: address lookup hits=0 miss=10 success=0% postfix/scache[31466]: statistics: max simultaneous domains=1 addresses=1 connection=10 postfix/anvil[31961]: statistics: max connection rate 1/60s for (smtp:203.58.57.128) at Jul 30 04:58:39 postfix/anvil[31961]: statistics: max connection count 1 for (smtp:203.58.57.128) at Jul 30 04:58:39 postfix/anvil[31961]: statistics: max cache size 1 at Jul 30 04:58:39 postfix/scache[32161]: statistics: start interval Jul 30 05:08:21 postfix/scache[32161]: statistics: domain lookup hits=2 miss=9 success=18% postfix/scache[32161]: statistics: address lookup hits=0 miss=9 success=0% postfix/scache[32161]: statistics: max simultaneous domains=1 addresses=1 connection=7 postfix/scache[32513]: statistics: start interval Jul 30 05:25:01 postfix/scache[32513]: statistics: domain lookup hits=0 miss=4 success=0% postfix/scache[32513]: statistics: address lookup hits=0 miss=4 success=0% postfix/scache[32513]: statistics: max simultaneous domains=1 addresses=1 connection=4 postfix/scache[387]: statistics: start interval Jul 30 05:41:41 postfix/scache[387]: statistics: domain lookup hits=37 miss=20 success=64% postfix/scache[387]: statistics: address lookup hits=0 miss=20 success=0% postfix/scache[387]: statistics: max simultaneous domains=1 addresses=1 connection=20 postfix/scache[753]: statistics: start interval Jul 30 05:58:20 postfix/scache[753]: statistics: domain lookup hits=4 miss=12 success=25% postfix/scache[753]: statistics: address lookup hits=0 miss=12 success=0% postfix/scache[753]: statistics: max simultaneous domains=1 addresses=1 connection=8 postfix/anvil[954]: statistics: max connection rate 2/60s for (smtp:190.2.6.116) at Jul 30 06:09:18 postfix/anvil[954]: statistics: max connection count 1 for (smtp:190.2.6.116) at Jul 30 06:08:21 postfix/anvil[954]: statistics: max cache size 1 at Jul 30 06:08:21 postfix/scache[1115]: statistics: start interval Jul 30 06:15:01 postfix/scache[1115]: statistics: domain lookup hits=0 miss=6 success=0% postfix/scache[1115]: statistics: address lookup hits=0 miss=6 success=0% postfix/scache[1115]: statistics: max simultaneous domains=1 addresses=1 connection=5 postfix/scache[1452]: statistics: start interval Jul 30 06:31:40 postfix/scache[1452]: statistics: domain lookup hits=0 miss=9 success=0% postfix/scache[1452]: statistics: address lookup hits=0 miss=9 success=0% postfix/scache[1452]: statistics: max simultaneous domains=1 addresses=1 connection=9 postfix/scache[1827]: statistics: start interval Jul 30 06:48:21 postfix/scache[1827]: statistics: domain lookup hits=2 miss=10 success=16% postfix/scache[1827]: statistics: address lookup hits=0 miss=10 success=0% postfix/scache[1827]: statistics: max simultaneous domains=1 addresses=1 connection=10
Ok, I'll fix it. Could you send me part from these files, which is about postfix? I have problem with reproducing the bug. /var/cache/logwatch/logwatch.XXXXXX/maillog /var/log/maillog
Created attachment 136887 [details] statistics lines from maillog This is the output of 'egrep statistics /var/log/maillog' on a RHES4 box. Note that this problem is also happening on RHES4, but we do not have a /var/cache/logwatch/ dir.
Fixed in logwatch-7.3.1-6.fc7.
This problem also exists on RHEL3 which runs logwatch-5.2.2-1. Is there no plan to fix it for non-fedora releases?