Wietse Venema:
> I am getting close to implementing {} for grouping options and for
> quoting arguments, because splitting on space/comma does not always
> work well. This would allow more natural main.cf syntax such as:
> pipemap:{map_1, ..., map_n}, join:{map_1, ..., map_n}{options},
> master.cf entries with -o {parameter = value}, options to specific
> milters, and so on.
I now have pipe:{map_1, ..., map_n} and randmap:{map_1, ..., map_n}
syntax support and updated (I think) all code that splits input
into lookup table names. In all but 4 cases this splitting happens
inside a Postfix library function, so most programs needed no change.
> Remotely related to this is my note about "beefing up Postfix macro
> processing" on the postfix-devel list.
Support for "${name?{text if true}:{text if false}}" works, as well
as "${ {text1} == {text2} ? {text if true} : {text if false}}".
Ditto for the != (inequality) operator.
That was necessary to make configurable message headers and
configurable logging more practical.
Wietse
