Umut D. <[EMAIL PROTECTED]> writes:
> First of all, consider upgrading to qsheff-2.0-r2... As I wrote before: "I tested this with both qsheff releases: 2.0-r1 (and now 2.0-r2), and 1.0-r5 -" There's no difference between r1 anf r2 in my case. :( >Did you checked all of the configure parameters? This may be the cause: >--enable-local-users Filter local users Of course, I did. This options enables checking of locally relayed messages (IHMO is should be enabled by default), so it has nothing to do with clamd socket operation in my understanding. In fact I testet r1, and r2 with and without this option, with clamd enabled, and with clamd disabled plus CUSTOM_PROG set to clamdscan full path too. No success at all! :( My qsheff is ignoring clamd at all (yes, during the configuration of sources all loooks pretty good - ClamAV enabled, /tmp/clamd socket found etc...). Thanks to well configured qsheff.attach most of attachments carrying viruses are denied, but really I just wanted to run it with clamd. In general it looks to me, like a problem with internal clamd client - simply no communication between qsheff, and clamd - but there's no SINGLE error message in the logs. :( I've already installed newest version of qsheff on four boxes (all are x86 based mailserves) in all cases problem is exactly the same - qsheff simply ignores clamd - or is not delivering any requests for scan to it - at least! Bestest, -Chris --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
