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

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 08-20-2010, 12:15 PM
Junior Member
 
Posts: 7
Default update to 6.0.7 and POP error : "Unrecognized SSL message, plaintext connection?"

Hi,

I've just update from 6.0.4 to 6.0.7_GA_2473.DEBIAN5_64.
Then, I have a POP error with an external mail account: "Unrecognized SSL message, plaintext connection?"
Here is my mailbox.log:
Code:
2010-08-20 19:49:56,293 WARN  [btpool0-64://my.zimbra-server.ltd/service/soap/TestDataSourceRequest] [name=user@my.domain.ltd;mid=12;ip=91.121.88.118;ua=ZimbraWebClient - FF3.0 (Win)/6.0.7_GA_2473.DEBIAN5_64;ds=my@email.ltd;] SoapEngine - handler exception
com.zimbra.common.service.ServiceException: system failure: Unable to connect to POP3 server: DataSource: { id=TestId, type=pop3, isEnabled=false, name=Test, host=host.pop-server.ltd, port=110, connectionType=cleartext, username=my@email.ltd, folderId=2 }
ExceptionId:btpool0-64://my.zimbra-server.ltd/service/soap/TestDataSourceRequest:1282326596293:5344f882ba7c2a21
Code:service.FAILURE
        at com.zimbra.common.service.ServiceException.FAILURE(ServiceException.java:248)
        at com.zimbra.cs.datasource.Pop3Sync.connect(Pop3Sync.java:165)
        at com.zimbra.cs.datasource.Pop3Sync.test(Pop3Sync.java:108)
        at com.zimbra.cs.datasource.DataSourceManager.test(DataSourceManager.java:176)
        at com.zimbra.cs.service.mail.TestDataSource.handle(TestDataSource.java:129)
        at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEngine.java:420)
        at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:274)
        at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:158)
        at com.zimbra.soap.SoapServlet.doWork(SoapServlet.java:291)
        at com.zimbra.soap.SoapServlet.doPost(SoapServlet.java:212)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
        at com.zimbra.cs.servlet.ZimbraServlet.service(ZimbraServlet.java:181)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
        at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511)
        at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1166)
        at com.zimbra.cs.servlet.SetHeaderFilter.doFilter(SetHeaderFilter.java:79)
        at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
        at org.mortbay.servlet.UserAgentFilter.doFilter(UserAgentFilter.java:81)
        at org.mortbay.servlet.GzipFilter.doFilter(GzipFilter.java:132)
        at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
        at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:388)
        at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
        at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
        at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765)
        at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:418)
        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(HandlerWrapper.java:152)
        at org.mortbay.jetty.handler.rewrite.RewriteHandler.handle(RewriteHandler.java:230)
        at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
        at org.mortbay.jetty.handler.DebugHandler.handle(DebugHandler.java:77)
        at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
        at org.mortbay.jetty.Server.handle(Server.java:326)
        at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:543)
        at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:939)
        at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:755)
        at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)
        at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:405)
        at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409)
        at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:451)
Caused by: javax.net.ssl.SSLException: Unrecognized SSL message, plaintext connection?
        at com.sun.net.ssl.internal.ssl.InputRecord.handleUnknownRecord(InputRecord.java:523)
        at com.sun.net.ssl.internal.ssl.InputRecord.read(InputRecord.java:355)
        at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:789)
        at com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1112)
        at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1139)
        at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1123)
        at com.zimbra.common.net.CustomSSLSocket.startHandshake(CustomSSLSocket.java:90)
        at com.zimbra.cs.mailclient.MailConnection.startTls(MailConnection.java:108)
        at com.zimbra.cs.mailclient.MailConnection.connect(MailConnection.java:92)
        at com.zimbra.cs.datasource.Pop3Sync.connect(Pop3Sync.java:157)
        ... 38 more
Well, I have another production server for another client of mine where the same POP external mail account don't fail.
Here is its mailbox.log:
Code:
2010-08-20 18:56:30,661 INFO  [btpool0-34] [name=user@my.domain2.ltd;mid=7;ip=77.194.215.253;ua=ZimbraWebClient - FF3.0 (Win)/5.0.18_GA_3011.UBUNTU8_64;] datasource - Testing: DataSource: { id=TestId, type=pop3, isEnabled=false, name=Test, host=host.pop-server.ltd, port=110, connectionType=cleartext, username=my@email.ltd, folderId=-1 }
2010-08-20 18:56:31,000 INFO  [btpool0-34] [name=user@my.domain2.ltd;mid=7;ip=77.194.215.253;ua=ZimbraWebClient - FF3.0 (Win)/5.0.18_GA_3011.UBUNTU8_64;] datasource - Test succeeded: DataSource: { id=TestId, type=pop3, isEnabled=false, name=Test, host=host.pop-server.ltd, port=110, connectionType=cleartext, username=my@email.ltd, folderId=-1 }
Any idea? Should I downgrade to 6.0.6?

Jean-Martial
Reply With Quote
  #2 (permalink)  
Old 10-07-2010, 06:48 AM
Active Member
 
Posts: 26
Default

Did you ever get this resolved? I have a similar problem but no answers so far.
ZCS can not access zimbra account via POP
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.