> So yes, if you change @mynetworks_maps in amavisd.conf, you also > need to re-evaluate the > @client_ipaddr_policy = map { $_ => 'MYNETS' } @mynetworks_maps; > > But, if you only change a value of @mynetworks without changing > the @mynetworks_maps, then the @client_ipaddr_policy is still valid.
I'll add the following to the documentation in 2.6.3 release notes (to come out with a future version): COMPATIBILITY WITH 2.6.2 - please see a note below about having to explitly re-assign the @client_ipaddr_policy list if @mynetworks_maps (not the @mynetworks) is changed in amavisd.conf; [...] The default setting retains backwards compatibility: @client_ipaddr_policy = map { $_ => 'MYNETS' } @mynetworks_maps; but please keep in mind that this assignment is made during startup before evaluating a config file, so if amavisd.conf changes the @mynetworks_maps list, the assignment to @client_ipaddr_policy needs to be re-evaluated to retain a desired default. This is not necessary when @mynetworks_maps is left untouched but only its component @mynetworks is changed. Mark ------------------------------------------------------------------------------ Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensign option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects _______________________________________________ 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/