Remove from list please

Erb VonHazze 25

> On Jul 20, 2018, at 1:23 AM, Pallavi Goyal <[email protected]> wrote:
> 
> Thanks Jacques!
> 
> Here is the JIRA ticket for the issue: OFBIZ-10490
> <https://issues.apache.org/jira/browse/OFBIZ-10490>.
> 
> Regards,
> Pallavi Goyal
> 
> On Wed, Jul 11, 2018 at 2:53 AM, Jacques Le Roux <
> [email protected]> wrote:
> 
>> Hi Pallavi,
>> 
>> Sorry to be late on this.
>> 
>> Please create a Jira for us to review closer.
>> 
>> This might help: https://cwiki.apache.org/confluence/display/OFBIZ/OFBiz+
>> Contributors+Best+Practices
>> 
>> Thanks
>> 
>> Jacques
>> 
>> 
>>> Le 26/06/2018 à 07:23, Pallavi Goyal a écrit :
>>> 
>>> Hello All,
>>> 
>>> I am using "getMessageBody" method of "MimeMessageWrapper.java" to get the
>>> email message.
>>> 
>>> It works perfectly fine for following cases:
>>> 
>>> 1. When there is a basic message with a basic signature (no images or
>>> attachments)
>>> 2. When there is a basic message with signature containing an image.
>>> 3. When there is a message having attachments with basic signature.
>>> 
>>> Issue:
>>> 
>>> -- When there is a message with the attachment and the signature having an
>>> image.
>>> In the above case, all the data is stored in the database *except* the
>>> actual message content (Eg.  Hello! How are you?).
>>> 
>>> Findings:
>>> 
>>> I checked the structure of the email received in all cases and find out
>>> following:
>>> 
>>> 1. In the cases where everything worked fine, the email parts identifiers
>>> i.e ID was of "0.x" series such as "0.0", "0.1".
>>> 2. In the issue case, the email parts ID was of "0.0.x" series such as
>>> "0.0.0", "0.0.1".
>>> 
>>> I then checked the code and found out that the implementation is hardcoded
>>> to work till "0.x" series only. Therefore all the content which was up to
>>> "0.x" part got stored while the actual message which was in "0.0.x" part
>>> was not stored.
>>> 
>>> Is there anything I missed out? How should I proceed further?
>>> 
>>> Thanks and Regards
>>> Pallavi Goyal
>>> 
>>> 
>> 

Reply via email to