[
https://issues.apache.org/jira/browse/CAMEL-5980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15243054#comment-15243054
]
Rick Johns commented on CAMEL-5980:
-----------------------------------
Should this work when sending the test email as a MimeMessage in a MailMessage
on the Exchange.in? That doesn't look like it can work without a MimeMultipart
converter, which breaks other unit tests. The problem is that a converter will
not handle the default case of a text/plain message correctly. It expects to
not find a converter, and so just return the body, which is the text. But a
MimeMessage needs the converter to retrieve the MimeMultipart message body.
There are some other quirks with the sample email I don't understand. For
example, the entire message can be retrieved but the "[Untitled].pdf"
attachment doesn't appear as a body part. However, it's still in the
MimeMultipart when I look at it as a string. The other pdf shows up as a
separate part. I'm not sure if this is a problem with the email itself,
although it looks OK. When I get a chance I'll try isolating that.
> camel-mail - Better handle null values when extracting attachments
> ------------------------------------------------------------------
>
> Key: CAMEL-5980
> URL: https://issues.apache.org/jira/browse/CAMEL-5980
> Project: Camel
> Issue Type: Improvement
> Components: camel-mail
> Affects Versions: 2.9.0, 2.10.0
> Reporter: Claus Ibsen
> Priority: Minor
> Fix For: Future
>
> Attachments: EmailExceptionTest.java, EmailTest.java, Exception
> Mail.eml, debug_log.txt
>
>
> See nabble
> http://camel.465427.n5.nabble.com/MailComponent-s-claim-to-handle-special-mail-multipart-formats-and-attachments-tp5724859.html
> We should see if we can fix the Camel code to handle those null data.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
