Re: [exim] Undefined variable in eval: (string expansion)

2007-07-06 Thread Philip Hazel
On Fri, 6 Jul 2007, Toralf Lund wrote: > I primarily had $acl_ variables in mind. "strict_acl_vars" is a fairly > new option, isn't it? 4.64. -- Philip HazelUniversity of Cambridge Computing Service Get the Exim 4 book:http://www.uit.co.uk/exim-book -- ## List details at htt

Re: [exim] Undefined variable in eval: (string expansion)

2007-07-06 Thread Toralf Lund
Philip Hazel wrote: > On Fri, 6 Jul 2007, Toralf Lund wrote: > > >> What do I get if I do something like >> >> ${eval:$some_variable+1} >> >> when "some_variable" is not actually defined? >> > > It depends on the variable. In the case of $acl_ variables it also > depends on whether you hav

Re: [exim] Undefined variable in eval: (string expansion)

2007-07-06 Thread Philip Hazel
On Fri, 6 Jul 2007, Toralf Lund wrote: > What do I get if I do something like > > ${eval:$some_variable+1} > > when "some_variable" is not actually defined? It depends on the variable. In the case of $acl_ variables it also depends on whether you have set strict_acl_vars or not. Many variables

Re: [exim] Undefined variable in eval: (string expansion)

2007-07-06 Thread Jakob Hirsch
Quoting Toralf Lund: > What do I get if I do something like > > ${eval:$some_variable+1} > > when "some_variable" is not actually defined? An undefined variable expands to nothing (except for acl_m/acl_c variables, if you have the strict_acl_vars option set), so this is the same as ${eval:+1},

Re: [exim] Undefined variable in eval: (string expansion)

2007-07-06 Thread Toralf Lund
> >>> What do I get if I do something like >>> >>> ${eval:$some_variable+1} >>> >>> when "some_variable" is not actually defined? >>> >> Looks like it treats some_variable as 0: >> >> [EMAIL PROTECTED]:~# /usr/sbin/exim -be >> > ${eval:$acl_m9+1} >> 1 >> > >> > > Hmmm. More accura

Re: [exim] Undefined variable in eval: (string expansion)

2007-07-06 Thread Mike Cardwell
Mike Cardwell wrote: >> What do I get if I do something like >> >> ${eval:$some_variable+1} >> >> when "some_variable" is not actually defined? > > Looks like it treats some_variable as 0: > > [EMAIL PROTECTED]:~# /usr/sbin/exim -be > > ${eval:$acl_m9+1} > 1 > > Hmmm. More accurately, it expa

Re: [exim] Undefined variable in eval: (string expansion)

2007-07-06 Thread Mike Cardwell
Toralf Lund wrote: > What do I get if I do something like > > ${eval:$some_variable+1} > > when "some_variable" is not actually defined? Looks like it treats some_variable as 0: [EMAIL PROTECTED]:~# /usr/sbin/exim -be > ${eval:$acl_m9+1} 1 > Mike -- ## List details at http://www.exim.org/

[exim] Undefined variable in eval: (string expansion)

2007-07-06 Thread Toralf Lund
What do I get if I do something like ${eval:$some_variable+1} when "some_variable" is not actually defined? - Toralf -- ## List details at http://www.exim.org/mailman/listinfo/exim-users ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://www.exim.org/eximw