[
https://issues.apache.org/jira/browse/TIKA-4153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17774129#comment-17774129
]
Hudson commented on TIKA-4153:
------------------------------
SUCCESS: Integrated in Jenkins build Tika ยป tika-main-jdk11 #1333 (See
[https://ci-builds.apache.org/job/Tika/job/tika-main-jdk11/1333/])
TIKA-4153 -- tighten RFC822 detection (#1396) (github:
[https://github.com/apache/tika/commit/c2e6b01b070e7961dc37d043018f10d41223fd9f])
* (add) tika-core/src/test/java/org/apache/tika/mime/RFC822DetectionTest.java
* (edit) tika-core/src/main/resources/org/apache/tika/mime/tika-mimetypes.xml
> Update RFC822 detection, again
> ------------------------------
>
> Key: TIKA-4153
> URL: https://issues.apache.org/jira/browse/TIKA-4153
> Project: Tika
> Issue Type: Task
> Reporter: Tim Allison
> Priority: Minor
> Fix For: 2.9.1, 3.0.0-BETA
>
>
> On the user list, Kashif Khan supplied the following example of a file that
> does not start with RFC822 fields, is detected as RFC822...leading to loss of
> text.
> {noformat}
> Some text here 1.
> Some text here 2.
> Some text here 3.
> Original Message----
> From: [email protected] <[email protected]>
> Sent: Thursday, October 31, 2019 9:52 AM
> To: Some person, (The XYZ group)
> Subject: RE: Mr. Random person phone call: MESSAGE
> Hi,
> I am available now to receive the call.
> Some text here 4.
> Some text here 5.**Some text here 6.
> {noformat}
> From what I can tell, we last modified the rfc822 detection on TIKA-4125,
> with the major minShouldMatch refactoring on TIKA-3153.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
