> The syntax of many settings in newer versions of amavisd-new has > changed but some settings from older versions can be used.
I'd like to think that practically all old config files (as far back as amavisd-new-20030314 or even earlier) still work with new versions of amavisd-new. I go to great lengths to retain upwards compatibility of config files. Syntactically they should be 100% compatible, while there are some minor semantical differences as documented in release notes, and of course new features fall to their default settings in absence of explicit controls. > Most older config files can be used with > newer versions of amavisd-new. Quite often you can get a new version > running by simply replacing the amavisd-new executable. At most I have > had to upgrade or install some programs on my system (amavisd-new will > tell you what it needs) when upgrading. Indeed. Keeping Perl modules recent is a must when upgrading amavisd-new, but update config files when time permits. Newer config files are cleaner and/or illustrate new features, which is the main reason that porting local config file changes to newer baseline config file is a good idea (but not a requirement). But of course I'm not talking about Debian port. Mark _______________________________________________ AMaViS-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/amavis-user AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 AMaViS-HowTos:http://www.amavis.org/howto/
