I have a guy with a fairly simple business network (a modem and several routers) who's having trouble sending email. The clients use Port 110 for receiving email (POP3). It's been working fine for several months then, without warning, started giving him problems this week. Here's a copy of the last email he sent me. I'm more of a software development guy and not a networking guru so I'm tapping as many resources as I can (including technical support at the hosting company).
- I have spent hours and hours on this POP3 timeout problem today
- This includes multiple phone calls to Comcast Business Services, who see my modem easily
- I installed a brand new modem and Comcast successfully configured it
- Multiple routers have been swapped in
- Routers have been set back to factory default, set to a previous known working configuration, and rebooted more times than I care to remember
- Mail.domainname.com accepts POP sending on port 25
- It does not, and has not for much of this week, allow POP receiving on port 110 (this is the problem)
- My comcast address works just fine on port 110
- When I use the modem directly with no router under it, all POP processes--domainname or comcast--work
- However, using the modem and router, I can use Comcast mail on ports 25 and 110; I can ping mail.domainname.com easily; I can send mail using mail.domainname.com easily; and we have internet access. It is only the port 110 for receiving mail that is an issue.
- I set up the firstname.lastname@example.org account in Outlook Express, at the request of Comcast tech, thinking that Thunderbird was perhaps the problem. OE gave exactly the same error: Connection to mail.domainname.com timed out.
- I have uninstalled Microsoft updates from June 12 and since, and Mozilla Firefox 3, thinking any of them could have somehow messed up using port 110
- Using the cPanel, I created a brand new address, email@example.com (pw password), but it shows the same issue: Connecting, hangs there, and times out
- I entered the mail server's IP address in the server field in Thunderbird's settings, with port 110; no difference
- I cannot (in cmd prompt) successfully telnet mail.domainname.com 110
- Comcast and other help I asked say my hosting company needs to check the server
- Perhaps there was a software update that affected the server this week?
- The only far-fetched thing to do yet, besides the possibility of a server glitch, is buy a new router that I know is brand new.