I was importing some psts for users this weekend when i hit one that was going really slow. I took a gander at top and saw load averages of around 96 with 400% utilization of processor (it's a quad core).

The culprit seemed to be a dozen or so kvoop processes. So I looked at mailbox.log and saw things like this

2008-08-31 15:06:51,675 WARN [btpool0-6151] [name=user@domain.com;mid=90;ip=;] ParsedMessage - Unable to parse part 2 (3wrrb5.p3, application/octet-stream) of message with Message-ID null.com.zimbra.cs.mime.MimeHandlerException: cannot extract text

and in convertd.log

2008-08-31 15:32:19,986 INFO [Convertd-6] [] convert - Extracting text from 3wrrb5.p3, docId=j52HQ39xXW4NM2f4dj1GFmYVt84=.
2008-08-31 15:32:19,986 WARN [Convertd-6] [] convert - Text extraction failed
com.zimbra.cs.convert.ConversionException: Cannot extract text from document that previously crashed convertd.

Restarted zimbra and all was good again.I seem to remember this happening with some dgn files, but following a wiki article I got it so it didn't try to convert them. I'm not as sure how to do it here because it's not a recognized mime type.

My question is, should I be concerned that the next time I go to import a pst that has .p3 attachments or if someone e-mails one is it going to cause my server to go haywire again? Is there anything I can do to stop it?