You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tika.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2018/03/28 16:41:00 UTC
[jira] [Commented] (TIKA-2614) RFC822 treats non-multipart as
attachment
[ https://issues.apache.org/jira/browse/TIKA-2614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16417707#comment-16417707 ]
Hudson commented on TIKA-2614:
------------------------------
UNSTABLE: Integrated in Jenkins build tika-2.x-windows #222 (See [https://builds.apache.org/job/tika-2.x-windows/222/])
TIKA-2614 -- treat simple body inline, not as an attachment (tallison: rev 0af75e0a07b6e0ab1d58e06ab103698b3ca233b6)
* (edit) tika-parsers/src/main/java/org/apache/tika/parser/mail/MailContentHandler.java
* (add) tika-parsers/src/test/resources/test-documents/testRFC822_simple_inline_body.txt
* (edit) tika-parsers/src/test/java/org/apache/tika/parser/mail/RFC822ParserTest.java
> RFC822 treats non-multipart as attachment
> -----------------------------------------
>
> Key: TIKA-2614
> URL: https://issues.apache.org/jira/browse/TIKA-2614
> Project: Tika
> Issue Type: Task
> Reporter: Tim Allison
> Priority: Blocker
> Attachments: TIKA-2614-from-common-crawl.txt
>
>
> Found during regression testing in prep for 1.18, now that we're identifying a lot more rfc822...for those that have no multipart, we need to treat the body "inline" and not as an attachment.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)