I was also puzzled about the apparent coexistence of the Zimbra servers with existing software like sendmail and apache. I followed the installation procedure and when I was done, ps showed the zimbra httpd as running along with the default apache httpd that was bound to port 80. An nmap scan of the machine didn't show any unusual ports available, and a connection to port 80 showed that the existing apache server was handling requests on that port.
I would have thought that the installation procedure would notice existing servers attached to ports that Zimbra uses and complain about this during the installation. It neither complained, nor did it stop the existing services. Instead it appeared that the zimbra servers were running alongside the existing ones, but then I should have seen complaints from the OS about a conflict over binding to the standard ports. If there were such complaints from Linux, I didn't see them on my screen during the installation.
While some of the responses here indicate I should have allocated Zimbra to other ports, or deactivated the existing services, nothing in the installation procedure indicated this was necessary. I therefore assumed the installer would handle stopping the relevant services and replacing them with their Zimbra equivalents.  |