Bobcares

‘Error connecting to IMAP server’ in Squirrelmail – Here’s how to fix it

by | Mar 10, 2019

Squirrelmail provides an easy way to check your emails.

However, sometimes it can lock you out and show errors.

One such error is “error connecting to IMAP server” in Squirrelmail.

At Bobcares, we help website owners resolve these errors as part of our Dedicated Support Services.

‘Error connecting to IMAP server’ in Squirrelmail – What’s this?

Customers usually see this error when they try to connect to Squirrelmail webmail client for checking emails. The complete error message looks like this.

"Error connecting to IMAP server: localhost. 111 : Connection refused"

 

This means that the IMAP server refused the connection made by the webmail client. So, our Support Experts primarily check the email logs(/var/log/mail.log or /usr/local/psa/var/log/maillog) to identify the origin of the problem.

 

‘Error connecting to IMAP server’ in Squirrelmail – Causes & Fixes

Now, let see the top reasons for this error and how our Dedicated Engineers fix them.

1) IMAP service downtime

One of the main reasons for this error is the IMAP service downtime on the server. Customers get locked out of Squirrelmail even though they give the correct login details. This is because the IMAP service isn’t active or dead in the server.

Here, our Support Experts first check the status of the IMAP service. Since the default IMAP port is 143, we check whether any service is listening on this port. For example, we use the below command to confirm if IMAP is running on the server.

netstat -lnpt | grep :143

 

Service downtime may occur due to many reasons like resource outage, disk errors, DDoS, traffic spikes, etc. Here, our Support Engineers identify and permanently fix the reason for the service downtime. Further, if we identify any dead process in the server, we’ll kill those process and restart the service. For example on CentOS 6, we restart the IMAP service using below command.

service dovecot restart

 

2) Firewall restrictions

Similarly, another common reason for this error is server firewall blocking connections to the server or IMAP port. We’ve seen instances where customer’s IP address or IP range get blocked on the server for abnormal activities.

Also, sometimes server firewall can block connections on IMAP ports 143 and 993 or these ports may not be opened in the server firewall. These can create problems and result in error connecting to IMAP server in Squirrelmail.

Firstly, our Support Engineers get the telnet results to IMAP port from the customer’s machine. This shows any connectivity issues between the user’s machine and the server.

telnet xxx.xxx.xxx.xxx 143

 

If we find that the connection doesn’t reach the server, we check whether there are any firewall rules offending the connection. For example, we use the below command to find the IP blocks on a Linux server.

iptables -nL

 

If the IP is blocked, we find the reason for the block and remove the block to restore email connectivity. Moreover, we make sure that the IMAP ports 143 and 993 are opened in the server to accept valid connections.

 

3) IMAP server configuration issues

Similarly, misconfiguration in the IMAP configuration file can also create problems. In other words typo mistakes, syntax errors, etc. can lead to this error connecting to IMAP server in Squirrelmail.

For example, we’ve seen customers face this error due to the wrong mailbox location specified in the dovecot configuration file. The mailbox of the customer is ‘/home/xxx/mbox‘. However, the mail_location wasn’t correctly given in the dovecot configuration file /etc/dovecot/dovecot.conf which created problems.

Our Support Engineers check and correct the configuration issues of the IMAP configuration file. Most importantly, we backup the configuration before making any changes.

[Need an expert to resolve this error? Our Support Engineers can help you here.]

Conclusion

In short, error connecting to IMAP server in Squirrelmail webmail client mainly occurs due to service downtime issues, firewall restrictions, etc. Today, we’ve discussed the top 3 reasons for this error and how our Dedicated Engineers fix them.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

var google_conversion_label = "owonCMyG5nEQ0aD71QM";

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Never again lose customers to poor
server speed! Let us help you.

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

_reb2bgeo - The visitor's geographical location

_reb2bloaded - Whether or not the script loaded for the visitor

_reb2bref - The referring URL for the visit

_reb2bsessionID - The visitor's RB2B session ID

_reb2buid - The visitor's RB2B user ID

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid
_reb2bgeo, _reb2bloaded, _reb2bref, _reb2bsessionID, _reb2buid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF