Quote:
Originally Posted by Baylink  And note that if you're behind a NAT box, and running the sort of "semi" split DNS necessary to make lmtp not crap out (in my case, an IP alias of your public IP on your private ethernet interface) then you need lines in your /etc/hosts file for *both* IPs, with the private one first. (In fact, John, what I got was the opposite: since I remembered to put the alias in *before* running the install, that was what Zimbra put in /etc/hosts: *only* the public one). |
If a zimbra server is simply behind a NAT router on a private IP then you don't need, nor should you have, both IP addresses in your hosts file - you only need the lines for the loopback and the LAN IP. There's nothing else in the hosts file of any of my Zimbra servers and they work perfectly well. Perhaps it's your specific configuration that's the problem?
BTW, I'm sure you already know this but the need to do a DNS lookup is a Postfix requirement and that's not likely to change.
Quote:
Originally Posted by Baylink It continues to irk me that Zimbra's install assumes that if the machine is benjamin.baylink.com, that it will be answering for email for benjamin.baylink.com; in a properly administered network that is *never* the case. And indeed, that's what it reports as the admin email address: admin@benjamin.baylink.com, an address which is *purposefully* not deliverable here. |
That isn't the case either. If you changed the domain name when you initially installed Zimbra to your correct domain of 'baylink.com' then it would work without problems. If it was installed without changing the domain name then you can rename it at any time so email addresses are correct for
user@baylink.com.