Description of problem: Logwatch's SpamAssassin script doesn't proper ignore Sendmail startup messages, for example: Jan 27 00:27:31 tux sendmail[12386]: starting daemon (8.14.6): SMTP+queueing@01:00:00 Jan 27 00:27:31 tux sm-msp-queue[12395]: starting daemon (8.14.6): queueing@01:00:00 Version-Release number of selected component (if applicable): logwatch-7.4.0-23.20130102svn127.fc19 How reproducible: Everytime, see above and below. Steps to Reproduce: 1. Put "Detail = 3" into /etc/logwatch/conf/services/sendmail.conf 2. (Re)start sendmail Actual results: Logwatch's SpamAssassin script doesn't proper ignore Sendmail startup messages. Expected results: Logwatch's SpamAssassin script ignore Sendmail startup messages, e.g. by using following patch: --- snipp --- --- logwatch/scripts/services/spamassassin 2013-01-27 14:21:37.000000000 +0100 +++ logwatch/scripts/services/spamassassin.rsc 2013-01-27 15:08:30.000000000 +0100 @@ -80,6 +80,7 @@ # Sendmail messages to ignore ( $ThisLine =~ m/^AUTH=/ ) or ( $ThisLine =~ m/^STARTTLS/ ) or + ( $ThisLine =~ m/^starting daemon \([0-9\.]+\): / ) or 0 # Always last in the list, so all above can say "or" at the end ) { ; # We don't care about these --- snapp ---
https://sourceforge.net/tracker/?func=detail&aid=3602285&group_id=312875&atid=1316826
Or, this could be titled, "I don't have SpamAssassin, so why is my Sendmail section gone?" With the latest release of logwatch, what used to be the "sendmail" section is now labeled "spamassassin". The latter is NOT installed on my system: --------------------- SpamAssassin Begin ------------------------ **Unmatched Entries** starting daemon (8.14.6): SMTP+queueing@01:00:00: 3 Time(s) /etc/aliases: 77 aliases, longest 18 bytes, 793 bytes total: 1 Time(s) alias database /etc/aliases rebuilt by sdstern: 1 Time(s) ---------------------- SpamAssassin End ------------------------- logwatch-7.4.0-23.20130102svn127.fc18.noarch
Just seen this on F17 as well.
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19
This bugzilla should be resolved with the latest update to r140. https://admin.fedoraproject.org/updates/logwatch-7.4.0-25.20130522svn140.fc19
Still happening on Logwatch 7.4.0 (released 03/01/11) logwatch-7.4.0-25.20130522svn140.fc18.noarch
Please, try https://admin.fedoraproject.org/updates/logwatch-7.4.1-1.20140924svn242.fc20 if it resolves the issue.
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.