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 like:
> >>
> >> Postfix main.cf file format [...] ? A logical line starts with
> >> non-whitespace text. A line that starts with whitespace continues a
> >> logical line.
> >>
> >> ? Parameter names are limited to the character set [a-zA-z0-9_].
> >
> > This is inaccurate. The above parameter name syntax limitation exists
> > only with $name or ${name....}, i.e. when a parameter value is used
> > in another parameter setting. A name can contain any non-space
> > character with 'name = value' or with master.cf service names.
>
> i see, thanks for clarifying this
>
> > Would spelling out such intricate rules make Postfix easier to use?
>
> i can't speak for everyone, of course, but it might, if it could be done
> concisely. when postfix tells me there was a syntax error, i've become
> accustomed to finding valid syntax defined in the documentation.
>
> would this be acceptable?:
>
> The expressions "$name" and "${name}" are recursively replaced with the
> value of the named parameter, except where noted. An undefined parameter
> value is replaced with the empty value. Named parameters are limited to
> the character set [a-zA-Z0-9_].
The disclaimer applies to all other ${...} forms. I will add similar
text there.
Wietse
