George Chelidze wrote:
I've run into the same situation. The above makes sense, but only if you're using a local copy of ClamAV to do the scanning. If you're using TCP to connect the milter(s) to a remote bank of ClamAV scanners, the DB version is only read when the milter starts up and never updates.Hello,
Wtexpo.com ClamAV wrote:
Thanks for reply. But I am still confusing. For example, why this replied mail is still scanned with old ClamAV 0.80/601/Mon Nov 22 21:40:21 2004 as its mail header shown. It should be scanned with new ClamAV 0.80/605/Wed Nov 24 22:09:47 2004 right?
May be you can see it at this mail header too if u use mail program like
outlook/outlook express.
Now clear. Seems you haven't notified your daemon after database update. Make sure your freshclam.conf contains line like this:
NotifyClamd /etc/clamd.conf
When connecting via TCP, the milter should periodically re-request the DB version from the remote scanners.
Regards,
Craig. ------ _______________________________________________ http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users
