Victor Duchovni a écrit :
> On Sun, Mar 08, 2009 at 03:07:16AM +0100, mouss wrote:
>
>> Victor Duchovni a ?crit :
>>> On Sat, Mar 07, 2009 at 07:51:13PM +0100, mouss wrote:
>>>
>>>> BTW, is there any reason why one can't do
>>>>
>>>> joepipe ... pipe
>>>> flags=${joe_flags}
>>>> user=${joe_user}
>>>> args=${joe_command} ${joe_options}
>>> The reason is that these arguments are not and should not be subject to
>>> main.cf macro substitution.
>> well, the question was why it is so. I mean what is the risk exactly?
>> after all, one can generate master.cf with a script that takes
>> definitions from main.cf (or from elsewhere). but I'm sure I'm missing
>> something. thus the question.
>
> Well, consider the syntax of "args", and think about how main.cf macro
> expansion would interact with it.
>
yes, this would make it impossible to add new macros for pipe without
risking someone using them as custom variables.
the idea I was thinking of would be something like
listmanager ....
user=${listmanager_user}
...
then let the admin chose his listmanager and define the parameters in
main.cf instead of touching master.cf. but this can be done by
generating master.cf instead. after all, postconf -e can't be used with
custom vars, so edition is needed anyway.
thanks!
