[
https://issues.apache.org/jira/browse/CAMEL-5980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13569875#comment-13569875
]
Joe San edited comment on CAMEL-5980 at 2/3/13 7:37 PM:
--------------------------------------------------------
I was not able to analyze the cause for this exception. So I tried to follow a
different approach. This is what I tried:
(1) Installed Apache James mail server on my machine
(2) Wrote a simple program to send and receive emails on my localhost (James
server)
(3) Used the email attachment as given above.
I do not see any errors in this scenario. Attached is the sample program
(EmailTest.java) and the corresponding debug log file (debug_log.txt). Could
anyone offer me additional hints on what could be done?
Thanks for the support!
was (Author: joesan):
I was not able to analyze the cause for this exception. So I tried to
follow a different approach. This is what I tried:
(1) Installed Apache James mail server on my machine
(2) Wrote a simple program to send and receive emails on my localhost (James
server)
(3) Used the email attachment as given above.
I do not see any errors in this scenario. Attached is the sample program and
the corresponding debug log file. Could anyone offer me additional hints on
what could be done?
Thanks for the support!
> 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
