[ https://issues.apache.org/jira/browse/TIKA-4153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tim Allison reopened TIKA-4153: ------------------------------- As part of this issue, I also modified the robots.txt detection. That was a mistake (robots.txt files typically have comments and other stuff at the beginning). I'm reopening this to note that I'm reverting the robots.txt patterns. > 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: some_m...@abc.com <some_m...@abc.com> > 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)