[
https://issues.apache.org/jira/browse/EMAIL-188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anurag Garg updated EMAIL-188:
------------------------------
Description:
Hi team,
We are facing below issues with apache commons email library
1) When a user is sending email having inline image in body along with image as
an attachment in that case when we are calling getAttachments() method of
MimeMessageparser it is giving both the images because of that we are not able
to distinguish between the actual image as attachment vs inline image.
2) When a user is sending email with .msg file as attachment in that case it is
not even coming as attachment when we are calling getAttachments() method of
MimeMessageparser.
Not sure if the above behavior is expected or not? Can you please look into
this.
was:
Hi team,
We are facing below issues with apache commons email library
1) When user is sending email having inline image in body that is coming as
another attachment because of that we are not able to distinguish between the
actual image as attachment vs inline image.
2) When user in sending email with .msg file as attachment then that is not
coming when we are calling getAttachments() method of MimeMessageparser.
Not sure if the above behavior is expected or not? Can you please look into
this.
> Issues with Apache commons email library
> ----------------------------------------
>
> Key: EMAIL-188
> URL: https://issues.apache.org/jira/browse/EMAIL-188
> Project: Commons Email
> Issue Type: Bug
> Reporter: Anurag Garg
> Priority: Major
>
> Hi team,
> We are facing below issues with apache commons email library
> 1) When a user is sending email having inline image in body along with image
> as an attachment in that case when we are calling getAttachments() method of
> MimeMessageparser it is giving both the images because of that we are not
> able to distinguish between the actual image as attachment vs inline image.
> 2) When a user is sending email with .msg file as attachment in that case it
> is not even coming as attachment when we are calling getAttachments() method
> of MimeMessageparser.
> Not sure if the above behavior is expected or not? Can you please look into
> this.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)