Hi There,
We use sendmail with clam & spamassassin (clamav-milter + spamass-milter).
When a message is routed across several MX servers to final destination, it is scanned by clamd multiple times on each MX server. In spamassassin we can configure spamass-milter with the -i option NOT to scan twice a message when goes from one MX server to another.
To my understanding clamav-milter has no option to recognize trusted IPs, and scans every message regardless of the fact that is coming from a trusted IP or it has been scanned already on another (trusted) server.
MX servers within the same organization may indeed be used as a cheap load balancing solution by using a trusted IP configuration option in clamav-milter or finding another (trusted & secure!) mechanism to identify whether mail has been already scanned. Regardless of load balancing, resources are waisted when a message transits via several MX servers where clamav-milter is installed.
What about adding a "trusted IP" option in clamav-milter (as in spamassassin's spamass-milter) :
-i networks
Ignores messages if the originating IP is in the network(s)
listed. The message will be passed through without calling cla-
mad at all. networks is a comma-separated list, where each
element can be either an IP address (nnn.nnn.nnn.nnn), a CIDR
network (nnn.nnn.nnn.nnn/nn), or a network/netmask pair
(nnn.nnn.nnn.nnn/nnn.nnn.nnn.nnn). Multiple -i flags will append
to the list.Thanks for your consideration, and keep on with the good work.
Ron
--
Ron Norton, NEXUS-IBA support, PO Box 11028, 20110 Milano, Italy
-------------------------------------------------------
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
