Ok, the problem was /usr/bin/reformime
when qmail-scanner runs it to unpack the email it puts everything
in the tmp/xxx.com. directory owned by root and group qmail.
My hack solution was to make a copy or reformime called reformime2 and
change the owner and group on that one. Then I went in
Ok, the problem was /usr/bin/reformime
when qmail-scanner runs it to unpack the email it puts everything
in the tmp/xxx.com. directory owned by root and group qmail.
My hack solution was to make a copy or reformime called reformime2 and
change the owner and group on that one. Then I went in
Hi,
Ownership:
-rwsr-xr-x 1 qscand qscand 86156 Jul 11 09:26 qmail-scanner-queue.pl
The weird thing is that the directory created in /var/spool/qmailscan/tmp
is owned by qscand... just the files it places in there have the wrong
ownership.
I see the comment in qmail-scanner-queue.pl where it
Hi,
I've been looking everywhere for a solution to this problem.
I am seeing the same "widely reported" error where clamd can't
read the files created by qmail-scanner. I have clamd running
as qscand and I've got the latest qmail-scanner 1.22.
I have confirmed that the tmp directory is writabl
