Could not send mail after updates in custombuild

flexjoly

Verified User
Joined
Nov 2, 2016
Messages
43
Location
Apeldoorn, Netherlands
Hi,

We could solve it, but how could this happen??

Yesterday we runned about 10 updates in custombuild and the latest yum updates (centos). This morning 2 clients reported that they could not send any mail. Testing it in roundcube, the error was: SMTP Error (-1): Connection to server failed.
In the logs we could find NOTHING :sick:

So we tried several things including: updating exim.conf in roundcube. That worked!!! 🤩
But how could this happen and how can we prevent this for the future??

Thanks in advance,
flexjoly

----------------------------------------

The settings for custombuild are: (this is how custombuild shows it in the popup)
Code:
Nginx: 1.17.8
LibModSecurity: no
htscanner: no
Dovecot: 2.3.9.2
Dovecot configuration: yes
AWstats: 7.7
Exim: 4.93.0.4
exim.conf update: yes, release 4.5
BlockCracking: yes
Easy Spam Fighter: yes
SpamAssassin: 3.4.4
SpamAssassin rule updates: daily
ClamAV: 0.102.2
MariaDB: 10.0.38
MySQL backup: yes
MySQL backup directory: /usr/local/directadmin/custombuild/mysql_backups
MySQL compress backups: no
PHP (default): 7.1 as php-fpm
phpMyAdmin: 4.9.4-all-languages
ProFTPD: no
Pure-FTPd: 1.0.49
RoundCube webmail: 1.4.2
Replace "php.ini" with '/usr/local/directadmin/custombuild/build all' and '/usr/local/directadmin/custombuild/build php_ini': yes
Replace "php.ini" using type: production
Cron for notifications and (or) updates: yes
Cron frequency: daily
Run "clean" every time: yes
Run "clean_old_webapps" every time: yes
Run "clean_old_tarballs" every time: yes
Show texts in bold: yes
SquirrelMail: no
Zend Guard Loader: no
ionCube loader: no
Suhosin: no
1581064106775.png
 

smtalk

Administrator
Staff member
Joined
Aug 22, 2006
Messages
8,936
Location
LT, EU
Maybe exim service was down? And "exim_conf" just restarted the service at the end :)
 

flexjoly

Verified User
Joined
Nov 2, 2016
Messages
43
Location
Apeldoorn, Netherlands
Hi smtalk,

We did check the service monitor, everything looked normal.
To be sure we restarted exim. We even rebooted the server. But that did not help.
Updating exim-conf did.

Well if no one else had this, then... we just hope it won't happen again ;-)

Greetz, flexjoly
 
Top