I'm running a Centos 7 system and I have just done a 'yum update' for the
first time in a while.
One of the effects of this was that my exim died. To finish off the update I
rebotted the server. Exim did not restart. Checking the status I got the
following:
root@ollie2 ~]# systemctl status exim
● exim.service - Exim Mail Transport Agent
Loaded: loaded (/usr/lib/systemd/system/exim.service; enabled; vendor
preset: disabled)
Active: failed (Result: exit-code) since Tue 2017-05-02 09:56:57 BST; 4s
ago
Process: 14002 ExecStart=/usr/sbin/exim -bd -q${QUEUE} (code=exited,
status=1/FAILURE)
Process: 13998 ExecStartPre=/usr/libexec/exim-gen-cert (code=exited,
status=0/SUCCESS)
Main PID: 14002 (code=exited, status=1/FAILURE)
May 02 09:56:57 ollie2.ringways.co.uk systemd[1]: Starting Exim Mail Transport
Agent...
May 02 09:56:57 ollie2.ringways.co.uk systemd[1]: Started Exim Mail Transport
Agent.
May 02 09:56:57 ollie2.ringways.co.uk exim[14002]: 2017-05-02 09:56:57 Exim
configuration error in line 1015 of /etc/exim/exim.conf:
May 02 09:56:57 ollie2.ringways.co.uk exim[14002]: error in ACL: unknown ACL
condition/modifier in "demime = *"
May 02 09:56:57 ollie2.ringways.co.uk systemd[1]: exim.service: main process
exited, code=exited, status=1/FAILURE
May 02 09:56:57 ollie2.ringways.co.uk systemd[1]: Unit exim.service entered
failed state.
May 02 09:56:57 ollie2.ringways.co.uk systemd[1]: exim.service failed.
[root@ollie2 ~]#
The offending code was in acl_check_data and was:
# GPS added 2014-04-30
warn message = X-MIME-Error: $demime_reason
demime = *
condition = ${if >{$demime_errorlevel}{0}{1}{0}}
set acl_m_greylistreasons = Message has MIME error: \
$demime_reason\n$acl_m_greylistreasons
As you can see, this code has been in for a long time. Can anyone tell me why
a system update would break this, and what I need to do to fix it.
All of the Google responses that seem to relate to this all date back to
2005 -> 2008 so I don't think they're relevant.
Gary
--
https://fundraise.cancerresearchuk.org/page/garys-march-march
