Quoting Matthew Newton <mcn4@???>:
> Hi,
>
> On Wed, Mar 05, 2014 at 04:06:00PM +0000, a.smith@??? wrote:
>> >
>> >Unless something has changed recently in exim that I'm not aware
>> >of, $acl_m is the right thing here.
>>
>> well be wrong, but from reading the documenation the only custom
>> variables I can set in an ACL are $acl_m and $acl_c variables.
>
> Yes - you wrote acl_a, which doesn't exist (afaik - hence my
> comment above :) ).
Oops sorry!
> Look at the -d debugging options. -d+rewrite would be a good
> start. If you really want to wade through likely irrelevant stuff,
> try -d+all :)
>
Ok using -d+all -bt I can see a the rewrite being processed:
17:29:19 26335 condition: def:acl_c_a
17:29:19 26335 result: false
17:29:19 26335 expanding: $acl_c_a
17:29:19 26335 result:
17:29:19 26335 skipping: result is not used
17:29:19 26335 failed to expand: ${if def:acl_c_a{$acl_c_a} fail}
17:29:19 26335 error message: "if" failed and "fail" requested
17:29:19 26335 failure was forced
But I really need to see whats happening where $acl_c_a is meant to be
set, in the ACL section as the only thing I can see here is that it is
null.
If I could run the Exim daemon in the foreground with this level of
debugging that might well help. I'm trying this via:
exim -bdf -d+all
But it prints a load of info at startup, gets to "Listening..." and
then I get no more debug output (although it logs normally to the
mainlog).
thanks again, Andy.
