• [Server Disconnect] error when the server fails to establish connection with the ports
  

• [Connection Error] when the web mail server refuses the connection.
  

• If the port numbers related to IMAP configuration are expired or closed 
  

• If there are multiple instances of same user's IMAP configured in different Zoho CRM accounts.
  

• If the IMAP is not properly configured inside Zoho CRM
  

How can you resolve these errors?

If the port numbers related to IMAP configuration are expired or closed:

- Check whether the ports related to IMAP configuration are open by using the link http://ping.eu/port-chk/. If it's closed ask your administrator to open the ports and if it's expired check with your Email service provider or system administrator for the updated port number.

If there are multiple instances of same user's IMAP configured in different Zoho CRM accounts:

-Ensure you have just one instance of IMAP open in Zoho CRM. If there are multiple instances, closing the other instances would help fix this issue.

If the IMAP is not properly configured inside Zoho CRM:

To configure IMAP inside CRM, Go to CRM Settings --->Setup --->Email settings ---> Email integration and update the IMAP information. To get the IMAP configuration details, follow the below steps:

• If you are using the Exchange server, get the IMAP information from your Exchange Server and update it in Zoho CRM. 
  

• If you are using a web mail, login to your email and get the valid IMAP configuration details. 
  

The steps shared here should help fix this issue. If you still encounter the same problem, try white listing the Zoho IP ranges - listed below - in the web mail server.

US3

8.40.222.0/24

8.40.223.0/23

216.52.72.0/24

204.141.32.0/24

US4

8.39.54.0/24

8.39.55.0/23

204.141.32.0/24

204.141.42.0/24

65.154.166.0/24

EU1

31.186.226.11/24

185.20.209.0 /24

EU2

84.207.209.0/24

87.252.213.0/24

Firewall IP's EU1

95.172.78.137

91.135.68.110

Firewall IP's EU2

87.252.215.25 

217.112.154.222

If the issue persists, do post in our community or contact our support team for the fix. We will continue to add more fixes to other prominent error messages in the coming weeks. Stay tuned!