On 03/06/2023 21:29, Julian Bradfield via Exim-users wrote:
> The delay on each recipient is triggered, but then cancelled because
> exim's smtp_out connection has been shut down.
Thanks - that's the item of info I was missing and
hadn't realised.
Dumping the previously-received input once we've
seen the channel close sounds feasible (I'm unsure
if anything should be specifically logged if we did that)
and would cut down on log noise for your specific case.
I don't think standards say anything about the situation,
but it comes into the realm of self-defence vs. bad actors
IMHO.
If you're seeing these often enough, you could run
a quick check with pipelining disabled to see what they
do then. If you can get a sufficient profile on them
(eg. $sender_host_name not good, or helo verify fails)
you could disable on that basis rather than wholesale
(see "control = no_pipelining" for that).
--
Cheers,
Jeremy
--
## subscription configuration (requires account):
##
https://lists.exim.org/mailman3/postorius/lists/exim-users.lists.exim.org/
## unsubscribe (doesn't require an account):
## exim-users-unsubscribe@???
## Exim details at
http://www.exim.org/
## Please use the Wiki with this list -
http://wiki.exim.org/
