[SOLVED] imapproxy conflict since 4.5.10 > 5.0.0 upgrade

[mmorse]

zmprov -l ms server.domain.com zimbraImapProxyBindPort 7143 zimbraImapSSLProxyBindPort 7993 zimbraPop3ProxyBindPort 7110 zimbraPop3SSLProxyBindPort 7995

zmprov -l ms server.domain.com -zimbraServiceEnabled imapproxy

When you grep drop the 'enabled' part & do a zmprov gs server.domain.com | grep zimbraService so we can see the output of zimbraServiceInstalled as well

[phoenix]

I assume you are trying to modify the ports via the admin UI? Try modifying them with zmprov, do this:

zmprov gs yourserver.com | grep Pop
zmprov gs yourserver.com | grep Imap

to list the settings for both services. My server shows these default settings:

zimbraPop3BindOnStartup: TRUE
zimbraPop3BindPort: 110
zimbraPop3CleartextLoginEnabled: FALSE
zimbraPop3NumThreads: 20
zimbraPop3ProxyBindPort: 110
zimbraPop3SSLBindOnStartup: TRUE
zimbraPop3SSLBindPort: 995
zimbraPop3SSLProxyBindPort: 995
zimbraPop3SSLServerEnabled: TRUE
zimbraPop3SaslGssapiEnabled: FALSE
zimbraPop3ServerEnabled: TRUE

zimbraImapBindOnStartup: TRUE
zimbraImapBindPort: 143
zimbraImapCleartextLoginEnabled: FALSE
zimbraImapNumThreads: 200
zimbraImapProxyBindPort: 143
zimbraImapSSLBindOnStartup: TRUE
zimbraImapSSLBindPort: 993
zimbraImapSSLProxyBindPort: 993
zimbraImapSSLServerEnabled: TRUE
zimbraImapSaslGssapiEnabled: FALSE
zimbraImapServerEnabled: TRUE

If your settings are different then change them to those settings and restart Zimbra.

[plumsicle]

After doing the grep I receive

zimbraPop3BindOnStartup: TRUE
zimbraPop3BindPort: 7110
zimbraPop3CleartextLoginEnabled: FALSE
zimbraPop3NumThreads: 100
zimbraPop3ProxyBindPort: 110
zimbraPop3SSLBindOnStartup: TRUE
zimbraPop3SSLBindPort: 7995
zimbraPop3SSLProxyBindPort: 995
zimbraPop3SSLServerEnabled: TRUE
zimbraPop3SaslGssapiEnabled: FALSE
zimbraPop3ServerEnabled: TRUE

zimbraImapBindOnStartup: TRUE
zimbraImapBindPort: 7143
zimbraImapCleartextLoginEnabled: TRUE
zimbraImapNumThreads: 200
zimbraImapProxyBindPort: 143
zimbraImapSSLBindOnStartup: TRUE
zimbraImapSSLBindPort: 7993
zimbraImapSSLProxyBindPort: 993
zimbraImapSSLServerEnabled: TRUE
zimbraImapSaslGssapiEnabled: FALSE
zimbraImapServerEnabled: TRUE

I tried using:

zmprov -l ms myserver.com zimbraPop3BindPort 110
ERROR: service.INVALID_REQUEST (invalid request: port 110 conflict between zimbraPop3ProxyBindPort and zimbraPop3BindPort on server myserver.com)

zmprov ms myserver.com zimbraPop3BindPort 110
ERROR: service.INVALID_REQUEST (invalid request: port 110 conflict between zimbraPop3ProxyBindPort and zimbraPop3BindPort on server myserver.com)

When I ran this:

zmprov gacf | grep zimbraService

Nothing was listed. It just came back to the prompt after taking a few seconds to think. Anything else I can try?

Thanks,
Jason.

[mmorse]

Try running all the port settings on one line, & put a 7 in front of anything with proxy in it.

zmprov -l ms server.domain.com zimbraPop3BindPort 110 zimbraPop3SSLBindPort 995 zimbraPop3ProxyBindPort 7110 zimbraPop3SSLProxyBindPort 7995 zimbraImapBindPort 143 zimbraImapSSLBindPort 993 zimbraImapProxyBindPort 7143 zimbraImapSSLProxyBindPort 7993

zmprov gs server.domain.com | grep zimbraService

[plumsicle]

Putting all the ports on one line has solved my problem. Thank you Mike and Bill for all your help through this. And in case this thread will help further people I have done the zmprov gs myserver.com | grep zimbraService:

zimbraServiceEnabled: antivirus
zimbraServiceEnabled: antispam
zimbraServiceEnabled: logger
zimbraServiceEnabled: mailbox
zimbraServiceEnabled: mta
zimbraServiceEnabled: stats
zimbraServiceEnabled: snmp
zimbraServiceEnabled: ldap
zimbraServiceEnabled: spell
zimbraServiceHostname: myserver.com
zimbraServiceInstalled: antivirus
zimbraServiceInstalled: antispam
zimbraServiceInstalled: logger
zimbraServiceInstalled: mailbox
zimbraServiceInstalled: mta
zimbraServiceInstalled: stats
zimbraServiceInstalled: archiving
zimbraServiceInstalled: imapproxy
zimbraServiceInstalled: snmp
zimbraServiceInstalled: ldap
zimbraServiceInstalled: spell

Thank you again for all your help.

Jason.

[mmorse]

How you doing Centrex?

Originally Posted by centrex

Server status page no longer mentions imapproxy

I will now try to manually set the ports for pop and imap now. Previously it wouldn't let me due to port conflict with the proxy.

Edit: Nope, still can't assign normal ports for imap/imaps and pop3/pop3s. It's complaining about a port conflict with proxy.

Any luck with doing them all on one line?

[centrex]

Thanks Bill and Mike,

As user zimbra I did:

zmprov -l ms mail.centrex.com zimbraPop3BindPort 110 zimbraPop3SSLBindPort 995 zimbraPop3ProxyBindPort 7110 zimbraPop3SSLProxyBindPort 7995 zimbraImapBindPort 143 zimbraImapSSLBindPort 993 zimbraImapProxyBindPort 7143 zimbraImapSSLProxyBindPort 7993

all on one line, then as user root I did

service zimbra restart

Now the services are listening on the correct ports.

imapproxy is no longer showing in the server status page and Thunderbird can retrieve and handle messages again!

I wish I could rename the thread title as it really seems to have been purely an issue with incorrect use of imapproxy, nothing directly related to Thunderbird.

Hopefully other people who are affected by this will find this thread anyway.

Thanks again!

[mmorse]

Cool, thanks for marking as solved - I just changed the title a bit - further tracking: Bug 22822 - proxy port issues on upgrade > Bug 22449 - avoid imap port conflicts during upgrades