Do this on the mailstore...
for i in {8443,7072,7071}; do lsof -i:$i;done
...to verify it's listening on those three ports. Then from the proxy, make sure your reach the mailstore on those three ports
for i in {8443,7072,7071}; do nc -zv mailstore.domain.ext $i ; done
Lastly make sure from the mailstore you can reach the LDAP server (I'm sure this is fine, the mailstore would function otherwise). nc -zv ldap.domain.ext 389.
When you access the Zimbra Web Client through the Proxy and enter your creds in the login page it then asks the mailstore route lookup handler to determine where the user lives (what mailstore), even if you only have one. It does this on 7072 from Proxy to mailstore, then mailstore call LDAP on 389.
for i in {8443,7072,7071}; do lsof -i:$i;done
...to verify it's listening on those three ports. Then from the proxy, make sure your reach the mailstore on those three ports
for i in {8443,7072,7071}; do nc -zv mailstore.domain.ext $i ; done
Lastly make sure from the mailstore you can reach the LDAP server (I'm sure this is fine, the mailstore would function otherwise). nc -zv ldap.domain.ext 389.
When you access the Zimbra Web Client through the Proxy and enter your creds in the login page it then asks the mailstore route lookup handler to determine where the user lives (what mailstore), even if you only have one. It does this on 7072 from Proxy to mailstore, then mailstore call LDAP on 389.
Statistics: Posted by karl.b — Fri Mar 01, 2024 7:45 pm