Migrating From Scalix To Zimbra: Hostname?

I want to start by thanking every one of you folks who have anything to do with Zimbra. Nice product!

We are currently running the Scalix mailserver and are ready to migrate. We couldn't get the [crypt}'d passwords to transfer into Zimbra, so, we set up a VirtualBox on another server machine, installed Zimbra in it and had all of our users (approx 400) log in and change their passwords.

Our main mail server is at mail.crawfordbroadcasting.com. This temporary was at mail.cbcbham.com (and different IP address), but I set up the VirtualBox so that it thought that it was at mail.crawfordbroadcasting.com. DNSMasq returned the virtual Zimbra's own IP address on mail.crawfordbroadcasting.com. Everything worked fine. I now have a Zimbra store with no mail (except for a few test messages), but about 400 usernames and passwords.

But I think I boo-boo'ed. Without thinking, I set the hostname on the Virtual Zimbra to the full, "mail.crawfordbroadcasting.com" instead of just "mail." When I copy the /opt/zimbra folder from the virtualbox over to the main mail server, install Zimbra (following the Wiki instructions for "Move to a new Server"), I can't get the zmmailctld component to run, regardless of hostname.

Figured It Out.

I wish I could change the title of this thread because it might help someone else out. I originally assumed that it was a hostname issue, but it wasn't. My DNSMasq and hostname settings were fine.

Here's what happened:

If you build Zimbra in a small memory environment, it's going to set up the memory allocations accordingly. Believe it or not, in that limited environment, it may actually allocate MORE memory (as a percentage) to some functions.

In my 2 Gig VirtualBox, it set the mailboxd memory percentage to 40%. When I moved that /opt/zimbra data over to my new server, it tried to allocate that much memory and couldn't.

... solved my problem. The logs were right, there was insufficient free memory when I'd try to start it on the new server, even though it had 4 times as much memory (8 gig).

If anyone hits this thread in a search, I'd suggest that you run zmlocalconfig (without arguments) on your old server, and then on the new, and carefully compare what you get. You can also compare the "config.xxx" files created by the installer, but to me, it's easier to use zmlocalconfig, because the output from that command is already formatted as you'll want them (ex., "mailboxd_java_heap_memory_percent," as shown above, instead of MAILBOXMEMORYPERCENT, as in the config.xxx output).