Sorry, I misread this issue. I thought it was failure for clamd to scan when integrated with exim4. It's the same underlying issue though; clamd cannot scan when either permissions or apparmor settings prevent it from doing so.
Shall I submit the exim4 version of this as a separate issue, or should we leave it as part of this one? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/708395 Title: clamdscan can't scan anything To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/708395/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
