java.net.SocketException when setting up email account

[iyre]

I too have the same problem.

I set up one IMAP mailbox fine, but the second gives this error:

2008-08-05 09:06:03,857 INFO [btpool0-27] [name=zimbra;ip=127.0.0.1;] datasource - Testing DataSource: { id=bd623fff-cb6d-4251-a96e-54df08540baf, type=imap, isEnabled=true, name=gurutoo, host=mail.gurutoo.com, port=143, connectionType=cleartext, username=iyre, folderId=1 }
2008-08-05 09:06:03,887 INFO [btpool0-27] [name=zimbra;ip=127.0.0.1;] datasource - Error connecting to mail store:
java.net.SocketException: Connection reset
at java.net.SocketInputStream.read(Unknown Source)
at com.sun.net.ssl.internal.ssl.InputRecord.readFully (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.cs.mailclient.MailConnection.startTls(M ailConnection.java:273)
at com.zimbra.cs.mailclient.MailConnection.connect(Ma ilConnection.java:89)
at com.zimbra.cs.mailclient.imap.ImapConnection.conne ct(ImapConnection.java:82)
at com.zimbra.cs.datasource.ImapSync.connect(ImapSync .java:134)
at com.zimbra.cs.datasource.ImapSync.test(ImapSync.ja va:103)
at com.zimbra.cs.datasource.DataSourceManager.test(Da taSourceManager.java:66)
at com.zimbra.cs.account.offline.OfflineProvisioning. testDataSource(OfflineProvisioning.java:515)
at com.zimbra.cs.account.offline.OfflineProvisioning. createDataSourceAccount(OfflineProvisioning.java:5 67)
at com.zimbra.cs.account.offline.OfflineProvisioning. createAccount(OfflineProvisioning.java:419)
at com.zimbra.cs.service.admin.CreateAccount.handle(C reateAccount.java:58)
at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEng ine.java:411)
at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:268)
at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:160)
at com.zimbra.soap.SoapServlet.doPost(SoapServlet.jav a:266)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:727)
at com.zimbra.cs.servlet.ZimbraServlet.service(Zimbra Servlet.java:188)
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)
2008-08-05 09:06:03,888 INFO [btpool0-27] [name=zimbra;ip=127.0.0.1;] datasource - Test failed: java.net.SocketException: Connection reset

[turbomettwurst]

Ok, i finally had the time to have a closer look at it and it noticed that connections work fine when used via ssl. Only Plaintext is borked...