-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'm seeing a ton of the following in /var/log/messages when using clamav-milter 0.92:
clamav-01: Operation not permitted connect: Operation not permitted clamav-01: Operation not permitted connect: Operation not permitted clamav-01: Operation not permitted clamav-01: Operation not permitted connect: Operation not permitted clamav-01: Operation not permitted clamav-01: Operation not permitted clamav-01: Operation not permitted connect: Operation not permitted connect: Operation not permitted clamav-01: Operation not permitted connect: Operation not permitted clamav-01: Operation not permitted connect: Operation not permitted clamav-01, above, is one of 10 machines used in a clamd cluster accessed by 12 filter servers. The machine that I'm seeing this on is a fresh install of the following: FreeBSD 6.2 postfix 2.4.6,1 (latest from ports) clamav-milter 0.92 All of the clamd servers were upgraded last week to clamd 0.92. The other 11 filter servers are all running clamav-milter 0.91.2. It appears that mail is still being scanned as it passes through the filter machine, but I'm rather disturbed by these messages that I'm seeing, especially because they are completely ambiguous as to what the problem exactly is. Has anyone else run into this since the upgrade to 0.92? Jay Deiman [EMAIL PROTECTED] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHcs1eQ0lr+ZVKSBgRAo/LAJ9bpe5gt/a01nyCRWF+Qfo3cBPhrQCdF4cc YKRQ5ZIxUJrnAkCstxEAuT8= =Eo27 -----END PGP SIGNATURE----- _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://lurker.clamav.net/list/clamav-users.html
