[ https://issues.apache.org/jira/browse/TIKA-3710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17545044#comment-17545044 ]
Hudson commented on TIKA-3710: ------------------------------ SUCCESS: Integrated in Jenkins build Tika ยป tika-main-jdk8 #624 (See [https://ci-builds.apache.org/job/Tika/job/tika-main-jdk8/624/]) TIKA-3710 - update mime detection for rfc822, again. (tallison: [https://github.com/apache/tika/commit/a52e4d153e950077f7fdedadcc5d75604fe2563d]) * (add) tika-parsers/tika-parsers-standard/tika-parsers-standard-package/src/test/resources/test-documents/testBrokenHTMLContainingRFC822.html * (edit) tika-parsers/tika-parsers-standard/tika-parsers-standard-package/src/test/java/org/apache/tika/mime/TestMimeTypes.java * (edit) tika-core/src/main/resources/org/apache/tika/mime/tika-mimetypes.xml > HTML document detected incorrect as message/rfc822 > -------------------------------------------------- > > Key: TIKA-3710 > URL: https://issues.apache.org/jira/browse/TIKA-3710 > Project: Tika > Issue Type: Bug > Components: detector > Affects Versions: 2.3.0 > Reporter: Sam Stephens > Priority: Major > Attachments: html-that-looks-like-rfc822.html > > > I'm detecting content types and extracting text from documents using the > AutoDetectParser. > I've received some documents that are HTML fragments generated from emails. > The documents are clearly HTML, not emails, but the AutoDetectParser gives me > the MIME type message/rfc822 and no text. I've attached an example. > It looks like the presence of From:, Sent:, and Subject: at the beginning of > lines is why the documents are matching RFC822. However, I believe the > presence of HTML before these headers means the document is not valid RFC822. -- This message was sent by Atlassian Jira (v8.20.7#820007)