Return-Path: X-Original-To: apmail-james-mime4j-dev-archive@minotaur.apache.org Delivered-To: apmail-james-mime4j-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id BA3F91072B for ; Wed, 8 Jan 2014 15:50:18 +0000 (UTC) Received: (qmail 20562 invoked by uid 500); 8 Jan 2014 15:50:15 -0000 Delivered-To: apmail-james-mime4j-dev-archive@james.apache.org Received: (qmail 20235 invoked by uid 500); 8 Jan 2014 15:50:07 -0000 Mailing-List: contact mime4j-dev-help@james.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: mime4j-dev@james.apache.org Delivered-To: mailing list mime4j-dev@james.apache.org Received: (qmail 19889 invoked by uid 99); 8 Jan 2014 15:50:01 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 08 Jan 2014 15:50:01 +0000 Date: Wed, 8 Jan 2014 15:50:01 +0000 (UTC) From: "Oleg Kalnichevski (JIRA)" To: mime4j-dev@james.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (MIME4J-235) NPE during parsing of an message MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/MIME4J-235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13865569#comment-13865569 ] Oleg Kalnichevski commented on MIME4J-235: ------------------------------------------ {noformat} ----------MB_8CFAAB0E6BFFBB7_16A8_733DA_webmail-d055.sysops.aol.com Content-Type: multipart/ALTERNATIVE; boundary*0=--------MB_8CFAAB0E6BFFBB7_16A8_733DB_webmail-d055.sysops.aol.co; boundary*1=m {noformat} Can anyone tell me if the Content-Type header is malformed or not? It looks malformed to me. Mime4j clearly does not support such header folding. So, all I can think of doing is throwing a more meaningful exception. Oleg > NPE during parsing of an message > -------------------------------- > > Key: MIME4J-235 > URL: https://issues.apache.org/jira/browse/MIME4J-235 > Project: James Mime4j > Issue Type: Bug > Components: parser (core) > Affects Versions: 0.8.0 > Reporter: Mariano Kamp > Attachments: error-205-NullPointerException.mbox, error-95-NullPointerException.mbox > > > Ran into an NPE. Reported it to the mailing list, was referred to here. > http://mail-archives.apache.org/mod_mbox/james-mime4j-dev/201401.mbox/browser > The linked message also contains the offending mail as well as the full strack trace. > Don't see how I could upload the file here. > java.lang.NullPointerException > at > org.apache.james.mime4j.io.MimeBoundaryInputStream.(MimeBoundaryInputStream.java:67) > at > org.apache.james.mime4j.stream.MimeEntity.createMimePartStream(MimeEntity.java:366) > at > org.apache.james.mime4j.stream.MimeEntity.advance(MimeEntity.java:320) > at > org.apache.james.mime4j.stream.MimeTokenStream.next(MimeTokenStream.java:368) > at > org.apache.james.mime4j.parser.MimeStreamParser.parse(MimeStreamParser.java:176) > at > org.apache.james.mime4j.message.DefaultMessageBuilder.parseMessage(DefaultMessageBuilder.java:316) > at com.mboxanalytics.util.MboxUtil.parseMessage(MboxUtil.java:95) -- This message was sent by Atlassian JIRA (v6.1.5#6160)