Quoting Dennis Peterson <[EMAIL PROTECTED]>: > Jose-Marcio's elegant J-Chkmail milter has a beautiful option. It will > create a new config file using to the extent possible all your existing > options. (That same tool can generate a clean config file that has all > defaults filled in, too.) If earlier options have changed or have been > disabled the tool will flag them with comments and place them at the top > of the config file where they are clear and obvious.
MailScanner (mailscanner.info) has a similar feature. It is great. I'd love to see clamav have it too (can someone open an enhancement request in the bug tracker for this?) BUT, realize, you still need to check the output. It isn't guaranteed to generate the output you want/need all by itself! I also like the apache "check configuration" option, that reports any obvious errors in the config file. So you can modify the file, then "lint" it for problems before you restart the service. I'd like to see this in clamav too. Note these ideas were already expressed on this list, they are not my ideas, I'm just given two examples of where other packages do this, as examples. I'm hoping someone will open a bug request on these, but if not, I'll probably do it eventually myself, as they are great features that I'd love to see in clamav (and most other packages too). > It is still very important to pause in the installation to read and > understand new options and to determine if the defaults are appropriate > for your environment. Yes, the OP seems to not want this step, but no automatted solution can be guaranteed to work. There is always a need to manually check the configuration and RTFM to be as certain as possible you configured it right (granted, even then, you can make mistakes... Life isn't fair). -- 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
