Zimbra offers Open Source email server software and shared calendar for Linux and the Mac
Go Back   Zimbra :: Forums > Zimbra Collaboration Suite > Users

Welcome to the Zimbra :: Forums!
Welcome, if you would like to post a comment please register. We also encourage you to explore all things Zimbra with our team and members of the community.

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 09-30-2009, 06:56 PM
Junior Member
 
Posts: 9
Default POP3 external acount

Hello everybody , i' am encountering some difficulties using the external acount setup in ZCS OSS 6 Beta2 under Ubuntu 8.04 LTS.

This is my error mesage.

2009-09-30 18:54:58,530 INFO [btpool0-281] [name=dguevara@nxtview.com;mid=11;ip=192.168.1.197; ua=ZimbraWebClient - FF3.0 (Linux)/6.0.0_BETA2_1547.UBUNTU8;]
datasource - Testing: DataSource: { id=TestId, type=pop3, isEnabled=false, name=Test, host=mail.sistemas.com.mx, port=110, connectionType=cleartext, username
=ingenieria, folderId=-1 }
2009-09-30 18:54:58,805 WARN [btpool0-281] [name=dguevara@nxtview.com;mid=11;ip=192.168.1.197; ua=ZimbraWebClient - FF3.0 (Linux)/6.0.0_BETA2_1547.UBUNTU8;]
datasource - Test failed: DataSource: { id=TestId, type=pop3, isEnabled=false, name=Test, host=mail.sistemas.com.mx, port=110, connectionType=cleartext, user
name=ingenieria, folderId=-1 }
com.zimbra.common.service.ServiceException: system failure: Unable to connect to POP3 server: DataSource: { id=TestId, type=pop3, isEnabled=false, name=Test,
host=mail.sistemas.com.mx, port=110, connectionType=cleartext, username=ingenieria, folderId=-1 }
ExceptionId:btpool0-281:1254354898805:6f23f1617d692929
Code:service.FAILURE
at com.zimbra.common.service.ServiceException.FAILURE (ServiceException.java:251)
at com.zimbra.cs.datasource.Pop3Sync.connect(Pop3Sync .java:138)
at com.zimbra.cs.datasource.Pop3Sync.test(Pop3Sync.ja va:83)
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:129)
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.HttpParser.parseNext(HttpParser. java:747)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpPa rser.java:218)
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:CN27:hillaguila01.hillaguila.com1:O5:OCOSA2:OU5 1:Office for Compl
ication of Otherwise Simple Affairs6:accept4:true5:alias37:mail.sistemas.com.m x6C3F5A5C72FE76A4:fromi1215023178000e4:host20:ma il.sistemas.com.mx3:icn27:hil
laguila01.hillaguila.com2:io5:OCOSA3:iou51:Office for Complication of Otherwise Simple Affairs3:md532:8011B35C0C6E3503823A88B7A880DF758:m ismatch5:false1:s16:
D6C3F5A5C72FE76A4:sha140:3601914420AFF5623B98D0BBC E13DF0323BB2E3F2:toi1217615178000ee
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.Pop3Sync.connect(Pop3Sync .java:130)
... 33 more
Caused by: java.security.cert.CertificateException: d2:CN27:hillaguila01.hillaguila.com1:O5:OCOSA2:OU5 1:Office for Complication of Otherwise Simple Affairs6:
accept4:true5:alias37:mail.sistemas.com.mx6C3F5A 5C72FE76A4:fromi1215023178000e4:host20:mail.sistem as.com.mx3:icn27:hillaguila01.hillaguila.com2:io5: OCOSA3:
iou51:Office for Complication of Otherwise Simple Affairs3:md532:8011B35C0C6E3503823A88B7A880DF758:m ismatch5:false1:s166C3F5A5C72FE76A4:sha140:36019 14420AF
F5623B98D0BBCE13DF0323BB2E3F2:toi1217615178000ee
at com.zimbra.common.util.CustomTrustManager.checkSer verTrusted(CustomTrustManager.java:89)
at com.sun.net.ssl.internal.ssl.JsseX509TrustManager. checkServerTrusted(SSLContextImpl.java:320)
at com.sun.net.ssl.internal.ssl.ClientHandshaker.serv erCertificate(ClientHandshaker.java:841)
... 44 more


I think the problems is that the mail server has a certificate that expired.
But i cannot do anything in this server, only tell us this situation.
Could I configure some stuff in the admin to bypass this error?

Thank you very much for your help.

best regards.

Danisam
Reply With Quote
  #2 (permalink)  
Old 10-02-2009, 11:44 AM
Moderator
 
Posts: 441
Default

My first suggestion at this point would be to upgrade to 6.0.1 - don't know if this is related to your running a beta version, but it could be.
Reply With Quote
  #3 (permalink)  
Old 10-02-2009, 11:50 AM
Junior Member
 
Posts: 9
Default

Ok , i will do that , and i came back.
Did you have some documentation around this upgrade, there is no known issues?

Thanks
Reply With Quote
Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes


Similar Threads

Why Join?

Registering let's you ask questions, makes it easier to search, displays any files attached to posts, and notifies you about replies.

blog.zimbra.com




 

SEO by vBSEO ©2011, Crawlability, Inc.