Server Notification Failure

[JC-Sol1]

Hi Folks,

So we have a client who is running there own Zimbra server, and they are all using outlook though with most of them when they send emails or move emails between folders they receive an email say server notification failure, though the email is sent/moved. Occasionally the email contains there email attached but normally not.

If anyone can help me with this issue it would be greatly appreciated

[phoenix]

So we have a client who is running there own Zimbra server, and they are all using outlook though with most of them when they send emails or move emails between folders they receive an email say server notification failure, though the email is sent/moved. Occasionally the email contains there email attached but normally not.

Why is this in the Zimbra Desktop forum?

You haven't given many details about the problem: which Zimbra version & release; is this using the Outlook Connector; if you're using the connector then which version is it?

[JC-Sol1]

Yes they are using the outlook connector v6.02 and the same version of zimbra. Though this issue only started occuring once they upgraded to 6.02.
This is happening with other peoples mailboxes they have open not there own.

This is the error message:
5e08d7ce-d15c-43bb-b189-2fac6422dc080_2cd2863ff308fa12b604d206b3711c10c34b e7b0_69643d33363a63663232613831392d623261332d34323 5662d383137372d6262653432306631373139353b6578703d3 1333a313235383636363431353133333b747970653d363a7a6 96d6272613bsoap:Sendercannot modify immutable object: 80473mail.IMMUTABLE_OBJECTbtpool0-586://zimbra/service/soap/SaveDraftRequest:1258493958639:afba1c33e0ae1b15804 73

[JC-Sol1]

So I have done a bit more digging in the logs on the zimbra server and this is the error in there. If you know what needs to be done to finx this please help.

2009-12-02 12:06:31,281 WARN [LmtpServer-1010] [name=someone@here.com.au;mid=9;ip=192.168.1.101;] indexadd - Caught exception while indexing message id 26088 - indexing blocked. Possibly corrupt index?
com.zimbra.common.service.ServiceException: system failure: indexMailItem caught IOException
ExceptionId:LmtpServer-1010:1259715991281:935c5e0b54b5bc92
Code:service.FAILURE
at com.zimbra.common.service.ServiceException.FAILURE (ServiceException.java:247)
at com.zimbra.cs.index.MailboxIndex.indexMailItem(Mai lboxIndex.java:516)
at com.zimbra.cs.mailbox.IndexHelper.indexingPartOfEn dTransaction(IndexHelper.java:995)
at com.zimbra.cs.mailbox.Mailbox.endTransaction(Mailb ox.java:6669)
at com.zimbra.cs.mailbox.IndexHelper.indexItemList(In dexHelper.java:890)
at com.zimbra.cs.mailbox.IndexHelper.indexDeferredIte msInternal(IndexHelper.java:360)
at com.zimbra.cs.mailbox.IndexHelper.indexDeferredIte ms(IndexHelper.java:278)
at com.zimbra.cs.mailbox.IndexHelper.maybeIndexDeferr edItems(IndexHelper.java:234)
at com.zimbra.cs.mailbox.Mailbox.addMessage(Mailbox.j ava:4233)
at com.zimbra.cs.mailbox.Mailbox.addMessage(Mailbox.j ava:4226)
at com.zimbra.cs.mailbox.Mailbox.addMessage(Mailbox.j ava:4186)
at com.zimbra.cs.filter.IncomingMessageHandler.addMes sage(IncomingMessageHandler.java:116)
at com.zimbra.cs.filter.IncomingMessageHandler.implic itKeep(IncomingMessageHandler.java:109)
at com.zimbra.cs.filter.ZimbraMailAdapter.doDefaultFi ling(ZimbraMailAdapter.java:284)
at com.zimbra.cs.filter.ZimbraMailAdapter.executeActi ons(ZimbraMailAdapter.java:188)
at org.apache.jsieve.SieveFactory.evaluate(SieveFacto ry.java:164)
at com.zimbra.cs.filter.RuleManager.applyRulesToIncom ingMessage(RuleManager.java:348)
at com.zimbra.cs.filter.RuleManager.applyRulesToIncom ingMessage(RuleManager.java:311)
at com.zimbra.cs.lmtpserver.ZimbraLmtpBackend.deliver MessageToLocalMailboxes(ZimbraLmtpBackend.java:425 )
at com.zimbra.cs.lmtpserver.ZimbraLmtpBackend.deliver MessageToLocalMailboxes(ZimbraLmtpBackend.java:257 )
at com.zimbra.cs.lmtpserver.ZimbraLmtpBackend.deliver (ZimbraLmtpBackend.java:162)
at com.zimbra.cs.lmtpserver.LmtpHandler.processMessag eData(LmtpHandler.java:365)
at com.zimbra.cs.lmtpserver.TcpLmtpHandler.continueDA TA(TcpLmtpHandler.java:72)
at com.zimbra.cs.lmtpserver.LmtpHandler.doDATA(LmtpHa ndler.java:350)
at com.zimbra.cs.lmtpserver.LmtpHandler.processComman d(LmtpHandler.java:170)
at com.zimbra.cs.lmtpserver.TcpLmtpHandler.processCom mand(TcpLmtpHandler.java:66)
at com.zimbra.cs.tcpserver.ProtocolHandler.processCon nection(ProtocolHandler.java:175)
at com.zimbra.cs.tcpserver.ProtocolHandler.run(Protoc olHandler.java:132)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Wo rker.run(Unknown Source)
at java.lang.Thread.run(Thread.java:619)

[fsiegel]

Looks like a server issue.