Re: [exim] event_action: one wish and one question

W dniu 2015-06-15 o 22:59, Marcin Mirosław pisze:
> W dniu 2015-06-15 o 22:41, Jeremy Harris pisze:
>> On 15/06/15 16:57, Jeremy Harris wrote:
>>> On 15/06/15 13:31, Jeremy Harris wrote:
>>>> On 15/06/15 11:46, Marcin Mirosław wrote:
>>>>> I wrongly configured event_action, I used too levels of brackets:
>>>>> event_action = ${if eq {msg:delivery}{$event_name} { {${lookup
>>>>> pgsql{SQL_POCZTA_WYCH}}} } }
>>>>>
>>>>> I added those line in transport. And then in main log I got:
>>>>> 2015-06-14 23:47:32 1Z4FfI-00048y-FX == aaaaaa@???
>>>>> R=dnslookup_batv T=external_smtp_batv defer (2): No such file or directory
>>>>>
>>>>> I spent a couple of minutes to find out what was the reason of this.
>>>>> Could it be possible to add some more information to logged information
>>>>> that this error comes from event_action?
>>>>
>>>> I'll have a think on that.
>>>
>>> The trouble here is that it was (probably) syntactically valid; the
>>> result of the expansion was not what you expected, but for this
>>> event it is ignored anyway - so there should not have been a
>>> semantic failure either.
>>>
>>> I'd like to see a debug run showing that it was actually the
>>> event that caused the defer.
>>
>> Ah, I forgot with "ignored anyway" that other events are involved.
>> It was processed for a tcp:connect event, where the result does
>> matter; anything but blank resulting in the connection not being
>> made (the event is raised before the connection is made, to give
>> a fine-control capability).
>
> Hmm, when I use 'select null' then message is still defered:
> == test@??? R=dnslookup_batv T=external_smtp_batv defer (2): No
> such file or directory


Sorry, I forgot about additional {} .