Each user also see's this error about once a week, in addition to the above posted debug:
Upon sending of an email, the message is returned to the draft folder and this message appears in the inbox:
Quote:
Your message "Re: one last piece needed for demo" sent on August 28, 2009 at 11:01 AM to "<<REMOVED>>" can't be delivered. None of the recipients will receive the message. It has been returned to Drafts folder for your review.
----------------------------------------------------------------------------
Product name: Zimbra Desktop
Product version: 1.0
Build ID: 1593
Release type: R
OS Platform: Windows XP x86 5.1
Time of event: 2009-08-28 11:01:20
Error type: account.AUTH_FAILED
Item ID: 1073742413
Error summary: send mail failed
Failure details - PLEASE REMOVE ANY SENSITIVE INFORMATION
----------------------------------------------------------------------------
<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope"><soap:Header><context xmlns="urn:zimbra"><nosession/><userAgent name="Yahoo! Zimbra Desktop" version="1.0_1593_Windows">1.0_1593_Windows</userAgent></context></soap:Header><soap:Body><AuthRequest xmlns="urn:zimbraAccount"><account by="id">113b6428-2502-43ce-a3d8-d75d16ae6f2e</account><password><<REMOVED>></password></AuthRequest></soap:Body></soap:Envelope>
<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope"><soap:Header><context xmlns="urn:zimbra"/></soap:Header><soap:Body><soap:Fault><soap:Code><soa p:Value>soap:Sender</soap:Value></soap:Code><soap:Reason><soap:Text>authentication failed for 113b6428-2502-43ce-a3d8-d75d16ae6f2e</soap:Text></soap:Reason><soap etail><Error xmlns="urn:zimbra"><Code>account.AUTH_FAILED</Code><Trace>btpool0-282:1251475280808:eee543101a8e4aa7</Trace></Error></soapetail></soap:Fault></soap:Body></soap:Envelope>
com.zimbra.common.soap.SoapFaultException: authentication failed for 113b6428-2502-43ce-a3d8-d75d16ae6f2e
ExceptionId:btpool0-282:1251475280808:eee543101a8e4aa7
Code:account.AUTH_FAILED
at com.zimbra.common.soap.Soap12Protocol.soapFault(So ap12Protocol.java:88)
at com.zimbra.common.soap.SoapTransport.extractBodyEl ement(SoapTransport.java:266)
at com.zimbra.common.soap.SoapTransport.parseSoapResp onse(SoapTransport.java:227)
at com.zimbra.common.soap.SoapHttpTransport.invoke(So apHttpTransport.java:295)
at com.zimbra.common.soap.SoapHttpTransport.invoke(So apHttpTransport.java:230)
at com.zimbra.common.soap.SoapTransport.invoke(SoapTr ansport.java:318)
at com.zimbra.common.soap.SoapTransport.invokeWithout Session(SoapTransport.java:305)
at com.zimbra.cs.mailbox.OfflineMailbox.sendRequest(O fflineMailbox.java:776)
at com.zimbra.cs.mailbox.OfflineMailbox.sendRequest(O fflineMailbox.java:740)
at com.zimbra.cs.mailbox.OfflineMailbox.sendRequest(O fflineMailbox.java:736)
at com.zimbra.cs.mailbox.OfflineMailbox.sendRequest(O fflineMailbox.java:732)
at com.zimbra.cs.mailbox.OfflineMailbox.getAuthToken( OfflineMailbox.java:167)
at com.zimbra.cs.mailbox.PushChanges.getZMailbox(Push Changes.java:161)
at com.zimbra.cs.mailbox.PushChanges.uploadMessage(Pu shChanges.java:532)
at com.zimbra.cs.mailbox.PushChanges.sendPendingMessa ges(PushChanges.java:441)
at com.zimbra.cs.mailbox.PushChanges.sendPendingMessa ges(PushChanges.java:518)
at com.zimbra.cs.mailbox.MailboxSync.sync(MailboxSync .java:152)
at com.zimbra.cs.mailbox.OfflineMailbox.sync(OfflineM ailbox.java:140)
at com.zimbra.cs.service.offline.OfflineSync.handle(O fflineSync.java:47)
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: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)
----------------------------------------------------------------------------
|
TO RESOLVE:
We open Desktop Setup,
on Zimbra Desktop My Accounts Screen
Password may have changed. Please go to edit screen of Account Setup to revalidate settings.
Status: can't login
Click "edit"
Click "Validate and Save"
Now Status is "Online"