Andy Fiddaman wrote:
<snip>Sounds like a good idea. Except that sendmail controls are not as fine grained as the milter. The milter may be configured to scan a certain subset of email traffic and therefore the sendmail values would not be representative of the true maximum you want to be running at once.
What I actually want to limit on my boxes is the number of concurrent scans,
not the number of milter threads since 1 thread == 1 incoming email (over
the initial signal threads etc.) and sendmail can control that itself.
Other people may have different priorities.
The way I see it, your main benefit in moving the logic closer to the actual scanning is in eliminating slow DATA senders from counting in the tally.
Concurrent scans can be controlled via clamd MaxThreads option I believe.
I'm currently using something similar to the code below. Because each thread
<snip> Would love a patch if you had one available.....
-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g. Take an Oracle 10g class now, and we'll give you the exam FREE. http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
_______________________________________________
Clamav-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/clamav-users
