Bug 141721 - logwatch for sendmail logs clone statements incorrectly
Summary: logwatch for sendmail logs clone statements incorrectly
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: logwatch
Version: 3
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Ivana Varekova
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-12-03 08:02 UTC by bjorn l.
Modified: 2007-11-30 22:10 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2005-06-27 15:16:23 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description bjorn l. 2004-12-03 08:02:48 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040510

Description of problem:
The sendmail script has the entry:

      ( $ThisLine =~ m/^clone [a-zA-Z0-9]+, owner=/ ) or

But my maillog has entries of the form:
    
      clone: owner=xxxxxx

where xxxxxx is the owner id.  This is verified by looking
at deliver.c in the sendmail source:

                        if (mode != SM_VERIFY && LogLevel > 4)
                                sm_syslog(LOG_INFO, e->e_id,
                                          "%s: clone: owner=%s",
                                          ee->e_id, owner);

The format in logwatch was used in sendmail 8.11.x;  the format
shown above has been used on 8.12.0 and successors (since Sept. 2001)

So I think you need an additional sendmail logwatch entry that
looks something like:

       ( $ThisLine =~ m/clone: owner=/ ) or


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


How reproducible:
Always

Steps to Reproduce:
1. Run logwatch (sendmail) on modern sendmail with -owner list, or
2. Look at the code for clone statements
3.
    

Additional info:

Comment 1 bjorn l. 2004-12-03 08:04:30 UTC
And on a somewhat related note, the sendmail script header says:
     Please send all comments, suggestions, bug reports,
              etc, to shiva.

But that is no longer a working address.  So that notation should
be either deleted or changed to a current address.


Comment 2 Ivana Varekova 2005-06-27 15:16:23 UTC
This bug is fixed in the last version (logwatch-6.1.2-1).


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