Created attachment 702709 [details] Unmatched spamassassin entries in daily logwatch report Description of problem: Logwatch reports dnsbl entries in the maillog as unmatched spamassassin entries while it should not. Version-Release number of selected component (if applicable): logwatch-7.4.0-23.20130102svn127.fc17.noarch spamassassin-3.3.2-14.fc17.i686 How reproducible: All the time. Steps to Reproduce: 1. install sendmail spamassassin logwatch and setup some dnsbl blocking in sendmail.cf 2.observe daily logwatch reports. 3. Actual results: As shown in the attachment. Expected results: No "unmatched" entries for dnsbl blockings. Additional info:
Can I implement some kind of workaround (for now)?
Please help me.
Since you didn't actually specify your configuration, I can't really tell what went wrong. Please, send a log sample and the respective logwatch output (unmatched entries).
Created attachment 730607 [details] Logwatch sample Hereby the Logwatch sample.
Created attachment 730608 [details] Corresponding maillog And the corresponding maillog.
I added two attachments. hope this is sufficient. Regards, Eddie (In reply to comment #3) > Since you didn't actually specify your configuration, I can't really tell > what went wrong. > > Please, send a log sample and the respective logwatch output (unmatched > entries).
(In reply to comment #3) > Since you didn't actually specify your configuration, I can't really tell > what went wrong. > > Please, send a log sample and the respective logwatch output (unmatched > entries). Have added these more than a month ago, can you give me an update on the pogress?
Dear Jan, I'd really like to see something being done to this issue. Although it might not sound really that important to you, those big logwatch reports every day become quit annoying. Can you help please? Best regards, Eddie.
Hi Eddie, you can use /etc/logwatch/conf/ignore.conf as a temporary solution. Try adding this line into the file: ruleset=check_relay.* Unfortunately, logwatch is now quite low on my priority list for a proper fix. So no, I'm not ignoring any reports.
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. 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 prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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 to Fedora 18's end of life. 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 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.