Suddenly Seeing Clamav Errors After MailScanner Update

Sean DuBois sean at
Tue Jun 11 04:38:07 UTC 2013

Hi Tim,

Double check what user clamd is run as, and what permissions your mail
spool have. Somewhere along the line your mail spool locked out clamd

The lstat system call's man page says 

`execute (search) permission is required on all of the
directories in path that lead to the file.`

Also, don't just go "chmoding -R 777"! 

On Mon, Jun 10, 2013 at 12:03:51PM -0500, Tim Daneliuk wrote:
> I am working on a FBSD 9.1-STABLE mail machine that's been working
> fine.  After upgrading to MailScanner 4.84.5_3, we are now
> suddenly seeing like this:
>       Clamd::ERROR:: UNKNOWN CLAMD RETURN ./lstat() failed: Permission denied. ERROR :: /var/spool/MailScanner/incoming/68340
> Any ideas what might cause this?   I have fallen back to the previous
> MailScanner.conf file wherein the problem does NOT seem to happen.
> But, after diffing old and new config files I cannot see where
> anything relevant to this might have changed.
> Ideas anyone?
> -- 
> -----------------------------------------------------------------------
> Tim Daneliuk
> _______________________________________________
> freebsd-questions at mailing list
> To unsubscribe, send any mail to "freebsd-questions-unsubscribe at"

More information about the freebsd-questions mailing list