Matthew Goodman wrote: > Woops replied to sender instead of reply-to. Let's try again: > > > Some items in these directories are owned qscand:nofiles, others are owned > qscand:qscand > > I really have no idea how they could be mis-chown'd like that. > > Any ideas where I could look? > > Without digging straight into your system, it'd be hard to say for sure.
What you have to realize is that you have a number of programs stirring the pot there. Here's a site to help a bit - http://qmail.jms1.net/clamav/qmail-scanner.shtml You have your antivirus scanner, you have spamassassin, and you can have other stuff as well as the actual Qmail install itself. The files have to be accessible by those various users, so you can actually do the work. I'd guess that the problem MAY be more on the output end than the scanning part - meaning that somewhere, when the system is supposed to 'clean up', it's dropping the ball. Doublecheck the documentation. If nothing else, you might be able to set qmail-scanner into 'verbose' mode, and feed a test message through so that you can track the exact process. (The contrib has a testing script) Again, I'm not familiar enough with all the code to tell you without actually rooting around in your system - take this stuff with a grain of salt, and do what Jason Haar recommends with the -z option run as a cron job every night. BW ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Qmail-scanner-general mailing list Qmail-scanner-general@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/qmail-scanner-general
