[SOLVED] 6.0.7 external account failure - SSL peer shut down incorrectly

[coldfusion]

dear experts

after upgrade from 6.0.6.1 to 6.0.7 one of the external pop accounts do not work anymore. we get an : "SSL peer shut down incorrectly".
It is strange, that one external domain is ok and the other is not working anymore. Both are from the same provider - but on different servers.

No configuration changes from my side. Until 6.0.7 everything was fine. I´ve also upgraded the server to 6.0.7.1 today with no luck. I allready recreate the external account (job). A third account, which I set up for testing also was ok. Receiving mail from the "problem server" with a normal client like thunderbird / apple mail is ok. outgoing mail is also ok.

System :
Ubuntu 8.04 - x64
ZCS : Network Edition.
External pop3 connection without ssl.

mailbox.log :

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.ja va:108)
at com.zimbra.cs.datasource.DataSourceManager.test(Da taSourceManager.java:176)
at com.zimbra.cs.service.mail.TestDataSource.handle(T estDataSource.java:129)
at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEng ine.java:420)
at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:274)
at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:158)
at com.zimbra.soap.SoapServlet.doWork(SoapServlet.jav a:291)
at com.zimbra.soap.SoapServlet.doPost(SoapServlet.jav a:212)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:727)
at com.zimbra.cs.servlet.ZimbraServlet.service(Zimbra Servlet.java:181)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:820)
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 org.mortbay.jetty.servlet.ServletHandler$CachedCha in.doFilter(ServletHandler.java:1157)
at org.mortbay.servlet.UserAgentFilter.doFilter(UserA gentFilter.java:81)
at org.mortbay.servlet.GzipFilter.doFilter(GzipFilter .java:132)
at org.mortbay.jetty.servlet.ServletHandler$CachedCha in.doFilter(ServletHandler.java:1157)
at org.mortbay.jetty.servlet.ServletHandler.handle(Se rvletHandler.java:388)
at org.mortbay.jetty.security.SecurityHandler.handle( SecurityHandler.java:216)
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: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(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.handler.DebugHandler.handle(Debu gHandler.java:77)
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:543)
at org.mortbay.jetty.HttpConnection$RequestHandler.co ntent(HttpConnection.java:939)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser. java:755)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpPa rser.java:212)
at org.mortbay.jetty.HttpConnection.handle(HttpConnec tion.java:405)
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: Remote host closed connection during handshake
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRec ord(SSLSocketImpl.java:808)
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.Pop3Sync.connect(Pop3Sync .java:157)
... 38 more
Caused by: java.io.EOFException: SSL peer shut down incorrectly
at com.sun.net.ssl.internal.ssl.InputRecord.read(Inpu tRecord.java:333)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRec ord(SSLSocketImpl.java:789)
... 45 more

Something is not correct at the handshake procedure - timing ???

I have no plan what can be wrong. Any idea? Thanks for your help..

[coldfusion]

Is it possible to go back to 6.0.6 without any trouble?
Or is it possible to use fetchmail until the problem is solved?

[coldfusion]

setting javamail_pop3_enable_starttls to false in localconfig.xml solved the problem.

Thank you Zimbra Support

[fyd]

That didn't help me dude .. restarted mailbox after making that change in localconfig.xml with the hope that it would fix the SSL peer shutdown error but now it gives me this

Error: Re-Authentication Failure

Looking for error in mailbox.log doesn't show anything. Using 6.0.8. Any help will get a free hug! for sure.

[fyd]

I got this from the logs

----------
Code:service.FAILURE
at com.zimbra.common.service.ServiceException.FAILURE (ServiceException.java:248)
Caused by: javax.security.auth.login.LoginException: Re-Authentication Failure
com.zimbra.common.service.ServiceException: system failure: Unable to connect to IMAP server: DataSource: { id=TestId, type=imap, isEnabled=false, name=Test, host=mx.server.com, port=143, connectionType=cleartext, username=account@domain.net, folderId=-1 }
-----------