Here are the log entries:
2009-02-04 09:36:58,879 INFO [btpool0-11] [] datasource - Testing: DataSource: { id=d404dc95-3d52-4b2a-a774-c7095219e5c9, type=pop3, isEnabled=true, name=admin@kdz.eu, host=mail.kdz.eu, port=110, connectionType=cleartext, username=admin+kdz.eu, folderId=2 }
2009-02-04 09:36:59,130 WARN [btpool0-11] [] datasource - Test failed: DataSource: { id=d404dc95-3d52-4b2a-a774-c7095219e5c9, type=pop3, isEnabled=true, name=admin@kdz.eu, host=mail.kdz.eu, port=110, connectionType=cleartext, username=admin+kdz.eu, folderId=2 }
com.zimbra.common.service.ServiceException: system failure: Unable to connect to IMAP server: DataSource: { id=d404dc95-3d52-4b2a-a774-c7095219e5c9, type=pop3, isEnabled=true, name=admin@kdz.eu, host=mail.kdz.eu, port=110, connectionType=cleartext, username=admin+kdz.eu, folderId=2 }
ExceptionId:btpool0-11:1233736619130:c37250e1e8839e0c
Code:service.FAILURE
at com.zimbra.common.service.ServiceException.FAILURE (ServiceException.java:253)
at com.zimbra.cs.datasource.Pop3Sync.connect(Pop3Sync .java:139)
at com.zimbra.cs.datasource.Pop3Sync.test(Pop3Sync.ja va:95)
at com.zimbra.cs.datasource.DataSourceManager.test(Da taSourceManager.java:64)
at com.zimbra.cs.account.offline.OfflineProvisioning. testDataSource(OfflineProvisioning.java:549)
at com.zimbra.cs.account.offline.OfflineProvisioning. createDataSourceAccount(OfflineProvisioning.java:6 41)
at com.zimbra.cs.account.offline.OfflineProvisioning. createAccount(OfflineProvisioning.java:446)
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:269)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:727)
at com.zimbra.cs.servlet.ZimbraServlet.service(Zimbra Servlet.java:190)
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: javax.net.ssl.SSLException: Unrecognized SSL message, plaintext connection?
at com.sun.net.ssl.internal.ssl.InputRecord.handleUnk nownRecord(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:294)
at com.zimbra.cs.mailclient.MailConnection.connect(Ma ilConnection.java:90)
at com.zimbra.cs.datasource.Pop3Sync.connect(Pop3Sync .java:131)
... 32 more
Even if the POP server advertises TLS but doesn't really support it, other mailers I tried did not have a problem with that. So at least there should be a setting somewhere where I can tell ZD not to try it?
- Bernhard |