I have installed my 1st single server zcs OS 7.0 environment. However going through the documentation raises a number of questions I would like to understand please.

I'm a bit wary about putting a large nr of questions in one thread as people tend to answer the ones they can and the others get lost in the noise. By the same token however, I'm also a little wary, as a new user, about (effectively) "spamming" the forum with multiple threads, so hopefully you will understand the multi-faceted post.

So the questions are;

managing/adding domains
when installing, zimbra recognises the hostname as the 'default' domain (e.g. host.domain.com) and complains if there is no MX record for that hostname FQDN. So during install you change the domain name to 'domain.com', it finds an MX record (e.g. mail.domain.com) and goes its merry way. I really don't want to be digging around in LDAP or MySQL messing with settings before I even have the thing up and running for the first time.

On a single server zimbra installation, if you have to have your DNS set up (be that on the zimbra box or elsewhere) and pointing to the zimbra host in order to enable you to do the install, how do you keep your present day mail server (which is a manual postfix/dovecot/clamav/spamassassin/horde install) online and working and still get zimbra installed with the necessary settings?


In two different areas of the documentation, it appears to indicate that if I want to;

1. accept mail for multiple different domains (_not_ virtual domains) or
2. Want users to be able to access their zimbra accounts via T'Bird, OSX Mail, etc.

then I HAVE TO have installed the zimbra proxy. EVEN IF I am carrying out a single server install. Is this correct?

If so, is it possible to install the proxy after the initial install has completed?
Does it then also automagically configure itself or what do I have to do in order to integrate it?


What benefit/use is there in implementing an "LMTP advertised name" on a single server install? Nothing?
Ditto the LMTP bind address?


Virtual Hosts - The documentation reads "…The virtual host requires a valid DNS configuration with an A record. Not required for Virtual Hosts…"
Which is it? Does it need an A record or not?


Documentation simultaneously speaks of domain aliases and virtual domains. Are these the same thing?
If not, are these absolutely separate from "Domains" you create for which you want to receive email? What I mean here is, if I understand it correctly;
Real Domains			Aliases (*assuming I own these domain names)
============			========
mydomain.com			parents.com, friends.com
family.com			uncles.com, aunties.com

Installing SSL certs, the documentation speaks of "…For each domain, a virtual host name and Virtual IP address are configured with the virtual domain name and IP address…" If I read this correctly, I have to set this up? Why?

And can the virtual host name I am now setting up in order to accommodate the SSL cert. be the same as any virtual host name I have set up by which end-users will log on. (I would think it would _have_ to be the same.)


Webmail MTA - Given Zimbra IS a web client, what is the difference between the "Zimbra MTA" and the "Webmail MTA"?

Presumably zimbra is architected and automatically installed such that the webmail MTA will hand off any externally addressed mails to the relay host (should one be configured)?

Also, if I'm reading the admin console correctly, zimbra has already installed a webmail MTA using the installed hostname; effectively meaning if I only want the one, I have to do nothing. Is this correct?


Relay MTA - IF I'm going to use a relay MTA, is there any way to add 'relay MTA - authentication information' into zimbra? I.e. separate to the physical user sending the mail - such as the ISP user/pass details?


Enable DNS lookup - disabling this forces all mail to traverse through the relay host, yes?


User URL to login - As I understand it, you set up a 'virtual host' url which end users use to access zimbra. Is this correct? Is there anything else I have to do other than have a valid DNS A record.
Because using a self-contained test host I have done both these and yet a browser on this self-contained host is unable to connect. This despite a 'dig @ virtualhost.domain.com' offering up the relevant hostname/IP.