You didn't specify what versions of Zimbra you were using (commercial or open source), however, you can just move the /opt/zimbra
directory in a cold migration via scp
or rsync
.
Also, Zimbra gives comprehensive instructions here:
http://wiki.zimbra.com/wiki/Moving_ZCS_to_New_Server
Webmail MTA hostname
Exactly what it says. It's hostname for your server. Since zimbra can be clustered, and you can have multiple servers each one should (ideally) have unique hostname.
eg:
mta1.myzimbra.tld
mta2.myzimbra.tld
This setting should match your unix hostname (for RHEL located @ /etc/sysconfig/network)
Relay MTA for external delivery
Usage scenario: Your zimbra is on your LAN behind a NAT. You use it primarily to send mail in your organisation/company, but your network admin allows connections only to ONE specific external SMTP server.
Your e-mail is john@mycompany.tld and you want to send an e-mail to john.doe@gmail.com, you need to specify external MTA relay hostname.
So it goes: your internal zimbra->external MTA->gmail
Inbound SMTP host name
You do not trust zimbra amavis to sort out your e-mails and do spam and virus checks.
Your MX points to some other machine that does all that for you and then push it to zimbra.
You need to set that hostname so zimbra knows where your e-mail comes from.
MTA Trusted Networks
On a zimbra cluster (multiple servers, one for ldap, other for mta, third for store, fourth for proxy) you should not use global settings for trusted networks. Trusted networks can, depending on your configuration, relay without auth and do some other stuff that non-trusted IP's cannot.
If your using monolithic zimbra conf (everything on one server) you can use either global, or specific settings.
I hope that clears all the issues for you. If you have more questions, ask :)
Best Answer
Well, we found the answer. It was a DNS related issue, kind of. The hosts file had mail.ourdomain.com resolving to 127.0.0.1 instead of the outside IP address interface. So when Zimbra started up it used 127.0.0.1 as the binding address. Looking at the jetty.properties file confirmed this: zimbraPop3BindAddress=mail.ourdomain.com. That is why a netstat -ln showed port 110 bound to 127.0.0.1. We couldn't figure out how to modify the jetty configuration to use a different bindaddress setting (the config kept getting overwritten during restart), so we changed the hosts file to resolve mail.ourdomain.com to only the outside ip address. After restarting the services, the proper port was bound and users were able to connect with pop3 again.
It would be nice to know how to change the jetty configuration as well (any takers?), but for now it is working as desired.