Jeremy, > On 11/18/07, Mark Martinec <[EMAIL PROTECTED]> wrote: > > On a second thought, preparing a policy bank with required > > settings (like suppressing quarantine, special templates, > > destiny* settings, ..) and having it pre-configured in the normal > > config file, then loaded when needed by a custom hook - could > > achieve most if not all of your needs. > > Yes, I think I see what you mean. In fact I'd probably have my policy > bank definition at the top of my included file that contains the > custom hook code, just to keep it all in one place. > > > Just call: > > Amavis::load_policy_bank($some_bank_name) > > as needed from a custom hook. > > Thanks a lot for your help. I'll give it a go now.
Just wanted to check: were you able to achieve what you intended? In my current code I moved the custom hook initialization call (the Amavis::Custom->new) slightly earlier, so that loading a policy bank from there can influence a few more things, just in case someone would need it (like OS fingerprinting settings, local_domains). Mark ------------------------------------------------------------------------- SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 _______________________________________________ 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/
