I get an email daily from cron on a few of my directadmin servers. No idea what it means or what that cron job is even supposed to be doing.
After searching around on the net there are a lot of people with the same issue.
Some of the suggested fixes do not sound very nice, like making some hacks to custombuild and then rebuilding every piece of software on the system. That simply sounds dangerous!
I found this blog post where the author deletes multiple copies that exist on his system and then create link to the correct version.
That sounded not so dangerous so I gave it a try and it worked. In my case I only had /usr/local/lib/libz.so.1.2.3 not /usr/local/lib/libz.so.22.214.171.124 so my solution looked more like this.
ln -s /usr/lib/libz.so.1.2.3 /usr/local/lib/libz.so.1
About 1.5 years ago I did a posting with easy instructions to compile in a custom build of Exim on Directadmin.
Since then I upgraded to Debian Wheezy and Exim has been upgraded to 4.84. The step-by-step instructions don’t work anymore as a result.
Here is an updated version of those instructions.
First, ensure you have the required dependencies.
apt-get install libdb5.1-dev libperl-dev libsasl2-dev
Change all occurrences of 4.84 to the version you want to use. The sample pulls Exim from some mirror, you might need to lookup a working URL to a mirror if this one goes down.
tar xvzf exim-4.84.tar.gz
perl -pi -e 's/^EXTRALIBS/#EXTRALIBS/' Makefile
perl -pi -e 's/HAVE_ICONV=yes/HAVE_ICONV=no/' Makefile
perl -pi -e 's/^#LOOKUP_DNSDB=yes/LOOKUP_DNSDB=yes/' Makefile
The above commands will download the unmodified source for exim, extract it, download a makefile from the directadmin servers, use a perl command to adjust the makefile, compile and install the fresh exim build.
The file that is created is /usr/sbin/exim-4.84-1, so we must change the name and overwrite the existing exim file.
cp -f /usr/sbin/exim-4.84-1 /usr/sbin/exim
chmod 4755 /usr/sbin/exim
To verify you have a working Exim with DNSDB compiled in do the following: