Re: disabling plugins

2008-04-09 Thread Matt Sergeant
Hanno Hecker wrote: seems like a rather heavy hammer, which can be influenced in a very bizarre cross connection manner. Except for using this before the 'connect' hook, I don't see where. But ...(thinking loud) maybe use the plugins_loaded() and ## Qpsmtpd.pm, run_continuation(): $self->

Re: disabling plugins

2008-04-09 Thread Hanno Hecker
On Wed, 09 Apr 2008 02:29:04 -0400 Matt Sergeant <[EMAIL PROTECTED]> wrote: > Hanno Hecker wrote: > > this patch sets a way to disable any loaded plugin(s) for the current > > client. I'm not going to commit this before Ask released 0.43. Matt [...] > I'm not sure this is the right way to do this

Re: disabling plugins

2008-04-08 Thread Matt Sergeant
Hanno Hecker wrote: Hi, this patch sets a way to disable any loaded plugin(s) for the current client. I'm not going to commit this before Ask released 0.43. Matt (and others with high traffic) should be ok with the one more line next unless $code->{run}; per hook. The plugins_loaded() should

disabling plugins

2008-04-08 Thread Hanno Hecker
Hi, this patch sets a way to disable any loaded plugin(s) for the current client. I'm not going to commit this before Ask released 0.43. Matt (and others with high traffic) should be ok with the one more line next unless $code->{run}; per hook. The plugins_loaded() should be in to Qpsmtpd.pm. A