Sync Error with Yahoo! Folder

[SFLD]

Debug message: Connection is closed

Exception:

com.zimbra.common.service.ServiceException: system failure: Synchronization of folder '/Resume Postings' failed
ExceptionId:btpool0-0:1262297345813:f6768a92864127ee
Code:service.FAILURE
at com.zimbra.common.service.ServiceException.FAILURE (ServiceException.java:253)
at com.zimbra.cs.datasource.ImapSync.syncFailed(ImapS ync.java:298)
at com.zimbra.cs.datasource.ImapSync.syncMessages(Ima pSync.java:260)
at com.zimbra.cs.datasource.ImapSync.syncFolders(Imap Sync.java:195)
at com.zimbra.cs.datasource.ImapSync.importData(ImapS ync.java:152)
at com.zimbra.cs.offline.OfflineImport.importData(Off lineImport.java:88)
at com.zimbra.cs.offline.YMailImport.importData(YMail Import.java:53)
at com.zimbra.cs.datasource.DataSourceManager.importD ata(DataSourceManager.java:157)
at com.zimbra.cs.mailbox.LocalMailbox.importData(Loca lMailbox.java:417)
at com.zimbra.cs.mailbox.LocalMailbox.syncAllLocalDat aSources(LocalMailbox.java:389)
at com.zimbra.cs.mailbox.LocalMailbox.sync(LocalMailb ox.java:431)
at com.zimbra.cs.service.offline.OfflineSync.handle(O fflineSync.java:49)
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:275)
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: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: java.io.IOException: Connection is closed
at com.zimbra.cs.mailclient.imap.ImapConnection.sendR equest(ImapConnection.java:459)
at com.zimbra.cs.mailclient.imap.ImapRequest.send(Ima pRequest.java:77)
at com.zimbra.cs.mailclient.imap.ImapRequest.sendChec kStatus(ImapRequest.java:81)
at com.zimbra.cs.mailclient.imap.ImapConnection.doSel ectOrExamine(ImapConnection.java:187)
at com.zimbra.cs.mailclient.imap.ImapConnection.selec t(ImapConnection.java:174)
at com.zimbra.cs.datasource.RemoteFolder.select(Remot eFolder.java:236)
at com.zimbra.cs.datasource.ImapFolderSync.checkUidVa lidity(ImapFolderSync.java:724)
at com.zimbra.cs.datasource.ImapFolderSync.syncMessag es(ImapFolderSync.java:205)
at com.zimbra.cs.datasource.ImapSync.syncMessages(Ima pSync.java:257)
... 35 more

[RyanMeray]

This is the same problem I'm having. Since the program itself hasn't changed, I'm sure the blame is on Yahoo's side, but Zimbra should be all over them trying to get this fixed. Utterly ridiculous. What a horrible product. If Yahoo just allowed unfettered, standards-compliant IMAP like a REAL email provider, we wouldn't have this problem.

[SFLD]

Some feedback would be nice. I know that it works for some Yahoo! mail accounts but why it does not in our cases eludes me.