Jun 14 00:12:49 server systemd[1]: Started RRDtool frontend for Mail statistic
(mailgraph).
Jun 14 00:12:49 server mailgraph.pl[24409]: Error opening : No such file or
directory at /usr/bin/mailgraph.pl line 578.
Jun 14 00:12:49 server systemd[1]: mailgraph.service: Main process exited,
code=exited, status=2/INVALIDARGUMENT
Jun 14 00:12:49 server systemd[1]: mailgraph.service: Unit entered failed
state.
Jun 14 00:12:49 server systemd[1]: mailgraph.service: Failed with result
'exit-code'.

Especially note the "Error opening : No such file or directory" line which
"shows" an empty filename before the colon.


My guess is that this change in the default sysconfig file (which does _not_
get applied to /etc/sysconfig/mailgraph automagically) causes this:

-MAILGRAPH_LOG_FILE=""
+MAILGRAPH_LOG_FILE="/var/log/mail"


If I change MAILGRAPH_LOG_FILE manually, I get at least another error message:

Jun 14 00:20:02 server systemd[1]: Started RRDtool frontend for Mail statistic
(mailgraph).
Jun 14 00:20:02 server mailgraph.pl[29218]: Internal error: unknown type:  at
/usr/bin/mailgraph.pl line 452.
Jun 14 00:20:02 server mailgraph.pl[29218]:        
Parse::Syslog::next(Parse::Syslog=HASH(0x55a9f31fb348)) called at
/usr/bin/mailgraph.pl line 584
Jun 14 00:20:02 server mailgraph.pl[29218]:         Parse::Syslog::main()
called at /usr/bin/mailgraph.pl line 1054
Jun 14 00:20:02 server systemd[1]: mailgraph.service: Main process exited,
code=exited, status=25/n/a
Jun 14 00:20:02 server systemd[1]: mailgraph.service: Unit entered failed
state.
Jun 14 00:20:02 server systemd[1]: mailgraph.service: Failed with result
'exit-code'.

Ah, that's caused by another change in the sysconfig file which doesn't get
applied to /etc/sysconfig/mailgraph automatically:

-MAILGRAPH_LOG_TYPE=""
+MAILGRAPH_LOG_TYPE="syslog"

After fixing this one, mailgraph finally starts again.


Please fix this breakage (either by aotomatically adjusting existing sysconfig
files that have empty values, or by pathing a default into mailgraph) and
release another maintenance update.


Note: I'm reporting this for 15.1, but it also affects 42.3 (and most likely
also 15.0, but I don't have a 15.0 server to test that).