• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS.

ATMail and Horde timing out when connecting to IMap

W

Workshed

Guest
Hi-

We cannot log into either Horde or ATMail with valid e-mail accounts. ATMail times out connecting to iMap server. Horde grinds away and tells us the username or password is incorrect, but it's not.

I've tried a number of things, but most curious is that I cannot seem to telnet to localhost. It always times out, no matter which port I try.

Running CentOS 5.5 with Plesk 9.5.2.

Here's everything I've tried:

Have upgraded to latest versions of PHP/MySQL/Apache via the Atomic repo.

Have made sure telnet server is enabled for testing. Can telnet from external machine.

Have checked hosts file. It has the 127.0.0.1 localhost localhost.localdomain record.

Netstat says courier-imap is monitoring port 143.

Anyone have any other thoughts? I have a few sites I'm migrating to this new server and they have Horde users, so I sort of need webmail working soon. Seems like something is amiss with the localhost record (can't ping localhost either). It's probably something pretty basic, but I can't seem to find anything online.

BTW, server is a Rackspace Cloud Server.

Any help is appreciated.

Thanks!

-Bret
 
Problem solved. We were missing an IPTabes rule to allow local traffic. D'oh! All fixed now!
 
Could you possibly list the steps you did to fix this? I have run into the same email problems since upgrading to php 5.x with Atomic...
 
Hi- It's been awhile, so I'll try to remember what I did. Basically, in my case, I believe it all amounted to adding the following lines to my iptables, then reloading the iptables rules:

-A INPUT -p tcp -m tcp --dport 143 -j ACCEPT
-A OUTPUT -p tcp -m tcp --dport 143 -j ACCEPT

You *might* have to do this with the SMTP ports as well, but this should open up imap ports for internal and external traffic.

All of that said, I don't think my issue was related to updating PHP, so your mileage may vary.

Hope this helps.
 
Back
Top