When upgrading to QMail-Scanner 1.25st, you'll encounter permissions error in your qmail-smtp logs asking you to run qmail-scanner-queue.pl -z Reproducible: Always Steps to Reproduce: 1.Use a working qmail/qmail-scanner installation (any versions) 2.emerge -u qmail-scanner 3.watch qmail-smtp logs Actual Results: If you simply emerge -u qmail-scanner some permissions are changed and prevent mail scanning and showing permissions errors in logs like this: [quote] @40000000421734ab190ff654 X-Qmail-Scanner-1.25st: [coyote110881705769417544] /var/spool/qmailscan/tmp/coyote110881705769417544 exists - try again later... @40000000421734ab194bb734 /bin/rm: cannot remove `/var/spool/qmailscan/tmp/coyote110881705769417544/': Permission denied [/quote] The file does not exist but QMail-scanner can't access to this dir. Expected Results: When a new mail come in, QMail-Scanner would scan it and deliver it to mailboxes. I use QMail-scanner for a long time now. First time I've installed with Gentoo everythings works fine... But from version 1.22, QMail-Scanner seems to have serious problems with permission sets during emerging on /var/spool/qmailscan directory and contents. Each time, I search for registered bugs or help in forums in order to resolv my problems and get mail delivered as soon as possible after update. After 3 installations (1.22, 1.23, 1.24), I've saved in safe place perms list for the /var/spool/qmailscan directory and content. After upgrading to QMail- Scanner-1.25st, I have to reset permissions as usual... Theses files and dirs have wrong perms after update: - /var/spool/qmailscan/qmail-queue.log - /var/spool/qmailscan/qmail-scanner-queue-version.txt - /var/spool/qmailscan/quarantine/ - /var/spool/qmailscan/quarantine-attachments.[db|txt] - /var/spool/qmailscan/tmp/ - /var/spool/qmailscan/working/ If you won't have any problems with you QMail after that, you need to change perms like this: coyote spool # ls qmailscan/ total 61476 drwxrwxr-x 7 qscand qscand 4096 d
When upgrading to QMail-Scanner 1.25st, you'll encounter permissions error in your qmail-smtp logs asking you to run qmail-scanner-queue.pl -z Reproducible: Always Steps to Reproduce: 1.Use a working qmail/qmail-scanner installation (any versions) 2.emerge -u qmail-scanner 3.watch qmail-smtp logs Actual Results: If you simply emerge -u qmail-scanner some permissions are changed and prevent mail scanning and showing permissions errors in logs like this: [quote] @40000000421734ab190ff654 X-Qmail-Scanner-1.25st: [coyote110881705769417544] /var/spool/qmailscan/tmp/coyote110881705769417544 exists - try again later... @40000000421734ab194bb734 /bin/rm: cannot remove `/var/spool/qmailscan/tmp/coyote110881705769417544/': Permission denied [/quote] The file does not exist but QMail-scanner can't access to this dir. Expected Results: When a new mail come in, QMail-Scanner would scan it and deliver it to mailboxes. I use QMail-scanner for a long time now. First time I've installed with Gentoo everythings works fine... But from version 1.22, QMail-Scanner seems to have serious problems with permission sets during emerging on /var/spool/qmailscan directory and contents. Each time, I search for registered bugs or help in forums in order to resolv my problems and get mail delivered as soon as possible after update. After 3 installations (1.22, 1.23, 1.24), I've saved in safe place perms list for the /var/spool/qmailscan directory and content. After upgrading to QMail- Scanner-1.25st, I have to reset permissions as usual... Theses files and dirs have wrong perms after update: - /var/spool/qmailscan/qmail-queue.log - /var/spool/qmailscan/qmail-scanner-queue-version.txt - /var/spool/qmailscan/quarantine/ - /var/spool/qmailscan/quarantine-attachments.[db|txt] - /var/spool/qmailscan/tmp/ - /var/spool/qmailscan/working/ If you won't have any problems with you QMail after that, you need to change perms like this: coyote spool # ls qmailscan/ total 61476 drwxrwxr-x 7 qscand qscand 4096 déc 22 13:00 ./ drwxr-xr-x 6 root root 4096 nov 13 13:10 ../ drwxr-x--- 5 qscand qscand 4096 déc 21 22:29 archive/ -rw-r--r-- 1 root root 0 déc 22 11:53 .keep -rw------- 1 qscand qscand 62866 déc 22 12:12 qmail-queue.log -rw-r--r-- 1 qscand qscand 62 déc 22 12:12 qmail-scanner-queue- version.txt drwxrwx--- 5 qmaild qscand 4096 aoû 13 10:17 quarantine/ -rw-r--r-- 1 qmaild qscand 12288 déc 22 13:00 quarantine-attachments.db -rw-r--r-- 1 qmaild qscand 7414 déc 22 11:53 quarantine-attachments.txt -rw-r--r-- 1 qmaild qscand 0 déc 22 11:53 quarantine.log drwx------ 2 qscand qscand 4096 déc 14 19:19 .spamassassin/ drwxrw-rw- 2 qmaild qmail 4096 déc 22 14:05 tmp/ lrwxrwxrwx 1 qscand qscand 31 aoû 13 10:17 viruses - > /var/spool/qmailscan/quarantine/ lrwxrwxrwx 1 root root 14 déc 22 11:53 viruses.log -> quarantine.log drwxrwx--- 5 qscand nofiles 4096 aoû 13 10:17 working/ Also, you need to remove /etc/cron.daily/qmail-scanner to prevent automatic prems correction with the 'qmail-scanner-queue.pl -z' That's all !
Ummmmmmm Very interesting if you would please show us the permissions it is setting on these files ... I will be more then willing to post my permissions if you would like I have not had a problem with updating qmail-scanner in a while back in 1.2.0 I believe was last time. So post your original permissions that are being set when updating and I will post mine and you can compare other then that I dont see the problem and I am sure other users arent seeing it seeing your only one reporting.
I do have the same problem with a fresh install of qmail and qmail scanner. I played around a little bit and changed :allow,QMAILQUEUE="/var/qmail/bin/qmail-scanner-queue.pl" to :allow,QMAILQUEUE="/var/qmail/bin/qmail-scanner-queue" as mentioned in http://forums.gentoo.org/viewtopic-t-288196-highlight-qmailscanner.html and i did an chown -R qscand:qscand /var/spool/qmailscan . After that i increasd the memory limit in /var/qmail/control/conf-common SOFTLIMIT_OPTS="-m 80000000" . But this was not the complet fix .. I author of the package suggest to use softlimit -a instead of im ? found in http://qmail-scanner.sourceforge.net/FAQ.php. Now it works for me Remember to set the memory limit to your needed system settings !!!
I have tested this over and over again on my test server and have found no evidence supporting your claim, this will be marked invalid. The permissions will stay the same.
