[
https://issues.apache.org/jira/browse/CAMEL-5980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13570055#comment-13570055
]
Axel Roeber commented on CAMEL-5980:
------------------------------------
I am not an email expert, but the difference seems to be that you construct
essential parts of the mail manually instead of using the mail/file as it is.
Maybe the way I did (in the junit test) is wrong but at least I have got the
same exception as we have seen on our live system when one of these emails
wered received.
As I wrote in the forum the mail isn't a typical mail (and may contain some
unusual or perhaps even wrong formats) but it is a mail which was created and
forwarded by Outlook and can be red/displayed without errors by Outlook and
Thunderbird. So to reproduce the error the mail (in the test) must be
constructed as unmodified as possible.
> 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: 2.10.4, 2.11.0
>
> Attachments: debug_log.txt, EmailTest.java, Exception Mail.eml
>
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
