[jira] [Comment Edited] (TIKA-3710) HTML document detected incorrect as message/rfc822

["Tim Allison (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/TIKA-3710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17515921#comment-17515921 ] 

Tim Allison edited comment on TIKA-3710 at 4/1/22 1:35 PM:
-----------------------------------------------------------

Y, I agree.  rfc822 detection continues to be a pain.

Did the original html file actually have an html header?  Or did it literally start at <h2>?

We can tighten our rules a bit.


was (Author: tallison@mitre.org):
Did the original html file actually have an html header?  Or did it literally start at <h2>?

> 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.1#820001)