> Otto Hirr:
> > In answer to my question, and so others don't have to
> > trudge thru the source to find it...
> >
> > The 'parameter name' may be and non-space, non-equals (i.e. =)
> > string of characters.
>
> The fine details are not documented, because I didn't want to promise
> that Postfix will forever support names with ^A<ESC>^Z<CR> in them,
> nor did I want to add code that artificially restricts the input.
>
> There are a few other characters that limit parameter names
> when they are used in macro substitution (this uses the '$', '{}'
> and '()', and also limits what the name in "$name" can be.)
>
> I suppose that for most people, the examples in Postfix documentation
> are a sufficient guideline. Being able to spell weird names does not
> mean that you have to use weird names.
>
> Wietse
Understand. My concern was related to use of
postfix/postmulti/mailman - where postfix has a
primary/all-other-instance naming scheme and i
wanted to attempt to have a "standardize" method...
then saw that it may result in a - (dash) in a
parameter name, which had concerned me...
I was not interested in anything strange.
Just like hostnames (per your previous post)
should not have underscore (but use dash),
but then "typical" parameters (e.g. variables)
can't have dashes but can have underscores...
..Otto
