Hello,
I've just installed qmail-scanner-2.06 on top of netqmail-1.06. Q-S
has successfully detected clamd 0.93.3 and spamd (fast) 3.2.5. It
_appears_ to be functioning well when sending and receiving plain text
email, but I find the following if I test the installation with
test_insallation.sh, or attempted to replicate it with an attachment
or something similar that would invoke clamd, I find the following:
test_installation.sh:
Sending standard test message - no viruses...
done!
Sending eicar test virus - should be caught by perlscanner module...
qmail-inject: fatal: qq temporary problem (#4.3.0)
Bad error. qmail-inject died
(I do receive the first test email intact.)
qmail-queue.log:
Thu, 02 Jul 2009 00:40:20 EDT:24660: ini_sc: start scanning
Thu, 02 Jul 2009 00:40:20 EDT:24660: ini_sc: recursively scan the
directory /var/spool/qscan/tmp/my-hostname124650962056624660/
Thu, 02 Jul 2009 00:40:20 EDT:24660: scanloop(virus): starting scan of
directory "/var/spool/qscan/tmp/my-hostname124650962056624660"...
Thu, 02 Jul 2009 00:40:20 EDT:24660: scanloop:
scanner=clamdscan_scanner,plain_text_msg=0
Thu, 02 Jul 2009 00:40:20 EDT:24660: clamdscan: starting scan of
directory "/var/spool/qscan/tmp/my-hostname124650962056624660"...
Thu, 02 Jul 2009 00:40:20 EDT:24660: run /usr/bin/clamdscan
--no-summary /var/spool/qscan/tmp/my-hostname124650962056624660 2>&1
Thu, 02 Jul 2009 00:40:20 EDT:24660: --output of clamdscan was:
/var/spool/qscan/tmp/my-hostname124650962056624660: Access denied. ERROR
--
Thu, 02 Jul 2009 00:40:20 EDT:24660: error_condition:
X-Qmail-Scanner-2.06: clamdscan: corrupt or unknown clamd scanner
error or memory/resource/perms problem - exit status 512/2
syslog:
Jul 2 00:40:20 my-hostname qmail-scanner-queue.pl:
qmail-scanner[24651]: Clear:RC:1(127.0.0.1): 0.012001 318
postmaster@my-d... postmaster@my-d...
Qmail-Scanner_test_(1/4):_inoffensive_message
<
20090702044020.24650.qmail@my-d...>
orig-my-hostname124650962056624651:318
1246509620.24653-0.my-hostname:68
Jul 2 00:40:20 my-hostname clamd[24430]: No stats for Database check
- forcing reload
Jul 2 00:40:20 my-hostname qmail-scanner-queue.pl:
X-Qmail-Scanner-2.06:[my-hostname124650962056624660] clamdscan:
corrupt or unknown clamd scanner error or memory/resource/perms
problem - exit status 512/2
Jul 2 00:40:21 my-hostname clamd[24430]: Reading databases from
/usr/share/clamav
Jul 2 00:40:25 my-hostname clamd[24430]: Database correctly reloaded
(581968 signatures)
I've looked around, and it appears that the most common explanation
for this is that clamd is not running as qscand, but it is. I must
note that I do not have perl installed with suid, instead I'm running
Q-S through the wrapper as specified, and it passes all of the tests.
However, I am not entirely convinced that the wrapper is working as it
should. I had some other permission issues when first starting qmail
that affected even plaintext mail, permission failures on certain
files in /var/spool/qscan, which seemed to be resolved by chown'ing
them to qmaild:nofiles. The wrapper sits in /var/qmail/bin, is owned
by qscand, has the permission mask 6755; qmail-scanner-queue.pl is the
same except its permission mask is 0755.
I would just install rebuild perl with suid, but this server runs
Linux from Scratch (Yes, I am insane, but this is just a proof of
concept install.) , which makes installing things rather tedious, and
as perl is pretty critical to a lot of things, I'd rather not risk
breaking it if it can be at all avoided.
So, is this really a suid problem, or is it just permissions
somewhere? I've checked everything against a previous qmail install
and people with similar experiences in mailing lists, and I can't seem
to find anything that helps.
Any help would be much appreciated.
Thanks in advance.
------------------------------------------------------------------------------
_______________________________________________
Qmail-scanner-general mailing list
Qmail-scanner-general@list...
https://lists.sourceforge.net/lists/listinfo/qmail-scanner-general
opensubscriber is not affiliated with the authors of this message nor responsible for its content.