Clamassassin broken in Feisty

Bug #139943 reported by Mendez
4
Affects Status Importance Assigned to Milestone
clamassassin (Ubuntu)
Fix Released
Medium
Unassigned
Feisty
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: clamassassin

I've been trying to setup Clamassassin to work with procmail and on checking the headers found that they weren't being scanned and that the header has an clamscan error 40 listed in one of the headers.

I then came across

http://lists.jameslick.com/pipermail/clamassassin-announce/2007-February/000030.html

which says that due to a change in the command line options of clamav you need to change clamassassin as follows...

CLAMSCANOPT="--no-summary --stdout --mbox"

to

CLAMSCANOPT="--no-summary --stdout"

I have done this and it's now working fine.

The correct solution is probably to upgrade the package to 1.2.4

Revision history for this message
Scott Kitterman (kitterman) wrote :

Before I expend effort on this, I'd like a read from motu-sru on if this would be approved. Is the manual edit sufficient work around that it's not SRU worthy?

Changed in clamassassin:
importance: Undecided → Medium
status: New → Fix Released
assignee: nobody → kitterman
Revision history for this message
LaserJock (laserjock) wrote :

I would be against an SRU for this. I don't think it rises to the level of an SRU given that a fix would really only help new Feisty installs, is a config file problem, and there is a well-documented workaround. I think it would take too many resources in packaging/testing.

Changed in clamassassin:
status: New → Invalid
Changed in clamassassin:
assignee: kitterman → nobody
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.