Re: [exim] EXPERIMENTAL_TPDA

Top Page
Delete this message
Reply to this message
Author: Jasen Betts
Date:  
To: exim-users
Subject: Re: [exim] EXPERIMENTAL_TPDA
On 2014-08-20, Jeremy Harris <jgh@???> wrote:
> Users of EXPERIMENTAL_TPDA be warned: just pushed is an
> incompatible change to the feature. You *will* need to
> rewrite the relevant portions of your exim.conf files.
>
> Please read the experimental-spec.txt file for further
> information, or mail me. Comments, further feature
> requests, cursing - all welcome.


First a request,

I'd like to be able to also do expansion in the context of log lines
like this: "2014-08-22 07:00:26 1XKXay-0005B6-Hr Completed"
and also the other terminal non-completions like "cancelled by admin"
I accept that while this is similar to the TPDA feature as it's not in
the transport context it may be outside the scope of your TPDA feature.
should I just pick a name for it eg "message terminal action" and write
a patch?


And now some comments: that's a fairly major reworking.

can I now program exim to quit if it sees
"220 Uceprotect.org spamtrap" during SMTP connect?


Is there a way to determine if this will be the last call from the
transport. say, if the remote host drops the conection after I send EHLO
will there be a further expansion so I can log this?


As you're still hacking at it might I suggest a further name change

tpda_event_action seems somewhat redundant

"T" we know it's a transport parameter from context
"P" "post" is now incorrect as it's expanded during delivery too
"D" "delivery" is implied from context
"A" "action" is repeated ans therefore redundant.

"progress_action", "progress_hook" or "progress_callback" might be a
better name for this transport parameter.

--
umop apisdn