1 Topic by tomwho (edited by tomwho 2020-09-28 00:39:36)

  • tomwho
  • Member
  • Offline
  • Registered: 2017-09-28
  • Posts: 17

Topic: Mail Undeliverable after YUM update

==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====
- iRedMail version (check /etc/iredmail-release): 0.9.7
- Deployed with iRedMail Easy or the downloadable installer? Download installer
- Linux/BSD distribution name and version: CentOS 7
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): MySQL
- Web server (Apache or Nginx): Apache
- Manage mail accounts with iRedAdmin-Pro? No
- [IMPORTANT] Related original log or error message is required if you're experiencing an issue.
====

After I did a Yum update recently, the daily status mails are suddenly undeliverable. This is the error message:

====

This is the mail system at host mydomain.com.

I'm sorry to have to inform you that your message could not
be delivered to one or more recipients. It's attached below.

For further assistance, please send mail to postmaster.

If you do so, please include this problem report. You can
delete your own text from the attached returned message.

                  The mail system

<root@mydomain.com>: delivery temporarily suspended: connect to
   127.0.0.1[127.0.0.1]:10024: Connection refused
Reporting-MTA: dns; mydomain.com
X-Postfix-Queue-ID: AFBE735D4
X-Postfix-Sender: rfc822; root@mydomain.com
Arrival-Date: Tue, 22 Sep 2020 03:25:05 -0700 (PDT)

Final-Recipient: rfc822; root@mydomain.com
Action: failed
Status: 4.4.1
Diagnostic-Code: X-Postfix; delivery temporarily suspended: connect to
   127.0.0.1[127.0.0.1]:10024: Connection refused

====

I replaced my actual domain with "mydomain.com" for privacy. Nothing else has changed on the server. I was getting these status email every day with no problem before the Yum update. I have no idea where to even begin looking for the reason this is happening, so I'm hoping someone here might be able to point me in the right direction. Thanks.

----

Spider Email Archiver: On-Premises, lightweight email archiving software developed by iRedMail team. Supports Amazon S3 compatible storage and custom branding.

2 Reply by wirthti

  • wirthti
  • Member
  • Offline
  • Registered: 2020-08-15
  • Posts: 5

Re: Mail Undeliverable after YUM update

Hi

It seems that the amavis service is stopped.
See if the amavis service is running by running the following command: systemctl status amavisd.

If stopped, run systemctl start amavisd

3 Reply by tomwho (edited by tomwho 2020-09-28 23:15:11)

  • tomwho
  • Member
  • Offline
  • Registered: 2017-09-28
  • Posts: 17

Re: Mail Undeliverable after YUM update

I think that was the problem, thank you for your help. I believe amavisd is now running, this is what I saw in my terminal: 

[]# systemctl status amavisd

● amavisd.service - Amavis mail content checker
   Loaded: loaded (/usr/lib/systemd/system/amavisd.service; disabled; vendor preset: disabled)
   Active: inactive (dead)
     Docs: http://www.ijs.si/software/amavisd/#doc

[]# systemctl start amavisd
[]# systemctl status amavisd

● amavisd.service - Amavis mail content checker
   Loaded: loaded (/usr/lib/systemd/system/amavisd.service; disabled; vendor preset: disabled)
   Active: active (running) since Mon 2020-09-28 07:55:36 PDT; 3s ago
     Docs: http://www.ijs.si/software/amavisd/#doc
  Process: 15926 ExecStart=/usr/sbin/amavisd -c /etc/amavisd/amavisd.conf (code=exited, status=0/SUCCESS)
 Main PID: 15927 (/usr/sbin/amavi)
   CGroup: /system.slice/amavisd.service
           ├─15927 /usr/sbin/amavisd (master)
           ├─15928 /usr/sbin/amavisd (virgin child)
           └─15929 /usr/sbin/amavisd (virgin child)

systemd[1]: Starting Amavis mail content checker...
amavis[15926]: starting. /usr/amavisd-n...F-8"
amavis[15926]: perl=5.016003, user=, EUID: 996 (996);  group=, EGID: 993 993...993)
amavis[15927]: Net::Server: Group Not Defined.  Defaulting to EGID '993 993'
amavis[15927]: Net::Server: User Not Defined.  Defaulting to EUID '996'
amavis[15927]: Using primary internal av scanner code for ClamAV-clamd
systemd[1]: Started Amavis mail content checker.
amavis[15927]: Found secondary av scanner ClamAV-clamscan at /usr/bin/clamscan
Hint: Some lines were ellipsized, use -l to show in full.

Somehow a previous Yum update has disabled loading amavisd on reboot, so, I ran this command to fix that, too: 

systemctl enable amavisd.service

Now amavisd restarts automatically whenever I need to reboot the server.

4 Reply by ZhangHuangbin

  • ZhangHuangbin
  • ZhangHuangbin
  • iRedMail Developers
  • Offline
  • Registered: 2009-05-06
  • Posts: 30,788

Re: Mail Undeliverable after YUM update

FYI: https://groups.google.com/g/iredmail/c/lZSaAqtEEOc