Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 159567 - Logwatch doesn't recongnize routine mailman access
Logwatch doesn't recongnize routine mailman access
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: logwatch (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Ivana Varekova
Depends On:
Blocks: 189992 FAST4.5APPROVED
  Show dependency treegraph
Reported: 2005-06-04 12:52 EDT by Matthew Saltzman
Modified: 2007-11-30 17:07 EST (History)
0 users

See Also:
Fixed In Version: RHBA-2006-0631
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-09-06 09:53:44 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Proposed patch. (2.04 KB, patch)
2005-08-31 07:15 EDT, Ivana Varekova
no flags Details | Diff
suppress the file list of no suffixes. (536 bytes, patch)
2005-09-02 07:02 EDT, Hideaki Suzuki
no flags Details | Diff

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2006:0631 normal SHIPPED_LIVE logwatch bug fix update 2007-05-01 10:10:43 EDT

  None (edit)
Description Matthew Saltzman 2005-06-04 12:52:04 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050513 Fedora/1.0.4-1.3.1 Firefox/1.0.4

Description of problem:
Logwatch reports routine access to mailman listinfo and archive pages as "unidentified 'other' records"

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

How reproducible:

Steps to Reproduce:
1. Standard RHEL 4 installation with mailman.
2. Access various pages under http://www.myserver.com/pipermail or http://www.myserver.com/mailman.
3. Wait for next day's logwatch report.

Actual Results:  Lots of "unidentified 'other' records" in httpd section of logwatch report, all "GET /pipermail/..." or "GET /mailman/..." with code 200 responses.

Expected Results:  The code 200 responses are normal accesses and should be filtered out by logwatch.

Additional info:
Comment 1 Ivana Varekova 2005-08-31 07:15:49 EDT
Created attachment 118292 [details]
Proposed patch.

This problem is fixed in the attached patch. Logwatch should ignore most of
mailx and pipermail log messages, but logwatch should not ignore (not only
mailman and pipermail) log messages with error response codes >400 (see
upstream version). The attached patch fixes this problem too.
Comment 2 Hideaki Suzuki 2005-09-02 06:57:33 EDT
logwatch seems to report all files without suffix.  Mailman uses cgi files 
without suffixes.

Chances are, the patch attached is good enough.
Comment 3 Hideaki Suzuki 2005-09-02 07:02:11 EDT
Created attachment 118387 [details]
suppress the file list of no suffixes.
Comment 14 Red Hat Bugzilla 2006-09-06 09:53:45 EDT
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


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