Suddenly mta stopped postfix is not running on Zimbra server. After that try to restart the Zimbra services but it does not succeed. Zimbra is SMTP server for oracle workflow notification. If you’re encountering an issue where the MTA (Mail Transfer Agent) service, specifically Postfix, is not running, there could be several reasons for this problem. Here’s a step-by-step troubleshooting guide to help you resolve the issue:
Steps to resolve mta stopped postfix is not running.
[zimbra@mail ~]$ zmcontrol start
Host mail.readmeout.in
Starting zmconfigd...Done.
Starting dnscache...Done.
Starting logger...Done.
Starting mailbox...Done.
Starting memcached...Done.
Starting proxy...Done.
Starting amavis...Done.
Starting antispam...Done.
Starting antivirus...Done.
Starting opendkim...Done.
Starting snmp...Done.
Starting spell...Done.
Starting mta...Failed.
Check status using zmcontrol:-
[zimbra@mail ~]$ zmcontrol status
Host mail.readmeout.in
amavis Running
antispam Running
antivirus Running
dnscache Running
ldap Running
logger Running
mailbox Running
memcached Running
mta Stopped
postfix is not running
opendkim Running
proxy Running
service webapp Running
snmp Running
spell Running
stats Running
zimbra webapp Running
zimbraAdmin webapp Running
zimlet webapp Running
zmconfigd Running
Check for Errors:
If the service fails to start, you should examine the logs to identify the cause of the issue. The logs for Postfix are typically located in /var/log/mail.log or /var/log/maillog or /var/log/zimbra.log. Use a command like this to view the logs: We will see how Zimbra mta not running work for us. In /var/log/zimbra.log, showing below logs.
Error:-
Dec 14 10:23:00 mail postfix/postqueue[23568]: fatal: Queue report unavailable - mail system is down
Dec 14 10:23:03 mail zimbramon[23601]: 23601:info: Starting services initiated by zmcontrol
Dec 14 10:23:04 mail zimbramon[23601]: 23601:info: Starting zmconfigd via zmcontrol
Dec 14 10:23:04 mail zimbramon[23601]: 23601:info: Starting dnscache via zmcontrol
Dec 14 10:23:04 mail zimbramon[23601]: 23601:info: Starting logger via zmcontrol
Dec 14 10:23:04 mail zimbramon[23601]: 23601:info: Starting mailbox via zmcontrol
Dec 14 10:23:04 mail zimbramon[23601]: 23601:info: Starting memcached via zmcontrol
Dec 14 10:23:04 mail zimbramon[23601]: 23601:info: Starting proxy via zmcontrol
Dec 14 10:23:04 mail zimbramon[23601]: 23601:info: Starting amavis via zmcontrol
Dec 14 10:23:04 mail zimbramon[23601]: 23601:info: Starting antispam via zmcontrol
Dec 14 10:23:07 mail zimbramon[23601]: 23601:info: Starting antivirus via zmcontrol
Dec 14 10:23:07 mail zimbramon[23601]: 23601:info: Starting opendkim via zmcontrol
Dec 14 10:23:07 mail zimbramon[23601]: 23601:info: Starting snmp via zmcontrol
Dec 14 10:23:07 mail zimbramon[23601]: 23601:info: Starting spell via zmcontrol
Dec 14 10:23:07 mail zimbramon[23601]: 23601:info: Starting mta via zmcontrol
Dec 14 10:23:07 mail /postfix-script[24064]: the Postfix mail system is not running
Check for Port Conflicts:
Ensure that there are no port conflicts with other services that might prevent Postfix from starting. Postfix typically uses port 25 for SMTP. You can check for open ports using commands. If another program using 25 port, then note PID of that program and kill.
Identify the problematic PID using netstat command.
[root@mail ~]#netstat -tuln | grep 25 or [root@mail ~]# netstat -tulpn
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 0.0.0.0:7993 0.0.0.0:* LISTEN 18927/java
tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN 3723/master
kill the port pid:-
Using kill command, we will kill 25 port pid.
# kill -9 3723
We know that earlier we were faced the issue as mta postfix is not running.
How to start Zimbra services?
Here we can see we are using zmcontrol command to start the zimbra services.
[zimbra@mail ~]$ zmcontrol start
Host mail.readmeout.in
Starting zmconfigd...Done.
Starting dnscache...Done.
Starting logger...Done.
Starting mailbox...Done.
Starting memcached...Done.
Starting proxy...Done.
Starting amavis...Done.
Starting antispam...Done.
Starting antivirus...Done.
Starting opendkim...Done.
Starting snmp...Done.
Starting spell...Done.
Starting mta...Done.
Starting stats...Done.
Starting service webapp...Done.
Starting zimbra webapp...Done.
Starting zimbraAdmin webapp...Done.
Starting zimlet webapp...Done.
Verify the services status: –
[zimbra@mail ~]$ zmcontrol status
Host mail.readmeout.in
amavis Running
antispam Running
antivirus Running
dnscache Running
ldap Running
logger Running
mailbox Running
memcached Running
mta Running
opendkim Running
proxy Running
service webapp Running
snmp Running
spell Running
stats Running
zimbra webapp Running
zimbraAdmin webapp Running
zimlet webapp Running
zmconfigd Running
Now check the workflow services are running.
You may check another related post at ‘mta postfix’ issue.
You may also check another post related to RMAN backup click ‘‘here‘.
Hi Sajid,
This solution is works for me.
Thank you
Great! We are thankful that you found this post useful. Best of luck!