[JAMES-1937] Recognizing the multipart/alternative and nested multipart attachments with RFC naming support

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 3.0-beta4
• Fix Version/s: 3.0.0
• Component/s: James Core
• Flags: Patch, Important
• Assignee: Unassigned
• Reporter: Krishnanunni K
• Created: 13/Feb/17 09:16
• Updated: 21/Mar/17 02:03

Description

I cannot conclude this as an issue / improvement. The JAMES server does not recognize many kind of attachments when creating a MimeMessage object. This includes
1. Nested multipart contents,
2. multipart/alternative types.
3. RFC encoded headers for file names. Like continuation, base64 encoded etc
4. Inline attachments, and proprietary types like the applcation/tnef etc.

Currently , we cannot depend blindly on the Mail.getMessage(), instead we have to build the DOM Tree using MessageBuilder and parse through it.
Can this be solved?