#399 NullPointerException getMimePartTree

[Thomas Wabner]

System: linux
jdk 1.4.2
protocol:imap

if i apply filters in my Inbox i got following
exception trace:

java.lang.NullPointerException
at
org.columba.mail.gui.message.filter.PGPMessageFilter.filter(PGPMessageFilter.java:120)
at
org.columba.mail.gui.message.command.ViewMessageCommand.execute(ViewMessageCommand.java:147)
at
org.columba.core.command.Command.process(Command.java:114)
at
org.columba.core.command.Worker.construct(Worker.java:110)
at
org.columba.core.util.SwingWorker$2.run(SwingWorker.java:58)
at java.lang.Thread.run(Thread.java:534)
at java.lang.Thread.run(Thread.java:534)
java.lang.NullPointerException
at
org.columba.mail.gui.message.viewer.MessageBodytextViewer.view(MessageBodytextViewer.java:185)
at
org.columba.mail.gui.message.MessageController.showMessage(MessageController.java:518)
at
org.columba.mail.gui.message.command.ViewMessageCommand.updateGUI(ViewMessageCommand.java:91)
at
org.columba.core.command.Command.finish(Command.java:267)
at
org.columba.core.command.Worker.finished(Worker.java:127)
at
org.columba.core.util.SwingWorker$1.run(SwingWorker.java:51)
at
java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:178)
at
java.awt.EventQueue.dispatchEvent(EventQueue.java:454)
at
java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:201)
at
java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:151)
at
java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:145)
at
java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:137)
at
java.awt.EventDispatchThread.run(EventDispatchThread.java:100)

=======================================

To see whats wrong i have added some logs into the
PGPFilter class and got following log-output:

09/06/2004 10:00:34 [PGPMessageFilter.filter()]
mimePartTree is null ... we should have a look why

You can have a look into the attached file.

[Thomas Wabner]

the java file which contains the debug output

[Timo Stich]

Logged In: YES
user_id=159246

This was most likely due to a bug in the imap protocol which
has been fixed.