I guess it's a bug in the perl script you two are using, it doesn't handle high port numbers correctly.
-trog On Thu, 2005-01-27 at 13:25 -0800, exo dia wrote: > Thank you Paul, I just made these changes to my clamd.conf, and > restarted clamd. Hopefully this will correct (work around?) the > problem! What do these settings mean (I haven't dug that far into the > source yet)? > > -ed > > On Thu, 27 Jan 2005 22:17:26 +0100, Paul Bijnens > <[EMAIL PROTECTED]> wrote: > > exo dia wrote: > > > > > I am piping e-mail via procmail, I pipe the e-mail to clamdscan > > > through a shell script (no milter or anything being used.) This is > > > the original version of the script I am using: > > > http://www.everysoft.com/clamfilter.pl.txt > > > > > > > I noticed the same, using a similar perlscript via procmail. > > > > I added, as trog suggested the following lines to clamd.conf > > > > StreamMinPort 1024 > > StreamMaxPort 2048 > > > > And since then (about 5 hours ago) not seen any error anymore. > > Before I saw the error 5-10 per hour.
signature.asc
Description: This is a digitally signed message part
_______________________________________________ http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users
