Did you also make changes to the /etc/hosts file to reflect the new name after you changed it with zmsetservername?
Does this fix the certs as well?Originally Posted by KevinH
So what is the conclusion ? Is this script safe to use ?
I gave up changing the hostname.
I used the script, and it seemed to work at first, but found errors after logging in.
In the end, reinstalled zimbra.
Somebody wrote this - but I didn't follow the steps there.
Originally Posted by gutzeit
Last edited by zzzzsg; 04-19-2006 at 03:21 PM.
I'm trying to do the same thing as the original poster. Same issue with the few mailservers that want to do a FQDN lookup with your helo info. Otherwise email flows fine in both directions.
Where is the $myhostname variable in main.cf being pulled from? It doesn't stick when you change it with the postconf -e command. When the server gets rebooted I have to go in and run the command again to set it to mail.mydomain.com.
My internal DNS servers have A and MX records pointing to the Zimbra server's hostname (mail-01.mydomain.com). The outside (ISP) MX record points to mail.mydomain.com which gets NATed and shipped to the Zimbra box. Works fine.
In all my other Postfix installs, this is a snap. Just set the $myhostname variable to mail.mydomain.com and other mail servers can do a FQDN lookup and you're good. I have not had to set the server's hostname the same as the outside MX record.
If you have to do this with Zimbra, is there a safe/clean what to change the server's hostname? I'm in production so reinstalling is not an option.