Outlook cannot connect to incoming POP3 server

This particular email account is my lifeline—it’s easily the most important one I own. I hadn't touched it since before I headed out on my five-day summer vacation, but now that I'm back and settled, I finally went to hit "Send and Receive," only to find everything has gone sideways.

It keeps throwing this error at me:

I’ve been staring at this particular error message long enough to consider making it my desktop wallpaper. It’s that classic, frustrating prompt: "Outlook cannot connect to your incoming (POP3) e-mail server." If you find yourself stuck in this loop, the system suggests reaching out to your server admin or your ISP—as if handing off the problem to someone else actually solves anything. Personally, I've found that when these connection issues start popping up, it's usually less about a catastrophic failure of the internet and more about some minor configuration hiccup or a temporary lapse in communication between the software and the server. It's one of those digital roadblocks that feels remarkably trivial yet completely halts your momentum.

I honestly can't wrap my head around what's going on here, because I know for a fact that nobody has even touched this email account.
It just started happening on its own...

What am I supposed to do here? It’s not just about some random inbox; literally everything that actually matters to me is tied to this specific email address. If I lose access, I'm essentially locked out of my entire digital life. Does anyone have a roadmap for fixing this, or am I just staring at a dead end?

Just ditch Outlook and log in directly through the webmail service instead.

William Richardson12 said:Just ditch Outlook and log in directly through the webmail service instead.

Sure, but we aren't talking about Gmail or Yahoo here.

This is an account I've been holding onto since 2002, and honestly, I've always just relied on Outlook to handle everything. It’s become a bit of a ritual at this point; the only thing that’s really shifted in all those years is the outgoing server settings.

email: ryan.gonzalez4@verizon.net

The incoming settings have worked perfectly fine for me right up until today...

Try logging in a different way, maybe through some other app instead of Outlook... if you can actually get in, finding a fix will be a lot easier.

William Richardson12 said:Try logging in a different way, maybe through some other app instead of Outlook... if you can actually get in, finding a fix will be a lot easier.

I’ve already given Thunderbird a shot, and frankly, it was a total bust. This isn't just some minor glitch I can ignore; it’s actually a massive headache for me. Does anyone have any other suggestions? I'm fairly certain there's a workaround out there somewhere, but I'm at a loss as to how to track it down.

Zimbra:

Unable to establish a connection to "pop.verizon.net:110". You might want to double-check the host, the port, or your general network stability.
View error specifics
com.zimbra.common.soap.SoapFaultException: pop.verizon.net:110 ExceptionId:com.zimbra.common.service.RemoteServic eException: pop.verizon.net:110 ExceptionId:btpool0-15:1410032081367:baeedea057ad69f6 Code:remote.CONNECT_FAILURE at com.zimbra.common.service.RemoteServiceException.C ONNECT_FAILURE(RemoteServiceException.java:80) at com.zimbra.common.service.RemoteServiceException.d oConnectionFailures(RemoteServiceException.java:16 3) at com.zimbra.cs.account.offline.OfflineProvisioning. testDataSource(OfflineProvisioning.java:758) at com.zimbra.cs.account.offline.OfflineProvisioning. createDataSourceAccount(OfflineProvisioning.java:8 35) at com.zimbra.cs.account.offline.OfflineProvisioning. createAccount(OfflineProvisioning.java:641) at com.zimbra.cs.service.admin.CreateAccount.handle(C reateAccount.java:64) at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEng ine.java:412) at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:287) at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:158) at com.zimbra.soap.SoapServlet.doWork(SoapServlet.java:303) at com.zimbra.soap.SoapServlet.doPost(SoapServlet.java:217) at javax.servlet.http.HttpServlet.service(HttpServlet .java:725) at com.zimbra.cs.servlet.ZimbraServlet.service(Zimbra Servlet.java:206) at javax.servlet.http.HttpServlet.service(HttpServlet .java:814) at org.mortbay.jetty.servlet.ServletHolder.handle(Ser vletHolder.java:511) at org.mortbay.jetty.servlet.ServletHandler.handle(Se rvletHandler.java:390) at org.mortbay.jetty.security.SecurityHandler.handle( SecurityHandler.java:218) at org.mortbay.jetty.servlet.SessionHandler.handle(Se ssionHandler.java:182) at org.mortbay.jetty.handler.ContextHandler.handle(Co ntextHandler.java:765) at org.mortbay.jetty.webapp.WebAppContext.handle(WebA ppContext.java:422) at org.mortbay.jetty.handler.ContextHandlerCollection .handle(ContextHandlerCollection.java:230) at org.mortbay.jetty.handler.HandlerCollection.handle (HandlerCollection.java:114) at org.mortbay.jetty.handler.HandlerWrapper.handle(Ha ndlerWrapper.java:152) at org.mortbay.jetty.handler.rewrite.RewriteHandler.h andle(RewriteHandler.java:230) at org.mortbay.jetty.handler.HandlerWrapper.handle(Ha ndlerWrapper.java:152) at org.mortbay.jetty.Server.handle(Server.java:326) at org.mortbay.jetty.HttpConnection.handleRequest(Htt pConnection.java:585) at org.mortbay.jetty.HttpConnection$RequestHandler.co ntent(HttpConnection.java:988) at org.mortbay.jetty.HttpParser.parseNext(HttpParser. java:756) at org.mortbay.jetty.HttpParser.parseAvailable(HttpPa rser.java:218) at org.mortbay.jetty.HttpConnection.handle(HttpConnec tion.java:415) at org.mortbay.jetty.io.nio.SelectChannelEndPoint.run(Selec tChannelEndPoint.java:429) at org.mortbay.thread.BoundedThreadPool$PoolThread.ru n(BoundedThreadPool.java:451) Caused by: java.net.ConnectException: Connection refused: connect at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(Unknown Source) at java.net.PlainSocketImpl.connectToAddress(Unknown Source) at java.net.PlainSocketImpl.connect(Unknown Source) at java.net.SocksSocketImpl.connect(Unknown Source) at java.net.Socket.connect(Unknown Source) at com.zimbra.cs.mailclient.MailConnection.newSocket( MailConnection.java:419) at com.zimbra.cs.mailclient.MailConnection.connect(Ma ilConnection.java:74) at com.zimbra.cs.datasource.Pop3Sync.connect(Pop3Sync .java:148) at com.zimbra.cs.datasource.Pop3Sync.test(Pop3Sync.ja va:109) at com.zimbra.cs.datasource.DataSourceManager.test(Da taSourceManager.java:209) at com.zimbra.cs.account.offline.OfflineProvisioning. testDataSource(OfflineProvisioning.java:745) ... 30 more Code:remote.CONNECT_FAILURE at com.zimbra.common.soap.Soap12Protocol.soapFault(So ap12Protocol.java:88) at com.zimbra.common.soap.SoapTransport.extractBodyEl ement(SoapTransport.java:354) at com.zimbra.common.soap.SoapTransport.parseSoapResp onse(SoapTransport.java:313) at com.zimbra.common.soap.SoapHttpTransport.invoke(So apHttpTransport.java:260) at com.zimbra.common.soap.SoapHttpTransport.invoke(So apHttpTransport.java:164) at com.zimbra.common.soap.SoapTransport.invoke(SoapTr ansport.java:407) at com.zimbra.common.soap.SoapTransport.invokeWithout Session(SoapTransport.java:393) at com.zimbra.cs.account.soap.SoapProvisioning.invoke Request(SoapProvisioning.java:342) at com.zimbra.cs.account.soap.SoapProvisioning.invoke (SoapProvisioning.java:350) at com.zimbra.cs.account.soap.SoapProvisioning.create Account(SoapProvisioning.java:493) at com.zimbra.cs.offline.jsp.JspProvStub.createOfflin eDataSource(JspProvStub.java:126) at com.zimbra.cs.offline.jsp.XmailBean.doRequest(Xmai lBean.java:262) at com.zimbra.cs.offline.jsp.FormBean.doRequest(FormB ean.java:156) at sun.reflect.GeneratedMethodAccessor33.invoke(Unkno wn Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unkno wn Source) at java.lang.reflect.Method.invoke(Unknown Source) at com.sun.el.parser.AstFunction.getValue(AstFunction .java:127) at com.sun.el.ValueExpressionImpl.getValue(ValueExpre ssionImpl.java:206) at org.apache.jasper.runtime.PageContextImpl.evaluate Expression(PageContextImpl.java:1001) at org.apache.jsp.desktop.accsetup_jsp._jspx_meth_c_w hen_3(Unknown Source) at org.apache.jsp.desktop.accsetup_jsp._jspx_meth_c_c hoose_0(Unknown Source) at org.apache.jsp.desktop.accsetup_jsp._jspService(Un known Source) at org.apache.jasper.runtime.HttpJspBase.service(Http JspBase.java:109) at javax.servlet.http.HttpServlet.service(HttpServlet .java:814) at org.apache.jasper.servlet.JspServletWrapper.servic e(JspServletWrapper.java:389) at org.apache.jasper.servlet.JspServlet.serviceJspFil e(JspServlet.java:486) at org.apache.jasper.servlet.JspServlet.service(JspSe rvlet.java:380) at javax.servlet.http.HttpServlet.service(HttpServlet .java:814) at com.zimbra.webClient.servlet.JspServlet.service(Js pServlet.java:64) at org.mortbay.jetty.servlet.ServletHolder.handle(Ser vletHolder.java:511) at org.mortbay.jetty.servlet.ServletHandler$CachedCha in.doFilter(ServletHandler.java:1166) at com.zimbra.cs.servlet.SetHeaderFilter.doFilter(Set HeaderFilter.java:79) at com.zimbra.webClient.filters.SetHeaderFilter.doFil ter(SetHeaderFilter.java:239) at org.mortbay.jetty.servlet.ServletHandler$CachedCha in.doFilter(ServletHandler.java:1157) at org.mortbay.jetty.servlet.ServletHandler.handle(Ser vletHandler.java:388) at org.mortbay.jetty.servlet.SecurityHandler.handle( SecurityHandler.java:218) at org.mortbay.jetty.servlet.SessionHandler.handle(Se ssionHandler.java:182) at org.mortbay.jetty.handler.ContextHandler.handle(Co ntextHandler.java:765) at org.mortbay.jetty.webapp.WebAppContext.handle(WebA ppContext.java:422) at org.mortbay.jetty.handler.ContextHandlerCollection .handle(ContextHandlerCollection.java:230) at org.mortbay.jetty.handler.HandlerCollection.handle (HandlerCollection.java:114) at org.mortbay.jetty.handler.HandlerWrapper.handle(Ha ndlerWrapper.java:152) at org.mortbay.jetty.handler.rewrite.RewriteHandler.h andle(RewriteHandler.java:230) at org.mortbay.jetty.handler.HandlerWrapper.handle(Ha ndlerWrapper.java:152) at org.mortbay.jetty.Server.handle(Server.java:326) at org.mortbay.jetty.HttpConnection.handleRequest(Htt pConnection.java:585) at org.mortbay.jetty.HttpConnection$RequestHandler.co ntent(HttpConnection.java:988) at org.mortbay.jetty.HttpParser.parseNext(HttpParser. java:756) at org.mortbay.jetty.HttpParser.parseAvailable(HttpPa rser.java:218) at org.mortbay.jetty.HttpConnection.handle(HttpConnec tion.java:415) at org.mortbay.jetty.io.nio.SelectChannelEndPoint.run(Selec tChannelEndPoint.java:429) at org.mortbay.thread.BoundedThreadPool$PoolThread.ru n(BoundedThreadPool.java:451)

Ryan Gonzalez4 said:Sure, but we aren't talking about Gmail or Yahoo here.

This is an account I've been holding onto since 2002, and honestly, I've always just relied on Outlook to handle everything. It’s become a bit of a ritual at this point; the only thing that’s really shifted in all those years is the outgoing server settings.

email: ryan.gonzalez4@verizon.net

The incoming settings have worked perfectly fine for me right up until today...

In that case, just get in touch with your email provider and ask them if they've messed with any of the POP3 configurations lately.

Pro tip: just ditch POP3 altogether.

Honestly, my money is on the mail server being totally dead... Ever since AT&T swallowed up those old legacy providers back in the day, they've been trimming all the fat, so they probably just pulled the plug on those old corporate addresses
Bottom line, though? Just give the company providing your email service a call and ask them if their systems are actually still breathing

After getting my PC fixed, the guys installed Windows 8 on me, and now I can't get into my email through Outlook Express. I called AT&T and they’re saying they don't support Windows 8 anymore. What am I supposed to do?
I heard from a few people that there might be a workaround.
If anyone could point me in the right direction, I'd really appreciate it.

@ Calvin Klein
If you haven't sorted this out yet, take a look here.

@ minael
Windows Mail is strictly for Windows XP; it won't work on Windows Vista, Windows 7, or Windows 8/8.1.
Just use the Mail app instead.