https://bugs.exim.org/show_bug.cgi?id=2972
--- Comment #4 from ente@??? ---
(In reply to Jeremy Harris from comment #3)
> The lack of the '!' and '=' in the error log line can be ignored.
> The log line is not the config line; it only refers to it.
>
> However, the issuing of those log lines does show there was a problem.
> I'm having a hard time seeing how, though. This report is the first
> such I've heard.
>
> The second variant could be a filesystem bug, but that sort of thing
> would be making your system unusable in man different ways.
>
> I suppose it could be induced by an overwrite of an old config files,
> which was halfway done just as a re-exec of the exim binary happened
> (Exim does that, to regain permissions, during message delivery processing).
> The solution to that is to *rename* the new file into place instead.
I was able to reproduce the issue several times. There can't be an issue that
happens randomly. Also I am in the middle of nowhere with a very bad internet
connection. My server definitely saves faster the file than I can restart a
server. Keystrokes on my SSH connection take up to 3 seconds to be recognized!
Unfortunately I am not sure how fast I will be able to provide additional
information.
Can I send you my full config to your mail address and be assured that it won't
be published anywhere? I guess that's the best way to find out. Once you can
reproduce the issue, you will be able to find the cause.
--
You are receiving this mail because:
You are on the CC list for the bug.
