On Wednesday 11 Feb 2004 11:45 pm, james nelson wrote: > Clamav-milter included with clamd .65 > RH9 > Scanning both incomming and outgoing > The primary smtp has niether the milter or clamd. It uses the milter and > clamd installed on server2. Connecting via tcp sockets. > The server running clamd and clamav-milter never breaks a sweat cpu stress > wise. However, for some reason the connection for user send mail to the > main server takes a longer than normal time. Is there not a setting to > have the mail server accept the message and close the client connection, > then scan it, then if necessary send the bounce back? As it sits it is > leaving the connection open while it waits to do the scan... This is not > good from a users point of view.
At it stands this is the way clamd works. There is a way round that, but it involves moving from TCP sockets to UNIX domain sockets, and enabling the --quarantine-dir option. -Nigel -- Nigel Horne. Arranger, Composer, Typesetter. NJH Music, Barnsley, UK. ICQ#20252325 [EMAIL PROTECTED] http://www.bandsman.co.uk ------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click _______________________________________________ Clamav-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/clamav-users
