Troubleshooting incoming mail

If you're having trouble receiving mail from outside, 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.
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.
To lookup lmtp addresses natively instead of by DNS, simply modify the following localconfig
values on all mta's:
zmlocalconfig -e postfix_lmtp_host_lookup=native
Once this is done, you'll need to restart the mta:

zmmtactl restart
Postfix will now lookup IP's for lmtp natively rather than in DNS, so you'll just need to ensure the
host is properly configured in /etc/hosts and things will work correctly.