No mails are being received or sent

Hi,
once again there are no mails coming in. I searched already through the log files (maillog) and found only this:

Code:

warning: connect to 127.0.0.1:10023: connection refused 

I checked postgrey, it is running. I restarted it, I upgraded ISPConfig in the wake of which all services were restarted, yet the problem remains. There are no failed services according to

Code:

systemctl --state=failed

In additon to that, messages sent will go out without error, but don't reach the recipient.
Where else can I look for the cause of the problem?

 

There is nothing, no output.

 

Yes, it's a typo...

 

No more ideas?
I just checked in roundcubemail, there it's the same, no mail for 4 days now.

 

I just checked amavisd (again), and for some strange reason the service wasn't running. So I restarted it, and lo, now mails are trickling in. I hope this solved the problem. But it's still strange, because day before yesterday I checked it as well and then it was running. I'll continue to keep an eye on it.

 

The mail queue is now empty, but the original warning continues to appear:

Code:

May 12 14:43:59 postfix/smtpd[25384]: warning: connect to 127.0.0.1:10023: Connection refused
May 12 14:43:59 postfix/smtpd[25384]: warning: problem talking to server 127.0.0.1:10023: Connection refused

I will take a look at rspamd. But port 10023 is used by postgrey, and that's not a spam filter, it rather helps avoiding spam in a different way. I would always want to use it next to a spam filter.

 

I just noticed that amavisd mainly serves as spamfilter. The HowTo is not so useful for me, as I run CentOS, but going through the text I found that the option to use rspamd instead of amavisd is given in the ISPConfig UI. But that doesn't mean it's available, from what I see.
rspamd is not part of the regular CentOS repositories, it seems.

 

Mail has stopped working again. I check the status of postgrey again and again, it's active and doesn't show any problem...
There is only one thing. It says:

Code:

Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.

 

Thanks for the input. There seem to be more problems CentOS, probably due to RHEL's policy change, so it seems I'll have to change the OS first before getting that done (or find a way around yum restrictions I currently encounter). Before that, I would like to get mail operating again. It has worked well for many years, why should it stop now? And it's probably not wise to change the OS while there are some unresolved issues.

 

I've been sending mails from different senders which are not on my server to an address on my server in order to find out if there are any error messages returned. Now I got one back saying:

Code:

Last error   : 451 4.3.5 

And a more wordy version:

Code:

Server configuration problem

Unfortunately that's not very helpful. I know that I didn't do any changes to the configuration. I checked if some software updates could have caused this, but none of the recently (on 8th of May, since when mails have stopped) updated packages are in any way related to the mail system (the only package updated was p7zip).

 

The weird thing is that postgrey is reported by systemctl to be active without problems. I find no other clues in the maillog. Only the message reported in my first post is repeated. To avoid confusion: the error message I posted above (Server configuration problem) has been sent by my server to the sender.

 

Here some output:

Code:

systemctl status postgrey
● postgrey.service - Postfix Greylisting Service
   Loaded: loaded (/usr/lib/systemd/system/postgrey.service; enabled; vendor preset: disabled)
   Active: active (running) since Do 2021-05-13 15:35:47 UTC; 17h ago
     Docs: man:postgrey(8)
  Process: 23634 ExecStart=/usr/sbin/postgrey $POSTGREY_TYPE $POSTGREY_PID $POSTGREY_GROUP $POSTGREY_USER --greylist-text=Greylisted for %%s seconds --daemonize $POSTGREY_DELAY $POSTGREY_OPTS (code=exited, status=0/SUCCESS)
  Process: 23632 ExecStartPre=/bin/rm -f /var/run/postgrey.pid (code=exited, status=0/SUCCESS)
 Main PID: 23637 (postgrey --unix)
   CGroup: /system.slice/postgrey.service
           └─23637 postgrey --unix=/var/spool/postfix/postgrey/socket --pidfile=/var/run/postgrey.pid --group=postgrey --user=postgrey --greylist-text=Greylisted for %s seconds --daemo...

Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.

And this one:

Code:

 lsof -p 23634

Yes, there is nothing (see my posts above). That's the curious part: postgrey is active, the process seems to run normally, yet there is no active process. How can that be?

 

How to strace a systemd process? Do I

Code:

strace 'systemctl restart postgrey'

? or ...