On Mon, 17 May 1999, Marc Haber wrote:
> I think it should be made clear in README.UPDATING that convert4r3
> doesn't gracefully handle macros. Also, I think it would be great if
> convert4r3 would print a message on stderr if it encounters macros
> during the conversion run.
Yes. A 3.01 release will appear, as a couple of problems have surfaced.
I will add some words and maybe code.
> (1)
> Introduce parenthesis handling:
>
> host_reject = ! (LOCALHOST:LOCALNET).
That would add a lot of complication to the code. In fact, much would
have to be re-written. Instead of simple "run along the string, stopping
at each colon" there would have to be some serious parsing done. The
idea is nice, but I'm not sure I want to complicate Exim that much.
> (2)
> Adding some extra semantics: If a host-list or a domain-list entry has
> the format ${boolean-expression}, the expression is evaluated and an
> entry matches if the expression returns true. This is the most
> flexible way to do it. Also, it does not make the syntax incompatible
> and it does not impose a performance penalty to configurations that
> don't use that feature.
Yes, that is a more flexible way to do it. However, some of the lists
are already expanded before being treated as a list, so there would be
complications about double-expansion. Again, I get a small
"over-complication" feeling here...
> >If you use aliases or forwarding to pipes, files, or autoreplies, you
> >need these settings.
>
> I think that should be documented with convert4r3 that administrators
> should review these changes and might want to remove the new options.
Noted.
--
Philip Hazel University of Cambridge Computing Service,
ph10@??? Cambridge, England. Phone: +44 1223 334714.
--
*** Exim information can be found at
http://www.exim.org/ ***
