Outlook Connector and "Local Failure Notice"

[sergous]

Client version info: office outlook 2007 (12.0.6535.5005) MSO SP2 (12.0.6535.5002)

File attachment is sync_response.xml, contents:

<?xml version="1.0"?>
<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope"><soap:Header/><soap:Body><SyncResponse xmlns="urn:zimbraMail"><m xmlns="" id="9447" pd="1"/></SyncResponse></soap:Body></soap:Envelope>

[fsiegel]

Thought there might be another attachment, but in any case, you can find out what message id 9447 is and look at it. If you don't need it, you can delete it from the server, and your problems will go away. If you find it on the server, you can do a Show Original on it and send it to me, and maybe I can see why there was a local failure.

To get the message that has Zimbra id 9447, you can use the content servlet:

http://<servername>:<port>/service/content/get?id=9447&fmt=sync

Substitute your servername and port

[sergous]

Thanx, fsiegel, I'll keep you informed regarding this case progress.

[sergous]

Hi fsiegel,

Sending message original in private message.
After 7 Feb error messages stops to come, it was more then 15 of them.

[asi_g]

Hi all,
I receive many "Server failure notice" emails but emails are received and sent with no problems.
It is just the annoyance of deleting the notices (automatic trashing doesn't work).
Before the example, another input which might be important, I am viewing 3 Zimbra mail boxes in my Outlook.
I do have an attachment to most of the notices. For example (also attached an email which I received before the notice):

<?xml version="1.0"?>
-<SyncError>-<Request>-<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope">-<soap:Header>-<context xmlns="urn:zimbra"><userAgent version="6.0.5981.7" name="ZimbraConnectorForOutlook"/><nonotify/><noqualify/><account by="id">68231fab-2e4e-46b8-825b-fa9d5b22ae0f</account><authToken>0_cb2b49b2534140191ae15764c5a03 25d13a9fd6e_69643d33363a37323464646564362d61646132 2d346237392d396664652d3031616661343831633439393b65 78703d31333a313331303032383231343631333b76763d313a 303b747970653d363a7a696d6272613b</authToken><nosession/></context></soap:Header>-<soap:Body>-<SaveDraftRequest xmlns="urn:zimbraMail"><m id="11946" aid="cc153503-fbc2-4517-91fc-ac4d03bb997f:42684928-072d-4741-9770-e8cc5a5940d5"/></SaveDraftRequest></soap:Body></soap:Envelope></Request>-<Response>-<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope">-<soap:Header>-<context xmlns="urn:zimbra"><change token="50134" acct="68231fab-2e4e-46b8-825b-fa9d5b22ae0f"/></context></soap:Header>-<soap:Body>-<soap:Fault>-<soap:Code><soap:Value>soap:Sender</soap:Value></soap:Code>-<soap:Reason><soap:Text>cannot modify immutable object: 11946</soap:Text></soap:Reason>-<soapetail>-<Error xmlns="urn:zimbra"><Code>mail.IMMUTABLE_OBJECT</Code><Trace>com.zimbra.cs.mailbox.MailServiceExcep tion: cannot modify immutable object: 11946 ExceptionId:btpool0-80955://ox.abt.co.il/service/soap/SaveDraftRequest:1310010518911:eb3b43a746305d2a Code:mail.IMMUTABLE_OBJECT ArgitemId, IID, "11946") at com.zimbra.cs.mailbox.MailServiceException.IMMUTAB LE_OBJECT(MailServiceException.java:379) at com.zimbra.cs.mailbox.Mailbox.saveDraft(Mailbox.ja va:4759) at com.zimbra.cs.service.mail.SaveDraft.handle(SaveDr aft.java:116) 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:155) 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) </Trace><a n="itemId" t="IID">11946</a></Error></soapetail></soap:Fault></soap:Body></soap:Envelope></Response></SyncError>

Thanks to the people taking the time to help with this

[fsiegel]

Any virus checking going on? Sometimes this can happen when a virus checker tries to update a message. They try to add "scanned" flags, etc.

[fsiegel]

[SOLVED] Server failures on shared inbox