KB 1311        Last updated on 2015-07-12  

(0 votes)



The Zimbra MTA

Zimbra uses the Postfix MTA server.

How the MTA routes mail

Note: Valid DNS records are necessary in order to send and receive email.

There are three general mail-sending scenarios:

1. sending mail from Zimbra to somewhere on the internet,
2. sending mail between users on the same Zimbra server, and
3. receiving mail from the internet to the Zimbra server.

Let's say the Zimbra server is, hosting mail for users @, and somewhere on the internet is a server, hosting mail for users @

1. Zimbra to the Internet

In order to send mail to a remote domain ( on the internet, Zimbra will look in DNS for the MX record(s) for that domain*. You can check this out yourself with this command: "host -t mx". You should see something like this:

$ host -t mx mail is handled by 10

The MX record "points" to a hostname ( of a machine that receives mail for it. That host also has an A record; once again, you can verify this for yourself: "host -t a", which should produce a result like this (though, if it truly is remote, you will see a publicly routable IP address):

$ host -t a has address

A newly installed Zimbra server can probably send mail to arbitrary remote domains just fine, even if it can't send in the cases that follow, because DNS is already configured for those domains.

2. Zimbra to Zimbra

In order to send mail to a domain hosted on the Zimbra server (, Zimbra will look in DNS for MX record(s) for that domain*. Again, you can check this for yourself: "host -t mx". Like before, you should see an MX record listed that "points" to the Zimbra server ( If your Zimbra server has a private IP address (keywords: private address space, LAN, NAT), you'll need to run what gets called "split dns"*. If you can't send mail to other users on the same Zimbra server, this may be why.

3. Internet to Zimbra

In order for a remote MTA on the internet to send mail to the Zimbra server, the remote host will look in DNS for MX record(s) for the destination domain ( After finding out that the MX record for is, the remote MTA will look for the A record of, so that it can connect to the appropriate server (Zimbra) and deliver the mail. If these entries are not available in public DNS, you probably will not receive mail from remote accounts.

* DNS Lookups

If you disable DNS Lookups (under the MTA tab of the admin console, or with zmprov), Zimbra will end up using (according to the postconf man page) the "gethostbyname() system library routine which normally also looks in /etc/hosts" (based on the entries on the "hosts" line in /etc/nsswitch.conf). If you do this but don't also specify an SMTP relay host (typically your ISP's SMTP server), which will take care of checking DNS, you will reverse your ability to send mail: suddenly you can send mail to other users on the Zimbra server, but you can't send to the internet (though you can still receive mail from the internet either way).

Related Topics

Special Cases and Zimbra Mail Routing Details

Split Domain

Local Mail Transfer Protocol (LMTP) and the zimbraMailHost attribute

Antispam/Antivirus and amavisd

MTA troubleshooting

Troubleshooting mail routing.

Verified Against: Zimbra Collaboration 8.0, 7.0 Date Created: 04/16/2014
Article ID: Date Modified: 2015-07-12

Try Zimbra

Try Zimbra Collaboration with a 60-day free trial.
Get it now »

Want to get involved?

You can contribute in the Community, Wiki, Code, or development of Zimlets.
Find out more. »

Looking for a Video?

Visit our YouTube channel to get the latest webinars, technology news, product overviews, and so much more.
Go to the YouTube channel »

Jump to: navigation, search