At the moment:
1 server doing everything
2 x MTA/LDAP
2 x Mailbox
1 x Zimbra-proxy (with http reverse proxying)
1) Does zimbra-proxy need to be installed on the mailbox (target) servers as well, or just on the 1 zimbra-proxy (source) dedicated machine?
Since we're using our 1 server setup in production, I can't break that right now. I've trying the proxy setup seperately as follows:
Built a mailbox server (and installed zimbra-proxy on it)
Built the zimbra-proxy box (just installed core and proxy on it)
Used all the default settings for ports in the config and when asked for a master LDAP server, pointed it at our 1 live server
I read this page: http://www.zimbra.com/docs/ne/latest...Proxy.7.1.html and tried various permutations including running the enable (with -w) line on both the proxy and the mailbox servers. I notice that the zimbraMailReferMode is set to 'wronghost' on the 1 live server (it's set to 'reverse-proxied' on the new ones) and if I change it, bad things happen so I have to change it back (which is why I'm guessing you have to install zimbra-proxy on 'target' nodes too).
I've created a user account on the new mailbox server and if I try to log into it through the proxy URL, it works, but still changes the address bar to the name of the mailbox server.
Is this all just not going to work until all the machines in my setup have zimbra-proxy installed? I was hoping to be able to see it work before I went and changed our production setup.
I've read this back and tried to explain things properly, but it doesn't seem to read very well. If I can clarify anything, please let me know. Thanks for any help.
BTW - zmprov doesn't run on the machine that just has core and proxy installed. It gives the following error (but the zmproxyinit command still works and outputs three prov> thingies):
ERROR: zclient.IO_ERROR (invoke Connection refused, server: localhost) (cause: java.net.ConnectException Connection refused)