The issue is that it used the register_hook and run_hooks functionality in an idosyncratic way -- it would register hooks with peculiar names and then (maybe) invoke them later.
With the new qpsmtpd, the list of hook names is fixed -- so this strategy will not work any more.
I see a number of course of action:1) Add an interface into Plugin.pm to allow me to (dynamically) crate new hook names.
2) Add a complete new infrastructure for creating hooks and running them. This seems likely to end up duplicating code.
3) Find some other way to do it.I'm leaning towards option (1) above -- it seems the smallest perturbation to the codebase. Any comments?
Philip
smime.p7s
Description: S/MIME Cryptographic Signature
