From owner-freebsd-questions@FreeBSD.ORG Tue Jun 11 04:38:07 2013 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 1698AB10 for ; Tue, 11 Jun 2013 04:38:07 +0000 (UTC) (envelope-from sean@siobud.com) Received: from siobud.com (unknown [IPv6:2600:3c03::f03c:91ff:feae:3ca5]) by mx1.freebsd.org (Postfix) with ESMTP id EAE6C1A1B for ; Tue, 11 Jun 2013 04:38:06 +0000 (UTC) Received: from sean by siobud.com with local (Exim 4.80) (envelope-from ) id 1UmGLM-0005wY-Fp; Tue, 11 Jun 2013 00:38:04 -0400 Date: Tue, 11 Jun 2013 00:38:04 -0400 From: Sean DuBois To: Tim Daneliuk Subject: Re: Suddenly Seeing Clamav Errors After MailScanner Update Message-ID: <20130611043804.GA22837@siobud.com> References: <51B606F7.4050604@tundraware.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <51B606F7.4050604@tundraware.com> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: FreeBSD Mailing List X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Jun 2013 04:38:07 -0000 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@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"