[TIKA-3962] Set RFC822 parser to noRecurse

• Type: Task
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 2.7.0
• Assignee: Unassigned
• Reporter: Tim Allison
• Created: 30/Jan/23 16:08
• Updated: 01/Feb/23 19:10
• Resolved: 30/Jan/23 16:21

Description

On our test file testGroupWiseEml.eml, there's an embedded rfc822 attachment that is currently not treated as an attachment but is inlined.

The relevant section of the test file is:

Content-Type: message/rfc822
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="test.eml"

When I open the email in several email clients, it shows this test.eml correctly as an attachment.

It turns out there's a setting on mime4j's parser "setNoRecurse" that yields the correct behavior on this test file. Given that Tika handles files recursively already by default, I think we should be safe to set no recurse in the mime4j parser and rely on Tika's own recursive parsing.