On Jun 13, 6:44pm, John P. Rouillard wrote:
>
> I am wondering what problem you are trying to solve.
We both really need to be able to have some policies that are getting
more complex than are currently available, and that probably will
not be available except through functions we make available.
In particular, we need to be able to have different policies based
on where the request came from and/or who the request is acting on
(the user being subscribed, etc). But I'd like to be able to put
in whatever I think necessary on a list by list basis, and have
all of the configuration for a given list in one place-- the
configuration file.
> What you suggest seems to be a bit out of the capabilities of most
> people using majordomo.
Yup. I very much see this as a specialized sort of thing, and I
really want to be able to hide it from those who don't want to
know.
(I just wanted to clarify these things now, I'll need to go over the
rest of the details later...)
> One way to solve this would be to use the writeconfig code with a
> optional keyword. For example:
>
> writeconfig bblisa <password> template-private template-open
This looks fine to me. I'm not certain if it is more straightforward
than what I mentioned (The details are clear to ME, I thought of them)
but if this makes more sense to others, I'll go for it.
laura de leon
References:
|
|
