A few Exim issues (non critical)

[rvandam]

I have installed a fresh Directadmin system on Debian 8

I have a few issues with Exim.

The first issue is a cron.daily error:

run-parts: /etc/cron.daily/exim exited with return code 123

The second issue is a paniclog entry line this:

2017-06-15 09:39:45 1dLPNY-0003PX-5P unable to open private key file for reading: /etc/virtual/server.mydomain.com/dkim.private.key

I have configured my server with hostname server.mydomain.com. I /etc/virtual there is an empty directory server.mydomain.com. For the other (real) domains everything works well, and dkim keys are generated. Should I add server.mydomain.com anywhere? Right now server.mydomain.com resolves, because I use the dns from my registrar.

The third issue are entries in the paniclog like this:

2017-05-31 06:25:08 1dFvC0-0004zh-00 User 0 set for local_delivery transport is on the never_users list

Looked like the system doesn't know what to do with root mails. I resolved this by making a .forward file in the root directory with my personal email address. Although the issue is resolved I wonder if there is a configuration error on my side.

 

[rvandam]

The second issue is triggered by a email read message. This is the part from the log (modified ip and email addresses):

2017-06-15 11:39:41 1dLRFd-0003kg-Ai <= <> H=(DESKTOPDSRFHL1) [111.222.333.444] P=esmtp S=2346 [email protected] T="Read: subject" from <> for emailaddress
2017-06-15 11:39:41 1dLRFd-0003kg-Ai unable to open private key file for reading: /etc/virtual/server.mydomain.com/dkim.private.key
2017-06-15 11:39:48 1dLRFd-0003kg-Ai => emailaddress F=<> R=lookuphost T=remote_smtp S=2424 H=mx1.compudac.com [222.333.444.555] K C="250 2.6.0 <[email protected]> [InternalId=523] Queued mail for delivery"
2017-06-15 11:39:48 1dLRFd-0003kg-Ai Completed

There are multiple entries like this, all for the same address, and all seem to be read comfirmation mails

 

[rvandam]

When I do a EX4DEBUG=true /etc/cron.daily/exim the output is:

now debugging /etc/cron.daily/exim 
+ E4BCD_DAILY_REPORT_TO=
+ E4BCD_DAILY_REPORT_OPTIONS=
+ E4BCD_WATCH_PANICLOG=yes
+ E4BCD_PANICLOG_LINES=10
+ E4BCD_PANICLOG_NOISE=
+ '[' '!' -x /usr/sbin/exim ']'
+ '[' -f /etc/default/exim ']'
+ . /etc/default/exim
++ EX4DEF_VERSION=
++ QUEUERUNNER=combined
++ QUEUEINTERVAL=30m
++ COMMONOPTIONS=
++ QUEUERUNNEROPTIONS=
++ QFLAGS=
++ SMTPLISTENEROPTIONS=
++ exim -bP spool_directory
++ sed 's/.*=[[:space:]]\(.*\)/\1/'
+ SPOOLDIR=/var/spool/exim
+ E4BCD_MAINLOG_NOISE='^[[:digit:][:space:]:-]\{20\}\(\(Start\|End\) queue run: pid=[[:digit:]]\+\|exim [[:digit:]\.]\+ daemon started: pid=[[:digit:]]\+, .*\)$'
+ '[' -n '' ']'
+ '[' yes '!=' no ']'
+ '[' -s /var/log/exim/paniclog ']'
+ '[' -x /usr/sbin/exim_tidydb ']'
+ cd /var/spool/exim/db
+ find /var/spool/exim/db -maxdepth 1 -name '*.lockfile' -or -name 'log.*' -or -type f -printf '%f\0'
+ xargs -0r -n 1 start-stop-daemon --start --exec /usr/sbin/exim_tidydb --chuid Debian-exim:Debian-exim -- /var/spool/exim
+ find /var/spool/exim/db -maxdepth 1 -name '*.lockfile' -or -name 'log.*' -or -type f -printf '%f\0'
+ su - --shell /bin/bash --command 'xargs -0r -n 1 /usr/sbin/exim_tidydb /var/spool/exim > /dev/null' Debian-exim

There could be an issue with the naming of the Exim dir in the spool directory. There ixists a exim and a exim 4 directory

drwxr-xr-x 5 root        root        4096 Oct 10  2014 cron
drwxr-x--- 5 mail        mail        4096 May 24 08:09 exim
drwxr-x--- 3 Debian-exim Debian-exim 4096 Feb 12  2015 exim4
lrwxrwxrwx 1 root        root           7 Oct 10  2014 mail -> ../mail
drwx------ 2 root        root        4096 Aug 20  2014 rsyslog
drwxrwxrwt 2 mail        mail        4096 May 24 08:25 virtual

 

[rvandam]

Looks like /etc/cron.daily/exim was installed by Debian, and not by Directadmin. I removed this cron job.