On 10/31/06 9:56 PM, "Ask Bjørn Hansen" <[EMAIL PROTECTED]> wrote:
> > On Oct 31, 2006, at 6:38 PM, John Peacock wrote: > >> The issue is that this plugin requires a patch to the core >> to actually implement the skip part, which might be fine, but there >> might also >> be a more elegant way to handle this that I can't see right now. > > I'm not sure what it would look like; but it'd be nice to have an API > for querying and changing the list of configured plugins. The API > should let you change them for the connection (changing them globally > would be hard or impossible, so that's less important). > When reading the patch I thought about what it would take to fiddle the plugin calling to pass in custom parameters as the hooks for that plugin are called. An example: I have the default configuration for spamassassin in the config/plugins file with the parameters for what gets tagged and dropped. Suppose that I have a plug-in that hooks on rcpt. If a specific recipient has the requirement of needing different parameters, it would be quite nice if the hook on rcpt could change the behavior of plug-ins including which plug-ins get called. I guess I'm suggesting that the API for changing plug-ins on the fly include the ability to pass args to the plug-ins as they're called. With a little luck, this could probably aid Gavin's usage of per-user conditioning. peter
