Re: [exim] Detecting a deferred sender callout verification

Pàgina inicial
Delete this message
Reply to this message
Autor: jacob
Data:  
A: exim-users
Assumpte: Re: [exim] Detecting a deferred sender callout verification
Very nice, thank you, that's exactly what I needed.
I hadn't thought of sub acls before, I've
never used them for anything so far.

Anyway, just tried it, and it seems to work. Just one question.

What's the final deny in the sverify_callout acl for?

Quoting Jeremy Harris <jgh@???>:

> Thomas Jacob wrote:
>> But I would like to know also if callout verification resulted in a
>> defer, so
>> that I could for instance do a defer !verify = reverse_host_lookup in
>> such
>> a case.
>>
>> Question: Is it somehow possible to find out in a condition check
>> whether the
>> last sender verify callout resulted in a :defer:?
>
> # Technique for explicitly seeing defers; credit andrew@???
> sverify_callout:
>   warn          set acl_c8 =    defer
>                 # Easynet puts a 30s delay on bounce inputs :-(
>   accept        verify =        sender/callout=60s,random
>                 set acl_c8 =    accept
>   warn          set acl_c8 =    deny
>   deny

>
> .
> .
> .
> foobar:
> .
> .
> .
>   warn          acl =           sverify_callout
>   accept        condition =     ${if eq {$acl_c8}{accept}}
>   deny          condition =     ${if eq {$acl_c8}{deny}}
>   accept        acl =           sverify_deferred

>
>
>
> Cheers,
>    Jeremy

>
> --
> ## 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/eximwiki/
>