Zimbra: Troubleshooting incoming mail problems

Troubleshooting incoming mail problems

If you're having trouble in receiving mail from users, you need to find out where the message is failing.

When sending your test message, check the Log Files, especially /var/log/zimbra.log, on your MTA server.

It's often helpful to tail the logfile as you send the message:

# tail -f /var/log/zimbra.log

If you see nothing logged (no connection, nothing) then the problem likely either DNS or your firewall.

Firewall
To troubleshoot your firewall, it helps to have an account on a system outside of your network. and check.

# service iptables stop


For mail to flow inbound, servers on the internet need to connect to your MTA on port 25.

DNS issues

The mail domain that your user accounts are created under must have an MX record. To test this:

# host -t mx domain

The IP address returned should be the IP (public or private) of your MTA. If it's the public address, make sure that the Firewall is forwarding port 25 to the MTA.

Mail is delivered to the MTA, but not to the mailbox
If there is a line in the /var/log/zimbra.log like:

 postfix/lmtp ... deferred ... connection refused
There is no connection to port 7025 to perform Local Mail Transfer Protocol (LMTP) delivery.

This is nearly always caused by a host that is configured on private IP Space (or using NAT) and that does not have an interface for the public IP address the server resides on. This can be easily fixed by simply using native IP address lookups for lmtp rather than DNS. Alternatively, you could have your internal network's domain name configured to lookup differently internally than it does externally. Using that method is beyond the scope of this document.

Zimbra Collaboration 8.5 or above

ZCS 8.5 or above onwards this attribute is now in ldap - zimbraMtaLmtpHostLookup

# su - zimbra
$ zmprov ms mtaserver.com zimbraMtaLmtpHostLookup native
$ zmmtactl restart

In case that you are using Single Server, be aware always of the Global Config as well:

$ zmprov mcf zimbraMtaLmtpHostLookup native

Once this is done, you'll need to restart the mta:

$ zmmtactl restart
Rewriting configuration files...done.
Stopping saslauthd...done.
Starting saslauthd...done.
/postfix-script: refreshing the Postfix mail system



Comments

Popular posts from this blog

Observium: Configuring Microsoft Windows 2008 Server SNMP Agent

AWS: Introduction to AWS (Amazon Web Services)

System/Server Health Status using PowerShell