Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Incoming email message Parsing issue because of message size

SA-11999

Summary



Incoming email body is rendered as HTML document after upgrading Email Exchange server to 2010. Pega email listener gets the email and pass it to user's Parse application which breaks the email body into multiple parts. User's parse application code (non-Pega application) has 4000 characters limitation for Parsing. if email message body content is more than 4000, message parsing fails.

This issue was not happened with the exchange server 2007 as message body come as text message. Message Divide functionality also break with this received HTML content.


Error Messages



Not applicable; parsing error in 3rd party application code.

Steps to Reproduce

  1. Send email from Outlook 2010 and have email listener consume it.
  2. This would requires User's application code to hit the character limit in parsing.

Root Cause



The root cause of this problem is defect/misconfiguration in the operating environment. 

Resolution



This issue is resolved by making the following change to the operating environment: 

User wrote a parser code that would remove the HTML tags from emails before sending it to parse application.
Suggest Edit

Published July 15, 2015 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us