[sergiumartin]

Originally Posted by sergiumartin :
hmm..this is probably related to our problem: i also noticed that since we upgraded (about a week ago) we have in mailbox.log files, lots of exceptions like this :

2009-11-06 00:00:20,996 WARN [LmtpServer-7360

[name=ipomian@myserver.com;mid=25;ip=192.168.29.8;] ParsedMessage - exception while analyzing message; message will be partially indexed
java.lang.NullPointerException
at com.zimbra.cs.mime.MimeHandlerManager.lookUpMimeTy peInfo(MimeHandlerManager.java:196)
at com.zimbra.cs.mime.MimeHandlerManager.loadHandler( MimeHandlerManager.java:119)
at com.zimbra.cs.mime.MimeHandlerManager.getMimeHandl er(MimeHandlerManager.java:82)
at com.zimbra.cs.mime.ParsedMessage.analyzePart(Parse dMessage.java:1049)
at com.zimbra.cs.mime.ParsedMessage.analyzeBodyParts( ParsedMessage.java:385)
at com.zimbra.cs.mime.ParsedMessage.getFragment(Parse dMessage.java:635)
at com.zimbra.cs.mailbox.Message.encodeMetadata(Messa ge.java:1008)
at com.zimbra.cs.mailbox.Message.createInternal(Messa ge.java:426)
at com.zimbra.cs.mailbox.Message.create(Message.java: 360)
at com.zimbra.cs.mailbox.Mailbox.addMessageInternal(M ailbox.java:4446)
at com.zimbra.cs.mailbox.Mailbox.addMessage(Mailbox.j ava:4293)
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.FilterUtil.addMessage(FilterU til.java:280)
at com.zimbra.cs.filter.IncomingMessageHandler.fileIn to(IncomingMessageHandler.java:86)
at com.zimbra.cs.filter.ZimbraMailAdapter.fileInto(Zi mbraMailAdapter.java:324)
at com.zimbra.cs.filter.ZimbraMailAdapter.executeActi ons(ZimbraMailAdapter.java:201)
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)


ArcaneMagus;161145]Actually serguimartin that index error is: Bug 42599 – Message causes NPE on ReIndex - indexing blocked
You can see some more discussion on that in this thread: Problems with mail search since upgrade to 6.0.1
...

I'm returning to this issue (a little off topic probably) because we also have users reporting searching problems (to be more specific, since the upgrade the latest emails are not included in the search results) ..

ArcaneMagnus, you mentioned is related to bug 42599 but as you can see our error is different from the one stated in that bugzilla :
indexadd - Caught exception while
indexing message id 17813 - indexing blocked. Possibly corrupt index?
java.lang.NullPointerException: value cannot be null
...

You can see that the exception is different..the exceptions are probably related (?), but i wanted to point this out so Zimbra would also take this into consideration when fixing bug 42599..
Any workarounds for this issue? Our boss and also other people from the company are having really lots of emails so the searching function not working properly is a big minus for us at this moment..