Bug 12271 - Barracuda spam firewall antry in logwatch cron.daily report
Summary: Barracuda spam firewall antry in logwatch cron.daily report
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 3
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Remco Rijnders
QA Contact: QA Team
URL: http://bugs.debian.org/cgi-bin/bugrep...
Whiteboard:
Keywords: PATCH, Triaged
Depends on:
Blocks:
 
Reported: 2014-01-12 11:43 CET by andre salaun
Modified: 2015-03-31 16:03 CEST (History)
0 users

See Also:
Source RPM: logwatch-7.4.0-2.mga3
CVE:
Status comment:


Attachments

Description andre salaun 2014-01-12 11:43:15 CET
0logwatch cron.daily report get these lines :


--------------------- barracuda spam firewall Begin ------------------------ 

 **Unmatched Entries**


described on Debian list :

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=618526
Manuel Hiebel 2014-01-20 23:59:40 CET

Keywords: (none) => PATCH, Triaged
Assignee: bugsquad => remco

Comment 1 Remco Rijnders 2014-08-18 10:24:15 CEST
Hi Andre,

Thank you for your report. I have applied the Debian patch to our package.

Can you please confirm this fixes the problem for you?

Updated packages are:
3: core/updates_testing/logwatch-7.4.0-3.mga3
4: core/updates_testing/logwatch-7.4.0-4.mga4
cauldron: core/release/logwatch-7.4.0-4.mga5

Also, for my understanding:
Can you confirm that you got this message as you have the barracuda firewall installed on your system?

If yes, this will make it hard for our QA team to validate the update, and we may have to rely on your test only.

Status: NEW => ASSIGNED
QA Contact: (none) => qa-bugs

Comment 2 andre salaun 2014-08-20 15:44:35 CEST
Hi Remco,

I confirm that fixes this bug for me, no more **Unmatched Entries** in logwatch report.

I don't know barracuda spam firewall and never installed it.

Thank you for your job.
Comment 3 David Walser 2014-10-06 18:12:08 CEST
This needs to be assigned to the QA Team if it will be pushed as an update.
Comment 4 Marja Van Waes 2015-03-31 16:03:49 CEST
Mageia 3 changed to end-of-life (EOL) status 4 months ago.
http://blog.mageia.org/en/2014/11/26/lets-say-goodbye-to-mageia-3/ 

Mageia 3 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 Mageia
please feel free to click on "Version" change it against that version of Mageia
and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
The Mageia Bugsquad

Status: ASSIGNED => RESOLVED
Resolution: (none) => OLD


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