Results 1 to 3 of 3

Thread: External account failed in Beta 6.0.2

  1. #1
    Join Date
    Jun 2009
    Posts
    5
    Rep Power
    6

    Default External account failed in Beta 6.0.2

    Hi, i upgrade to Beta 6.0.2 from 5.0.2 and now the get email from external accounts failed.
    When i push in test connection, show a popup very long, but with any error type detail, only a line with data of the connection.
    I search in release notes but don't find any about this.

    What is the problem?
    Before upgrade work fine.
    thanks

  2. #2
    phoenix is offline Zimbra Consultant & Moderator
    Join Date
    Sep 2005
    Location
    Vannes, France
    Posts
    23,587
    Rep Power
    58

    Default

    You should not upgrade a production system with the Zimbra 6 beta and BTW, it's Zimbra 6 Beta2 and not beta 6.0.2 (that would be a future release number).

    Without the error message and some details of the external account it's impossible to answer your question. What errors do you see in the log files?
    Regards


    Bill


    Acompli: A new adventure for Co-Founder KevinH.

  3. #3
    Join Date
    Jun 2009
    Posts
    5
    Rep Power
    6

    Default This is the log

    This is the log.
    In the account config i have unchecked the ssl and the default port

    2009-06-21 00:05:59,408 INFO [btpool0-8] [name=soporte@mail.el1003.com;mid=3;ip=216.131.118. 26;ua=ZimbraWebClient - IE6 (Win)/6.0.0_BETA2_1547.RHEL5;] soap - TestDataSourceRequest
    2009-06-21 00:05:59,409 INFO [btpool0-8] [name=soporte@mail.el1003.com;mid=3;ip=216.131.118. 26;ua=ZimbraWebClient - IE6 (Win)/6.0.0_BETA2_1547.RHEL5;] datasource - Testing: DataSource: { id=TestId, type=imap, isEnabled=false, name=Test, host=213.162.200.58, port=143, connectionType=cleartext, username=isec, folderId=-1 }
    2009-06-21 00:06:00,264 WARN [btpool0-8] [name=soporte@mail.el1003.com;mid=3;ip=216.131.118. 26;ua=ZimbraWebClient - IE6 (Win)/6.0.0_BETA2_1547.RHEL5;] datasource - Test failed: DataSource: { id=TestId, type=imap, isEnabled=false, name=Test, host=213.162.200.58, port=143, connectionType=cleartext, username=isec, folderId=-1 }
    com.zimbra.common.service.ServiceException: system failure: Unable to connect to IMAP server: DataSource: { id=TestId, type=imap, isEnabled=false, name=Test, host=213.162.200.58, port=143, connectionType=cleartext, username=isec, folderId=-1 }
    ExceptionId:btpool0-8:1245535560264:789e54fcad9a4a67
    Code:service.FAILURE
    at com.zimbra.common.service.ServiceException.FAILURE (ServiceException.java:251)
    at com.zimbra.cs.datasource.ImapSync.connect(ImapSync .java:196)
    at com.zimbra.cs.datasource.ImapSync.test(ImapSync.ja va:123)
    at com.zimbra.cs.datasource.DataSourceManager.test(Da taSourceManager.java:52)
    at com.zimbra.cs.service.mail.TestDataSource.handle(T estDataSource.java:125)
    at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEng ine.java:415)
    at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:272)
    at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:156)
    at com.zimbra.soap.SoapServlet.doPost(SoapServlet.jav a:273)
    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:502)
    at org.mortbay.jetty.servlet.ServletHandler$CachedCha in.doFilter(ServletHandler.java:1148)
    at org.mortbay.servlet.UserAgentFilter.doFilter(UserA gentFilter.java:81)
    at org.mortbay.servlet.GzipFilter.doFilter(GzipFilter .java:119)
    at org.mortbay.jetty.servlet.ServletHandler$CachedCha in.doFilter(ServletHandler.java:1139)
    at org.mortbay.jetty.servlet.ServletHandler.handle(Se rvletHandler.java:378)
    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:765)
    at org.mortbay.jetty.webapp.WebAppContext.handle(WebA ppContext.java:417)
    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:324)
    at org.mortbay.jetty.HttpConnection.handleRequest(Htt pConnection.java:534)
    at org.mortbay.jetty.HttpConnection$RequestHandler.co ntent(HttpConnection.java:879)
    at org.mortbay.jetty.servlet.ServletHandler.handle(Se rvletHandler.java:378)
    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:765)
    at org.mortbay.jetty.webapp.WebAppContext.handle(WebA ppContext.java:417)
    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:324)
    at org.mortbay.jetty.HttpConnection.handleRequest(Htt pConnection.java:534)
    at org.mortbay.jetty.HttpConnection$RequestHandler.co ntent(HttpConnection.java:879)
    at org.mortbay.jetty.HttpParser.parseNext(HttpParser. java:747)
    at org.mortbay.jetty.HttpParser.parseAvailable(HttpPa rser.java:212)
    at org.mortbay.jetty.HttpConnection.handle(HttpConnec tion.java:404)
    at org.mortbay.io.nio.SelectChannelEndPoint.run(Selec tChannelEndPoint.java:409)
    at org.mortbay.thread.BoundedThreadPool$PoolThread.ru n(BoundedThreadPool.java:451)
    Caused by: javax.net.ssl.SSLHandshakeException: java.security.cert.CertificateException: d2:CN14:213.162.200.581:O9:grupoisec2:OU4:mail6:ac cept4:true5:alias23:213.162.200.58:485D1F794:fromi 1214062457000e4:host14:213.162.200.583:icn14:213.1 62.200.582:io9:grupoisec3:iou4:mail3:md532:47B9ED9 3DB81969425998B1B28992DD58:mismatch5:false1:s8:485 D1F794:sha140:F36D06CD524E0483522E1A00B865835F4EC3 3E3E2:toi1245598457000ee
    at com.sun.net.ssl.internal.ssl.Alerts.getSSLExceptio n(Alerts.java:150)
    at com.sun.net.ssl.internal.ssl.SSLSocketImpl.fatal(S SLSocketImpl.java:1584)
    at com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Ha ndshaker.java:174)
    at com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Ha ndshaker.java:168)
    at com.sun.net.ssl.internal.ssl.ClientHandshaker.serv erCertificate(ClientHandshaker.java:848)
    at com.sun.net.ssl.internal.ssl.ClientHandshaker.proc essMessage(ClientHandshaker.java:106)
    at com.sun.net.ssl.internal.ssl.Handshaker.processLoo p(Handshaker.java:495)
    at com.sun.net.ssl.internal.ssl.Handshaker.process_re cord(Handshaker.java:433)
    at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRec ord(SSLSocketImpl.java:877)
    at com.sun.net.ssl.internal.ssl.SSLSocketImpl.perform InitialHandshake(SSLSocketImpl.java:1089)
    at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHa ndshake(SSLSocketImpl.java:1116)
    at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHa ndshake(SSLSocketImpl.java:1100)
    at com.zimbra.common.util.CustomSSLSocket.startHandsh ake(CustomSSLSocket.java:213)
    at com.zimbra.cs.mailclient.MailConnection.startTls(M ailConnection.java:292)
    at com.zimbra.cs.mailclient.MailConnection.connect(Ma ilConnection.java:88)
    at com.zimbra.cs.datasource.ImapSync.connect(ImapSync .java:179)
    ... 33 more
    Caused by: java.security.cert.CertificateException: d2:CN14:213.162.200.581:O9:grupoisec2:OU4:mail6:ac cept4:true5:alias23:213.162.200.58:485D1F794:fromi 1214062457000e4:host14:213.162.200.583:icn14:213.1 62.200.582:io9:grupoisec3:iou4:mail3:md532:47B9ED9 3DB81969425998B1B28992DD58:mismatch5:false1:s8:485 D1F794:sha140:F36D06CD524E0483522E1A00B865835F4EC3 3E3E2:toi1245598457000ee
    at com.zimbra.common.util.CustomTrustManager.checkSer verTrusted(CustomTrustManager.java:89)
    at com.sun.net.ssl.internal.ssl.Js***509TrustManager. checkServerTrusted(SSLContextImpl.java:320)
    at com.sun.net.ssl.internal.ssl.ClientHandshaker.serv erCertificate(ClientHandshaker.java:841)
    ... 44 more

Similar Threads

  1. [SOLVED] Zimbra logwatch.
    By nishith in forum Administrators
    Replies: 5
    Last Post: 06-10-2009, 05:42 PM
  2. Help!!! Moving ZCS does not work!
    By ASebestian in forum Migration
    Replies: 7
    Last Post: 02-12-2009, 06:06 PM
  3. Problem with Mail Server - Need help!
    By joeleo in forum Installation
    Replies: 2
    Last Post: 03-04-2008, 12:03 PM
  4. My Zimbra server down ... please help :)
    By frankb in forum Administrators
    Replies: 2
    Last Post: 12-12-2007, 11:29 AM
  5. Lotus migration
    By babou in forum Migration
    Replies: 15
    Last Post: 03-05-2007, 10:33 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
  •