On 4/25/2010 6:50 PM, Mark Martinec wrote: > Stefan, > >>> The variable is still declared for compatibility with old config files, >>> but its value is ignored >> >> To be honest, I'm not very happy with the way you handled some of the >> "retired" settings, like e.g. $sa_timeout or $notify_xmailer_header: >> Declaring and completely ignoring those is not the "nice" way to go >> about this, IMHO. It'd like it much more if the amavisd process would >> abort with a warning on startup if these are set, like with >> $warnvirussender, for example. > > I can remove the declaration and let perl abort on seeing such variable > in a config file, or add a warning if a value of such phased-out variable > is different from its old default value. The first choice is easiest > to implement and probably most effective. I'm open to persuasion if > this is a common feeling. > > Mark >
I kind of like ignoring deprecated options with the new behavior noted in RELEASE_NOTES. That way existing installations don't break after upgrade. Too many people update their whole system with yum or such without ever looking at what gets upgraded or what may need changing. -- Noel Jones ------------------------------------------------------------------------------ _______________________________________________ AMaViS-user mailing list AMaViS-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amavis-user AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 AMaViS-HowTos:http://www.amavis.org/howto/
