On Wed Apr 07 2010 22:47:27 GMT+0200 (CET) David F. Skoll <[email protected]> wrote:
> OK. That's bad. Really bad. It's an enormous problem for us. > > We have some customers (I don't know exactly how many) who are > running ClamAV <= 0.94.2. When this hits the ether, their mail > servers will tempfail all mail because clamd will error out. > > This might even put us in legal difficulties: some of our customers > have contracts with us in which we assert our software has no "kill > switch" that can disable mail delivery. Thanks to the fine ClamAV > developers, we've been shipping a kill-switch for years. Do your customers use the public ClamAV mirror infrastructure? If they do, and also use old ClamAV versions, they're (or will be) making harm to our infrastructure and the other users of ClamAV who run the latest releases. This is because the old versions of freshclam fail to apply some incremental updates and need to download entire database files as described in the original announcement: http://lists.clamav.net/lurker/message/20091006.143601.d27bbd20.en.html If they don't and *you* provide them with some private database mirror (what you should really be doing!), then I see no problem - you can simply keep redirecting (with some httpd rule or so) their installations to a specific daily.cvd file which works for them until they get upgraded to some recent release. We can't do that globally because the diversity of software run by our mirrors makes this solution ineffective. Regards, -- oo ..... Tomasz Kojm <[email protected]> (\/)\......... http://www.ClamAV.net/gpg/tkojm.gpg \..........._ 0DCA5A08407D5288279DB43454822DC8985A444B //\ /\ Wed Apr 7 23:08:57 CEST 2010 _______________________________________________ http://lurker.clamav.net/list/clamav-devel.html Please submit your patches to our Bugzilla: http://bugs.clamav.net
