On Fri, 1 Aug 2003, Alexander Sabourenkov wrote:
> Hmm. I'm more concerned about the case when, say, realm has to be hardcoded
> into configuration and to have a curly brace(s) in itself.
If you have a hard-coded curly brace in an expanded string, you can
escape it with \ just like any other character that the expander treats
specially.
$ exim -be
> ${if eq {\{}{\}}{yes}{no}}
no
> Problem is, while for two fields with more-or-less clear semantics this is
> acceptable, four fields of saslauthd, with two latter still remaining a
> mystery, I'm afraid colon-separation is not the right thing.
Oh, I entirely agree.
> I think it's better to deprecate pwcheck condition itself. In Cyrus SASL
> pwcheck has been deprecated long long ago in favor of saslauthd.
Ah. I didn't know that. Makes sense.
--
Philip Hazel University of Cambridge Computing Service,
ph10@??? Cambridge, England. Phone: +44 1223 334714.
Get the Exim 4 book: http://www.uit.co.uk/exim-book
