Firstly Alex, thanks for reporting this issue. I am still not sure how it got passed our Q&A, as everything worked as expected during testing.

I successfully confirmed the above described problem. To workaround this issue please add the following lines (bold) before # initialize documents (notebook wiki):

# restart zimbra services for changes to take effect
$ZM_SUDO "$ZM_BIN/zmcontrol stop"
$ZM_SUDO "$ZM_BIN/zmcontrol start"

# initialize documents (notebook wiki)
WIKIUSER=wiki@${DOMAIN}

With regards to using a subdomain different to the default mail, the following change should work:

FQDN=mail.${DOMAIN}         # before
FQDN=groupware.${DOMAIN}    # after

Please report back whether the above helps.

I went ahead and changed the "/etc/hosts" file to reflect the correct hostname, etc.

(1)  Changed the entry within the "/etc/hostname" from "zimbra" to "xmail".

(2)  Modified the "/etc/hosts" file:

root@xmail:/etc# more hosts
127.0.0.1       localhost xmail.domain.net
127.0.1.1       zimbra
10.32.214.xxx   srvrxxx        srvrxxx.dmz.domain.net
aaa.bbb.ccc.xxx  xmail           xmail.domain.net

Rebooted several times, and finally got it to take the effects.  Now, I've got an increasing number of "Deferred" emails.  Again, I CAN send email OK, just not receive it.

Also, an annoying little @&*$^@ involving the "/etc/resolv.conf" file.  Need to add additional nameservers.  Current nameserver is nameserver for "dmz.domain.net".  Need to add the 3 nameservers for "domain.net".  Any suggestions?

Last, if I have the Zimbra admin port (7071) NAt'd to something else, say "666" (meaning, external port is "666", internal port within DMZ is "7071"), it doesn't seem to work; however, if I keep the ports the same on both external AND internal, it works fine.  Just to be safe, I am adding IP address and MAC restriction ACLs.  This is a POWERFUL utility.

Any help would be mucho appreciato...

-rad
 

After reviewing what happened, I can't figure out which step I messed up on.

OK...here's 'da deal...I've got everything firewalled to a DMZ.  The DMZ has its own DNS (and yes, I checked the entry for the local DMZ IP address).  DMZ does a passthru on DNS as part of the aliasing and port forwarding...

-rad

OK, here's 'da deal with the setup.  I will try and provide a configuration of my network:

Internet                                                            DMZ

ext IP 122.45.167.222           int IP 10.32.214.222

ext NM 255.255.255.240       int NM 255.255.255.0

ext GW 122.45.167.193        int GW 10.32.214.1
             (router)                         (firewall, which is 122.45.167.207)

ext DNS 122.45.167.201       int DNS 10.32.214.2
             122.45.167.202
             122.45.167.203

Current MX records on external DNS is:

MX 0 mail1.domain.net
MX 1 mail2.domain.net

new address will be "mail1a.domain.net", replacing "mail1.domain.net" -- eventually; "mail2.domain.net" is secondary mail server, and will remain a secondary mail server, and will not be replaced.

Typically, servers utilize the internal DMZ DNS.  So for this server, it is "mail1a.dmz.domain.net", external DNS entry was "mail1a.domain.net".  The internal DMZ DNS server is another server (not Zimbra server).

Resolving externally?  Yes.  I was able to access a SSH account from an offsight lcoation, and it corresponded to "mail1a.domain.net".

I don't know what else to say, except that I am familiar with the SuSE/CentOS/Red Hat environment.  This configuration has me all confused.

=============

Second question, what do I do about the "/etc/network/interfaces", the "/etc/resolv.conf", and the "/etc/motd" files reverting back to whatever the server *thinks* it should be (this implies that there is a configuration somewhere else that is overriding the current configuration files).  This is all well and good, but makes for some interesting times, adding to the confusion.  Any ideas as to how to fix this?

Third, when I took a look at the "/etc/hosts" file after the initial build, it read something to the effect of:

127.0.0.1     localhost
127.0.0.1     zimbra

Typically, I would place a few entries within the "/etc/hosts" file to show this.  On the current "mail1a.domain.net" server, my "/etc/hosts" file is reflected this way:

127.0.0.1     localhost
10.32.214.200     mail1a         mail1a.domain.net
122.45.167.200   mail1a         mail1a.domain.net

The "mail1.domain.net" server is runing "sendmail", and is on the lateest and greater version.  This might be that "split DNS" configuration that Zimbra was discussing on their troubleshooting page. 

========================

I think the combination of not knowing how the Zimbra configuration interacts with everyone else, along with a Debian-like environment (as compared to a Red Hat-ish like environment) has caused some confusion.  I've had to revert back to my previous DNS settings (removing "mail1a.domain.net" as the primary MX/MTA, and replacing it back with "mail1.domain.net"), and will try again reloading the turnkey solution and redoing the whole thing from scratch, but this time, testing it out first with "mail1a.domain.net" as the terrtiary mail server, and going from there.

Did any of this help?

Thanks for all your help.

-rad

P.S. The firewall is IPCOP.

Remember that annoying little feature that I said about the "/etc/resolv.conf", "/etc/network/interfaces" and "/etc/motd" files reverting back to a preconfigured version?  Well..I found out what's causing this...

I am an *OLD* UNIX dude (been working with UNIX since 1978 -- BEFORE the Internet, kiddies...  ;)

I am used to doing things manually and via CLI (called "command-line interface"; non-graphical method, using a serial connection and keyboard, no mouse...ugh).  This is what us "old farts" used back in the days of modems...  ;P

Anywho...the product is called "NetworkManager".  It is an annoyance.  I have sent some seething emails to the Ubuntu development team about this (ahem) "feature".  Nonetheless, here's the scoop on this package:

https://help.ubuntu.com/community/NetworkManager

To turn it OFF, simply type:  /etc/init.d/NetworkManager stop

I'd find methods of ensuring that this forkin' thing doesn't startup, and there are plenty 'o methods from preventing it from starting up...  ;P

Does the Zimbra appliance have chkconfig?  That is how I usually tell services not to start.

I guess if it does not, you can remove the startup files for it.  They should be like /etc/rc3.d/S08NetworkManager, etc.

Hello.

I'm trying to change zimbra server name from mail.example.com to mail.myserver.com :

zmsetservername -d -o mail.example.com -n mail.myserver.com

bash window returning :

zimbra@zimbra:/root$ zmsetservername -d -o mail.example.com -n mail.myserver.com                                                                                       
bash: zmsetservername: command not found

thank you in advance.

?