https://bugs.exim.org/show_bug.cgi?id=2972
--- Comment #3 from Jeremy Harris <jgh146exb@wizmail.org> ---
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.
--
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/ ##
--- Comment #3 from Jeremy Harris <jgh146exb@wizmail.org> ---
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.
--
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/ ##