EXIM does not function properly after reboot. Does not send mail. BUG.

Please do not quote complete posts. ;)

That having said....
At reboot it hang again, then I thought about putting a 30 second delay in starting Exim, and somehow that seems to work?!
Very nice find!! (y)

Since in other answers one can read that the issue is probably something caused by hardware/OS/memory combination and also lots of people do not have an issue with Exim 4.94, it could very well be a timing issue.
Maybe it has to do with resolving, or maybe Exim is starting faster then Bind causing an issue. Might be a possibility.

But if you can leave configs default and also /etc/domains like it should be with the hostname in it, and the delay in starting exim takes care of the issue, then it's sure worth for others experiencing this issue, to test this too.
 
Hello, dear all.

Finally Exim has released an update (Exim 4.94.2). So I have updated, and after initial testing, it seems that all this issue for me is gone.
Restart works fine, its sends emails nicely after restart, and exim.dkim.conf is also back to normal (no changes made), and it all seems to work.

Thank You all and I hope that this issue is solved for others too.
 
Last edited:
All still going well for you @needhelppp ? Like you, I had never-ending problems with 4.94, and have been running 4.93.0.4 for a long time. But DA was making it very hard to stay there (see this post), so I've just installed 4.94.2. Feeling cautiously hopefully!
 
But DA was making it very hard to stay
Why DA? It was an Exim issue. DA only caused a dkim issue by a upgrade via custombuild. That can happen.
So why say DA made it "very hard" to stay? Even when the did not make that dkim mistake, which can easily be found quickly when monitoring the systems, the big Exim problem would not be fixed by that.
 
So why say DA made it "very hard" to stay?
I linked to the other post where I explained that. In summary, DA ignored my custom_versions.txt file and updated config files to versions that were incompatible with 4.93.0.4. I could manually revert exim.dkim.conf to version 1.5 each time, but now DA simply refuses to build with exim.conf version 4.5.23, saying 'Selecting exim.conf 4.5.24 automatically, as older versions are not supported with exim 4.94 and newer', even though I had Exim 4.93.0.4 installed! See the problem??
 
I linked to the other post where I explained that.
I know that and I did see the problem. But I still think the term "very hard" is correct. Because it's easy to set exim.conf updates to no in the options.conf which prevent updates. So the only real DA issue still was the exim.dkim.conf which should not be overwritten.
However, once knowing that, you could restore it and then chattr it so it could not be overwritten.

Unless if that issue also occurred with exim.conf update disabled in options.conf and then DA still wanting to use exim.conf 4.5.24 automatically.

Anyway, since there should not be any overwriting and since it should be possible (for example in case of bugs) to use older versions, this certainly is something to smtalk or dasupport to have a look at, so things will not be automatically choosen and/or overwritten once a custom_versions.txt is in effect.
 
But I still think the term "very hard" is correct. Because it's easy to set exim.conf updates to no in the options.conf which prevent updates. So the only real DA issue still was the exim.dkim.conf which should not be overwritten.
Did you mean to say 'incorrect'? Look, we can quibble over the definition of 'very hard' if you want, but don't lose sight of the big picture here… DirectAdmin is supposed to make our lives easier. CustomBuild has a feature that is specifically designed to lock in an older version of software, and protect them from future updates. If it doesn't do what it says on the tin, and you have to come up with your own workarounds, then sorry, but that is an issue.

Anyway, since there should not be any overwriting and since it should be possible (for example in case of bugs) to use older versions, this certainly is something to smtalk or dasupport to have a look at, so things will not be automatically choosen and/or overwritten once a custom_versions.txt is in effect.
Yep, which is why I lodged a support ticket with them. They have responded and acknowledged the issue.
 
No according that solution, first downgrade to 4.93.04 that automatically downgrade your exim_conf as well
later go to the file exim.dkim.conf (in /etc map) make this change

Code:
find:
dkim_domain = ${if eq{${lc:${domain:$h_from:}}}{}{$primary_hostname}{${lookup{${lc:${domain:$h_from:}}}lsearch,ret=key{/etc/virtual/domainowners}{$value}}}}

replace with:
dkim_domain = $sender_address_domain
Save and restart exim
I have no problem in send and receive mail with Roundcube but problem for forward to any mail

 
Back
Top