Gary wrote:
> $policy_bank{'MYNETS'} = { # clients in @mynetworks
> spam_lovers_maps => [[qw( .example.com .example.net )]],
> final_spam_destiny => D_BOUNCE,
> spam_dsn_cutoff_level_maps => 9999,
> };
Mark, this works in 2.4.2, but no DSN is created in 2.4.3.
Is this the reason?:
- when loading a policy bank, its entries of type hash are now merged with
existing hash, a key at a time; previously a newly loaded hash replaced
a previous one entirely;
If so, how should the policy bank read to achieve the desired
behavior?
Gary V
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
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/