Hi, I'm running clamd 0.8 under Windows XP Pro, my own compile under Cygwin (it compiles almost out of the box with shared libraries and everything working fine). I've has version 0.75 before 0.8 working alongside with clamsmptd to catch viruses in a mail server with low traffic, only 4 or 5 viruses are detected each day; this is all working fine and it has been working for the last 3 months.
My configuration is clamd using a socket, the socket is used by clamsmtpd and clamdwatch.pl, in fact the Windows service I made is a small script that starts clamd and runs clamdwatch.pl every 3 minutes. Now my question: why is clamd listening on a TCP port (only one port but the port number varies) and also on 1,467 UDP ports? I found this by accident, trying to run TrippLite's PowerAlert the program reported that the port was in use, I checked and clamd was using that TCP port. So I checked some more, with Sysinternals' tcpvcon to see what ports was the clamd process using and the list is really big. I didn't expect clamd to be using any port (yes I checked the documentation and FAQ). I also checked that the code is the original code, using the signature, no problem there. I haven't checked on the other installation I have, under Solaris, because there I'm using MailScanner and that doesn't use clamd. Thanks for any information you can provide. -- René Berber _______________________________________________ http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users
