On 2014-08-23, Jeremy Harris <jgh@???> wrote: > 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
not really. a message may have several recipients, and thus several
deliveries but it is only completed once, exim prints that line when
it deletes the spool file.
>> 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.
it comes from exim when messages are killed from the command-line. eg:
2014-08-24 06:01:04 1XLQr0-0004TV-1D removed by root
2014-08-24 06:01:04 1XLQr0-0004TV-1D Completed
>> 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?
>
> By all means; all contributions welcome.
Ok, I'll look into that in the new week.
I've got same damage control from a sql injection exploit (on a php
page) to handle tomorrow and then commissioning a new server that I
want this feature for
>> 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.
That would have been useful 5 years ago, I think I've
found them all now.
