> I don't quite see why a config hook plugin should have to know from
> which plugin or hook it is called.
See my posting yesterday. With every new plugin we are running into the
danger of having collisions within config names. This could be solved
by either prepending 'pluginname_' to each config name, or as i would
prefer by giving both informations seperated to the conf plugin. This
would also allow my suggestion of having ~qpsmtpd/config/plugin/conffile.
> So you can do something like:
>
> $self->qp->config("my_plugin/category1/parameter2",
> {
> plugin => ref($self),
> hook => "rcpt",
> rcpt => $rcpt,
> foo => [ qw(baz gazonk) ],
> }
> );
I don't see why i should have to add plugin and hook if the
$self->qp->config subroutine could do this for me. I think your solution
is more complicated.
> There are at least 2: http_config and per_recipient_config.
per_recipient_config patch does not work with latest cvs. I tried
changing it to the latest needs but some patched parts in qpsmtpd
have been heavily changed (e.g. a former single subroutine splitted
in two), so i had no luck yet of getting the patch attached.
I'm just looking for a generic and powerful solution for the whole
problem of configuration. This could after all mean that some old
plugins might need to be modified (your solution above will in
fact need modification in many plugins!).
-kju
--
It's an insane world, but i'm proud to be a part of it. -- Bill Hicks
