Results 1 to 10 of 10

Thread: Cannot connect to "mail.xxxxxxxxx.com:110". Please check host/port and network connec

  1. #1
    Join Date
    Jan 2010
    Location
    Cochrane, Alberta
    Posts
    40
    Rep Power
    5

    Default Cannot connect to "mail.xxxxxxxxx.com:110". Please check host/port and network connec

    I'm trying to setup a new POP account and I'm getting this error:

    Cannot connect to "mail.xxxxxxx.com:110". Please check host/port and network connectivity.

    Same goes for IMAP.

    I can connect to a Zimbra email server however.

    This is basic stuff and should just work. Every other email client I've tried works.

    I'm trying to pitch some clients on switching to zdesktop so a fix soon would be nice.

    thx
    Glenn
    Last edited by ArcaneMagus; 01-19-2010 at 10:07 AM. Reason: Changed title to match post content

  2. #2
    Join Date
    Feb 2007
    Location
    Portland, OR
    Posts
    1,147
    Rep Power
    10

    Default

    It's rather hard to diagnose a "can't connect" without a bit more information... the most that can generally be said is "check your spelling".

    However using the old title of your post (which I changed to xxxxxxx to match what you wrote within the post) I can tell you that I can open a connection to the server, so something is blocking your outbound port 110 connection, or you need to check your spelling

  3. #3
    Join Date
    Jan 2010
    Location
    Cochrane, Alberta
    Posts
    40
    Rep Power
    5

    Default Can't connect

    Hi there,


    That's the error that Zimbra gives me when I try and create a POP or IMAP account and Validate and Save:

    Cannot connect to "mail.xxxxxxx.com:110". Please check host/port and network connectivity.

    I also have the same problem from my laptop and I don't experience this problem using other email clients.

    Here's the log file entry:

    2010-01-18 19:14:53,703 INFO [btpool0-18] [] datasource - Testing: DataSource: { id=8e9611ac-19bb-4448-988c-2b33b0ec221c, type=pop3, isEnabled=true, name=Glenn, host=mail.e-xxxxxxx.com, port=110, connectionType=cleartext, username=glenn@xxxxxxx.com, folderId=2 }
    2010-01-18 19:14:53,781 DEBUG [btpool0-18] [] pop - S: +OK Hello there. <7360.1263867292@localhost.localdomain>
    2010-01-18 19:14:53,781 DEBUG [btpool0-18] [] pop - C: CAPA
    2010-01-18 19:14:53,781 DEBUG [btpool0-18] [] pop - S: +OK Here's what I can do:
    2010-01-18 19:14:53,781 DEBUG [btpool0-18] [] pop - S: STLS
    2010-01-18 19:14:53,781 DEBUG [btpool0-18] [] pop - S: TOP
    2010-01-18 19:14:53,781 DEBUG [btpool0-18] [] pop - S: USER
    2010-01-18 19:14:53,781 DEBUG [btpool0-18] [] pop - S: LOGIN-DELAY 10
    2010-01-18 19:14:53,781 DEBUG [btpool0-18] [] pop - S: PIPELINING
    2010-01-18 19:14:53,781 DEBUG [btpool0-18] [] pop - S: UIDL
    2010-01-18 19:14:53,781 DEBUG [btpool0-18] [] pop - S: IMPLEMENTATION Courier Mail Server
    2010-01-18 19:14:53,781 DEBUG [btpool0-18] [] pop - S: .
    2010-01-18 19:14:53,781 DEBUG [btpool0-18] [] pop - C: STLS
    2010-01-18 19:14:53,796 DEBUG [btpool0-18] [] pop - S: +OK Begin SSL/TLS negotiation now.
    2010-01-18 19:14:53,890 WARN [btpool0-18] [] datasource - Test failed: DataSource: { id=8e9611ac-19bb-4448-988c-2b33b0ec221c, type=pop3, isEnabled=true, name=Glenn, host=mail.xxxxxxx.com, port=110, connectionType=cleartext, username=glenn@xxxxxxx.com, folderId=2 }
    com.zimbra.common.service.ServiceException: system failure: Unable to connect to IMAP server: DataSource: { id=8e9611ac-19bb-4448-988c-2b33b0ec221c, type=pop3, isEnabled=true, name=Glenn, host=mail.xxxxxxx.com, port=110, connectionType=cleartext, username=glenn@xxxxxxx.com, folderId=2 }
    ExceptionId:btpool0-18:1263867293890:58db7f7c3ffba6e2
    Code:service.FAILURE
    at com.zimbra.common.service.ServiceException.FAILURE (ServiceException.java:253)
    at com.zimbra.cs.datasource.Pop3Sync.connect(Pop3Sync .java:142)
    at com.zimbra.cs.datasource.Pop3Sync.test(Pop3Sync.ja va:98)
    at com.zimbra.cs.datasource.DataSourceManager.test(Da taSourceManager.java:67)
    at com.zimbra.cs.account.offline.OfflineProvisioning. testDataSource(OfflineProvisioning.java:587)
    at com.zimbra.cs.account.offline.OfflineProvisioning. createDataSourceAccount(OfflineProvisioning.java:6 85)
    at com.zimbra.cs.account.offline.OfflineProvisioning. createAccount(OfflineProvisioning.java:475)
    at com.zimbra.cs.service.admin.CreateAccount.handle(C reateAccount.java:58)
    at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEng ine.java:429)
    at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:286)
    at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:160)
    at com.zimbra.soap.SoapServlet.doPost(SoapServlet.jav a:275)
    at javax.servlet.http.HttpServlet.service(HttpServlet .java:727)
    at com.zimbra.cs.servlet.ZimbraServlet.service(Zimbra Servlet.java:187)
    at javax.servlet.http.HttpServlet.service(HttpServlet .java:820)
    at org.mortbay.jetty.servlet.ServletHolder.handle(Ser vletHolder.java:487)
    at org.mortbay.jetty.servlet.ServletHandler.handle(Se rvletHandler.java:362)
    at org.mortbay.jetty.security.SecurityHandler.handle( SecurityHandler.java:216)
    at org.mortbay.jetty.servlet.SessionHandler.handle(Se ssionHandler.java:181)
    at org.mortbay.jetty.handler.ContextHandler.handle(Co ntextHandler.java:716)
    at org.mortbay.jetty.webapp.WebAppContext.handle(WebA ppContext.java:406)
    at org.mortbay.jetty.handler.ContextHandlerCollection .handle(ContextHandlerCollection.java:211)
    at org.mortbay.jetty.handler.HandlerCollection.handle (HandlerCollection.java:114)
    at org.mortbay.jetty.handler.HandlerWrapper.handle(Ha ndlerWrapper.java:139)
    at org.mortbay.jetty.handler.RewriteHandler.handle(Re writeHandler.java:176)
    at org.mortbay.jetty.handler.HandlerWrapper.handle(Ha ndlerWrapper.java:139)
    at org.mortbay.jetty.Server.handle(Server.java:313)
    at org.mortbay.jetty.HttpConnection.handleRequest(Htt pConnection.java:506)
    at org.mortbay.jetty.HttpConnection$RequestHandler.co ntent(HttpConnection.java:844)
    at org.mortbay.jetty.HttpParser.parseNext(HttpParser. java:644)
    at org.mortbay.jetty.HttpParser.parseAvailable(HttpPa rser.java:211)
    at org.mortbay.jetty.HttpConnection.handle(HttpConnec tion.java:381)
    at org.mortbay.io.nio.SelectChannelEndPoint.run(Selec tChannelEndPoint.java:396)
    at org.mortbay.thread.BoundedThreadPool$PoolThread.ru n(BoundedThreadPool.java:442)
    Caused by: java.net.SocketException: Connection reset
    at java.net.SocketInputStream.read(Unknown Source)
    at com.sun.net.ssl.internal.ssl.InputRecord.readFully (Unknown Source)
    at com.sun.net.ssl.internal.ssl.InputRecord.read(Unkn own Source)
    at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRec ord(Unknown Source)
    at com.sun.net.ssl.internal.ssl.SSLSocketImpl.perform InitialHandshake(Unknown Source)
    at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHa ndshake(Unknown Source)
    at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHa ndshake(Unknown Source)
    at com.zimbra.common.util.CustomSSLSocket.startHandsh ake(CustomSSLSocket.java:197)
    at com.zimbra.cs.mailclient.MailConnection.startTls(M ailConnection.java:293)
    at com.zimbra.cs.mailclient.MailConnection.connect(Ma ilConnection.java:89)
    at com.zimbra.cs.datasource.Pop3Sync.connect(Pop3Sync .java:134)
    ... 32 more


    Hope this helps more and thanks for x'ing out my domain name.

    Cheers
    Glenn

  4. #4
    Join Date
    Jan 2010
    Location
    Cochrane, Alberta
    Posts
    40
    Rep Power
    5

    Default Bump

    Still need help with this.

    thx
    Glenn

  5. #5
    Join Date
    Mar 2009
    Location
    Sarajevo
    Posts
    44
    Rep Power
    6

    Default

    Hello. I'm trying to find a similar problem in order not to start a new thread. This seems similar except I started to have a problem after the upgrade to 6.0.7. When I login in ZWA, I get an error for my EXTERNAL IMAP accounts "Error: Connection reset".
    Everything worked fine with versions up to 6.0.6. What I think is that the external IMAP server is not using SSL, only port 143 is open.

    Here is part of my mailbox.log:
    2010-06-17 11:30:05,749 WARN [ScheduledTask-2] [name=login@mail;.... datasource - Scheduled DataSource import failed.
    com.zimbra.common.service.ServiceException: system failure: Unable to connect to IMAP server: DataSource: ... type=imap,
    isEnabled=true, name=name, host=IP, port=143, connectionType=cleartext, username=Code:service.FAILURE login@mail folderId=1304 }
    ExceptionId:ScheduledTask-...
    Code:service.FAILURE
    at com.zimbra.common.service.ServiceException.FAILURE (ServiceException.java:248)
    at com.zimbra.cs.datasource.imap.ImapSync.connect(Ima pSync.java:248)
    at com.zimbra.cs.datasource.imap.ImapSync.importData( ImapSync.java:84)
    at com.zimbra.cs.datasource.imap.ImapSync.importData( ImapSync.java:79)
    at com.zimbra.cs.datasource.DataSourceManager.importD ata(DataSourceManager.java:254)
    at com.zimbra.cs.datasource.DataSourceManager.importD ata(DataSourceManager.java:214)
    at com.zimbra.cs.datasource.DataSourceTask.call(DataS ourceTask.java:82)
    at com.zimbra.cs.datasource.DataSourceTask.call(DataS ourceTask.java:28)
    at com.zimbra.common.util.TaskScheduler$TaskRunner.ca ll(TaskScheduler.java:96)
    at java.util.concurrent.FutureTask$Sync.innerRun(Futu reTask.java:303)
    at java.util.concurrent.FutureTask.run(FutureTask.jav a:138)
    at java.util.concurrent.ScheduledThreadPoolExecutor$S cheduledFutureTask.access$301(ScheduledThreadPoolE xecutor.java:98)
    at java.util.concurrent.ScheduledThreadPoolExecutor$S cheduledFutureTask.run(ScheduledThreadPoolExecutor .java:207)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run Task(ThreadPoolExecutor.java:886)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:908)
    at java.lang.Thread.run(Thread.java:619)
    Caused by: java.net.SocketException: Connection reset
    at java.net.SocketInputStream.read(SocketInputStream. java:168)
    at com.sun.net.ssl.internal.ssl.InputRecord.readFully (InputRecord.java:293)
    at com.sun.net.ssl.internal.ssl.InputRecord.read(Inpu tRecord.java:331)
    at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRec ord(SSLSocketImpl.java:789)
    at com.sun.net.ssl.internal.ssl.SSLSocketImpl.perform InitialHandshake(SSLSocketImpl.java:1112)
    at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRec ord(SSLSocketImpl.java:789)
    at com.sun.net.ssl.internal.ssl.SSLSocketImpl.perform InitialHandshake(SSLSocketImpl.java:1112)
    at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHa ndshake(SSLSocketImpl.java:1139)
    at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHa ndshake(SSLSocketImpl.java:1123)
    at com.zimbra.common.net.CustomSSLSocket.startHandsha ke(CustomSSLSocket.java:90)
    at com.zimbra.cs.mailclient.MailConnection.startTls(M ailConnection.java:108)
    at com.zimbra.cs.mailclient.MailConnection.connect(Ma ilConnection.java:92)
    at com.zimbra.cs.datasource.imap.ImapSync.connect(Ima pSync.java:231)

    Is this an upgrade or other issue? Where should I look further?

  6. #6
    Join Date
    Jan 2010
    Location
    Cochrane, Alberta
    Posts
    40
    Rep Power
    5

    Default Check MTA Trusted Networks under Servers

    Check your Trusted Network settings under the MTA in Servers.

    I had to change it to this:

    127.0.0.0/8 192.168.10.0/24 192.168.10.60/32

    my internal IP is 192.168.10.60 so your IP settings will reflect your IP range.

    I was using an earlier version so not sure if this applies since yours was already working before.

  7. #7
    Join Date
    Mar 2009
    Location
    Sarajevo
    Posts
    44
    Rep Power
    6

    Default

    Trusted Networks is for internal connections, that's a relay issue, and my problem is for external accounts connected through IMAP.
    I don't think I should put some external addresses here.

  8. #8
    Join Date
    Jan 2010
    Location
    Cochrane, Alberta
    Posts
    40
    Rep Power
    5

    Default Trusted Networks

    Those are internal addresses. Try it. If it doesn't work then switch back.

  9. #9
    Join Date
    Feb 2007
    Location
    Portland, OR
    Posts
    1,147
    Rep Power
    10

    Default

    The trusted network setting should have no affect on this issue at all. From what it looks like it is unable to access the information for the external account properly. Since these are external IMAP accounts have you tried simply removing the account and adding it back?

  10. #10
    Join Date
    Sep 2006
    Location
    477 Congress Street | Portland, ME 04101
    Posts
    1,374
    Rep Power
    11

    Default

    Looks like this could be caused by Bug 48129 &ndash; 6.0.7 upgrade failure, Could not bind to port=143.

    Fixed in 6.0.7.1.

    Hope that helps,
    Mark

Similar Threads

  1. Replies: 5
    Last Post: 08-14-2010, 07:28 AM
  2. Replies: 3
    Last Post: 09-15-2009, 05:09 AM
  3. Replies: 1
    Last Post: 09-08-2009, 08:58 PM
  4. upgrading to network edition
    By zzzzsg in forum Installation
    Replies: 11
    Last Post: 03-06-2008, 09:58 PM
  5. Curl Dep Check ZCS Network Ubuntu 6.06 LTS
    By EnriqueI in forum Installation
    Replies: 2
    Last Post: 02-01-2008, 02:20 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •