I've had enough now, and I want all you ClamAV people to listen up. ClamAV has been continuously and repetitively adjusting configuration options in such a way that breaks anything which is automatically upgraded just stops working.
This is further aggravated by the fact that Exim does not know how to gracefully handle failures of clamav daemon. Is there a reason people feel it necessary to fail startup on old configuration options? Is there a reason it can't at least log deprecations ahead of time to allow people to transition smoothly between versions *without* their entire mail service grinding to a halt? Is there a reason these options have to change at all, or that the configuration parser can't know about old options for n versions and simply gracefully step over them? It's a line-for-line configuration system, startup does not need to fail at all when options are unrecognised! I think ClamAV should be mature enough now to start respecting the users it has and try to behave in a somewhat more stable way. That is all, thank you for your time and the great work. -- Colin Alston <[EMAIL PROTECTED]> _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
