Disabling Imapproxy

Revision as of 17:12, 24 March 2015 by Jorge de la Cruz (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Admin Article

Article Information

This article applies to the following ZCS versions.

ZCS 4.5 Article ZCS 4.5

In ZCS if you are running the Zimbra server with standard Imap and POP services i.e no proxy is running and if you enable ImapProxy then the Zimbra server will detect port conflicts.

The ports 110 and 143 will become occupied by the Imapproxy services.

Tomcat will not be able to start itself because when it starts it will try to bind to POP and Imap services on port 110 and 143 which are occupied by the proxy services and because of which the following error is received in the catalina.out file:

Error from /opt/zimbra/tomcat/logs/catalina.out:-

   Zimbra server reserving server socket port=110 bindaddr=null ssl=false
   Fatal error: terminating: PrivilegedServlet init failed
   java.net.BindException: Address already in use


Disable ImapProxy using:-

   1) su - zimbra

   2) zmprov -l ms `zmhostname` -zimbraServiceEnabled imapproxy

[-l option will modify the configuration in LDAP as the normal zmprov command will not run, as tomcat is not running and it will give Java errors.]

Restart Zimbra Services.

zmcontrol stop

zmcontrol start

Check if the services are running.

zmcontrol status.

Verified Against: Zimbra Collaboration Suite 4.5.x Date Created: 12/19/2007
Article ID: https://wiki.zimbra.com/index.php?title=Disabling_Imapproxy Date Modified: 2015-03-24

Try Zimbra

Try Zimbra Collaboration with a 60-day free trial.
Get it now »

Want to get involved?

You can contribute in the Community, Wiki, Code, or development of Zimlets.
Find out more. »

Looking for a Video?

Visit our YouTube channel to get the latest webinars, technology news, product overviews, and so much more.
Go to the YouTube channel »

Headline text

Jump to: navigation, search