Re: [exim] EXPERIMENTAL_TPDA

Top Page
Delete this message
Reply to this message
Author: Jeremy Harris
Date:  
To: exim-users
Subject: Re: [exim] EXPERIMENTAL_TPDA
On 23/08/14 04:24, Jasen Betts wrote:
> 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"


That sounds like the TPDA msg:delivery event

> 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 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.


Doesn't matter; as you noted re. the name, it's now grown beyond just
the transport and needs a rename.

> should I just pick a name for it eg "message terminal action" and write
> a patch?


By all means; all contributions welcome.


> 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?


Yes. Use the tcp:connect event; you get given the banner
and if you return a non-empty string for the expansion the
connection will be dropped.

> 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?


If you use the transport option, *all* event types call the expansion.
It's up to you to do something appropriate for all types
(usually this will be "return an empty string" for all but the
ones you're interested in).


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


Yup, something along those lines.
--
Cheers,
Jeremy