btb:
[ Charset windows-1252 converted... ]
> On 2016.11.15 11.44, Wietse Venema wrote:
> > btb:
> >> since parameters can be user defined, i think it would be good if
> >> the documentation stated this, maybe in postconf(5)? it would
> >> alleviate guessing games.
> >>
> >> possibly something lik
On 2016.11.15 11.44, Wietse Venema wrote:
> btb:
>> since parameters can be user defined, i think it would be good if
>> the documentation stated this, maybe in postconf(5)? it would
>> alleviate guessing games.
>>
>> possibly something like:
>>
>> Postfix main.cf file format [...] ? A logical l
btb:
> since parameters can be user defined, i think it would be good if the
> documentation stated this, maybe in postconf(5)? it would alleviate
> guessing games.
>
> possibly something like:
>
> Postfix main.cf file format
> [...]
> ? A logical line starts with non-whitespace text. A line tha
On 2016.11.14 20.04, Wietse Venema wrote:
> btb:
>> by chance, i happened to create a parameter which used a dash in the
>> name, and was referencing it in another parameter, e.g.:
>>
>> foo-param = foo
>> bar_param = ${foo-param}
>>
>> upon restart, postfix complained about this:
>>
>> postconf: w
btb:
> by chance, i happened to create a parameter which used a dash in the
> name, and was referencing it in another parameter, e.g.:
>
> foo-param = foo
> bar_param = ${foo-param}
>
> upon restart, postfix complained about this:
>
> postconf: warning: macro name syntax error: "foo-param"
> pos
by chance, i happened to create a parameter which used a dash in the
name, and was referencing it in another parameter, e.g.:
foo-param = foo
bar_param = ${foo-param}
upon restart, postfix complained about this:
postconf: warning: macro name syntax error: "foo-param"
postconf: fatal: macro proce
