Unhandled RuntimeException with Djigzo 1.4.0-5

Hello

today we got the following in the logs for an outgoing mail:

12 Jan 2011 09:32:24 | INFO decryptKeepSignature | MailID:
c1186b0f-e855-4dc9-9077-a5c402f3f97e; Sender: xxxx(a)satzundmedien.de;
   (mitm.application.djigzo.james.mailets.Log) [Spool Thread #0]
12 Jan 2011 09:32:24 | WARN Don't know how to handle the extracted
content. Class: javax.mail.util.SharedByteArrayInputStream
(mitm.common.mail.BodyPartUtils) [Spool Thread #0]
12 Jan 2011 09:32:24 | ERROR Unhandled RuntimeException.
(mitm.application.djigzo.james.mailets.SMIMEHandler) [Spool Thread #0]
org.apache.commons.lang.NullArgumentException: part must not be null.
  at mitm.common.util.Check.notNull(Check.java:45)
  at
mitm.common.security.smime.SMIMEInspectorImpl.<init>(SMIMEInspectorImpl.java:60)
  at
mitm.common.security.smime.handler.SMIMEHandler.handlePart(SMIMEHandler.java:341)
  at
mitm.common.security.smime.handler.RecursiveSMIMEHandler.internalHandlePart(RecursiveSMIMEHandler.java:183)
  at
mitm.common.security.smime.handler.RecursiveSMIMEHandler.access$000(RecursiveSMIMEHandler.java:46)
  at
mitm.common.security.smime.handler.RecursiveSMIMEHandler$AttachedPartHandler.handlePart(RecursiveSMIMEHandler.java:247)
  at
mitm.common.security.smime.handler.AttachedSMIMEHandler.onPart(AttachedSMIMEHandler.java:142)
  at
mitm.common.security.smime.handler.AttachedSMIMEHandler.access$000(AttachedSMIMEHandler.java:73)
  at
mitm.common.security.smime.handler.AttachedSMIMEHandler$1.onPart(AttachedSMIMEHandler.java:277)
  at mitm.common.mail.PartScanner.scanPart(PartScanner.java:135)
  at mitm.common.mail.PartScanner.scanPart(PartScanner.java:119)
  at mitm.common.mail.PartScanner.scanPart(PartScanner.java:88)
  at
mitm.common.security.smime.handler.AttachedSMIMEHandler.handlePart(AttachedSMIMEHandler.java:286)
  at
mitm.common.security.smime.handler.RecursiveSMIMEHandler.internalHandlePart(RecursiveSMIMEHandler.java:216)
  at
mitm.common.security.smime.handler.RecursiveSMIMEHandler.handlePart(RecursiveSMIMEHandler.java:232)
  at
mitm.application.djigzo.james.mailets.SMIMEHandler.handleMessageAction(SMIMEHandler.java:352)
  at
mitm.application.djigzo.james.mailets.SMIMEHandler.access$200(SMIMEHandler.java:82)
  at
mitm.application.djigzo.james.mailets.SMIMEHandler$1.doAction(SMIMEHandler.java:286)
  at
mitm.application.djigzo.james.mailets.SMIMEHandler$1.doAction(SMIMEHandler.java:277)
  at
mitm.common.hibernate.DatabaseActionExecutorImpl.executeTransaction(DatabaseActionExecutorImpl.java:64)
  at
mitm.common.hibernate.DatabaseActionExecutorImpl.executeTransaction(DatabaseActionExecutorImpl.java:112)
  at
mitm.common.hibernate.DatabaseActionExecutorImpl.executeTransaction(DatabaseActionExecutorImpl.java:104)
  at
mitm.application.djigzo.james.mailets.SMIMEHandler.serviceMail(SMIMEHandler.java:276)
  at
mitm.application.djigzo.james.mailets.AbstractDjigzoMailet.service(AbstractDjigzoMailet.java:239)
  at
org.apache.james.transport.LinearProcessor.service(LinearProcessor.java:424)
  at
org.apache.james.transport.JamesSpoolManager.process(JamesSpoolManager.java:405)
  at
org.apache.james.transport.JamesSpoolManager.run(JamesSpoolManager.java:309)
  at java.lang.Thread.run(Thread.java:636)
12 Jan 2011 09:32:24 | INFO postDecrypt | MailID:
c1186b0f-e855-4dc9-9077-a5c402f3f97e; Sender: xxxx(a)satzundmedien.de;
   (mitm.application.djigzo.james.mailets.Log) [Spool Thread #0]

The mail seems to go out anyway, but i wonder why this happend. The
system has ECC RAM, Ubuntu 8.04 LTS + latest fixes and Djigzo 1.4.0-5
running. No other errors logged for the time of the event.

Many Thanks

Andreas

It seems that the message contained a message/rfc822 attachment but the
attached message could not be extracted by Java.

WARN Don't know how to handle the extracted content. Class:
javax.mail.util.SharedByteArrayInputStream

When extracting an attached message, the message should result in a
MimeMessage and not in a SharedByteArrayInputStream.

Could it be that the attached message/rfc822 was corrupt?

Can you replicate this? If I would have a message that triggers this I
can perhaps see how to handle it better.

The mail seems to go out anyway...

When a message cannot be handled, it's still being sent out and/or
delivered.

Kind regards,

Martijn

···

On 01/-10/-28163 08:59 PM, lst_hoe02(a)kwsoft.de wrote:

Hello

today we got the following in the logs for an outgoing mail:

12 Jan 2011 09:32:24 | INFO decryptKeepSignature | MailID:
c1186b0f-e855-4dc9-9077-a5c402f3f97e; Sender: xxxx(a)satzundmedien.de;
(mitm.application.djigzo.james.mailets.Log) [Spool Thread #0]
12 Jan 2011 09:32:24 | WARN Don't know how to handle the extracted
content. Class: javax.mail.util.SharedByteArrayInputStream
(mitm.common.mail.BodyPartUtils) [Spool Thread #0]
12 Jan 2011 09:32:24 | ERROR Unhandled RuntimeException.
(mitm.application.djigzo.james.mailets.SMIMEHandler) [Spool Thread #0]
org.apache.commons.lang.NullArgumentException: part must not be null.
    at mitm.common.util.Check.notNull(Check.java:45)
    at
mitm.common.security.smime.SMIMEInspectorImpl.<init>(SMIMEInspectorImpl.java:60)

    at
mitm.common.security.smime.handler.SMIMEHandler.handlePart(SMIMEHandler.java:341)

    at
mitm.common.security.smime.handler.RecursiveSMIMEHandler.internalHandlePart(RecursiveSMIMEHandler.java:183)

    at
mitm.common.security.smime.handler.RecursiveSMIMEHandler.access$000(RecursiveSMIMEHandler.java:46)

    at
mitm.common.security.smime.handler.RecursiveSMIMEHandler$AttachedPartHandler.handlePart(RecursiveSMIMEHandler.java:247)

    at
mitm.common.security.smime.handler.AttachedSMIMEHandler.onPart(AttachedSMIMEHandler.java:142)

    at
mitm.common.security.smime.handler.AttachedSMIMEHandler.access$000(AttachedSMIMEHandler.java:73)

    at
mitm.common.security.smime.handler.AttachedSMIMEHandler$1.onPart(AttachedSMIMEHandler.java:277)

    at mitm.common.mail.PartScanner.scanPart(PartScanner.java:135)
    at mitm.common.mail.PartScanner.scanPart(PartScanner.java:119)
    at mitm.common.mail.PartScanner.scanPart(PartScanner.java:88)
    at
mitm.common.security.smime.handler.AttachedSMIMEHandler.handlePart(AttachedSMIMEHandler.java:286)

    at
mitm.common.security.smime.handler.RecursiveSMIMEHandler.internalHandlePart(RecursiveSMIMEHandler.java:216)

    at
mitm.common.security.smime.handler.RecursiveSMIMEHandler.handlePart(RecursiveSMIMEHandler.java:232)

    at
mitm.application.djigzo.james.mailets.SMIMEHandler.handleMessageAction(SMIMEHandler.java:352)

    at
mitm.application.djigzo.james.mailets.SMIMEHandler.access$200(SMIMEHandler.java:82)

    at
mitm.application.djigzo.james.mailets.SMIMEHandler$1.doAction(SMIMEHandler.java:286)

    at
mitm.application.djigzo.james.mailets.SMIMEHandler$1.doAction(SMIMEHandler.java:277)

    at
mitm.common.hibernate.DatabaseActionExecutorImpl.executeTransaction(DatabaseActionExecutorImpl.java:64)

    at
mitm.common.hibernate.DatabaseActionExecutorImpl.executeTransaction(DatabaseActionExecutorImpl.java:112)

    at
mitm.common.hibernate.DatabaseActionExecutorImpl.executeTransaction(DatabaseActionExecutorImpl.java:104)

    at
mitm.application.djigzo.james.mailets.SMIMEHandler.serviceMail(SMIMEHandler.java:276)

    at
mitm.application.djigzo.james.mailets.AbstractDjigzoMailet.service(AbstractDjigzoMailet.java:239)

    at
org.apache.james.transport.LinearProcessor.service(LinearProcessor.java:424)

    at
org.apache.james.transport.JamesSpoolManager.process(JamesSpoolManager.java:405)

    at
org.apache.james.transport.JamesSpoolManager.run(JamesSpoolManager.java:309)

    at java.lang.Thread.run(Thread.java:636)
12 Jan 2011 09:32:24 | INFO postDecrypt | MailID:
c1186b0f-e855-4dc9-9077-a5c402f3f97e; Sender: xxxx(a)satzundmedien.de;
(mitm.application.djigzo.james.mailets.Log) [Spool Thread #0]

The mail seems to go out anyway, but i wonder why this happend. The
system has ECC RAM, Ubuntu 8.04 LTS + latest fixes and Djigzo 1.4.0-5
running. No other errors logged for the time of the event.

Many Thanks

Andreas

--
Djigzo open source email encryption