Re: Permission denied on /var/spool/qmailscan/tmp with 2.01st

Salvatore Toribio <[email protected]>
Newsgroups gmane.mail.qmail.scanner
Message-ID <a06230909c084f8feb6fa@[193.43.129.133]>
At 9:23 -0400 8-05-2006, Richard Santiago wrote:
>Hi,
>
>For some reason, I get this message on the mail logs when I activate 
>the new qmail-scanner-2.01-st version:
>
>X-Qmail-Scanner-2.01st: [] cannot create /var/spool/qmailscan/tmp - 
>Permission denied
>
>This dir is already created and owned by qscand as I'm using the 
>same structure from the previous version (1.25st). 
>
>Thanks for your help.
>

I think you need to change some ownerships and permissions, as now 
qscand need a differente umask. You can try to remove the tmp dir so 
qmail-scanner recreates it again, or look below for the actual 
ownerships and permissions:

drwxr-xr-x    6 qscand   qscand       4096 May  7 04:02 qmailscan/

drwxrwx---    6 qscand   qscand       4096 May  7 04:02 qscan/



drwxrwx---    5 qscand   qscand       4096 Mar 18 19:47 archives/
-rwxr-x---    1 qscand   qscand       1381 Apr 16 11:24 log-report.sh*
-rw-rw----    1 qscand   qscand    1569404 May  8 15:36 qmail-queue.log
-rw-rw----    1 qscand   qscand         85 Apr 23 12:18 
qmail-scanner-queue-version.txt
lrwxrwxrwx    1 qscand   qscand         37 Apr 13 13:17 
qmail-scanner-queue.pl -> /var/qmail/bin/qmail-scanner-queue.pl*
drwxrwx---    5 qscand   qscand       4096 Mar 18 19:47 quarantine/
-rw-r-----    1 qscand   qscand      12288 Apr 17 11:25 quarantine-events.db
-rw-rw----    1 qscand   qscand      10192 Mar 20 09:22 quarantine-events.txt
-rw-rw----    1 qscand   qscand       2782 May  8 15:05 quarantine.log
-rw-r-----    1 qscand   qscand      12288 Mar 20 09:30 settings_per_domain.db
-rw-r-----    1 qscand   qscand       3681 Mar 20 09:33 settings_per_domain.txt
drwxr-x---    2 qscand   qscand       4096 May  8 15:36 tmp/
drwxrwx---    5 qscand   qscand       4096 Mar 18 19:47 working/


Regards

ST
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.