[
https://issues.apache.org/jira/browse/JAMES-1937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15864775#comment-15864775
]
Tellier Benoit commented on JAMES-1937:
---------------------------------------
You can use MimeMessageInputStream then process with Mime4J.
This subject is interresting. Do you have failing tests ? Classes that are
failing in your case ?
Cheers,
Benoit Tellier
> Recognizing the multipart/alternative and nested multipart attachments with
> RFC naming support
> ----------------------------------------------------------------------------------------------
>
> Key: JAMES-1937
> URL: https://issues.apache.org/jira/browse/JAMES-1937
> 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 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?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
