Unable to connect to MTA

Discuss your pilot or production implementation with other Zimbra admins or our engineers.
Post Reply
wauters
Posts: 13
Joined: Thu Mar 21, 2019 7:10 pm

Unable to connect to MTA

Post by wauters »

I can not send or receive email. I have been searching for hours.

This started after a power failure. The machine rebooted and has not worked since. I can get to the admin webpage and the mailbox webpage.

I have checked the hosts file multiple times. Keep in mind this has not changed.

I have restarted multiple times. I have done zmcontrol status and everything is running.

When I do a postfix check I get nothing. After I hit enter it thinks for a little bit and then goes back to the command prompt. I try to do a postfix start and I don't get errors. I do a postfix stop I get an error that says the postfix mail system is not running. I think I have a postfix problem but I am not sure what to do to correct it.

Thank you.
User avatar
JDunphy
Outstanding Member
Outstanding Member
Posts: 897
Joined: Fri Sep 12, 2014 11:18 pm
Location: Victoria, BC
ZCS/ZD Version: 9.0.0_P39 NETWORK Edition

Re: Unable to connect to MTA

Post by JDunphy »

What does /var/log/maillog say?
Also try this:

Code: Select all

% grep 'starting the Postfix' /var/log/zimbra.log
Dec 10 07:39:44 relay3 /postfix-script[24222]: starting the Postfix mail system
You could also investigate if something odd has happened such as another process has the MTA listen port (25,587, etc) open so zimbra can't start its MTA... Try this:

Code: Select all

# lsof -i TCP:25
COMMAND     PID    USER   FD   TYPE    DEVICE SIZE/OFF NODE NAME
postscree  5901 postfix    6u  IPv4 312730975      0t0  TCP *:smtp (LISTEN)
master    16422    root   13u  IPv4 312730975      0t0  TCP *:smtp (LISTEN)

# cat /proc/16422/cmdline 
/opt/zimbra/common/libexec/master-w

# ps auxw |grep postfix
ps auxw |grep postfix
postfix   5903  0.0  0.1  97340  8868 ?        S    12:52   0:00 proxymap -t unix -u
postfix   5904  0.0  0.0  50888  5264 ?        S    12:52   0:00 anvil -l -t unix -u
postfix   5905  0.0  0.0  67284  5424 ?        S    12:52   0:00 trivial-rewrite -n rewrite -t unix -u
root      7538  0.0  0.0 103388  2256 pts/0    S+   12:56   0:00 grep postfix
postfix  16424  0.0  0.0  51092  5376 ?        S    Mar20   0:00 qmgr -l -t unix -u
postfix  18411  0.0  0.0  50904  5708 ?        S    Mar20   0:00 tlsmgr -l -t unix -u
postfix  20965  0.0  0.0  50896  5292 ?        S    12:00   0:00 pickup -l -t unix -u
postfix  25790  0.0  0.0  50972  5248 ?        S    12:14   0:00 showq -t unix -u
Sometimes people forget to uninstall the default MTA or one is installed without them realizing during an update/reboot. The other thing you could rule out if you have hit a bug. see Ref link below for explanation:

Run these commands as ROOT to verify. These commands should also get you going if you have hit that bug.

Code: Select all

# /opt/zimbra/common/sbin/postfix status
/postfix-script: the Postfix mail system is running: PID: 16422
# /opt/zimbra/common/sbin/postfix stop
/postfix-script: stopping the Postfix mail system
# /opt/zimbra/common/sbin/postfix start
/postfix-script: starting the Postfix mail system
HTH

Ref: viewtopic.php?f=15&t=65332&hilit=MTA+fails
wauters
Posts: 13
Joined: Thu Mar 21, 2019 7:10 pm

Re: Unable to connect to MTA

Post by wauters »

So I fixed it.

I deleted my resolv.conf file and recreated it. Then rebooted. I have no clue why this resolved my issues.
wauters
Posts: 13
Joined: Thu Mar 21, 2019 7:10 pm

Re: Unable to connect to MTA

Post by wauters »

Thank you for the post helping.
User avatar
JDunphy
Outstanding Member
Outstanding Member
Posts: 897
Joined: Fri Sep 12, 2014 11:18 pm
Location: Victoria, BC
ZCS/ZD Version: 9.0.0_P39 NETWORK Edition

Re: Unable to connect to MTA

Post by JDunphy »

DNS resolution is a requirement.

Given that /etc/resolv.conf changed without your knowledge, I would recommend you lock it down. A lot of dhcp clients will reset this in various cloud services. Others will reset it on hard boot up (power on/off).
This is probably the simplest way to lock it so no one else can change it but you.

Code: Select all

chattr +i /etc/resolv.conf
Now not even root can change it after this. If you need to change it in the future, use the -i option to chattr. make your change and then put it back to protected.
Hint: put the commands in that file as a comment to remind you what you did. :-)
Post Reply