At 9:17 +0800 12-07-2007, Rohan Carly wrote:
>I'm having trouble with the final test suggested by the qmail-scanner
>configure script. I get the "permission denied" error as below.

>If you see the error "Can't do setuid", or "Permission denied", then
>refer to the FAQ.
>
>(e.g.  "setuidgid qmaild /var/qmail/bin/qmail-scanner-queue.pl -g")
>
>
>That's it! To report success:
>
>     % (echo 'First M. Last'; cat SYSDEF)|mail
>[EMAIL PROTECTED]
>Replace First M. Last with your name.
>[EMAIL PROTECTED] qmail-scanner-2.01]# setuidgid qmaild
>/var/qmail/bin/qmail-scanner-queue.pl -g
>perlscanner: generate new DB file from
>/var/spool/qscan/quarantine-events.txt
>X-Qmail-Scanner-2.01:[] cannot open for write
>/var/spool/qscan/quarantine-events.db.tmp - Permission denied
>[EMAIL PROTECTED] qmail-scanner-2.01]# d -l /var/spool/qscan
>total 28
>-rw-rw---- 1 qscand qscand    21 2007-07-12 09:02
>qmail-scanner-queue-version.txt
>-rw-r----- 1 qscand qscand 12288 2007-07-12 09:02 quarantine-events.db
>-rw-rw---- 1 root   root    9168 2007-07-11 23:48 quarantine-events.txt
>-rw-rw---- 1 root   root       0 2007-07-12 09:02 quarantine.log

Hi Rohan

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"

Regards

ST

-------------------------------------------------------------------------
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/
_______________________________________________
Qmail-scanner-general mailing list
Qmail-scanner-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/qmail-scanner-general

Reply via email to