You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by "Krishnanunni K (JIRA)" <se...@james.apache.org> on 2017/02/13 09:17:42 UTC
[jira] [Created] (JAMES-1938) Recognizing the multipart/alternative
and nested multipart attachments with RFC naming support
Krishnanunni K created JAMES-1938:
-------------------------------------
Summary: Recognizing the multipart/alternative and nested multipart attachments with RFC naming support
Key: JAMES-1938
URL: https://issues.apache.org/jira/browse/JAMES-1938
Project: James Server
Issue Type: Bug
Components: James Core
Affects Versions: 3.0-beta4
Reporter: Krishnanunni K
Fix For: 3.0.0-beta5
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 application/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?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org