Fix JAR for Parse Error Exception Raised during Mail Fetching

Fix JAR for Parse Error Exception Raised during Mail Fetching

Issue :
      Some mail are fetched and created as ticket without description due to message corruption temporarily. The issue is can be identified with the below trace. 

Fix : 
      The issue is not recreated when the mail is skipped to next schedule and fetched again.

Error Trace :
  1. [10:02:11:958]|[09-01-2022]|[SYSOUT]|[INFO]|[1378]: -ERR Message corrupted|
  2. [10:02:11:958]|[09-01-2022]|[com.manageengine.servicedesk.mail.core.ProcessMailMessage]|[INFO]|[1378]: com.adventnet.servicedesk.mailutils : processMailContent()|
  3. [10:02:11:958]|[09-01-2022]|[com.manageengine.servicedesk.mail.core.ProcessMailMessage]|[SEVERE]|[1378]: javax.mail.MessagingException|
  4. [10:02:11:958]|[09-01-2022]|[com.manageengine.servicedesk.mail.core.ProcessMailMessage]|[SEVERE]|[1378]: Exception in multipart/* - mp.getCount()......|
  5. [10:02:11:958]|[09-01-2022]|[SYSERR]|[INFO]|[1378]: javax.mail.MessagingException: No inputstream from datasource;
  6.   nested exception is:
  7. java.io.IOException: can't retrieve message #1 in POP3Message.getContentStream|
  8. [10:02:11:958]|[09-01-2022]|[SYSERR]|[INFO]|[1378]:  at javax.mail.internet.MimeMultipart.parse(MimeMultipart.java:600)|


FJAR Description :
  1. FJAR Handles the parse error mentioned above while fetching mails by catching the messaging exception, The same mail will be fetched in the next schedule without any error.
Jar Compatibility

Build No
File Name
12007
1_Empty_Description.fjar
 14006
 14006_8499371.fjar

                  New to ADSelfService Plus?