Quote:
Originally Posted by phoenix If you already have a mail server on your LAN you'll need a split domain setup if you want to migrate to zimbra after testing it. |
Fair enough, the wiki entry is hepful.
I opened my router admin page and routed several of the required ports with forwarding to my zimbra machine's IP address. Then I reran ./install.sh as root on that machine.
It proceeded without incident until this point:
Setting defaults from existing config...Checking for port conflicts
Port conflict detected: 993 (zimbra-store)
Port conflict detected: 389 (zimbra-ldap)
Port conflict detected: 389 (zimbra-ldap)
Port conflict detected: 110 (zimbra-store)
Port conflict detected: 143 (zimbra-store)
Port conflict detected: 25 (zimbra-mta)
Port conflict detected: 80 (zimbra-store)
Port conflicts detected! - Any key to continue
Starting ldap...Done
I don't have all ports forwarded, but had hoped that by forwarding 993, 389, and 707x .. as mentioned on the wiki entry, it would show success on those when checking, but all appear to have failed, despite being forwarded to the correct machine.
What might I be missing with this? Certainly I'd need 25, 80, 110, 143 also forwarded to be complete, but I have to maintain my system in the meantime.
Do I have to rerun the entire ./install.sh routine every time or can I have zimbra just check the port status without running all the rest of it?