I think this bug can be closed as Jaunty is EOL and in Karmic it got
fixed.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to amavisd-new in ubuntu.
https://bugs.launchpad.net/bugs/377216
Title:
amavisd-new fails to block viruses with
** Changed in: amavisd-new (Ubuntu Jaunty)
Status: Confirmed = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to amavisd-new in ubuntu.
https://bugs.launchpad.net/bugs/377216
Title:
amavisd-new fails to block viruses
Confirmed it's working ok with my testcase on Karmic.
--
amavisd-new fails to block viruses with backup scanner (clamscan)
https://bugs.launchpad.net/bugs/377216
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to amavisd-new in ubuntu.
--
This also affects Jaunty and Intrepid, maybe it should be fixed there
also. One could argue that the following could be a real scenario:
- one installs MTA + amavis + clamav (with clamav-daemon because it's faster,
and clamscan because it can be run manually whenever needed)
- primary AV scanner
I set up a task for Jaunty. I think that's worth doing. I doubt
Intrepid still has enough use to make it worth the trouble (if anyone
needs this fixed on Intrepid, speak up).
** Also affects: amavisd-new (Ubuntu Jaunty)
Importance: Undecided
Status: New
** Also affects: amavisd-new
I have tested with the version included in Karmic and it's fixed.
** Changed in: amavisd-new (Ubuntu)
Status: Triaged = Fix Released
** Changed in: amavisd-new (Ubuntu)
Status: Fix Released = Fix Committed
--
amavisd-new fails to block viruses with backup scanner (clamscan)
This got fixed upstream in amavis 2.6.3
We now have 2.6.4 for karmic, could you confirm that this is now fixed ?
--
amavisd-new fails to block viruses with backup scanner (clamscan)
https://bugs.launchpad.net/bugs/377216
You received this bug notification because you are a member of Ubuntu
Thanks for the report. Although this is an important functional issue,
it's not a security issue. I'm going to unmark this as a
private/security bug.
** Visibility changed to: Public
** This bug is no longer flagged as a security vulnerability
** Changed in: amavisd-new (Ubuntu)
Importance:
