Location of imapproxy / nginx logs

[arctics]

After upgrading from 7.1.1 to 7.1.3, the imapproxy service fails to start. After following some threads that indicated that in a single server setup, it wasn't needed, we disabled the imapproxy service from starting using steps similar to these:

remove/disable imapproxy

However, after doing so, clients that require 993 imap connections to the server can no longer do so.

Running netstat -antp reveals that nothing is listening on 993. Which leads me to believe that imapproxy is required for imap clients to connect.

How can I determine what is preventing imapproxy from connecting? Am I looking in the wrong direction here? Is there anything else that may have caused this?

Prior to the upgrade, everything was working fine. Mailflow appears to be functioning fine from within the zimbra webclient.

After working on this for pretty much 20 hrs now, any suggestion would be much appreciated.

Thanks.

[phoenix]

You need to disable imapproxy, memcached and reset the ports to their defaults. You'll find details in the forums on how to do all of that.

[arctics]

Thanks Phoenix, I'll try this.

I'll disable memcached then run:

zmprov -l ms `zmhostname` zimbraPop3BindPort 110 zimbraPop3SSLBindPort 995 zimbraPop3ProxyBindPort 7110 zimbraPop3SSLProxyBindPort 7995 zimbraImapBindPort 143 zimbraImapSSLBindPort 993 zimbraImapProxyBindPort 7143 zimbraImapSSLProxyBindPort 7993

to reset ports.

Thanks

[phoenix]

Originally Posted by arctics

Thanks Phoenix, I'll try this.

You''re welcome.

Originally Posted by arctics

I'll disable memcached then run:

zmprov -l ms `zmhostname` zimbraPop3BindPort 110 zimbraPop3SSLBindPort 995 zimbraPop3ProxyBindPort 7110 zimbraPop3SSLProxyBindPort 7995 zimbraImapBindPort 143 zimbraImapSSLBindPort 993 zimbraImapProxyBindPort 7143 zimbraImapSSLProxyBindPort 7993

to reset ports.

Yes, that's the command you need.

[arctics]

This worked like a charm. Thanks for your help!