Hello,
Since a couple of days I'm using clamd/clamdscan on an OpenBSD
(snapshot/i386) machine. Clamd is started at boot time and clamdscan is
being used by means of a maildrop filter...
if (`/usr/local/bin/clamdscan --mbox --disable-summary --stdout - | grep -c
'FOUND'` == 1)
{
to "$DEFAULT/.SPAM-VIRUS"
}
As can be seen every mail is being tested by clamdscan and every output is
being scanned on the string 'FOUND'. If this string is found the mail is
being send to a maildir named 'SPAM-VIRUS'.
At the moment I'm experiencing two problems:
1.) When not using StreamSaveToDisk, viruses are not always recognized
(known feature);
2.) When using StreamSaveToDisk clamdscan is initiated, does its thing.and
does not die! The result of clamdscan not dying is that after a couple of
hours there are about 40 (or more...) clamdscan processes running. The
end-result is a system in which both Perl and maildrop dumps its cores and
mail is not being delivered.
Is this feature/problem known? If so, is there a solution?
With kind regard,
Björn Ketelaars
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Clamav-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/clamav-users
