Quoting Simon Hobson <[email protected]>:
As pointed out, it was ***NOT*** sent to people running the servers - you've done the equivalent of Ford putting a notice up in it's corporate reception and expecting all owners to know about it. Had I known 6 months ago rather than this morning, I'd not be complaining for the simple reason that I'd have been able to deal with it.
The only solution for this is to: 1) Require everyone who used clamav to register and provide contact info (won't run if you don't) 2) Send out periodic messages/calls to catch invalidated registration data, and hire an investigator to track down the problems. 3) Require that when an important notification is sent out, that everyone replies to confirm they received it and understand the content. If not, hire people to follow up with those who either don't respond or don't understand the content. Do we really want this? Do we really believe this is practical?
For half the day I've been forced to detect no virus's. Now I'm only detecting the ones known about up till yesterday.
The first is because you don't keep up with the news about products you use. The second is because you refuse to upgrade. Both are, to put it bluntly, your fault and your problem. Yes, you can't get new definitions now, but at least you know that. This is better than if you _thought_ you were getting new updates and were not, is it not? -- Eric Rostetter The Department of Physics The University of Texas at Austin Go Longhorns! _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
