Re: [exim] adding a header to a message in an ACL, ?even whe…

Pàgina inicial
Delete this message
Reply to this message
Autor: Josip Rodin
Data:  
A: exim-users
Assumpte: Re: [exim] adding a header to a message in an ACL, ?even when the condition defers
On Sun, Nov 12, 2006 at 12:07:18PM +0100, joy wrote:
> > I really think[1] this fixed version should work, although you still get
> > Warning: ACL "warn" statement skipped: condition test deferred: Could
> > not complete sender verify callout in the logfile.
>
> And the same will work with 'warn message'? I don't want to have to upgrade
> to 4.63 (to get add_header) since I'm running 4.50 from Debian stable.


Yep, it works, although it still logs the annoying skipped message. Oh well.

> Also, could I perhaps somehow differentiate between defer and fail,
> other than parsing $acl_verify_message?


Unfortunately, I can't seem to *get* $acl_verify_message, either.
The headers come in:

X-Exim-ACL-envelope-sender-verify: failed ()
X-Exim-ACL-header-sender-verify: failed ()

Then I figured that the variable is getting lost due to the ending of the
verb that generated it, and I then tried doing this:

  warn set acl_m2 = failedordefered
       verify = sender/callout=60s
       set acl_m3 = $acl_verify_message
       set acl_m2 = ok
  warn condition = ${if eq{$acl_m2}{failedordefered}{true}{false}}
       message = X-Exim-ACL-envelope-sender-verify: failed ($acl_m3)


However, there's still nothing in there.

Then I thought that this may be another side effect of it being a deferral,
that Exim is not generating the $acl_verify_message variable, but then I
tested with a truly unverifiable addresses, and it still didn't record the
reason in that variable (and consequently $acl_m3). Any idea why not?

-- 
     2. That which causes joy or happiness.