[
https://issues.apache.org/jira/browse/TIKA-3153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17175053#comment-17175053
]
Tim Allison edited comment on TIKA-3153 at 8/10/20, 8:54 PM:
-------------------------------------------------------------
bq.Maybe a regex testing for the presence of at least 2 or 3 standard RFC822
headers?
Y, that's exactly the kind of thing I'd want to be able to specify either in
our current mime structure or in a custom classifier.
was (Author: [email protected]):
bq. [~kkrugler] regex match idea is good, probably faster than a mime4j based
detector. Maybe a regex testing for the presence of at least 2 or 3 standard
RFC822 headers?
Y, that's exactly the kind of thing I'd want to be able to specify either in
our current mime structure or in a custom classifier.
> Text File identified as message/rfc822
> --------------------------------------
>
> Key: TIKA-3153
> URL: https://issues.apache.org/jira/browse/TIKA-3153
> Project: Tika
> Issue Type: Bug
> Components: detector
> Affects Versions: 1.24.1
> Reporter: Akash
> Priority: Major
> Attachments: TextFileIdentifiedAsMessage.txt
>
>
> Text file containing the word Received: is identified as message/rfc22.
> We were earlier using version 1.9 and it used to identify file type properly
> as text/plain.
> Even if multiple lines are there, if one line with Received: is present,
> content type is incorrectly identified.
> To check we can run java -jar tika-app-1.24.1.jar
> TextFileIdentifiedAsMessage.txt
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
