Quoting Charles Gregory <[EMAIL PROTECTED]>: > A lot of people seem to think it is 'proper' for a mis-configured server > to just "die" or fail to start.
Yes, a lot of people do... :) > This makes sense when the server has an > *obvious* function/effect and its failure will be noted by interruptions > in end-user performance/service. But when a mail filter 'fails', mail > goes through UNFILTERED, and UNNOTICED. This is just WRONG. Sorry, it is. The OP was complaining that it did cause the mailer (exim) to stop. And if the config is wrong, and it continues to run with the wrong config, it will possibly let mail through UNFILTERED and UNNOTICED. Why isn't this just WRONG? Sorry, it is. If you want better support, sign up for "Certified ClamAV Support"... While this thread has brought up a valid complaint (it doesn't log an error when the config file is bad and it is started in daemon mode), the rest of the thread is just a waste of time... People who don't understand why you don't do (untested) automatic updates on a production server just don't get it, and no continuation of this thread will help them get it. Hence I plan to stop responding with this message. I'm quite sure SourceFire and the clamav developers know how to handle these things properly, and will do so when the 1.0 release comes out (within the 1.x release tree). People who don't understand this just don't get it, and never will. -- 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
