On Tue, 3 Feb 2004, [UTF-8] Kriе║tof Petr wrote: KP>I decided to switch from LocalSocket to TcpSocket on clamd server KP>for windows users can start testing windows client from their Win KP>workstations. KP> KP>But this option is exclusive with --quarantine-dir on clamav-milter. KP> KP>Is there some technical reason or clamav simply reach his design limit KP>and new features are patched 'head over heel' style?
I've implemented this option to solve two things: a) To have quarantine b) To have mail files processed only after they completely came from the network. Without qurantine-dir I had to have very big timeout value in clamd and it did not save me from timeouts. My first implementation was able to scan over TCP socket but this could be done only with local files because I've used SCAN clamd command instead of STREAM. Nigel Horne said and I agreed that disabling TCP mode would make local-only limitation more clear for end-users. There are two ways to reimplement TCP mode with quarantine-dir: a) As this was done in my first version. Easy but not so good. b) Save file in quarantine, then use STREAM to send it to clamd. A little harder to implement and less efficient (clamd need to save this file before scanning to process nested elements). But this would allow to have milter and clamd on different servers. Also you can have two separate clamd running on the same server - one for milter and one for Windoze. misha. ------------------------------------------------------- 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
