Now pushed; 14a465c3f
> On 24/08/14 08:01, Jasen Betts wrote:
>>>> and also the other terminal non-completions like "cancelled by admin"
>>>
>>> I'll need to look into that - exactly who is providing that message;
>>> is it the receiving MTA rejecting the message? Agreed we need the
>>> facility for them.
>
> I've coded this up, though I'm not sold on the architecture or
> the exact names I picked:
>
> - a main config option "delivery_fail_event", string, expansion
> just like the per-transport TPDA one
renamed "delivery_event_action"
>
> - an event "msg:fail:internal" with $tpda_data (for this specific case)
> "delivery cancelled by administrator" and also-useful variable
> $address_data with the recipient address. The event is also raised for
> system-filter fails, message-timeouts.
>
- and "msg:complete"
> - another event "msg:fail:delivery" for the per-transport expansion
> raised for permanent rejects from the target system
Now, should we rename the transport option from "tpda_event_action"
to just "event_action" ?
