[exim-dev] [Bug 2733] log_file_path=syslog null-pointer dere…

Top Page
Delete this message
Reply to this message
Author: admin
Date:  
To: exim-dev
Old-Topics: [exim-dev] [Bug 2733] New: log_file_path=syslog null-pointeer dereference breakage on local delivery with allow_insecure_taint_data patch
Subject: [exim-dev] [Bug 2733] log_file_path=syslog null-pointer dereference breakage on local delivery with allow_insecure_taint_data patch
https://bugs.exim.org/show_bug.cgi?id=2733

--- Comment #15 from Heiko Schlittermann <hs@???> ---
While I believe your observations, I can't reproduce it.

4.94.2-31-503e55a2c is the version I'm running (latest commit on
exim-4.94.2+taintwarn).
LOG_FILE_PATH is set to "/opt/exim/log". `exim -C /dev/null -bP log_file_path`
returns the expected output:

log_file_path = /opt/exim/log/%slog

With the real runtime config I get:

log_file_path = :syslog


Starting Exim `exim -bdf` (or `exim -bd`) writes the startup message to the
syslog *and* to the mainlog.
So, what I'm missing here?

Journal:
Mai 13 19:00:53 x1 exim[29680]: 2021-05-13 19:00:53 [29680] exim
4.94.2-31-503e55a2c daemon started: pid=29680, no queue runs, listening for
SMTP on port 25 (IPv4)

Mainlog:
2021-05-13 19:00:53 [29680] exim 4.94.2-31-503e55a2c daemon started: pid=29680,
no queue runs, listening for SMTP on port 25 (IPv4)

--
You are receiving this mail because:
You are on the CC list for the bug.