On Fri, Sep 11, 2020 at 10:48:27AM +0200, Heiko Schlittermann via Exim-users wrote: > > Sounds like a known (and fixed) issue to me. I'll try to find any > > reference. > > This may be fixed in 8f9adfd36222d4e9e730734e00dffe874073e5b4 > This commit is currently only part of master and exim-4.94+fixes > > If I remember well and if you really hit this bug, I believe, disabling > pipelining would mitigate it. That was going to be my next thing to try :)
> In case the Debian Exim package maintainer is willing, we can help > providing a backport of the above mentioned commit. I can start looking in the source to see if that's in the latest package. On Fri, Sep 11, 2020 at 05:15:28PM +0100, Jeremy Harris via Exim-users wrote: > >> Marc MERLIN via Exim-users <[email protected]> (Do 10 Sep 2020 21:24:51 > >> CEST): > >>> Howdy, > >>> I have Exim version 4.92 #3 built 07-May-2019 17:44:23 > > Note that Buster, at least, is showing 4.92-8+deb10u4 Yes. I only update exim (or anything) when I have to, due to how many times I've been burned by upgrades that broke me in various ways. In the case of the now half maintained sa-exim which I still use (yes, I suck, I'm the original author, but I moved on to other things), I also have to be careful as newer exim can break sa-exim. Thanks for the pointers, I'll look for the best solution depending on whether that patch is in a debian package, or not. if not, I'll read the docs on how to disable pipelining on my backup MX. Thanks, Marc -- "A mouse is a device used to point at the xterm you want to type in" - A.S.R. Home page: http://marc.merlins.org/ -- ## List details at https://lists.exim.org/mailman/listinfo/exim-users ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://wiki.exim.org/
