Watson Supply Chain Ideas

Use this form to submit an idea for a new product feature. The product team will review your input and provide status updates as decisions are made regarding the request.

Before you submit a new idea, please view requests that have already been submitted. If your idea has already been submitted, you can add comments or vote on the existing idea, thereby indicating your agreement with the idea. We may use this information to help prioritize development of new features.


Submit ideas for Watson Marketing and Watson Commerce products

Mail MIME Parse: Differentiate body from attachments

When parsing a received email with Mail MIME Service, there is no way
to distinguish the body document from attachment documents.



Which one of PrimaryDocument or Mail_Mime_DOC_2 is the body ?

3 cases:
- Body is in PrimaryDocument
- Body is in Mail_Mime_DOC_2
- Body is actually null, and it turns out PrimaryDocument and
Mail_Mime_DOC_2 are attachments

The problem is the Mail MIME Service assumes that the first document in the MIME message is always the email body. This is wrong.

The RFC 2183 (https://www.ietf.org/rfc/rfc2183.txt) defines how to differentiate the body from attachments, by evaluating the Content-Disposition header.

The Mail MIME Service should evaluate this header as well, and add a new tag in the ProcessData to indicate which returned document is the body (if there is a body in the email).
  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Dec 19 2017
  • Planned for Future Release
How will this idea be used?
What is your industry?
What is the idea priority? High
DeveloperWorks ID DW_ID74237
Link to original RFE http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=74237
  • Attach files