MailScanner logwatch script

[Tony Stocker]

Hello All,

I'm getting a lot of things listed under "Unmatched Entries" with the
logwatch script for MailScanner.  They fall into a couple of
categories:

SpamAssassin:
Expired 1 records from the SpamAssassin cache : 42 Time(s)
Read 748 hostnames from the phishing whitelist : 30 Time(s)
Enabling SpamAssassin auto-whitelist functionality... : 30 Time(s)
Using SpamAssassin results cache : 30 Time(s)
Connected to SpamAssassin cache database : 30 Time(s)
SpamAssassin cache hit for message 2497B8EB51.3A7D5 : 1 Time(s)

ClamAV:
I have found clamavmodule scanners installed, and will use them all by
default. : 30 Time(s)
ClamAV update of /usr/local/share/clamav/daily.cvd detected, resetting
ClamAV Module : 5 Time(s)
ClamAV virus database has been updated, killing this child : 5 Time(s)

Batch messages:
Batch (1 message) processed in 5.19 seconds : 3 Time(s)

Message conversions:
   6C2968EB51.6A5A9 to 969018EB6B : 1 Time(s)
   CC0308EB6F.696B5 to 5152D8EB72 : 1 Time(s)
   D72728EB43.1582F to 69C2A8EB6B : 1 Time(s)

My mail server is currently not very heavily used and already the
logwatch report is filled with these types of messages.  When we move
the rest of our users I imagine that this will increase linearly with
the number of users we add.  I'd really like to avoid this mass of
extraneous information ending up in the logwatch report.

Does anyone have any ideas how to tune things so this stuff doesn't
end up in there?  There are a lot of entry types here so I'm loathe to
rewrite the mailscanner logwatch script and I'm not even sure how to
write a filter for what I called the "Message conversion" entries that
wouldn't catch everything.

Tony