Comment 13 for bug 708395

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?