You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mime4j-dev@james.apache.org by "Tellier Benoit (JIRA)" <mi...@james.apache.org> on 2018/01/05 17:22:00 UTC
[jira] [Commented] (MIME4J-266) NPE in
MimeBoundaryInputStream.java:67
[ https://issues.apache.org/jira/browse/MIME4J-266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16313483#comment-16313483 ]
Tellier Benoit commented on MIME4J-266:
---------------------------------------
Hi.
I confirm there is an issue with mime4J 0.7.2 and successfully reproduced it.
I tried reproducing your issue on the latest version of mime4J (0.8.2) and could not reproduce it with your EML.
Given that mime4j 0.7.2 was released in 2007, I would advise you updating to the latest version...
> NPE in MimeBoundaryInputStream.java:67
> --------------------------------------
>
> Key: MIME4J-266
> URL: https://issues.apache.org/jira/browse/MIME4J-266
> Project: James Mime4j
> Issue Type: Bug
> Affects Versions: 0.7.2
> Reporter: Raffaele Gambelli
> Attachments: MimeBoundaryInputStreamNPE.eml
>
>
> I had this NPE, It is the first time that I receive it despite of thousands parsed emails.
> "java.lang.NullPointerException: null
> at org.apache.james.mime4j.io.MimeBoundaryInputStream.<init>(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:360)
> at org.apache.james.mime4j.parser.MimeStreamParser.parse(MimeStreamParser.java:176)
> at org.apache.james.mime4j.message.DefaultMessageBuilder.parseMessage(DefaultMessageBuilder.java:311)
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)