Bug 204432 - **Unmatched Entries** when using with mailman, amavis and spamassassin
**Unmatched Entries** when using with mailman, amavis and spamassassin
Product: Fedora
Classification: Fedora
Component: logwatch (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Ivana Varekova
Depends On:
  Show dependency treegraph
Reported: 2006-08-28 22:39 EDT by Pedro Bezunartea
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-08-29 04:16:59 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Patch for amavis script: /usr/share/logwatch/scripts/services/amavis (751 bytes, patch)
2006-08-28 22:39 EDT, Pedro Bezunartea
no flags Details | Diff

  None (edit)
Description Pedro Bezunartea 2006-08-28 22:39:55 EDT
Description of problem:
The amavis script in logwatch doesn't detect lines generated by mailman when it
resends a spam message to a list. The different entries in /var/maillog are as
- Spam message for a list:
Aug 27 04:08:42 hostname amavis[14372]: (14372-09) Passed SPAM, []
[] <kfxxov@eba.com> -> <gc@domain.deleted>, Message-ID:
<000b01c6c97d$b595b4a0$5baf6650@pc>, mail_id: UFL+vAvISpyg, Hits: 15.09,
queued_as: 02D333B6383, 6025 ms
- Spam message from mailman to the list owners:
Aug 27 04:08:46 hostname amavis[14372]: (14372-10) Passed SPAM, LOCAL
[] [] <gc-bounces@domain.deleted> ->
<gc-owner@domain.deleted>, Message-ID:
<mailman.1199.1156644523.5005.gc@domain.deleted>, mail_id: SBYKf6j5a2Nx, Hits:
9.659, queued_as: D2D1D3B6387, 1887 ms

The only difference is the word "LOCAL" after "Passed SPAM".

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Install mailman, amavis and spamassassin.
Configure amavis to pass spam to the users.
2. Get some spam sent to any mailman list.
3. Wait for logwatch to run.
Actual results:
All spam messages re-sent from mailman appear under **Unmatched Entries** in
logwatch report.

Expected results:
No **Unmatched Entries**. I'm not sure how these messages should be actually
counted, or if they should be counted at all, but they should certainly not
appear under unmatched entries.

Additional info:
I modified logwatch's amavis script to get rid of those lines. I enclose the
diff file (patch file?). The only problem is that spam messages to the mailing
lists are counted twice.
Comment 1 Pedro Bezunartea 2006-08-28 22:39:57 EDT
Created attachment 135101 [details]
Patch for amavis script: /usr/share/logwatch/scripts/services/amavis
Comment 2 Ivana Varekova 2006-08-29 04:16:59 EDT
Fixed in logwatch-7.3-5

Note You need to log in before you can comment on or make changes to this bug.