https://bugs.exim.org/show_bug.cgi?id=2518
Jeremy Harris <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|[email protected] |[email protected] Target Milestone|Exim 4.95+ |Exim 4.94 Status|NEW |ASSIGNED --- Comment #8 from Jeremy Harris <[email protected]> --- It would be, yes. I don't see the log; did you actually attach it to the bug? However, this issue may be already partly fixed: that flag-setting is moved to early on in main() in current HEAD, so the unsetting done in daemon_go() will not be overridden. We're still left with the case of a command-line sourced message being sent over SMTP/TCP. TFO will be attempted and with your (odd?) case of an exim built for a modern Linux being run on an old kernel, will fail. It should be spooled, and the daemon would be avoiding TFO so it's only a delay - but the fix is simple so we may as well bulletproof where we can. -- You are receiving this mail because: You are on the CC list for the bug. -- ## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim details at http://www.exim.org/ ##
