Re: cannot open for write /var/spool/qscan/quarantine-events.db.tmp

Salvatore Toribio wrote:
>
> You are having a logical result from that test, unfortenately you are 
> running a test for the very old versions of qmail-scanner and that 
> information has not been updated in recent version... The user 
> 'qmaild' cannot read that file, in past times qmail-scanner was run 
> by 'qmaild' but currently is run by 'qscand', so the test should be:
>
> "setuidgid qscand /var/qmail/bin/qmail-scanner-queue.pl -g"
>   
Hi there

Actually the documentation is correct. As
/var/qmail/bin/qmail-scanner-queue.pl is setuid qscand, running
"setuidgid qmaild xxxxx" works fine. It represents a "full test" -
emulating what happens when qmail-smtpd (which runs as qmaild) calls
qmail-scanner.

The presence of those "root" files makes me think you've got a
half-installed Q-S. Remove the lot and do it again. End of the day, the
/var/spool/qscan directory tree is meant to be owned by "qscand"...


-- 
Cheers

Jason Haar
Information Security Manager, Trimble Navigation Ltd.
Phone: +64 3 9635 377 Fax: +64 3 9635 417
PGP Fingerprint: 7A2E 0407 C9A6 CAF6 2B9F 8422 C063 5EBB FE1D 66D1


-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/